John,
Out of curiosity, where's the second one?
Dave
On Jan 31, 2008, at 6:30 AM, John Pollard wrote:
Dave,
Just a quick update to say that I now think it probably best not to
use wojavaclient.jar at all, at least in our case. For one thing,
Apple appear to provide two versions, one far larger than the other
with no explanation of their intended use. To avoid picking up
unwanted resources, like the large embedded D2JC jar, I think it is
best for us to not use them. It all seems a bit unfriendly how this
has been packaged with lack of guidance.
Regards,
John
On 28 Jan 2008, at 11:06, David Avendasora wrote:
I got this back from Daryl Lee from Apple. I'm working on a reply
to him with some more questions. I just haven't sent it yet. Watch
the list.
Dave
Begin forwarded message:
From: Daryl Lee <[EMAIL PROTECTED]>
Date: January 25, 2008 4:23:53 PM EST
To: David Avendasora <[EMAIL PROTECTED]>
Cc: WebObjects-Dev List <[email protected]>
Subject: Re: Auto Open Client Application isn't
David,
On Jan 25, 2008, at 11:38 AM, David Avendasora wrote:
On Jan 24, 2008, at 2:22 PM, Daryl Lee wrote:
I'd file a bug with WOLips. If I have spare cycles (which is
rare these days), I might be able to look into this for you.
I'm not sure what I'd say in the bug report ... There's so many
pieces and I don't _know_ which are needed and which aren't. I
don't want to spend a bunch of time figuring out what something
is used for and then filling a bug report/feature request, if it
isn't even needed anymore.
Well, at a minimum, I'd file a request for the client side launch
script and a default client classpath file to be embedded as part
of the build process (development and deployment).
Just to start with, Is there someplace that defines the client-
side classes?
I suppose I could do a filter on the contents of /System/Library/
Frameworks for any with WebServerResources/Java/*.jar and then
add all those to a text file, then add in any contents of my
project/WebServerResources/Java directory as well.
Any other places I should look? What's the deal with /Library/
WebServer/Documents/WebObjects/Java/wojavaclient.jar?
I believe the wojavaclient.jar has all the base client-side
frameworks that you'll need for deploying java client
applications (both D2JC and Nib). It's a signed jar and is
intended for WebStart deployments. The clients side classes are
also copied on (OS X) into the Apache doc root for people who are
deployment java client based applets.
Is that a combined jar of everything from the System/Library/
Frameworks/*.framework/WebServerResources/Java/*.jar or what?
I believe so.
What about the other scripts and such?
Which scripts are you referring to? The stuff in Application
support? Most of those scripts support the Xcode JAM build system.
What was/is their function in a WO Application?
I can find no documentation (old or new) about what they do. Do
they only serve a function for development builds, or are they
needed in deployment too?
Mostly to assemble the application/framework bundles for various
deployment styles (J2EE vs .woa and .framework vs self contained
jars). They also did the split deployment builds.
Try examining the build phases in the 'Development' and
'Deployment' targets in an old Xcode WO project and you'll see them.
These are the things I'm trying to figure out.
Thanks,
Dave
Dave
Now I can easily modify my javaclient.xml Ant build file
(http://wiki.objectstyle.org/confluence/display/WO/Java
+Client-Incremental+Build) to make the MyApp.woa/MacOS
directory and copy the two files in there, BUT the other
problem is that I'm on 5.3 and I'm assuming that the /
Library/Application Support/Apple/Developer Tools/WebObjects
Support/ directory and it's contents go away on 10.5/Xcode 3
and later. Or don't they?
We left the old (JAM) build system in place for 10.5/XCode
3.0 so feel free to move to Leopard/5.4.
There but deprecated, I'm guessing. No worries, I'll make my
build task point to there for the script file and wait for
something to change.
If you need certain bits to stick around in the developer tool
centric bits, file a bug.
For now I'll just include it in my project, but what about
other developers? Can we distribute the UnixLaunchClient.sh
file from the wiki? I'm guessing not since it was Apple
supplied.
Thanks,
Dave
ClasspathClient.txt contents:
# ApplicationClass ==
com.webobjects.eoapplication.client.EOClientApplicationSupport
# JDB == jdb
# JDBOptions ==
# JVM == java
# JVMOptions ==
/System/Library/Frameworks/JavaFoundation.framework/
WebServerResources/Java/JavaFoundation.jar
WOROOT/Library/Frameworks/JavaEOControl.framework/
WebServerResources/Java/JavaEOControl.jar
WOROOT/Library/Frameworks/JavaXML.framework/
WebServerResources/Java/JavaXML.jar
WOROOT/Library/Frameworks/JavaDirectToWeb.framework/
WebServerResources/Java/JavaDirectToWeb.jar
WOROOT/Library/Frameworks/JavaEOApplication.framework/
WebServerResources/Java/JavaEOApplication.jar
WOROOT/Library/Frameworks/JavaEODistribution.framework/
WebServerResources/Java/JavaEODistribution.jar
WOROOT/Library/Frameworks/JavaEOGeneration.framework/
WebServerResources/Java/JavaEOGeneration.jar
WOROOT/Library/Frameworks/JavaEOInterface.framework/
WebServerResources/Java/JavaEOInterface.jar
WOROOT/Library/Frameworks/JavaEOInterfaceSwing.framework/
WebServerResources/Java/JavaEOInterfaceSwing.jar
WOROOT/Library/Frameworks/JavaEORuleSystem.framework/
WebServerResources/Java/JavaEORuleSystem.jar
WOROOT/Library/Frameworks/JavaWOJSPServlet.framework/
WebServerResources/Java/JavaWOJSPServlet_client.jar
HOMEROOT/Library/Java
LOCALROOT/Library/Java
WOROOT/Library/Java
/Network/Library/Java
WOROOT/Library/Frameworks/JavaVM.framework/Classes/classes.jar
WOROOT/Library/Frameworks/JavaVM.framework/Classes/ui.jar
On Jan 23, 2008, at 8:05 PM, Daryl Lee wrote:
You might also want to double check that the
UnixLaunchClient.sh script is embedded in your .woa bundle
by WOLips. It's been a while so I can't remember if Xcode
used to rename that script.
You can find a copy at:
/Library/Application Support/Apple/Developer Tools/
WebObjects Support
On Jan 23, 2008, at 2:41 PM, Xavier Destombes wrote:
Hello Dave,
have a look at the "Unable to locate WOOpenURL on your
computer" thread.
Xavier
Hi all,
I have migrated my Xcode Java Client project (using
WebStart) to Eclipse/WOLips and the Auto Open In Browser
feature no longer works. I get the following message in
the Eclipse Run Log:
Unable to locate client launch script in your
application, using the Auto Open In Browser feature
instead of the Auto Open Client Application feature.
It does still launch the browser and give me a link to
the .jnlp file, but that is just so tedious (I know it's
whining/whinging but I _want_ it back). Is there a way to
make Eclipse just open the .jnlp file? It says something
about a client launch script, but try as I might, I just
can't find it in the original Xcode project either.
Any help?
Dave
_______________________________________________
Do not post admin requests to the list. They will be
ignored.
Webobjects-dev mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/
webobjects%40anazys.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-
[EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/dlee%
40apple.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
