I have seen that error when there is an attempt to parse an xsd file, that is not a
schema. The error is coming from the xerces layer so the question is one of getting hold
of enough info to improve this error. What was the cause here?
I'll see if the binding layer can do a better job of building the exception.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094644#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...