Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Re: Easily switch the current default Java version' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Re: Easily switch the current default Java version
Authored by: raider on Jan 29, '06 05:16:46PM

One of the problems with many Java applications and/or the developers of them - is that they treat Java like a compiled language where you can guarantee more about how your application is run...

Which could be a problem with Java itself. It could probably be argued both ways.

But when you develop a Java application that is going to be run in unknown environments - you HAVE to account for EVERY POSSIBLE configuration. You HAVE to - or you get the problems you describe.

Hell, dealing with classloader issues in different custom JVMs is a pain in the arse. IBM is constantly mucking with the classloading in the JVMs they ship with WebSphere - and BEA likes to break standardized things like SSL... And don't even try and get into having cross JVM compatible encryption and the like without accounting for almost every possible difference in environment...

Even in my work - where I can reasonably guarantee the environment of a server, I regularly run into a problems when porting to other systems with similarly "stable" environments.

Like an old instructor of mine was fond of saying - "if you write it so it will run everywhere it will run nowhere." :)

We go to production with the Java we have - not the Java we want...


[ Reply to This | # ]