Jetty endpoints not accessable by http gateway
Issue
- Jetty endpoints are not accessable by http gateway. Benefit of using jetty component is that it is a basic http endpoint which is easy and fast to configure.
- But problem is jetty endpoint is not getting registered within zookeeper registry while cxf based endpoint are registered.
- Below are the steps to reproduce scenario
- In a clean
Fuse 6.2.0fabric, do - Create new profile
- Add file to profile with name camel-blueprint.xml with the below content.
- Under "Deployments" on the profile's page, add:
blueprint:profile:camel-blueprint.xml. - Add "jboss-fuse-minimal" as parent profile.
- Create new child container with the new profile assigned to it.
- After the container has started, in the
Hawtioconsole browse toServices,Registryand notice that the jetty endpoint is not registered, and hence ignored by thehttp gateway.
- In a clean
<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://www.osgi.org/xmlns/blueprint/v1.0.0
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd">
<camelContext xmlns="http://camel.apache.org/schema/blueprint">
<route id="myRoute">
<from uri="jetty:http://0.0.0.0:7171/prototype"/>
<setBody>
<simple>Hello from Camel route</simple>
</setBody>
<log message="Received payload: ${body}"/>
</route>
</camelContext>
</blueprint>
Environment
- Red Hat JBoss Fuse
- 6.3.0
- 6.2.0
- 6.1.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
