Re: Missing properties on exception

Hi Can you share how did you solve this issue? I am facing the same issue. -- View this message in context: http://camel.465427.n5.nabble.com/Missing-properties-on-exception-tp4775029p5752857.html Sent from the Camel - Users mailing list archive at Nabble.com.

Making Camel based middle layer available even when services are not

Hi There, In any integration solution there is a high possibility that one of the consumed services are unavailable but the integration layer should still be available. The same case applies to my problem statement, that is I have the following - 1) The integration gateway connects to service-1

Re: How To implement a periodically polled queue.

Thanks Claus, for the reply. I thought so, but then for the time-being my problem is solved and maybe in future we can see some new component in Camel for this as I believe JMS (with peristent store) is a reasonable fallback for retrying in case any of the services being unreachable/down.

How To implement a periodically polled queue.

Hi, I have the following requirement - 1) If a message is received on the save entity route and the authentication server is not available, then queue up the request in the *periodicallyPolledInputQueue*. 2) The *periodicallyPolledInputQueue* thus may have n number of messages. 3) Every 30

Re: How To implement a periodically polled queue.

For the time being, I am using a consumer template to fetch n number of messages in the *periodicallyPolledInputHandler* processor triggered from the quartz and pushing it to the originating queue using a producer template. Is there a better way of doing this? -- View this message in context:

Header goes missing while posting from a periodically polled consumer

Hi, I have a route somewhat like below - route id=periodicallyPolledInputQueueHandlerRoute from uri=quartz://periodicallyPolledInputQueueHandler?cron=0+0/5+*+*+*+?/ camel:transacted ref=PROPAGATION_REQUIRED_XL/ pollEnrich

Re: Header goes missing while posting from a periodically polled consumer

Strangely enough, the following method seems to be working - template.sendBodyAndHeader(originalConsumer, ExchangePattern.InOnly , exchange.getIn().getBody(String.class), USERNAME_TOKEN, username); But the problem is that I have multiple tokens that I need to set in the header :( -- View this

Re: some routing error in XA transaction

I too faced the same issue, was puzzled a lot. In my case I was having 2 transaction managers, 1 was for JpaTransactionManager for hibernate usage for database operations and I wanted another transaction manager for JmsTransactionManager. I am not sure why this is thrown. Though I tweaked some of

Defaulting using XSLT.

Hi, I have a requirement such that I need to merge 2 XMLs, The sources are as follows - 1) XML coming in as an input payload as part of WS 2)The default values stored in DB in form of XML. The problem at hand is if the values of the defaulted tags are not provided in the incoming payload, then

Re: exposing different operations under same service in camel + cxf routing.

My bad, I used the dataFormat as MESSAGE and it seems teh operation name is available only in case of dataFormat = PAYLOAD. It works for me with dataFormat = PAYLOAD. Thanks. -- View this message in context:

Re: How Do We Specify Operation To Choose In Camel CXf

My bad, I used the dataFormat as MESSAGE and it seems the operation name is available only in case of dataFormat = PAYLOAD. It works for me with dataFormat = PAYLOAD. Thanks. -- View this message in context:

Re: exposing different operations under same service in camel + cxf routing.

Following is the header that I see in the logs when run with mvn camel:run and routed to log uaing show header option like below- to uri=log:before?showHeaders=true/. I don't see no operationName header - Headers:{SOAPAction=http://reportincident.example.camel.apache.org/ReportIncident;,

Re: exposing different operations under same service in camel + cxf routing.

By the way I am calling the 2 operations in the WSDL using SOAPUI. -- View this message in context: http://camel.465427.n5.nabble.com/exposing-different-operations-under-same-service-in-camel-cxf-routing-tp5716944p5717444.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: How Do We Specify Operation To Choose In Camel CXf

http://camel.465427.n5.nabble.com/file/n5717466/camel-example-cxf-proxy.rar camel-example-cxf-proxy.rar I have this in the attached project. But the issue is that the operation name header is not displayed on teh incoming request. I have used the following - to uri=log:before?showHeaders=true/

Re: exposing different operations under same service in camel + cxf routing.

http://camel.465427.n5.nabble.com/file/n5717345/camel-example-cxf-proxy.rar camel-example-cxf-proxy.rar Hi There, Thanks for the reply. My goal is to expose a WS as an endpoint in Camel-CXF and based on the WS operation triggered by an external WS consumer I need to trigger the route/workflow. I

Re: How Do We Specify Operation To Choose In Camel CXf

Hi There, I have a similar short of issue. The problem is with the producer end. That is the from side of the route I want to chose an operation. route from uri=cxf:bean:reportIncident/ . /route Camel allows having only one endpoint at a single address like the following-