Hi Alex and thanks for the response.
This is an issue with a number of XSD files that are present in my jar. I can see that
the XSDs whose imports resolve correctly have a relative URL for the schemaLocation.
Here's a "friendly" URL example:
<xsd:import
namespace="http://www.opengis.net/gml/3.2"
schemaLocation="OGC/net/opengis/gml/3.2.1/gml.xsd"/>
The ones that don't resolve correctly are from a different namespace that is dependent
on the namespace listed above. The difference is they are also using relative URLs from
that other namespace. I think these dependent relative URLs are causing the issue in that
they're not resolving correctly (or at least timely). Here's one that I know logs
the error I posted previously:
<xsd:import
namespace="http://www.opengis.net/gml/3.2"
schemaLocation="../../../../net/opengis/gml/3.2.1/gml.xsd"/>
This URL should resolve as the XSD is valid and everything generates to code and runs
(just very slowly at first because of this). Perhaps, as you suggest, there is also a
solution to be addressed in the calling code to get this URL to resolve. I'll
cross-post to the WS user forums as well.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262769#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...