Philippe
What I observer is he following
When I compile on Windows Vista or OpenVMS under JDK 1.5.0
I can run this class or classes in the jar/mar on JDK 1.5.0
and when I later change to JDK 6.0 I can run it too
I call this upward compatible
BUT
when I build/compile with JDK 6.0 (i.e. I built Rampart on Windows Vista with
maven 2.2.1 on a JDK 6.0 platform (as a build for Rampart with JDK 1.5.0 fails
to build) (see my note in the axis2 users forum and answer provided by Andreas
Veit) on both OpenVMS and Windows Vista, and later use this jar/Rampart.mar on
a JDK 1.5.0 platform/environment, both OpenVMS and Windows Vista I get i.e. for
the Rampart Sample Client 01
E:\Users\C770817\SW-UMGEBUNG\rampart-1.6.0\samples\policy>ant client.01
"running :runAntNoClasspath"
Buildfile: build.xml
check.dependency:
client.01:
[copy] Copying 1 file to
E:\Users\C770817\SW-UMGEBUNG\rampart-1.6.0\samples\policy\build\client_repositories\sample01\modules
[copy] Copying 1 file to
E:\Users\C770817\SW-UMGEBUNG\rampart-1.6.0\samples\policy\build\client_repositories\sample01\modules
[copy] Copying 1 file to
E:\Users\C770817\SW-UMGEBUNG\rampart-1.6.0\samples\policy\build\temp_client
[copy] Copying 1 file to
E:\Users\C770817\SW-UMGEBUNG\rampart-1.6.0\samples\policy\build\temp_client
[java] java.lang.UnsupportedClassVersionError: Bad version number in
.class file
[java] at java.lang.ClassLoader.defineClass1(Native Method)
[java] at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
[java] at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
[java] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
[java] at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
[java] at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
[java] at java.security.AccessController.doPrivileged(Native Method)
[java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
[java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
[java] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
[java] Exception in thread "main"
[java] Java Result: 1
BUILD SUCCESSFUL
Total time: 1 second
E:\Users\C770817\SW-UMGEBUNG\rampart-1.6.0\samples\policy>set java_home
JAVA_HOME=C:\Program Files\Java\jdk1.5.0_18
E:\Users\C770817\SW-UMGEBUNG\rampart-1.6.0\samples\policy>
If I turn to JDK 6.0 and build AXIS2-1.6.0 AND RAMPART-1.6.0 WITH MAVEN ON TOP
OF JDK 6.0 I DO NOT HAVE ANY PROBLEMS to BUILD AND RUN
In this case I cannot debug later on OpenVMS as OpenVMS hot spot VM the only
one, does not support JPDA
It is a mess a mess a mess !
Josef
-----Ursprüngliche Nachricht-----
Von: Philippe Vouters [mailto:philippe.vout...@laposte.net]
Gesendet: Dienstag, 18. Oktober 2011 13:16
An: Schilling, Paul (GCC OVMS HAS BCS); Stadelmann Josef
Cc: java-user@axis.apache.org; Metzger, Norbert (HAS BCS OpenVMS)
Betreff: Re: Latest axis distribution on OAS (using jdk 1.4)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear Paul, Josef,
As far as it looks, Java bytecode produced with any Java V1.6.0_x
javac compiler on Linux/VMS seems to be backward compatible with Java
V1.5.x running on OpenVMS. This is untrue if Sun's Java 1.5.0_x is
instead used on a Linux computer.
If this can help Josef, I shall be glad.
Philippe
Le 18/10/2011 10:59, Schilling, Paul (GCC OVMS HAS BCS) a écrit :
> Hallo Sepp,
>
>
>
> In Java Notes conference habe ich schon einen Eintrag, aber ohne
> Antwort. Ich werde Dein mail hinzufügen.
>
>
>
> Viele Grüsse
>
>
>
> Paul Schilling
>
>
>
> EMEA HP OpenVMS Software Support
>
> HP Technology Services
>
> GCC OVMS
>
> Switzerland
>
>
>
> paul.schill...@hp.com / email
>
>
>
>
>
> Brian Johnson / Manager
>
> johns...@hp.com / Manager's email
>
>
>
> The content of this message and any attachements to it are
> confidential and may be legally privileged. If you have received
> this message in error you should delete it from your system
> immediately and advise the sender. To any recipient of this message
> within HP, unless otherwise stated you should consider this message
> and any attachements as "HP CONFIDENTIAL"
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> ITRC at http://www.ITresourcecenter.hp.com is the HP web portal
> for services and support offering you a wide range of knowledge
> tools, flexible and personalized maintenance solutions as well as
> training modules and forums on line. Take advantage of this new
> online experience !
>
>
>
>
>
> *From:*Stadelmann Josef
> [mailto:josef.stadelm...@axa-winterthur.ch] *Sent:* Dienstag, 18.
> Oktober 2011 10:57 *To:* java-user@axis.apache.org *Cc:* Schilling,
> Paul (GCC OVMS HAS BCS); Metzger, Norbert (HAS BCS OpenVMS);
> Philippe Vouters *Subject:* AW: Latest axis distribution on OAS
> (using jdk 1.4)
>
>
>
> It would be very nice, and I would be very thanks full to anyone,
> if one can clearly state which version of axis2 or related modules
> needs which version of JDK to build and run.
>
>
>
> Sooner than later we run into a nightmare here. Why?
>
>
>
> OpenVMS from HP does not have a JVM 6.0 supporting a JPDA.
>
> Hence we are just unable to debug code on OpenVMS which is not
> built with a JAVAC 1.5.0
>
> That is - we build the product first on Windows with JDK 1.5.0
> active, and if that works we move it to OpenVMS and start debugging
> remotely by attaching a debugger to the JVM and the debugger
> application shows all statement lines in sync, local with remote.
>
>
>
> That is why we would be very thanks full to know which versions of
> axis2 AND related modules like Rampart uses which version of a Java
> compiler to build and run.
>
>
>
> This is also to see in relation that I tried yesterday to build
> /Rampart/tags/1.6.0. using JDK 1.5.0 and it fails on Windows
> Vista.
>
> But builds perfect just switching to JDK 1.6.0,
>
> So no problem for Windows Vista e all, and debugging on Vista
>
> But a BIG problem for OpenVMS running Tomcat on top of JDK 1.5.0
> for debugging purpose.
>
>
>
> Wonder about any attitudes, hopefully also from HP
>
>
>
> Josef
>
>
>
> *Von:*Abhijeet C Kale [mailto:ak...@etouch.net] *Gesendet:* Montag,
> 17. Oktober 2011 07:26 *An:* java-user@axis.apache.org *Betreff:*
> Re: Latest axis distribution on OAS (using jdk 1.4)
>
>
>
> Thank you for the quick response Deepal. Do you know which version
> of axis is supported on jdk 1.4? your help appreciated.
>
> Regards, Abhijeet C Kale
>
> Website : *http://www.etouch.net* | Twitter:
> *http://twitter.com/samepagewiki*
>
>
> On 10/17/2011 9:45 AM, Deepal Jayasinghe wrote:
>
> Hi there, If you are referring to Axis2, then that does not work on
> JDK 1.4, you need to use JDK 1.5 or above,
>
> Deepal On 10/16/2011 11:13 PM, Abhijeet C Kale wrote:
>
> Hi,
>
> I was wondering if anyone has tried using the latest axis binary
> distribution and deployed it on a OAS (oracle application server,
> jdk 1.4.1)?
>
> -- Regards, Abhijeet C Kale
>
> Website : *http://www.etouch.net* | Twitter:
> *http://twitter.com/samepagewiki*
>
>
>
> -- Blog - http://blogs.deepal.org/
>
- --
Philippe Vouters (Fontainebleau/France)
URL: http://vouters.dyndns.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6dX9MACgkQsUYBDUbOpdrNXgCfYokZSy/+jl4JxE365o7CInpI
g7gAn2ZG0vLTS2kr4XRic/cE9ONAwBFk
=7Vko
-----END PGP SIGNATURE-----
