[ http://jira.jboss.com/jira/browse/JBAS-4679?page=all ] Carlo de Wolf updated JBAS-4679: -------------------------------- JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4071148 -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4679?page=all ] Thomas Diesler resolved JBAS-4679. ---------------------------------- Resolution: Done -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4679?page=all ] Thomas Diesler resolved JBAS-4679. ---------------------------------- Resolution: Done Starting with jbossws-2.0.1 all integration concerns only have a dependency on jbossws-spi.jar. This is a separate binary but might as well become part of jboss-integration.jar The AS5 specific implementation of that SPI, which includes the EJB3 integration has been moved to the jboss code base. It currently lives in the webservice module. EJB3 specific integration might as well become part of the EJB3 module, which would become relevant once EJB3 becomes a standalone project. Hence, EJB3 cannot change implementation details without modifying the relevant WS integration points in the webservice module. It might be necessary to modify SPI details for Beta3. If so , these change requests should become individual jira issues. -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4679?page=comments#action_12377975 ] Heiko Braun commented on JBAS-4679: ----------------------------------- There is a couple of interconnection points between WS and EJB3: - InvocationHandling - Resource injection - HandlerCallbacks - DeploymentHooks and MetaData Most of them are bi-directional dependencies, on the WS side we cover them through an SPI, that decouples the container integration from the stack. However on the container side we still do heavily rely EJB3 internals. Carlo and I did agree on the need for an EJB3 SPI that clearly addresses the issues above and further decouples both projects. In order to proceed I suggest: * WS Team provides a paper that clearly points out the interconnection points * EJB3 Team provides an SPI based on these requirements -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4679?page=all ] Heiko Braun reassigned JBAS-4679: --------------------------------- Assignee: Carlo de Wolf (was: Heiko Braun) The first draft of the docs is online. Please provide some feedback which allows us to derive action items from it. -- 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