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

Bug

• [PETALSESBCONT-2] - Impossible to cast the TransactionManager in a component when the classloader isolation is activated
• [PETALSESBCONT-9] - Delete endpoint failure at the stop of the container
• [PETALSESBCONT-10] - Unable to deploy a SL containing a JBI descriptor without the attribute "version"
• [PETALSESBCONT-14] - Empty topology.xml on dynamic mode
• [PETALSESBCONT-16] - Problem on unregistration of endpoints at the shutdown of RMI component
• [PETALSESBCONT-17] - "Too many open files" after several component or SA installations/uninstallations
• [PETALSESBCONT-22] - No synchronization made by Petals container "master" node when restarted after crash (distributed configuration with at least 2 nodes)
• [PETALSESBCONT-65] - PetalsClassLoader does not implement getResources properly
• [PETALSESBCONT-71] - Duplicated & conflicting fields in the HibernateHelper class
• [PETALSESBCONT-91] - unpredictable log4j:WARN
• [PETALSESBCONT-106] - Trying to unregister not registred endpoint
• [PETALSESBCONT-170] - When the master is stopped, the slave displays an incomprehensible error when synchronizing
• [PETALSESBCONT-189] - PetalsClassLoader includes a tricky method to unlock JAR file of classloader
• [PETALSESBCONT-201] - NullPointerException when the NIO transporter receives a message
• [PETALSESBCONT-260] - Petals ESB does not restart when its host restarts
• [PETALSESBCONT-261] - No trace is logged when the Petals ESB container is started/stopped
• [PETALSESBCONT-263] - Few classes are duplicates in the Jar of the Petals default launcher
• [PETALSESBCONT-270] - No debug trace when the log level of loggers is set to FINE or FINER
• [PETALSESBCONT-279] - No default value is defined for the property 'petals.task.timeout'
• [PETALSESBCONT-280] - The JMX API for the service 'Topology' is not the expected one
• [PETALSESBCONT-295] - Service invocation on remote container fails
• [PETALSESBCONT-296] - The temporary file '/tmp/petals-local-server.xxxx.properties' is not removed
• [PETALSESBCONT-297] - An error occurs if no url is provided starting manually a Petals ESB container
• [PETALSESBCONT-306] - Error 'Operation isExchangeWithConsumerOkayForComponent not in ModelMBeanInfo'
• [PETALSESBCONT-307] - IN message must be dumped by log handler 'PetalsPayloadDumperFileHandler' only on starting trace MONIT for MEP InOnly
• [PETALSESBCONT-308] - The following error occurs dumping message content with log handler PetalsPayloadDumperFileHandler
• [PETALSESBCONT-310] - Unable to start Petals ESB in debug mode
• [PETALSESBCONT-315] - Unable to start Petals ESB if installed in a directory whose the name contains spaces
• [PETALSESBCONT-316] - Can't recover Components and SAs when the container is in a directory with spaces in its path
• [PETALSESBCONT-317] - Unable to install a component using the Autoloader if the installation directory name contains a space character
• [PETALSESBCONT-320] - Invalid name for the property defining that a mex is sent synchronously
• [PETALSESBCONT-330] - Implementation of MessageExchange does not respect owner contract
• [PETALSESBCONT-332] - Use of the wrong URI for optional MEP
• [PETALSESBCONT-334] - Verification of state when changing status is buggy in MessageExchangeImpl
• [PETALSESBCONT-340] - Container state are not correctly returned by the JMX API 'retrieveTopology'
• [PETALSESBCONT-341] - Component classloader not completly isolated
• [PETALSESBCONT-345] - Do not remove In, Out or Fault from an Exchange before sending it
• [PETALSESBCONT-347] - sendSync timeout should not return ownership to sender

Improvement Request

