Introduction

The following diagrams aim to describe the composition of the Fractal components of Petals ESB.

By naming convention, if not specified, the default name of the interface 'server' is "service".
To have readable diagrams, some interface links are not drawn:

the links between the interfaces "server" of a composite and the interfaces "server" of its internal components,
the links between the interfaces "client" of internal components of a composite and the interfaces "client" of the composite.
Into a composition, only links between internal components are drawn.

The following diagrams are exported as JPEG image from the slides contained in [Fractal-Diagrams.odp]. The export is done with following parameters:

width: 27.99 cm,
height: 21.01 cm,
resolution: 37 pixel/cm
color: 24bits,
quality: 100%

Table of contents

1 Introduction
2 Fractal tips

2.1 Composite startup

3 Diagrams

3.1 Petals Composite
3.2 System Composite
3.3 Container Composite
3.4 JBI Management Composite
3.5 JBI Messaging Composite
3.6 Communication Composite
3.7 Transporter Composite

3.7.1 NioTransportProtocol

4 Known problems

4.1 Deadlock when starting a composite

Contributors

No contributors found for: authors on selected page(s)

Fractal tips

Composite startup

The sub-components of a Fractal composite are started sequentially, so you MUST declare the sub-component in the right order in the Fractal ADL.

Diagrams

Petals Composite

System Composite

Container Composite

A component SharedLibraryLifeCycleImpl is intantiated each time a JBI shared library is installed into the JBI container. It is dynamically created.
A component ComponentLifeCycleImpl and Installer is intantiated each time a JBI component is installed into the JBI container. It is dynamically created.
A component ServiceAssemblyLifeCycleImpl is intantiated each time a JBI service assembly is deployed into the JBI container. It is dynamically created.