[
http://jira.jboss.com/jira/browse/JBESB-876?page=comments#action_12373474 ]
Mark Little commented on JBESB-876:
-----------------------------------
It's certainly the case that when we have things like reliable messaging, security and
transactions the message content will be built up from the point the application hands it
off to the point it actually hits the network. But then that's really a different
message: the application shouldn't see transaction, security etc. information. It
shouldn't see EPRs either. It should only be dealing logical service names and
payloads.
But in this case, it may make sense to be consistent. Since we don't change anything
else in the Message it should be easy to not change the hdr info when the methods return.
ServiceInvoker changes To field
-------------------------------
Key: JBESB-876
URL:
http://jira.jboss.com/jira/browse/JBESB-876
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2 Milestone Release 3
Reporter: Mark Little
Assigned To: Mark Little
Fix For: 4.2.1
Intern:
"Not sure if this is a bug, but it didn't behave as I expected. If I set a To
field in the message header then the ServiceInvoker will change that as it iterates over a
series of registered eprs. Wouldn't it be better to try to keep the input message
unchanged when deliverSync/deliverAsync return? As far as I can tell, nothing else of the
input message is changed by the ESB at the sender side when it tries to deliver."
--
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