JARJARing Xerces

[bill.burke]

I think we may want to JARJAR xerces for JBossXB. The question is, are SchemaBindings and ObjectFactories isolated from Xerces?

One thing Bill D just ran into was Xerces problems on running embeddable stuff on Weblogic 9.0. I don't want to have SEAM users have to jump through hoops to get SEAM+EJB3 running on WLS.

[adrian.brock]

Nice version ;-)

www.brocksearch.com?query=xerces+jbossxb

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3905993#3905993

[bill.burke]

I read that thread before posting. This is a different topic. Can and should we JARJAR xerces for JBoss XB. A lot of JEMS projects/products are going go need to run in other app servers where Xerces version mismatching will be a huge problem. JAR JAR may solve this issue, I don't know enough about XB to know if it is worth looking into.

[adrian.brock]

Yes, and did you also read the long discussion where I was arguing
that JBossXB should be able to use any Sax parser and Alex said he will look it
along with the double xsd parse problem.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=71748

JBossWS also has a similar requirement where they can't depend upon
Xerces' XSD model.

JARJAR then becomes irrelevant. We can just use whatever SAX Parser is in the host
environment.

[starksm64]

jarjar would just masks the current schema integration problems. jarjar an xml parser does not in general solve integration problems because there are the shared jaxp factory interfaces coming from the jdk.