This content has been marked as final. Show 4 replies
Welcome to the Sun forums.
The basic answer to your question is to put the API on the application's run-time class-path. This can be done using the -cp option, a manifest, JWS, the applet archive element, placing the Jar in the WEB-INF/lib of a web application..
To provide a more specific answer, would require (a lot) more information about the context.
I'll try to explain better. The 3DS Loader I'm using is called StarfireExt.jar. I have two computers that I am using right now: a custom built desktop with Windows XP 32 bit that runs Netbeans, and a Dell laptop that I'm using to test my software. On the desktop, I have JDK1.6u18 with Java3D also installed. StarfireExt.jar is in my C:/Program Files/Java/jdk1.6.0_18/lib/ext/ folder, and Netbeans allows me to import and use StarfireExt. On the laptop, I have JRE1.6u20, Java3D, and StarfireExt in the lib/ext/ folder. When I'm on the desktop in Netbeans and press F6, it runs fine and the 3DS files load and are displayed. When I clean and build the JAR and move all of the models and JAR to my laptop, the program seems not able to find StarfireExt. The models don't load; no error windows that I've coded pop up.
P.S. I'm sorry if I'm kind of a Java newbie. I don't know all those awesome developer tricks yet.
trozamon wrote:Whoa, take a breath! I skimmed that mess of words and it did not seem to add anything I did not already know that was relevant. For example, I still don't know if this is intended to be a command line app. (no GUI), a servlet, applet, or rich client desk-top application. The ways of adding APIs to the run-time class path of an application (basically) break down along those lines.
I'll try to explain better. .. (big snip)
Try researching based on the keywords I gave you, and come back with a more focused question.
..P.S. I'm sorry if I'm kind of a Java newbie. ..In that case, I suggest that you have bitten off more than you can chew in taking on this project. Perhaps you should put it aside and come back to it later.