JPA: entity for multiple PU and different DB

[daniele licitra]

Hi to all.

I have a package (JAR_A) for entity and controller definition, for example:
entity: Entity
controller: EntityController

Then I use this jar in other projects/applications that use the entity.

I want to use the same JAR_A with different persistence unit and different database (in particular, mysql and postgresql) but when I define two persistence unit that include the same class, I have an exception.
So, I comment the other PU and compile the project.

there is a smarter way for use same package with different PU ?

[E Armitage]

How did you create the two persistence units and what error message did you get?

[daniele licitra]

I'm sorry, I did not explain the situation in the right way.

I have at least 3 package:
- the first package (it's a maven project) contains a "superclass" entity

@MappedSuperclass
public abstract class StandardEntity implements InterfacciaStandardEntity, Cloneable{
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
@Basic(optional = false)
@Column(nullable = false)
protected Integer id;
@Column(name = "ins_time", updatable=false)
@Temporal(TemporalType.TIMESTAMP)
protected Date insTime;
@Column(name = "ins_user", length = 20, updatable=false)
protected String insUser;
@Column(name = "upd_time")
@Temporal(TemporalType.TIMESTAMP)
protected Date updTime;
@Basic(optional = false)
@Column(name = "upd_user", nullable = false, length = 20)
protected String updUser;
@Column
protected Character status;
....

It defines the basic field of an entity and the relative getter and setter.

Inside the POM I define a plugin to enhance the class using datanucleus:
<plugin> <groupId>org.datanucleus</groupId> <artifactId>maven-datanucleus-plugin</artifactId> <dependencies> <dependency> <groupId>org.datanucleus</groupId> <artifactId>datanucleus-core</artifactId> <version>${dnversion}</version> </dependency> </dependencies> <version>${dnEnhVersion}</version> <configuration> <log4jConfiguration>${basedir}/log4j.properties</log4jConfiguration> <verbose>true</verbose> <api>JPA</api> <verbose>true</verbose> [b]<persistenceUnitName>abstract</persistenceUnitName>[/b] </configuration> <executions> <execution> <phase>process-classes</phase> <goals> <goal>enhance</goal> </goals> </execution> </executions> </plugin>
The plugin enhance the StandardEntity using the abstract persistence unit:
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/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"> <persistence-unit name="abstract" transaction-type="RESOURCE_LOCAL"> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> <class>com.bss.libbssabstract.database.entity.StandardEntity</class> <properties> <property name="javax.persistence.jdbc.url" value="jdbc:mysql://192.168.89.10:3306/easycooking_prova?zeroDateTimeBehavior=convertToNull"/> <property name="javax.persistence.jdbc.password" value="****"/> <property name="javax.persistence.jdbc.driver" value="com.mysql.jdbc.Driver"/> <property name="javax.persistence.jdbc.user" value="****"/> </properties> </persistence-unit> <persistence-unit name="abstract2" transaction-type="RESOURCE_LOCAL"> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> <class>com.bss.libbssabstract.database.entity.StandardEntity</class> <properties> <property name="javax.persistence.jdbc.url" value="jdbc:postgresql://localhost:3306/webbss?zeroDateTimeBehavior=convertToNull"/> <property name="javax.persistence.jdbc.password" value="****"/> <property name="javax.persistence.jdbc.driver" value="org.postgresql.Driver"/> <property name="javax.persistence.jdbc.user" value="****"/> </properties> </persistence-unit> </persistence>
If the PU is like above, it works.

- the second package use the first and define software specific entity:

@Entity
@Table(name = "basericette")
public class BaseRicette extends com.bss.libbssabstract.database.entity.BssStandardEntity implements Serializable {
...

the pom is:
<plugin> <groupId>org.datanucleus</groupId> <artifactId>maven-datanucleus-plugin</artifactId> <dependencies> <dependency> <groupId>org.datanucleus</groupId> <artifactId>datanucleus-core</artifactId> <version>${dnversion}</version> </dependency> </dependencies> <version>${dnEnhVersion}</version> <configuration> <log4jConfiguration>${basedir}/log4j.properties</log4jConfiguration> <verbose>true</verbose> <api>JPA</api> <verbose>true</verbose> <!--<persistenceUnitName>easycooking</persistenceUnitName>--> <persistenceUnitName>mysqlpu</persistenceUnitName> </configuration> <executions> <execution> <phase>process-classes</phase> <goals> <goal>enhance</goal> </goals> </execution> </executions> </plugin>

and the PUs are:

<persistence-unit name="easycooking" transaction-type="RESOURCE_LOCAL"> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> <class>com.bss.easycooking.libdataeasycooking2.entity.BaseRicette</class> <properties> <property name="javax.persistence.jdbc.url" value="jdbc:postgresql://192.168.89.5/easycooking"/> <property name="javax.persistence.jdbc.password" value="****"/> <property name="javax.persistence.jdbc.driver" value="org.postgresql.Driver"/> <property name="javax.persistence.jdbc.user" value="****"/> <property name="eclipselink.ddl-generation" value="create-tables"/> </properties> <exclude-unlisted-classes>false</exclude-unlisted-classes> </persistence-unit> <persistence-unit name="mysqlpu" transaction-type="RESOURCE_LOCAL"> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> <class>com.bss.easycooking.libdataeasycooking2.entity.BaseRicette</class> <properties> <property name="javax.persistence.jdbc.url" value="jdbc:mysql://192.168.89.10:3306/easycooking?zeroDateTimeBehavior=convertToNull"/> <property name="javax.persistence.jdbc.password" value="****"/> <property name="javax.persistence.jdbc.driver" value="com.mysql.jdbc.Driver"/> <property name="javax.persistence.jdbc.user" value="****"/> <property name="eclipselink.ddl-generation" value="create-tables"/> </properties> </persistence-unit>
Even if I specified in the POM plugin only a PU, i get the following error:

An annotation processor threw an uncaught exception.
Consult the following stack trace for details.
java.lang.RuntimeException: javax.annotation.processing.FilerException: Attempt to recreate a file for type com.bss.easycooking.libdataeasycooking2.entity.BaseRicette_
at org.eclipse.persistence.internal.jpa.modelgen.CanonicalModelProcessor.process(CanonicalModelProcessor.java:407)
...
Caused by: javax.annotation.processing.FilerException: Attempt to recreate a file for type com.bss.easycooking.libdataeasycooking2.entity.BaseRicette_
at com.sun.tools.javac.processing.JavacFiler.checkNameAndExistence(JavacFiler.java:522)


i found this page:
https://netbeans.org/bugzilla/show_bug.cgi?id=194605
The problem is that the same entity can't stay in two PU...the class first is enhanced for PU1 and then for PU2 but files already exists.

So, is a possible solution to create two plugin, one for PU, and create two JAR, *-mysql.jar and *postgresql.jar ?

[E Armitage]

what happens if you don't list the entity classes in persistence.xml files?

[daniele licitra]

Same issue

An annotation processor threw an uncaught exception.
Consult the following stack trace for details.
java.lang.RuntimeException: javax.annotation.processing.FilerException: Attempt to recreate a file for type com.bss.easycooking.libdataeasycooking2.entity.BaseRicette_
at org.eclipse.persistence.internal.jpa.modelgen.CanonicalModelProcessor.process(CanonicalModelProcessor.java:407)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:722)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1700(JavacProcessingEnvironment.java:97)
at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1029)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1163)
at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824)
at com.sun.tools.javac.main.Main.compile(Main.java:439)
at com.sun.tools.javac.main.Main.compile(Main.java:353)
at com.sun.tools.javac.main.Main.compile(Main.java:342)
at com.sun.tools.javac.main.Main.compile(Main.java:333)
at com.sun.tools.javac.Main.compile(Main.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554)
at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: javax.annotation.processing.FilerException: Attempt to recreate a file for type com.bss.easycooking.libdataeasycooking2.entity.BaseRicette_
at com.sun.tools.javac.processing.JavacFiler.checkNameAndExistence(JavacFiler.java:522)
at com.sun.tools.javac.processing.JavacFiler.createSourceOrClassFile(JavacFiler.java:396)
at com.sun.tools.javac.processing.JavacFiler.createSourceFile(JavacFiler.java:378)
at org.eclipse.persistence.internal.jpa.modelgen.CanonicalModelProcessor.generateCanonicalModelClass(CanonicalModelProcessor.java:98)
at org.eclipse.persistence.internal.jpa.modelgen.CanonicalModelProcessor.generateCanonicalModelClasses(CanonicalModelProcessor.java:226)
at org.eclipse.persistence.internal.jpa.modelgen.CanonicalModelProcessor.process(CanonicalModelProcessor.java:403)
... 41 more

[E Armitage]

Try the suggested workaround of separating the packages for the gerated meta model using syntax like the below
<persistence-unit name="Bar"> <properties> <property name="eclipselink.canonicalmodel.subpackage" value="one"/> </properties> </persistence-unit> <persistence-unit name="Bar2"> <properties> <property name="eclipselink.canonicalmodel.subpackage" value="two"/> </properties> </persistence-unit>

[daniele licitra]

 

E Armitage wrote:Try the suggested workaround of separating the packages for the gerated meta model using syntax like the below
<persistence-unit name="Bar"> <properties> <property name="eclipselink.canonicalmodel.subpackage" value="one"/> </properties> </persistence-unit> <persistence-unit name="Bar2"> <properties> <property name="eclipselink.canonicalmodel.subpackage" value="two"/> </properties> </persistence-unit>

It worked with the two different subpackage! Thanks