Petals Studio

BPEL graphical designer does not handle WSDL properly

Details

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

    I have a lot of problems with the graphical editor of the Studio, it can't do anything without having any error in the error console.

    For instance :

    • I generate a new BPEL sketch project
    • I put my WSDL with its XSD in this very project
    • I delete the default partner, all variables, all imports in the BPEL source code (to start from a blank project)
    • I create a new partner...and when I want to affect him a type, when I click on the "Browse" button I got an error in the error console
    • The partner link manager pops up...but when I select my WSDL and click on the "Add WSDL" button, nothing. It is not imported and I got errors in the error console
    Show
    I have a lot of problems with the graphical editor of the Studio, it can't do anything without having any error in the error console. For instance :
    • I generate a new BPEL sketch project
    • I put my WSDL with its XSD in this very project
    • I delete the default partner, all variables, all imports in the BPEL source code (to start from a blank project)
    • I create a new partner...and when I want to affect him a type, when I click on the "Browse" button I got an error in the error console
    • The partner link manager pops up...but when I select my WSDL and click on the "Add WSDL" button, nothing. It is not imported and I got errors in the error console
  • Environment:
    Petals Studio 1.1

Attachments

  1. File
    FAIS011-2.wnk
    (8.24 MB)
    Charles Casadei
    Thu, 5 Aug 2010 - 14:05:46 +0200
  2. Zip Archive
    FAIS011.zip
    (6 kB)
    Charles Casadei
    Thu, 5 Aug 2010 - 14:05:46 +0200
  1. image001.jpg
    (166 kB)

Activity

Ascending order - Click to sort in descending order
Charles Casadei made changes - Thu, 5 Aug 2010 - 14:04:03 +0200
Field Original Value New Value
Link This issue blocks SPVEOLIAE-33 [ SPVEOLIAE-33 ]
Charles Casadei made changes - Thu, 5 Aug 2010 - 14:05:46 +0200
Attachment FAIS011.zip [ 10152 ]
Attachment image001.jpg [ 10153 ]
Attachment FAIS011-2.wnk [ 10154 ]
Charles Casadei made changes - Thu, 5 Aug 2010 - 14:24:04 +0200
Priority Minor [ 4 ]
Charles Casadei made changes - Fri, 6 Aug 2010 - 10:43:35 +0200
Priority Minor [ 4 ] Major [ 3 ]
Vincent Zurczak made changes - Tue, 10 Aug 2010 - 12:13:26 +0200
Status New [ 10000 ] Open [ 10002 ]
Vincent Zurczak made changes - Tue, 10 Aug 2010 - 12:13:36 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Vincent Zurczak added a comment - Tue, 10 Aug 2010 - 18:37:55 +0200

Commit # 1571
The use case was the following:
1. Copy a WSDL (with its dependencies) in a BPEL project (in the "jbi" directory).
2. Create a new partner link.
3. In its properties, click "Browse...".
4. Click "Add WSDL".
5. Select the copied WSDL and click OK.

We would have expected to see the WSDL imported.
Whereas this action resulted in an error in the log. Several ones in fact.

+ Invalid Thread access (UI)
+ Issues with platform URIs
+ Issues with the computation of relative URIs

The following actions were undertaken:
=> Fixed the invalid thread access.
=> Replaced platform URLs by absolute file URLs.
=> Updated the way relative URIs are computed.

The use case now works correctly, with:
+ WSDL files from the same directory (Eclipse resource).
+ WSDL files from other projects (Eclipse resource).
+ WSDL files taken from the disk (File resource).
+ WSDL files identified by an URL (URL resource).

The creation of partner links (with a partner link type and a partner role) has been tested for each kind of import.
Once saved, the BPEL process was completely valid.

Show
Vincent Zurczak added a comment - Tue, 10 Aug 2010 - 18:37:55 +0200 Commit # 1571 The use case was the following: 1. Copy a WSDL (with its dependencies) in a BPEL project (in the "jbi" directory). 2. Create a new partner link. 3. In its properties, click "Browse...". 4. Click "Add WSDL". 5. Select the copied WSDL and click OK. We would have expected to see the WSDL imported. Whereas this action resulted in an error in the log. Several ones in fact. + Invalid Thread access (UI) + Issues with platform URIs + Issues with the computation of relative URIs The following actions were undertaken: => Fixed the invalid thread access. => Replaced platform URLs by absolute file URLs. => Updated the way relative URIs are computed. The use case now works correctly, with: + WSDL files from the same directory (Eclipse resource). + WSDL files from other projects (Eclipse resource). + WSDL files taken from the disk (File resource). + WSDL files identified by an URL (URL resource). The creation of partner links (with a partner link type and a partner role) has been tested for each kind of import. Once saved, the BPEL process was completely valid.
Vincent Zurczak made changes - Tue, 10 Aug 2010 - 18:37:55 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Vincent Zurczak made changes - Tue, 10 Aug 2010 - 18:38:01 +0200
Status Resolved [ 10004 ] Closed [ 10005 ]
Fix Version/s 1.1.1 [ 10078 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
4d 22h 10m
1
Vincent Zurczak
Tue, 10 Aug 2010 - 12:13:26 +0200
Open Open In Progress In Progress
10s
1
Vincent Zurczak
Tue, 10 Aug 2010 - 12:13:36 +0200
In Progress In Progress Resolved Resolved
6h 24m
1
Vincent Zurczak
Tue, 10 Aug 2010 - 18:37:55 +0200
Resolved Resolved Closed Closed
6s
1
Vincent Zurczak
Tue, 10 Aug 2010 - 18:38:01 +0200

People

Dates

  • Created:
    Thu, 5 Aug 2010 - 14:02:53 +0200
    Updated:
    Tue, 10 Aug 2010 - 18:38:01 +0200
    Resolved:
    Tue, 10 Aug 2010 - 18:37:55 +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.