You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Daniel Kulp <da...@iona.com> on 2007/01/22 23:35:24 UTC
Java 6 failures...
Just to let everyone know...
Don't upgrade to java 6 yet unless you want to start debugging tests. There
are a LOT of test failures right now when you use java 6. I'm not sure why
yet. It looks like the XML parsers/validators are very different which is
causing some issues.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
Re: Java 6 failures...
Posted by Cameron Taggart <ca...@gmail.com>.
I'm using Java 6 and a bunch of stuff is bundled with it that you can
override with the endorsed mechanism. In order to get my CXF client
working just now, I had to endorse stax-api-1.0.1.jar. I found it
simplest to put it in jre\lib\endosed. I had to create that folder
first. On my PC, the full path:
D:\java\jdk1.6.0\jre\lib\endorsed\stax-api-1.0.1.jar
It would be nice if there was a list of the bundled api versions. Is
the stax api 1.0 in Java 6? The other override mechanism is passing
in a system property. I think something like this would work.
-Djava.endorsed.dirs=D:/java/cxf-2.0-incubator-M1/lib
That would pick up at least jaxb-api-2.0.jar, jaxws-api-2.0.jar, &
stax-api-1.0.1.jar. Otherwise they won't get loaded in Java 6.
cheers,
Cameron
On 1/22/07, Dan Diephouse <da...@envoisolutions.com> wrote:
> This probably isn't the problem you're encountering, but another potential
> problem source is that JAXB is bundled in J6 Which means depending on the
> version thats in there, there could be bugs which aren't fixed, which might
> cause unit tests to fail.
>
> - Dan
>
> On 1/22/07, Daniel Kulp <da...@iona.com> wrote:
> >
> >
> > Just to let everyone know...
> >
> > Don't upgrade to java 6 yet unless you want to start debugging tests.
> > There
> > are a LOT of test failures right now when you use java 6. I'm not sure
> > why
> > yet. It looks like the XML parsers/validators are very different which
> > is
> > causing some issues.
> >
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727 C: 508-380-7194
> > daniel.kulp@iona.com
> >
>
>
>
> --
> Dan Diephouse
> Envoi Solutions
> http://envoisolutions.com | http://netzooid.com/blog
>
>
Re: Java 6 failures...
Posted by Daniel Kulp <da...@iona.com>.
Peter,
Just FYI, your changes fixed the validation problems in the tools. There are
still core failures and system test failures. I'm hoping some of your
other IBM JDK work might help those as well. :-)
Dan
On Tuesday 23 January 2007 17:23, Peter Jones wrote:
> Hi Dan,
>
> On Tue, Jan 23, 2007 at 04:55:56PM -0500, Daniel Kulp wrote:
> > On Monday 22 January 2007 17:39, Dan Diephouse wrote:
> > > This probably isn't the problem you're encountering, but another
> > > potential problem source is that JAXB is bundled in J6 Which means
> > > depending on the version thats in there, there could be bugs which
> > > aren't fixed, which might cause unit tests to fail.
> >
> > I wish that was the problem. That would be easy to explain.
> >
> > It looks like the XML parser that is in J6 is a bit different than the
> > one in J5. Probably a newer version of xerces or something. In
> > anycase, it's causing much of the WSDL parsing and validating to fail.
> >
> > 7 out of 8 of the org.apache.cxf.tools.validator.WSDLValidationTest
> > test fail. Strange errors like:
> > Error : org.xml.sax.SAXParseException: src-resolve: Cannot resolve the
> > name 'xml:lang' to a(n) 'attribute declaration' component.
>
> I noticed the same sort of error when trying out the ibm jdk yesterday.
> There, IIRC it seemed to be caused by the version of xerces prepending
> file://path_to_current_dir to the baseURI relative path of the imported
> schemas that was passed to the resolver. Anyway, I have a work-around for
> the WSDL11Validator.java which I can check in shortly which may help
> (assuming its the same cause).
>
> Cheers,
> Peter
>
> > 1 of 2 in
> > org.apache.cxf.tools.wsdl2java.processor.WSDLToJavaXMLFormatTest failed
> > with the same error.
> >
> > org.apache.cxf.wsdl11.WSDLServiceBuilderTest fails as it's having issues
> > getting the Schemas from the ServiceInfo (seems to be null when they
> > shouldn't be)
> >
> >
> > Strangest one:
> > org.apache.cxf.workqueue.AutomaticWorkQueueTest.testThreadPoolShrink
> > It's shrinking down below the minimum threashold. Not sure why.
> >
> >
> > BUNCH of type tests fail with maxLength/minLength restriction violations.
> > Those might be JAXB issues. Also in typetest is an
> > IllegalArgumentException creating a XMLGregorianCalendarImpl thing inside
> > xerces.
> >
> >
> > SchemaValidation test is failing
> >
> > jaxws.ClientServerTest is failing with a strange exception down in
> > woodstox: java.lang.IllegalStateException: Can't overwrite cause
> > at java.lang.Throwable.initCause(Throwable.java:320)
> > at com.ctc.wstx.compat.Jdk14Impl.setInitCause(Jdk14Impl.java:70)
> > at com.ctc.wstx.exc.WstxException.<init>(WstxException.java:46)
> > at
> > com.ctc.wstx.exc.WstxIOException.<init>(WstxIOException.java:16) at
> > com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313) at
> > org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMess
> > age(SoapOutInterceptor.java:94)
> >
> >
> >
> > Basically, there's a bunch of work to do to get the tests passing with
> > Java 6.
> >
> >
> > Dan
> > [...]
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
Re: Java 6 failures...
Posted by Peter Jones <pe...@iona.com>.
Hi Dan,
On Tue, Jan 23, 2007 at 04:55:56PM -0500, Daniel Kulp wrote:
> On Monday 22 January 2007 17:39, Dan Diephouse wrote:
> > This probably isn't the problem you're encountering, but another potential
> > problem source is that JAXB is bundled in J6 Which means depending on the
> > version thats in there, there could be bugs which aren't fixed, which might
> > cause unit tests to fail.
>
> I wish that was the problem. That would be easy to explain.
>
> It looks like the XML parser that is in J6 is a bit different than the one in
> J5. Probably a newer version of xerces or something. In anycase, it's
> causing much of the WSDL parsing and validating to fail.
>
> 7 out of 8 of the org.apache.cxf.tools.validator.WSDLValidationTest
> test fail. Strange errors like:
> Error : org.xml.sax.SAXParseException: src-resolve: Cannot resolve the
> name 'xml:lang' to a(n) 'attribute declaration' component.
I noticed the same sort of error when trying out the ibm jdk yesterday.
There, IIRC it seemed to be caused by the version of xerces prepending
file://path_to_current_dir to the baseURI relative path of the imported
schemas that was passed to the resolver. Anyway, I have a work-around for
the WSDL11Validator.java which I can check in shortly which may help
(assuming its the same cause).
Cheers,
Peter
> 1 of 2 in org.apache.cxf.tools.wsdl2java.processor.WSDLToJavaXMLFormatTest
> failed with the same error.
>
> org.apache.cxf.wsdl11.WSDLServiceBuilderTest fails as it's having issues
> getting the Schemas from the ServiceInfo (seems to be null when they
> shouldn't be)
>
>
> Strangest one:
> org.apache.cxf.workqueue.AutomaticWorkQueueTest.testThreadPoolShrink
> It's shrinking down below the minimum threashold. Not sure why.
>
>
> BUNCH of type tests fail with maxLength/minLength restriction violations.
> Those might be JAXB issues. Also in typetest is an IllegalArgumentException
> creating a XMLGregorianCalendarImpl thing inside xerces.
>
>
> SchemaValidation test is failing
>
> jaxws.ClientServerTest is failing with a strange exception down in woodstox:
> java.lang.IllegalStateException: Can't overwrite cause
> at java.lang.Throwable.initCause(Throwable.java:320)
> at com.ctc.wstx.compat.Jdk14Impl.setInitCause(Jdk14Impl.java:70)
> at com.ctc.wstx.exc.WstxException.<init>(WstxException.java:46)
> at com.ctc.wstx.exc.WstxIOException.<init>(WstxIOException.java:16)
> at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313)
> at
> org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMess
> age(SoapOutInterceptor.java:94)
>
>
>
> Basically, there's a bunch of work to do to get the tests passing with Java 6.
>
>
> Dan
> [...]
--
Peter Jones
IONA Technologies Inc.
E-Mail: mailto:peter.jones@iona.com
Tel: (w) 709-738-3725 x22 | Fax: 709-738-3745
84-86 Elizabeth Ave. St. John's, NL A1A 1W7 Canada
Re: Java 6 failures...
Posted by Cameron Taggart <ca...@gmail.com>.
Dan, that was the same error I got before endorsing
stax-api-1.0.1.jar. Fun, eh?
> jaxws.ClientServerTest is failing with a strange exception down in woodstox:
> java.lang.IllegalStateException: Can't overwrite cause
> at java.lang.Throwable.initCause(Throwable.java:320)
> at com.ctc.wstx.compat.Jdk14Impl.setInitCause(Jdk14Impl.java:70)
> at com.ctc.wstx.exc.WstxException.<init>(WstxException.java:46)
> at com.ctc.wstx.exc.WstxIOException.<init>(WstxIOException.java:16)
> at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313)
> at
> org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMess
> age(SoapOutInterceptor.java:94)
Re: Java 6 failures...
Posted by Daniel Kulp <da...@iona.com>.
On Monday 22 January 2007 17:39, Dan Diephouse wrote:
> This probably isn't the problem you're encountering, but another potential
> problem source is that JAXB is bundled in J6 Which means depending on the
> version thats in there, there could be bugs which aren't fixed, which might
> cause unit tests to fail.
I wish that was the problem. That would be easy to explain.
It looks like the XML parser that is in J6 is a bit different than the one in
J5. Probably a newer version of xerces or something. In anycase, it's
causing much of the WSDL parsing and validating to fail.
7 out of 8 of the org.apache.cxf.tools.validator.WSDLValidationTest
test fail. Strange errors like:
Error : org.xml.sax.SAXParseException: src-resolve: Cannot resolve the
name 'xml:lang' to a(n) 'attribute declaration' component.
1 of 2 in org.apache.cxf.tools.wsdl2java.processor.WSDLToJavaXMLFormatTest
failed with the same error.
org.apache.cxf.wsdl11.WSDLServiceBuilderTest fails as it's having issues
getting the Schemas from the ServiceInfo (seems to be null when they
shouldn't be)
Strangest one:
org.apache.cxf.workqueue.AutomaticWorkQueueTest.testThreadPoolShrink
It's shrinking down below the minimum threashold. Not sure why.
BUNCH of type tests fail with maxLength/minLength restriction violations.
Those might be JAXB issues. Also in typetest is an IllegalArgumentException
creating a XMLGregorianCalendarImpl thing inside xerces.
SchemaValidation test is failing
jaxws.ClientServerTest is failing with a strange exception down in woodstox:
java.lang.IllegalStateException: Can't overwrite cause
at java.lang.Throwable.initCause(Throwable.java:320)
at com.ctc.wstx.compat.Jdk14Impl.setInitCause(Jdk14Impl.java:70)
at com.ctc.wstx.exc.WstxException.<init>(WstxException.java:46)
at com.ctc.wstx.exc.WstxIOException.<init>(WstxIOException.java:16)
at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:313)
at
org.apache.cxf.binding.soap.interceptor.SoapOutInterceptor.handleMess
age(SoapOutInterceptor.java:94)
Basically, there's a bunch of work to do to get the tests passing with Java 6.
Dan
>
> - Dan
>
> On 1/22/07, Daniel Kulp <da...@iona.com> wrote:
> > Just to let everyone know...
> >
> > Don't upgrade to java 6 yet unless you want to start debugging tests.
> > There
> > are a LOT of test failures right now when you use java 6. I'm not sure
> > why
> > yet. It looks like the XML parsers/validators are very different which
> > is
> > causing some issues.
> >
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727 C: 508-380-7194
> > daniel.kulp@iona.com
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
Re: Java 6 failures...
Posted by Dan Diephouse <da...@envoisolutions.com>.
This probably isn't the problem you're encountering, but another potential
problem source is that JAXB is bundled in J6 Which means depending on the
version thats in there, there could be bugs which aren't fixed, which might
cause unit tests to fail.
- Dan
On 1/22/07, Daniel Kulp <da...@iona.com> wrote:
>
>
> Just to let everyone know...
>
> Don't upgrade to java 6 yet unless you want to start debugging tests.
> There
> are a LOT of test failures right now when you use java 6. I'm not sure
> why
> yet. It looks like the XML parsers/validators are very different which
> is
> causing some issues.
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194
> daniel.kulp@iona.com
>
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog