I'm using Camel 2.2.0-fuse-02-00 in Fure SMX.
What I want is to catch any exception when sending to the recipientList,
something like:
from("...")
.doTry()
.recipientList(header(..))
.doCatch(Exception.class)
.to(..)
.end()
But Eclipse does not allow me to do .doCatch(..) after .recipientList(..
Andrei,
If you do not specify both service class and WSDL in the endpoint, the
validation is bypassed. (The "skipPayloadMessagePartCheck" flag is not
a user settable option). You can send any XML payload you wish.
Otherwise, message will be checked to make sure required body parts are
prov
Sorry bout that, hopefully this is better.
Message body
http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.springframework.org/schema/beanshttp://www.springframework.org/schema/beans/spring-beans.xsd
http://came
Hi Claus,
Yep, it is possible way.
Another possibility is using java CXF client with dispatch interface and
integrate it with my route via bean component.
Do you have any ideas why Camel CXF code makes this validation at all?
Basically root payload element can be not the same as web service met
eventually found the problem.
if transactions are enabled nothing works. Only the first message gets through
the route, the rest disappear. The problems start by adding transacted and
transactionManager to the ActiveMQComponent as per:
http://camel.apache.org/transactional-client.html
so I'm n
Hi
The Splitter have built-in aggregator, which seems like what you do
with that embedded aggregator
See example
http://camel.apache.org/splitter
Maybe you can take a thread dump when the app is hanging.
Or if you could create an unit test that reproduces the issue would be great.
On Thu, Sep
Hi
You can use plain HTTP component to forward a web service call.
On Fri, Sep 30, 2011 at 5:54 PM, Andrei Shakirin wrote:
> Hi,
>
> Is there any way to avoid expected message part checking (CxfEndpoint.java)
> in 2.7.3?
> skipPayloadMessagePartCheck option was introduced in 2.8.0:
> https://
Hi,
>> unless you are already use JBI a lot, and are happy with it as
is.
Yes, we are using JBI a lot.
>> No JBI is dying/dead
Yes, this is what we are concerned about.
Is staying with Servicemix 3.x an option? Or should we migrate to
Camel? Is c
On Thu, Sep 29, 2011 at 4:31 PM, Nserra wrote:
> Hello
>
> I have a route that copy each hour a file and process it, but, at some part
> of the day the file won't be there and I wan't to catch this to look at
> another file in another folder is this possible?
>
You can implement a PollingConsumer
Hi
Can you post the XML so its readable :)
On Sat, Oct 1, 2011 at 6:40 PM, Aaron Doyle wrote:
> I have a small route that reads from an activemq queue and sends the message
> to a bean, a service client that calls a web service, and am experiencing a
> few issues. The onException configurati
On Fri, Sep 30, 2011 at 8:19 PM, diwakar wrote:
> Hi,
>
> I have a File sender endpoint (test:s) created that sends a file
> to a folder. The SA containg this SU is deployed into Servicemix 4.3 deploy
> folder. I am trying to send a file from Camel poller (file:input2) to the
> JBI sende
On Fri, Sep 30, 2011 at 8:31 PM, diwakar wrote:
> Hi,
>
> Thanks for the reply. With async and defaultThreadPoolProfile, is
> Camel support for parallel processing as good as Servicemix 3.x. Are there
> any known limitations in Camel over JBI(Servicemix3.x). Is there any good
> reason to
12 matches
Mail list logo