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:19 UTC
[jira] Created: (ODE-139) Lifecycle management for
BpelEventListeners
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
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.
[jira] Commented: (ODE-139) Lifecycle management for
BpelEventListeners
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506303 ]
Matthieu Riou commented on ODE-139:
-----------------------------------
Sounds good. I'll try to apply it correctly this time :)
> 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
> Assignee: Matthieu Riou
> 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.
[jira] Resolved: (ODE-139) Lifecycle management for
BpelEventListeners
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou resolved ODE-139.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.1-incubating
Patch applied on r549636. Thanks Tammo!
> 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
> Assignee: Matthieu Riou
> Fix For: 1.1-incubating
>
> Attachments: configurable-event-listeners.patch, 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.
[jira] Updated: (ODE-139) Lifecycle management for
BpelEventListeners
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-139:
---------------------------------
Attachment: configurable-event-listeners.patch
This patch enables lifecycle management for BpelEventListeners and passes properties defined in Ode's configuration file to the listeners startup() methods. This makes them configurable. The patch integrates with Axis2, JBI and Test IL.
> 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
> Assignee: Matthieu Riou
> Attachments: configurable-event-listeners.patch, 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.
[jira] Issue Comment Edited: (ODE-139) Lifecycle management for
BpelEventListeners
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506545 ]
Tammo van Lessen edited comment on ODE-139 at 6/20/07 7:16 AM:
---------------------------------------------------------------
This patch enables lifecycle management for BpelEventListeners and passes properties defined in Ode's configuration file to the listeners startup() methods. This makes them configurable. The patch integrates with Axis2, JBI and Test IL.
This patch makes the old patch obsolete.
was:
This patch enables lifecycle management for BpelEventListeners and passes properties defined in Ode's configuration file to the listeners startup() methods. This makes them configurable. The patch integrates with Axis2, JBI and Test IL.
> 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
> Assignee: Matthieu Riou
> Attachments: configurable-event-listeners.patch, 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.
[jira] Reopened: (ODE-139) Lifecycle management for
BpelEventListeners
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen reopened ODE-139:
----------------------------------
When looking into the repository, it seems that the patch has not been applied yet.
> 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
> Assignee: Matthieu Riou
> 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.
[jira] Updated: (ODE-139) Lifecycle management for
BpelEventListeners
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Issue Comment Edited: (ODE-139) Lifecycle management for
BpelEventListeners
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506298 ]
Tammo van Lessen edited comment on ODE-139 at 6/19/07 2:22 PM:
---------------------------------------------------------------
When looking into the repository, it seems that the patch has not been applied yet.
However, it would be also good to pass the OdeConfigProperties to the startup() method so that listeners can share the Ode configuration file. I'll make another patch for that.
was:
When looking into the repository, it seems that the patch has not been applied yet.
> 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
> Assignee: Matthieu Riou
> 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.
[jira] Resolved: (ODE-139) Lifecycle management for
BpelEventListeners
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou resolved ODE-139.
-------------------------------
Resolution: Fixed
Assignee: Matthieu Riou
Patch applied some time ago already.
> 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
> Assignee: Matthieu Riou
> 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.