Release Notes - Petals ESB Container - Version 4.2.0 - HTML format

Bug

• [PETALSESBCONT-27] - The server parameter 'petals.topology.url' does not work
• [PETALSESBCONT-89] - The method getResourceAsStream doesn't work when path contains space character
• [PETALSESBCONT-123] - Topology has not to have a dependency on WS API
• [PETALSESBCONT-173] - Installation of a component using JMX fails
• [PETALSESBCONT-196] - NPE if no property 'handlers' is defined in logging configuration
• [PETALSESBCONT-198] - Petals launcher defines a classloader that contains unneeded JAR files
• [PETALSESBCONT-204] - Unable to use my own LogHandler
• [PETALSESBCONT-206] - The JMX API methods AdminServiceMBean.isEngine(...) and AdminServiceMBean.isBinding(...) return false if a component has only its installer loaded
• [PETALSESBCONT-207] - Component installer can be unload even if the component is installed
• [PETALSESBCONT-241] - DeploymentServiceImpl.getState() prints a severe error message if the service assembly is not deployed
• [PETALSESBCONT-247] - Easymock is delivered with Petals ESB
• [PETALSESBCONT-258] - Replace org.ow2.petals.microkernel.testutil.PrivateAccessor using ReflectionHelper
• [PETALSESBCONT-259] - PetalsClassLoader is unable to read a resource having spaces in its name

Improvement Request

• [PETALSESBCONT-51] - The topology configuration should be read by the petals launchers and not by the kernel itself
• [PETALSESBCONT-52] - The container configuration should be read by the petals launchers and not by the kernel itself
• [PETALSESBCONT-53] - Add an API to parse a topology configuration from an InputStream
• [PETALSESBCONT-62] - Handling configuration resources
• [PETALSESBCONT-81] - Launch several containers from one installation
• [PETALSESBCONT-208] - Add technical monitoring metrics
• [PETALSESBCONT-209] - The JMX API PetalsAdminServiceMBean.retrieveTopology returns JMX credentials without dedicated security
• [PETALSESBCONT-210] - Add a JMX API to uninstall all no more used shared libraries
• [PETALSESBCONT-211] - Add a JMX API to uninstall all no more used components
• [PETALSESBCONT-212] - Add a JMX API to shutdown all no more used components
• [PETALSESBCONT-215] - The file 'server.properties' should be read by the launcher instead of the kernel
• [PETALSESBCONT-219] - Add a flag to the petals launcher to print error stack trace of the launcher
• [PETALSESBCONT-223] - The topology configuration resource should be read by the launcher instead of the kernel
• [PETALSESBCONT-257] - Externalize Java options

New Feature

• [PETALSESBCONT-202] - Add a script 'initd' to automatically start/stop Petals

Task

• [PETALSESBCONT-197] - Remove the hard-coded configuration of logging sub-system
• [PETALSESBCONT-205] - The log level MONIT-MSG has no sens, replaced by a new LogHandler
• [PETALSESBCONT-214] - Create a Debian package to install Petals ESB
• [PETALSESBCONT-216] - Use Apache Commons CLI to manage launcher arguments on the command line
• [PETALSESBCONT-217] - The registry should use the configuration service to get its configuration
• [PETALSESBCONT-218] - The default value of the property 'petals.topology.url' must be changed to be relative to the local configuration resource
• [PETALSESBCONT-220] - Remove support of the domain mode "standalone"
• [PETALSESBCONT-222] - Remove support of the domain mode "autodiscover"
• [PETALSESBCONT-225] - Move the autoloader as an extension of the Petals ESB container
• [PETALSESBCONT-226] - Move the artifact repository as an extension of the Petals ESB container
• [PETALSESBCONT-229] - Create a Debian package to install the Petals ESB Autoloader
• [PETALSESBCONT-230] - Create a Debian package to install the Petals ESB Artifact Repository
• [PETALSESBCONT-231] - Replace the internal JMX client stack by petals-jmx-api
• [PETALSESBCONT-232] - The configuration service has not to depend on the Kernel WS API
• [PETALSESBCONT-233] - The configuration service API must throw its own exceptions
• [PETALSESBCONT-234] - The topology service must throw its own exceptions
• [PETALSESBCONT-235] - The autoloader implementation uses a child class of the repository implementation
• [PETALSESBCONT-236] - 'ServiceAssemblyLifeCycle' is a fractal component, not a simple class
• [PETALSESBCONT-238] - Use usual naming conventions for the Fractal component 'ComponentLifeCycle'
• [PETALSESBCONT-239] - MBeanNameImpl should be a Fractal component
• [PETALSESBCONT-240] - The composite "JBI-Messaging" required the not used client interface "admin"
• [PETALSESBCONT-242] - The Autoloader does not require the AdminService
• [PETALSESBCONT-243] - Improve Fractal component-based architecture of the Autoloader
• [PETALSESBCONT-244] - The component 'Transaction' should be a subcomponent of the composite 'System'
• [PETALSESBCONT-245] - The component 'LoggingService' should be a subcomponent of the composite 'System'
• [PETALSESBCONT-246] - Reorganize container projects in expectation of creating the petals micro kernel
• [PETALSESBCONT-248] - The 'Installer' is a Fractal component and it MUST be accessed by its interface
• [PETALSESBCONT-249] - Move the WS API as an extension of the Petals ESB container
• [PETALSESBCONT-250] - The topology service uses the WSAPI
• [PETALSESBCONT-251] - Reorganize Petals API
• [PETALSESBCONT-253] - Create a Debian package to install the Petals ESB WS-API

The text area below allows the project release notes to be edited and copied to another document.