Release de maintenance - Petals 3.1.3

Soumis par llacote le lun, 01/08/2011 - 13:44

Petals ESB 3.1.3 est publié ! Cette publication inclut les corrections à la fois des versions de maintenance 3.1.2 et 3.1.3, ainsi qu'une version de maintenance du composant SE-POJO.

Téléchargement : Petals ESB 3.1.3 - Petals-SE-POJO 2.2.5

Release notes

Bugfixes

[PETALSESBCONT-18] - The container is always on State: UNKNOWN
[PETALSESBCONT-28] - The MIME "application / zip" check is too restrictive when deploying a JBI artefact
[PETALSESBCONT-70] - A META tag is added when a HTML message is set as output message content
[PETALSESBCONT-83] - Lack of robustness if we play with JMX
[PETALSESBCONT-92] - Error creating new org.ow2.petals.registry.core.repository.bo.Endpoint
[PETALSESBCONT-93] - Two versions of petals-registry-api are packaged
[PETALSESBCONT-98] - The JMX API InstallationServiceMBean.loadInstaller is not JBI compliant when the installer does not exist
[PETALSESBCONT-100] - Successful creation of... 2 EPs with same name !
[PETALSESBCONT-105] - WSDL are transmitted at each request
[PETALSESBCONT-117] - Use of an unsynchronized DateFormat
[PETALSESBCONT-127] - Error message when using the autoloader to install a component
[PETALSESBCONT-131] - Error restart Petals ESB after to have installed a faulty component
[PETALSESBCONT-136] - Unable to install a component from a readonly file-based JBI archive
[PETALSESBCONT-141] - Some HQL requests of the registry don't use named parameter
[PETALSESBCONT-142] - Unable to uninstall a component using Ant task after a failed installation
[PETALSESBCONT-143] - The error message of Ant task 'jbi-uninstall-component' is not clear when the component is not installed
[PETALSESBCONT-144] - The Ant task does not manage correctly configuration attributes when set by configuration file and nested element
[PETALSESBCONT-145] - No error occurs stopping a component in state 'shutdown'
[PETALSESBCONT-146] - A suite of life cycle changes results in end-point leak
[PETALSESBCONT-147] - The error message of the Ant task 'jbi-install-...' or 'jbi-deploy-...' is not clear when the attribute 'file' is empty
[PETALSESBCONT-149] - The error message of the Ant task 'petals-configure-...' is not clear when the attribute 'file' or 'outputFile' is empty
[PETALSESBCONT-151] - The Ant task 'petals-configure-...' does not delete its temporary files
[PETALSESBCONT-161] - Unable to re-install a component: "Component already registered"
[PETALSESBCONT-164] - A NumberFormatException occurs when component configuration parameters are set with invalid values
[PETALSSEPOJO-10] - Unable to configure the component attribute 'properties-file'
[PETALSSEPOJO-11] - Unable to configure the component attribute 'processor-max-pool-size'

Improvement requests

[PETALSESBCONT-45] - A trace MUST be logged about recovering of shared libraries
[PETALSESBCONT-96] - In the server.properties, correct and improve comment about the parameter 'petals.repository.path'
[PETALSESBCONT-103] - Error about opening zip file when loading a new installer from an HTTP URL associated to an HTML page
[PETALSESBCONT-107] - Instanciation number of DOM document builder can be optimized
[PETALSESBCONT-108] - Instanciation number of transformer factory can be optimized
[PETALSESBCONT-109] - Fix and improve inheritance between JBIServiceEndpointImpl and ServiceEndpointImpl
[PETALSESBCONT-112] - Exchange forker can be improved using an entry set instead of a key set
[PETALSESBCONT-116] - Prefer to use ConcurrentHasMap instead of Collections.synchronizedMap(...)
[PETALSESBCONT-118] - Incorrect error message when loading a new installer from a HTTP URL pointing on something that is not a ZIP file
[PETALSESBCONT-119] - Incorrect error message when loading a new installer from an inexisting HTTP URL
[PETALSESBCONT-120] - Don't use utility method of the registry implementation
[PETALSESBCONT-125] - Use preparedStatement instead of simple statement to improve performance and security
[PETALSESBCONT-128] - The recovering thread pool should be sizable
[PETALSESBCONT-130] - Add default option -Djava.net.preferIPv4Stack=true when starting petals
[PETALSESBCONT-132] - Use String Reader instead of StringBufferInputStream in XmlUtil
[PETALSESBCONT-134] - The persistence service should use batch of SQL commands to insert array of the same data
[PETALSESBCONT-135] - The persistence service should use fetch-array with ResultSet to retrieve data of a request returning several lines
[PETALSESBCONT-138] - The logged trace about installer loading should be different in both installer loading methods
[PETALSESBCONT-148] - The error message of Ant tasks managing component lifecycle is not clear when the component identifier is empty
[PETALSESBCONT-150] - No error is thrown when using the Ant task 'petals-configure-...' with an output archive that already exists
[PETALSESBCONT-155] - The error message of Ant tasks uninstalling a shared library is not clear when the shared library identifier is empty
[PETALSESBCONT-158] - Add a MBean operation to synchronize the registry

Nous espérons que vous apprécierez les corrections et ajouts apportés. :) Nous restons comme d'habitude à disposition sur le forum ou le bugtracker.

L'équipe Petals

Actualités

Contactez-nous

Références

ACOSS, le système de recouvrement de cotisations de sécurité sociale, a choisi l'ESB open source Petals ESB pour mettre en place son architecture SOA.

Le groupe Akerys, leader français de l'investissement locatif, a sélectionné Petals ESB pour constituer le socle structurant de son système d'information.

Almerys, éditeur de logiciel de mutuelle, fait appel à Petals Link concernant l'intégration des bénéfices de la SOA au sein de son application.

L'Armée de l'air a choisi Petals ESB dans le cadre d'un projet d'étude sur les technologies SOA, visant à la restructuration de son portail de ressources humaines.

Cegedim Activ, leader du marché français des logiciels et services dédiés à l'assurance de personnes, intègre Petals ESB comme socle de communication de ses applications.

Le Conseil général de la Gironde choisit le bus de services d'entreprise open source Petals ESB pour son portail usager.

Magellium choisit l'ESB open source Petals ESB pour structurer INGRID, une nouvelle application de gestion d'image de la Direction Générale de l'Armement.

La Direction Générale de la Modernisation de l'Etat a retenu Petals comme socle de gestion des échanges pour son portail citoyen "Monservicepublic.fr".