Petals ESB Container

Add a controller in the Petals composite

Details

  • Type: Task Task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.2.0
  • Fix Version/s: 5.0.0
  • Component/s: Component framework
  • Security Level: Public
  • Description:
    Hide

    Nowadays, the Fractal component composition is written using Fractal ADL. That is a static composition way that does not permit to have configurable component implementation as the registry because interfaces are not bound before startup of components and composites.

    So the Fractal architecture must be reviewed to mix Fractal ADL and pieces of Java code:

    • Fractal ADL can be used for static composites,
    • The composite Petals will contains:
      • the configuration service
      • a new component 'PetalsCompositeController' that will instantiate and start following component when starting:
        1. the composite 'Communication',
        2. the composite 'System',
        3. the composite 'ExtensionManager',
        4. the composite 'JBI-Management',
        5. the component 'org.ow2.petals.microkernel.admin.PetalsAdminServiceImpl',
        6. the composite 'JBI-Messaging',
        7. the composite 'Transporter',
        8. the composite 'Container'.
    Show
    Nowadays, the Fractal component composition is written using Fractal ADL. That is a static composition way that does not permit to have configurable component implementation as the registry because interfaces are not bound before startup of components and composites. So the Fractal architecture must be reviewed to mix Fractal ADL and pieces of Java code:
    • Fractal ADL can be used for static composites,
    • The composite Petals will contains:
      • the configuration service
      • a new component 'PetalsCompositeController' that will instantiate and start following component when starting:
        1. the composite 'Communication',
        2. the composite 'System',
        3. the composite 'ExtensionManager',
        4. the composite 'JBI-Management',
        5. the component 'org.ow2.petals.microkernel.admin.PetalsAdminServiceImpl',
        6. the composite 'JBI-Messaging',
        7. the composite 'Transporter',
        8. the composite 'Container'.
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Thu, 7 Nov 2013 - 18:07:42 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Christophe DENEUX made changes - Thu, 7 Nov 2013 - 18:08:18 +0100
Link This issue blocks PETALSESBCONT-267 [ PETALSESBCONT-267 ]
Christophe DENEUX made changes - Thu, 7 Nov 2013 - 18:08:27 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Tue, 12 Nov 2013 - 15:42:32 +0100
Description Nowadays, the Fractal component composition is written using Fractal ADL. That is a static composition way that does not permit to have configurable component implementation as the registry because of interface not bind before startup of components and composites.

So the Fractal architecture must be reviewed to mix Fractal ADL and pieces of Java code:
* Fractal ADL can be used for static composites,
* The composite Petals will contains:
** the configuration service
** a new component '{{PetalsCompositeController}}' that will instantiate when starting:
### the composite '{{Communication}}',
### the composite '{{System}}',
### the composite '{{ExtensionManager}}',
### the composite '{{JBI-Management}}',
### the component '{{org.ow2.petals.microkernel.admin.PetalsAdminServiceImpl}}',
### the composite '{{JBI-Messaging}}',
### the composite '{{Transporter}}',
### the composite '{{Container}}'. 		Nowadays, the Fractal component composition is written using Fractal ADL. That is a static composition way that does not permit to have configurable component implementation as the registry because of interface not bind before startup of components and composites.

So the Fractal architecture must be reviewed to mix Fractal ADL and pieces of Java code:
* Fractal ADL can be used for static composites,
* The composite Petals will contains:
** the configuration service
** a new component '{{PetalsCompositeController}}' that will instantiate and start following component when starting:
### the composite '{{Communication}}',
### the composite '{{System}}',
### the composite '{{ExtensionManager}}',
### the composite '{{JBI-Management}}',
### the component '{{org.ow2.petals.microkernel.admin.PetalsAdminServiceImpl}}',
### the composite '{{JBI-Messaging}}',
### the composite '{{Transporter}}',
### the composite '{{Container}}'.
Christophe DENEUX made changes - Tue, 12 Nov 2013 - 15:44:57 +0100
Description Nowadays, the Fractal component composition is written using Fractal ADL. That is a static composition way that does not permit to have configurable component implementation as the registry because of interface not bind before startup of components and composites.

So the Fractal architecture must be reviewed to mix Fractal ADL and pieces of Java code:
* Fractal ADL can be used for static composites,
* The composite Petals will contains:
** the configuration service
** a new component '{{PetalsCompositeController}}' that will instantiate and start following component when starting:
### the composite '{{Communication}}',
### the composite '{{System}}',
### the composite '{{ExtensionManager}}',
### the composite '{{JBI-Management}}',
### the component '{{org.ow2.petals.microkernel.admin.PetalsAdminServiceImpl}}',
### the composite '{{JBI-Messaging}}',
### the composite '{{Transporter}}',
### the composite '{{Container}}'. 		Nowadays, the Fractal component composition is written using Fractal ADL. That is a static composition way that does not permit to have configurable component implementation as the registry because interfaces are not bound before startup of components and composites.

So the Fractal architecture must be reviewed to mix Fractal ADL and pieces of Java code:
* Fractal ADL can be used for static composites,
* The composite Petals will contains:
** the configuration service
** a new component '{{PetalsCompositeController}}' that will instantiate and start following component when starting:
### the composite '{{Communication}}',
### the composite '{{System}}',
### the composite '{{ExtensionManager}}',
### the composite '{{JBI-Management}}',
### the component '{{org.ow2.petals.microkernel.admin.PetalsAdminServiceImpl}}',
### the composite '{{JBI-Messaging}}',
### the composite '{{Transporter}}',
### the composite '{{Container}}'.
Hide
Permalink
Christophe DENEUX added a comment - Wed, 13 Nov 2013 - 11:08:22 +0100

Done in trunk

Show
Christophe DENEUX added a comment - Wed, 13 Nov 2013 - 11:08:22 +0100 Done in trunk
Christophe DENEUX made changes - Wed, 13 Nov 2013 - 11:08:22 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 4.2.1 [ 10413 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
13s
1
Christophe DENEUX
Thu, 7 Nov 2013 - 18:07:42 +0100
Open Open In Progress In Progress
45s
1
Christophe DENEUX
Thu, 7 Nov 2013 - 18:08:27 +0100
In Progress In Progress Resolved Resolved
5d 16h 59m
1
Christophe DENEUX
Wed, 13 Nov 2013 - 11:08:22 +0100



People

Dates

  • Created:
    Thu, 7 Nov 2013 - 18:07:29 +0100
    Updated:
    Wed, 13 Nov 2013 - 11:08:22 +0100
    Resolved:
    Wed, 13 Nov 2013 - 11:08:22 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.