Hi,
Here are the dependencies jars when you are using JDK 1.6.x
[INFO] The following files have been resolved:
[INFO]aopalliance:aopalliance:jar:1.0:compile
[INFO]org.apache.camel:camel-core:jar:2.5-SNAPSHOT:compile
[INFO]org.apache.camel:camel-spring:jar:2.5-SNAPSHOT:compile
[INFO]
Hi Bryce,
I just went through the code of camel-rss, if you want to get the Feed
object from the different RSS services, you can consider to use
RssDataFormat, it will help you to turn an input stream into SyndFeed.
The route could like this
from("http://";).unmarshal().rss().to("someOthe
Hi,
I'm a little confused by the use of a processor when consuming message (in
POJO mode) from a CXF endpoint.
Basically, what I want to do is consuming messages from the latter : just
knowing what the operation is and do some processing depending on it,
returning the result to the caller (the pro
Hi
You can set the header Exchange.BEAN_METHOD_NAME on the Exchange and
then invoke a bean.
The bean could then have the same method names as the CXF. Then Camel
will pick the appropriate method.
You may even just copy the CXF operations header to the method name header.
from(cxf)
.setHeader(Exch
If we can map the CXF operation name to the bean's method, then camel
can invoke the bean as you want.
You can use CXF directly by setting the implementor with your bean.
If you already has the response, I don't know what you want to do next
with the camel route. Can you tell me your user st
Hi
Yeah its just a warning that the ftp operation could not complete due
it being shutting down.
I will polish the logging a bit so you wont see the WARN and
stacktraces during shutdown.
On Mon, Jul 19, 2010 at 10:51 PM, Glebow, Philip
wrote:
> I'm using Camel 2.4 and this route to move files f
On Tue, 20 Jul 2010 16:46:41 +0800, Willem Jiang
wrote:
> If we can map the CXF operation name to the bean's method, then camel
> can invoke the bean as you want.
>
> You can use CXF directly by setting the implementor with your bean.
>
> If you already has the response, I don't know what you w
Hi
I have committed a fix to trunk. You are welcome to test with latest
source code on your system, if the logging is "more friendly" when
shutting down Camel.
On Tue, Jul 20, 2010 at 10:57 AM, Claus Ibsen wrote:
> Hi
>
> Yeah its just a warning that the ftp operation could not complete due
> i
You can use producerTemplate to send original message into a JMS queue.
Please check out the camel-example-reportincident[1] for more information.
[1]http://camel.apache.org/tutorial-example-reportincident-part5.html
Willem
--
Apache Camel, Apache CXF committer
Hi, I'm trying to understand the use of streamcaching and I have a doubt. In a
simple case like this:
from("jetty")
.process( {processor that consumes the body input stream})
.to("http:")
the processor consumes the in body and it is not available for the next step
(the "to" sta
Hi
The logger will not consume streams but log that is a streaming type.
So its expected behavior.
On Tue, Jul 20, 2010 at 12:43 PM, Cappa Roberto
wrote:
> Hi, I'm trying to understand the use of streamcaching and I have a doubt. In
> a simple case like this:
>
> from("jetty")
> .process(
Hi
I have two routes in a routecontext. Both share an errorhandler but one of
the routes has a special exception clause. These routes works as expected
when defined directly in a camelContext, but when imported from a
routeContext, behaviour is flawed. In the routes below route2 "inherits" the
on
Actually I'm not sure if startuporder has anything to do with it, or if it's
just the physical placement in the .xml file.
--
View this message in context:
http://camel.465427.n5.nabble.com/possible-onException-bug-when-using-routeContext-tp1616244p1616574.html
Sent from the Camel - Users mailin
Hi
Could you create a JIRA ticket
On Tue, Jul 20, 2010 at 1:17 PM, Andreas Asmuss wrote:
>
> Hi
>
> I have two routes in a routecontext. Both share an errorhandler but one of
> the routes has a special exception clause. These routes works as expected
> when defined directly in a camelContext, bu
Hi
Created a ticket an attached a sample case:
https://issues.apache.org/activemq/browse/CAMEL-2972
--
View this message in context:
http://camel.465427.n5.nabble.com/possible-onException-bug-when-using-routeContext-tp1616244p1618526.html
Sent from the Camel - Users mailing list archive at Nab
Ok, but if the the straming was consumed in a processor that preceeds the log,
how does the content stream could be read another time from the log?
Thanks
Da: Claus Ibsen [claus.ib...@gmail.com]
Inviato: martedì 20 luglio 2010 13.09
A: users@camel.apache.o
I am really not trying to be difficult, I promise (imagine if I were :-) )
So, there are Spring JARs that are now required for camel 2.4.0 but are not
included in the binary distribution because the new version of Sping, has
additional dependencies that only get sorted out if you choose to use mav
Hi
I have created a ticket
https://issues.apache.org/activemq/browse/CAMEL-2974
To include the missing new jars provided in spring 3.0.x which we
missed when upgrading.
I will move the jdk 1.5 jars into a lib/jdk15 folder so they wont be
in the main lib folder.
Then you only got the core jars ne
On 20 July 2010 14:21, Ron Smith wrote:
> I am really not trying to be difficult, I promise (imagine if I were :-) )
>
> So, there are Spring JARs that are now required for camel 2.4.0 but are not
> included in the binary distribution because the new version of Sping, has
> additional dependencies
On 19 July 2010 22:12, Ron Smith wrote:
> I'm with you, Jim. I think that is part of why others at my company consider
> spring to be "evil" -- for a "light-weight" framework, there sure are a lot
> of pieces you have to include and they seem to be growing and becoming more
> intertwined with each
On Tue, Jul 20, 2010 at 5:17 PM, James Strachan
wrote:
> On 19 July 2010 22:12, Ron Smith wrote:
>> I'm with you, Jim. I think that is part of why others at my company consider
>> spring to be "evil" -- for a "light-weight" framework, there sure are a lot
>> of pieces you have to include and they
Hi
I have created a ticket to see if there is something we can do in the future
https://issues.apache.org/activemq/browse/CAMEL-2975
On Mon, Jul 19, 2010 at 10:34 PM, gnanda1 wrote:
>
> Thanks Clause for the reply.
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Stoppin
See this wiki page about the need to be a subscriber of the mailinglist
http://camel.apache.org/discussion-forums.html
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-evaluate-an-expression-substitute-a-variable-for-building-URI-s-at-runtime-tp1618587p1618962.html
Sent
Unfortunately, all those cool features (especially pooling and reconnect)
are exactly why I was wanting to use something like camel. This isn't the
first time that this companies unreasonable biases have limited my choices
of tools. I'm not a fan of spring or maven but I understand their value.
I
On 20 July 2010 16:38, Ron Smith wrote:
> Unfortunately, all those cool features (especially pooling and reconnect)
> are exactly why I was wanting to use something like camel. This isn't the
> first time that this companies unreasonable biases have limited my choices
> of tools. I'm not a fan of
I hadn't thought about it that way, James, but does that mean there needs to
be some distinction between what is "core" functionality and what is
"add-in" functionality? And, if we go that route, how do you manage the
dependencies of each of the add-ins? I think Claus is on the right track by
separ
On 20 July 2010 16:51, Ron Smith wrote:
> I hadn't thought about it that way, James, but does that mean there needs to
> be some distinction between what is "core" functionality and what is
> "add-in" functionality?
There kinda already is :). camel-core.jar is the core :). That comes
with a bunch
Thanks Willem. My message selector is working now.
After a few debugging I found that it was not the issue with the message
selector on consumer side. It was the issue with the header setup.
I am just writing up it here, in case anyone has similar issue and trying to
resolve it.
I have a class n
It could be much easier if you implement a DataFormat[1] yourself.
Then you could pass the "CONVERT_BODY_TO_RSSURL" as the message header and
tell the DataFormat to do the job for you.
[1]https://cwiki.apache.org/CAMEL/data-format.html
Willem
--
Apache Camel, Apac
29 matches
Mail list logo
