Ashwin,
Thank you very much for the reply.
My further comments below.
On Fri, Jul 31, 2009 at 3:29 AM, Ashwin Karpe wrote:
>
> Hi,
>
> There is no need for a fix. Please find the answers to your questions below.
>
>> 1. I can't use setBody(null) to remove the payload of the message.
>> instead, I
Ah yes - summer in the northern hemisphere appears to be why the list has
quietened. Of course, it is winter down here in Australia so we're busy as
ever!
--
View this message in context:
http://www.nabble.com/Hello-community-tp24735480p24747465.html
Sent from the Camel - Users (activemq) mailin
Hi,
Community here... Just off sippng some cool drinks in a warm place :). Ah
the joys of summer...
Cheers,
Ashwin...
huntc wrote:
>
> Traffic appears to have quietened on this forum recently - any known
> reason why?
>
-
---
Ashwin Karpe, Principal Consultant, PS - Opensource Center
Hi,
There is no need for a fix. Please find the answers to your questions below.
> 1. I can't use setBody(null) to remove the payload of the message.
> instead, I have to use setBody("") or similar value to represent an
> empty payload, which can be problematic in some cases, as NULL and
> non-N
You might want to check out this online utility to search the required jar
files and get past all the "ClassNotFound" errors:
http://www.ellipsissolutions.com/xray.php
Thanks,
GT
jpcook wrote:
>
> Hi,
>
> I was reading this post:
> http://www.nabble.com/What-jar-is-ca.uhn.hl7v2.parser.Pars
On Thu, Jul 30, 2009 at 12:03 PM, huntc wrote:
>
> Hi there,
>
> I just used the concurrentConsumers parameter of the seda component and fell
> into the trap of not including parameters in the producer URI. Having to
> have the producer and consumer specify the same parameters seems troublesome
>
On Thu, Jul 30, 2009 at 11:58 AM, huntc wrote:
>
> Traffic appears to have quietened on this forum recently - any known reason
> why?
> --
A reason should be that people are on vacation or that they are just
happy with how it goes with their Camel :)
For me I am sitting duck with heavy rain outsi
Hi there,
I just used the concurrentConsumers parameter of the seda component and fell
into the trap of not including parameters in the producer URI. Having to
have the producer and consumer specify the same parameters seems troublesome
and non-intuitive. Additionally the producer URI shouldn't
Traffic appears to have quietened on this forum recently - any known reason
why?
--
View this message in context:
http://www.nabble.com/Hello-community-tp24735480p24735480.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Fast work, Claus! I'll move my code over to Camel 2.0, which should be
straightforward enough now I can see my way around things a bit more (Camel,
MINA and HAPI are quite a lot to learn in one go, especially while I'm
trying to get my head around HL7 as well).
--
View this message in context:
h
On Thu, Jul 30, 2009 at 11:13 AM, Johnny2R wrote:
>
> I use a PipeParser, but to be honest it's not that important, the only thing
> I really need is validation or not, so I think the best thing to do is what
> you're already doing.
> --
Cool.
The validation option is now avail in the Camel 2.0 r
I use a PipeParser, but to be honest it's not that important, the only thing
I really need is validation or not, so I think the best thing to do is what
you're already doing.
--
View this message in context:
http://www.nabble.com/How-to-prevent-HL7-message-validation--tp24717549p24734897.html
Se
12 matches
Mail list logo