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.
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">
<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>
<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>
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.
Thanks for your answer!
I tried that and it worked. So that seems to be the solution.
One question that still bothers me is that when I export a test case (created in OPM) which contains attributes of the type currency to a file (xds), the xml of that test case shows <currency-val> for those attributes, not <number-val>. Is that then a bug in OPA?
I would not call this a bug, although it does cause confusion when trying to translate an xds file into a request for the Assess operation. They are different formats, for different purposes, so there are some differences.
The "number-val" element requirement is in the documentation for the Assess request, on the following page(10.3):
"[...] The number-val element is used for all numeric values including currency."