Right, you were able to replace 1.3 with 1.4. But Dave is unable to do this with log4j. If he uses 1.1.3 it breaks his code. If he uses 1.2.7 it breaks CFMX. Only one version can be used at any one time. Sean summed it up as:
"What you've got here are two Java applications running on the same JVM that require different versions of the same library - and the library itself has changed its API. If you're going to point a finger of blame at some component of this, you could reasonably pick the library (log4j) for breaking the contract (API) it had with its users." chris >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Sunday, June 22, 2003 12:32 PM >To: CF-Talk >Subject: Re: Java development risk? (was: log4j problem migrating J2SE app) > >Forgive me if I am off track here, but isn't this what the classpath >is for? For example, MX comes with Javamail 1.3, but I installed 1.4 >and just edited the classpath to include the javamail jar at the >beginning and MX used 1.4... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
