E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (89)
View Page Historyh1. Petals Studio 1.23
Here are the new and noteworthy features of Petals Studio 1.23.
h2. Service Unit Wizard
{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.
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.
These categories replace the former _use cases_ that were in fact very specific to the Petals terminology.
\\
This version supports all the components released with the last distribution of Petals (called Petals 4).{note}
This version supports all the components released with the last distribution of Petals (called Petals 4).{note}
!petals-studio-nnn-5.jpg!
h2. Petals Creation Wizards
!petals-studio-nnn-6.jpg!
Petals Creation Wizards were reorganized.
!petals-studio-nnn-4.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.
In the wizards to create a service consumer, there is now a helper to select the service operation to invoke.
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)...
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-79.jpg!
... and a wizard to create *service consumers*.
!petals-studio-nnn-8.jpg!
!petals-studio-nnn-8.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.
If no operation is found, it will have to be typed in manually.
This makes sense with the methodology we try to adopt with our users.
!petals-studio-nnn-5.jpg!
However, note that the created projects have the same structure than before.
So, former projects are still working with this version.
However, note that the created projects have the same structure than before.
So, former projects are still working with this version.
\\
Besides, the wizard page to select a service to invoke has changed.
These wizards also have less pages than before, and only show the meaningful fields to complete.
For service providers, there are few changes. Note that there is an option now 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).
For service providers, there are few changes. Note that there is an option now 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-23.jpg! !petals-studio-nnn-6.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.
It means that when you select a service to consume, only those that are technically invocable are shown.
For service consumers, the first page is now richer than before.
!petals-studio-nnn-24.jpg! !petals-studio-nnn-11.jpg!
\\
This preference can be changed to display all the services.
The helper has changed a little bit for the occasion.
!petals-studio-nnn-8.jpg! !petals-studio-nnn-10.jpg!
\\
In the same dialog, target components are now visible.
Notice that Petals projects now natively support working sets.
!petals-studio-nnn-12.jpg! !petals-studio-nnn-7.jpg!
h2. EIP
There is now a graphical editor to build EIP chains in Petals Studio.
The wizard to create EIP service units has been removed.
The use of croquis is now mandatory.
The use of croquis is now mandatory.
!petals-studio-nnn-12.jpg!
\\
Such chains can be created through an _EIP croquis_.
Such chains can be created through an _EIP croquis_.
\\ Croquis have a graphical editor to build EIP chains.
!petals-studio-nnn-21.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.
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.
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.
h2. JBI Editors
!petals-studio-nnn-4.jpg!
The key files files with Petals are named jbi.xml.
Many changes have been done here.
Many changes have been done here.
h2. Utilities
First, source edition and form edition have been completely separated.
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.
* Create a Web service client.
* Create a Java interface from a WSDL definition.
* Generate a WSDL from a Java interface.
!petals-studio-nnn-12.jpg!
!petals-studio-nnn-10.jpg! \\
The form editor was redesigned. It now provides a main tab, an advanced one and a source view (read-only).
!petals-studio-nnn-113.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.
It is a very handy alternative to the Petals Maven plug-in.
!petals-studio-nnn-14.jpg!
!petals-studio-nnn-19.jpg! \\
!petals-studio-nnn-15.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 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...
In provider mode...
This editor allows to edit almost all the fields of a jbi.xml file.
!petals-studio-nnn-20.jpg! !petals-studio-nnn-16.jpg!
!petals-studio-nnn-21.jpg!
h2. POJO
\\
... and in consumer mode.
... and in consumer mode.
The wizard to create POJO service units has been reviewed.
!petals-studio-nnn-22.jpg! !petals-studio-nnn-17.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.
It allows to create service units for components that are not natively supported by the studio.
You can now create a Java project, with a default POJO implementation and the right libraries in the class path.
!petals-studio-nnn-25.jpg! !petals-studio-nnn-18.jpg!
\\
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.
h2. BPEL
!petals-studio-nnn-13.jpg!
Petals Studio 1.3 now rely 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...
Contributions were done for this. The new BPEL wizard was completely reviewed.
You can either start with a template...
\\ !petals-studio-nnn-18.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.
Like for components, it is a simple _façade_ for the Petals Maven plug-in.
!petals-studio-nnn-20.jpg!
!petals-studio-nnn-15.jpg!
\\
The service unit validation now checks the invoked operations and the invocation patterns (MEP).
... or you can generate a skeleton from a WSDL definition (top-down approach).
!petals-studio-nnn-16.jpg! !petals-studio-nnn-21.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-22.jpg!
!petals-studio-nnn-17.jpg!
h2. Miscellaneous
\\
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.
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.
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.
This includes:
* No more support for the KPI component and Petals View.
* No more support for SCA.
* No more support for REST.
It means old features from Petals 3, which are not part of Petals 4, were removed.
This includes:
* No more support for the KPI component and Petals View.
* No more support for SCA.
* No more support for REST.
!petals-studio-nnn-18.jpg!
\\
This version also contains:
+ Many bug fixes (in particular on EIP croquis).
+ some minor enhancements
+ some underlying changes (based on Eclipse Helios, built with Maven Tycho...)
+ some underlying changes (based on Eclipse Helios, built with Maven Tycho...)
+ Minor enhancements.
+ Some underlying changes (based on Eclipse Indigo, built with Maven Tycho, tests with SWT Bot...).
+ Some underlying changes (based on Eclipse Indigo, built with Maven Tycho, tests with SWT Bot...).
See [the complete release note|http://jira.petalslink.com/secure/ReleaseNote.jspa?projectId=10070&version=10079] note|http://jira.petalslink.com/secure/ReleaseNote.jspa?projectId=10070&version=10190] for more details...