Hi Yogesh
Thanks for digging into this and reporting back. I have created a
ticket about the upgrade
https://issues.apache.org/activemq/browse/CAMEL-1567
On Fri, Apr 24, 2009 at 9:41 PM, ychawla wrote:
>
> Hi Claus,
> Here is an explanation of the API change from Christopher Beck at JUEL:
>
>
Hi Claus,
Here is an explanation of the API change from Christopher Beck at JUEL:
Hello Yogesh,
the API to resolve methods has changed in 2.1.1. Camel's method resolver
is breaks with JUEL 2.1.1. Generally, methods are still resolved via
ELResolver.getValue(context, base, property), but
- in 2.1
Hadrian,
I guess the remark about the patch refers to the HL7 Decoder problem - I
haven't submitted one for the convertBodyTo() ... yet.
The piece of code wasn't originally intended as patch, more of a proposal
how to resolve the issue. If the releases are not on Monday ;-) I'm
confident I can p
@Christian, the patch you submitted requires a bit of work to be
applied to Camel. At least the "package bla;" needs to change, and
the apache license headers applied, a unit test and so forth. I could
do this part if you don't have time. However we would need a sample
HL7 message that
I have a situation where a request comes in to Jetty, and goes through
two other routes and queues before a response is generated that allows
the HTTP response to be sent to the caller. I'd like to be able to
force Jetty into using continuations so it doesn't park a thread while
those other routes
Hi Christian
No that is fantastic. We would love to incorporate your findings into
the camel-hl7 component.
So if you are willing to donate then please create a JIRA ticket and
attach your work.
On Fri, Apr 24, 2009 at 5:39 PM, christian ohr wrote:
>
> Hi there,
>
> in the current implementat
Hi, me again...
Another problem I came across:
when reading HL7 messages e.g. from a stream, they become unusable after
running though a convertBodyTo(String.class) converter for further
processing.
The reason is that the converter uses the readLine() method of a
BufferedReader which splits up a
Done. (https://issues.apache.org/activemq/browse/CAMEL-1566)
Please note that there's no camel-hl7 component in JIRA, so I temporarily
filed it under camel-mina
Christian
http://gforge.openehealth.org/gf/project/ipf/
Hi Christian
No that is fantastic. We would love to incorporate your f
Hi there,
in the current implementation of the HL7 component, HL7v2 messages that
exceed a certain size (I guess it's related to the TCP packet size, 1024
bytes on my machine) are split into two or more exchanges. The second (,
third, forth, ...) exchange body starts somewhere in the middle of th
Hi
But you could also give a try to add an option to the endpoint and
provide a patch to us.
Then the fix will be implemented much faster.
On Fri, Apr 24, 2009 at 2:41 PM, Claus Ibsen wrote:
> On Fri, Apr 24, 2009 at 2:33 PM, raulvk.soa wrote:
>>
>> Hi Claus,
>>
>> Ticket created: https://issu
On Fri, Apr 24, 2009 at 2:33 PM, raulvk.soa wrote:
>
> Hi Claus,
>
> Ticket created: https://issues.apache.org/activemq/browse/CAMEL-1565.
>
> Any ideas on a temporary workaround while the fix is found?
You could try to create your own component that extends the one in Camel.
There is a doStart()
Hi Claus,
Ticket created: https://issues.apache.org/activemq/browse/CAMEL-1565.
Any ideas on a temporary workaround while the fix is found?
Many thanks!
Claus Ibsen-2 wrote:
>
> Hi
>
> Could you create a ticket in JIRA for this.
>
> Link to jira from here:
> http://camel.apache.org/support
Hi
Could you create a ticket in JIRA for this.
Link to jira from here:
http://camel.apache.org/support.html
Then we wont forget and will be able to put in a fix
On Fri, Apr 24, 2009 at 11:53 AM, raulvk.soa wrote:
>
> Hi,
>
> I have a Camel flow which seems to be experimenting concurrency issue
On Fri, Apr 24, 2009 at 12:26 PM, sebodev wrote:
>
> Hi,
>
> the problem ist fixed. If i have putted a jar orai18n.jar as dependency into
> project then receiving for messages from queue starts to working. Thank you
> for your replies.
Thanks for sharing this information.
And glad you got it work
Hi,
the problem ist fixed. If i have putted a jar orai18n.jar as dependency into
project then receiving for messages from queue starts to working. Thank you
for your replies.
Kind regards
Sebastian
sebodev wrote:
>
> Hi James,
>
> it is not a permission issue because i please my administrat
Hi,
I have a Camel flow which seems to be experimenting concurrency issues with
the camel-validation component. This flow is invoked twice in parallel by a
splitter.
It seems like the camel-validation component lazily-loads the XSD, when the
first request comes in.
As a consequence, when two si
16 matches
Mail list logo