[JBoss JIRA] Created: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
6:34 a.m.
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
6:55 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344681 ]
Mark Little commented on JBESB-181:
-----------------------------------
There's no notion of "current object" in a generic message. It is up to each
component where it puts the relevant information in the message. The notion of
"current object" in the ActionProcessors work is simply a convenient term, I
believe. It is not relevant to Message.
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
8:37 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ http://jira.jboss.com/jira/browse/JBESB-181?page=all ]
Tom Fennelly closed JBESB-181.
------------------------------
Resolution: Done
closed
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
9:25 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344687 ]
Mark Little commented on JBESB-181:
-----------------------------------
One possible modification that might clarify things would be to rename
public static final String
CURRENT_OBJECT="org.jboss.soa.esb.actions.current.object";
to something like
public static final String PROCESSING_ELEMENT
="org.jboss.soa.esb.actions.processingElement";
or
public static final String PROCESSING_ENTRY
="org.jboss.soa.esb.actions.processingEntry";
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
9:34 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344688 ]
Tom Fennelly commented on JBESB-181:
------------------------------------
And yet another option might be to define a static inner class in the ActionProcessor
interface such that ActionProcessor to provide "helper" type methods for
accessing message components e.g.
ActionProcessor.MessageAccessor.setProcessingObject(message, object);
...
Object processingObj = ActionProcessor.MessageAccessor.getProcessingObject(message);
... so the static string is completely hiden and the getting and setting are centrally
managed... in fact, we could change where we store it in the future (should we decide to
do that) and no ones code would break (in theory ;-) )
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
9:37 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344689 ]
Tom Fennelly commented on JBESB-181:
------------------------------------
And of course, that "MessageAccessor" class doesn't have to be an inner
class of the ActionProcessor interface... putting it in there though does scope the type
in a way - scope is the wrong word there but you know what I mean ;-)
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
10:07 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ 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
10:19 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ 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
10:22 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344693 ]
Tom Fennelly commented on JBESB-181:
------------------------------------
Of course that should be "addNotification"
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
10:22 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344695 ]
Mark Little commented on JBESB-181:
-----------------------------------
OK, now we're into design discussions that should be carried out on the forum ;-)
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
10:34 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344700 ]
Tom Fennelly commented on JBESB-181:
------------------------------------
Just shoot'n the breeze... sorry
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
10:37 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-181) Provide a more convenient/obvious means of accessing the "current" object on the Message Body???
[ http://jira.jboss.com/jira/browse/JBESB-181?page=comments#action_12344702 ]
Mark Little commented on JBESB-181:
-----------------------------------
No, I meant: let's take it to the forum, not: let's close this down ;-)
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
6660
days inactive
6660
days old
11 comments
2 participants
participants (2)
-
Mark Little (JIRA) -
Tom Fennelly (JIRA)