> -----Original Message----- > From: Discussion list for Java 3D API > [mailto:[EMAIL PROTECTED]]On Behalf Of Andrea Boright > > I have looked through the documentation "Deploying Java > Extensions" and "Optional Package Versioning", and it seems > rather theoretical. That is, I understand that the parameters in > the manifest need to be supplied with values, but I don't know > what specific values to use for Java3D. > > for instance: java3d-Implementation-URL: > > As far as I can tell, Sun doesn't provide a signed jar file for > Java3D that I can put here. >
<snip> Can anyone from Sun speak to the long term plans on the extension deployment issue, and whether or not an official "HOWTO" type document is planned? Given the existence of the Extension Mechanism, Package Version Identification, Endorsed Standards Override Mechanism, Applets (APPLET + EMBED + OBJECT), the Java Plug-In, WebStart, and finally, JSR 38 "Application Installation API Specification", it's getting to be a little confusing as to how one should best deploy a Java application. Also, the fact that you can't get a Java3D JAR file signed by Sun seems a little odd. Is this just an oversight (e.g. does the JMF group provide one?), or is there some other issue at hand? Thanks, Simeon =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
