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

Posted to issues@cxf.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2011/04/20 15:41:09 UTC

[jira] [Commented] (CXF-3384) Create one http transport that is always present and delegates to the actual http transport

    [ https://issues.apache.org/jira/browse/CXF-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022123#comment-13022123 ] 

Glen Mazza commented on CXF-3384:
---------------------------------

How do you determine if the "url contains a server name" in order to use Jetty?  What is the algorithm for determining whether an OSGi environment is in use?  Might it be better to add an additional element explicitly specifying whether jetty, standalone servlet container, or OSGi is intended for the particular configuration?

> Create one http transport that is always present and delegates to the actual http transport
> -------------------------------------------------------------------------------------------
>
>                 Key: CXF-3384
>                 URL: https://issues.apache.org/jira/browse/CXF-3384
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 2.4
>
>
> Problem:
> Currently we have three server side http transports: Servlet, Jetty and Osgi. They each register for the same transport URIs. So only one of them may be present at a time. So it is necessary for usersto import a special spring context like cxf-servlet.xml for each transport. 
> Additionally it is difficult to for example test with jetty and run with servlet in production using the same code. It is also not possible to publish some services using a servlet and others using a sperate port using jetty.
> Solution:
> So to make things easier and more flexible we should register a delegating http transport that analyzes the endpoint url and delegates to the correct transport factory. So if the url contains a server name then jetty should be used. If not then the servlet transport should be used. Optionally an OSGi environment should also be detected and then the OSGi servlet transport should be used instead of the normal servlet transport
>  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira