Schemas could not be resolved ...

[bernd-wechner]

I am stuck with these messages on starting Eclipse:

!ENTRY org.eclipse.wildwebdeveloper.xml 2 0 2025-07-26 13:53:31.682
!MESSAGE The given URI https://jakarta.ee/xml/ns/jakartaee/application-client_9.xsd from org.eclipse.jst.standard.schemas could not be resolved for local access

!ENTRY org.eclipse.wildwebdeveloper.xml 2 0 2025-07-26 13:53:31.683
!MESSAGE The given URI https://jakarta.ee/xml/ns/jakartaee/jobXML_2_0.xsd from org.eclipse.jst.standard.schemas could not be resolved for local access

!ENTRY org.eclipse.wildwebdeveloper.xml 2 0 2025-07-26 13:53:31.684
!MESSAGE The given URI https://jakarta.ee/xml/ns/jakartaee/beans_3_0.xsd from org.eclipse.jst.standard.schemas could not be resolved for local access

!ENTRY org.eclipse.wildwebdeveloper.xml 2 0 2025-07-26 13:53:31.685
!MESSAGE The given URI https://jakarta.ee/xml/ns/jaxb/bindingschema_3_0.xsd from org.eclipse.jst.standard.schemas could not be resolved for local access

!ENTRY org.eclipse.wildwebdeveloper.xml 2 0 2025-07-26 13:53:31.693
!MESSAGE The given URI https://jakarta.ee/xml/ns/validation/validation-configuration-3.0.xsd from org.eclipse.jst.standard.schemas could not be resolved for local access

!ENTRY org.eclipse.wildwebdeveloper.xml 2 0 2025-07-26 13:53:31.697
!MESSAGE The given URI http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_1.xsd from org.eclipse.jst.standard.schemas could not be resolved for local access

Yet I found each of those schemas in the standard XML catalog:

Window > Preferences > XML > XML Catalog

I couldn't see them in the WWD Catalog:

Window > Preferences > XML (Wild Web Developer) > Catalogs

But I could add the system catalog by clicking Add then selecting:

...workspace/.metadata/.plugins/org.eclipse.wst.xml.core/system_catalog.xml

I can even click the Open in Editor button and search the file and find them in there:

  <uri name="https://jakarta.ee/xml/ns/jakartaee/application-client_9.xsd" uri="https://jakarta.ee/xml/ns/jakartaee/application-client_9.xsd"/>
  <uri name="https://jakarta.ee/xml/ns/jakartaee/jobXML_2_0.xsd" uri="https://jakarta.ee/xml/ns/jakartaee/jobXML_2_0.xsd"/>
  <uri name="https://jakarta.ee/xml/ns/jakartaee/beans_3_0.xsd" uri="https://jakarta.ee/xml/ns/jakartaee/beans_3_0.xsd"/>
  <uri name="https://jakarta.ee/xml/ns/jaxb/bindingschema_3_0.xsd" uri="https://jakarta.ee/xml/ns/jaxb/bindingschema_3_0.xsd"/>
  <uri name="https://jakarta.ee/xml/ns/validation/validation-configuration-3.0.xsd" uri="https://jakarta.ee/xml/ns/validation/validation-configuration-3.0.xsd"/>
  <uri name="http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_1.xsd" uri="http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_1.xsd"/>

Then I start eclipse with:

eclipse -clean -consoleLog

And I still get these complaints!

Why or why? What is happening here?

(They are in Error Log too, which is how I come to see them and wish them gone).

[mickaelistria]

I suspect the LemMinX language server is started without taking some particular network configuration (which seems working in your Eclipse IDE). Do you have some specific network settings in place in your Eclipse IDE ?

[bernd-wechner]

Apologies, but I have no idea what "LemMinX language server" is, nor what "specific network settings" might mean with regard to the Eclipse IDE. You would have to clarify that a little for me to understand your suspicions. But I thank you kindly for your contribution to the issue.

[angelozerr]

@mickaelistria it is not a problem from lemminx but from WWD

wildwebdeveloper/org.eclipse.wildwebdeveloper.xml/src/org/eclipse/wildwebdeveloper/xml/internal/ui/preferences/XMLCatalogs.java

Line 170 in a7496ab

ILog.get().warn("The given URI " + element.getAttribute("uri")

[mickaelistria]

Ah, so the issue is that URLs in here are https while only file is supported?

[angelozerr]

Ah, so the issue is that URLs in here are https while only file is supported?

Yes it is the issue from WWD. If I remember LemMinX should support XML catalog with http uri, so I think the fix in WWD should return the http uri in this case instead of returning null.

I am sorry I will not have time to try and do this fix.

[mickaelistria]

Thanks @angelozerr
@bernd-wechner would you like to contribute a PR removing the constraint just like @angelozerr suggested?

[bernd-wechner]

@bernd-wechner would you like to contribute a PR removing the constraint just like @angelozerr suggested?

Sadly, my finding time for that seems very unlikely. I seem to running from one commitment or interest to the next all day every day ;-).. Loosely I'm hoping to both speed up my Eclipse startup and clean up its console output so am looking loosely and a setup to debug Eclipse itself, but no guarantees, and not likely to produce anything PR worthy any time if at all. We'll see (I have a bit of an uphill curve here just on Java and Eclipse debugging first, which I started primarily because where I'm working right now they use a Java app in part of there sales management and expressed interest in maintenance and fixes ... so I have some basic Java exercises behind me now and might get Eclipse debugging rolling in coming weeks).