[
https://issues.apache.org/jira/browse/CXF-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673894#comment-15673894
]
Benson Margulies edited comment on CXF-7141 at 11/17/16 2:45 PM:
-----------------------------------------------------------------
I don't mind if you keep the extra property so long as you fix the non-dynamic
import :-).
I am currently in the middle of trying to make something work that has only the
CXF non-servet (http-jetty) transport in OSGi.
was (Author: bmargulies):
I don't mind if you keep the extra property so long as you fix the non-dynamic
import :-).
I am currently in the middle of trying to make something work that has only the
CXF non-servet (http-jetty) transport in OSGi. I think that I should be leaving
the plain http transport of the deployment altogether, but I ran into wiring
errors looking for HttpService in one of my intermediate states.
> 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)
