 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | -none- | -none- 2007-08-16 - By David Smith
Back
In my experience, a resource is usually only relevant to one webapp.
There's no need to put it in server.xml as a GlobalNamingResource unless
you want that resource available in all your webapps. Moving the
resource to the <Context> block of a context.xml file also makes it so
resources can come and go with deployment of an individual webapp
without restarting tomcat and disrupting all the webapps.
Developers could define their Resources in the <GlobalNamingResources>
... </GlobalNamingResources> block of server.xml and then add a
<ResourceLink> element to the context.xml file. That'll get you out of
having database specific information in the <Context ..../> element.
See this page for further details on that:
http://tomcat.apache.org/tomcat-5 (See http://cat-5.ora-code.com).5-doc/config/globalresources.html
--David
Matthew Kerle wrote:
> Hi David
>
> David Smith wrote:
>
>> My only editorial comment on the page is to NOT place your
>> <Resource.../> or <Context .../> definition in server.xml as
>> recommended on the page. Place it in context.xml or myapp.xml as I
>> describe above.
>
>
> Just quickly, I was wondering why you recommend this? I know the
> tomcat docs have changed to reflect the deprecation of defining the
> <Resource.../> or <Context .../> definition in server.xml, but I never
> understood why, and personally doing things that way is a serious pain
> for me since it means I need to build a separate deployment descriptor
> for dev, test & prod, which means I need to know the prod database
> details. which I don't want.
>
> Is there a better way that the sysadmin can setup a JNDI datasource so
> that deployed war's don't have to contain database-specific details?
> the only way I've seen so far is to configure that in the server.xml...
>
> cheers!
>
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
|
