DEPLOYMENT FAILED

[hmougy]

I got everything right with session beans but when i try to add entity i got no success because of unit name or connecting to database i think,

i tried to choose diffrent names it works well with ant , but with IDEs it
shows this deployment fail message






--- MBeans waiting for other MBeans ---
ObjectName: persistence.units:jar=titan.jar,unitName=titan
State: FAILED
Reason: org.hibernate.AnnotationException: No identifier specified for entity: com.titan.domain.Cabin
I Depend On:
jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
Depends On Me:
jboss.j2ee:jar=titan.jar,name=TravelAgentBean,service=EJB3

ObjectName: jboss.j2ee:jar=titan.jar,name=TravelAgentBean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
persistence.units:jar=titan.jar,unitName=titan

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: persistence.units:jar=titan.jar,unitName=titan
State: FAILED
Reason: org.hibernate.AnnotationException: No identifier specified for entity: com.titan.domain.Cabin
I Depend On:
jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
Depends On Me:
jboss.j2ee:jar=titan.jar,name=TravelAgentBean,service=EJB3

[jimmymani]

hope you got the reply already(Questionposted on june/06).

its failing because there is no @Id annotation for atleast one field.

because every entity must have a primary key.
it can be either simple or composite

[floechen]

I have the same problem (using EJB 3.0 RC9), but after a series of tests I found the source: I defined my identifier within an abstract superclass, and the EJB 3 deployer didn't recognize it, leading to the throwing of the exception mentioned in the previous post.

Is this a bug (which must be reported) or is a feature of the J2EE 5 spec?