[jboss-jira] [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
Mark Little (JIRA)
jira-events at jboss.com
Thu Oct 5 11:07:41 EDT 2006
[ http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344690 ]
Mark Little commented on JBESB-181:
-----------------------------------
We could add an accessor.
If we change the notifications for Error and OK to return messages too then I'd assume we would have different indexes into the message for these too.
> 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
More information about the jboss-jira
mailing list