Re: What are the consequences of putting shared web resources in the "common" folder?
If you look at the development of tomcat, you'll see tomcat 6.0.x
actually eliminated the split between shared and common putting all
shared and common jars in the /lib directory. I would guess it's
primarily because no one was using shared. With that in mind, I don't
see any benefit to using shared over common unless you have a library
that conflicts with tomcat's internal classes.
--David
Edward Song wrote:
Thanks guys for replying.
I should of stated that the shared resources were already in the common
folder and have been for quite a while.
It seems to work fine, however, I was looking at my catalina.properties and
the documentation and noticed that maybe the shared resources should be
moved to the shared folder.
We don't do anything here with a "if it ain't broke, don't fix it"
mentality, so I was wondering what arguments I might pose for fixing it.
"driver .dll is already loaded. Moving it into the common folder prevents
this from happening." I guess it would be the same if it was moved to the
shared folder, so it doesn't really apply.
My thinking is that if it's only a hierarchy on how classes are loaded, and
that there are no real application or security threats, than there would be
no real consequences of keeping shared resources in the common folder.
It looks like, I don't have much of an argument for change.
Ed.
-Original Message-
From: Steve Ochani [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 09, 2008 12:51 PM
To: Tomcat Users List
Subject: Re: What are the consequences of putting shared web resources in
the "common" folder?
Date sent: Wed, 09 Jul 2008 12:42:34 -0400
From: David kerber <[EMAIL PROTECTED]>
Subject: Re: What are the consequences of putting shared web
resources in
the
"common" folder?
To: Tomcat Users List
Send reply to: Tomcat Users List
Steve Ochani wrote:
On 9 Jul 2008 at 11:57, Edward Song wrote:
What are the consequences of putting shared web resources in the
"common" folder vs. the "shared" folder?
I´m not sure how to articulate the consequences of putting shared
resources in the "common" folder. The following below is in the
documentation, but is it enough to force another QA cycle on a
server running multiple web apps?
Common - This class loader contains additional classes that are
made visible to both Tomcat internal classes and to all web
applications. Normally, application classes should NOT be placed
here.
Thanks in advance for anyone participating in this thread.
Why would you want to put "shared web resources" in the common
folder if the resources are just being used by the webapps?
One thing I've run into is a database driver that is used by multiple
webapps (on windows). If it's in each app's own lib, I get an error
that the driver .dll is already loaded. Moving it into the common
folder prevents this from happening. If there was a folder that was
shared only among web apps, and not with tomcat itself, that would
work as well.
I've used the shared dir. for that which is what the OP is comparing
against.
-Steve O.
D
-
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 e-mail transmission, and any documents, files or previous e-mail messages
attached to it may contain confidential information that is legally privileged.
If you are not the intended recipient, or a person responsible for delivering
it to the intended recipient, you are hereby notified that any disclosure,
copying, distribution or use of any of the information contained in or attached
to this transmission is STRICTLY PROHIBITED. If you have received this
transmission in error, please immediately notify me by reply e-mail and destroy
the original transmission and its attachments without reading or saving in any
manner. Thank you.
-
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]
RE: What are the consequences of putting shared web resources in the "common" folder?
Thanks guys for replying. I should of stated that the shared resources were already in the common folder and have been for quite a while. It seems to work fine, however, I was looking at my catalina.properties and the documentation and noticed that maybe the shared resources should be moved to the shared folder. We don't do anything here with a "if it ain't broke, don't fix it" mentality, so I was wondering what arguments I might pose for fixing it. "driver .dll is already loaded. Moving it into the common folder prevents this from happening." I guess it would be the same if it was moved to the shared folder, so it doesn't really apply. My thinking is that if it's only a hierarchy on how classes are loaded, and that there are no real application or security threats, than there would be no real consequences of keeping shared resources in the common folder. It looks like, I don't have much of an argument for change. Ed. -Original Message- From: Steve Ochani [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 09, 2008 12:51 PM To: Tomcat Users List Subject: Re: What are the consequences of putting shared web resources in the "common" folder? Date sent: Wed, 09 Jul 2008 12:42:34 -0400 From: David kerber <[EMAIL PROTECTED]> Subject: Re: What are the consequences of putting shared web resources in the "common" folder? To: Tomcat Users List Send reply to: Tomcat Users List > Steve Ochani wrote: > > On 9 Jul 2008 at 11:57, Edward Song wrote: > > > > > >> What are the consequences of putting shared web resources in the > >> "common" folder vs. the "shared" folder? > >> > >> I´m not sure how to articulate the consequences of putting shared > >> resources in the "common" folder. The following below is in the > >> documentation, but is it enough to force another QA cycle on a > >> server running multiple web apps? > >> > >> Common - This class loader contains additional classes that are > >> made visible to both Tomcat internal classes and to all web > >> applications. Normally, application classes should NOT be placed > >> here. > >> > >> Thanks in advance for anyone participating in this thread. > >> > >> > > > > > > Why would you want to put "shared web resources" in the common > > folder if the resources are just being used by the webapps? > > > > One thing I've run into is a database driver that is used by multiple > webapps (on windows). If it's in each app's own lib, I get an error > that the driver .dll is already loaded. Moving it into the common > folder prevents this from happening. If there was a folder that was > shared only among web apps, and not with tomcat itself, that would > work as well. > I've used the shared dir. for that which is what the OP is comparing against. -Steve O. > D > > > > - > 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 e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify me by reply e-mail and destroy the original transmission and its attachments without reading or saving in any manner. Thank you. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What are the consequences of putting shared web resources in the "common" folder?
Date sent: Wed, 09 Jul 2008 12:42:34 -0400
From: David kerber <[EMAIL PROTECTED]>
Subject: Re: What are the consequences of putting shared web
resources in
the
"common" folder?
To: Tomcat Users List
Send reply to: Tomcat Users List
> Steve Ochani wrote:
> > On 9 Jul 2008 at 11:57, Edward Song wrote:
> >
> >
> >> What are the consequences of putting shared web resources in the
> >> "common" folder vs. the "shared" folder?
> >>
> >> I´m not sure how to articulate the consequences of putting shared
> >> resources in the "common" folder. The following below is in the
> >> documentation, but is it enough to force another QA cycle on a
> >> server running multiple web apps?
> >>
> >> Common - This class loader contains additional classes that are
> >> made visible to both Tomcat internal classes and to all web
> >> applications. Normally, application classes should NOT be placed
> >> here.
> >>
> >> Thanks in advance for anyone participating in this thread.
> >>
> >>
> >
> >
> > Why would you want to put "shared web resources" in the common
> > folder if the resources are just being used by the webapps?
> >
>
> One thing I've run into is a database driver that is used by multiple
> webapps (on windows). If it's in each app's own lib, I get an error
> that the driver .dll is already loaded. Moving it into the common
> folder prevents this from happening. If there was a folder that was
> shared only among web apps, and not with tomcat itself, that would
> work as well.
>
I've used the shared dir. for that which is what the OP is comparing against.
-Steve O.
> D
>
>
>
> -
> 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]
Re: What are the consequences of putting shared web resources in the "common" folder?
Steve Ochani wrote: On 9 Jul 2008 at 11:57, Edward Song wrote: What are the consequences of putting shared web resources in the "common" folder vs. the "shared" folder? I´m not sure how to articulate the consequences of putting shared resources in the "common" folder. The following below is in the documentation, but is it enough to force another QA cycle on a server running multiple web apps? Common - This class loader contains additional classes that are made visible to both Tomcat internal classes and to all web applications. Normally, application classes should NOT be placed here. Thanks in advance for anyone participating in this thread. Why would you want to put "shared web resources" in the common folder if the resources are just being used by the webapps? One thing I've run into is a database driver that is used by multiple webapps (on windows). If it's in each app's own lib, I get an error that the driver .dll is already loaded. Moving it into the common folder prevents this from happening. If there was a folder that was shared only among web apps, and not with tomcat itself, that would work as well. D - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What are the consequences of putting shared web resources in the "common" folder?
On 9 Jul 2008 at 11:57, Edward Song wrote: > > What are the consequences of putting shared web resources in the "common" > folder vs. the > "shared" folder? > > I´m not sure how to articulate the consequences of putting shared resources > in the "common" > folder. > The following below is in the documentation, but is it enough to force > another QA cycle on a > server running multiple web apps? > > Common - This class loader contains additional classes that are made visible > to both > Tomcat internal classes and to all web applications. Normally, application > classes should > NOT be placed here. > > Thanks in advance for anyone participating in this thread. > Why would you want to put "shared web resources" in the common folder if the resources are just being used by the webapps? -Steve O. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What are the consequences of putting shared web resources in the "common" folder?
What are the consequences of putting shared web resources in the "common" folder vs. the "shared" folder? I'm not sure how to articulate the consequences of putting shared resources in the "common" folder. The following below is in the documentation, but is it enough to force another QA cycle on a server running multiple web apps? Common - This class loader contains additional classes that are made visible to both Tomcat internal classes and to all web applications. Normally, application classes should NOT be placed here. Thanks in advance for anyone participating in this thread. Ed This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify me by reply e-mail and destroy the original transmission and its attachments without reading or saving in any manner. Thank you. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
