1 Reply Latest reply on Feb 1, 2013 11:09 PM by 450652

    Message variable initialization


      We had this ridiculous situation a while ago where out service instances create their variables with multiple nodes.

      For example if we have xsd looking like this:
      <element name="Response">
      <element name="Result">
      <restriction base="string">
      <enumeration value="OK"/>
      <enumeration value="ERR"/>
      <element name="Comment" minOccurs="0" type="string"/>

      In BPEL we have message variable which part is this "Response" element. Everything is fine till the moment we start getting initial variable looking like this:
      <part name="payload" >

      Of course we have no reason for this, no logs, no info and so on. Any idea anyone?
      Everything is normal concerning the BPEL, no errors are raised till the moment we need to populate the variable. The process is working correctly but we cannot return result to the caller.

      WL version:
      SOA version:
      BPEL version: 2.0

      Best regards.
        • 1. Re: Message variable initialization
          could you please send your test case to our support team? this doesn't look right. bpel engine would initialize the variable based on the xpath usage in to-spec expressions. you can try turning of variable initialization for that particular component using bpel.config.initializeVariables to false. and go with literal xml variable initiation. [http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html#SA00038]

          here is the sample for that property
          in composite.xml, find the component, under that component add this property, and re-deploy with your literal variable init.
          <property name="bpel.config.initializeVariables">false</property>