You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Jérémie Brébec (JIRA)" <ji...@apache.org> on 2010/10/23 18:18:40 UTC

[jira] Created: (CAMEL-3269) CXF CamelTransport and "Can't find input stream in message"

CXF CamelTransport and "Can't find input stream in message"
-----------------------------------------------------------

                 Key: CAMEL-3269
                 URL: https://issues.apache.org/activemq/browse/CAMEL-3269
             Project: Apache Camel
          Issue Type: Bug
          Components: camel-cxf
    Affects Versions: 2.4.0
            Reporter: Jérémie Brébec
            Priority: Minor


When using a JaxWS proxy with camel transport, to a route with only one processor, CXF fail with the message "Can't find input stream in message".

CamelConduit call CxfMessageHelper.getCxfInMessage which is looking for an Out part in the exchange. If the processor of the route doesn't use the Out message, or doesn't copy the in part to the out part (like the Pipeline processor), the call to the JaxWS proxy fail with "Can't find input stream in message"

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

[jira] Resolved: (CAMEL-3269) CXF CamelTransport and "Can't find input stream in message"

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CAMEL-3269.
---------------------------------

    Resolution: Fixed

Applied the patch in reversion 1029558 with thanks to Jeremie.

> CXF CamelTransport and "Can't find input stream in message"
> -----------------------------------------------------------
>
>                 Key: CAMEL-3269
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3269
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.4.0
>            Reporter: Jérémie Brébec
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 2.6.0
>
>         Attachments: camel-cxf.patch
>
>
> When using a JaxWS proxy with camel transport, to a route with only one processor, CXF fail with the message "Can't find input stream in message".
> CamelConduit call CxfMessageHelper.getCxfInMessage which is looking for an Out part in the exchange. If the processor of the route doesn't use the Out message, or doesn't copy the in part to the out part (like the Pipeline processor), the call to the JaxWS proxy fail with "Can't find input stream in message"

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

[jira] Updated: (CAMEL-3269) CXF CamelTransport and "Can't find input stream in message"

Posted by "Jérémie Brébec (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jérémie Brébec updated CAMEL-3269:
----------------------------------

    Attachment: camel-cxf.patch

A simple patch with a JUnit testcase for this issue

> CXF CamelTransport and "Can't find input stream in message"
> -----------------------------------------------------------
>
>                 Key: CAMEL-3269
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3269
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.4.0
>            Reporter: Jérémie Brébec
>            Priority: Minor
>         Attachments: camel-cxf.patch
>
>
> When using a JaxWS proxy with camel transport, to a route with only one processor, CXF fail with the message "Can't find input stream in message".
> CamelConduit call CxfMessageHelper.getCxfInMessage which is looking for an Out part in the exchange. If the processor of the route doesn't use the Out message, or doesn't copy the in part to the out part (like the Pipeline processor), the call to the JaxWS proxy fail with "Can't find input stream in message"

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

[jira] Updated: (CAMEL-3269) CXF CamelTransport and "Can't find input stream in message"

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-3269:
-------------------------------

    Fix Version/s: 2.6.0
         Assignee: Willem Jiang

> CXF CamelTransport and "Can't find input stream in message"
> -----------------------------------------------------------
>
>                 Key: CAMEL-3269
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3269
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.4.0
>            Reporter: Jérémie Brébec
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 2.6.0
>
>         Attachments: camel-cxf.patch
>
>
> When using a JaxWS proxy with camel transport, to a route with only one processor, CXF fail with the message "Can't find input stream in message".
> CamelConduit call CxfMessageHelper.getCxfInMessage which is looking for an Out part in the exchange. If the processor of the route doesn't use the Out message, or doesn't copy the in part to the out part (like the Pipeline processor), the call to the JaxWS proxy fail with "Can't find input stream in message"

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