Looks like you're running into this bug: https://issues.apache.org/jira/browse/ODE-570
The code that's evaluating the xpath within the ODE engine should handle this for you but it doesn't due to the bug above. I'm not aware of a workaround within bpel that's not ugly. On Thu, Jun 30, 2011 at 2:13 PM, Christian Bruckhoff <[email protected]> wrote: > Hi. > > The following assignment sets a:currentRetries e.g. to "2.0" if it was "1" > before. a:currentRetries is of type xsd:integer. Why BPEL/Xpath sets it to a > xsd:double value then? > How can I fix this? > > Regards > Christian > > <bpel:assign validate="no" name="currentRetriesPlusPlus"> > <bpel:copy> > <bpel:from> > > <![CDATA[$processAlertRequest.processAlertRequestPart/tns:alert/a:currentRetries > + 1]]> > </bpel:from> > <bpel:to> > > <![CDATA[$processAlertRequest.processAlertRequestPart/tns:alert/a:currentRetries]]> > </bpel:to> > </bpel:copy> > </bpel:assign> > >
