Greetings dear Petals users,
we are very glad to announce the public availability of our latest ESB, Petals ESB 4.0!
This distribution packs sweeties.

• Latest container with new kernel 3.2, which brings strong enhancements under the hood: beyond usual performance/stability profits, many parts have been rewritten to prepare for exciting new features (yeah, we're teasing you :)). Beware though, in spite of our care, there may be a few regressions, which we'll detect and fix as fast as we can.
• A new business monitoring system: no more Petals View+KPI, now all is based on plain texts logs, for extensive configurability and choice in third-party exploitation tool.
• A new Command Line Interface: now brings all essential administration tools in one dedicated shell, usable locally or remotely (including replacement for old "stop" and "shutdown" scripts).
• Pack of updates for most used components, to make them compatible with the new monitoring: Filetransfer, FTP, Mail, SFTP, SOAP, SQL, BPEL, EIP, JSR, Quartz, Validation, XSLT.
• BC-SOAP now supports WS-Security and SSL connexions.
• BC-Filetransfer is simpler to use as a service provider, and is now ready for high availability use-cases as a consumer.
• Petals startup script has been improved, using your feedback as guidelines.

Also, please note that package structure of the container and our versioning policy has slightly evolved. 

You're welcome to download Petals ESB 4.0 and try it at work... Or at home? For more information about an individual novelty, please refer to previous news on the blog.

We hope you'll enjoy Petals ESB 4.0, and are waiting for your feedback on Petals forum.

 

Petals ESB 3.1.3 maintenance version was just released. It includes both 3.1.2 and 3.1.3  container fixes, and a SE-POJO maintenance version.

Download: Petals ESB 3.1.3 - Petals-SE-POJO 2.2.5

Release note :

Bug

• [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 Request

• [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

 

These maintenance versions correct a few bugs, including a fix for notifications in SE-BPEL.

Downloads :

petals-se-bpel-1.0.6.zip

30-Nov-2010 09:00

11M

petals-webconsole-ui-2.0.5.war

Mon Nov 22 10:37:16 CET 2010

5715360

Compatible with Petals ESB 3.1.1+

Bug fixes:

• [PETALSSEBPEL-14] - Notifications are not sent on responses (fault or out message)
• [PETALSWEBC-31] - NumberFormatError when we refresh an empty domain
• [PETALSWEBC-33] - NPE during management server page displaying
• [PETALSWEBC-35] - NPE from webconsole service layer
• [PETALSWEBC-37] - Unable to correctly recover wsdl for endpoint

Improvements:

• [PETALSWEBC-7] - The package javax.activation is embedded twice
• [PETALSWEBC-36] - Avoid to load all endpoints for each node

Petals components were updated. They include a new CDK, to update notification system. EIP, Jsr-181 and SQL got a few more modifications.
Work with Petals ESB 3.0.6+ et 3.1.1+

Changelogs:

Download link:

petals-bc-ejb-1.3.zip

10-Nov-2010 09:15

12M

petals-bc-mail-3.1.4.zip

03-Nov-2010 14:39

5.4M

petals-bc-sql-1.2.zip

03-Nov-2010 11:14

5.1M

petals-bc-soap-4.0.4.zip

02-Nov-2010 18:22

17M

petals-bc-filetransfer-2.4.4.zip

02-Nov-2010 17:28

5.0M

petals-bc-sftp-1.2.1.zip

02-Nov-2010 17:13

5.3M

petals-bc-ftp-3.3.1.zip

02-Nov-2010 16:51

5.2M

petals-se-jsr181-1.1.3.zip

08-Nov-2010 13:47

14M

petals-se-xslt-2.3.4.zip

03-Nov-2010 14:22

5.0M

petals-se-xslt-2.4.1.zip

03-Nov-2010 12:22

5.0M

petals-se-validation-1.1.3.zip

03-Nov-2010 12:19

5.0M

petals-se-quartz-1.1.2.zip

03-Nov-2010 12:15

5.4M

petals-se-talend-1.0.2.zip

03-Nov-2010 12:05

5.0M

petals-se-pojo-2.2.4.zip

03-Nov-2010 11:04

5.0M

petals-se-eip-2.5.zip

03-Nov-2010 10:02

5.0M

petals-se-kpi-1.1.1.zip

03-Nov-2010 10:07

19M

petals-se-bpel-1.0.5.zip

03-Nov-2010 08:44

11M

petals-se-notification-1.0.3.zip

02-Nov-2010 17:37

5.0M

Petals Master, Petals SOA governance platform, was released as version 1.1.

Download link:

http://download.forge.objectweb.org/petalsmaster/PetalsMaster-1.1.war

Release note:

Improvements

• Remove hardlink between Service and WSDL

• Creation from scratch of a service (+ delete)
• Add a wsdl to an existing service (+ delete)
• Edit service info : name, description

• Manage service endpoints

• Creation from scratch of a service endpoint (+ delete)
• Add wsdl to an existing endpoint (+ delete)
• Edit endpoint info : name, address, environment
• Add the concept of endpoint environment : dev, prod, QA, etc.

Bug fix

• Fix : Suppress email constraint : now supports email likefoo.bar@toto.biz.fr
• Fix : Suppress constraint on endpoint name : now you could create two endpoints with the same name for two different services
• Fix : Many bug with oracle 10g database (table names, etc.)
• Fix : [PETALSMASTER-10] - Impossible to consult service with UDDI V3 API
• Fix : [PETALSMASTER-11] - Unable to customize taxonomies
• Fix : [PETALSMASTER-12] - Petals Master doesn't start offline

Petals ESB 3.1.1 was released ! This version includes lots of corrections and a few new features: Message priority, selective message persistence, filtered monitoring in webconsole.
Petals ESB 3.0.6 was also released as maintenance version, to use latest components.
Warning: Please do not activate notification with both versions. Another maintenance version will come with stable notification.

Released

• Petals ESB-Container 3.1.1 (and 3.1)
• Petals ESB-Container 3.0.6
• Internal: CDK 5.1
• Internal: WS-Notification 1.2.1 (for Petals View)
• Webconsole 2.0.4 (and 2.0.3)
• BC-Filetransfer 2.4.3
• BC-FTP 3.3
• BC-Mail 3.1.3
• BC-SFTP 1.2
• BC-SOAP 4.0.3
• SE-BPEL 1.0.4 (and 1.0.3)
• SE-KPI 1.1
• SE-XSLT 2.4
• SE-Talend 1.0.1

New Features

• [PETALSCDK-11] - Persist and resend notifications when problem occurs
• [PETALSCDK-13] - Add client API for notifications
• [PETALSCDK-17] - Add asynchronous client API for notifications
• [PETALSBCSOAP-34] - Axis 1 webservice stack compatibility
• [PETALSBCSFTP-22] - Add overwrite parameter
• [PETALSBCFTP-11] - Add overwrite parameter
• Petals ESB Container 3.1 - Regulates message flow across Petals domain
• Petals ESB Container 3.1 - Handles message priorities across Petals domains
• Petals ESB Container 3.1 - Persist messages when memory usages reach a given value
• Petals ESB Container 3.1 - Persist messages that are monitored in Webconsole
• Petals Webconsole 2.0.3 - Technical monitoring is back, with changes in Petals ESB collection

Improvements

• [PETALSCDK-9] - Improve notification provider subscription process
• [PETALSCDK-12] - Improve notification subscriber support
• [PETALSCDK-28] - Format the JBI descriptor with indentation
• [PETALSCDK-29] - Enhance the Fault management from error raising during InOut MEP process
• [WSNOTIF-1] - Create Document Builders on each notification requests
• [WSNOTIF-2] - Create Unmarshaller on each notification requests
• [WSNOTIF-3] - Convert Dom document into JDom one on each notification request
• [PETALSSEXSLT-1] - Improve the log management
• [PETALSSEXSLT-3] - Improve log & xsl error detection accuracy
• [PETALSSEXSLT-4] - Remove process related information from the INFO log
• [PETALSSEXSLT-6] - (AS-014) Having specific jbi.xml fields that would be parameters sent to the XSL at runtime
• [PETALSSEXSLT-12] - Properties of the incoming message should be passed to the XSL stylesheet as parameter
• [PETALSSEXSLT-14] - The SE should respect the InOut MEP
• [PETALSSEXSLT-15] - Some libraries are duplicated into the component archive
• [PETALSSEKPI-2] - Provide more than one consumes into the same service unit
• [PETALSSEKPI-3] - Parameters In/Out/Fault
• [PETALSSEKPI-4] - Log4j configuration file
• [PETALSSEBPEL-2] - JDOM to DOM conversion generate double namespace in AXIOM at marshal time
• [PETALSBCSOAP-15] - Resolve the target operation and MEP in consume mode
• [PETALSBCSOAP-38] - Remove the SU parameters add-root and remove-root
• [PETALSBCSOAP-39] - JMS parameters should be settable from the configuration MBean
• [PETALSBCSOAP-41] - wrong log level when ctaching axis exception
• [PETALSBCSOAP-48] - The fault actor is not transmitted in the SOAP fault in the consumer mode
• [PETALSSETAL-8] - Log the bus messages in DEBUG
• [PETALSSETAL-7] - Add 'processor-max-pool-size' and 'properties-file' in the component's jbi.xml
• Petals SE-BPEL 1.0.3 - Performance optimizations, up to 4x faster
• Petals Webconsole 2.0.3 - Improved monitoring performances (by filtering selected monitoring monitoring)
• Petals SE-Talend 1.0.1 - Compatible with Talend Open Studio 4.1.0

Bugs fixed

• [PETALSESBCONT-19] - Leak on PriorityOrdererModule
• [PETALSESBCONT-21] - StackOverflowError dans la WebConsole
• [PETALSESBCONT-33] - java.lang.ArrayIndexOutOfBoundsException when registring an endpoint without interface
• [PETALSESBCONT-40] - Error stack trace when stopping an empty container
• [PETALSESBCONT-46] - Classloader isolation uncomplete
• [PETALSESBCONT-60] - Too many open Files when sending attachment to remote node
• [PETALSESBCONT-61] - Prevent a container to override it's own configuration when synchronizing its topology.
• [PETALSCDK-6] - [CDK] RejectedExcecutionException is not correclty catched in the JBI acceptor
• [PETALSCDK-22] - Error on JBI Worker during performance tests
• [PETALSCDK-23] - Unpredictable FileNotFoundException: /createCustomer.xsd (No such file or directory)
• [PETALSCDK-25] - The CDK activate notification endpoints even if notification is off
• [PETALSWEBC-2] - StackTrace cause by OpenSUIT handling
• [PETALSWEBC-27] - Same service assembly deployement
• [PETALSSEXSLT-2] - [SE-XSLT] Can't import properly XSL stylesheet with imports
• [PETALSSEXSLT-8] - Imports are not correctly handled
• [PETALSSEXSLT-9] - Unable to load the XSL using the classloader
• [PETALSSEXSLT-11] - Unable to start the component if SE Notif is not available
• [PETALSBCSOAP-2] - When handling SOAP faults, faultCode can have an unbounded prefix.
• [PETALSBCSOAP-16] - Some traces are not handled by the component logger and some others at a level too high
• [PETALSBCSOAP-17] - As consumer, the timeout of a sendSync is not properly logged
• [PETALSBCSOAP-19] - Modules are loaded even if they are not set in configuration
• [PETALSBCSOAP-24] - Can't create get an Axis service client from the pool
• [PETALSBCSOAP-26] - NPE in the Petals console
• [PETALSBCSOAP-28] - Propagate partner's SOAP Fault "as is"
• [PETALSBCSOAP-32] - Log that JMS is activated whereas the SU configuration specifies not.
• [PETALSBCSOAP-35] - SOAP over JMS - A queue is created on the JMS server when installing a SU even if the JMS transport parameter is disabled
• [PETALSBCSOAP-40] - Unable to start the component if SE Notif is not available
• [PETALSBCSOAP-42] - BC soap returns wrong WSDL.
• [PETALSBCSOAP-43] - Change the default host in the jbi.xml of the component to 0.0.0.0
• [PETALSBCSOAP-44] - Error when uninstalling a SU REST
• [PETALSBCSOAP-45] - 0.0.0.0, the default host, crashes the component under some OS
• [PETALSBCSFTP-3] - The SSH/SFTP connections are not properly handled.
• [PETALSBCSFTP-7] - Parameter "folder" is marked as optionnal
• [PETALSBCSFTP-18] - SFTP connection not reset
• [PETALSBCSFTP-26] - Unable to start the component if SE Notif is not available
• [PETALSBCMAIL-11] - Unable to start the component if SE Notif is not available
• [PETALSBCFTP-14] - Unable to start the component if SE Notif is not available
• [PETALSBCFTP-17] - <folder> attribute written as optionnal, but sends a fault when not specified in my case
• [PETALSBCFTP-19] - [FTP] No error returned when remote directory is unavailable
• [PETALSBCFTRANS-10] - Unable to start the component if SE Notif is not available
• [PETALSBCFTRANS-12] - Consume mode, error when polled directory is unreachable
• [PETALSSETAL-4] - Use the exceptions that are declared in the WSDL
• [PETALSSETAL-5] - Unable to start the component if SE Notif is not available
• [PETALSSETAL-9] - Input streams are not closed correctly

Petals Studio 1.1.1 has just been released. Release note:

New Features

• New shortcut to export Service Assembly projects with a right-click action.
• Basic validation on "MEP" and "operation" fields in "consumes" sections (except for SOAP).
• The BPEL validation now resolves the line numbers for every found error and warning.
• Support for the Petals-BC-FileTransfer 3.0.
• Support for the Petals-BC-FTP 3.2.
• Support for the Petals-BC-SFTP 1.2.
• Support for the Petals-SE-EIP 2.5.
• ANT's view is now part of the studio.
• The POJO's creation wizard now allows to directly create a Java project.
• The studio now supports updates of "native" plug-ins.
• Support for the Petals-BC-FTP 3.3.
• Addition of an action to explicitly validate jbi.xml files.
• Brand new creation wizard for the JSR-181 component (WSDL-first and implementation-first approaches).
• SA projects: update the POM dependencies automatically (associated entry in the preferences).
• SA projects: right-click action to explicitly update the POM depdendencies of a SA project.
• Support for the Petals-SE-XSLT 2.4.
• XSLT projects now have a builder, similar to the one used in the XSLT SE (it prevents most of the deployment errors).
• The XSLT component wizard can now generate a default XSL style sheet.
• The Validation component wizard can now generate a default XML schema.
• It is now possible to directly create a BPEL Service-Unit project.
• Java SU projects can now directly be exported within the studio (Jsr-181, SCA, POJO).
• Update sites for development tools were pre-registered (FindBuds, PMD, CheckStyle).
• Be able to refactor a SU project (by changing the service name).
• Add a wizard to easily create a new Petals reference (SCA).
• Maven POM customisation (wizard configuration through a preference page).
• It is now possible to directly create a SCA Service-Unit project.

Improvements

• POMs for Service-Unit and Service Assembly projects are now complete and ready-to-use.
• Merge of the different JBI editors into a single one.
• Lighter and more simple BPEL process in the "BPEL wizard > New BPEL".
• Line numbers for errors found in JBI validation are now resolved whatever editor is used.
• The EJB wizard has been updated to ease the WSDL generation.
• A Service Assembly project is now validated when one of its Service-Unit projects changes.
• Allow the removal of several Service-Units at once in the Service Assembly editor.
• Drag'n'Drop of Petals end-points onto the BPEL Designer: default choices.
• Drag'n'Drop of Petals end-points onto the BPEL Designer: generated variables with the right message type.
• Drag'n'Drop of Petals end-points onto the BPEL Designer: drop at the right position in sequences.
• Drag'n'Drop of Petals end-points onto the BPEL Designer: role definition in existing WSDL and not always in the artifact WSDL).
• Validate jbi.xml files in Service-Unit projects when a WSDL file changes.
• Allow to overwrite projects in Service Assembly import and sketch export wizards.
• The User Interface was updated in the BPEL Designer (palette and dashboard).
• The CDK page was removed from the BPEL wizard (it was useless).
• The generated files for Petals-SE-KPI now list optional elements in comments (XPath and SOA dialects).
• The BPEL nature is now added by default on BPEL projects resulting from a sketch export.
• Newly created BPEL files are now open in the BPEL Designer on wizard completion.
• The User Interface in the Service Assembly's import wizard was updated.
• Always import the partner's WSDL on a drag'n'drop from the end-points explorer.
• Use relative locations when it is possible, in BPEL files and WSDL artifacts.
• The default WSDL for XSLT and Validation components were updated (useful fixes to use them with BPEL).
• The Jsr181's creation wizard has changed (now a Java project, with a default JAX-WS implementation).
• Do not try to show the welcome page if it is already displayed.
• The EIP plug-in was moved in the core feature.
• The Quartz wizard now only lists the MEP this component supports.
• Files can now be dragged an dropped from the Petals Projects explorer.
• The registration page can now restore information when a new version is installed (including proxy settings).
• Update of the KPI wizard to create watching configurations based on XPath expressions.
• Update of the default WSDL for the Petals Mail component.
• Update of the default WSDL for the Petals XSLT component.
• The wizard for the XSLT component can now create a default XSL style sheet.
• The JBI fields are now read-only in the 'provides' wizards if a WSDL is selected.
• The EIP wizard now supports the definition of a consumer defined with only an interface and service names.
• It is now possible to specify Service-Unit projects to add in the new Service Assembly project wizard.
• It is now possible to import several service assemblies at once.
• SA projects are now validated when a SU project is removed, refreshed or added in the workspace.
• FindBugs was removed from the studio. It should now be installed apart.
• Show line numbers in text editors (by default).
• Choose EIP's consumed end-points from the Petals Services view
• Soap UI was removed from the studio. It should now be installed apart.
• POM files can now be validated off-line (without an internet connection).
• "Sketch projects" have been renamed into "Croquis".
• The SOAP consume field "soap-address" is depreciated.
• Replace the JBI binding editor by tabbed properties (SCA).
• The dialog to choose the services to invoke is not enough intuitive (EIP).
• Add an XPath field in the EIP wizard for the aggragator correlation.
• Remove the useless parameters in the REST wizard.
• Remove remove-root and add-root parameters from the SOAP and REST wizard.
• REST parameter when creating a SOAP SU consume.
• Add a preference to display JAX-WS traces.
• Add an action to directly create the service WSDL's (SCA).
• Croquis for SCA have been disabled.
• Use the BPEL's XML schemas to validate BPEL files with the XML editor.
• Generate only one KPI SU for a given end-point.
• Remove a restriction when deleting several resources at once.
• Support the copy of several (non-sibling) resources at once

Bugs fixed

• Correct handling of environment variables in the Service-Unit wizards.
• WSDL import was fixed for WSDL which import files located above them.
• XML schemas used in the editor contained an illegal character.
• The (EIP) Splitter patttern needs a condition in its configuration.
• WSDL generated by the EJB wizard with Apache CXF are now correct.
• The WSDL generation with Apache CXF for the EJB wizard does not throw an error anymore (Linux).
• New Service-Unit projects for the EJB component are now correctly refreshed and synchronized.
• SCA files are now created in the 'java' directory (instead of the 'jbi' one).
• Various warnings were removed (logs).
• Generate a correct BPEL file from a WSDL file.
• WSDL locations written in WSDL artifacts are now correct (URL instead of file locations - BPEL Designer).
• Allow update-parsing of WSDL in the Service-Unit wizard (parse the same URL).
• Do not fill-in the operation and a MEP when creating a SOAP consume in the BPEL sketch export.
• Allow reedition of CDK parameters in the EIP wizard (definition of consumed services).
• Character encoding was fixed in registration.
• Bug fix in Service Assembly import (component names with white spaces around).
• The JBI editor now handles correctly file deletion and file moves (closed editor or updated part name).
• Update the Petals project explorer when a Service-Unit project is added to (or removed from) a Service Assembly project.
• Fixed a bug from the BPEL Designer in variable filtering (variable's combo in invoke properties).
• The BPEL Drag'n'Drop works on Linux.
• Drag'n'Drop of Petals end-points onto the BPEL Designer: check variable existence before creating a default one.
• The validation of the CDK field 'operation' now reacts when the name space URI is changed.
• Import correctly WSDL files with several "schema import" mark-ups.
• Manual creation of partner links has been fixed in the BPEL designer.
• Properties of exported Sketch projects are now correctly handled.
• Prevent line number resolution from failing (validation marker).
• Fix: Error when creating component projects (Linux).
• Problem with Studio when a WSDL contains multiple ports (creating SOAP provider).
• Fix: the service DnD erases some imports from the Artifacts WSDL (BPEL).

Petals ESB 3.0.6 was released. It adds minor corrections and compatibility with latest component version.
Note: notification should not be activated with this release. Next maintenance release will include stable notification.

Bugs fixed:

• [PETALSESBCONT-46] - Classloader isolation uncomplete
• [PETALSESBCONT-60] - Too many open Files when sending attachment to remote node
• [PETALSESBCONT-61] - Prevent a container to override it's own configuration when synchronizing its topology.

Petals Studio 1.0 was released ! This is a small step for Petals and a great step for developers.
As the first stable release, Petals Studio 1.0 includes a lot of enhancements, which will make Petals easier and faster for you. Here are some

• Unified Petals ESB Wizards
• Sketching for BPEL and SCA
• Organize the workspace by Projects or Services (endpoints)
• Text editor, with auto-completion, for JBI, SU and SA
  
• Extended validation for JBI, SU and SA
  
• Import existing WSDL with dependencies
• Project export
• Interaction with Petals ESB Server
• Compatible with Linux and Windows, 32 and 64 bit
  

Get more details on this release + Screenshots

Download Petals Studio 1.0