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 100733 - Mapper for Assign activity in CatchAll is not showing its scope variable
Summary: Mapper for Assign activity in CatchAll is not showing its scope variable
Status: CLOSED INVALID
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Mapper (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Nikita Krjukov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-12 08:37 UTC by Murali Pottlapelli
Modified: 2008-04-11 13:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Murali Pottlapelli 2007-04-12 08:37:11 UTC
InvalidInvokeSvcOperationOut1 is not shown in the mapper for Assign 4 if it is
moved to scope-1

<?xml version="1.0" encoding="UTF-8"?>
<process
    name="InvalidInvokeSvc"
   
targetNamespace="http://enterprise.netbeans.org/bpel/InvalidInvoke/InvalidInvokeSvc"
    xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
   
xmlns:tns="http://enterprise.netbeans.org/bpel/InvalidInvoke/InvalidInvokeSvc"
xmlns:ns1="http://j2ee.netbeans.org/wsdl/InvalidInvokeSvc"
xmlns:ns2="http://j2ee.netbeans.org/wsdl/InvalidInvoke"
xmlns:ns3="http://j2ee.netbeans.org/wsdl/InvalidOneWayInvoke">
    <import namespace="http://j2ee.netbeans.org/wsdl/InvalidInvokeSvc"
location="InvalidInvokeSvc.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
    <import namespace="http://j2ee.netbeans.org/wsdl/InvalidInvoke"
location="InvalidInvoke.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
    <import namespace="http://j2ee.netbeans.org/wsdl/InvalidOneWayInvoke"
location="InvalidOneWayInvoke.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
    <partnerLinks>
        <partnerLink name="PartnerLink3"
partnerLinkType="ns3:InvalidOneWayInvoke1"
partnerRole="InvalidOneWayInvokePortTypeRole"/>
        <partnerLink name="PartnerLink2" partnerLinkType="ns2:InvalidInvoke1"
partnerRole="InvalidInvokePortTypeRole"/>
        <partnerLink name="PartnerLink1" partnerLinkType="ns1:InvalidInvokeSvc1"
myRole="InvalidInvokeSvcPortTypeRole"/>
    </partnerLinks>
    <variables>
        <variable name="InvalidOneWayInvokeOperationIn"
messageType="ns3:InvalidOneWayInvokeOperationRequest"/>
        <variable name="InvalidInvokeOperationOut"
messageType="ns2:InvalidInvokeOperationReply"/>
        <variable name="InvalidInvokeOperationIn"
messageType="ns2:InvalidInvokeOperationRequest"/>
        <variable name="InvalidInvokeSvcOperationOut"
messageType="ns1:InvalidInvokeSvcOperationReply"/>
        <variable name="InvalidInvokeSvcOperationIn"
messageType="ns1:InvalidInvokeSvcOperationRequest"/>
        <variable name="InvalidInvokeSvcOperationOut1"
messageType="ns1:InvalidInvokeSvcOperationReply"/>

    </variables>
    <sequence>
        <receive name="Receive1" createInstance="yes" partnerLink="PartnerLink1"
operation="InvalidInvokeSvcOperation" portType="ns1:InvalidInvokeSvcPortType"
variable="InvalidInvokeSvcOperationIn"/>
        <assign name="Assign1">
            <copy>
                    <from variable="InvalidInvokeSvcOperationIn" part="part1"/>
                        <to variable="InvalidInvokeOperationIn" part="part1"/>
                </copy>
        </assign>
        <assign name="Assign2">
            <copy>
                    <from variable="InvalidInvokeSvcOperationIn" part="part1"/>
                        <to variable="InvalidOneWayInvokeOperationIn" part="part1"/>
                </copy>
        </assign>
        <if name="If1">
            <sequence name="Sequence2">
                <invoke name="Invoke1" partnerLink="PartnerLink2"
operation="InvalidInvokeOperation" portType="ns2:InvalidInvokePortType"
inputVariable="InvalidInvokeOperationIn"
outputVariable="InvalidInvokeOperationOut"/>
            </sequence>
            <elseif>
                <sequence name="Sequence3">
                    <invoke name="Invoke2" partnerLink="PartnerLink3"
operation="InvalidOneWayInvokeOperation"
portType="ns3:InvalidOneWayInvokePortType"
inputVariable="InvalidOneWayInvokeOperationIn"/>
                </sequence>
            </elseif>
            <elseif>
                <sequence name="Sequence1">
                    <scope name="Scope1">
                        <variables>
                        </variables>
                        <faultHandlers>
                            <catchAll>
                                <sequence name="Sequence4">
                                    <assign name="Assign4"/>
                                    <reply name="Reply2"
partnerLink="PartnerLink1" operation="InvalidInvokeSvcOperation"
portType="ns1:InvalidInvokeSvcPortType" variable="InvalidInvokeSvcOperationOut1"/>
                                </sequence>
                            </catchAll>
                        </faultHandlers>
                        <invoke name="Invoke3"/>
                    </scope>
                </sequence>
            </elseif>
            <else>
                <scope name="Scope2">
                    <invoke name="Invoke4"/>
                </scope>
            </else>
        </if>
        <assign name="Assign3">
            <copy>
                <from>
                    <literal>Not expected output</literal>
                </from>
                <to part="part1" variable="InvalidInvokeSvcOperationOut"/>
            </copy>
        </assign>
        <reply name="Reply1" partnerLink="PartnerLink1"
operation="InvalidInvokeSvcOperation" portType="ns1:InvalidInvokeSvcPortType"
variable="InvalidInvokeSvcOperationOut"/>
    </sequence>
</process>
Comment 1 Sergey Lunegov 2007-10-25 17:00:12 UTC
Will address in Sierra.
Comment 2 Andrei Chistiakov 2008-01-17 11:09:20 UTC
Changed target milestone from Sierra to 6.1 in order to display correct info on
NB 6.1 dashboard
Comment 3 Nikita Krjukov 2008-02-11 12:09:41 UTC
I can't reproduce the issue because of the BPEL editor doesn't work with variables 
of not resolved data type. Moreover, by the date of the issue I see that it 
relates to the old BPEL mapper. 
I haven't seen any problem with variables' visibility in nested scopes in the new BPEL mapper.