Matt,
Thank you for the quick response. It makes sense and all of our new
stuff is on 1.4.2 and higher. However, this issue was on an older
supported release where we had 1.3 as our minimum JRE and thus packaged
up the xerces, xalan and xml-apis jars. Packaging up these jars with
the app launched with 1.5 caused XSL transforms to throw exceptions
because they were not properly loaded using the extensions or endorsed
(not in 1.3) mechanisms. We will just re-make our bundle on that older
release to use only 1.4.2 and newer.
Regards,
Michael
Matt Drance wrote:
Hi Michael,
What you're seeing is expected behavior:
5: Is Java 1.3 or earlier releases of
Java supported on Intel based Macs?
No. J2SE 1.4 and 5.0 (1.5) are
currently supported on Intel based Macintosh computers.
Hopefully, launching the application under 1.5 results in no
visible difference to your users. If there is something explicitly
keeping you on 1.3, please let us know in the form of bug reports at https://bugreport.apple.com/ We
want to stomp out any 1.3 migration issues developers may have.
md
----------------------
Matt Drance
DTS Engineer
email@hidden
On Sep 11, 2006, at 2:50 PM, Michael Macaluso wrote:
All,
We are experiencing a rather strange
problem and we would like to know if it is just our location or a
general issue. On our lone
MacBook Pro machine, setting the JVMVersion in the Info.plist of our
Application Bundle to "1.3*" or "1.3.1" still causes the 1.5 VM to
launch (1.4 and 1.5 related values work fine). Same exact bundle on our PPC
machines, the 1.3 VM still launches.
Can anyone else confirm similar behavior? If not, any ideas on how this
machine might have gotten into this state (preferences, paths, etc.)? If so, doesn't this pretty
much mean that 1.3 is officially dead for those of us using application
bundles?
Thanks for the help.
Michael
_______________________________________________
Do not post admin requests to the list.
They will be ignored.
Help/Unsubscribe/Update your Subscription:
|
