[
http://jira.jboss.com/jira/browse/JBESB-724?page=comments#action_12371151 ]
Daniel Bevenius commented on JBESB-724:
---------------------------------------
Just wanted to clarify that the current impl (pre my changes) also handles all properties
as Strings. This will cause problems if users have selectors that are not of type String
(byte, short, int, long, float, double).
This is what the spec says:
Values must also by set with the correct type so that selector expressions work as
expected.
For example:
myMessage.setStringProperty("NumberOfOrders", "2");
The following expression in a message selector would evaluate to false,
because a string cannot be used in an arithmetic expression:
"NumberOfOrders > 1"
I guess nonone is using selectors that are not Strings, but it might be good to know this
in case someone does try this with the current impl. Atleast we know why the selector
expressions don't work in that case.
PackageJMSMessageContents should set the appropriate ESB Message body
content to the type of JMSMessage being packaged
-----------------------------------------------------------------------------------------------------------------------
Key: JBESB-724
URL:
http://jira.jboss.com/jira/browse/JBESB-724
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
The current implementation of PackageJmsMessageContent will always package the content of
a JMSMessage as a byte array. This has the effect of the JMSRouter's property
'unwrap' extract the contents of the ESB Message object but always send a JMS
message of type BytesMessage.
Try to find a way to add this "typing" of the ESB Message contents so that I
doesn't break clients the depend on it. This sort of packaging/unpacking of
JMSMessages could be extracted into a separate class so that the same logic is used
whenever this is needed (like in NotifyJMS, JMSRouter ).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira