Yeah, I know ;-) What i probably meant was you dont need to "hack up" the distribution with custom libraries. The endorsed directory is there because the new jdk includes apis which are still under revision. Obviously this means that the standards are likely to change, as they quite obviously have, hence the incompatibilities in the libraries mentioned. I find this a great deal more realistic than waiting for an update to the jdk, or hacking throught the configuration file of every piece of software I wish to run which requires a newer version of, for example, the sax api. Deployment nightmare?
-----Original Message----- From: Lewis, Andrew J [mailto:[EMAIL PROTECTED]] Sent: miércoles, 06 de marzo de 2002 14:02 To: '[EMAIL PROTECTED]' Subject: RE: HOWTO: jdk1.4 /jre/lib/endorsed is in fact within the /jre/lib I understand that you may like it this way, but I'll stick with other solutions (which have been mentioned since my post). In my experience, this sort of solution is a deployment nightmare.... > ---------- > From: Matt Williams[SMTP:[EMAIL PROTECTED]] > Reply To: [EMAIL PROTECTED] > Sent: Tuesday, March 05, 2002 6:02 PM > To: [EMAIL PROTECTED] > Subject: RE: HOWTO: jdk1.4 > > Hi andrew, > Dont seem to be any required changes to the jre/lib at all. Maybe you > mean the jre/lib/endorsed directory. This isnt so much "grief" as > updating specific classes. I like it this way. > > Matt > > -----Original Message----- > From: Lewis, Andrew J [mailto:[EMAIL PROTECTED]] > Sent: martes, 05 de marzo de 2002 14:53 > To: '[EMAIL PROTECTED]' > Subject: RE: HOWTO: jdk1.4 > > > is it just me, or did the 1.4 JDK introduce a lot of grief here > REQUIRING changes to the jre/lib directory? Or is there another way to > make this work? --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
