You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "willem Jiang (JIRA)" <ji...@apache.org> on 2007/03/12 08:10:09 UTC

[jira] Resolved: (CXF-342) Servlet transport should be independent of the JAX-WS frontend

     [ https://issues.apache.org/jira/browse/CXF-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

willem Jiang resolved CXF-342.
------------------------------

    Resolution: Fixed

> Servlet transport should be independent of the JAX-WS frontend
> --------------------------------------------------------------
>
>                 Key: CXF-342
>                 URL: https://issues.apache.org/jira/browse/CXF-342
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>            Reporter: Eoghan Glynn
>         Assigned To: willem Jiang
>
> The servlet transport is implemented as part of the JAX-WS frontend, but the only real dependency on JAX-WS is the hardcoding of the instantiation of org.apache.cxf.jaxws.EndpointImpl and the Endpoint.publish() call. 
> This should be done via reflection instead, with  the class to instantiate and the publish method configured in the cxf-servlet.xml.
> That way the servlet transport could be used with any front-end (as opposed to be being limited to JAX-WS) and the code could be moved out of the rt-frontend-jaxws module and into the rt-transpots-http module.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.