FOTY0001 error xslt

Question

Hi,
I'm having problems processing BPEL instances. I have a BPEL process with transform activies (each of them with an xslt file). When I deploy the BPEL process for the first time, the instance finishes with no problems.
But then, I redeploy the instance and I get the following error:
Error del manejador de mensajes.
Se ha producido una excepción al intentar procesar el mensaje "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; la excepción es: No se ha podido ejecutar la expresión XPath.
Error al procesar la expresión xpath, la expresión es "ora:processXSLT('input_to_NotificarClientes.xsl',bpws:getVariableData('inputVariable'))", el motivo es FOTY0001: Error de tipo.
Verifique la consulta de xpath.
ORABPEL-05002
After this error, I create a new xsl (input_to_NotificarClientes2.xsl) and it works ok, even though this second xslt is identical to the other xsl.
I don't understand what is happening here. Anyone can help me? Thanks in advance,
Zaloa

Answer 1

Hi,
You gotta call the function in a right way. This error happens because the function is not callled with the right paramater. It's expecting the parameter to be passed in the form of a fully qualified path, which means we have to drill down to the level where the data comes in. The best way is to to open up the XSL file, which is supposedly the 1st arg of processXSLT() function and look at the source XSD structure. One is supposed to pass until that node as an input to this function, as below -
ora:processXSLT('TransformationOAToVantive.xsl',bpws:getVariableData('InvokeOA_OracleEBiz_OutputVariable','OutputParameters','/ns6:OutputParameters'),bpws:getVariableData('inputVariable','payload','/ns8:parameters'))
If you try to pass as below then it won't be able to determine the type that the function expects -
ora:processXSLT('TransformationOAToVantive.xsl',bpws:getVariableData('InvokeOA_OracleEBiz_OutputVariable'),bpws:getVariableData('inputVariable'))
It will definitely throw you an error. Of course there might be some sort of caching issues with JDeveloper, for which you need to delete and create this assign step once again.
Thanks.