JBoss AS 4.2.3 to 5.1 upgrade Dependancy issue

[flesner]

i'm upgrading an application from 4.2.3 to 5.1. it's contained in a SAR and in the process i'm upgrading some of the EJB to annotations to resolve the startup dependencies. i get the following error on startup:

DEPLOYMENTS MISSING DEPENDENCIES:
  Deployment "jboss.j2ee:ear=m2g.sar,jar=m2g-db-0.5.jar,name=AdminDAO,service=EJB3_endpoint" is missing the following dependencies:
    Dependency "jboss.j2ee:ear=m2g.sar,jar=m2g-db-0.5.jar,name=AdminDAO,service=EJB3" (should be in state "Configured", but is actually in state "** NOT FOUND Depends on 'jboss.j2ee:ear=m2g.sar,jar=m2g-db-0.5.jar,name=AdminDAO,service=EJB3' **")

when i look in the jmx-console, the EJB is deployed, but it's deployed under a slightly different name (without the "ear=m2g.sar") as:

id="jboss.j2ee:jar=m2g-db-0.5.jar,name=AdminDAO,service=EJB3",type=Component

it won't start because it's waiting for the other named service?

any ideas why  the discrepancy in the actual name and the dependency name?

[wdfink]

ATM it is not very clear to me what you try to deploy.

Is it the same as with 4.2.3 works? Or what you have changed?

Please post the structure of deployed file.

[flesner]

this part actually worked int 4.2.3, but the file structure has changed. in 4.2.3 the jar files were in the "lib" subdirectory, but in 5.1 that isn't automatically picked up in the classpath? the current file structure is:

m2g.sar/

     m2g-db-0.5.jar

     m2g-db-0.5.war

4.2.3 it was:

m2g.sar/

     m2g-db-0.5.war

     lib/

          m2g-db-0.5.jar

[jaikiran]

Why are you deploying it as a .sar with a .war and .jar inside it? Why not deploy it as a .ear?

[flesner]

for legacy reasons.

[jaikiran]

Try deploying it via a .ear instead of .sar. I don't really know that deploying EJBs from within a .sar in AS5 is really tested or supported.