Hi,


I am using a xsl... but in compilation time i got this error:

what can be? thaks ??


BPEL Compilation errors were encountered prior to deployment.
-------------------------
Error during compilation
-------------------------
error: [CompilationErrors] Compilation completed with 1 error(s):
null:244: error: [CantFindXslt] Could not find the XSLT stylesheet referenced with URI urn:/Transformacion/ComboTipoIden.xsl, make sure it has been properly provided to the compiler.

-------------------------
org.apache.ode.bpel.compiler.api.CompilationException: error: [CompilationErrors] Compilation completed with 1 error(s):
null:244: error: [CantFindXslt] Could not find the XSLT stylesheet referenced with URI urn:/Transformacion/ComboTipoIden.xsl, make sure it has been properly provided to the compiler.

at org.apache.ode.bpel.compiler.BpelCompiler.compile(BpelCompiler.java:726)
at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:260)
at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:330)
at com.intalio.bpms.designer.pxecompiler.builders.BpelCompileJob.compileBpel(BpelCompileJob.java:226)
at com.intalio.bpms.designer.pxecompiler.builders.BpelCompileJob.run(BpelCompileJob.java:150)
at com.intalio.bpms.designer.pxecompiler.builders.PxeBuilder.compileBPELResource(PxeBuilder.java:104)
at com.intalio.bpms.designer.deployment.deploy.DeploymentJob.validateBpelFiles(DeploymentJob.java:186)
at com.intalio.bpms.designer.deployment.deploy.DeploymentJob.run(DeploymentJob.java:126)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

-------------------------
null:244: error: [CantFindXslt] Could not find the XSLT stylesheet referenced with URI urn:/Transformacion/ComboTipoIden.xsl, make sure it has been properly provided to the compiler.

This is quite straight forward: the BPEL compiler cannot find the xsl file. Please enter the relative path of the XSL stylesheet.

Thanks,

Antoine

I just hit this problem today - which is very odd, since I was already using the xsl in two other places in my bpm file. It turns out that the order in which you draw lines in the mapper is very critical. You must connect the box with the path of your xsl file first and then connect the XML that you want to transform. If you do it in the other order, the BPEL created is reversed and you can get this error.

Hi Richard,

Could you please attach the process for investigation?

Thanks
Chandra

Thanks for checking in on this...

No need for me to upload a project as you can use one of the samples that you guys already have (doXSLTransform3) since I believe this happens on all maps. And arguably, it is not a bug - but it certainly is confusing.

Here's a way to reproduce the problem

1. Open doXSLTransform3 (or, in theory, any map that uses the doXSLTransform function)
2. Select the "Create Display and selection" task
3. Choose the mapper tab - you should now see taskOutput/output/candidatesTable and "candidateToDisplayCandidate.xsl" as the two nodes that are connected to the bpel:doXSLTransform()
4. If you mouse over the connections, you will notice that the connection from the xsl file is #1 and the connection from candidatesTable is #2.
5. Switch the order by deleting the links and reconnecting in the order (1) candidatesTable, (2) xsl file
6. Save the bpm file - there will be no errors reported
7. Deploy the project - you will get an error along the lines of:
error: [CompilationErrors] Compilation completed with 1 error(s):
null:162: error: [CantFindXslt] Could not find the XSLT stylesheet referenced with URI net.sf.saxon.expr.PathExpression@8292276d, make sure it has been properly provided to the compiler.

------

If the order of the connection to the doXSLTransform function matters, then it should be caught in the Save - as the error message on deploy is harder to resolve.

Hope this helps,
RB