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.veit...@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 <josef.stadelm...@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-unsubscr...@axis.apache.org > For additional commands, e-mail: java-user-h...@axis.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
