Referencing camel endpoint defined in the ‘blueprint’ XML does not appears to work

In previous camel projects (deployed to Tomcat) I used the to define endpoints and reference these from Routes in DSL. I am now experimenting with karaf & Fuse and using the ‘blueprint’ XML file with ‘camel:endpoint’ does not appear to work. The XMLs at the end of this message show the bluepri

Re: Referencing camel endpoint defined in the 'blueprint' XML does not appears to work

Works fine now. Thanks for that -- View this message in context: http://camel.465427.n5.nabble.com/Referencing-camel-endpoint-defined-in-the-blueprint-XML-does-not-appears-to-work-tp5749850p5749855.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Referencing camel endpoint defined in the 'blueprint' XML does not appears to work

Just a note on adding Java DSL, I had to place the before the endpoint definition to get it to work. It will be good if the camel page 'using-osgi-blueprint-with-camel' will highlight the differences between 'blueprint' XML and 'spring' XML (currently it suggests similarity). -- View this mess

How to chain together request-reply with sends in a synchronous way?

I have a requirement to perform the following steps: 1. Receive an HTTP POST with a list of parameters 2. Reply immediately with an empty body and HTTP 200 3. Send HTTP POST message to endpoint-1 with content based on the parameters received in step 1 4. Process the response

CXFRS Component - setting providers for version 2.10.4

We are using Camel 2.10.4 (constrains due to our existing run-time) Is there a way to set the jaxrs:providers on the CXFRS Component for this version? We want to secure the component with HTTP Basic Authentication by specifying the following filter as a provider using the following:

Re: CXFRS Component - setting providers for version 2.10.4

I tried with no success... The schema element type for providers is xsd:anyType What is the correct syntax? -- View this message in context: http://camel.465427.n5.nabble.com/CXFRS-Component

Re: CXFRS Component - setting providers for version 2.10.4

The option jaxrs:server/@address="camel://myEndpoint" appear to be feasible but I haven't tried it. As a short term solution , we ended up using a Spring based application (already secured with HTTP Basic...) as a proxy Long term we intend to move to the fabric8 run-time with a more recent Camel ve

Camel CXF and Weblogic

Our main integration system is Oracle based and runs on Weblogic, we have other Java based system utilizing JBoss and Tomcat/Spring. I find Camel as an appealing light weight integration solution that we could use to supplement our other integration systems and preferably use across different platf

Polling Consumer invoking multiple requests.

We have a requirement to implement a polling consumer that periodically checks for messages (via Web Service or RMI requests). In this case the polling consumer expects to invoke multiple requests until all messages have been read without waiting for the next polling (there is a ‘No More Messages’

Re: Polling Consumer invoking multiple requests.

Thanks for the tip, RoutePolicy or controlling the route from the CamelContext could do the trick. The problem that we need to solve is still in a feasibility stage but since we have the ability to define the interface I am inclined to suggest that the message producer will include all pending mess

CXF SOAP Message Sent from a Camel Client Twice When No HTTP Response Received

We came across the following issue when using the Camel CXF component to invoke a SOAP request with Payload mode over HTTPS on a third party service. The third party server provides two endpoints primary and secondary. As part of certifying our system with this service (fail over test), we were r

Re: CXF SOAP Message Sent from a Camel Client Twice When No HTTP Response Received

It took us a few day to respond as the third party server was down. Anyway after adding logging to the project we still couldn't find any obvious trace for sending the message twice. As mentioned soapUI client and the same camel project with HttpClient library don't exhibit the same issue which is