Databases
StackOverflow2013
Postsdbo
PONot able to read environment variable in persistence.xml
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONot able to read environment variable in persistence.xml
    primarykey
    data
    text
    <p>I have a Maven3 project where I'm using the tomcat7-maven-plugin. I would like to set the path for the embedded database via an environment variable argument to the jvm.</p> <p>Reading the variable with System.getenv("myDataDir") within a Java-Method returns the correct path. But when I try to set the variable ${myDataDir} in my persistence.xml and then I start tomcat with "mvn tomcat:run" I get FileNotFoundExceptions because the variable is not replaced with the actual value (it says e.g. Cannot find path for ${myDataDir}\derby.log)</p> <p>I don't know what's causing this - if it's the persistence provider (EclipseLink) that doesn't support this or if it's something else.</p> <p>My persistence.xml looks like this:</p> <pre><code>&lt;persistence xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd" version="2.0" xmlns="http://java.sun.com/xml/ns/persistence"&gt; &lt;persistence-unit name="myPersistence" transaction-type="RESOURCE_LOCAL"&gt; &lt;provider&gt;org.eclipse.persistence.jpa.PersistenceProvider&lt;/provider&gt; &lt;properties&gt; &lt;property name="javax.persistence.jdbc.driver" value="org.apache.derby.jdbc.EmbeddedDriver" /&gt; &lt;property name="javax.persistence.jdbc.url" value="jdbc:derby:${myDataDir}/DB;create=true;upgrade=true" /&gt; &lt;property name="javax.persistence.jdbc.user" value="admin" /&gt; &lt;property name="javax.persistence.jdbc.password" value="password" /&gt; &lt;property name="eclipselink.ddl-generation" value="create-tables" /&gt; &lt;property name="eclipselink.ddl-generation.output-mode" value="both" /&gt; &lt;property name="eclipselink.logging.level" value="SEVERE" /&gt; &lt;property name="eclipselink.logging.file" value="${myDataDir}/derby.log" /&gt; &lt;property name="eclipselink.application-location" value="${myDataDir}/dbScripts" /&gt; &lt;/properties&gt; &lt;/persistence-unit&gt; &lt;/persistence&gt; </code></pre> <h2>EDIT:</h2> <p>I forgot to mention, that I'm in a Spring 3 Framework environment. According to the examples on the web, this should be capable of using environment variables in persistence.xml...</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USStefan
    1. USStefan
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COIMHO this need to be done in eclipselink
      singulars
      1. PONot able to read environment variable in persistence.xml
      1. USOlivier Lamy
    2. COSorry, but I don't get what you mean by that?
      singulars
      1. PONot able to read environment variable in persistence.xml
      1. USStefan
    3. COthe library which read this file must interpolate placeholders ( ${myDataDir} ). That's NOT the role of Apache Tomcat as it's not part of xml descriptor it knows!
      singulars
      1. PONot able to read environment variable in persistence.xml
      1. USOlivier Lamy
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload