Hi
Have you tried with ftpClient.soTimeout also?
And what version of Camel are you using?
On Thu, May 27, 2010 at 2:06 PM, Srini97 wrote:
>
> Hello,
>
>
> I am using the following URI for the delivery to FTp end point.
>
> ftp://castrolfootb...@94.236.51.10/?fileName=srml-4-2009-squads.xml&pas
On Thu, May 27, 2010 at 7:03 PM, marcin80 wrote:
>
> Hi,
>
> I have a topic and consumer consuming messages from this topic. I'd like to
> save data from those messages to database using batch processing. I'm using
> aggregator EIP and processor like this:
>
>
>
>
>
Hi,
In camel you can get the Charset information from exchange, I just
created a JIRA[1] for it, it should be easy to fix.
[1]https://issues.apache.org/activemq/browse/CAMEL-2763
Willem
tide08 wrote:
It looks like camel-mail cannot handle unicode chars in subject header? I
have something l
Great thanks once again,
Last questions,
1) in my scenario, message have to go as a soap headed request,
is there a generic way to do so (otherwise I will do a freemaker
transformation...) ?
2) answer comes back as "base64 content"
How to have it as the text answer (with or without soap headers
It looks like camel-mail cannot handle unicode chars in subject header? I
have something like below and subject does not appear correctly in mail
client -
@Test
public void testMailSubjectWithUnicode() throws Exception {
Mailbox.clearAll();
String body = "Hello Camel Ride
Hi Claus,
Thank you for responding
by the way - hope you had a nice trip home from Frankfurt...
How would i configure an exception listener explicitly on the MQ Endpoint?
or let's say it in another way: Not that i know :-(
In the meantime i found out, that it has nothing to do with the
onExcep
Hi,
I have a topic and consumer consuming messages from this topic. I'd like to
save data from those messages to database using batch processing. I'm using
aggregator EIP and processor like this:
Hi raymond,
Fixed length format is not yet supported by bindy -->
https://issues.apache.org/activemq/browse/CAMEL-2731
I will try to work on that soon.
Kind regards,
Charles Moulliard
Senior Enterprise Architect (J2EE, .NET, SOA)
Apache Camel/ServiceMix Committer
*
Guys I have a fixed input file thus:
##H##0 FGBGH5JE20100202 0100
JBJCBD44 655F0044001106/10/2009K-50600
JBJCBD44 655F0045001124/09/2009K-50700
JBJCBD442653F0042001116/10/2009K-51300
JBJCBD60 758F0001004302/10/2009KY-1400
I wo
Hi
Have you configured an exception listener explicit on the MQ endpoint?
By debugging a simple JmsInOut unit test with embedded AMQ there is no
exeption listener set when that Requester is started.
On Thu, May 27, 2010 at 2:29 PM, waterback wrote:
>
> Hello,
>
> i've got a real ugly problem r
FYI, we just fix this kind of issue[1] in camel trunk yesterday.
[1] https://issues.apache.org/activemq/browse/CAMEL-2750
Willem
eirilwan wrote:
Hi
When upgrading from Camel 2.1.0 to 2.3.0 we encountered a problem using
Mockito to mock endpoint behaviour while testing camel routes.
Our tes
Your cxfEndpoint should be
http://192.168.5.1:9767/services/version";
wsdlURL="http://192.168.5.1:9763/services/version?wsdl";
xmlns:s="http://ws.apache.org/axis2";
serviceName="s:getVersion"
endpointName="s:versionSOAP12port1">
Hi
Can you try latest code as we have committed a fix after the 2.3 release.
On Thu, May 27, 2010 at 2:51 PM, eirilwan wrote:
>
> Hi
>
> When upgrading from Camel 2.1.0 to 2.3.0 we encountered a problem using
> Mockito to mock endpoint behaviour while testing camel routes.
>
> Our test is runni
ok,
thanks for your reply,
it allows me to go deeper and to get some new errors suggesting an endpoint
spring definition anyway.
I'm here now :
http://192.168.5.1:9767/services/version";
wsdlURL="http://192.168.5.1:9763/services/version?wsdl";
serviceName="getVersion">
Hi
When upgrading from Camel 2.1.0 to 2.3.0 we encountered a problem using
Mockito to mock endpoint behaviour while testing camel routes.
Our test is running with junit4 using Spring context configuration. We
inject mockito mocked endpoints into both the test and the route like this:
@Pro
Hello,
i've got a real ugly problem right now as i try to use the camel
onException() in my j2ee-application on a specific route on a webapp in
websphere 6.1-Server.
My Routedefinition is:
from(routeStart).
routeId("pserun.fullrun.route").
Hello,
I am using the following URI for the delivery to FTp end point.
ftp://castrolfootb...@94.236.51.10/?fileName=srml-4-2009-squads.xml&password=C3te4aVNY8fWNnGr&ftpClie
t.dataTimeout=15000&ftpClient.defaultTimeout=15000&ftpClient.connectTimeout=12&tempFileName=%24%7Bfile%3Aname.noext%7D
I created a JIRA ticket:
https://issues.apache.org/activemq/browse/CAMEL-2759
Claus Ibsen-2 wrote:
>
> Hi
>
> No that is not possible.
>
> What we need is to add support for
> /transaction[1]/@DocType = '{{doctype}}
>
> So you can use Camel expressions. And on top of that the {{ }} should
>
Thanks it works like a charm. I've tried so many different permutations but
couldn't get it to work.
janstey wrote:
>
> Try something like this:
>
>
> org.apache.camel
> camel-maven-plugin
> 2.2.0
>
>
>
>
Ok that's bad.
Destroys the point of our design atm. :)
ankelee wrote:
>
> I'd like to be able to use properties to configure different parts of my
> route to fit it to different message types. Something like this:
>
> /transaction[1]/@DocType = '{{doctype}}'
>
> But this doesn't get interp
Hi
No that is not possible.
What we need is to add support for
/transaction[1]/@DocType = '{{doctype}}
So you can use Camel expressions. And on top of that the {{ }} should
be added to the Simple language.
Fell free to create a JIRA ticket
On Thu, May 27, 2010 at 10:20 AM, ankelee wrote:
>
>
I'd like to be able to use properties to configure different parts of my
route to fit it to different message types. Something like this:
/transaction[1]/@DocType = '{{doctype}}'
But this doesn't get interpreted. Is there any way to do this?
--
View this message in context:
http://old.nabble.c
On Thu, May 27, 2010 at 9:10 AM, ankelee wrote:
>
> Oh, 2.3 was released, cool :)
>
> I redesigned the route and now has an acceptable behaviour.
>
> So what effects does that bug in onCompletion have exactly?
>
That if you change your routes that "original" file as the input on
the Exchange may
Oh, 2.3 was released, cool :)
I redesigned the route and now has an acceptable behaviour.
So what effects does that bug in onCompletion have exactly?
--
View this message in context:
http://old.nabble.com/errorHandler-%2B-.handled%28false%29%29--in-Spring-DSL.-tp28670904p28690338.html
Sent fr
24 matches
Mail list logo