XSL transformation: source parts or variables are either simple type or complex type, thus cannot be used to create mapper file

some hint on this here


I was trying to use a variable
variable name="currentLine" type="ns1:Preactivation"

with ns1:Preactivation defined in a XSD. This is not accepted (don't ask me why,
SOA has reasons that the reason itself doesn't have).

If you change a WSDL and add an element of that type:
xs:element name="Preactivation" type="Preactivation"

and you declare the variable as of "element" type:

variable name="currentLine" element="ns1:Preactivation"

then the XSL mapping is happy to accept it.

WARNING: if you change the File Adapter that generated that WSDL, your element will be gone....

Adding a new Source to the BPEL XSL Transformation in SOA Suite doesn't reflect in the oracle-xsl-mapper mapSources

you must delete from XSL and recreate it from scratch.

:o(

ORAMED-03601

oracle.fabric.common.FabricInvocationException: oracle.tip.mediator.infra.exception.MediatorException: ORAMED-03601:[Invalid transformer configuration]Unable to create transformer. It could be because of transformation file or configuration issues


I am struggling with XSL transformations. JDeveloper doesn't seem to react very well to manual manipulations of the file. You come back from "source" to "design" and the design doesn't reflect the connections. And you get the runtime error.

Workaround: avoid manual hacks..... :o(