> -----Original Message-----
> From: Christopher Schultz [mailto:[email protected]]
> Sent: Thursday, April 18, 2013 5:01 PM
> To: Tomcat Users List
> Subject: Re: <resource-ref> in web.xml
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Jakub,
>
> On 4/17/13 9:22 PM, Jakub 1983 wrote:
> > can I define database connection only in web.xml, without using
> > context.xml files ?
> >
> > can I pass database url, login and password into <resource-ref> ?
> >
> > when I define database conn in context.xml, resource-ref is not
> needed
> > at all, so what is it actually for ?
>
> If you define your database configuration in server.xml, you'll have to
> map from global to local scope. You don't need to do this with
> context.xml because the scope is -- by definition -- already local.
>
> - -chris
Chris -
Am I reading that correctly? If in my context.xml file, I define a DB resource
as:
<Resource
name="jdbc/oracleUCPPool"
type="oracle.ucp.jdbc.PoolDataSource"
factory="oracle.ucp.jdbc.PoolDataSourceImpl"
auth="Container"
connectionFactoryClassName="oracle.jdbc.pool.OracleDataSource"
... obviously redacted stuff ...
/>
I DO NOT need to add these lines to my web.xml?
<resource-ref>
<description>Oracle Universal Connection Pool</description>
<res-ref-name>jdbc/oracleUCPPool</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
That also brings up another, related, question.
In my old web.xml, I had this entry:
<context-param>
<param-name>LOG4J_PROPS</param-name>
<param-value>/WEB-INF/Log4j.properties</param-value>
</context-param>
Which I removed and replaced with an entry in the context.xml file:
<Parameter name="LOG4J_PROPS" value="/WEB-INF/Log4j.properties"
override="false" />
However, that didn't work. I had to provide the full path to the file in the
value parameter.
Is there a particular reason why? Or would it be something inside our code?
We are set up multi-tenant and trying to minimize the changes needed per tenant.
I'm using Tomcat 6.0.36 with Sun JDK 1.6.0_43.
Jeff
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
