Hi Alex, I got this part to work for the following example: JBossEntityResolver.registerEntity( "../../../../net/opengis/gml/3.2.1/gml.xsd", | "gov/faa/wmscr/OGC/net/opengis/gml/3.2.1/gml.xsd"); This resolves a few of the issues. However, the remainder of them come from something that I don't think I can resolve in this manner. <xsd:include schemaLocation="wxBase.xsd"/> In this case the caller sets the publicId to the targetNamespace, which in this case is "http://www.eurocontrol.int/wx/1.1" and the sysId to "wxBase.xsd". The problem as I see it is that there are many .xsd files that are in the "http://www.eurocontrol.int/wx/1.1" namespace. If JBossEntityResolver uses the publicId and sysId separately and never together, these schema references cannot be resolved down to one .xsd file no matter what registry entries I add. This seems like a problem to me, unless I'm just missing the obvious. Perhaps it lies with the caller, perhaps with the resolver. I'm guessing given that the contract doesn't put them together that it lies with the caller. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263042#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...