In Creating_new_Services_for_NexusBPM_1.2.1.pdf on page 4 (Under 'Creating
an ActionHandler') you mention that the service should not be an
ActionHandlers itself but rather use the JMS-based way of doing things.
What was your reason to move away from using ActionHandlers directly? It
would be interesting to hear about your motives.
Thanks a lot!
Regards,
Gunnar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We were interested in asynchronous handling of the nodes was the main reason. We use an actionhandler to pass info out to jms but thats about it. It's not that you can't create your own action handler - you can - it's just that for our needs, we don't.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
In Creating_new_Services_for_NexusBPM_1.2.1.pdf on page 4 (Under 'Creating
an ActionHandler') you mention that the service should not be an
ActionHandlers itself but rather use the JMS-based way of doing things.
What was your reason to move away from using ActionHandlers directly? It
would be interesting to hear about your motives.
Thanks a lot!
Regards,
Gunnar
We were interested in asynchronous handling of the nodes was the main reason. We use an actionhandler to pass info out to jms but thats about it. It's not that you can't create your own action handler - you can - it's just that for our needs, we don't.
Also the jBPM transaction will time out if the action handler takes too long, such as a long running Jython or Groovy script.