Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 13 Jun 2012 14:49:42 +0000 (UTC)
From: "Willem Jiang (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <540112758.12841.1339598983407.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1071898753.12377.1339589502907.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Assigned] (CAMEL-5365) SOAPMessage to InputStream
 conversion needed for some CXF SOAPMessage Provider scenarios
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Willem Jiang reassigned CAMEL-5365:
-----------------------------------

    Assignee: Willem Jiang
    
> SOAPMessage to InputStream conversion needed for some CXF SOAPMessage Provider scenarios
> ----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5365
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5365
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cxf
>    Affects Versions: 2.9.2
>            Reporter: Aki Yoshida
>            Assignee: Willem Jiang
>            Priority: Minor
>         Attachments: trunk-camel-cxf-patch.diff
>
>
> When you have a SOAPMessage Provider based CXF endpoint in your Camel route and the message is forwarded to an input stream based processor or producer (e.g., File), it is necessary to have a converter that converts SOAPMessage into InputStream.
> It would be practical to have this conversion method included in CxfConverter.
> I am attaching a test case and a possible implementation. 
> This implementation uses CachedOutputStream to make an InputStream from a SOAPMessage. There might be a better way to get an InputStream, but I don't know a simple one.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira