-
Bug
-
Resolution: Done
-
Major
-
None
-
None
<!--TODO Parser complains about this
xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/-->
Chris sais:
On Jul 10, 2006, at 7:14 PM, Julien Viet wrote:
> This is a general xml schema issue. Is the namespace URI not correctly registered with the JBossEntityResolver?
Note that the URI causing problem is the standard XML schema address (http://www.w3.org/2001/xml.xsd). I would assume that this schema would be bundled with the WS stack and resolved to the local version at runtime to avoid remote access. Not only this, but even when you have an internet connection available but are behind a firewall/proxy, the XML parser can also fail to retrieve the remote schema...
How do I check what is known by JBossEntityResolver? How do I configure it?
> In case it is not, there is no known workaround. Entity resolution will be handeled by OASIS catalog support in future
What's the timeline on this? Is catalog a standard now? Last time I looked at it (in my previous job), it didn't seem finished/adopted...
- duplicates
-
JBWS-715 wsdl4j does not resolve local copy of xml.xsd
- Closed