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.
Bug
Closed
Major
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.