The standard solution to manage the database connections in a web application is to let the server manage it, and use Spring to inject it wherever it is needed. By doing so, we can let also the transaction management to be done by a third party API, Spring fits perfectly this need. But this option… Continue reading Oracle proxy user with Spring
Tag: datasource
Define configuration file outside of the classpath
Here I describe the way I use to configure my applications. The main idea is to define a property file outside of the application, doing this, it is possible to deploy the same application in several environments (dev/test/prod) without any changes. First of all, the property file: net.classnotfound.app.jdbc.server=db-server net.classnotfound.app.jdbc.port=1521 net.classnotfound.app.jdbc.sid=xe net.classnotfound.app.jdbc.user=scott net.classnotfound.app.jdbc.password=koala The tips is… Continue reading Define configuration file outside of the classpath
Add datasource access in tests
In my web applications, the datasource is often defined in Tomcat (see here), when I execute my integration tests using JUnit, I don’t need Tomcat, but I need an access to the database, and to the Spring context too. My solution is to create an abstract test which provides me these features, I use: the… Continue reading Add datasource access in tests
Tomcat Datasource configuration
I describe here my favorite solution to define the datasource of my web applications. To do that in Tomcat : Copy the JDBC driver jar into the Tomcat lib directory define the datasource in the file server.xml: <GlobalNamingResources> <Resource auth=”Container” driverClassName=”oracle.jdbc.OracleDriver” maxActive=”20″ maxIdle=”10″ maxWait=”-1″ name=”jdbc/myGlobalDatasource” password=”password” type=”javax.sql.DataSource” url=”jdbc:oracle:thin:@[server]:[port]:[sid]” username=”user”/> </GlobalNamingResources> map this datasource to your… Continue reading Tomcat Datasource configuration