That works quite well actually. What would be good though is if we could find a
better name for the beforeWrap, something that communicates the intent,
something like updateDefinitions, something that would be more intuitive about
how the interface should be used. Yeah, not easy to come with the
On Wed, Jul 7, 2010 at 9:46 AM, Hadrian Zbarcea wrote:
> That works quite well actually. What would be good though is if we could find
> a better name for the beforeWrap, something that communicates the intent,
> something like updateDefinitions, something that would be more intuitive
> about h
Fair enough, let's do that. I think beforeWrap is actually better though. And
then we document how it could/should be used.
On Jul 7, 2010, at 3:51 AM, Claus Ibsen wrote:
> On Wed, Jul 7, 2010 at 9:46 AM, Hadrian Zbarcea wrote:
>> That works quite well actually. What would be good though is if
On Wed, Jul 7, 2010 at 10:07 AM, Hadrian Zbarcea wrote:
> Fair enough, let's do that. I think beforeWrap is actually better though. And
> then we document how it could/should be used.
>
Yeah great. There is already javadoc documentation.
But maybe we should add a wiki page about Policy and Defi
Hi,
I want to operate in charset iso-8859-1 in my route because of some special
characters. Therefore I do at the start of my routes. I also do
exchange.setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
As long as JAXB is not involved this works fine. I can do
xslt-transformations etc. and the
Thanks Claus,
I can do it in the morning. It got kinda late.
Hadrian
On Jul 7, 2010, at 4:17 AM, Claus Ibsen wrote:
> On Wed, Jul 7, 2010 at 10:07 AM, Hadrian Zbarcea wrote:
>> Fair enough, let's do that. I think beforeWrap is actually better though.
>> And then we document how it could/shoul
On Wed, Jul 7, 2010 at 10:28 AM, Hadrian Zbarcea wrote:
> Thanks Claus,
>
> I can do it in the morning. It got kinda late.
>
I took the liberty to commit the changes in the trunk. What's missing
is wiki documentation.
Please take a look at the code to see if there is anything you can
spot that's
Which version of Camel are you using?
xslt-transformation will use "UTF-8" the by default, and you can change
it by setting the system property for it, but it relates to the Camel
version that you are using.
Willem
--
Apache Camel, Apache CXF committer
Open SOA
I'm using 2.3.
I thought setting CHARSET_NAME would instruct JAXB to use the encoding set
there?
"In Camel 1.6.1 and newer you can set the encoding option to use when
marshalling. Its the Marshaller.JAXB_ENCODING encoding property on the JAXB
Marshaller.
You can setup which encoding to use when
Hi Claus,
I've been doing some additional testing. First off, as the FTP server I need
to code against is external, I tried setting up a local FTP (using
FileZilla), and connect to that and transfer/delete files in the exact same
way. - This worked like a charm.
I then proceded to try against th
Hi
Can you try not to write the consumed FTP to a File endpoint.
Instead just do
from(ftp?delete=true).to("log:foo");
Just to see that if you download and write to a file causes any
mysterious issues.
On Wed, Jul 7, 2010 at 12:39 PM, Morten Engel wrote:
>
> Hi Claus,
>
> I've been doing some
Hmm, maybe I was to hastily to reply and file the issue yesterday. It turned
out that there is also a connection timeout on the JCH
http://grepcode.com/file/repo1.maven.org/maven2/com.jcraft/jsch/0.1.42/com/jcraft/jsch/Channel.java#Channel.connect%28int%29
Channel class, which is super class to
This resulted in the exact same log pattern on my side, except the 4 lines
below missing:
11:47:49,906 | TRACE | 0: FtpComponent | GenericFileProducer |
mponent.file.GenericFileProducer 69 | Processing Exchange[Message:
GenericFile[test3.txt]]
11:47:49,906 | TRACE | 0: FtpCompone
Hello Willem, hello Christian!
Thanks a lot for your help. I modified my setUpBeforeClass method to:
@BeforeClass
public static void setUpBeforeClass() {
// start a simple CXF server
ServerFactoryBean svrBean = new ServerFactoryBean();
svrBean.setAddress("http://lo
I checked somewhere that we can add maxInactivityDuration option to the
activeMQ URL
ie.
wireFormat.maxInactivityDuration=0
brokerconnection
=tcp://dev01.sportingstatz.com:61616?wireFormat.maxInactivityDuration=0
will this solves the above above problem.
--
View this message in context:
ht
Ok, in general I understand the source code shown on pages like:
http://camel.apache.org/walk-through-an-example.html
But the result is just a source code.
What to do next?
I guess I have to compile with something like
javac CamelJmsToFileExample.java
I will get a *.class file (or do I h
That's odd and should be fixed. Please create a JIRA ticket plus a small unit
test case (or sample app) for reproducing your findings.
Thanks,
Martin
--
View this message in context:
http://camel.465427.n5.nabble.com/Resequence-Stream-ConcurrentModificationException-tp524555p1044698.html
Sent
What you could also try is to increase the timeout. It is currently set to
100ms. Every two out-of-order messages separated by more than 100 ms in time
cannot be resequenced properly then. Try using 3000 ms, for example. Does
that help?
--
View this message in context:
http://camel.465427.n5.nab
Hi
You can use wireshark or something to trace what gets send over the network.
Then you can check that DELETE being sent or not.
Also on Camel 2.4 we have fixed an issue with using absolute paths.
Many FTP clients sends file paths using absolute, eg they start with a /
Maybe that remote FTP serv
No matter what I do the marshaller complains about:
java.io.UTFDataFormatException: Invalid byte 1 of 1-byte UTF-8 sequence.
I set these values:
System.setProperty("org.apache.camel.default.charset", "iso-8859-1");
exchange.setProperty(Exchange.CHARSET_NAME, "iso-8859-1");
And the marshaller
Hi
You should maybe try to ask / get the attention of the JSCH team.
I think bengt (A camel user) did that when he found an issue with
using private keys and something else.
So they are there.
On Wed, Jul 7, 2010 at 1:13 PM, Mattias Severson wrote:
>
> Hmm, maybe I was to hastily to reply and
Hi,
First, thanks for your help last time and thanks to the authors of "Camel
in Action"; this is a great book.
After solving my last problem - which was entirely my fault btw - I now
try to design a bigger project.
I'm trying to rewrite a project I've made some time ago.
It used BPEL, EJB's (bo
Hi
Sometimes its easier to use a bit of Java code.
If you read chapter 10 about the async client API you can from a
Processor / Bean just send the Exchange to the webservice endpoint
uri.
And then use the Future handle to wait with timeout.
Then you know if the Exchange was done without the timeo
Hi Claus,
I've installed Wireshark on the server, and have found that it sends the
delete request every time, but gets the response
238 24.617119 192.168.98.84 195.215.57.203 FTP Request: DELE
Export/test3.txt
239 24.617963 195.215.57.203 192.168.98.84 FTP Respo
Oh, I should probably add, that it seems the files are being referenced to
the same way on RETR and DELE, an example of a RETR line (which works fine)
is :
305 27.250223 192.168.98.84 195.215.57.203 FTP Request: RETR
Export/test3.txt
I'm guessing it's not a question of relative/
On Wed, Jul 7, 2010 at 5:23 PM, Morten Engel wrote:
>
> Oh, I should probably add, that it seems the files are being referenced to
> the same way on RETR and DELE, an example of a RETR line (which works fine)
> is :
>
> 305 27.250223 192.168.98.84 195.215.57.203 FTP Request: RETR
Again, a good call. This definatly highlighted odd behaviour.
Trying to delete from windows server 2003, (the server running FUSE) via
file explorer, resulted in a 550 access is denied pop up. (Machine A, for
reference)
Deleting the exact same file, with the same credentials, and the same method
You need to be a subscriber of the Camel mailinglist before the mails are
send to the list.
Otherwise the mails dont get forwarded to the mailinglist, and we the
subscribers cant see your mails and frankly dont want to mess with using
nabble to reply.
--
View this message in context:
http://cam
On Wed, Jul 7, 2010 at 2:52 PM, benxs wrote:
>
> Ok, in general I understand the source code shown on pages like:
>
> http://camel.apache.org/walk-through-an-example.html
>
> But the result is just a source code.
> What to do next?
>
> I guess I have to compile with something like
>
> javac C
You have to be a subscriber of the Camel mailinglist to be able to post and
have nabble forward those posts to the actual mailinglist.
If you dont do this your post will only show up in Nabble
--
View this message in context:
http://camel.465427.n5.nabble.com/Spring-remoting-proxy-call-from-wit
You have to be a subscriber of the Camel mailinglist to be able to post and
have nabble forward those posts to the actual mailinglist.
If you dont do this your post will only show up in Nabble
--
View this message in context:
http://camel.465427.n5.nabble.com/Injecting-Properties-into-the-Prop
The component is quite nice - however a good improvement would be allowing
properties to be injected through Spring.
Currently there are two ways to do this using Spring.
1) Declare a bean with an id of properties:
This would be improved if we could simply say:
This wou
32 matches
Mail list logo
