This content has been marked as final. Show 6 replies
Hi..1 person found this helpful
In your xpath use the option like /outputvariable/../../result/ and it will sort out the problem.
Unfortunately I have the exactly same error. BPEL engine replicates the elements in the bpel variable without any apparent reason.
After restarting the composite this problem disappear and return randomly in the future. I was not able to understand the conditions when the abnormal behavior returns.
Putting the 'index'  in xpath is indeed a workaround, but i ask if someone has solved this situation and understood the situation in depth.
Thanks in advance.
I too am facing same issue, can someone provide any solution.
In my case this happened when the modified XSD (added a further child element to a complex type) my Assign was expecting was not yet deployed to MDS.
I have this same issue, someone found the solution?
Hi I understand the workaround here (adding  to the to-spec expression) - but what about the extra empty nodes, when we move to the next step in our process will those empty nodes still exist - since our XSD sets that node to maxOcurrs="1" this would cause issues down stream if these empty nodes are carried forward - we are thinking of putting in a XSLT to remove them, but wanted to see if anyone has input on if they will be carried forward - since this is a random issue ware not able to reproduce it in our dev/test environment, it seems to only happen in our Production environment.