Hi all,
I was going through the Resequencer camel component available in the
link: http://camel.apache.org/resequencer.html
On trying the resequencer camel component with the StreamResequencer
config with the code below:
from("jms:queue:nq1").
convertBodyTo(Strin
Hi
Is this a duplicate? We got this mail yesterday (I think) as well? And
answered it.
On Tue, Apr 21, 2009 at 9:05 AM, Nawaz Ahmed wrote:
>
>
> Hi all,
>
> I was going through the Resequencer camel component available in the
> link: http://camel.apache.org/resequencer.html
>
>
>
> On trying
Hi Claus,
thank you for your resourceful remarks.
I am now facing a new problem. The JPA component creates a
org.springframework.orm.jpa.JpaTransactionManager on its own - which
conflicts quite badly with the JTA environment of an EJB container. Is there
any built-in facility to a more declarati
On Tue, Apr 21, 2009 at 2:01 PM, Frank Schwarz wrote:
>
> Hi Claus,
>
> thank you for your resourceful remarks.
>
> I am now facing a new problem. The JPA component creates a
> org.springframework.orm.jpa.JpaTransactionManager on its own - which
> conflicts quite badly with the JTA environment of
Hi,
I am experiencing some weird behavior on the character encoding front.
I have simplified/narrowed the problem down to the conversion from
file input to xml:
from("file:src/data/input")
.to("direct:tvaDropbox");
from("direct:tvaDropbox")
.to("xslt:tvaTransformer.xsl"
Hey,
Just a bit of feedback regarding the Camel 2 milestones. We have
created experimental branches of all our corporate projects which make
use of Camel 1.x, and upgrading them to use Camel 2M1. These branches
have been added to our Bamboo, which we plan to keep up to date with any
subsequent m
I'm using the camel snapshot release... but recall having this problem
before.
On Apr 21, 2009, at 16:28 , Peter Maas wrote:
Hi,
I am experiencing some weird behavior on the character encoding
front. I have simplified/narrowed the problem down to the conversion
from file input to xml:
2009/4/21 Martin Gilday :
> Hey,
>
> Just a bit of feedback regarding the Camel 2 milestones. We have
> created experimental branches of all our corporate projects which make
> use of Camel 1.x, and upgrading them to use Camel 2M1. These branches
> have been added to our Bamboo, which we plan to
Hi Martin
Thanks a lot for the feedback. Nice to hear the upgrade path for you
so far has not been with any pain.
On Tue, Apr 21, 2009 at 4:30 PM, Martin Gilday wrote:
> Hey,
>
> Just a bit of feedback regarding the Camel 2 milestones. We have
> created experimental branches of all our corpora
I have implemented a route using multicast, what I want is to:
1: get a file from an http/xml service
2a: save the file
2b: split the file and forward to a queue
I notice that only the first endpoint gets passed the body of the message.
In my example the file is empty. If I change the order
Hi,
It looks like the input stream of the http client doesn't be cached.
Which version of Camel are you using?
Can you try out the Camel 2.0M1 to see if the issue is still there?
Willem
G.J. van de Streek wrote:
> I have implemented a route using multicast, what I want is to:
> 1: get a file f
I don't suggest your start the ActiveMQ Broker (Using TCP transport)
with Guice in the same time you start up the Camel Context.
If you have multi Camel Contexts which share same ActiveMQ broker, that
will cause some troubles.
How about to write a ActiveMQ Module to wrap the start and stop methods
Hi,
I just check the code, xslt component uses UTF-8 as the default
character encoding, and the ConertBodyTo(String.class) using the default
character encoding of your OS.
I don't know if the testing xml document is really encoded with UTF-8.
BTW, you can set the encoding of XSLT component by set
I am using Camel 1.5.0 / ActiveMQ 5.2.0.
Is there any way to upgrade to Camel 2.0 and still use activeMQ 5.2.0?
--
View this message in context:
http://www.nabble.com/usage-of-multicast-tp23163812p23169890.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
It seems from the documentation that the multicast function would actively
copy the http message to both destinations. That should be disregarding a
caching, or non caching http client.
/**
* Multicasts messages to all its child outputs; so that each processor
and
* destination get
On Wed, Apr 22, 2009 at 7:25 AM, G.J. van de Streek wrote:
>
> I am using Camel 1.5.0 / ActiveMQ 5.2.0.
>
> Is there any way to upgrade to Camel 2.0 and still use activeMQ 5.2.0?
Camel has no strict dependency which version of ActiveMQ you are
using. So Camel works basically with any one you like.
In Camel 1.6.0 there should be some stream cache you can enable (its
enabled by default If I recall correctly).
This stream cache should be able to let you read the http stream multiple times.
But there should be a .enableStreaming() or what the DSL name was,
cant remember exactly if you want to f
17 matches
Mail list logo
