]
David Ward updated JBESB-3234:
------------------------------
Summary: NotifyTCP assumes payload is character based (was: NotifyTCP assumes payload
is characher based)
NotifyTCP assumes payload is character based
--------------------------------------------
Key: JBESB-3234
URL:
https://jira.jboss.org/browse/JBESB-3234
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.7
Reporter: Tom Fennelly
Assignee: David Ward
Priority: Minor
Fix For: 4.9
org.jboss.soa.esb.notification.NotifyTCP assumes the message payload is a String
(explicitly, or encoded as a byte[]). No need to make such a restrictive assumption. If
it's a byte payload, just send it out onto the target socket as raw bytes - will work
for any encoded payload type then.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: