Another way could be to deploy a single webapp in a single Tomcat instance so there are no classloading issues. But of course that will create as many VMs as there are webapps.
-----Original Message----- From: Sharma, Siddharth Sent: Friday, July 21, 2006 3:04 PM To: 'Tomcat Users List' Subject: RE: Shared code but different pages on different virtual hosts? W AS: RE: BOOBIES! No, don't put the jars anywhere where a classloader looks for them automatically (such as extension dirs). Create a different name of the same jar for each version. Put them at the enterprise app level. <my_ent_app>/myJar1_ver1.jar <my_ent_app>/myJar1_ver2.jar <my_ent_app>/myJar2_ver1.jar <my_ent_app>/myJar2_ver2.jar in webapp1's manifest add myJar1_ver1.jar myJar2_ver1.jar in webapp2's manifest add myJar1_ver2.jar myJar2_ver2.jar This will only work if Tomcat uses a different classloader for each webapp, each with its unique classpath. I do not know enough about Tomcat to know the answer. -----Original Message----- From: Avi Deitcher [mailto:[EMAIL PROTECTED] Sent: Friday, July 21, 2006 2:53 PM To: Tomcat Users List Subject: Re: Shared code but different pages on different virtual hosts? W AS: RE: BOOBIES! Ah, that is nice and simple. Put versionized by name jars in /shared/lib/, but reference the specific versions in the manifest? But how do you ensure that the jars won't be loaded anyways? Sharma, Siddharth wrote: >No you don't copy. >My suggestion was to have one physical jar(s) referenced in the manifest of >all webapps. > > >-----Original Message----- >From: Harris, Thomas [mailto:[EMAIL PROTECTED] >Sent: Friday, July 21, 2006 2:40 PM >To: Tomcat Users List >Subject: RE: Shared code but different pages on different virtual hosts? >WAS: RE: BOOBIES! > > >That means that for each change of the core code, I have to copy a jar >to each of 40 web apps. That's what I've been trying to avoid... A >maintenance nightmare. I want a single copy of each version of the core >code (in a WAR file, or something) sitting on it's own, and each of the >web apps refers to it. The web apps need to have their own JSP and tag >file folders, since they are different sites. > >Tom > >-----Original Message----- >From: Sharma, Siddharth [mailto:[EMAIL PROTECTED] >Sent: Friday, July 21, 2006 2:32 PM >To: Tomcat Users List >Subject: RE: Shared code but different pages on different virtual hosts? >WAS: RE: BOOBIES! > >Jar up the common code into one or more libraries. >Put them somewhere (possibly at the enterprise app level) and add each >jar in each webapp's MANIFEST file. > > >-----Original Message----- >From: Harris, Thomas [mailto:[EMAIL PROTECTED] >Sent: Friday, July 21, 2006 2:19 PM >To: Tomcat Users List >Subject: Shared code but different pages on different virtual hosts? >WAS: >RE: BOOBIES! > > >I wanted to have multiple web applications defined, all using the same >core Java code, but each having different JSP and tag file folders. I >tried following the example in the Tomcat Wiki at >http://wiki.apache.org/tomcat/CreateVirtualHosts, but it assumes all the >web apps have the same JSP and tag files, inside a WAR. I would like to >package up all of the common code for all the sites in a WAR file, then >point each separate web app to private JSP and tag file folders. What I >was trying to determine is: > >1. Is it even possible? >2. If so, how could it be done? > >As for the subject line, my previous email sat with the subject "Shared >code but different pages on different virtual hosts?" for two weeks >without a single response, and I'm still waiting so that my project can >continue down it's path. No offense is meant, and it should be pretty >obvious, I think, that I just wanted a little attention for my issue. >Sorry for any offense it may have caused. > >Tom > >-----Original Message----- >From: Mike Wannamaker [mailto:[EMAIL PROTECTED] >Sent: Friday, July 21, 2006 2:09 PM >To: 'Tomcat Users List' >Subject: RE: BOOBIES! > >I believe the subject was posted under different subject heading with no >response and he's trying to get people looking at it, which I'm sure he >will now. > >That said, some proper netiquette is appreciated in forums. > >I believe that I'm doing something similar, but using a different >approach. >I too want to have some common resources that all webapps use. To do >this I'm installing my own FileDirContext for web apps which I inject >what we call aliases. > >IE: /basefiles = /home/tomcat/basefiles > >Thus when someone in the webapp makes a request for >/basefiles/common.css it looks it up in /home/tomcat/basefiles, which is >outside of any web app context. > >Is this what you want to do? > >Mike Wannamaker > >-----Original Message----- >From: Mead, Jennifer L - VSCM [mailto:[EMAIL PROTECTED] >Sent: July 21, 2006 2:01 PM >To: Tomcat Users List >Subject: RE: BOOBIES! > >Could this person (inject other undesirable word) please consider the >fact that women are in the user's group also. > >Jennifer > >-----Original Message----- >From: Harris, Thomas [mailto:[EMAIL PROTECTED] >Sent: Friday, July 21, 2006 10:59 AM >To: users@tomcat.apache.org >Subject: BOOBIES! > > >I have been trying to determine how to configure Tomcat 5.5.17 to have a >shared appBase on multiple webapps, but have a different set of JSPs for >each web app. I've followed the Wiki's CreateVirtualHosts page to >configure multiple webapps that use exactly the same WAR file. But, I >would like to share the Java, but supply a different docBase for each >site. Is this possible? > >Reference: >http://wiki.apache.org/tomcat/CreateVirtualHosts > >Thanks! > >Tom Harris > >"This communication is intended solely for the addressee and is >confidential and not for third party unauthorized distribution" > >--------------------------------------------------------------------- >To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, >e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >--------------------------------------------------------------------- >To start a new topic, e-mail: users@tomcat.apache.org >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > >--------------------------------------------------------------------- >To start a new topic, e-mail: users@tomcat.apache.org >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >"This communication is intended solely for the addressee and is >confidential >and not for third party unauthorized distribution" > >--------------------------------------------------------------------- >To start a new topic, e-mail: users@tomcat.apache.org >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > >--------------------------------------------------------------------- >To start a new topic, e-mail: users@tomcat.apache.org >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >"This communication is intended solely for the addressee and is confidential >and not for third party unauthorized distribution" > >--------------------------------------------------------------------- >To start a new topic, e-mail: users@tomcat.apache.org >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > >--------------------------------------------------------------------- >To start a new topic, e-mail: users@tomcat.apache.org >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > -- ______________________________ Avi Deitcher [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
