h1. Petals Studio 1.3

Here are the new and noteworthy features of Petals Studio 1.3.

{note}The main work in this version was about changing the way the tooling was implemented. This work was necessary to provide a better user experience in the next versions. Therefore, you should see this version as an intermediate (stable) release.

\\
This version supports all the components released with the last distribution of Petals (called Petals 4).{note}

h2. Petals Creation Wizards

Petals creation wizards were reorganized.

!petals-studio-nnn-4.jpg!

\\
The *Service Unit* wizard was splitted and replaced by two new wizards.
Service Unit is a term inherited from JBI to define an artifact. Petals Studio made a move to a more functional terminology. There is now a wizard to create *Petals services* (service providers)...

!petals-studio-nnn-9.jpg!

\\
... and a wizard to create *service consumers*.

!petals-studio-nnn-8.jpg!

\\
This makes sense with the methodology we try to push with our users.

!petals-studio-nnn-5.jpg!

Note that the created projects have the same structure than before.
Former projects are still working with this version.

\\
These wizards also have less pages than before, and only show the meaningful fields to complete.
For service providers, there are few changes. There is now an option to not import the WSDL in the final project. This way, it is possible to centralize XML schemas and WSDL on a web server (as an example).

!petals-studio-nnn-6.jpg!

\\
For service consumers, the first page is now richer than before.

!petals-studio-nnn-11.jpg!

\\
The helper has changed a little bit for the occasion.

!petals-studio-nnn-10.jpg!

\\
You can directly associate a Petals service project with a working set.

!petals-studio-nnn-7.jpg!

h2. EIP

The wizard to create EIP service units has been removed.
The use of croquis is now mandatory.

!petals-studio-nnn-2.jpg!

\\ Croquis have a graphical editor to build EIP chains.

!petals-studio-nnn-1.jpg!

\\
This kind of croquis can either be exported as a Petals service assembly, or as a set of Petals Maven projects.
The service assembly export is useful for demonstrations and tests.
The Petals project export is useful for continuous integration using the Petals Maven plug-in.

!petals-studio-nnn-3.jpg!

h2. JBI Editors

The key files files with Petals are named *jbi.xml*.
Many changes have been done here.

First, source edition and form edition have been completely separated.

!petals-studio-nnn-12.jpg!

\\
The form editor was redesigned. It now provides a main tab, an advanced one and a source view (read-only).

!petals-studio-nnn-13.jpg!

\\
!petals-studio-nnn-14.jpg!

\\
!petals-studio-nnn-15.jpg!

\\
This editor allows to edit almost all the fields of a jbi.xml file.

!petals-studio-nnn-16.jpg!

h2. POJO

The wizard to create POJO service units has been reviewed.

!petals-studio-nnn-17.jpg!

\\
You can now create a Java project, with a default POJO implementation and the right libraries in the class path.

\\
!petals-studio-nnn-18.jpg!

h2. BPEL

Petals Studio 1.3 relies on the official BPEL Designer from the Eclipse Foundation.
Contributions were done for this. The new BPEL wizard was completely reviewed.
You can either start with a template...

!petals-studio-nnn-19.jpg!

\\
!petals-studio-nnn-20.jpg!

\\
... or you can generate a skeleton from a WSDL definition (top-down approach).

!petals-studio-nnn-21.jpg!

\\
!petals-studio-nnn-22.jpg!

h2. Miscellaneous

This version works with Petals 4 and the main features of Petals 3.
It means old features from Petals 3, which are not part of Petals 4, were removed from the studio.
* No more support for the KPI component and Petals View.
* No more support for SCA.
* No more support for REST.

\\
This version contains:
* Many bug fixes (in particular on EIP croquis).
* Minor enhancements.