E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (3)
View Page HistoryThe source code tree reflects the Petals ESB architecture, and is organized as following:
* the '{{container}}' is composed of following sub-projects:
* the '{{container}}' is composed of following sub-projects:
** {{petals-local-transporter-default}} {{petals-transporter-local-default}} : Futur project. The current implementation of the local transporter (perhaps new implementations could occur, they will name '{{petals-local-transporter-xxx}}')
** {{petals-remote-transporter-nio}} {{petals-transporter-remote-nio}} : Futur project. The current implementation of the remote transporter using NIO
** {{petals-remote-transporter-ws}} {{petals-transporter-remote-ws}} : A potential future implementation of the remote transporter using SOAP over HTTP(S) (ie: web-service)
** {{petals-microkernel-api}}: The API of {{petals-microkernel) to implement internal components and to implement Petals extensions
** {{petals-microkernel}}: The Petals microkernel containing the internal components that can't be implemented differently and the mechanisms to load implementation of other components and extensions
** {{petals-microkernel}}: The Petals microkernel containing the internal components that can't be implemented differently and the mechanisms to load implementation of other components and extensions
...
** {{petals-container-junit}}: Futur project. An assembly of the {{petals-microkernel}} and selected internal component implementations to run a Petals container into a JUnit test, *_without Petals µKernel extension, but with default logging extensions_*