h1. Petals Studio 1.2
Here are the new and noteworthy features of Petals Studio 1.2.
h2. Service Unit Wizard
The creation wizard for service units now proposes usage categories.
These categories replace the former _use cases_ that were in fact very specific to the Petals terminology.
!petals-studio-nnn-5.jpg!
!petals-studio-nnn-6.jpg!
\\
An important progress was made to help users in selecting operations to consume.
In the wizards to create a service consumer, there is now a helper to select the service operation to invoke.
!petals-studio-nnn-7.jpg!
\\
In the case where the service does not have a WSDL, the Petals target component will be found and native operations will be proposed.
If no operation is found, it will have to be typed in manually.
\\
Besides, the wizard page to select a service to invoke has changed.
!petals-studio-nnn-23.jpg!
\\
The consumption dialog now filters invocable services.
It means that when you select a service to consume, only those that are technically invocable are shown.
!petals-studio-nnn-24.jpg!
\\
This preference can be changed to display all the services.
!petals-studio-nnn-8.jpg!
\\
In the same dialog, target components are now visible.
!petals-studio-nnn-12.jpg!
h2. EIP
There is now a graphical editor to build EIP chains in Petals Studio.
!petals-studio-nnn-1.jpg!
\\
Such chains can be created through an _EIP croquis_.
!petals-studio-nnn-2.jpg!
\\
This 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!
\\
The usual service unit wizard for EIP still exists but is now deprecated.
However, for those who would stick to this wizard, be noticed that its user interface was a little bit improved.
!petals-studio-nnn-4.jpg!
h2. Utilities
Petals Studio provides some utility wizards related to Web services and WSDL:
* Create a Web service client.
* Create a Java interface from a WSDL definition.
* Generate a WSDL from a Java interface.
!petals-studio-nnn-10.jpg!
!petals-studio-nnn-11.jpg!
\\
There is another utility to associate a Petals component with a shared library.
It is a very handy alternative to the Petals Maven plug-in.
!petals-studio-nnn-19.jpg!
h2. Miscellaneous
The EJB wizard was simplified.
Besides, the studio now embeds Apache CXF. You do not have to download it and configure the _WSDL preferences_ anymore.
!petals-studio-nnn-9.jpg!
\\
The File Transfer wizard was reviewed to be more explicit and more intuitive.
In provider mode...
!petals-studio-nnn-20.jpg!
!petals-studio-nnn-21.jpg!
\\
... and in consumer mode.
!petals-studio-nnn-22.jpg!
\\
There is now a *Generic* component in the Service Unit wizard.
It allows to create service units for components that are not natively supported by the studio.
!petals-studio-nnn-25.jpg!
\\
The Petals projects view now shows the Java packages like in the Package explorer.
!petals-studio-nnn-13.jpg!
\\
What is displayed by this view can be configured using its menu.
!petals-studio-nnn-14.jpg!
\\
Shared Libraries can be created from the studio.
Like for components, it is a simple _façade_ for the Petals Maven plug-in.
!petals-studio-nnn-15.jpg!
\\
The service unit validation now checks the invoked operations and the invocation patterns (MEP).
!petals-studio-nnn-16.jpg!
\\
The Drag'n'Drop of Petals services onto a BPEL diagram now opens a dialog to select the operation to invoke.
!petals-studio-nnn-17.jpg!
\\
The BPEL croquis has been replaced by an export wizard.
Select a BPEL file from your work space and generate from it a set of Petals Maven projects.
This is useful to make any BPEL process run in Petals ESB.
!petals-studio-nnn-18.jpg!
E-mail
...