This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 178587

Summary: Regression: BPEL Mapper is generating a wrong code in the BPEL Editor when I assign partnerRole from PartnerLink to another PartnerLink
Product: soa Reporter: senthilprabhu <senthilprabhu>
Component: BPEL MapperAssignee: Vitaly Bychkov <lativ>
Status: CLOSED FIXED    
Severity: normal CC: alexpetrov
Priority: P1    
Version: 6.x   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:
Attachments: Screenshot of BPEL Mapper assignment

Description senthilprabhu 2009-12-14 06:11:28 UTC 
Regression: BPEL Mapper is generating a wrong code in the BPEL Editor when I assign partnerRole from a PartnerLink to another PartnerLink

In the attached picture, we assign the partnerRole of PartnerLink "TwoWay3" to "DynamicPL2Way" Partner Link.

Expected Output:
================
<assign name="AssignPL_2Way3">
                            <copy>
                                <from partnerLink="TwoWay3" endpointReference="partnerRole"/>
                                <to partnerLink="DynamicPL2Way"/>
                            </copy>
                        </assign>

Actual Output:
==============
<assign name="AssignPL_2Way3">
                            <copy>
                                <from>ns0:doXslTransform('urn:stylesheets:wrap2serviceref.xsl')</from>
                                <to partnerLink="DynamicPL2Way"/>
                            </copy>
                        </assign>
Comment 1 senthilprabhu 2009-12-14 06:13:02 UTC 
Created attachment 92525 [details]
Screenshot of BPEL Mapper assignment
Comment 3 senthilprabhu 2009-12-17 04:06:04 UTC 
On assigning the partnerRole of one PL to another PL, correct code is generated

              <copy>
                  <from partnerLink="TwoWay1" endpointReference="partnerRole"/>
                  <to partnerLink="DynamicPL2Way"/>
              </copy>

This issue is verified to work correctly in GFESB build 20091216-0720.
This issue can be closed.