[kryptontri]

Ok ignore the number 69 suffixed after every iplay word, i missed editing/search/replacing before posting!

[bill.burke]

Ok, now deploy the datasource outside of the EAR. I forgot to mention that...I still don't know why the dependency error happens :(

Really what it looks like is that the jndi name you provide in your *-ds.xml file does not match the jndi name you provided in your persistence.xml. Can you double, triple check this?

[kryptontri]

Hi Bill, thanks for the advice, what i found, which didn't appear in the logs before, was 1 of my ejbs had some wrong annotations, this could be showing now because i changed the jndi name to something simpler to match the ds and persistence.xml

Caused by: org.hibernate.AnnotationException: No identifier specified for entity:

Anyway, i fixed the ejb and it all deploys works.

Can i remove this from persistence.xml ?

<property name="jboss.no.implicit.datasource.dependency" value="true"/>

BTW Thanks for helping me pinpoint this error. Its User/My error.

[bill.burke]

yes, you should be able to remove:

BTW, please log a bug on Hibernate EntityManager JIRA. This is a usability bug as you had no intelligible message from the deployer on what went wrong.

[epbernard]

Bill, what intelligible error?

I raise org.hibernate.AnnotationException: No identifier specified for entity:

How happens that this exception was swallowed before?
I don't really understand what went wrong before.

[rezebric]

See this bit:

13:32:13,217 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: persistence.units:ear=cms.ear.ear,jar=cms-ejb.jar.jar,unitName=iplaycmsEntityManager
 State: NOTYETINSTALLED
 I Depend On:
 jboss.jca:name=iplaycmsDatasource,service=ManagedConnectionFactory
 Depends On Me:
 jboss.j2ee:service=EJB3,ear=cms.ear,jar=cms-ejb.jar,name=ChangePasswordAction
 jboss.j2ee:service=EJB3,ear=cms.ear,jar=cms-ejb.jar,name=LoginAction
 jboss.j2ee:service=EJB3,ear=cms.ear,jar=cms-ejb.jar,name=RegisterAction

ObjectName: jboss.j2ee:service=EJB3,ear=cms.ear,jar=cms-ejb.jar,name=ChangePasswordAction
 State: NOTYETINSTALLED
 I Depend On:
 persistence.units:ear=cms.ear.ear,jar=cms-ejb.jar.jar,unitName=iplaycmsEntityManager

ObjectName: jboss.j2ee:service=EJB3,ear=cms.ear,jar=cms-ejb.jar,name=LoginAction
 State: NOTYETINSTALLED
 I Depend On:
 persistence.units:ear=cms.ear.ear,jar=cms-ejb.jar.jar,unitName=iplaycmsEntityManager

ObjectName: jboss.j2ee:service=EJB3,ear=cms.ear,jar=cms-ejb.jar,name=RegisterAction
 State: NOTYETINSTALLED
 I Depend On:
 persistence.units:ear=cms.ear.ear,jar=cms-ejb.jar.jar,unitName=iplaycmsEntityManager

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:name=iplaycmsDatasource,service=ManagedConnectionFactory
 State: NOTYETINSTALLED
 Depends On Me:
 persistence.units:ear=cms.ear.ear,jar=cms-ejb.jar.jar,unitName=iplaycmsEntityManager

It is important. It is telling you why the EJBs cannot start.

But why is this happening? And what we must do to solve it?

[gavin.king]

"rezebric" wrote:

But why is this happening? And what we must do to solve it?

This is a JBoss question, and nothing to do with Seam. (And no, I'm not the right guy to help with this stuff.)