Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.2.0
-
Fix Version/s: 5.0.0
-
Component/s: Micro-kernel
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | The microkernel should be able to load extension before loading its internal components | The microkernel should be able to load extensions before loading its internal components |
| Fix Version/s | 4.2.1 [ 10413 ] | |
| Priority | Major [ 3 ] | |
| Component/s | Micro-kernel [ 10291 ] | |
| Component/s | Administration [ 10052 ] |
| Description |
Nowadays the Petals µKernel supports:
# to load extension once all its internal component are loaded, # and to load dedicated implementation of mutable internal component. In some case, an implementation of a mutable component can require to embed its external resources into dedicated Fractal components (for example, the registry overlay is embedded into a Fractal component to avoid to start another process using the sample configuration). So this Fractal component *must* be loaded before the mutable component implementation. |
Nowadays the Petals µKernel supports:
* to load extension once all its internal component are loaded, * and to load dedicated implementation of mutable internal component. In some case, an implementation of a mutable component can require to embed its external resources into dedicated Fractal components (for example, the registry overlay is embedded into a Fractal component to avoid to start another process using the sample configuration). So this Fractal component *must* be loaded before the mutable component implementation. |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Link | This issue blocks PETALSREGOVER-5 [ PETALSREGOVER-5 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |