Re: Java 1.4.2 Update ..... safe for WO
Re: Java 1.4.2 Update ..... safe for WO
- Subject: Re: Java 1.4.2 Update ..... safe for WO
- From: Jonathan Rochkind <email@hidden>
- Date: Wed, 4 Feb 2004 15:09:43 -0600
At 9:39 AM +1300 2/5/04, Denis Stanton wrote:
Hi Cliff
I'm pleased to see an Apple person join in this discussion.
Could we have a statement from the WebObjects team please? Is Java
1.4.2 safe for WebObjects?
You point out the dilemma below - Software Update offers us
something, but we don't know whether we can trust it.
You seem to be implying indirectly that we shouldn't trust Software Update.
Exactly. What we learned from the whole 1.4.1 with WO 5.2.1 debacle,
is that until Apple has made a statement that WO is qualified for a
particular new (Apple) release of the JRE, then... it is not
qualified, you use it at your own risk. At the moment, we know that
1.4.1 is qualified for WO 5.2.2, and WO 5.2.1 is qualified only with
JRE 1.3.1. Until Apple has officially qualified 1.4.2, you use it at
your own risk, and it may or may not work with WO. Somebody from
Apple, maybe Cliff I forget, already gave us a statement outlining a
couple places that WO _may_ have problems with 1.4.2, to pay special
attention to if you want to be a risk taker and try 1.4.2 with WO.
Even if you do install 1.4.2, there are apple provided instructions
(for ProjectBuilder, may also work for XCode, who knows) on how to
force your WO project to use an older-than-most-recent JRE version
for compilation and execution. You may want to take advantage of
those instructions if you want to install 1.4.2 for other purposes,
but don't want to use it with WO because it is not qualified.
The standing advice for JRE versions and WO is "Until Apple says it
is qualiifed for particular versions of WO, you use it at your own
risk." That's pretty straightforward. [The not straightforward
thing, of course, is that if you haven't heard that advice, and the
Software Updater offers you a new version, you are likely to use it
unthinkingly without realizing it is not qualified for WO. So it
goes.]
--Jonathan
I don't know who is responsible for this sort of thing inside Apple,
but do you think you could impress upon someone that it is very poor
to have no official advice on Java 1.4.2 / WebObjects compatibility
several days after the java update was released?
Ernie set up email@hidden.
The last posting was from Bob in October last year.
I think a note about Java 1.4.2 would be in order, particularly
after Java 1.3.1 stung early adopters who were using WebObjects.
Denis Stanton
On Thursday, February 5, 2004, at 06:08 AM, Cliff Tuel wrote:
And what about us Windows-based folks? (Yes, there are still some of us
suffering :rolleyes: )
If you want to use what's tested and supported by Apple, you continue to use
the same Java version. The problem on OS X is users were offered a newer
Java by our Software Update feature, and may assume it's safe to use with
WebObjects. Java doesn't have an auto-update mechanism on Windows, so
you're actually better-off. (And that's the last time you'll hear me say
that! :-) )
--
Cliff Tuel email@hidden http://apple.com/services/technicalsupport
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
Denis Stanton
email@hidden
Home: +64 9 533 0391
mobile: +64 21 1433622
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.