camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gert Vanthienen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-179) Handling StreamSource when routing to multiple endpoints
Date Mon, 22 Oct 2007 19:24:23 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gert Vanthienen updated CAMEL-179:
----------------------------------

    Attachment: CAMEL-179.diff

This patch is a first attempt to solve this issue.  As discussed on IRC, a reusable ReReadableInterceptor
was created to make it easier to add message re-readability to e.g. the dead letter channel
afterwards.

> Handling StreamSource when routing to multiple endpoints
> --------------------------------------------------------
>
>                 Key: CAMEL-179
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-179
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.1.0
>            Reporter: Gert Vanthienen
>            Priority: Minor
>         Attachments: CAMEL-179.diff
>
>
> If the original message in the example below contains a StreamSource, the second target
in the to() will probably fail.  Auto-converting it to e.g. DOMSource should fix this...
> {code}
> from("jbi:service:urn:servicemix:tutorial:wiretap")
>          .to("jbi:endpoint:urn:servicemix:tutorial:jms:myQueue", "jbi:endpoint:urn:servicemix:tutorial:file:sender");
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message