[jboss-dev-forums] [Design of JBoss ESB] - Re: Trailblazer out-of-the-box experience

[mark.little@jboss.com]

"estebanschifman" wrote : Tom,
  | As a result of your observation yesterday, I have introduced a fix for that problem.
  | 

I think we should have discussed this further before any change was made. It may be that this is a problem, but I'd like to understand it first. As I've just said to Tom, at first glance this behaviour would break information containment rules. Maybe I'm missing something and this is default behaviour we want for ActionProcessors (definitely NOT what I want for dispatchers though), but I'd like to understand the potential issue.

anonymous wrote : 
  | The AbstractListener will now keep the 'before action' as well as the 'after action' current object, until the processing pipeline is about to start the next step in the chain.
  | As a consequence of this, the notification methods (and in fact any other methods that we might have in the future invoked after the process(Message) and the end of this action)  have now access to both. (before and after action).
  | 
  | Thanks.   E

Can you show the interface here, so we can discuss? I'd like to separate out the issue of the changes from the issue of why the change may be necessary. Probably better to have that latter discussion first.

Thanks.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976749#3976749

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976749