E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (67)
View Page Historyh1. Petals Studio 1.12
Here are the new and noteworthy features of Petals Studio 1.12.
h2. BPEL
h2. Service Unit Wizard
It is now possible to directly create a Service-Unit project for BPEL.
BPEL croquis (sketches) remain an alternative.
BPEL croquis (sketches) remain an alternative.
Creation wizards are now categorized.
These categories replace the former _use cases_ that were in fact specific to the Petals terminology.
These categories replace the former _use cases_ that were in fact specific to the Petals terminology.
!petals-studio-nnn-15.jpg!
\\ !petals-studio-nnn-6.jpg!
The BPEL Designer has a new layout.
!petals-studio-nnn-3.jpg!
\\
The creation of BPEL processes from a WSDL has been fixed.
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.
In the wizards to create a service consumer, there is now a helper to select the service operation to invoke.
!petals-studio-nnn-27.jpg!
\\
The direct creation of partner links has been fixed.
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.
If no operation is found, it will have to be typed in manually.
!petals-studio-nnn-4.jpg! \\
Besides, notice that the consumption dialog now filters invocable services.
It means that when you select a service to consume, only those that are technnically invocable are shown.
This preference can be changed to display all the services.
It means that when you select a service to consume, only those that are technnically invocable are shown.
This preference can be changed to display all the services.
h2. Jsr181
!petals-studio-nnn-8.jpg!
The creation for the Petals Jsr181 component was completely changed.
It now directly creates a Java project. It supports WSDL-first and Java-first approaches.
The Java export is similar to the usual Petals export.
It now directly creates a Java project. It supports WSDL-first and Java-first approaches.
The Java export is similar to the usual Petals export.
\\
In the same dialog, target components are now visible.
In the same dialog, target components are now visible.
!petals-studio-nnn-5.jpg|thumbnail! !petals-studio-nnn-6.jpg|thumbnail! !petals-studio-nnn-7.jpg|thumbnail!
!petals-studio-nnn-12.jpg!
h2. Other wizards
h2. EIP
The XSLT wizard supports both the import and the creation of a XSL style-sheet.
It can also generate a default WSDL and validate XSL style-sheets while being edited.
It can also generate a default WSDL and validate XSL style-sheets while being edited.
There is now a graphical editor to build EIP chains in Petals Studio.
!petals-studio-nnn-81.jpg!
\\
The XSLT wizard supports both the import and the creation of a XML schema.
It can also generate a default WSDL.
It can also generate a default WSDL.
Such chains can be created through an _EIP croquis_.
!petals-studio-nnn-92.jpg!
\\
The user interface and the validation in the EIP wizard was improved.
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.
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-10.jpg! !petals-studio-nnn-3.jpg!
h2. SCA support
\\
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.
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.
Service-Unit projects for SCA can directly be created.
!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 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!
\\
Three creation patterns are proposed: empty composite, simple Petals service and service orchestration.
Three creation patterns are proposed: empty composite, simple Petals service and service orchestration.
!petals-studio-nnn-12.jpg|thumbnail! !petals-studio-nnn-13.jpg|thumbnail! !petals-studio-nnn-14.jpg|thumbnail!
h2. Miscellaneous
\\
The JBI binding editor was replaced by an enhanced tab property section.
The JBI binding editor was replaced by an enhanced tab property section.
The EJB wizard has been simplified.
Besides, the studio now embeds Apache CXF. You do not have to download it and configure the WSDL preferences anymore.
Besides, the studio now embeds Apache CXF. You do not have to download it and configure the WSDL preferences anymore.
!petals-studio-nnn-15.jpg|thumbnail!
!petals-studio-nnn-9.jpg!
h2. Other features
\\
The Petals projects view now shows the Java packages like in the Package explorer.
The Petals projects view now shows the Java packages like in the Package explorer.
JBI descriptors can be validated explictely.
!petals-studio-nnn-13.jpg!
!petals-studio-nnn-16.jpg! \\
What is displayed by this view can be configured using its menu.
!petals-studio-nnn-14.jpg!
\\
Service Assembly projects have a shortcut to package them.
Shared Libraries can be created from the studio.
Like for components, it is a simple _façade_ for the Petals Maven plug-in.
Like for components, it is a simple _façade_ for the Petals Maven plug-in.
!petals-studio-nnn-175.jpg!
\\
It is now possible to refactor Petals projects.
For Service-Unit projects, it can be used to change service names in both the jbi.xml and a WSDL.
For Service-Unit projects, it can be used to change service names in both the jbi.xml and a WSDL.
The service unit validation now checks the invoked operations and the invocation patterns (MEP).
!petals-studio-nnn-18.jpg|thumbnail! !petals-studio-nnn-19.jpg|thumbnail! !petals-studio-nnn-20.jpg|thumbnail!
!petals-studio-nnn-16.jpg!
\\
Maven support was drastically improved in this new version of the studio.
Default POM are ready-to-be-used with the Petals Maven plug-in.
POM files can also be customized through templates specified in the preferences (up to a template per Petals component).
Default POM are ready-to-be-used with the Petals Maven plug-in.
POM files can also be customized through templates specified in the preferences (up to a template per Petals component).
The Drag'n'Drop of Petals services into the a BPEL diagram now opens a dialog to select the operation to invoke.
!petals-studio-nnn-21.jpg! !petals-studio-nnn-17.jpg!
\\
The wizard to import a service assembly was updated.
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 file run in Petals ESB.
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 file run in Petals ESB.
!petals-studio-nnn-22.jpg! !petals-studio-nnn-18.jpg!
\\
+ bug fixes
+ some minor enhancements