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 blueprint that failed and the Spring XML that works. Notes I used the maven archetype blueprint and spring to generate the deployment jar I am mainly interested in implementing the routes using DSL and defining the ‘camel endpoint’ in the XML file. Any information on how to define camel endpoint using blueprint will be great. - blueprint http://www.osgi.org/xmlns/blueprint/v1.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:camel="http://camel.apache.org/schema/blueprint"; xsi:schemaLocation=" http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd http://camel.apache.org/schema/blueprint http://camel.apache.org/schema/blueprint/camel-blueprint.xsd";> http://camel.apache.org/schema/blueprint";> - Spring works OK http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:camel="http://camel.apache.org/schema/spring"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd";> http://camel.apache.org/schema/spring";> -- View this message in context: http://camel.465427.n5.nabble.com/Referencing-camel-endpoint-defined-in-the-blueprint-XML-does-not-appears-to-work-tp5749850.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
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 message in context: http://camel.465427.n5.nabble.com/Referencing-camel-endpoint-defined-in-the-blueprint-XML-does-not-appears-to-work-tp5749850p5749856.html Sent from the Camel - Users mailing list archive at Nabble.com.
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 from step 3 and invoke a web service with content based on the parameters from step 1 and the response from step 3 (endpoint-1 ) My understanding is that typically with default camel exchange the reply to the original request is sent at the end of the chain. Any suggestions? -- View this message in context: http://camel.465427.n5.nabble.com/How-to-chain-together-request-reply-with-sends-in-a-synchronous-way-tp5753195.html Sent from the Camel - Users mailing list archive at Nabble.com.
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: users = $[karaf.base]/etc/users.properties -- View this message in context: http://camel.465427.n5.nabble.com/CXFRS-Component-setting-providers-for-version-2-10-4-tp5754643.html Sent from the Camel - Users mailing list archive at Nabble.com.
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-setting-providers-for-version-2-10-4-tp5754643p5754703.html Sent from the Camel - Users mailing list archive at Nabble.com.
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 version. The correct XML under providers appears to be a bean definition... Cheers, Avi -- View this message in context: http://camel.465427.n5.nabble.com/CXFRS-Component-setting-providers-for-version-2-10-4-tp5754643p5754732.html Sent from the Camel - Users mailing list archive at Nabble.com.
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 platforms. I created a war based Camel project and deployed it with no issues to Weblogic. However a Camel project that supports Web Services requires CXF and Weblogic Web Services support is different (Metro..). Is there an easy way to have Camel running in Weblogic and supporting Web Services? We would also be interested to find a similar solution (Camel with Web Services support) for JBoss. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-and-Weblogic-tp4384040p4384040.html Sent from the Camel - Users mailing list archive at Nabble.com.
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’ flag in the result of each request). The messages further processing is expected to be done by multiple threads. I am new to Camel (we looked at it a long time ago but never had a chance to use it). I couldn’t find an obvious way to achieve the above, a loop processor could help but we don’t process the same message multiple times and in this case it is not a ‘for’ loop with a counter. I also considered ‘splitter’ but in this case we will have to read all available messages first before continue processing and we prefer to send each message immediately after getting it to a pool of multi-threaded executors. We will most likely define the endpoints using Spring beans and implementation will be using Java DSL. Any suggestions on how to achieve the above will be great. -- View this message in context: http://camel.465427.n5.nabble.com/Polling-Consumer-invoking-multiple-requests-tp5599204p5599204.html Sent from the Camel - Users mailing list archive at Nabble.com.
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 messages in one message upon receiving the request. We can than split the message and use a parallel processing (or any other concurrency method) to efficiently process the multiple messages. This problem appears to be a common one so it would be nice to have a Camel solution. Perhaps a loop with a predicate with a fix count that could serve as a loop limit… -- View this message in context: http://camel.465427.n5.nabble.com/Polling-Consumer-invoking-multiple-requests-tp5599204p5609951.html Sent from the Camel - Users mailing list archive at Nabble.com.
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 required to invoke a test request on the primary (which failed with No HTTP Response error). The Camel client sent one message (as observed on our Camel Trace log) but the server received two requests. We used soapUI client to invoke the same test server just to confirm that the server register one request only. Note that the 'Redelivery Policies' were configured with 'maximumRedeliveries' of 0. We ended up replacing the "cxf://.." endpoint with a 'processor' with Apache HTTPClient and this solve the duplicate message being sent. We couldn't find any obvious setting on the cxf configuration or the HTTP Conduit to prevent this from happening. Any suggestions on what may cause a 'NoHttpResponse' error to trigger sending a second message will be appreciated. -- View this message in context: http://camel.465427.n5.nabble.com/CXF-SOAP-Message-Sent-from-a-Camel-Client-Twice-When-No-HTTP-Response-Received-tp5771010.html Sent from the Camel - Users mailing list archive at Nabble.com.
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 - the server indicates that the following was sent twice org.apache.cxf.transport.http.Headers: 284 - SOAPAction: "Increment" The full log associated with the above as follows: 2015-09-01 11:58:38,582 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d c.b.g.sampleService.routes.sampleRoutes: 189 - Body: https://api.uri.com/1.0/types_trans";>*10.0 2015-09-01 11:58:38,587 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.camel.spring.SpringCamelContext: 387 - Using ComponentResolver: org.apache.camel.impl.DefaultComponentResolver@3c161441 to resolve component with name: cxf 2015-09-01 11:58:38,587 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.camel.impl.DefaultComponentResolver: 49 - Found component: cxf in registry: null 2015-09-01 11:58:38,590 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.camel.impl.DefaultComponentResolver: 82 - Found component: cxf via type: org.apache.camel.component.cxf.CxfComponent via: META-INF/services/org/apache/camel/component/cxf 2015-09-01 11:58:38,590 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d o.s.b.factory.support.DefaultListableBeanFactory: 450 - Creating instance of bean 'org.apache.camel.component.cxf.CxfComponent' 2015-09-01 11:58:38,592 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d o.s.b.factory.support.DefaultListableBeanFactory: 248 - Returning cached instance of singleton bean 'camelContext' 2015-09-01 11:58:38,592 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d o.s.b.factory.support.DefaultListableBeanFactory: 757 - Autowiring by type from bean name 'org.apache.camel.component.cxf.CxfComponent' via constructor to bean named 'camelContext' 2015-09-01 11:58:38,603 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d o.s.b.factory.support.DefaultListableBeanFactory: 478 - Finished creating instance of bean 'org.apache.camel.component.cxf.CxfComponent' 2015-09-01 11:58:38,604 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.camel.management.DefaultManagementAgent: 361 - Registered MBean with ObjectName: org.apache.camel:context=camel-1,type=components,name="cxf" 2015-09-01 11:58:38,605 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.camel.impl.DefaultComponent: 111 - Creating endpoint uri=[cxf://bean:samplePrimaryService?dataFormat=PAYLOAD], path=[bean:samplePrimaryService] 2015-09-01 11:58:38,606 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d o.s.b.factory.support.DefaultListableBeanFactory: 450 - Creating instance of bean 'samplePrimaryService' 2015-09-01 11:58:38,649 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d o.s.b.factory.support.DefaultListableBeanFactory: 248 - Returning cached instance of singleton bean 'loggingOutInterceptor' 2015-09-01 11:58:38,787 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.cxf.configuration.spring.ConfigurerImpl: 452 - Could not determine bean name for instance of class org.apache.cxf.ws.policy.PolicyAnnotationListener. 2015-09-01 11:58:38,794 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.cxf.configuration.spring.ConfigurerImpl: 452 - Could not determine bean name for instance of class org.apache.cxf.service.factory.FactoryBeanListenerManager. 2015-09-01 11:58:38,800 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.cxf.configuration.spring.ConfigurerImpl: 452 - Could not determine bean name for instance of class org.apache.cxf.ws.policy.PolicyEngineImpl. 2015-09-01 11:58:38,802 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.cxf.configuration.spring.ConfigurerImpl: 452 - Could not determine bean name for instance of class org.apache.cxf.ws.policy.PolicyDataEngineImpl. 2015-09-01 11:58:38,802 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.cxf.configuration.spring.ConfigurerImpl: 452 - Could not determine bean name for instance of class org.apache.cxf.bus.managers.CXFBusLifeCycleManager. 2015-09-01 11:58:38,805 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.cxf.configuration.spring.ConfigurerImpl: 452 - Could not determine bean name for instance of class org.apache.cxf.bus.managers.ServerRegistryImpl. 2015-09-01 11:58:38,805 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d o.s.b.factory.support.DefaultListableBeanFactory: 248 - Returning cached instance of singleton bean 'cxf' 2015-09-01 11:58:38,806 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d o.s.b.factory.support.DefaultListableBeanFactory: 248 - Returning cached instance of singleton bean 'cxf' 2015-09-01 11:58:38,808 DEBUG d87c73ab-1c15-480b-81de-73f3d314148d org.apache.camel.util.IntrospectionSupport: 528 - Configured property: data
