but I couldn't see how that could get on the Jaikoz classpath
I agree with Tomas Hurka: the problem could be in one of the
extensions dirs.
You can make a trial app-bundle for this particular customer that
disable the extensions dirs, then have them run it and see if it works.
To create the trial, edit Info.plist of the existing app, and add a
key:value pair under Java's Properties dictionary.
Set the key to: java.ext.dirs
Set the value to nothing (an empty string).
Hit return, save, and try launching it yourself, to confirm it still
works (i.e. isn't implicitly relying on any extensions installed on
your machine).
If it also runs on the customer machine, then you can either tell
them how to solve the problem themselves (remove jars from ext dirs),
or you can give them a tailored version of the app with no extensions.
You can also try enabling certain extension dirs, such as /System/
Library/Java/Extensions, but not others, by creating your own list of
colon-separated pathnames as the value of java.ext.dirs. This isn't
bulletproof: some people will still install extensions in places they
shouldn't, and those might cause your app to malfunction.
If your app does rely on some system-provided extensions, but
otherwise this solves the problem for the customer, post again and
I'll outline an idea for a solution.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
