End Node and ExecutionListeners

[Cheong Chung Onn]

Hi Paul,

I have encountered a new problem. Previously we decided to create a
custom EndNode to achieve my need to have an explicit EndNode, however I
realized this approach has side effect. This is because when the token
reaches the End Node, Sarasvati still fires all the registered
listeners like NodeTokenCompleted, NodeTokenExecuted and
ProcessCompleted etc.

My use case is EndNode should not exhibit the same behaviors as a
regular Node in terms of Node lifecycle. To avoid these extraneous
triggers I had to work around it. I wonder should Node has a special
flag to request it not to fire all the events?

Regards
chung-onn

[Paul Lorenz]

Have you considered using and either a whitelist or blacklist approach to control which nodes your execution listeners pay attention to? You could just put

public void notify (ExecutionEvent event ) {
  NodeToken token = event.getNodeToken();
  if ( token != null && token.getNode().getType().equals( "end" ) )
  {
    return;
  }
  ..
}

Which is easier than updating the xml schema, the xml classes, the loader, the database schema, the node class and the engine. Maybe I'm missing something, though. Are there use cases for an 'ignore events' flag that couldn't be handled in this way?

cheers,
Paul

[Cheong Chung Onn]

Hi Paul,

Thanks for pointing me the right direction. I failed to dig deeper into
the javadoc :)

Cheers!
chung-onn