Well, ideally all of the stuff in jaxp-api are part of the JDK or pulled from stax-api. It looks like there are two classes (StAXResult and StAXSource) that aren't in either unless running on IBM Java 6. That kind of sucks. I guess that exclusion should be removed.
Dan On Wed July 15 2009 5:58:05 pm Peter Jones wrote: > Hi there, > > cxf includes the jaxp-ri as a dependency when needed in a couple of > places (only when running with the ibm jdk), but I notice that in > the parent/pom.xml, jaxp-api is specifically excluded: > > <dependency> > <groupId>com.sun.xml.parsers</groupId> > <artifactId>jaxp-ri</artifactId> > <version>1.4.2</version> > <exclusions> > <exclusion> > <groupId>javax.xml.parsers</groupId> > <artifactId>jaxp-api</artifactId> > </exclusion> > </exclusions> > </dependency> > > Is there a good reason to exclude it? I'm seeing some test > failures in common/common when using the ibm jdk > (StaxUtilsTest, W3CDOMStreamReaderTest, and XMLUtilsTest). They > hit a NoClassDefFoundError for javax.xml.transform.stax.StAXResult. > If I don't exclude the jaxp-api, the tests run fine, and thus why > I am wondering if there is a good reason... > > Regards, > Peter > > ---------------------------------------- > Peter Jones > Progress Software > 570 Newfoundland Drive > St. John's, NL, Canada A1A 5B1 > Tel: +1 (709) 738-3725 ext 321 > > Internal wiki: http://wiki.progress.com/display/PRODENG/Home -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
