[jira] Resolved: (ODE-177) Empty (i.e., no parts) message variables cause uninitialized variable fault

["Matthieu Riou (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ODE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthieu Riou resolved ODE-177.
-------------------------------

    Resolution: Fixed
      Assignee: Matthieu Riou

Should be fixed in the trunk. Note that in your process the part in the property alias should be just 'counterName' (unqualified).

> Empty (i.e., no parts) message variables cause uninitialized variable fault
> ---------------------------------------------------------------------------
>
>                 Key: ODE-177
>                 URL: https://issues.apache.org/jira/browse/ODE-177
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.1
>         Environment: r566310
>            Reporter: Paul R. Brown
>            Assignee: Matthieu Riou
>             Fix For: 1.1
>
>
> A message variable with no parts, i.e.:
>   <wsdl:message name="emptyResponse" />
>   <wsdl:portType name="port">
>     <wsdl:operation name="op">
>       <wsdl:input message="t:requestMessage" />
>       <wsdl:output message="t:emptyResponse" />
>     </wsdl:operation>
>   </wsdl:portType>
>   <b:variable name="empty" messageType="t:emptyResponse" />
> And then trying to reply:
>   <b:reply partnerLink="plink" operation="op" variable="empty" />
> Causes:
>   DEBUG - GeronimoLog.debug(66) | Fault response message: {http://docs.oasis-open.org/wsbpel/2.0/process/executable}uninitializedVariable
> Should this be allowed to slide by since it can't really be initialized?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.