Details
-
Type:
Task
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.2.3
-
Fix Version/s: 5.0.0
-
Component/s: Administration, Component framework, Installation/Deployment, Micro-kernel
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Summary | We should shutdown a component only if no SU is deployed on | We should be able to shutdown a component only if no SU is deployed on |
| Fix Version/s | 4.3.0 [ 10413 ] |
| Description |
To shutdowner a component, it should no longer have SU deployed on. All SUs must be undeployed before to shutdown the component.
|
To shutdown a component, it should no longer have SU deployed on. All SUs must be undeployed before to shutdown the component.
|
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Description |
To shutdown a component, it should no longer have SU deployed on. All SUs must be undeployed before to shutdown the component.
|
To shutdown a component, it should no longer have SU deployed on. All SUs must be undeployed before to shutdown the component.
In previous version of Petals ESB it was possible to shutdown a component id SUs are deployed on, but the following use case cannot be supported: * according to JBI specifications: all external resource connections (as database) are: ** created on {{init()}}, ** released on {{shutdown()}}. * but component as SE BPMN that requires an external resource connection (as database) when (un)deploying service unit can not be supported, except if the component shutdown is blocked if SUs are deployed on. |
| Description |
To shutdown a component, it should no longer have SU deployed on. All SUs must be undeployed before to shutdown the component.
In previous version of Petals ESB it was possible to shutdown a component id SUs are deployed on, but the following use case cannot be supported: * according to JBI specifications: all external resource connections (as database) are: ** created on {{init()}}, ** released on {{shutdown()}}. * but component as SE BPMN that requires an external resource connection (as database) when (un)deploying service unit can not be supported, except if the component shutdown is blocked if SUs are deployed on. |
To shutdown a component, it should no longer have SU deployed on. All SUs must be undeployed before to shutdown the component.
In previous version of Petals ESB it was possible to shutdown a component with SUs deployed on, but the following use case cannot be supported: * according to JBI specifications: all external resource connections (as database) are: ** created on {{init()}}, ** released on {{shutdown()}}. * but component as SE BPMN that requires an external resource connection (as database) when (un)deploying service unit can not be supported, except if the component shutdown is blocked if SUs are deployed on. |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Done in trunk