WOLaunchURL is a command line tool that resides in /System/Library/
WebObjects/Executables/WOOpenURL.
[mbp:Library/WebObjects/Executables] th% ./WOOpenURL
2007-10-31 22:26:53.961 WOOpenURL[10403] OpenURL - Syntax : OpenURL
<url>
I would bet that it's called directly from within WOApplication via
Runtime.exec().
Creating a symlink to "open" will probably be the easiest fix.
sudo mkdir -p /System/Library/WebObjects/Executables
sudo ln -s /usr/bin/open /System/Library/WebObjects/Executables/
WOOpenURL
Just tested it in Tiger and it appears to work fine.
[mbp:Library/WebObjects/Executables] th% ls -la
total 96
drwxr-xr-x 4 root wheel 136 Oct 31 22:28 ./
drwxr-xr-x 7 root wheel 238 Jun 3 2006 ../
lrwxr-xr-x 1 root wheel 13 Oct 31 22:28 WOOpenURL@ -> /usr/bin/
open
-rwxr-xr-x 1 root wheel 42380 Sep 12 2006 WOOpenURL.bak*
Timo
Am 31.10.2007 um 21:55 schrieb Mike Schrag:
I'm not familiar with the wolips startup script template but I'll
take a look. The autolaunch stuff is part of the rapid turnaround
support. If a valid project is detected then the 'open' command
is called. WOLips tends to muddy the issue since by default most
projects create a PB.project, .xcode project and build.xml file.
This is likely confusing our the resource discovery.
Well, I'm not even sure this is part of the startup script -- So WO
calls open, which means presumably 5.3 WO calls WOLaunchURL,
right? I've never looked at this particular element to see where
this call actually lives. If it's in WO, then almost certainly
this is because I'm running 5.3 on Leopard and WOLaunchURL is gone
away.
_______________________________________________
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]
