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 78083

Summary: NB 5.5 BPEL Editor presently does not support the BPEL 2.0 virtual assign constructs
Product: soa Reporter: bugbridge <bugbridge>
Component: BPELAssignee: issues@soa <issues>
Status: VERIFIED INVALID    
Severity: blocker    
Priority: P4    
Version: 5.x   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:

Description bugbridge 2006-06-16 14:30:09 UTC
Original status: 1-Dispatched; Suggested Status: NEW

Description:
Editor presently does not support the BPEL 2.0 virtual assign constructs

e.g. 

        <receive name="receive"
                 partnerLink="virtualAssignIncoming1"
                 operation="virtualAssignOperation1"
                 portType="wsdlNS:virtualAssignPortType1"
                 createInstance="yes">
                 <fromPart part="simpleStringPart" toVariable="var1"/>***<- not
supp.
        </receive>
   
      <invoke name="invoke_to_subbp" 
              partnerLink="PartnerLink_for_invoke_out_to_subbp"
              operation="virtualAssignOperation1" 
	      portType="wsdlNS:virtualAssignPortType1">
              <toPart part="simpleStringPart" fromVariable="var1"/>***<- not supp.
              <fromPart part="simpleStringPart" toVariable="var2"/>***<- not supp.
      </invoke>

        <reply name="reply" 
               partnerLink="virtualAssignIncoming1"
               operation="virtualAssignOperation1"
               portType="wsdlNS:virtualAssignPortType1">
               <toPart part="simpleStringPart" fromVariable="var2"/>***<- not
supp.      
        </reply>
Comment 1 Michael Frisino 2006-07-16 23:25:38 UTC
Yes, this is not supported by runtime. It is out of scope for the 5.5 release.

The code listed below should work in the editor though, and should not result in
any exceptions. However, the Assign element sould be badged with a "Not
supported by runtime" error message. 

If that is happening, then this is corrrect behavior for the 5.5 release.
Comment 2 Mikhail Kondratyev 2006-07-24 13:11:47 UTC
Verified in build from 060723