[
https://issues.apache.org/jira/browse/CXF-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673886#comment-15673886
]
Sergey Beryozkin edited comment on CXF-7141 at 11/17/16 2:41 PM:
-----------------------------------------------------------------
Benson, DISABLE_DEFAULT_HTTP_TRANSPORT is there for CXF Http Osgi Transport,
for Servlet based deployments to work without default CXF HTTP transport
interfering, ex, CXFBlueprintServlet. There were also other side-effects with
the users doing their own OSGI CXF integration and a "/cxf" servlet
interfering.
In other words, even of OSGI HttpService is available, CXF users should still
be able to tell CXF not to use a default transport. So lets keep it. Thanks
was (Author: sergey_beryozkin):
Benson, DISABLE_DEFAULT_HTTP_TRANSPORT is there for CXF Http Osgi Transport,
for Servlet based deployments to work without default CXF HTTP transport
interfering, ex, CXFBlueprintServlet. There were also other side-effects with
the users doing their own OSGI CXF integration and a "/cxf" servlet
interfering, so lets keep it. Thanks
> cxf-rt-transports-http incorrectly requires org.osgi.http.service
> -----------------------------------------------------------------
>
> Key: CXF-7141
> URL: https://issues.apache.org/jira/browse/CXF-7141
> Project: CXF
> Issue Type: Bug
> Affects Versions: 3.1.4
> Reporter: Benson Margulies
>
> org.apache.cxf.transport.http.osgi.HTTPTransportActivator optionally touches
> the HTTP service, but imports org.osgi.service.http unconditionally. I think
> it should be a dynamic import, and DISABLE_DEFAULT_HTTP_TRANSPORT should be
> replaced by reacting to the presence or absence of the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
