New branch 'bug/966777' available with the following commits:
commit 8d3cee90914164538471b723b1f344fbaffcfe8c
Author: Thomas Segismont <tsegismo(a)redhat.com>
Date: Tue Jul 2 12:24:21 2013 +0200
Bug 966777 - EAP 6 plug-in is using a hard-coded operation timeout for start and stop
instead of using the operation timeout or agent's default operation timeout of 10
minutes
Make ComponentInvocationContext accessible from ResourceContext. Expose interface only
in plugin api.
commit cf043bcb4499155839dcf00818e6e12c22b90d05
Author: Thomas Segismont <tsegismo(a)redhat.com>
Date: Thu Jun 27 17:05:03 2013 +0200
Bug 966777 - EAP 6 plug-in is using a hard-coded operation timeout for start and stop
instead of using the operation timeout or agent's default operation timeout of 10
minutes
Introduce ComponentInvocationContext class. An instance of this class is created by
the plugin container and bound to facet-locked component invocation thread.
Make BaseServerComponent use ComponentInvocationContext to deal with operation timeout
or cancellation.
commit fa52ed9d1a80905903a4294971c898c978cd11d5
Author: Thomas Segismont <tsegismo(a)redhat.com>
Date: Thu Jun 27 16:09:58 2013 +0200
Bug 966777 - EAP 6 plug-in is using a hard-coded operation timeout for start and stop
instead of using the operation timeout or agent's default operation timeout of 10
minutes
The component invocation handler now has a transferInterrupt parameter. If set to
true, the component invocation thread will be interrupted when the caller thread is.
Show replies by date