3 Replies Latest reply: Jan 23, 2013 2:31 PM by Andrew Higginbottom RSS

    Error with attribute of type <currency-val> on SOAP request (v. 10.3.0.77)

    968980
      OPA settings and environment settings
      OPA version
      10.3.0.77

      OPA Project properties
      Rule language: Dutch
      Region: Netherlands (Dutch)

      OS configuration
      Not specified.

      Test tools
      soapUI 3.6.1

      Test steps
      A rule base is deployed in the test environment. The rule base contains a number of attributes of the type currency-val.
      The rule base is called with a SOAP request using soapUI. In the SOAP request there a number of attributes of the type currency-val, such as displayed below.

      <attribute id="xxxxxxxxxx" type="currency" inferred="false">
           <currency-val>100.00</currency-val>
      </attribute>

      Observed result
      In the SOAP response an error is reported on the attribute: "Can not parse value for attribute". See the SOAP response below.

      <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:i18n="http://www.w3.org/2005/09/ws-i18n" xmlns:typ="http://oracle.com/determinations/server/10.3/rulebase/assess/types">
      <SOAP-ENV:Header>
      <i18n:international>
      <i18n:locale>en_US</i18n:locale>
      <i18n:tz>GMT+0100</i18n:tz>
      </i18n:international>
      </SOAP-ENV:Header>
      <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
      <faultcode>SOAP-ENV:Client</faultcode>
      <faultstring>Can not parse request. Reason: Can not parse value for attribute 'xxxxxxxxxx' in entity 'global[global]', expected the start of an attribute value element</faultstring>
      <detail>
      <typ:error-response>
      <typ:code>com.oracle.determinations.server.exceptions.DeterminationsServerParseException</typ:code>
      <typ:message>Can not parse request. Reason: Can not parse value for attribute 'xxxxxxxxxx' in entity 'global[global]', expected the start of an attribute value element</typ:message>
      </typ:error-response>
      </detail>
      </SOAP-ENV:Fault>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>

      Note
      The actual value is of no consequence to the error message. I tried the following numbers: '100.00', '100.0', '100', '100,00' and 100,0', all with the same result.