Thanks again Alex,
If I understand what you're saying correctly, I must code the mappings in my
application using the registerEntity method calls so that JBoss can resolve them. I think
I can do this, but I also don't know if this isn't a shortcoming of the contract.
I'm open to the possibility that the package mappings in my binding.xml are causing
the issue, but I'm not seeing it after rechecking.
If I'm not mistaken, using the same /OGC/net/opengis/gml prefix as the relative path
in the failing instance is not the correct relative path from where that XSD file exists
in terms of specifying the schemaLocation property. The one with the ../../../../ is
actually correct in terms of a relative path.
OGC\int\eurocontrol\wx\1.1.0\wxBase.xsd is referring to
OGC\net\opengis\gml\3.2.1\gml.xsd using
<xsd:import
namespace="http://www.opengis.net/gml/3.2"
schemaLocation="../../../../net/opengis/gml/3.2.1/gml.xsd"/>
Based on the JBossEntityResolver code, I'm not seeing where a relative path should be
used at all for the sysId (schemaLocation). Is that correct according to the contract?
Perhaps seeing the contract would help me understand better.
Also, I can see in the code where the sysId is checked as a URL, but not the publicId +
"/" + sysId. I don't know if that makes the XSD bad or not, but that is
what I've been given (I don't control the contents of the schema) and the schema
validates. Here's what I mean:
wx.xsd refers to wxBase.xsd, which is located in the same directory, by using the
following:
<xsd:include schemaLocation="wxBase.xsd"/>
Does this make any sense?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263005#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...