Datasource in web.xml

[Ajay Xavier]

hi,

What is the advantage of specifying datasource reference in web.xml ? Is it necessary that datasource reference should be added to web.xml?

Regards,
Ajay.

[ak pillai]

You can acyiure it declaratively by specifying in your web.xml something like

<resource-ref>
  <description>Customer Database</description>
  <res-ref-name>jdbc/CustomerDB</res-ref-name>
  <res-type>javax.sql.DataSource</res-type>
  <res-auth>Container</res-auth>
</resource-ref>

There's nothing stopping you from using data sources programmatically instead of declaratively. Having declarative approach is preferable because you code can concentrate more writing business logic as opposed to infrastructure services.

[Bear Bibeault]

Originally posted by ak pillai:
You can acyiure it declaratively by specifying in your web.xml something like

acyiure?

[ak pillai]

was meant to write acquire.

[Ajay Xavier]

Thanks for your reply Arul.

If we don't specify it in web.xml
is there any other way we can acquire datasource connection in our web application?

Regards,
Ajay.

[Naseem Khan]

You can also do it from server.xml.

In Tomcat 5.5.8, you can put this tag within the innermost tag (<Host> tag)

<Context path="/DBTest" docBase="ABSOLUTE_PATH_OF_PROJECT_HERE"
         debug="5" reloadable="true">   
         
         <Resource name="jdbc/TestDB" auth="Container"     
                         type="javax.sql.DataSource"               
                         maxActive="100" maxIdle="30" 
                         maxWait="10000" username="" password="" 
                         driverClassName="sun.jdbc.odbc.JdbcOdbcDriver" 
                         url="jdbc:odbc:db1"/>
</Context>

Naseem
[ July 13, 2006: Message edited by: Naseem Khan ]

[Scott Selikoff]

You could put it in a properties text file if you have a lot of other properties you need to store. It doesn't matter where you put it (web.xml, text file, or setup a database connection pool on the server*) as long as its not hardcoded into the java file.

*Best solution

[Ajay Xavier]

Hi scott,

You could put it in a properties text file if you have a lot of other properties you need to store. It doesn't matter where you put it (web.xml, text file, or setup a database connection pool on the server*) as long as its not hardcoded into the java file.

Do you mean this?

We have to create a datasource in the Application server and bind it with a JNDI name. The Jndi name can be given either in the web.xml or a properties file.

Regards,
Ajay.