Looks like it's an issue of the calling code, not in JBossEntityResolver itself.
I think if the namespace/publicId for the not resolved schemas was mapped to the
schemaLocation/systemId of the resovled schemas it would be able to resolve it. If
that's true then it's a configuration issue and should be fixed in the calling
code (JBossWSEntityResolver, JBossWS code or something on top).
I'd suggest posting this on the WS user forums as well to get the WS team look into
this.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262661#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...