Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Jar Bundler and bootclasspath




On Oct 13, 2005, at 5:15 PM, Greg Guerin wrote:

Andrew Hart wrote:

I'm trying to bundle up an application that  requires some specific
classes be in the boot class path.  ...snip...
I have the jar files in the Contents/Resources/Java directory:
vbjorb.jar, vbjapp.jar, and swingall.jar.

Why do you need swingall.jar? Mac OS X already has Swing.

Or is that the jar with the classes you need to force into the boot classpath?

Can you explain why you need to force classes into the boot classpath,
rather than just using the normal classpath?  Boot-classpathing is
generally discouraged, by Sun and others, unless you're doing something
experimental and have to hide or mask existing JRE classes.


The application uses an API that provides access to a particular digital asset management system (Artesia TEAMS). Their API requires that these three jars be in the bootclasspath. I know that the vbjorb and vbjapp jars are related to their use of a specific Visibroker ORB class. If they are not there, then Sun's orb gets resolved to instead. I don't know the specific purpose for the swingall.jar file. It's just a requirement of their API.

I have successfully used their API from a Java app and from a web app by modifying Tomcat's bootclasspath. I run it on windows systems using a bat file. I wanted to be a bit more elegant on OSX and take advantage of their java app bundling.



I have the VM Option set to:
-

No options came through there.

And the name of the key in Info.plist is "VMOptions", plural, no space.


Here is the relevant entry from the generated Info.plist file:

<key>VMOptions</key>
<string>


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.