[
http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344692 ]
Tom Fennelly commented on JBESB-181:
------------------------------------
Sure.
Could we eliminate those 2 notifications methods altogether and just provide a way for the
process method to attach whatever notifications it wants to add through a static set/get:
MessageAccessor.setNotification(message, new Notification(notificationObj));
....
MessageAccessor.setNotification(message, new ErrorNotification(notificationObj));
... and then in the controlling code - e.g. after the pipeline is complete ....
Notification[] notifications = MessageAccessor.getNotifications(message);
etc...
Provide a more convenient/obvious means of accessing the
"current" object on the Message Body???
------------------------------------------------------------------------------------------------
Key: JBESB-181
URL:
http://jira.jboss.com/jira/browse/JBESB-181
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: ESB Core
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Mark Little
Priority: Minor
Fix For: 4.0
ActionProcessors need to call "Message.getBody().get(CURRENT_OBJECT)" in order
to access the "current" body Object. Is this not a little obscure? Would it
not be more convenient/intuitive if the "current" object could be accessed via
something like "Message.getBody().getCurrent()" - it could wrap
"Message.getBody().get(CURRENT_OBJECT)" in the Body impl.
Also, should CURRENT_OBJECT be defined on the ActionProcessor or Body type? It's
currently defined in ActionProcessor? Of course this would mean that the current
"Message.getBody().get(CURRENT_OBJECT)" calls would all need to be modified to
"Message.getBody().get(Body.CURRENT_OBJECT)", but I'd think that is clearer
anyway.
Just some usability thoughts - feel free to delete the issus!
--
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