Re: The Official What-I-Did-To-Run-5.3-On-Leopard Post
Re: The Official What-I-Did-To-Run-5.3-On-Leopard Post
- Subject: Re: The Official What-I-Did-To-Run-5.3-On-Leopard Post
- From: Art Isbell <email@hidden>
- Date: Tue, 30 Oct 2007 13:13:32 -1000
On Oct 30, 2007, at 11:26 AM, Thomas wrote:
I guess I'll just give up on Leopard development for now, and use an
older 10.4 machine to do development. Direct connect is not an
option, because my apps use mod-rewrite and readable URLs for most
links.
For what it's worth, I've had no problem running my WO 5.3/Xcode/
Apache 1.3 apps under WO 5.4/Eclipse 3.2.2/Apache 2.2 in Web server
connect mode (i.e., not Direct Connect) after migrating to Eclipse and
working around one WO 5.4 API bug. Mine was a clean Leopard, XCode
tools, and WO 5.4 install including a migration of everything from a
Tiger partition. So I don't think that Leopard, WO 5.4, or Apache 2.2
is to blame for your problem.
I don't recall how you're launching wotaskd and JavaMonitor. I
suggest using the launchd config files posted a few days ago on this
mailing list. These ensure that wotaskd is running as appserver
rather than root or any other user which could cause problems.
Aloha,
Art
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden