Jon wrote:
> Has anyone applied this patch to their 2.0 JSDK yet? If so, were they any
> problems? Or, did you just replace the jar file and go on with your life
(the
> answer I'm hoping for).
The answer you are looking for is the right one. Although, if you read what
it fixes you will notice that you really don't need it for 99.9999% cases and
even if you are hit by the bug it isn't a big deal cause all it means is that
the page won't be cached.
Yeah, but I have to sign that Y2K certification document :(
> Might as well add that JDK 118 is now out (security patch to 117).
If you are on Solaris, get the 1.2.1_03 production version. It is released
now and much better than 118. I don't understand why people haven't started
migrating to 1.2.x.
Just downloaded, and I thought I had seen people raving about it here, so I
figured, since everything is getting a new coat of paint, this should probably
be done as well (over 1.1.8).
> Looks like I'm going to be fixing everything at once :(
It isn't that hard. I did it last night in under 30 minutes.
The best news yet (but, then, I'm upgrading Raven and such as well). Hopefully,
less than one hour to do it, and most of that should be compile time :)
Thanks for the pointers (and, yes, Jon, I still owe you a document for your
FAQ-o-matic, which I dearly love, btw). Consider a fire lit.... Basic documents
already written. Trying to format them to look halfway decent.
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
