Art,
it looks like our emails crossed. Leopard has had a last-minute
reprieve.
I'm glad your journey was less painful than mine. 8^|
Yes, I was launching wotaskd as per the initial email in this thread.
I'm not using JavaMonitor on this development machine.
And for the next exciting episode in the journey-- virtual sites and
mod_rewrite WERE a red herring. Now I put them back, they are working
fine.
Now, as a Cold War friend of mine says: "Back to Factory! Increase
Production!"
Regards
Thomas
On 31/10/2007, at 10:13 AM, Art Isbell 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.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
