[
http://jira.jboss.com/jira/browse/JBAS-5288?page=comments#action_12415129 ]
Dimitris Andreadis commented on JBAS-5288:
------------------------------------------
From the svn logs I can see that:
jboss-head/server/src/main/org/jboss/deployment/spi
is later than:
projects/integration/jboss-deployment-spi/src/main/java/org/jboss/deployment/spi
EndPointInfo has an additional:
public String getComponentKey()
{
return type + "/" + pathName + "#" + name;
}
And DeploymentEndpointResolver requires an additional/undocumented vfsContext parameter:
EndpointInfo getEndpointInfo(Class businessIntf, String endpointType, String
vfsContext);
...
EndpointInfo getEndpointInfo(String ref, String endpointType, String vfsContext);
I'll find out if we need to synch the integration deployment spi with the one in
JBossAS and then re-release the integration module, import it in AS and remove the
duplicate code.
Upgrade jboss-integration to 5.0.0.CR1
--------------------------------------
Key: JBAS-5288
URL:
http://jira.jboss.com/jira/browse/JBAS-5288
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Other
Reporter: Dimitris Andreadis
Assigned To: Dimitris Andreadis
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
Attachments: jbas5288_ejb3module.patch
I assume that the EJB3/WS spi will be moved to the jboss-integration project, and so a
new release will be needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira