Details
Task
Resolved
Major
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] | |
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.0.2 [ 10661 ] | |
| Resolution | Fixed [ 1 ] |
| Description |
ContainerConfiguration store local configuration information, but not anything that is meant to be accessed remotely through client server api!
Modifying this class impacts almost half of our code base when we want to add some server configuration while it shouldn't. So it should be moved to microkernel were it is meant to be so that future modification of it won't impact all of our artifacts (such as JMX or CLI). |
ContainerConfiguration store local configuration information, but not anything that is meant to be accessed remotely through client server api!
Modifying this class impacts almost half of our code base when we want to add some server configuration while it shouldn't. So it should be moved to microkernel were it is meant to be so that future modification of it won't impact all of our artifacts (such as JMX or CLI). The main impact it has in practice is that the API for Topology attachment is changed and thus Petals CLI must be modified (see |
| Link |
This issue blocks |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Done in r40192.