Home/ Questions/Q 6872761
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T03:58:13+00:00

I want to create database at the first time of an application deploying process.

  • 0

I want to create database at the first time of an application deploying process. I am using JPA. So I consider two ways.

1) I have a full connection description in my persistence.xml:

<property name="mysql.jdbc.user" value="root"/>
<property name="mysql.jdbc.password" value=""/>
<property name="mysql.jdbc.url" value="jdbc:mysql://localhost:3306/DB"/>
<property name="mysql.jdbc.driver" value="com.mysql.jdbc.Driver"/>

When an application is started, it cannot connect to DB and reports about this trouble advising to go to the install page. In this install page I launch a DB creation with explicit SQL queries.

2) I have a connection to a database server:

<property name="mysql.jdbc.user" value="root"/>
<property name="mysql.jdbc.password" value=""/>
<property name="mysql.jdbc.url" value="jdbc:mysql://localhost:3306/"/>
<property name="mysql.jdbc.driver" value="com.mysql.jdbc.Driver"/>

An application informs me that it is a first conneciton and redirect me to the install page. During a DB installation persistence.xml should be modified. The property mysql.jdbc.url must be changed a new value assignment which declares a database name.

What do you think about this? How to do this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What you could do is add a servlet that is configured to run (once) at application startup. This servlet could check whether the database already exists and if not, create it programmatically. Check this question’s answers to see how this can be achieved for MySQL. If you have a running server, you can obtain a connection and run the SQL to create the database. After that, the necessary tables and the like can be auto-created using the right property for your JPA implementation (like Nulldevice showed for Hibernate).

    You could even have the servlet locate the persistence.xml file, since it’s supposed to be in a particular location anyway, and parse it to find out several properties like URL to make sure they’re only defined in one place.

    What I’m not certain about is whether JPA would only try connecting (and possibly creating the tables) after the servlet is run, or how this could be forced. For this, you might have to check the lifecycle of JavaEE applications. It could depend on the implementation by the Application Server vendor too.

    • 0