You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Peter Jones <pj...@progress.com> on 2009/07/15 23:58:05 UTC
jaxp-api exclusion from parent/pom.xml
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
RE: jaxp-api exclusion from parent/pom.xml
Posted by Peter Jones <pj...@progress.com>.
Hi Dan,
Yeah that does kind of suck. I'll remove the exclusion from
the dependency.
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
-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org]
Sent: Thu 7/16/2009 3:04 PM
To: dev@cxf.apache.org
Cc: Peter Jones
Subject: Re: jaxp-api exclusion from parent/pom.xml
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
dkulp@apache.org
http://www.dankulp.com/blog
Re: jaxp-api exclusion from parent/pom.xml
Posted by Daniel Kulp <dk...@apache.org>.
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
dkulp@apache.org
http://www.dankulp.com/blog