camel SFTP endpoint Exception if connection was closed

Hi, If the camel sftp component creates a connection to a server (when a message is sent to an SFTP endpoint) and then the server closes the connection (e.g. because the server is restarted or it closes the connection for other reasons (like a timeout)) the next message sent to this endpoint

Platform specific tests (CAMEL-6854)

Hi, when fixing the issue in CAMEL-6854 we have created a change in the test in a way that will recreate the described issue, however only on Windows (or a different platform where the platform encoding is not UTF-8). On a UNIX or Linux platform with UTF-8 default encoding the test will

JIRA component for camel-base64

Hi, I just submitted a minor extension to the camel-base64 component (https://issues.apache.org/jira/browse/CAMEL-7056 ). However there is no component in JIRA for this. What component should I assign to this JIRA task? Maybe camel-core? Best regards Stephan

Expected behaviour of camel-ahc component concerning headers

Hi, The documentation of the camel-ahc component (http://camel.apache.org/ahc.html ) says: Message Body Camel will store the HTTP response from the external server on the OUT body. All headers from the IN message will be copied to the OUT message, so headers are preserved during routing.

RE: Expected behaviour of camel-ahc component concerning headers

a bug, so it didn't find the bug in the component. I created a JIRA bug (https://issues.apache.org/jira/browse/CAMEL-7363) and attached a rather trivial patch to it (one line for the test and one line for the component...). Best regards Stephan -Original Message- From: Siano, Stephan

RE: Apache Camel 2.13.1 released

Hi Willem, I don't want to be too picky about this, but isn't this a patch release (not a major release)? Best regards Stephan -Original Message- From: Willem Jiang [mailto:willem.ji...@gmail.com] Sent: Mittwoch, 14. Mai 2014 04:28 To: us...@camel.apache.org; dev@camel.apache.org

CAMEL-8091

Hi, I am aware that Willem is quite busy, but could anyone have a look at CAMEL-8091? It's about considering Exchange.LOG_DEBUG_BODY_MAX_CHARS in the DefaultExchangeFormatter. The patch is really easy to understand (only about 10 lines plus unit test). Best regards Stephan

RE: CAMEL-8091

://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On December 8, 2014 at 2:26:47 PM, Siano, Stephan (stephan.si...@sap.com) wrote: Hi, I am aware that Willem is quite busy, but could anyone have a look at CAMEL-8091? It's about

RE: Question about type converter logic

can add a type converter to camel-saxon that converts a NodeInfo to DOMSource which Camel ought to use then. On Tue, Jan 13, 2015 at 8:12 AM, Siano, Stephan stephan.si...@sap.com wrote: Hi, I am trying to figure out how to write a type converter that can convert e.g. from

Question about documentType in XPathBuilder

Hi, If you look into the XPathBuilder in camel (actually the doInEvaluateAs() method), you see that the data that the evaluated with the XPath expression (a header or the body) is first converted into a data type defined in the documentType attribute of the XPath builder. Afterwards the

RE: Question about documentType in XPathBuilder

Hi Claus, Ok that does really look easy, I will prepare a patch and append it to the JIRA task. However I didn't manage to find any tests for that. In org.apache.camel.language are only tests using the Java DSL and in org.apache.camel.model and I didn't find any XPath related tests. Do you

RE: Question about documentType in XPathBuilder

Hi Claus, Ok, thanks. I didn't find anything in camel-jaxb, but camel-saxon does indeed contain some XML configurations for XPath. I extended the tests there and attached the patch to https://issues.apache.org/jira/browse/CAMEL-8182 . Is this ok? Best regards Stephan

Question about XPath builder and BeanInvocation

Hi, I have written some extension for the XPathBuilder ( https://issues.apache.org/jira/browse/CAMEL-8273 ). While doing so, I stumbled over the following code: // okay we can try to remedy the failed conversion by some special types if (answer == null) { // let's

Question about type converter logic

Hi, I am trying to figure out how to write a type converter that can convert e.g. from net.sf.saxon.om.NodeInfo to DOMSource. The problem with this is that the NodeInfo implements

RE: Question about type converter logic

[mailto:claus.ib...@gmail.com] Sent: Dienstag, 13. Januar 2015 08:16 To: dev Subject: Re: Question about type converter logic You can add a type converter to camel-saxon that converts a NodeInfo to DOMSource which Camel ought to use then. On Tue, Jan 13, 2015 at 8:12 AM, Siano, Stephan stephan.si...@sap.com

RE: [VOTE] Release Camel 2.14.1

Ibsen [mailto:claus.ib...@gmail.com] Sent: Montag, 2. März 2015 08:27 To: dev Subject: Re: [VOTE] Release Camel 2.14.1 On Mon, Mar 2, 2015 at 8:22 AM, Siano, Stephan stephan.si...@sap.com wrote: Hi, The version does still contain the XXE vulnerability for XPath and the XmlConverter (CAMEL

RE: [VOTE] Release Camel 2.14.1

Hi, The version does still contain the XXE vulnerability for XPath and the XmlConverter (CAMEL-8311 and CAMEL-8312). I think this is about as serious as the issues from CVE-2014-0002 and CVE-2014-0003, so these two patches should really be in there. -1 (non binding) Best regards Stephan

RE: StreamCache for CxfPayload

shortly.   -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On February 25, 2015 at 5:12:19 PM, Siano, Stephan (stephan.si...@sap.com) wrote: Hi, The CxfPayload

StreamCache for CxfPayload

Hi, The CxfPayload data type (from camel-cxf) contains some stream elements but does not support stream caching. I am working on a contribution to provide stream caching for that. During that if found some strange things in the CxfPayloadConverter: If the CxfPayloadConverter converts a

data format for MIME-Multipart

Hi, I have written a data format that can convert a Camel message with attachments into a Camel message having a MIME-Multipart message as message body (and no attachments). The use case for this is to enable the user to send attachments over endpoints that do not directly support attachments,

RE: data format for MIME-Multipart

. See how to run with that at: http://camel.apache.org/building.html Otherwise it seems likely good. I put it on the roadmap for next 2.17 release. Are you able to work on documentation as well? Are you able to edit the wiki directly? On Wed, Nov 11, 2015 at 8:53 AM, Siano, Stephan <stephan.si...@sap.com>

RE: data format for MIME-Multipart

Hi, Sorry for nagging but I haven't received any feedback so far. Is the patch in the JIRA task ok or is there something wrong with it? Best regards Stephan -Original Message- From: Siano, Stephan [mailto:stephan.si...@sap.com] Sent: Montag, 2. November 2015 17:00 To: dev

RE: data format for MIME-Multipart

Hi, Any feedback on this? Do you think I should contribute this into camel-mail, into a new component or not at all? Best regards Stephan -Original Message- From: Siano, Stephan [mailto:stephan.si...@sap.com] Sent: Montag, 26. Oktober 2015 14:51 To: dev@camel.apache.org Subject: data

RE: data format for MIME-Multipart

Hi Claus, I have created https://issues.apache.org/jira/browse/CAMEL-9283 for it. Best regards Stephan -Original Message- From: Siano, Stephan [mailto:stephan.si...@sap.com] Sent: Montag, 2. November 2015 12:55 To: dev@camel.apache.org Subject: RE: data format for MIME-Multipart Hi

RE: data format for MIME-Multipart

on the code and when you are ready then you know how to contribute. http://camel.apache.org/contributing On Mon, Oct 26, 2015 at 2:51 PM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi, > > I have written a data format that can convert a Camel message with > attachments in

RE: Changing a single component version

Hi, This depends on what you are intending to do with the change. If you just want to do *test* the new feature with a released version you might build the version locally without changing the version at all. Obviously you cannot push that to any nexus or send it to anybody else without

RE: Avoid file transferring in [dos] file format in camel-ftp

Hi, I guess, your problem is different: The file is already containing DOS CRs and you want to convert it to UNIX linefeeds. It may work if you set binary to false (this should at least work for FTP), but AFAIK unlike for FTP, for SFTP the binary (and also the passive) parameters do not do

Support for attachment headers in Camel 2.x

Hi, Sorry for bringing this up again, but I have received no feedback at all about this topic yet. The current attachment support in Camel 2.x is essentially a Map. As such it can transport the attachment body (in the DataHandler), the Content-Type (also in the

RE: Premature End Of File Error in XML

Hi, I guess your log statement reads the body. If the body returned by your http endpoint is a stream and you do not have stream caching enabled on your route the stream will be read and the body will be empty afterwards. The XML parser used to process your XSLT mapping will then get an empty

Concerning Attachments and Attachment Headers in Camel

Hi, Is there anybody available in this list who knows why the attachment handling in Camel is as it is? I have had a look into this topic with the Camel-Mail and Camel-CXF components and would like to discuss my thoughts about that. In General the attachment handling is designed to support

RE: copyTo for mail producer

Hi, The SMTP producer is actually sending mail via SMTP. This protocol has no idea of anything like folders or the like. The component has no notion of outlook servers. I am not sure how open the outlook protocol is and if javamail supports that (I would guess it doesn't), so I actually do

RE: Concerning Attachments and Attachment Headers in Camel

Camel On Mon, Apr 11, 2016 at 7:45 AM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi Claus, > > I tend to disagree on that. I actually think that having a generic Attachment > API in Camel does make sense. Having Attachments only as part of MailMessage > and e.g. a (curr

RE: Apache camel mime-multipart usage and examples?

Hi, Have you tried PAYLOAD mode? I don't know which JBOSS FUSE version will contain Camel 2.17 (that one is pretty new). Anyway, I noticed yesterday that there is a bug in the 2.17.0 MIME-Multipart decoder that will prevent your multipart from being processed (because the attachment doesn't

RE: Apache camel mime-multipart usage and examples?

Hi, Which camel version are you using? MIME-Multipart is only available starting Camel 2.17.0. I am not 100% sure, but your response looks somewhat like SOAP with attachments or MTOM. If you are using some kind of Camel-CXF endpoint for receiving it, the endpoint might parse it for you. Best

RE: Concerning Attachments and Attachment Headers in Camel

eaders in Camel On Thu, Apr 7, 2016 at 2:42 PM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi, > > Is there anybody available in this list who knows why the attachment handling > in Camel is as it is? > > I have had a look into this topic with the Camel-Mail and Camel-CX

Camel build, tests and charsets

Hi, I have found an issue with the camel-csv component. The fix itself is pretty trivial (a one-liner to use the IOHelper.getCharsetName(exchange)) for an OutputStreamWriter in the marhaller (the InputStreamWriter in the unmarshaller already does this). However I have some difficulties with

RE: Concerning Attachments and Attachment Headers in Camel

-Original Message- From: Siano, Stephan [mailto:stephan.si...@sap.com] Sent: Montag, 18. April 2016 16:48 To: dev@camel.apache.org Subject: RE: Concerning Attachments and Attachment Headers in Camel Hi Claus, I have evaluated three different approaches to add attachment headers to Camel 2.18

Please grant karma to edit the Wiki

Hi, could you please grant karma to edit the Camel documentation to my wiki username stephan.siano? The ICLA has already been received in the past. Best regards Stephan

RE: Please grant karma to edit the Wiki

Thanks a lot. -Original Message- From: Claus Ibsen [mailto:claus.ib...@gmail.com] Sent: Dienstag, 24. Mai 2016 10:39 To: dev <dev@camel.apache.org> Subject: Re: Please grant karma to edit the Wiki Hi I have granted you karma On Tue, May 24, 2016 at 10:30 AM, Siano, Stephan <s

RE: Camel build, tests and charsets

arsets Is it "Lucky Luke" that has non ASCII chars? You can use \u to specify non ascii chars. We do that in some unit tests. I remember we have some for german, and also for the Thai elephant which is named Chang, which is a good beer btw ;) On Fri, Apr 29, 2016 at 2:49 PM, Siano, Ste

RE: Camel build, tests and charsets

May 2, 2016 at 7:41 AM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi Claus, > > Ok, this solves the string definition issue, however the platform encoding > issue is somewhat more difficult. For the specific use case I might find a > way around the issue, but in gen

RE: Concerning Attachments and Attachment Headers in Camel

To: dev <dev@camel.apache.org> Subject: Re: Concerning Attachments and Attachment Headers in Camel On Thu, Apr 14, 2016 at 2:51 PM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi Claus, > > I have filed CAMEL-9868 for the Camel 3.0 changes. > > I will try out both opt

RE: Concerning Attachments and Attachment Headers in Camel

4. April 2016 09:49 To: dev <dev@camel.apache.org> Subject: Re: Concerning Attachments and Attachment Headers in Camel On Wed, Apr 13, 2016 at 11:51 AM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi Claus, > > Sorry for the late reply, but I had to do some thinking about th

RE: Concerning Attachments and Attachment Headers in Camel

hments and Attachment Headers in Camel Hi Yeah both approaches are doable. But I think the first one is the least invasive and fits 2.x the best. On Thu, Apr 14, 2016 at 11:19 AM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi Claus, > > OK, I will file a JIRA task for Camel 3.0 to re

RE: [DISCUSS] Reusing Exclusive ReplyTo Queue..

Hi James, I am not sure whether I understand the context. Are you talking about request/reply over JMS with the camel-jms component? In that case the replyToDestinationSelectorName parameter might help you with shared reply to queues. I actually do not see any impact that may have on

RE: [DISCUSS] Reusing Exclusive ReplyTo Queue..

[mailto:ja...@carmanconsulting.com] Sent: Mittwoch, 13. Juli 2016 13:11 To: dev@camel.apache.org Subject: Re: [DISCUSS] Reusing Exclusive ReplyTo Queue.. Shared uses selectors. There's no reason to use selectors in my case On Wed, Jul 13, 2016 at 6:31 AM Siano, Stephan <stephan.si...@sap.com>

RE: [DISCUSS] Attachment Headers

d your proposals and very good with the pros/cons of them. Yeah I also think its better to go with #3 so we get a better solution for this which we carry forward for Camel 3, and have @deprecated the old api on 2.x. +1 for option #3. On Mon, Jul 11, 2016 at 3:31 PM, Siano, Stephan <stephan.si..

RE: [DISCUSS] Attachment Headers

l You are welcome to create a new wiki page with more details, such as the heads up email you wrote, and then link from the release notes to this wiki page. On Tue, Jul 19, 2016 at 12:55 PM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi Claus, > > How do I provide input for t

[HEADS UP] Extensions for attachments in master branch

Hi, I have just checked an extension for the attachment handling into the master (2.18) branch. As long as you don't use attachments you will very likely not notice any difference. If you have created an implementation of the Message interface that does not extend DefaultMessage, you will

RE: [DISCUSS] Attachment Headers

auling and improving our documentation on the online Camel website. On Mon, Jul 18, 2016 at 2:51 PM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi Claus, > > Thank you for your feedback. I have polished the code a little in order to be > submitted (added support

Camel.trunk.notest build job

Hi, After my commit yesterday I got a mail that the Camel.trunk.notest job failed. On a first look I found out that it failed with an OOM in the camel-olingo component (so I would guess that it is completely unrelated to any recent check-in but more like a job-setup issue). On a second look I

RE: [DISCUSS] Reusing Exclusive ReplyTo Queue..

jms:queue:bar?replyToType=Exclusive=REPLIES=5 Right now, this doesn't work. Is there any reason folks can think of that we wouldn't or couldn't support such a thing? On Tue, Jul 12, 2016 at 1:50 AM Siano, Stephan <stephan.si...@sap.com> wrote: > Hi James, > > I am not sure whether I underst

RE: [DISCUSS] Attachment Headers

Hi, Unfortunately I have received no feedback about this so far. If nobody objects I will go on with the implementation for option 3 and check that into the master branch sometime next week. If anybody here has doubts about this please speak up! Best regards Stephan -Original

[DISCUSS] HTTP session handling in Camel routes

Hi, is there some kind of holistic concept for HTTP session handling (for HTTP based producer endpoints) in Camel? I managed to find basic HTTP session handling in the following camel component: - The camel-http4 component allows injecting a org.apache.http.client.CookieStore to the

RE: [DISCUSS] HTTP session handling in Camel routes

that is somewhat of limited use. What would you propose how to document the overall feature? Best regards Stephan -Original Message- From: Siano, Stephan [mailto:stephan.si...@sap.com] Sent: Montag, 17. Oktober 2016 13:09 To: dev@camel.apache.org Subject: RE: [DISCUSS] HTTP session handling

RE: [DISCUSS] HTTP session handling in Camel routes

en you would need to implement this in more of them, and not only a limited set. On Fri, Oct 14, 2016 at 7:24 AM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi, > > I have not received any feedback so far, so I assume that there is at least > nobody strongly against t

RE: Adding type awareness in Camel route

it is probably very hard to implement. Best regards Stephan -Original Message- From: Tomohisa Igarashi [mailto:tm.igara...@gmail.com] Sent: Montag, 17. Oktober 2016 16:51 To: dev@camel.apache.org Subject: Re: Adding type awareness in Camel route Hi, On 10/17/2016 03:32 PM, Siano, Stephan

RE: [DISCUSS] HTTP session handling in Camel routes

2016 08:55 To: Siano, Stephan <stephan.si...@sap.com>; dev@camel.apache.org Subject: Re: [DISCUSS] HTTP session handling in Camel routes Hello Stephan, To preview the docs and all the links just run mvn clean install into camel-website folder. You'll have the Gitbook site running locall

RE: [DISCUSS] HTTP session handling in Camel routes

--- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, October 20, 2016 9:09 AM, "Siano, Stephan" <stephan.si...@sap.com> wrote: Hi, The JIRA task is https://issues.apache.org/ji

RE: New feature GROK parser

Hi, I think that depends on what the component is supposed to do. If the semantics is that you extract values that are supposed to be used as an expression or a predicate to be used in patterns like message router or a message filter a language might be appropriate. In contrast to that a

RE: [DISCUSS] HTTP session handling in Camel routes

Hi, I have not received any feedback so far, so I assume that there is at least nobody strongly against this feature. Maybe I can sketch what I would like to implement and ask some questions about implementation details. I would create an interface (CamelCookieHandler and two implementation

RE: Adding type awareness in Camel route

Hi, I am not sure if I really understand the concept behind this. Is there any text about the general ideas behind these changes? If I got this right, you propose that endpoints declare a kind of data type that can be verified as input and output types (like a specific XML schema) and the

RE: [DISCUSS] HTTP session handling in Camel routes

Oct 17, 2016 at 10:58 AM, Siano, Stephan <stephan.si...@sap.com> wrote: > Hi Claus, > > Having the interface (and implementations) in camel-http-common makes sense > to me. This means that all the components below would have a dependency to > camel-http-common. Does this make s

Flaw in exchange scope for HTTP-Session-Handling

Hi, I have found a flaw in the HTTP-Session Handling I implemented some time ago: If all the endpoints supporting HTTP-Session Handling are called in a multicast and the scope of the session is supposed to be the exchange, this will not work as expected. See the following examples:

RE: Camel 4 roadmap and affect on Camel 3

Hi, Actually removing the OSGi manifests from the bundles coming from the general camel build would mean that we have to create an OSGi wrapper bundle for each and every jar coming out of the general build, which looks like a lot of maintenance effort to me. Best regards Stephan