[
https://issues.apache.org/activemq/browse/CAMEL-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54709#action_54709
]
Willem Jiang commented on CAMEL-916:
------------------------------------
I'd like to close this issue, as the camel-servlet component support to use the
HttpService
Here is a helper activator[1] to do registrer work.
[1]https://svn.apache.org/repos/asf/camel/trunk/tests/camel-itest-osgi/src/test/java/org/apache/camel/itest/osgi/servlet/support/ServletActivator.java
> Create a new component that uses the OSGi HttpService to accomplish what
> came-jetty currently does
> --------------------------------------------------------------------------------------------------
>
> Key: CAMEL-916
> URL: https://issues.apache.org/activemq/browse/CAMEL-916
> Project: Apache Camel
> Issue Type: New Feature
> Affects Versions: 1.4.0
> Reporter: Michael Murphree
> Fix For: 2.1.0
>
>
> The current camel-jetty component starts up a new Jetty server instance to
> host listeners for producing endpoints. It would be nice if, in an OSGi
> environment, there were a component that uses the OSGi HttpService to create
> a producing endpoint instead.
> One of the restrictions over this component would be that the end user would
> not be able to configure the port number in the URI as the HttpService uses
> the system property org.osgi.services.http.port to determine the port setting.
> Use case:
> I should be able to configure a route in a manner similar to camel-jetty:
> ...
> from("osgi-http:localhost:8192/services/myservice").
> .to(...)
> ...
> The host name (or address) and port number would necessarily be ignored.
> See
> http://www.nabble.com/Proxying-web-services-tt19498936s22882.html#a19536118
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
