[ http://issues.apache.org/jira/browse/TUSCANY-63?page=comments#action_12368825 ]
Jim Marino commented on TUSCANY-63: ----------------------------------- Can we have the builder set this up, perhaps through the builder registry? I was also thinking it may be useful if the Axis engine was somehow a component and we have it register as a transport in the runtime. There would be some kind of eventing mechanism where the builder passes a reference to the entry point context which when created sends a request to that reference for a transport address, etc., to be created. Normally, I would like the builder to do all of this, but we have to be careful that the transport is not notified prior to the entry point context being created. > Need an SPI for co-ordination between EntryPoints and the infrastructure that > will invoke them > ---------------------------------------------------------------------------------------------- > > Key: TUSCANY-63 > URL: http://issues.apache.org/jira/browse/TUSCANY-63 > Project: Tuscany > Type: Bug > Components: Java SCA Core > Reporter: Jeremy Boynes > > In order to get the Tomcat integration code to create servlets for > web-services bound entry points it needed to know implementation details of > the binding. This will not allow integrators to freely embed Tuscany in > different environments or binding providers to contribute new bindings > without knowing something about those environments. > I would suggest that we define an SPI implemented by environment integrators > that will allow entry point implementations to request creation of transport > endpoints. So, taking the example of Axis2 and Tomcat, the Axis2 binding > would request a transport binding from the environment and which would be > activated when the EP started. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
