RE: Common/lib works shared/lib doesn't
Hi, It's OK to leave it in common/lib. (IMHO it's also fine to have a copy for each webapp in WEB-INF/lib, but you stated you don't want that). Yoav Shapira Millennium Research Informatics -Original Message- From: Wangenheim, Marc [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 9:54 AM To: [EMAIL PROTECTED] Subject: Common/lib works shared/lib doesn't I need some help trying to get a shared jar to work in shared/lib. I've searched the archives and found many posts with this issue but no fix. Win2k Tomcat 4.1.30 JDK 1.42_03 My webapps are based on a framework I developed that is contained within one jar. Up until now I have included this jar with every webapp where it resides in WEB-INF/lib. This works fine but is a pain to support because every change to the framework needs to be pushed to all apps. I would like to share this jar so only one update for all apps is necessary. When moving the jar to shared/lib I get a runtime CNFE on the Login.jsp. The class that can't be found is part of the jar that now resides in shared/lib. Initially I did not have CATALINA_BASE set. I played around with setting CATALINA_BASE and adding the jar to the classpath but nothing seems to work. I then moved the jar to common/lib and the app worked. Tomcat documentation clearly states that shared application code should reside in shared/lib not in common/lib. Should I try to resolve the shared/lib issue or is it OK to leave the jar in common/lib ? Thanks, Marc Wangenheim ** The content of this e-mail message and any attachments are confidential and may be legally privileged, intended solely for the addressee. If you are not the intended recipient, be advised that any use, dissemination, distribution, or copying of this e-mail is strictly prohibited. If you receive this message in error, please notify the sender immediately by reply email and destroy the message and its attachments. ** This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Common/lib works shared/lib doesn't
I have seen this happen as well. I'm fine with putting jars in either the common/lib or the WEB-INF/lib, but how come shared/lib doesn't work at all? Nothing that gets placed in that directory shows up in the classloader. Is there something I need to configure to get those jars to load? Thanks for the help. Charlie Shapira, Yoav said the following on 6/11/2004 9:55 AM: Hi, It's OK to leave it in common/lib. (IMHO it's also fine to have a copy for each webapp in WEB-INF/lib, but you stated you don't want that). Yoav Shapira Millennium Research Informatics -Original Message- From: Wangenheim, Marc [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 9:54 AM To: [EMAIL PROTECTED] Subject: Common/lib works shared/lib doesn't I need some help trying to get a shared jar to work in shared/lib. I've searched the archives and found many posts with this issue but no fix. Win2k Tomcat 4.1.30 JDK 1.42_03 My webapps are based on a framework I developed that is contained within one jar. Up until now I have included this jar with every webapp where it resides in WEB-INF/lib. This works fine but is a pain to support because every change to the framework needs to be pushed to all apps. I would like to share this jar so only one update for all apps is necessary. When moving the jar to shared/lib I get a runtime CNFE on the Login.jsp. The class that can't be found is part of the jar that now resides in shared/lib. Initially I did not have CATALINA_BASE set. I played around with setting CATALINA_BASE and adding the jar to the classpath but nothing seems to work. I then moved the jar to common/lib and the app worked. Tomcat documentation clearly states that shared application code should reside in shared/lib not in common/lib. Should I try to resolve the shared/lib issue or is it OK to leave the jar in common/lib ? Thanks, Marc Wangenheim ** The content of this e-mail message and any attachments are confidential and may be legally privileged, intended solely for the addressee. If you are not the intended recipient, be advised that any use, dissemination, distribution, or copying of this e-mail is strictly prohibited. If you receive this message in error, please notify the sender immediately by reply email and destroy the message and its attachments. ** This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Common/lib works shared/lib doesn't
OK I'll leave it in common/lib. The problem with WEB-INF/lib is that is takes too much time to update all webapps. We have a rather cumbersome environment. Each app has to go through four environments (development, integration, certification, production) before it is available to the customer. Hopping from one environment to the next can take up to two days each because after Sarbanes-Oxley all we developers have access to is development and that's it. Now imagine I have 30 apps using this jar. If I need to make a change to the jar it becomes a nightmare to deploy. Thanks for the help tho =) -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 9:56 AM To: Tomcat Users List Subject: RE: Common/lib works shared/lib doesn't Hi, It's OK to leave it in common/lib. (IMHO it's also fine to have a copy for each webapp in WEB-INF/lib, but you stated you don't want that). Yoav Shapira Millennium Research Informatics ** The content of this e-mail message and any attachments are confidential and may be legally privileged, intended solely for the addressee. If you are not the intended recipient, be advised that any use, dissemination, distribution, or copying of this e-mail is strictly prohibited. If you receive this message in error, please notify the sender immediately by reply email and destroy the message and its attachments. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Common/lib works shared/lib doesn't
Hi, shared/lib works on tomcat 5.0.25. It's trivial to test and verify for yourself. The user reported this on 4.1.30, which is in maintenance mode where only showstopper and security bugs would be fixed, and further an OK workaround (using common/lib) exists. I didn't even try to confirm or reject his claim on 4.1.30, because of the above reasons, just answered his question of whether it's OK to use common/lib or not. Yoav Shapira Millennium Research Informatics -Original Message- From: Charles N. Harvey III [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 10:14 AM To: Tomcat Users List Subject: Re: Common/lib works shared/lib doesn't I have seen this happen as well. I'm fine with putting jars in either the common/lib or the WEB-INF/lib, but how come shared/lib doesn't work at all? Nothing that gets placed in that directory shows up in the classloader. Is there something I need to configure to get those jars to load? Thanks for the help. Charlie Shapira, Yoav said the following on 6/11/2004 9:55 AM: Hi, It's OK to leave it in common/lib. (IMHO it's also fine to have a copy for each webapp in WEB-INF/lib, but you stated you don't want that). Yoav Shapira Millennium Research Informatics -Original Message- From: Wangenheim, Marc [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 9:54 AM To: [EMAIL PROTECTED] Subject: Common/lib works shared/lib doesn't I need some help trying to get a shared jar to work in shared/lib. I've searched the archives and found many posts with this issue but no fix. Win2k Tomcat 4.1.30 JDK 1.42_03 My webapps are based on a framework I developed that is contained within one jar. Up until now I have included this jar with every webapp where it resides in WEB-INF/lib. This works fine but is a pain to support because every change to the framework needs to be pushed to all apps. I would like to share this jar so only one update for all apps is necessary. When moving the jar to shared/lib I get a runtime CNFE on the Login.jsp. The class that can't be found is part of the jar that now resides in shared/lib. Initially I did not have CATALINA_BASE set. I played around with setting CATALINA_BASE and adding the jar to the classpath but nothing seems to work. I then moved the jar to common/lib and the app worked. Tomcat documentation clearly states that shared application code should reside in shared/lib not in common/lib. Should I try to resolve the shared/lib issue or is it OK to leave the jar in common/lib ? Thanks, Marc Wangenheim * * The content of this e-mail message and any attachments are confidential and may be legally privileged, intended solely for the addressee. If you are not the intended recipient, be advised that any use, dissemination, distribution, or copying of this e-mail is strictly prohibited. If you receive this message in error, please notify the sender immediately by reply email and destroy the message and its attachments. * * This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Common/lib works shared/lib doesn't
Works for me. I was just looking for the explanation. I'll give it a go with 5.0.25 but I trust you on this one. :) Charlie Shapira, Yoav said the following on 6/11/2004 10:21 AM: Hi, shared/lib works on tomcat 5.0.25. It's trivial to test and verify for yourself. The user reported this on 4.1.30, which is in maintenance mode where only showstopper and security bugs would be fixed, and further an OK workaround (using common/lib) exists. I didn't even try to confirm or reject his claim on 4.1.30, because of the above reasons, just answered his question of whether it's OK to use common/lib or not. Yoav Shapira Millennium Research Informatics -Original Message- From: Charles N. Harvey III [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 10:14 AM To: Tomcat Users List Subject: Re: Common/lib works shared/lib doesn't I have seen this happen as well. I'm fine with putting jars in either the common/lib or the WEB-INF/lib, but how come shared/lib doesn't work at all? Nothing that gets placed in that directory shows up in the classloader. Is there something I need to configure to get those jars to load? Thanks for the help. Charlie Shapira, Yoav said the following on 6/11/2004 9:55 AM: Hi, It's OK to leave it in common/lib. (IMHO it's also fine to have a copy for each webapp in WEB-INF/lib, but you stated you don't want that). Yoav Shapira Millennium Research Informatics -Original Message- From: Wangenheim, Marc [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 9:54 AM To: [EMAIL PROTECTED] Subject: Common/lib works shared/lib doesn't I need some help trying to get a shared jar to work in shared/lib. I've searched the archives and found many posts with this issue but no fix. Win2k Tomcat 4.1.30 JDK 1.42_03 My webapps are based on a framework I developed that is contained within one jar. Up until now I have included this jar with every webapp where it resides in WEB-INF/lib. This works fine but is a pain to support because every change to the framework needs to be pushed to all apps. I would like to share this jar so only one update for all apps is necessary. When moving the jar to shared/lib I get a runtime CNFE on the Login.jsp. The class that can't be found is part of the jar that now resides in shared/lib. Initially I did not have CATALINA_BASE set. I played around with setting CATALINA_BASE and adding the jar to the classpath but nothing seems to work. I then moved the jar to common/lib and the app worked. Tomcat documentation clearly states that shared application code should reside in shared/lib not in common/lib. Should I try to resolve the shared/lib issue or is it OK to leave the jar in common/lib ? Thanks, Marc Wangenheim * * The content of this e-mail message and any attachments are confidential and may be legally privileged, intended solely for the addressee. If you are not the intended recipient, be advised that any use, dissemination, distribution, or copying of this e-mail is strictly prohibited. If you receive this message in error, please notify the sender immediately by reply email and destroy the message and its attachments. * * This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
RE: Common/lib works shared/lib doesn't
Marc, The only issue with having jars in common/lib, is that any static class variables are shared across every webapp, as the class loader only loads these classes once per server. Classes under webapp/WEB-INF/lib are loaded once per webapp and invisible to other webapps. For example, if you're using log4j, you can get every webapp logging to the same file, even if each webapp initialises logging separately (the webapp that initialises last wins). This is because log4j uses static variables to hold log configuration. To prevent this, I keep a copy of log4j.jar in webapp/WEB-INF/lib for every webapp. I keep most other jars in common/lib though This is not to say that everything should be in webapp/WEB-INF/lib, just that its worth knowing that there can be confusing consequences of sharing jars across webapps. Andy -Original Message- From: Wangenheim, Marc [mailto:[EMAIL PROTECTED] Sent: 11 June 2004 15:18 To: Tomcat Users List Subject: RE: Common/lib works shared/lib doesn't OK I'll leave it in common/lib. The problem with WEB-INF/lib is that is takes too much time to update all webapps. We have a rather cumbersome environment. Each app has to go through four environments (development, integration, certification, production) before it is available to the customer. Hopping from one environment to the next can take up to two days each because after Sarbanes-Oxley all we developers have access to is development and that's it. Now imagine I have 30 apps using this jar. If I need to make a change to the jar it becomes a nightmare to deploy. Thanks for the help tho =) -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 9:56 AM To: Tomcat Users List Subject: RE: Common/lib works shared/lib doesn't Hi, It's OK to leave it in common/lib. (IMHO it's also fine to have a copy for each webapp in WEB-INF/lib, but you stated you don't want that). Yoav Shapira Millennium Research Informatics ** The content of this e-mail message and any attachments are confidential and may be legally privileged, intended solely for the addressee. If you are not the intended recipient, be advised that any use, dissemination, distribution, or copying of this e-mail is strictly prohibited. If you receive this message in error, please notify the sender immediately by reply email and destroy the message and its attachments. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
