Hi,
I have this question. We have a requirement in a project in which we have to
use remoting for our application. Reading the Spring Documentation, it says
that it is possible to do remoting via Spring Remoting Facilities. They have
several options and I opted to use the JMS Version.
Here is my
Hi DRy,
it can get quite complicated to handle all those jars by hand. I always
use maven to avoid copying jars around. You should try it if you do not
have another
build system. The camel examples are a good starting point. In any case
it is very important to make sure you don´t mix jars from
Hi,
I tried to build a small (eclispe) project that shows what happens. To keep
this project as small as possible I do not include the used libs to that
project but use the lib path from a standard camel "installation" (2.1
Snapshot). What should I say ... everything works fine in that project .
Hi
Thanks for the findings.
Maybe you can save the feed which have the feeds ordered in non
publication order.
And we can use that for unit testing.
Feel free to anym the feed beforehand.
And we love contributions so if you want to take a stab to see if you
can resolve this please go ahead.
htt
On Mon, Nov 9, 2009 at 10:46 AM, Willem Jiang wrote:
> I checked the code of http client 3.1, there is no parameter key of
> "http.protocol.handle-redirects".
> This option is part of client 4.0.
> Maybe we should consider to upgrade camel-http to use httpclient 4.0.
>
Yeah sometime after Camel 2
On Mon, Nov 9, 2009 at 10:26 AM, marcin80 wrote:
>
> Hi,
>
> Thanks for your help. I have other question. How shoud I do it in XML? My
> Java DSL code looks like this:
>
> from("timer:foo?period=5000").
> setBody(constant("select dz.xx from table dz")).
>
> to("jdbc:
On Mon, Nov 9, 2009 at 6:14 PM, boday wrote:
>
> Claus, my questions are really specific to how Camel wraps the underlying AMQ
> technologies. In particular, how Camel handles transactions and client
> acknowledgements when exceptions are raised and redelivery policies applied
> (using Camel's on
Claus, my questions are really specific to how Camel wraps the underlying AMQ
technologies. In particular, how Camel handles transactions and client
acknowledgements when exceptions are raised and redelivery policies applied
(using Camel's onException clause, etc).
Also, I'm not running in DUPS_
created:
https://issues.apache.org/activemq/browse/CAMEL-2153
Claus Ibsen-2 wrote:
>
> Hi
>
> Could you create a ticket in JIRA.
>
> And also pin point exactly which file is that you mean when you say
> "when the destination file exists".
> - is it the temp file
> - is it the final destinatio
You bet. http://issues.apache.org/activemq/browse/CAMEL-2152
I'll see about trying to add a standalone unit test...
Claus Ibsen-2 wrote:
>
> Could you create a JIRA ticket and attach your patch.
> And if you have any kind of unit test that can verify this that would
> be great as well.
>
--
Hi
Could you create a ticket in JIRA.
And also pin point exactly which file is that you mean when you say
"when the destination file exists".
- is it the temp file
- is it the final destination file
What OS do you use.
On Mon, Nov 9, 2009 at 3:07 PM, mcrive wrote:
>
> Hi,
> I am using FTP com
Hi,
I am using FTP component to push files via FTP.
I am facing issues pushing a file on subfolder when using tempPrefix or
tempFileName.
route sample:
from("direct:start").to("ftp://usern...@ipaddress?password=mypass&fileName=./camel/test/message.txt&tempFileName=${file:name.noext}.tmp";);
no
Hi
yikes ugly story.
Could you create a JIRA ticket and attach your patch.
And if you have any kind of unit test that can verify this that would
be great as well.
On Mon, Nov 9, 2009 at 2:17 PM, dcheckoway wrote:
>
> Claus,
>
> Thanks...that got us further along but didn't quite work. I final
Claus,
Thanks...that got us further along but didn't quite work. I finally got my
butt in gear and started doing camel builds, and I managed to get this
problem fixed. Here's the scoop:
The Message instance we're working with is read-only. So when calling
setHeader it threw:
javax.mail.Illeg
Many thanks to those who have commented on my initial post.
Here's a bit of an update on what we've found with some additional
investigation on the behavior of the RSS component.
It appears that if you configure it to pick up one item/story at a time (as
opposed to the entire feed), it will do t
I checked the code of http client 3.1, there is no parameter key of
"http.protocol.handle-redirects".
This option is part of client 4.0.
Maybe we should consider to upgrade camel-http to use httpclient 4.0.
Willem
Willem Jiang wrote:
Oh, camel-http component doesn't support to take the
paramete
Duly logged in JIRA.
Claus Ibsen-2 wrote:
>
> On Mon, Nov 9, 2009 at 9:38 AM, Ian de Beer wrote:
>>
>> Hi
>> I have tried to sort RRS feeds or to split the entries as described in
>> the
>> documentation. The problem is that the parameters that are to be consumed
>> by
>> Camel are passed thro
Hi,
Thanks for your help. I have other question. How shoud I do it in XML? My
Java DSL code looks like this:
from("timer:foo?period=5000").
setBody(constant("select dz.xx from table dz")).
to("jdbc:dataSource").splitter(body()).convertBodyTo(String.class).
Ok, many thanks for the precious help
Claus Ibsen-2 wrote:
>
> And if you are looking for such kind of support you very likely have
> to acquired paid support. Which offers such kind of custom specific
> patches.
>
--
View this message in context:
http://old.nabble.com/Error-handling-with-r
On Mon, Nov 9, 2009 at 9:38 AM, Ian de Beer wrote:
>
> Hi
> I have tried to sort RRS feeds or to split the entries as described in the
> documentation. The problem is that the parameters that are to be consumed by
> Camel are passed through to the endpoint, who does not understand the
> parameter
Hi
I have tried to sort RRS feeds or to split the entries as described in the
documentation. The problem is that the parameters that are to be consumed by
Camel are passed through to the endpoint, who does not understand the
parameters.
Here is my code: from("rss:" + feedLocation+
"?sortEntries
21 matches
Mail list logo