Petals Studio

The "Generate BPEL skeleton from WSDL" option does not seem to work

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.0, 1.1.0
  • Fix Version/s: 1.1.1
  • Component/s: BPEL Tools
  • Security Level: Public
  • Description:
    Hide

    This function does not work on PetalsStudio 1.0.

    1) the XSD imported by the WSDL are not copied in the BPEL project (the WSDL is), so the generated WSDL is not valid.
    2) by default, the generated partner (mainPartner) has no role (the other role are properly created)
    3) When we try to use the "Create concrete project" after having copied the XSD by hand, the wizard crashes and shows an error popup "Conversion Error, the conversion process encountered errors. Reason: The cause of the error was not reported."

    Show
    This function does not work on PetalsStudio 1.0. 1) the XSD imported by the WSDL are not copied in the BPEL project (the WSDL is), so the generated WSDL is not valid. 2) by default, the generated partner (mainPartner) has no role (the other role are properly created) 3) When we try to use the "Create concrete project" after having copied the XSD by hand, the wizard crashes and shows an error popup "Conversion Error, the conversion process encountered errors. Reason: The cause of the error was not reported."
  • Environment:
    PetalsStudio 1.x

Attachments

  1. Zip Archive
    FAIS007.zip
    (3 kB)
    Charles Casadei
    Thu, 5 Aug 2010 - 10:20:07 +0200

Issue Links

Depends
 

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 19:39:59 +0200

The generation issues were workarounded.
EasyBPEL should fix the underlying issues anyway.

Show
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 19:39:59 +0200 The generation issues were workarounded. EasyBPEL should fix the underlying issues anyway.
Hide
Permalink
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 19:33:15 +0200

Commit # 1841
The abstract BPEL name space must not be part of the generated BPEL. Otherwise, the BPEL designer considers it abstract.
The wizard workarounds this by erasing this name space and using the concrete one instead.

Show
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 19:33:15 +0200 Commit # 1841 The abstract BPEL name space must not be part of the generated BPEL. Otherwise, the BPEL designer considers it abstract. The wizard workarounds this by erasing this name space and using the concrete one instead.
Hide
Permalink
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 18:40:54 +0200

Despite the previous commit, this bug is not yet solved.
Indeed, when we try to add a child activity to the generated process, it does not pass the validation.
The reported error is that the onMessage does not accept the added child.

Roughly, it seems to indicate that EasyBPEL generates a BPEL process that it cannot execute.
An investigation is in progress about it.

Show
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 18:40:54 +0200 Despite the previous commit, this bug is not yet solved. Indeed, when we try to add a child activity to the generated process, it does not pass the validation. The reported error is that the onMessage does not accept the added child. Roughly, it seems to indicate that EasyBPEL generates a BPEL process that it cannot execute. An investigation is in progress about it.
Hide
Permalink
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 18:34:16 +0200

Commit # 1840
The wrong myRole is overwritten in the generated BPEL.

Show
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 18:34:16 +0200 Commit # 1840 The wrong myRole is overwritten in the generated BPEL.
Hide
Permalink
Vincent Zurczak added a comment - Thu, 5 Aug 2010 - 10:52:01 +0200

1) was fixed in the commit # 1738.
The WSDL is now imported and not written from the in-memory process.

2) and 3) come from errors in EasyBPEL.
When the partner role is correctly set, the export (3) works correctly.

Show
Vincent Zurczak added a comment - Thu, 5 Aug 2010 - 10:52:01 +0200 1) was fixed in the commit # 1738. The WSDL is now imported and not written from the in-memory process. 2) and 3) come from errors in EasyBPEL. When the partner role is correctly set, the export (3) works correctly.

People

Dates

  • Created:
    Thu, 5 Aug 2010 - 10:19:32 +0200
    Updated:
    Tue, 14 Sep 2010 - 19:39:59 +0200
    Resolved:
    Tue, 14 Sep 2010 - 19:33:15 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.