Does anybody have any thoughts on this? The way we're doing it now could
get messy. We've already got third-party drivers for db2 and oracle, and
now we are adding this paymentech thing. Over time I imagine our jrun4\lib
could get real junked up.
I suppose it depends what you mean by "junked up"--it's not all that uncommon to dump all your third-party stuff into lib. The advantage is this makes it available to all your servers on JRun without any additional configuration since it's already in the classpath. You just have to be careful about possible conflicts, but since everything will either be a jar file or in package format it shouldn't get too terribly disorganized I wouldn't think.
I also worry that at some point we need to add a third-party SDK which uses different versions of stuff like log4j than another third-party application, causing a conflict .. not sure how to manage that either.
This can get kind of messy (especially with something like log4j that's part of CF), but worst case is usually that you just create a startup file for the specific server that needs these libraries and give it its own classpath. For example, if you have CF 7 and Flex both installed on JRun, it can cause some conflicts since bits of Flex are in CF. If you have a separate startup config file for each server it avoids any conflicts.
Matt
-- Matthew Woodward [EMAIL PROTECTED]
----------------------------------------------------------
To post, send email to [email protected]
To unsubscribe: http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe: http://www.dfwcfug.org/form_MemberRegistration.cfm
