Cross reference: https://jira.jboss.org/jira/browse/JBXB-238
Alexey Loubyansky wrote:
XB-wise it means all XB users must be on Java annotation-based binding, XSD-based bindings won't be supported in the AS.
Dependency on xerces may cause a lot of problems to us in the future.Moreover we want to use Java API only to be portable
Which projects are using JBossXB XSD based binding for configuration purposes?
Why cannot we provide our own classes/interfaces for XSD based binding and we are using xerces instead?
BTW, we have the same non trivial problem in JBossWS
Because we won't do better parsing of XSD and its Java represetation than Xerces. I am sure that's one of the reasons you are using it as well. And JBoss WS, BTW, is one of those projects using XSD-based bindings, at least it used to. Otherwise, there might be uses in the AS.
In any way, I can binary-separate the XSD-based binding part (which should be done anyway) and try running the AS to see what fails, if anything.
|Retrieving data ...|