[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1829) EJB3 Endpoint deployer picks up EJB2.x deployments and results in deployment dependency failures

jaikiran pai (JIRA) jira-events at lists.jboss.org
Mon May 11 10:25:59 EDT 2009


     [ https://jira.jboss.org/jira/browse/EJBTHREE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai resolved EJBTHREE-1829.
------------------------------------

                  Resolution: Done
    Component Fix Version(s): jboss-ejb3-endpoint-deployer:0.1.2


> EJB3 Endpoint deployer picks up EJB2.x deployments and results in deployment dependency failures
> ------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1829
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1829
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: endpoint-deployers
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>            Priority: Blocker
>
> TCK showed failures related to EJB deployments where the endpoint-deployer picked up EJB2.x deployments resulting in incorrect deployment dependencies being created. 
> DEPLOYMENTS MISSING DEPENDENCIES:
>   Deployment "jboss.j2ee:jar=xxx_statelessclient_ejb.jar,name=StatefulDefaultLocalBean,service=EJB3_endpoint" is missing the following dependencies:
>     Dependency "jboss.j2ee:jar=xxx_statelessclient_ejb.jar,name=StatefulDefaultLocalBean,service=EJB3" (should be in state "Configured", but is actually in state "** NOT FOUND Depends on 'jboss.j2ee:jar=xxx_statelessclient_ejb.jar,name=StatefulDefaultLocalBean,service=EJB3' **")

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list