On 7/27/12 1:25 PM, nishant.rupani wrote:
Hi,
Yes, I've setup JMS. I checked the setup by putting "" directly into the router and it worked well.
Few more things I noticed,
- if I call a method directly from main route that throws test exception
then it gets written to error queue fine.
Yeah, this example is setting the right headers on the message which is
passed by the exchange.
On Sat Jul 28 06:17:56 2012, ychawla wrote:
I have something like this working in a unit test. Maybe you can try
something similar:
public static final String CXF_OPERATION_NAME = "operatio
I have something like this working in a unit test. Maybe you can try
something similar:
public static final String CXF_OPERATION_NAME = "operation";
public static final String CXF_OPERATION_NAMESPACE =
"http://opNamespace";;
@Test
@DirtiesContext
public void
Dears,
I have a project that has tcp mina to endpoint deployed on Fuse and is
communicated with Network element .
The network element doesn't return textdelimiter as normal per configuration ,
and the incoming response from Network element to Fuse is textlimited with semi
column ;.
The Text
Hi
I've added a unit-test based on your issue, however based on ActiveMQ which
we use for JMS testing.
http://svn.apache.org/viewvc?view=revision&revision=1366483
So I wonder what's exactly the issue you're facing. Maybe provide more
information like stacktrace, logs, etc..
Babak
--
View thi
You use the same WebShere MQ queue manager for receiving the messages and
writing the failed messages, correct?
Could you please share the entire Spring XML configuration (including the
JMS component configuration). I'm a bit confused because you use 'wmq' and
'wmqError' as schema name. Did you al
You have to cache the stream if you want to read it multiple times:
http://camel.apache.org/stream-caching.html
Best,
Christian
On Fri, Jul 27, 2012 at 6:08 PM, marnold wrote:
> Camel Users,
>
> I need to take a large XML message, split into smaller messages, send each
> small message to a JMS
Sorry - should've mentioned. As is apparent from the exception, I am using
at the top of my route, followed by http://";> . Not
sure if that makes a difference...
--
View this message in context:
http://camel.465427.n5.nabble.com/After-split-get-Stream-closed-on-original-message-tp57165
Hi
I need to interact with a vendor product which exposes a number of readable
mbean attributes. Unfortunatly, no notifications exist for these attributes.
I need to poll these managed attributes every 2 mins to see if any have
updated.
Since the JMX component does not appear to support polling
Camel Users,
I need to take a large XML message, split into smaller messages, send each
small message to a JMS destination, then apply XSLT to original message and
send that somewhere else...
The split works well, the smaller messages are processed correctly, but when
I try to apply an XSLT to th
Am 27.07.12 14:16 schrieb "Caa_man" unter :
>Hello everyone!
>
>I would like to use several MQ managers in my Camel application (I use
>Camel
>2.9.2) like this:
>
>
>
>...
>
>
>
>
>...
>
>
>
>
>
>
>
>
>
Hello everyone!
I would like to use several MQ managers in my Camel application (I use Camel
2.9.2) like this:
...
...
Yeah it's solve, it was just a problem of bad coding that sent the following
message :
""com.awl.acq.wlsi.sips.xsd" doesnt contain ObjectFactory.class or jaxb.index
to validate with a xsd."
To the validation endpoint.
Thanks for your help and your time :-)
KR,
Arnaud Deprez
-Original Me
Nope it doesn't. It just has print. I've removed it too but still same issues.
Regards,
Nishant
From: Christian Mueller [via Camel]
[mailto:ml-node+s465427n5716543...@n5.nabble.com]
Sent: Friday, July 27, 2012 1:32 PM
To: Rupani, Nishant (ISGT)
Subject: Re: Not writing to Error queue
May be th
May be the exceptionPrint method of exceptionHandler throws an exception?
Christian
On Fri, Jul 27, 2012 at 7:25 AM, nishant.rupani <
nishant.rup...@morganstanley.com> wrote:
> Hi,
>
> Yes, I've setup JMS. I checked the setup by putting " uri="wmqError:${error.queue}" />" directly into the route
Thank you Pontus and Willem for the recommendations.
We are using JBoss 4.0.4 and 5.1.0 and rather topics than queues and we have
several source systems (even our Jboss servers can do that) using several
protocols to provide messages for that topic.
Could be possible that we go for 7.1.1 for both
16 matches
Mail list logo