PEtALS Azalee pack



Friday, June, the first, 2007



PEtALS Azalee pack

The PEtALS Azalee pack contains all the PETALS elements that are useful for integration solutions.

PEtALS is the highly distributed Open Source ESB hosted by OW2.

PEtALS delivers OW2 JavaTM Business Integration (JBI) platform.

PEtALS provides lightweight and packaged integration solutions, based on JSR-208 specifications, with a strong focus on distribution and clustering.




New features

New Features

Distributed environment : The PETALS nodes topology can be configured statically. The standard multicast auto-discovering is disabled in this mode

The Web Administrative console manages JBI components

The ComponentDevelopmentKit eases the JMX exposition of components configuration attributes during installation phase

IBM JVM compatibility

A new FTP binding component

(see release notes for an exhaustive list)




Content

Component

Version

Note

Documentation

PETALS Container – Standalone

v1,3

the PETALS JBI container, running as a standalone application

http link

Web Administration console

v1,3

a monitoring and administrative console for PETALS, can be deployed in a J2EE server as a web application. Run on almost J2EE servers

http link

Component Development Kit

v1,4,1

ease the development of custom JBI components

http link

Petals-bc-soap

v1,3

a binding component to consume or provide WebServices. Based on Axis2 v1,1

http link

Petals-bc-filetransfer

v1,4

a binding component to read or write files

http link

Petals-bc-ftp

v1,0

a binding component to get or put files on an FTP server

http link

Petals-bc-jms

v1,2

a binding component to send/receive/pub/sub messages on a JMS server

http link

Petals-bc-mail

v1,2

a binding component to send or pop emails on a mail server

http link

Petals-bc-xquare

v1,2

a binding component to access database with insert, query and storedQuery operations. Based on XQuare Bridge library

http link

Petals-se-csv

v1,3

a service engine to convert CSV format to XML

http link

Petals-se-forward

v1,2

a service engine to chain (pipe) several services

http link

Petals-se-pojo

v1,3

a service engine to expose Java code as a service

http link

Petals-se-xslt

v1,3

a service engine to transform message by usin XSL style sheets

http link






Release notes

id

FeatureRequest

306683

The registry of the container must be removed from the transporter layer

306587

multi-platform installer

306646

WebAdmin

306745

improvement of the deployment process in the administration console

306784

[Axis2BC] Add Axis2 modules deployment support

306785

[Axis2BC] Add support for services.xml description when deploying a SU

306787

[CDK] Use the ComponentConfiguration mechanism to set thread pool configuration

306809

[CDK] MBean management for attributes and methods during bootstrap

306791

[Axis2BC] Enable/Disable services list display

307048

[CDK] Add optional extensions validation on Su deployment

306786

[JNDI] Use JORAM JNDI server

306824

[SystemUtil] Refactor properties loading

306905

[FTP BC] creation

307134

set a timeout on administration task on components preventing thread blocking

306789

[INSTALLATION] Refactoring of the installation service

306810

Compression of Normalized message content

307033

Compile/launch PEtALS on other JDK/JRE than SUN

306988

allow in SU an OPERATION tag

307000

Manage OPERATION tag element in SOAP Body

306645

JoramTransport : use multithreading for receiving jms messages






id

Corrected Bugs

307125

problem when setting the repository.path value - URI format is bad

307124

Unknow state not managed by administration

306999

Webadmin doesn't work if Tomcat is started before Petals

306930

Uninstallation failed when the PETALS repository path is not the default one

307127

InstallationService : loadInstaller must call init() on the bootstrap

306742

The Petals WebApp shutdown cause a crash in the Jboss shutdown process.

307132

when a component throw a runtime exception during an installation task, Petals becomes instable

307129

SA failed to undeploy on Petals shutdown

307128

when only a component Installer is loaded (not the CLifeCycle), it is not reloaded on Petals restart

306583

ConcurrentModificationException in ComponentContextImpl when shutdown

306590

NameAlreadyBoundException when deploying an endpoint on an already used interface

306779

Bug with proxy sample using Petals 1.2.1

306250

Undeployment of a Component-Installer

306808

[Platform] System state recovery must use expended packges instead of zipped archive

306740

Problem with interface resolution when an endpoint is asked for the first time.

307077

extensions in jbi.xml are not saved

307009

Service Endpoint unicity in Petals

307035

Unable to compile petals-kernel because unsastified dependency

307052

[petals-standalone] The path is not correctly set in the Windows scripts

307017

org.objectweb.petals:petals-component-common:1.0.1is missing on objectweb maven repository

307014

[petals-bc-soap] NPE if no HTTP-SOAP header in the web-service request

307008

[MBean] Petals Installation MBean is named InstallationInstallation

307003

org.objectweb.petals:petals-plugin-maven-jbi:1.2 is missing on objectweb maven repository

306986

[petals-platform] Some debug messages are displayed when stoping petals.

306906

[SE-POJO] Pojo SE doesn't find inherited methods

306909

[SE-SampleClient] Unable to specify an endpoint when invoking a service

306845

[SOAP BC] Addresses of WSDL ports are not valids

306844

[SOAP BC] Class cast exception on JBI response

306744

JMX communication problem when the IP address is not set in the /etc/hosts

307131

logs file are sometimes written in petals/bin directory

307126

InstallationService : install() failed after an uninstall()

307123

InterruptedException not catch in Components on accept() when Petals stops

306825

[Samples] SE Clock does not return its WSDL

306815

server.properties is overwriten when server starts