You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Stadelmann Josef <jo...@axa-winterthur.ch> on 2011/10/17 17:03:06 UTC
[Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
I have a demand to build Rampart using JDK 1.5.0_18
/asf/axis/axis2/java/core/tags/v1.6.0 using JDK1.5.0_18
success
/asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.5.0_18 failed
/asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.6.0_22
success
This on Windows Vits SP2
One could now arg that it isnot necessary to build Rampart under JAVA
1.5.0_18
But our JVM on OpenVMS to which we move the built Rampart tereafter does
not have
A JPDA Debugger Port for its JDK 1.6.0_22 JVM, hence we are unable to
debugg on
OpenVMS as we can't have sources and jars built with different JAVA
Compilers
And expect the debugger to work correctly under NetBeans
In this case the only working way is tio use JDK 1.5.0_18 and maven
2.2.1 to build
Rampart. However that fails while building with JDK 1.6.0_22 builds
successfully.
Question:
Is it possible to build Rampart-1.6.0 like Axis2-1.6.0 using a JAVAC
1.5.0 compiler?
In this case the following failer occures when building Rampart-1.6.0
taged version.
The build log is attached here.
<<Rampart_build_with_JDK_1.5.0_18.log>>
What are your recommenadtions
Josef
using
AW: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Andreas, no I did not add intentionally any such thing like Xerxes to endorsed libraries in and JDK version!
-----Ursprüngliche Nachricht-----
Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Gesendet: Montag, 17. Oktober 2011 17:49
An: java-user@axis.apache.org
Betreff: Re: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Josef,
Rampart normally builds fine with Java 1.5. There is however a known
issue that occurs when the JRE provides a Xerces version that uses the
original package name (org.apache.xerces). I've seen this on IBM JDKs,
while with Sun/Oracle JDKs, they normally use a Xerces version with a
modified package name (com.sun.*). Is it possible that you have added
Xerces to the endorsed libraries of the JRE?
Andreas
On Mon, Oct 17, 2011 at 17:03, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> I have a demand to build Rampart using JDK 1.5.0_18
>
> /asf/axis/axis2/java/core/tags/v1.6.0 using JDK1.5.0_18 success
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.5.0_18 failed
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.6.0_22 success
>
> This on Windows Vits SP2
>
> One could now arg that it isnot necessary to build Rampart under JAVA
> 1.5.0_18
>
> But our JVM on OpenVMS to which we move the built Rampart tereafter does not
> have
>
> A JPDA Debugger Port for its JDK 1.6.0_22 JVM, hence we are unable to debugg
> on
>
> OpenVMS as we can't have sources and jars built with different JAVA
> Compilers
>
> And expect the debugger to work correctly under NetBeans
>
> In this case the only working way is tio use JDK 1.5.0_18 and maven 2.2.1 to
> build
>
> Rampart. However that fails while building with JDK 1.6.0_22 builds
> successfully.
>
> Question:
>
> Is it possible to build Rampart-1.6.0 like Axis2-1.6.0 using a JAVAC 1.5.0
> compiler?
>
> In this case the following failer occures when building Rampart-1.6.0 taged
> version.
>
> The build log is attached here.
>
> <<Rampart_build_with_JDK_1.5.0_18.log>>
>
> What are your recommenadtions
>
> Josef
>
> using
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
AW: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Hallo Andreas,
where and which directory do I have to investigate on Windows Vista to say
Yes, the endorsed libraries have Xerxes or no there is no such thing endorsed.
I was just seeking under C:\Program Files\JAVA\.... for any *.jar and then checked
and could not find any Xerces.jar or a jar with such a name being part of it.
So which directory do you refer to when you say endorsed lib in this situation?
Sorry, but very thank full for any help.
Again - it fails when I build it on Vista using JDK 1.5.0_18 and succeeds when building it using JDK 1.6.0_22
Is it possible that Rampart depends in JAVA JDK 6.0 in a way?
Josef
-----Ursprüngliche Nachricht-----
Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Gesendet: Montag, 17. Oktober 2011 17:49
An: java-user@axis.apache.org
Betreff: Re: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Josef,
Rampart normally builds fine with Java 1.5. There is however a known
issue that occurs when the JRE provides a Xerces version that uses the
original package name (org.apache.xerces). I've seen this on IBM JDKs,
while with Sun/Oracle JDKs, they normally use a Xerces version with a
modified package name (com.sun.*). Is it possible that you have added
Xerces to the endorsed libraries of the JRE?
Andreas
On Mon, Oct 17, 2011 at 17:03, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> I have a demand to build Rampart using JDK 1.5.0_18
>
> /asf/axis/axis2/java/core/tags/v1.6.0 using JDK1.5.0_18 success
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.5.0_18 failed
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.6.0_22 success
>
> This on Windows Vits SP2
>
> One could now arg that it isnot necessary to build Rampart under JAVA
> 1.5.0_18
>
> But our JVM on OpenVMS to which we move the built Rampart tereafter does not
> have
>
> A JPDA Debugger Port for its JDK 1.6.0_22 JVM, hence we are unable to debugg
> on
>
> OpenVMS as we can't have sources and jars built with different JAVA
> Compilers
>
> And expect the debugger to work correctly under NetBeans
>
> In this case the only working way is tio use JDK 1.5.0_18 and maven 2.2.1 to
> build
>
> Rampart. However that fails while building with JDK 1.6.0_22 builds
> successfully.
>
> Question:
>
> Is it possible to build Rampart-1.6.0 like Axis2-1.6.0 using a JAVAC 1.5.0
> compiler?
>
> In this case the following failer occures when building Rampart-1.6.0 taged
> version.
>
> The build log is attached here.
>
> <<Rampart_build_with_JDK_1.5.0_18.log>>
>
> What are your recommenadtions
>
> Josef
>
> using
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
AW: [Rampart-1.5.2] Build fails with JDK 1.5.0 but succeeds with JDK 1.6.0
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
And that is one of the test which fail if I only build rampart - integration but with JDK 1.5.0_18 on a windows Vista
Is there as Andreas said an issue somewhere with a xml parser?
I would be very happy if that would run , if it comes to move this code to target OpenVMS
we like to be able to debug it, to attach a debugger to OpenVMS JVM 1.5.0 as JVM 1.6.0
does not have JPDA / JDWP implemented. Hence - why does it not build properly with JDK 1.5.0
and the same is true for Rampart 1.5.1, as well. Builds with JDK 1.6.0_22 and fails with JDK 1.5.0_18 on Vista
Josef
NetBeans: Executing 'E:\Users\C770817\SW-UMGEBUNG\apache-maven-2.2.1\bin\mvn.bat -Dnetbeans.execution=true -Dmaven.repo.local=E:\Users\C770817\.m2\repository --fail-fast install'
NetBeans: JAVA_HOME=C:\Program Files\Java\jdk1.5.0_18
Scanning for projects...
------------------------------------------------------------------------
Building Rampart - Integration
task-segment: [install]
------------------------------------------------------------------------
. . .
Running org.apache.rahas.RahasSAML2TokenTest
Server started on port 5555.....2011-10-20 17:31:19,832 ERROR org.opensaml.xml.XMLConfigurator - Configuration file does not validate against schema
org.xml.sax.SAXParseException: UndeclaredPrefix: Cannot resolve 'xt:DEFAULT' as a QName: the prefix 'xt' is not declared.
at com.sun.org.apache.xerces.internal.jaxp.validation.Util.toSAXParseException(Util.java:109)
at com.sun.org.apache.xerces.internal.jaxp.validation.ErrorHandlerAdaptor.error(ErrorHandlerAdaptor.java:104)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:429)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3185)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.processOneAttribute(XMLSchemaValidator.java:2799)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.processAttributes(XMLSchemaValidator.java:2735)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2094)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:705)
at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(ValidatorHandlerImpl.java:335)
at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073)
at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359)
at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390)
at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.process(ValidatorImpl.java:220)
at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:141)
at javax.xml.validation.Validator.validate(Validator.java:82)
at org.opensaml.xml.XMLConfigurator.validateConfiguration(XMLConfigurator.java:373)
at org.opensaml.xml.XMLConfigurator.load(XMLConfigurator.java:162)
at org.opensaml.xml.XMLConfigurator.load(XMLConfigurator.java:142)
at org.opensaml.DefaultBootstrap.initializeXMLTooling(DefaultBootstrap.java:143)
at org.opensaml.DefaultBootstrap.bootstrap(DefaultBootstrap.java:83)
at org.apache.rahas.impl.SAML2TokenIssuer.<clinit>(SAML2TokenIssuer.java:108)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at org.apache.rahas.TokenRequestDispatcherConfig.createIssuer(TokenRequestDispatcherConfig.java:391)
at org.apache.rahas.TokenRequestDispatcherConfig.getIssuer(TokenRequestDispatcherConfig.java:343)
at org.apache.rahas.TokenRequestDispatcher.handle(TokenRequestDispatcher.java:67)
at org.apache.rahas.STSMessageReceiver.invokeBusinessLogic(STSMessageReceiver.java:57)
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:266)
at org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)
at org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)
at org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
2011-10-20 17:31:19,832 ERROR org.apache.rahas.impl.SAML2TokenIssuer - SAML2TokenIssuerBootstrapError
org.opensaml.xml.ConfigurationException: Configuration file does not validate against schema
at org.opensaml.xml.XMLConfigurator.validateConfiguration(XMLConfigurator.java:382)
at org.opensaml.xml.XMLConfigurator.load(XMLConfigurator.java:162)
at org.opensaml.xml.XMLConfigurator.load(XMLConfigurator.java:142)
at org.opensaml.DefaultBootstrap.initializeXMLTooling(DefaultBootstrap.java:143)
at org.opensaml.DefaultBootstrap.bootstrap(DefaultBootstrap.java:83)
at org.apache.rahas.impl.SAML2TokenIssuer.<clinit>(SAML2TokenIssuer.java:108)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at org.apache.rahas.TokenRequestDispatcherConfig.createIssuer(TokenRequestDispatcherConfig.java:391)
at org.apache.rahas.TokenRequestDispatcherConfig.getIssuer(TokenRequestDispatcherConfig.java:343)
at org.apache.rahas.TokenRequestDispatcher.handle(TokenRequestDispatcher.java:67)
at org.apache.rahas.STSMessageReceiver.invokeBusinessLogic(STSMessageReceiver.java:57)
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:173)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:266)
at org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)
at org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)
at org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)org.apache.axis2.AxisFault: unknown
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:446)
at java.lang.Thread.run(Thread.java:595)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
Caused by: org.xml.sax.SAXParseException: UndeclaredPrefix: Cannot resolve 'xt:DEFAULT' as a QName: the prefix 'xt' is not declared.
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
at com.sun.org.apache.xerces.internal.jaxp.validation.Util.toSAXParseException(Util.java:109)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at com.sun.org.apache.xerces.internal.jaxp.validation.ErrorHandlerAdaptor.error(ErrorHandlerAdaptor.java:104)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:540)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:521)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:429)
at org.apache.rahas.TestClient.testRequest(TestClient.java:112)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3185)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.processOneAttribute(XMLSchemaValidator.java:2799)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.processAttributes(XMLSchemaValidator.java:2735)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2094)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:705)
at junit.framework.TestCase.runTest(TestCase.java:164)
at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(ValidatorHandlerImpl.java:335)
at junit.framework.TestCase.runBare(TestCase.java:130)
at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145)
at junit.framework.TestResult.run(TestResult.java:109)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390)
at junit.framework.TestCase.run(TestCase.java:120)
at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.process(ValidatorImpl.java:220)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:141)
at junit.framework.TestSuite.run(TestSuite.java:225)
at javax.xml.validation.Validator.validate(Validator.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at org.opensaml.xml.XMLConfigurator.validateConfiguration(XMLConfigurator.java:373)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
... 26 more
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[SimpleHTTPServer] Stop called
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Server stopped .....@SLTests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.382 sec <<< FAILURE!
Running org.apache.rahas.RahasSAMLTokenCertForHoKV1205Test
And the other test is
Running org.apache.rahas.RahasSAML2TokenCertForHoKTest
org.apache.axis2.AxisFault: unknown
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:446)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:540)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:521)
at org.apache.rahas.TestClient.testRequest(TestClient.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Server started on port 5555.....[SimpleHTTPServer] Stop called
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Server stopped .....@SLTests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.132 sec <<< FAILURE!
Results :
Failed tests:
testRequest(org.apache.rahas.RahasSAML2TokenTest)
testRequest(org.apache.rahas.RahasSAML2TokenCertForHoKTest)
Tests run: 42, Failures: 2, Errors: 0, Skipped: 0
-----Ursprüngliche Nachricht-----
Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
Gesendet: Donnerstag, 20. Oktober 2011 14:32
An: java-user@axis.apache.org
Betreff: AW: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Andreas
When I build the Rampart project using JDK 1.5.0_18 on Windows Vista
Starting from the root pom.xml fails with the Rampart - Integration Module in the lengthy test . . .
When I just build the Rampart - Integration Module all works fine including the lengthy tests, all are running all well.
When I use JDK 1.6.0_22
Starting from the root pom.xml works perfect including the lengthy test.
This on Windows Vista
But
I see the same symptoms attempting to build axis2 (not Rampart) on OpenVMS
When the reactor triggers the module build module/codegen fails in the surefire test
When I do the same using mvn install --projects module/codegen all works fine even on OpenVMS (not using GNV/Bash) but with our own ant-1.7.1-sst in the local cache.
Yesterday, I have built axis2-1.6.0
With maven-2.2.1
On top of Java 1.6.0
On top of OpenVMS
Mvn -Dmaven.test.skip=true install
Any clue
Regards
Sepp
-----Ursprüngliche Nachricht-----
Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Gesendet: Montag, 17. Oktober 2011 17:49
An: java-user@axis.apache.org
Betreff: Re: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Josef,
Rampart normally builds fine with Java 1.5. There is however a known
issue that occurs when the JRE provides a Xerces version that uses the
original package name (org.apache.xerces). I've seen this on IBM JDKs,
while with Sun/Oracle JDKs, they normally use a Xerces version with a
modified package name (com.sun.*). Is it possible that you have added
Xerces to the endorsed libraries of the JRE?
Andreas
On Mon, Oct 17, 2011 at 17:03, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> I have a demand to build Rampart using JDK 1.5.0_18
>
> /asf/axis/axis2/java/core/tags/v1.6.0 using JDK1.5.0_18 success
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.5.0_18 failed
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.6.0_22 success
>
> This on Windows Vits SP2
>
> One could now arg that it isnot necessary to build Rampart under JAVA
> 1.5.0_18
>
> But our JVM on OpenVMS to which we move the built Rampart tereafter does not
> have
>
> A JPDA Debugger Port for its JDK 1.6.0_22 JVM, hence we are unable to debugg
> on
>
> OpenVMS as we can't have sources and jars built with different JAVA
> Compilers
>
> And expect the debugger to work correctly under NetBeans
>
> In this case the only working way is tio use JDK 1.5.0_18 and maven 2.2.1 to
> build
>
> Rampart. However that fails while building with JDK 1.6.0_22 builds
> successfully.
>
> Question:
>
> Is it possible to build Rampart-1.6.0 like Axis2-1.6.0 using a JAVAC 1.5.0
> compiler?
>
> In this case the following failer occures when building Rampart-1.6.0 taged
> version.
>
> The build log is attached here.
>
> <<Rampart_build_with_JDK_1.5.0_18.log>>
>
> What are your recommenadtions
>
> Josef
>
> using
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
AW: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Andreas
When I build the Rampart project using JDK 1.5.0_18 on Windows Vista
Starting from the root pom.xml fails with the Rampart - Integration Module in the lengthy test . . .
When I just build the Rampart - Integration Module all works fine including the lengthy tests, all are running all well.
When I use JDK 1.6.0_22
Starting from the root pom.xml works perfect including the lengthy test.
This on Windows Vista
But
I see the same symptoms attempting to build axis2 (not Rampart) on OpenVMS
When the reactor triggers the module build module/codegen fails in the surefire test
When I do the same using mvn install --projects module/codegen all works fine even on OpenVMS (not using GNV/Bash) but with our own ant-1.7.1-sst in the local cache.
Yesterday, I have built axis2-1.6.0
With maven-2.2.1
On top of Java 1.6.0
On top of OpenVMS
Mvn -Dmaven.test.skip=true install
Any clue
Regards
Sepp
-----Ursprüngliche Nachricht-----
Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Gesendet: Montag, 17. Oktober 2011 17:49
An: java-user@axis.apache.org
Betreff: Re: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Josef,
Rampart normally builds fine with Java 1.5. There is however a known
issue that occurs when the JRE provides a Xerces version that uses the
original package name (org.apache.xerces). I've seen this on IBM JDKs,
while with Sun/Oracle JDKs, they normally use a Xerces version with a
modified package name (com.sun.*). Is it possible that you have added
Xerces to the endorsed libraries of the JRE?
Andreas
On Mon, Oct 17, 2011 at 17:03, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> I have a demand to build Rampart using JDK 1.5.0_18
>
> /asf/axis/axis2/java/core/tags/v1.6.0 using JDK1.5.0_18 success
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.5.0_18 failed
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.6.0_22 success
>
> This on Windows Vits SP2
>
> One could now arg that it isnot necessary to build Rampart under JAVA
> 1.5.0_18
>
> But our JVM on OpenVMS to which we move the built Rampart tereafter does not
> have
>
> A JPDA Debugger Port for its JDK 1.6.0_22 JVM, hence we are unable to debugg
> on
>
> OpenVMS as we can't have sources and jars built with different JAVA
> Compilers
>
> And expect the debugger to work correctly under NetBeans
>
> In this case the only working way is tio use JDK 1.5.0_18 and maven 2.2.1 to
> build
>
> Rampart. However that fails while building with JDK 1.6.0_22 builds
> successfully.
>
> Question:
>
> Is it possible to build Rampart-1.6.0 like Axis2-1.6.0 using a JAVAC 1.5.0
> compiler?
>
> In this case the following failer occures when building Rampart-1.6.0 taged
> version.
>
> The build log is attached here.
>
> <<Rampart_build_with_JDK_1.5.0_18.log>>
>
> What are your recommenadtions
>
> Josef
>
> using
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
AW: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Hi Andreas,
I copied all the files mentioned below from the maven .m2/repository/org/apache/xerxes and xalan to
%JAVA_HOME%/jre/lib/endorsed directory. The maven build with JDK 1.5.0_18 on Vista runs perfect now.
Josef
Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
Gesendet: Donnerstag, 20. Oktober 2011 18:02
An: java-user@axis.apache.org
Betreff: AW: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Hi Andreas,
Guess I found what you addresses below, but thanks for the tip !
It is in the README.txt of the Apache Rampart module under release documents.
. . .
Test cases written for SAML 2.0 support requires endorsing the JDK's default JAXP
implementation with Xerces(http://xerces.apache.org/mirrors.cgi#binary) and
Xalan(http://xml.apache.org/xalan-j/downloads.html#latest-release). So before building Rampart from the
source distribution, you need to copy resolver-x.x.x.jar, serializer-x.x.x.jar, xercesImpl-x.x.x.jar
and xml-apis-x.x.x.jar from the Xerces binary distribution and xalan-x.x.x.jar from the xalan binary
distribution to the endorsed directory. If you are using Sun JDK, endorsed directory is located at
$JAVA_HOME/jre/lib/endorsed.
. . .
That is I have to create an endorsed directory and copy files to that endorsed directory under the JDK 1.5.0_18 in question !
So the answer to the question :
Is it possible that you have added Xerces to the endorsed libraries of the JRE?
THE ANSWER IS A CLEAR NO ---- BUT I HAVE TO DO SO NOW AND AS WELL FOR XALAN ! taking the stuff out of local cache as it is there and re-try
If that will work, what surprises me bit is that mvn and ant e all cannot manage that.
Josef
-----Ursprüngliche Nachricht-----
Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Gesendet: Montag, 17. Oktober 2011 17:49
An: java-user@axis.apache.org
Betreff: Re: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Josef,
Rampart normally builds fine with Java 1.5. There is however a known
issue that occurs when the JRE provides a Xerces version that uses the
original package name (org.apache.xerces). I've seen this on IBM JDKs,
while with Sun/Oracle JDKs, they normally use a Xerces version with a
modified package name (com.sun.*). Is it possible that you have added
Xerces to the endorsed libraries of the JRE?
Andreas
On Mon, Oct 17, 2011 at 17:03, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> I have a demand to build Rampart using JDK 1.5.0_18
>
> /asf/axis/axis2/java/core/tags/v1.6.0 using JDK1.5.0_18 success
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.5.0_18 failed
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.6.0_22 success
>
> This on Windows Vits SP2
>
> One could now arg that it isnot necessary to build Rampart under JAVA
> 1.5.0_18
>
> But our JVM on OpenVMS to which we move the built Rampart tereafter does not
> have
>
> A JPDA Debugger Port for its JDK 1.6.0_22 JVM, hence we are unable to debugg
> on
>
> OpenVMS as we can't have sources and jars built with different JAVA
> Compilers
>
> And expect the debugger to work correctly under NetBeans
>
> In this case the only working way is tio use JDK 1.5.0_18 and maven 2.2.1 to
> build
>
> Rampart. However that fails while building with JDK 1.6.0_22 builds
> successfully.
>
> Question:
>
> Is it possible to build Rampart-1.6.0 like Axis2-1.6.0 using a JAVAC 1.5.0
> compiler?
>
> In this case the following failer occures when building Rampart-1.6.0 taged
> version.
>
> The build log is attached here.
>
> <<Rampart_build_with_JDK_1.5.0_18.log>>
>
> What are your recommenadtions
>
> Josef
>
> using
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
AW: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Hi Andreas,
Guess I found what you addresses below, but thanks for the tip !
It is in the README.txt of the Apache Rampart module under release documents.
. . .
Test cases written for SAML 2.0 support requires endorsing the JDK's default JAXP
implementation with Xerces(http://xerces.apache.org/mirrors.cgi#binary) and
Xalan(http://xml.apache.org/xalan-j/downloads.html#latest-release). So before building Rampart from the
source distribution, you need to copy resolver-x.x.x.jar, serializer-x.x.x.jar, xercesImpl-x.x.x.jar
and xml-apis-x.x.x.jar from the Xerces binary distribution and xalan-x.x.x.jar from the xalan binary
distribution to the endorsed directory. If you are using Sun JDK, endorsed directory is located at
$JAVA_HOME/jre/lib/endorsed.
. . .
That is I have to create an endorsed directory and copy files to that endorsed directory under the JDK 1.5.0_18 in question !
So the answer to the question :
Is it possible that you have added Xerces to the endorsed libraries of the JRE?
THE ANSWER IS A CLEAR NO ---- BUT I HAVE TO DO SO NOW AND AS WELL FOR XALAN ! taking the stuff out of local cache as it is there and re-try
If that will work, what surprises me bit is that mvn and ant e all cannot manage that.
Josef
-----Ursprüngliche Nachricht-----
Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Gesendet: Montag, 17. Oktober 2011 17:49
An: java-user@axis.apache.org
Betreff: Re: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Josef,
Rampart normally builds fine with Java 1.5. There is however a known
issue that occurs when the JRE provides a Xerces version that uses the
original package name (org.apache.xerces). I've seen this on IBM JDKs,
while with Sun/Oracle JDKs, they normally use a Xerces version with a
modified package name (com.sun.*). Is it possible that you have added
Xerces to the endorsed libraries of the JRE?
Andreas
On Mon, Oct 17, 2011 at 17:03, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> I have a demand to build Rampart using JDK 1.5.0_18
>
> /asf/axis/axis2/java/core/tags/v1.6.0 using JDK1.5.0_18 success
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.5.0_18 failed
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.6.0_22 success
>
> This on Windows Vits SP2
>
> One could now arg that it isnot necessary to build Rampart under JAVA
> 1.5.0_18
>
> But our JVM on OpenVMS to which we move the built Rampart tereafter does not
> have
>
> A JPDA Debugger Port for its JDK 1.6.0_22 JVM, hence we are unable to debugg
> on
>
> OpenVMS as we can't have sources and jars built with different JAVA
> Compilers
>
> And expect the debugger to work correctly under NetBeans
>
> In this case the only working way is tio use JDK 1.5.0_18 and maven 2.2.1 to
> build
>
> Rampart. However that fails while building with JDK 1.6.0_22 builds
> successfully.
>
> Question:
>
> Is it possible to build Rampart-1.6.0 like Axis2-1.6.0 using a JAVAC 1.5.0
> compiler?
>
> In this case the following failer occures when building Rampart-1.6.0 taged
> version.
>
> The build log is attached here.
>
> <<Rampart_build_with_JDK_1.5.0_18.log>>
>
> What are your recommenadtions
>
> Josef
>
> using
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: [Rampart-1.6.0] Build fails with JDK 15.0 but succeeds with JDK 1.6.0
Posted by Andreas Veithen <an...@gmail.com>.
Josef,
Rampart normally builds fine with Java 1.5. There is however a known
issue that occurs when the JRE provides a Xerces version that uses the
original package name (org.apache.xerces). I've seen this on IBM JDKs,
while with Sun/Oracle JDKs, they normally use a Xerces version with a
modified package name (com.sun.*). Is it possible that you have added
Xerces to the endorsed libraries of the JRE?
Andreas
On Mon, Oct 17, 2011 at 17:03, Stadelmann Josef
<jo...@axa-winterthur.ch> wrote:
> I have a demand to build Rampart using JDK 1.5.0_18
>
> /asf/axis/axis2/java/core/tags/v1.6.0 using JDK1.5.0_18 success
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.5.0_18 failed
>
> /asf/axis/axis2/java/rampart/tags/v1.6.0 using JDK1.6.0_22 success
>
> This on Windows Vits SP2
>
> One could now arg that it isnot necessary to build Rampart under JAVA
> 1.5.0_18
>
> But our JVM on OpenVMS to which we move the built Rampart tereafter does not
> have
>
> A JPDA Debugger Port for its JDK 1.6.0_22 JVM, hence we are unable to debugg
> on
>
> OpenVMS as we can't have sources and jars built with different JAVA
> Compilers
>
> And expect the debugger to work correctly under NetBeans
>
> In this case the only working way is tio use JDK 1.5.0_18 and maven 2.2.1 to
> build
>
> Rampart. However that fails while building with JDK 1.6.0_22 builds
> successfully.
>
> Question:
>
> Is it possible to build Rampart-1.6.0 like Axis2-1.6.0 using a JAVAC 1.5.0
> compiler?
>
> In this case the following failer occures when building Rampart-1.6.0 taged
> version.
>
> The build log is attached here.
>
> <<Rampart_build_with_JDK_1.5.0_18.log>>
>
> What are your recommenadtions
>
> Josef
>
> using
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org