• [PETALSESBCONT-50] - The registry should be exploded in two parts
• [PETALSESBCONT-69] - Add all the registry database configuration to the server.properties
• [PETALSESBCONT-74] - The Message exchange setters do not control properly the rights to set according to the current step of the MEP
• [PETALSESBCONT-121] - Replace and externalize the existing registry
• [PETALSESBCONT-122] - Access to the description of an endpoint is excessively synchronized
• [PETALSESBCONT-227] - Merge both logging systems
• [PETALSESBCONT-267] - Externalize the registry implementation
• [PETALSESBCONT-273] - Move the registry synchronization as an administration operation of the Petals ESB initial registry
• [PETALSESBCONT-274] - Remove the dedicated configuration parameters linked to the Petals ESB initial registry from the topology
• [PETALSESBCONT-275] - Create a Petals ESB Registry based on a Hazelcast cluster
• [PETALSESBCONT-282] - The microkernel should be able to load extensions before loading its internal components
• [PETALSESBCONT-283] - The extension 'Petals Registry Overlay' is packaged with the default container
• [PETALSESBCONT-284] - The Petals Registry Overlay should be embedded as a Petals ESB extension
• [PETALSESBCONT-293] - Use a human readable name for threads of the recovery service
• [PETALSESBCONT-294] - The properties of the recovery service are not described
• [PETALSESBCONT-298] - The delays of the topology pinger timer task should be customizable
• [PETALSESBCONT-301] - The thread used as priority processor by the router should be correctly named
• [PETALSESBCONT-303] - Move the configuration of the WS-API extension from topology definition to the local container configuration
• [PETALSESBCONT-304] - Move the dedicated configuration parameters linked to the Petals ESB initial registry from the local container configuration
• [PETALSESBCONT-305] - Deployable service unit deployment/undeployment
• [PETALSESBCONT-314] - The version of shared libraries used should be required by JBI components
• [PETALSESBCONT-326] - The system property 'petals.log.dir' should accept relative path
• [PETALSESBCONT-337] - Petals ESB container requires a Java Runtime Environment head less

New Feature

• [PETALSESBCONT-276] - Make the topology dynamic
• [PETALSESBCONT-343] - Add a PETALS_CLASSPATH environment variable for the startup script

Task

• [PETALSESBCONT-255] - Improve the definition of the TransformerFactory to use in Petals ESB
• [PETALSESBCONT-268] - The registry should be a sub-component of the composite "System"
• [PETALSESBCONT-269] - Add a controller in the Petals composite
• [PETALSESBCONT-271] - Create a Debian package to install the registry implementation 'Initial registry'
• [PETALSESBCONT-272] - Externalize the initial registry implementation in a dedicated project
• [PETALSESBCONT-281] - Move the API 'retrieveTopology' from PetalsAdminMBean to TopologyMBean
• [PETALSESBCONT-285] - A sub-domain supports the mode 'static' and 'dynamic'
• [PETALSESBCONT-287] - Move the composite 'Container' inside the composite 'JBI-Management'
• [PETALSESBCONT-288] - Introduce the Fractal component 'ContainerController'
• [PETALSESBCONT-289] - 'Installer' should be referenced inside the 'ContainerService' instead of the 'AdminService'
• [PETALSESBCONT-290] - 'ServiceAssemblyLifeCycle' should be referenced inside the 'ContainerService' instead of the 'AdminService'
• [PETALSESBCONT-291] - 'ComponentLifeCycle' should be referenced inside the 'ContainerService' instead of the 'AdminService'
• [PETALSESBCONT-292] - 'SharedLibraryLifeCycle' should be referenced inside the 'ContainerService' instead of the 'AdminService'
• [PETALSESBCONT-311] - Add an integration test about usage of the Petals handler dumping message content
• [PETALSESBCONT-313] - We should be able to shutdown a component only if no SU is deployed on
• [PETALSESBCONT-318] - Migrate from Fractal Spoon to the new Fractal Juliac Compiler version 2.6
• [PETALSESBCONT-319] - Refactor jbi-descriptor classe
• [PETALSESBCONT-321] - Some exceptions in Threads are not logged
• [PETALSESBCONT-322] - The component 'JMXService' uses a map of JMXClient instead of an object pool
• [PETALSESBCONT-323] - Remove unneeded dependencies from the system classpath
• [PETALSESBCONT-327] - Improve the caching of streams (*Source in the content of messages)
• [PETALSESBCONT-328] - Remove useless contextual (related to flow attributes) exchange builder
• [PETALSESBCONT-329] - Remove deprecated pattern URI in MessageExchangeImpl
• [PETALSESBCONT-331] - Remove home-made MEP and use those from EasyWSDL
• [PETALSESBCONT-333] - Improve classloading for components
• [PETALSESBCONT-335] - Use JUL for logging
• [PETALSESBCONT-342] - Upgrade commons-pool to version 1.6
• [PETALSESBCONT-344] - Add system extensions
• [PETALSESBCONT-414] - Remove Petals Artifact Repository Extension
• [PETALSESBCONT-445] - Explain how to disable log file hierarchy

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