[Hibernate-JIRA] Created: (HBX-731) All the fields are marked as <key-property> in <composite-id>
by Al Dev (JIRA)
All the fields are marked as <key-property> in <composite-id>
-------------------------------------------------------------
Key: HBX-731
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-731
Project: Hibernate Tools
Type: Bug
Environment: Hibernate Tools 3.1.0.beta5
MS Windows, Oracle 9i server
Reporter: Al Dev
All the fields are marked as <key-property> in <composite-id>
in the Scbcrse.hbm.xml file. How come the tool is not picking up the unique index key fields in the database table?
What I expect from the hibernate tool is that it should not the unique key indexes created for the database table and
based on that it should make the <composite-id> fields.
It looks like the tool is completely ignoring the unique key indexes created on the table.
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<!-- Generated Aug 16, 2006 4:23:47 PM by Hibernate Tools 3.1.0.beta5 -->
<hibernate-mapping>
<class name="edu.sjcd.hibernate.oracle.ScbcrseMy" table="SCBCRSE" schema="SATURN">
<composite-id name="id" class="edu.sjcd.hibernate.oracle.generated.ScbcrseId">
<key-property name="scbcrseSubjCode" type="string">
<column name="SCBCRSE_SUBJ_CODE" length="4" />
</key-property>
<key-property name="scbcrseCrseNumb" type="string">
<column name="SCBCRSE_CRSE_NUMB" length="5" />
</key-property>
<key-property name="scbcrseEffTerm" type="string">
<column name="SCBCRSE_EFF_TERM" length="6" />
</key-property>
<key-property name="scbcrseCollCode" type="string">
<column name="SCBCRSE_COLL_CODE" length="2" />
</key-property>
<key-property name="scbcrseDivsCode" type="string">
<column name="SCBCRSE_DIVS_CODE" length="4" />
</key-property>
<key-property name="scbcrseDeptCode" type="string">
<column name="SCBCRSE_DEPT_CODE" length="4" />
</key-property>
</composite-id>
</class>
</hibernate-mapping>
I have table in oracle which has fields like this:
CREATE TABLE SATURN.SCBCRSE
(
SCBCRSE_SUBJ_CODE VARCHAR2(4 BYTE) NOT NULL,
SCBCRSE_CRSE_NUMB VARCHAR2(5 BYTE) NOT NULL,
SCBCRSE_EFF_TERM VARCHAR2(6 BYTE),
SCBCRSE_COLL_CODE VARCHAR2(2 BYTE),
SCBCRSE_DIVS_CODE VARCHAR2(4 BYTE),
SCBCRSE_DEPT_CODE VARCHAR2(4 BYTE)
)
CREATE UNIQUE INDEX SATURN.SCBCRSE_KEY_INDEX ON SATURN.SCBCRSE
(SCBCRSE_SUBJ_CODE, SCBCRSE_CRSE_NUMB, SCBCRSE_EFF_TERM)
And I have the reveng.xml as :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-reverse-engineering PUBLIC "-//Hibernate/Hibernate Reverse Engineering DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" >
<hibernate-reverse-engineering>
<schema-selection match-schema="SATURN" />
<type-mapping>
<sql-type jdbc-type="NUMERIC" precision="22" scale="0" hibernate-type="long" />
</type-mapping>
<table-filter match-name="SCBCRSE.*" />
</hibernate-reverse-engineering>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 4 months
[Hibernate-JIRA] Commented: (HHH-198) Websphere transaction management with Hibernate
by Andrei Iltchenko (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-198?page=co... ]
Andrei Iltchenko commented on HHH-198:
--------------------------------------
I am discovering this issue anew on WebSphere 6.0.2.9 and Hibernate 3.2.CR2, cf. <http://forum.hibernate.org/viewtopic.php?t=963579>.
> Websphere transaction management with Hibernate
> -----------------------------------------------
>
> Key: HHH-198
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-198
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.0 rc 1
> Environment: 1) Websphere Application developer 5.1.2 edition
> 2) Hibernate version: 2.1.6
> 3) Oracle 10g
> 4) Driver Oracle 10g XA thin driver (Managed Connection)
> Reporter: Cem Kayan
> Assignee: Gavin King
> Priority: Blocker
> Fix For: 3.0.1
> Attachments: HibernateWAS6.0.doc
>
>
> I'm trying to use Hibernate's transaction interface to lookup and use WebsphereTransactionManager.
> In my hibernate config files (at the moment i have two) ;
> i configured to initializeHibernateSessionFactories (both)
> there is a session facade calling a dao which are both SLSB's
> I'm using CMT
> SessionFacade : RequiresNew
> DAO: Mandatory
> during startup i have a HibernateException:
> (Could not obtain WebSphere JTSXA instance)
> Everthing else seems to be ok with my Wsad Server.
> for more details: http://forum.hibernate.org/viewtopic.php?t=935229&highlight=websphere
> I received following message from an IBM WAS Developers ;
> "The Hibernate code does not work on WebSphere Application Server 5.1.0.3 which you are running. It is using undocumented API and it is accessing the old 5.0 classes which are not present in 5.1 of WebSphere. It is trying to access a class JTSXA which does not exist in 5.1 You need to go back to the open source provider for a solution on this as this is not using the new classes in this undocumented internal api. "
> In Hibernate WebSphereTransactionManagerLookup class, there are three trials but in my case non of them is successfull.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months
[Hibernate-JIRA] Commented: (HHH-1740) Build-time instrumentation breaks lazy="proxy"
by Frank Grimes (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=c... ]
Frank Grimes commented on HHH-1740:
-----------------------------------
The ant changes made the failure more deterministic.... when run individually, the javassist and cglib instrument tests run fine.
When run together as part of the main test suite, org.hsqldb.persist.NIOLockFile errors occur on the second one that is run.
Switching HSQLDB to in-memory mode (in hibernate.properties) gets rid of the error.
> Build-time instrumentation breaks lazy="proxy"
> ----------------------------------------------
>
> Key: HHH-1740
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2
> Reporter: Frank Grimes
> Assignee: Steve Ebersole
> Priority: Critical
> Fix For: 3.2.0.ga
> Attachments: 312Document.class, Document.class, HHH-1740.diff, Hibernate3-Branch_3_2.diff, TestLazyManyToOne-Branch_3_2.diff
>
>
> I have a mapping that contains a many-to-one lazy="proxy".
> This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load
> Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks.
> Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object)
> This works fine in hibernate-3.1.2.
> This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881
> Please let me know if more info or a test case is needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months
[Hibernate-JIRA] Commented: (HHH-1740) Build-time instrumentation breaks lazy="proxy"
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=c... ]
Steve Ebersole commented on HHH-1740:
-------------------------------------
I've got a pretty expanded test case here locally, but thanks.
Also, so then did the ant changes I just committed today work for you? Specifically I defined the instrument tests to not spawn seperate threads...
> Build-time instrumentation breaks lazy="proxy"
> ----------------------------------------------
>
> Key: HHH-1740
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2
> Reporter: Frank Grimes
> Assignee: Steve Ebersole
> Priority: Critical
> Fix For: 3.2.0.ga
> Attachments: 312Document.class, Document.class, HHH-1740.diff, Hibernate3-Branch_3_2.diff, TestLazyManyToOne-Branch_3_2.diff
>
>
> I have a mapping that contains a many-to-one lazy="proxy".
> This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load
> Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks.
> Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object)
> This works fine in hibernate-3.1.2.
> This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881
> Please let me know if more info or a test case is needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months
[Hibernate-JIRA] Commented: (ANN-382) Exception raising : Strange behaviour depending on package names
by Emmanuel Bernard (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-382?page=co... ]
Emmanuel Bernard commented on ANN-382:
--------------------------------------
This is due to the fact that your PK is a ManytoOne to an entity itself having a PK made of a ManyToOne
> Exception raising : Strange behaviour depending on package names
> ----------------------------------------------------------------
>
> Key: ANN-382
> URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-382
> Project: Hibernate Annotations
> Type: Bug
> Environment: Hibernate's annotations packaged in JBoss EJB 3.0 RC8- FD
> Microsoft SQL Server 2000
> Reporter: Pierre Fourès
> Assignee: Emmanuel Bernard
> Fix For: 3.2.0
> Attachments: BugEJB3.zip
>
>
> As described in hibernate forum (http://forum.hibernate.org/viewtopic.php?t=960763) and discussed with Emmanuel, I encounter a strange behaviour with annotations depending of my package's names.
> Supposing hibernate load classes by package alphabetical order; if it get the "parent" class first all works fine, if it get the "child" class first, it raise an exception !
> Here is a subset of my classes, cleaned of getters, setters and all unrelated things, then followed by the exception stack :
> ///////////////////////////////////////////////
> package fr.ifis.entity.field.card;
> import java.io.Serializable;
> import javax.persistence.Embeddable;
> import javax.persistence.Entity;
> import javax.persistence.Id;
> import javax.persistence.ManyToOne;
> import fr.ifis.entity.project.Card;
> @Entity
> public class CardField {
> @Id
> private PrimaryKey primaryKey = new PrimaryKey();
>
> // cardtmp is a trick used in order to wait for http://opensource.atlassian.com/projects/hibernate/browse/ANN-381 resolution
> @ManyToOne
> private Card cardtmp;
> @Embeddable
> private class PrimaryKey implements Serializable {
>
> @ManyToOne(optional = false)
> private Card card;
>
> @ManyToOne(optional = false)
> private CardKey key;
> }
> }
> ///////////////////////////////////////////////
> package fr.ifis.entity.field.card;
> import javax.persistence.Entity;
> import javax.persistence.GeneratedValue;
> import javax.persistence.Id;
> @Entity
> public class CardKey {
> @Id
> @GeneratedValue
> private int id;
> }
> ///////////////////////////////////////////////
> package fr.ifis.entity.project;
> import java.io.Serializable;
> import java.util.Set;
> import javax.persistence.CascadeType;
> import javax.persistence.Embeddable;
> import javax.persistence.Entity;
> import javax.persistence.FetchType;
> import javax.persistence.Id;
> import javax.persistence.ManyToOne;
> import javax.persistence.OneToMany;
> import fr.ifis.entity.field.card.CardField;
> @Entity
> public class Card {
> @Id
> private CardPrimaryKey primaryKey = new CardPrimaryKey();
>
> @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER, mappedBy="cardtmp") //
> private Set<CardField> fields;
>
> @Embeddable
> private class CardPrimaryKey implements Serializable {
>
> @ManyToOne(optional = false)
> private Project project;
>
> //An other @ManyToOne is also present in the real model
> //The problem still occurs even when i remove this relation, it was no use to kept it for describe the problem
> }
> }
> ///////////////////////////////////////////////
> package fr.ifis.entity.project;
> import javax.persistence.Entity;
> import javax.persistence.GeneratedValue;
> import javax.persistence.Id;
> @Entity
> public class Project {
> @Id
> @GeneratedValue
> private int id;
> }
> ///////////////////////////////////////////////
> [java] ERROR 29-06 19:42:18,272 (AbstractController.java:incrementState:350) -Error installing to Start: name=persistence.units:unitName=Refonte state=Create
> [java] org.hibernate.MappingException: Foreign key (FK6771BFAA1845E8B:CardField [])) must have same number of columns as the referenced primary key (Card [project_id])
> [java] at org.hibernate.mapping.ForeignKey.alignColumns(ForeignKey.java:90)
> [java] at org.hibernate.mapping.ForeignKey.alignColumns(ForeignKey.java:73)
> [java] at org.hibernate.cfg.Configuration.secondPassCompileForeignKeys(Configuration.java:1182)
> [java] at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1089)
> [java] at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:302)
> [java] at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1034)
> [java] at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1015)
> [java] at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:154)
> [java] at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:751)
> [java] at org.hibernate.ejb.Ejb3Configuration.createContainerEntityManagerFactory(Ejb3Configuration.java:350)
> [java] at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:119)
> [java] at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:264)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> [java] at java.lang.reflect.Method.invoke(Method.java:585)
> [java] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
> [java] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:107)
> [java] at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> [java] at org.jboss.kernel.plugins.dependency.KernelControllerContextActions.dispatchJoinPoint(KernelControllerContextActions.java:100)
> [java] at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$LifecycleAction.installAction(KernelControllerContextActions.java:582)
> [java] at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextActions.java:175)
> [java] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> [java] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
> [java] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)
> [java] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)
> [java] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)
> [java] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)
> [java] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225)
> [java] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151)
> [java] at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:79)
> [java] at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:73)
> [java] at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:91)
> [java] at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:626)
> [java] at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:475)
> [java] at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.start(EJB3StandaloneDeployer.java:460)
> [java] at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:291)
> [java] at fr.ifis.Main.main(Unknown Source)
> ///////////////////////////////////////////////
> Indeed, depending on the package names I get or not an excpetion !
> It doesn't work with the package fr.ifis.entity.project but if I rename the package in fr.ifis.entity.aproject and then move it "before" the field.card package, all works fine.
> In order to facilitate the identification of the problem, I also include as attachement the eclipse project of this problem repport.
> In order to keep reasonable the size of the attachement, I did not included the libraries nor the configuration files for launch ejb3-embedded. Thoses files are issued from the project simple-deployment included in JBoss EJB 3.0 RC8-FD. The only change i've done was to specify in embedded-jboss-beans.xml the properties of my database.
> Regards,
> Pierre.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months
[Hibernate-JIRA] Commented: (ANN-382) Exception raising : Strange behaviour depending on package names
by Emmanuel Bernard (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-382?page=co... ]
Emmanuel Bernard commented on ANN-382:
--------------------------------------
This is a quite complex graph resolution issue. Basically Hibernate Annotations does not try to reorder FK creation depending on graph dependencies (it actually does but only for the first order). Solving that is quite complex, but the easiest workaround is to use excplicit class declaration in the persistence.xml file (and possibly disable class autodiscovery).
> Exception raising : Strange behaviour depending on package names
> ----------------------------------------------------------------
>
> Key: ANN-382
> URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-382
> Project: Hibernate Annotations
> Type: Bug
> Environment: Hibernate's annotations packaged in JBoss EJB 3.0 RC8- FD
> Microsoft SQL Server 2000
> Reporter: Pierre Fourès
> Assignee: Emmanuel Bernard
> Fix For: 3.2.0
> Attachments: BugEJB3.zip
>
>
> As described in hibernate forum (http://forum.hibernate.org/viewtopic.php?t=960763) and discussed with Emmanuel, I encounter a strange behaviour with annotations depending of my package's names.
> Supposing hibernate load classes by package alphabetical order; if it get the "parent" class first all works fine, if it get the "child" class first, it raise an exception !
> Here is a subset of my classes, cleaned of getters, setters and all unrelated things, then followed by the exception stack :
> ///////////////////////////////////////////////
> package fr.ifis.entity.field.card;
> import java.io.Serializable;
> import javax.persistence.Embeddable;
> import javax.persistence.Entity;
> import javax.persistence.Id;
> import javax.persistence.ManyToOne;
> import fr.ifis.entity.project.Card;
> @Entity
> public class CardField {
> @Id
> private PrimaryKey primaryKey = new PrimaryKey();
>
> // cardtmp is a trick used in order to wait for http://opensource.atlassian.com/projects/hibernate/browse/ANN-381 resolution
> @ManyToOne
> private Card cardtmp;
> @Embeddable
> private class PrimaryKey implements Serializable {
>
> @ManyToOne(optional = false)
> private Card card;
>
> @ManyToOne(optional = false)
> private CardKey key;
> }
> }
> ///////////////////////////////////////////////
> package fr.ifis.entity.field.card;
> import javax.persistence.Entity;
> import javax.persistence.GeneratedValue;
> import javax.persistence.Id;
> @Entity
> public class CardKey {
> @Id
> @GeneratedValue
> private int id;
> }
> ///////////////////////////////////////////////
> package fr.ifis.entity.project;
> import java.io.Serializable;
> import java.util.Set;
> import javax.persistence.CascadeType;
> import javax.persistence.Embeddable;
> import javax.persistence.Entity;
> import javax.persistence.FetchType;
> import javax.persistence.Id;
> import javax.persistence.ManyToOne;
> import javax.persistence.OneToMany;
> import fr.ifis.entity.field.card.CardField;
> @Entity
> public class Card {
> @Id
> private CardPrimaryKey primaryKey = new CardPrimaryKey();
>
> @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER, mappedBy="cardtmp") //
> private Set<CardField> fields;
>
> @Embeddable
> private class CardPrimaryKey implements Serializable {
>
> @ManyToOne(optional = false)
> private Project project;
>
> //An other @ManyToOne is also present in the real model
> //The problem still occurs even when i remove this relation, it was no use to kept it for describe the problem
> }
> }
> ///////////////////////////////////////////////
> package fr.ifis.entity.project;
> import javax.persistence.Entity;
> import javax.persistence.GeneratedValue;
> import javax.persistence.Id;
> @Entity
> public class Project {
> @Id
> @GeneratedValue
> private int id;
> }
> ///////////////////////////////////////////////
> [java] ERROR 29-06 19:42:18,272 (AbstractController.java:incrementState:350) -Error installing to Start: name=persistence.units:unitName=Refonte state=Create
> [java] org.hibernate.MappingException: Foreign key (FK6771BFAA1845E8B:CardField [])) must have same number of columns as the referenced primary key (Card [project_id])
> [java] at org.hibernate.mapping.ForeignKey.alignColumns(ForeignKey.java:90)
> [java] at org.hibernate.mapping.ForeignKey.alignColumns(ForeignKey.java:73)
> [java] at org.hibernate.cfg.Configuration.secondPassCompileForeignKeys(Configuration.java:1182)
> [java] at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1089)
> [java] at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:302)
> [java] at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1034)
> [java] at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1015)
> [java] at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:154)
> [java] at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:751)
> [java] at org.hibernate.ejb.Ejb3Configuration.createContainerEntityManagerFactory(Ejb3Configuration.java:350)
> [java] at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:119)
> [java] at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:264)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> [java] at java.lang.reflect.Method.invoke(Method.java:585)
> [java] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
> [java] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:107)
> [java] at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> [java] at org.jboss.kernel.plugins.dependency.KernelControllerContextActions.dispatchJoinPoint(KernelControllerContextActions.java:100)
> [java] at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$LifecycleAction.installAction(KernelControllerContextActions.java:582)
> [java] at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextActions.java:175)
> [java] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> [java] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
> [java] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)
> [java] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)
> [java] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)
> [java] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)
> [java] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225)
> [java] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151)
> [java] at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:79)
> [java] at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:73)
> [java] at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:91)
> [java] at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:626)
> [java] at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:475)
> [java] at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.start(EJB3StandaloneDeployer.java:460)
> [java] at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:291)
> [java] at fr.ifis.Main.main(Unknown Source)
> ///////////////////////////////////////////////
> Indeed, depending on the package names I get or not an excpetion !
> It doesn't work with the package fr.ifis.entity.project but if I rename the package in fr.ifis.entity.aproject and then move it "before" the field.card package, all works fine.
> In order to facilitate the identification of the problem, I also include as attachement the eclipse project of this problem repport.
> In order to keep reasonable the size of the attachement, I did not included the libraries nor the configuration files for launch ejb3-embedded. Thoses files are issued from the project simple-deployment included in JBoss EJB 3.0 RC8-FD. The only change i've done was to specify in embedded-jboss-beans.xml the properties of my database.
> Regards,
> Pierre.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
18 years, 5 months