We are using an increasing amount of third-party jar files, everything from better jdbc drivers to vendor interfaces (ie paymentech java SDK). I am starting to wonder if just shoveling them all into jrun4\lib is such a great idea. Another option is to create a new folder for each one of these suckers that names the specific reason it is there (ie, c:\jtOpen, c:\paymentech, etc), but this could get pretty complicated and I like simple things.
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 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. Thanks, Eric Knipp Web Applications Group Unitrin Specialty - Insurance for U ----------------------------------------- CONFIDENTIALITY NOTICE: The information contained in this e-mail and attached document(s) may contain confidential information that is intended only for the addressee(s). If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action in reliance upon the information is prohibited. If you have received this e-mail in error, please immediately notify the sender and delete it from your system. ---------------------------------------------------------- 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
