Come configurare hbm2java e hbm2dao aggiungere packagename alle classi generate
-
27-09-2019 - |
Domanda
Sto provando a configurare hbm2java
con Maven per generare classi POJO e oggetti DAO. Uno dei problemi che sto trattando è nomi dei pacchetti non vengono generati. Sto utilizzando il seguente pom per questo:
<execution>
<id>hbm2java</id>
<phase>generate-sources</phase>
<goals>
<goal>hbm2java</goal>
</goals>
<inherited>false</inherited>
<configuration>
<components>
<component>
<name>hbm2java</name>
<implementation>configuration</implementation>
</component>
</components>
<componentProperties>
<packagename>package.name</packagename>
<configurationfile>target/hibernate3/generated-mappings/hibernate.cfg.xml</configurationfile>
</componentProperties>
</configuration>
</execution>
Eppure il codice generato inizia con la seguente:
// default package
// Generated 2010-05-17 13:11:51 by Hibernate Tools 3.2.2.GA
/**
* Messages generated by hbm2java
*/
public class Messages implements java.io.Serializable {
C'è un modo per forzare Maven per generare il pacchetto parte come definito in packagename
Aggiornamento:
Ecco il mio hibernate.cfg.xml, anche generato automaticamente da Hibernate-tools (hbm2cfgxml):
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
<hibernate-configuration>
<session-factory>
<property name="hibernate.c3p0.max_size">20</property>
<property name="hibernate.c3p0.max_statements">50</property>
<property name="hibernate.c3p0.min_size">5</property>
<property name="hibernate.c3p0.timeout">1800</property>
<property name="hibernate.connection.driver_class">org.postgresql.Driver</property>
<property name="hibernate.connection.password">password</property>
<property name="hibernate.connection.url">jdbc:postgresql://localhost:5432/db</property>
<property name="hibernate.connection.username">username</property>
<property name="hibernate.dialect">org.hibernate.dialect.PostgreSQLDialect</property>
<mapping resource="package/name/Messages.hbm.xml" />
</session-factory>
</hibernate-configuration>
Soluzione
Nel caso in cui, qui è una configurazione di lavoro del Hibernate3-Maven-plug per un approccio bottom-up:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>hibernate3-maven-plugin</artifactId>
<version>2.2</version>
<executions>
<execution>
<id>generate-xml-files</id>
<phase>generate-resources</phase>
<goals>
<goal>hbm2hbmxml</goal>
<goal>hbm2cfgxml</goal>
</goals>
</execution>
<execution>
<id>generate-entities</id>
<phase>generate-sources</phase>
<goals>
<goal>hbm2java</goal>
</goals>
</execution>
</executions>
<configuration>
<components>
<component>
<name>hbm2hbmxml</name>
<implementation>jdbcconfiguration</implementation>
<outputDirectory>target/classes</outputDirectory>
</component>
<component>
<name>hbm2cfgxml</name>
<implementation>jdbcconfiguration</implementation>
<outputDirectory>target/classes</outputDirectory>
</component>
<component>
<name>hbm2java</name>
<implementation>configuration</implementation>
<outputDirectory>target/generated-sources/hibernate3</outputDirectory>
</component>
</components>
<componentProperties>
<propertyfile>src/main/resources/database.properties</propertyfile>
<jdk5>true</jdk5>
<ejb3>false</ejb3>
<packagename>com.mycompany.myapp</packagename>
<format>true</format>
<haltonerror>true</haltonerror>
</componentProperties>
</configuration>
<dependencies>
<dependency>
<groupId>org.apache.derby</groupId>
<artifactId>derby</artifactId>
<version>10.5.3.0_1</version>
</dependency>
</dependencies>
</plugin>
E qui è il contenuto del mio file src/main/database.properties
:
hibernate.connection.driver_class=org.apache.derby.jdbc.EmbeddedDriver
hibernate.connection.url=jdbc:derby:./derbyDBs/EMPLDB
hibernate.connection.username=APP
hibernate.connection.password=APP
hibernate.dialect=org.hibernate.dialect.DerbyDialect
#workaround for http://opensource.atlassian.com/projects/hibernate/browse/HBX-1145
hibernate.connection.autocommit=true
Questa configurazione:
- Genera
*.hbm.xml
intarget/classes
(con il pacchetto) durantegenerate-resources
. - Genera un
hibernate.cfg.xml
intarget/classes
con le voci per i file di mapping. - Genera organismi dei mappature in
target/generated-sources/hibernate3
(vi consiglio a seguito della convenzionetarget/generated-sources/<tool>
per le fonti generate in modo che otterranno automaticamente rilevato dal IDE).
Ecco il risultato di clean compile
contro un database di esempio con due tabelle:
$ mvn clean compile ... $ tree target/ target/ ├── classes │ ├── com │ │ └── mycompany │ │ └── myapp │ │ ├── Department.class │ │ ├── Department.hbm.xml │ │ ├── Employee.class │ │ └── Employee.hbm.xml │ ├── database.properties │ └── hibernate.cfg.xml └── generated-sources └── hibernate3 └── com └── mycompany └── myapp ├── Department.java └── Employee.java
Altri suggerimenti
Ok, ho capito. Ho messo la risposta qui .