[ http://jira.nuxeo.org/browse/NUXEO-49?page=all ]
Eric Barroca updated NUXEO-49:
------------------------------
Summary: cannot use other extensions than .ear for nuxeo ear deployment
(was: cannot use other extensions than .era for nuxeo ear deployment)
> cannot use other extensions than .ear for nuxeo ear deployment
> --------------------------------------------------------------
>
> Key: NUXEO-49
> URL: http://jira.nuxeo.org/browse/NUXEO-49
> Project: Nuxeo 5
> Issue Type: Bug
> Security Level: External(All people)
> Reporter: Bogdan Stefanescu
> Assigned To: Bogdan Stefanescu
> Priority: Critical
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> This is due to an inconsistency between webservices and ejb3 in jboss
> Problem description:
> web service manager generate for each webservice a key of the form:
> jboss.ws:di=nuxeo.ear/nuxeo.jar,port=FileManageInterfacePort,service=FileManageService
> and try to find a mbean named:
> jboss.j2ee:ear=nuxeo.ear,jar=nuxeo.jar,name=FileManageWS,service=EJB3
> This mbean is registered by ejb3 deployer
> When using nuxeo.ear as EAR name it is ok.
> If I change nuxeo.ear to nuxeo.nxp the web service manager try to find:
> jboss.j2ee:ear=nuxeo.nxp,jar=nuxeo.jar,name=FileManageWS,service=EJB3
> which seems the normal behavior
> but the EJB3 deployer is creating a mbean having as name:
> jboss.j2ee:jar=nuxeo.jar,name=FileManageWS,service=EJB3
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
