You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Raul Kripalani (JIRA)" <ji...@apache.org> on 2008/10/23 15:06:52 UTC
[jira] Created: (SM-1654) Format of the Message cannot be different
than XML within Camel
Format of the Message cannot be different than XML within Camel
---------------------------------------------------------------
Key: SM-1654
URL: https://issues.apache.org/activemq/browse/SM-1654
Project: ServiceMix
Issue Type: Bug
Components: servicemix-camel
Affects Versions: 3.2.2
Reporter: Raul Kripalani
Priority: Blocker
Please see: http://www.nabble.com/XStream-with-JBI-td20129124s22882.html
This is due to the limitation imposed by the JbiExchange class, since its messages can only be NormalisedMessage objects, which in turn can only have XML Bodies.
This is issue blocks development with many Camel components, such as XStream, iBATIS, or, in general, any component that requires a Java Object, CSV file, etc. instead of XML to operate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1654) Format of the Message cannot be
different than XML within Camel
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SM-1654.
---------------------------------
Assignee: Gert Vanthienen
Fix Version/s: 3.3.1
Resolution: Fixed
Fixed in
- http://svn.eu.apache.org/viewvc?view=rev&revision=708120 for components' trunk
- http://svn.eu.apache.org/viewvc?view=rev&revision=708121 for smx 3.2 branch
> Format of the Message cannot be different than XML within Camel
> ---------------------------------------------------------------
>
> Key: SM-1654
> URL: https://issues.apache.org/activemq/browse/SM-1654
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-camel
> Affects Versions: 3.2.2
> Reporter: Raul Kripalani
> Assignee: Gert Vanthienen
> Priority: Blocker
> Fix For: 3.3.1
>
>
> Please see: http://www.nabble.com/XStream-with-JBI-td20129124s22882.html
> This is due to the limitation imposed by the JbiExchange class, since its messages can only be NormalisedMessage objects, which in turn can only have XML Bodies.
> This is issue blocks development with many Camel components, such as XStream, iBATIS, or, in general, any component that requires a Java Object, CSV file, etc. instead of XML to operate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.