[jira] Commented: (ODE-219) Using a variable with 2 message parts, refering to header and body, fails for a inoke activity.

["Mike Vallender (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ODE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552800 ] 

Mike Vallender commented on ODE-219:
------------------------------------

Attached a patch which resolves this problem - following the fix for the related ODE211 bug. 

As with previous bug - not test the patch with other cases like ODE extension "urn:ode.apache.org/axis2-il/headers".....  so please review.


> Using a variable with 2 message parts, refering to header and body, fails for a inoke activity. 
> ------------------------------------------------------------------------------------------------
>
>                 Key: ODE-219
>                 URL: https://issues.apache.org/jira/browse/ODE-219
>             Project: ODE
>          Issue Type: Bug
>          Components: Axis2 Integration
>    Affects Versions: 1.1
>         Environment: tomcat4.17/ JDK1.5
>            Reporter: Mike Vallender
>             Fix For: 1.2
>
>         Attachments: SoapMessageConverter.java.patch
>
>
> This is similar to JIRA ODE-211 only for an invoke activity. 
> With the message items 
>     <wsdl:message name="getList1In">
>         <wsdl:part name="header" element="bibus:biBusHeader"/>
>         <wsdl:part name="request" element="raas:getList1Request"/>
>     </wsdl:message>
>     <wsdl:message name="getList1Out">
>         <wsdl:part name="header" element="bibus:biBusHeader"/>
>         <wsdl:part name="response" element="raas:getList1Response"/>
>     </wsdl:message>
> the operation 
>         <wsdl:operation name="getList1">
>             <wsdl:input message="y:getList1In" name="getList1In" />
>             <wsdl:output message="y:getList1Out" name="getList1Out" />
>         </wsdl:operation>
> the binding 
>         <wsdl:operation name="getList1">
>             <soap:operation soapAction="http://developer.cognos.com/schemas/rds/2"/>
>             <wsdl:input>
>                 <soap:header message="y:getList1In" part="header" use="literal"/>
>                 <soap:body use="literal" parts="request"/>
>             </wsdl:input>
>             <wsdl:output>
>                 <soap:header message="y:getList1Out" part="header" use="literal"/>
>                 <soap:body use="literal" parts="response"/>
>             </wsdl:output>
>         </wsdl:operation>
> the variable 
>     <variable name="raasResponse" messageType="raas:getList1Out"/>
> and the invoke 
>       <invoke name="callRaas" 
>       partnerLink="PromptNewsItemReportPLink" 
>       operation="getList1" 
>       inputVariable="raasRequest" 
>       outputVariable="raasResponse"/>
> I get the following error - from this assign
>       <assign name="getResponseValue">
>           <copy>
>               <from>$raasResponse.header/CAM</from>
>               <to variable="result" part="ack"/>
>           </copy>
>       </assign>
> java.lang.IllegalArgumentException: null parent
>         at org.apache.ode.utils.DOMUtils.findChildByName(DOMUtils.java:740)
>         at org.apache.ode.utils.DOMUtils.findChildByName(DOMUtils.java:735)
>         at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.getPartData(BpelRuntimeContextImpl.java:1213)
>         at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.fetchVariableData(BpelRuntimeContextImpl.java:421)
>         at org.apache.ode.bpel.runtime.ExprEvaluationContextImpl.readVariable(ExprEvaluationContextImpl.java:85)
>         at org.apache.ode.bpel.elang.xpath10.runtime.JaxenContexts.getVariableValue(JaxenContexts.java:170)
>         at org.jaxen.ContextSupport.getVariableValue(ContextSupport.java:224)
> It appears that the message part raasResponse.header is not created. 

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