Petals Studio

The service DnD erases some imports from the Artifacts WSDL

Details

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

    When completing a BPEL using the DnD feature, the Artifacts WSDL erases the previous imports.
    Or at least, it erases the main one.

  • Environment:
    Windows XP.

Activity

Hide
Vincent Zurczak added a comment - Fri, 17 Sep 2010 - 12:12:23 +0200

Commit # 1845
Port types can now be resolved locally to a partner role (fix for a BPEL loading weakness)

Show
Vincent Zurczak added a comment - Fri, 17 Sep 2010 - 12:12:23 +0200 Commit # 1845 Port types can now be resolved locally to a partner role (fix for a BPEL loading weakness)
Hide
Vincent Zurczak added a comment - Fri, 17 Sep 2010 - 10:49:03 +0200

More information on this bug:

  • It only occurs with BPEL processes that were generated from a WSDL.
  • The partner role defines the name space of the port type inside the partner link type definition. And not in the root mark-up.

I guess the designer removes the import because it does not seem to be used.

<ns4:partnerLinkType name="TuxDroidPortTypePLT">
	<ns4:role xmlns:ns17="http://tuxdroid.ebmwebsourcing.com/" name="TuxDroidPortTypeRole" portType="ns17:TuxDroidPortType" />
</ns4:partnerLinkType>
<w:import location="tuxDroid.wsdl" namespace="http://tuxdroid.ebmwebsourcing.com/" />
Show
Vincent Zurczak added a comment - Fri, 17 Sep 2010 - 10:49:03 +0200 More information on this bug:
  • It only occurs with BPEL processes that were generated from a WSDL.
  • The partner role defines the name space of the port type inside the partner link type definition. And not in the root mark-up.
I guess the designer removes the import because it does not seem to be used.
<ns4:partnerLinkType name="TuxDroidPortTypePLT">
	<ns4:role xmlns:ns17="http://tuxdroid.ebmwebsourcing.com/" name="TuxDroidPortTypeRole" portType="ns17:TuxDroidPortType" />
</ns4:partnerLinkType>
<w:import location="tuxDroid.wsdl" namespace="http://tuxdroid.ebmwebsourcing.com/" />
Hide
Vincent Zurczak added a comment - Thu, 16 Sep 2010 - 21:14:59 +0200

It seems to only reject the import of the WSDL that describes the process.

Show
Vincent Zurczak added a comment - Thu, 16 Sep 2010 - 21:14:59 +0200 It seems to only reject the import of the WSDL that describes the process.

People

Dates

  • Created:
    Tue, 14 Sep 2010 - 19:35:12 +0200
    Updated:
    Fri, 17 Sep 2010 - 12:12:28 +0200
    Resolved:
    Fri, 17 Sep 2010 - 12:12:23 +0200