Re: WebObjects-admin Digest, Vol 43, Issue 1

hello,

did you try the compiler switches:

-target 1.5
-source 1.5

when you compile with 1.6 and want's to depoly on 1.5?

juergen



Am 02.09.2009 um 21:00 schrieb [email protected]:

> Send WebObjects-admin mailing list submissions to
> 	[email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.omnigroup.com/mailman/listinfo/webobjects-admin
> or, via email, send a message with subject or body 'help' to
> 	[email protected]
>
> You can reach the person managing the list at
> 	[email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebObjects-admin digest..."
>
>
> Today's Topics:
>
>    1. Run your WO apps on Leopard Server (Intel) with Java 6
>       (Brendan Duddridge)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 1 Sep 2009 12:31:20 -0600
> From: Brendan Duddridge <[email protected]>
> Subject: Run your WO apps on Leopard Server (Intel) with Java 6
> To: WebObjects Admin <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
>
> Hey WO Folks,
>
> So I had a class version mismatch exception when building from Snow
> Leopard (JDK 1.6) and deploying on Leopard Server (JDK 1.5). So I
> wanted to switch my servers to use JDK 1.6 by default. Nothing we
> tried would make that happen. We tried dragging the Java 6 entry in
> Java Preferences up to the top of the list and rebooting the Xserve,
> but that still didn't work. We also tried changing the CurrentJDK to
> point to the 1.6.0 directory. But that also didn't work. Tried
> changing the Current symlink to point to 1.6.0 instead of to A as is
> by default.
>
> Well, when I say it didn't work, I mean it didn't help to launch our
> WO apps with Java 1.6. They still launched with Java 1.5, even though
> typing 'java -version' into the command line returned 1.6, typing in
> 'sudo -u appserver java -version' returned 1.5.
>
> So the solution was to modify the build.xml file in Eclipse to have it
> generate a hard coded path to the JVM to point to 1.6.
>
> Here's what I added to the build.xml file's <woapplication> task:
>
> JVM="/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/
> bin/java"
>
> So it looks like this now:
>
> <woapplication name="${build.app.name}" JVM="/System/Library/
> Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/java" destDir="$
> {dest.dir}" customInfoPListContent="${customInfoPListContent}"
> principalClass="${principalClass}" webXML="${webXML}"
> webXML_CustomContent="${webXML_CustomContent}"
> servletAdaptor="com.webobjects.jspservlet.WOServletAdaptor">
>
> The end result is a MacOSClassPath.txt file with the following entry
> at the top:
>
> # JVM              == /System/Library/Frameworks/JavaVM.framework/
> Versions/1.6.0/Home/bin/java
>
> That works for us, so I thought I'd share it with you.
>
> Thanks go to Mike Schrag for the help with this! Is there anything
> that guy doesn't know? :-)
>
> Sincerely,
>
> ____________________________________________________________________
> Brendan Duddridge | CTO | 403-277-5591 x24 |  [email protected]
>
> ClickSpace Interactive Inc.
> Suite L100, 239 - 10th Ave. SE
> Calgary, AB  T2G 0V9
>
> http://www.clickspace.com
>
>
>
>
> ------------------------------
>
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>
>
> End of WebObjects-admin Digest, Vol 43, Issue 1
> ***********************************************