Hi all,

I have a web application of Struts2.2.1+spring2.5.6+hibernate3.3.1. The datasource is configured in applicationContext.xml like the following:

<bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
<property name="driverClassName" value="com.mysql.jdbc.Driver" />
<property name="url" value="jdbc:mysql://localhost:3306/db_ictboxm?useUnicode=true&amp;characterEncoding=utf8" />
<property name="username" value="root" />
<property name="password" value="passw0rd" />

</bean>


It works fine after the WAR is deployed, but in the case that the datasource parameters are different from that in applicationContext.xml, the hostname, the username and password, for example, I need to edit the applicationContext.xml to change these three values manually, and then restart the container tomcat, finally access the website.

Is there a way that allows the deployer to reset the three values, not by editing the applicationContext.xml?
can applicationContext.xml be read and saved by code? and do i must restart container tomcat after the applicationContext.xml is changed? how to solve this problem?

Lucy

the standard way to do this properly is to not use the datasource bean, but to have a datasource defined in the configuration of the application server (also Tomcat).
This configuration defines a JNDI name for the datasource, and you configure Hibernate to access this datasource.

Hi ,

Your suggestion may partly solve the problem, but my reqiurement is to let the end user to configure the datasource by themselves. I created a Web application (Struts 2 +Spring +Hibernate), I want to let the user to download my application from my website and install it to their own machine. Once the user visit the homepage of the application, the homepage will check if the database can be accessed. If not , the user will be directed to a configure page. After the user input the url ,username and password of database properly, the application can run properly. This is my purpose.

Is there any way to solve this problem?

Thanks in advance.

Lucy

yes, in many creative ways, and no, this is not Hibernate's business :)
All code you provide to your customer is easily reverse engineered, so you'd need an asymmetric encription, but that's not supported by databases.
You could add a new user account on the database for each customer, or as people do more often keep hibernate on your remote webserver, and have people call via RMI / EJB3 remote into your application.