[
https://issues.apache.org/jira/browse/CAMEL-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977335#action_12977335
]
Hadrian Zbarcea commented on CAMEL-3133:
----------------------------------------
Camel uses the convention that the next in is the previous out (if any) or
previous in otherwise. So the camel way of defining void is really an null
output.
However in this case, especially because it is possible to have not only one
bean invoked, but many between unmarshall and marshall (and other processors as
well), my take would be to add a property on the Exchange during unmarshall
that identifies the soap method, so that during marshall you can use it do
serialize the bean output (if any) into the right type, and perform an
automatic type conversion if necessary (and available) as well.
> Camel soap dataformat does not work correctly if a method has no input or no
> output
> -----------------------------------------------------------------------------------
>
> Key: CAMEL-3133
> URL: https://issues.apache.org/jira/browse/CAMEL-3133
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: camel-soap-3133.patch
>
>
> Currently the camel soap dataformat can not handle exachanges for a soap
> method that has no input or no output. This is a known limitation but we
> should support this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
