Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.0
-
Fix Version/s: 4.2.0
-
Component/s: Administration
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | ||||
|---|---|---|---|---|
|
|
|
|||
Activity

| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
| Link |
This issue blocks |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Link |
This issue blocks |
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 4.2.0 [ 10356 ] | |
| Priority | Major [ 3 ] | |
| Description |
# Using the JMX API, just load a new installer of a component
# Next, invoke {{AdminServiceMBean.isEngine(...)}} or {{AdminServiceMBean.isBinding(...)}} # The returned value is always {{false}} The JBI specifications does not define restrictions on the lifecycle about these methods. |
# Using the JMX API, just load a new installer of a component
# Next, invoke {{AdminServiceMBean.isEngine(...)}} or {{AdminServiceMBean.isBinding(...)}} # The returned value is always {{false}} The JBI specifications define no restriction about lifecycle on these methods. |
Fixed in trunk