> > > 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: > > > >Isnt this the sort of thing that you can use a custom class loader for? > > Maybe, but unless you know about the conflict up-front, it will > still require reworking your code. If my application is using a > third-party library just fine now but a future version of CFMX > starts using an incompatible version of the same library, I'm > still faced with either reworking the code or not upgrading to > the new version of CFMX. >
Can't you resolve these sorts of conflicts by using CFMX for J2EE and just intalling your application to a different context root? Excuse me if I'm way off, as I'm not a heavy Java programmer (yet). But isn't the point of a context root to prevent these sorts of collisions? The standalone version of MX I can see as being a problem, but it sounds like you'd benefit from the J2EE version of MX (which I use, and it's been fantastic). Regards, Dave. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
