You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2007/05/22 12:01:26 UTC

[jira] Updated: (ODE-139) Lifecycle management for BpelEventListeners

     [ https://issues.apache.org/jira/browse/ODE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tammo van Lessen updated ODE-139:
---------------------------------

    Attachment: eventlistener-lifecycle.patch

> Lifecycle management for BpelEventListeners
> -------------------------------------------
>
>                 Key: ODE-139
>                 URL: https://issues.apache.org/jira/browse/ODE-139
>             Project: Ode
>          Issue Type: New Feature
>          Components: BPEL Runtime
>    Affects Versions: Incubator
>            Reporter: Tammo van Lessen
>         Attachments: eventlistener-lifecycle.patch
>
>
> The BPEL Event Listener interface provides a nice way to monitor execution events. In my use case I'm publishing BPEL events via JMS to a JMS topic. However, this requires some initialization and clean up functionality to setup the JMS connection on Ode's startup and to gently close it when Ode is shutting down. The attached patch extends the BpelEventListener interface with startup() and shutdown() methods and calls them in BpelServerImpl in order to give implementers the possibility to implement their own initialization and finalization code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.