I wasn't sure so I just changed both.
Also (I'm still looking for it) I assume that those files are copied
from some stock template somewhere. If so you could just alter the
template for those files and then you won't have to do this every time
you rebuild your application.
--
Galen Rhodes
[EMAIL PROTECTED]
On Jan 11, 2008, at 2:47 PM, Guido Neitzer wrote:
On 11.01.2008, at 12:36, Galen Rhodes wrote:
To get your WebObjects application to run in 64-bit mode then you
need to alter the classpath files. Once the application is built,
edit the two classpath files in the application folder. If your
application is named "Foo" then the two files you need to edit are
"Foo.woa/Contents/MacOS/MacOSClassPath.txt" and "Foo.woa/Contents/
MacOS/MacOSXServerClassPath.txt".
At least on Tiger the file MacOSXServerClassPath.txt was never read.
It always used the MacOSClassPath.txt. Wasn't the old file only for
Mac OS X Server 1.0 (aka Rhapsody)? So to make classpath changes, on
Tiger you only had to edit one file for client and server.
Has that changed recently?
cug
--
Real-World WebObjects class at the Big Nerd Ranch
March 2008, Frankfurt, Germany
http://www.bignerdranch.com/classes/webobjects.shtml
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
