We are using a substring-after in 10.1.3.4 which will not port to 10.1.3.5.
This is the input:
<Expression>//Credit/LedgerID[.="278070000H,2008,76022917AA,50I0000000,21380,61000000,0000000000,0000000000,0000000000,0000000000"]</Expression>
This 10.1.3.4 code works fine to grab the first argument of 278070000H. It gets everything after =" then grabs everything before the first comma. We keep doing this nested to get all 10 fields.
{code}<xsl:value-of select='substring-before(substring-after(.,"=&quot;"),",")'/>{code}
In 10.1.3.5, the substring-after won't find the string if the double quote is in there. If I remove the &quot; and leave just the = then the output is "278070000H the qoute is not stripped out.
I realize there are other ways to fix this but we are in user test and don't want to change base code.
Is this a change/bug between the versions or do we need a setup or setting change?
We've noticed other bugs in 10.1.3.5. When a bpel transformation gui is returned to and opened, the source side variable defaults to the first choice in the list instead of the actual one when created. Also the gui for the substring-after changes a "." in the input string to the full path which is a problem when inside a for-each because it causes it to find the first item in the for-each instead of the current item. We have to change these back to "." in the source.