E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (79)
View Page Historyh1. Petals Studio 1.01
h2. Creation Wizards
Here are the new and noteworthy features of Petals Studio 1.1.
Formerly, there were several wizards to create service-units. And only service-units.
Several changes have been brought to the wizards, which can be found under *File > New > Petals*.
Several changes have been brought to the wizards, which can be found under *File > New > Petals*.
h2. BPEL
!Menu_New_Wiz.jpg!
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.
\\ !petals-studio-nnn-1.jpg!
The former Petals wizards (to create service-unit projects) have been merged into a single one.
!WizardSu_1.jpg|thumbnail! !WizardSu_2.jpg|thumbnail! !Wiz_se.jpg|thumbnail!
\\
The BPEL Designer has a new layout.
The BPEL Designer has a new layout.
!Wiz_su_1.jpg|thumbnail! !Wiz_su_2.jpg|thumbnail! !Wiz_su_3.jpg|thumbnail!
!petals-studio-nnn-3.jpg!
\\
The wizard for service assembly projects has been reviewed.
The creation of BPEL processes from a WSDL has been fixed.
!WizardSa.jpg|thumbnail!
!petals-studio-nnn-2.jpg!
\\
A new wizard, relying on the Petals Maven plug-in, has been added as a shortcut to create Petals components.
The direct creation of partner links has been fixed.
!WizardComponent.jpg|thumbnail!
!petals-studio-nnn-4.jpg!
h2. Jsr181
\\
A creation wizard was also added to ease the configuration of Petals View.
A creation wizard was also added to ease the configuration of Petals View.
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.
!Wiz_KPI_1.jpg|thumbnail! !Wiz_KPI_2.jpg|thumbnail! !Wiz_KPI_3.jpg|thumbnail!
!petals-studio-nnn-5.jpg|thumbnail! !petals-studio-nnn-6.jpg|thumbnail! !petals-studio-nnn-7.jpg|thumbnail!
\\
Eventually, this release comes with a new (but still experimental) concept in Petals tools: sketching.
Sketches are primarily intended for BPEL and SCA. They aim at going through an intermediary design step before the projection on Petals ESB.
\\
Eventually, this release comes with a new (but still experimental) concept in Petals tools: sketching.
Sketches are primarily intended for BPEL and SCA. They aim at going through an intermediary design step before the projection on Petals ESB.
h2. Other wizards
!Wiz_sketch.jpg|thumbnail!
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.
!petals-studio-nnn-8.jpg!
h2. Petals Views
A new view has been added in the studio.
The *Petals Projects* view aims at organizing the workspace by ordering Petals projects in categories.
!ProjectsExplorer.jpg! !Projects_View.jpg|thumbnail!
A new view has been added in the studio.
The *Petals Projects* view aims at organizing the workspace by ordering Petals projects in categories.
!ProjectsExplorer.jpg! !Projects_View.jpg|thumbnail!
\\
Another useful view is the *Petals Services* view.
It allows you to list Petals end-points, from different sources and locations.
By default, this view only lists the end-points located in the workspace, but it also possible to list end-points from zipped service assemblies.
It allows you to list Petals end-points, from different sources and locations.
By default, this view only lists the end-points located in the workspace, but it also possible to list end-points from zipped service assemblies.
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.
!PetalsServiceExplorer.jpg! !petals-studio-nnn-9.jpg!
\\
Populating this view is crucial to ease the creation of service consumers.
The user interface and the validation in the EIP wizard was improved.
!Wiz_Consume.jpg|thumbnail!
!petals-studio-nnn-10.jpg!
h2. SCA support
h2. JBI & Petals Editors
Service-Unit projects for SCA can directly be created.
This new version of the studio comes with editors for jbi.xml files.
The basis editor is an extension of the Eclipse XML editor for JBI descriptors.
The basis editor is an extension of the Eclipse XML editor for JBI descriptors.
!petals-studio-nnn-11.jpg!
!JbiEditorAutoCompletion.jpg|thumbnail!
\\
It is completed by specialized editors for Service-Units and Service Assemblies.
Three creation patterns are proposed: empty composite, simple Petals service and service orchestration.
!SU_editor.jpg|thumbnail! !SA_editor.jpg|thumbnail!
!petals-studio-nnn-12.jpg|thumbnail! !petals-studio-nnn-13.jpg|thumbnail! !petals-studio-nnn-14.jpg|thumbnail!
h2. Extended Validation
The validation of jbi.xml files has been improved drastically.
Just like for editors, there is basic solution, which relies on a XML-based validation in the XML editor....
!JbiEditorValidation.jpg|thumbnail!
\\
... and more advanced validations for service-units and service assemblies.
The JBI binding editor was replaced by an enhanced tab property section.
!JbiEditorSuValidation.jpg|thumbnail! !Validation_sa.jpg|thumbnail!
!petals-studio-nnn-15.jpg|thumbnail!
h2. Other features
h2. Import Wizards
JBI descriptors can be validated explictely.
Import wizards have been added under *File > Import > Petals*.
!petals-studio-nnn-16.jpg!
!Menu_Import_Wiz.jpg!
You can now import WSDL files with all their dependencies (XSDs and other WSDLs that are referenced by the first file).
And it is now possible to import zipped service assemblies in your workspace, and create a set of Petals projects.
!ImportWizardMenu.jpg|thumbnail! !ImportWizardWsdl.jpg|thumbnail! !ImportWizardSa.jpg|thumbnail!
h2. Export Wizards
Project export can now be achieved through several means.
These wizards can be found under *File > Export > Petals*.
!Menu_Export_Wiz.jpg!
You can now import WSDL files with all their dependencies (XSDs and other WSDLs that are referenced by the first file).
And it is now possible to import zipped service assemblies in your workspace, and create a set of Petals projects.
!ImportWizardMenu.jpg|thumbnail! !ImportWizardWsdl.jpg|thumbnail! !ImportWizardSa.jpg|thumbnail!
h2. Export Wizards
Project export can now be achieved through several means.
These wizards can be found under *File > Export > Petals*.
!Menu_Export_Wiz.jpg!
\\
There is a wizard to export Service-Unit projects using different export options.
Service Assembly projects have a shortcut to package them.
!Export_su.jpg|thumbnail!
!petals-studio-nnn-17.jpg!
A shortcut for this export is also available.
If you right-click a Service-Unit project and select *Petals > fast export*, a zipped service assembly is built at the root of the project.
!FastExport.jpg|thumbnail!
If you right-click a Service-Unit project and select *Petals > fast export*, a zipped service assembly is built at the root of the project.
!FastExport.jpg|thumbnail!
\\
Among these wizards, there is also one to export a Service Assembly project with the referenced Service-Units project.
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.
!Export_sa.jpg|thumbnail!
!petals-studio-nnn-18.jpg|thumbnail! !petals-studio-nnn-19.jpg|thumbnail! !petals-studio-nnn-20.jpg|thumbnail!
\\
Eventually, there is a bulk export, which can create several services from one service.
This export is mainly interesting for tests.
This export is mainly interesting for tests.
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).
!Export_bulk.jpg|thumbnail!
!petals-studio-nnn-21.jpg!
h2. BPEL and SCA sketching
Now, BPEL processes and SCA applications must first be designed independently from Petals.
It means that in your design, you do not have to be worried about any constraint or specific requirement from Petals.
Once this first step is done, your sketches are introspected and can be exported as a set of specialized projects for Petals.
Thus, from something which is completely standard, you can project it on Petals by generating the required artifacts.
!Sketch_1.jpg|thumbnail! !Sketch_2.jpg|thumbnail! !Sketch_3.jpg|thumbnail!
h2. Interact with Petals Servers from Eclipse
You can now define Petals servers in Eclipse.
This give you the ability to start Petals (in interactive mode or not) on various JDK, stop and shutdown it.
Project deployment is one of the next steps.
!Server_1.jpg|thumbnail! !Server_3.jpg|thumbnail! !Server_2.jpg|thumbnail!
h2. Updates regarding Petals components
The service-unit wizards have been updated against the last version of Petals components.
In particular, there are brand new WSDL definitions proposed as default for most of the components.
Among them, you can find: FTP, SFTP, FileTransfer, Mail, SQL, Validation, XSLT and REST.
\\
Notice also that the SOAP wizard was split to distinguish between the REST configuration and the SOAP configuration.
The wizard to import a service assembly was updated.
!Wiz_REST.jpg|thumbnail!
!petals-studio-nnn-22.jpg!
\\
Eventually, the SOAP wizard was updated. It can now determine the SOAP binding automatically and update the field accordingly.
!Wiz_Soap_binding.jpg|thumbnail!