I believe we went through this once before. It's a known bug.
The only way to get around it is to unjar j3dcore.jar,
fix the manifest, and re-jar it yourself. Of course you
can't distribute it like this because that would violate
the license agreement, but it should solve the problem.
The problems are being worked out and should be solved by the
release of our next beta. . .
-Paul
> MIME-Version: 1.0
> Date: Wed, 14 Mar 2001 10:33:42 -0500
> From: "J. Lee Dixon" <[EMAIL PROTECTED]>
> Subject: [JAVA3D] Number format exception during extension check
> To: [EMAIL PROTECTED]
>
> I have my code in a JAR, and I use the Java1.3 extension mechanism and
> ask for Java3D ver 1.2.1 in the JAR manifest.
>
> Well, if the user has installed Java3D ver 1.2.1 beta 2, then I get a
> NumberFormatException because "1.2.1 beta 2" is not really a number, and
> Java throws the exception while trying to check for the Java3D
> extension.
>
> Java3D team, how can I get around this? Are you ready to release 1.2.1
> yet, because I need to deploy my "beta" applet...
>
> Also, how can we prevent this from happening in the future during other
> Java3D beta releases?
>
> -Lee
>
> J. Lee Dixon
> SAIC - Celebration, FL
> 321-939-7917
> [EMAIL PROTECTED] AOL: LeeOrlando
>
> ===========================================================================
> 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".
===========================================================================
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".
