You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <tu...@ws.apache.org> on 2006/05/08 11:37:22 UTC

[jira] Closed: (TUSCANY-63) Need an SPI for co-ordination between EntryPoints and the infrastructure that will invoke them

     [ http://issues.apache.org/jira/browse/TUSCANY-63?page=all ]
     
ant elder closed TUSCANY-63:
----------------------------


> 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
>     Versions: M1
>     Reporter: Jeremy Boynes
>     Assignee: ant elder
>     Priority: Blocker
>      Fix For: M1

>
> 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