You might use JNDI in a way that's not tied to the  servlet engine. This could 
seperate it from the servlet engine  altogether, maybe LDAP or something.

Hadraba Petr <[EMAIL PROTECTED]> wrote:  Hi,

maybe helps this, but it's working on Tomcat 5.5.15:-(

http://mail-archives.apache.org/mod_mbox/tomcat-users/200602.mbox/[EMAIL 
PROTECTED]


PETR

On 2/13/06, chen jacky  wrote:
> hi,
>   Do you mean add the following code in the web.xml?
> 
>       DB Connection
>       jdbc/TestDB
>       javax.sql.DataSource
>       Container
>   
>
> But this still need to add the jdbc config in the server.xml,right?
> Can you give me some suggestions?
>
> >From: "Duan, Nick" 
> >Reply-To: "Tomcat Users List" 
> >To: "Tomcat Users List" 
> >Subject: RE: jdbc context
> >Date: Mon, 13 Feb 2006 10:11:34 -0500
> >
> >You should be able to add the context info in your web.xml file.  In
> >other words, instead of making the JDBC resource available to all web
> >apps, you make it only to particular applications.  If this JDBC
> >connection is only used by the workflow web app, defining it in web.xml
> >is actually preferred.
> >
> >ND
> >
> >-----Original Message-----
> >From: jacky [mailto:[EMAIL PROTECTED]
> >Sent: Monday, February 13, 2006 5:07 AM
> >To: users@tomcat.apache.org
> >Subject: jdbc context
> >
> >hi,
> >    I have deploy a workflow webapp in Tomcat4.1.31. First time, i add
> >the following code in server.xml:
> >
> >
> >           
> >           
> >           

> >      maxActive
> >     > >-->
> >      100
> >     

> >     

> >      maxIdle
> >     > >0 for no limit. -->
> >      30
> >     

> >     

> >      maxWait
> >     > >ms.An exception is thrown if this timeout is exceeded.Set to -1 to 
> > wait
> >indefinitely. -->
> >      15000
> >     

> >     

> >      removeAbandoned
> >     
> >      true
> >     

> >     

> >      removeAbandonedTimeout
> >     > >seconds a DB connection has been idle before it is considered 
> > abandoned.
> >-->
> >      60
> >     

> >     

> >      logAbandoned
> >     
> >      false
> >     

> >     

> >      factory
> >     
> >      org.apache.commons.dbcp.BasicDataSourceFactory
> >   

> >
> >
usernamesa

> >             
password

> >             
driverClassName
> >
> >com.microsoft.jdbc.sqlserver.SQLServerDriver

> >             
url
> >
> >jdbc:microsoft:sqlserver://localhost:1433;databaseName=myworkflow
> >

> >           
> >
> >
> >It works well. But now, we need to migrate myworkflow into another
> >tomcat4.1.31, in which the server.xml can't be modified.
> >So what shall i do to deploy the jdbc context? Thanks for your help!
> >
> >      Best Regards.
> >        jacky
> >
> >
> >---------------------------------------------------------------------
> >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]
>
>



                
---------------------------------
Yahoo! Messenger  NEW - crystal clear PC to PC calling worldwide with voicemail 

Reply via email to