[
https://jira.jboss.org/jira/browse/JBESB-2174?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2174:
-------------------------------------
Grrr... looks like this bug was actually introduced in Jan (it was correct before that)
and then fixed again in October, hence it made it's way into the v1.0 and v1.0.1
releases.
We could run a v1.0.2 patch release if needed. On the other hand, I would have thought
that people using Smooks via the ESB would be more likely to use the ESBRouter to route to
a service (i.e. transport agnostic) and if so, that would reduce the severity of this
issue.
org.milyn.routing.jms.JMSRouter is always creating a String message
-------------------------------------------------------------------
Key: JBESB-2174
URL:
https://jira.jboss.org/jira/browse/JBESB-2174
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transformation Service
Affects Versions: 4.4 CP1
Reporter: Jaroslaw Kijanowski
When I use org.milyn.routing.jms.JMSRouter during splitting and routing I always end up
with a String message, even if I set
<param name="messageType">ObjectMessage</param> (instead of the
default value "TextMessage").
The reason for this is the creation strategy. In smooks-1.0.1,
ObjectMessageCreationStrategy creates an ObjectMessage by calling the object's
toString() method:
return session.createObjectMessage( object.toString() );
This looks fixed in smooks trunk:
return session.createObjectMessage( object );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira