ServiceMix 7.0.0.M2 saxon for XSLT

[BURN, James]

Hi

I'm testing/developing with ServiceMix 7.0 to use some of the latest Camel 2.16.3 features.

We need to do XSLT transformations using ServiceMix.

I install camel-saxon feature, but when I deploy a route calling an XSLT which works in other versions of ServiceMix, it would appear that ServiceMix is trying to run with a xalan XSLT 1.0 processor.

So I get errors like:

Caused by: javax.xml.transform.TransformerException: Could not find function: encode-for-uri
at org.apache.xalan.processor.XSLTAttributeDef.processEXPR(XSLTAttributeDef.java:769)[:]
at org.apache.xalan.processor.XSLTAttributeDef.processValue(XSLTAttributeDef.java:1405)[:]
at org.apache.xalan.processor.XSLTAttributeDef.setAttrValue(XSLTAttributeDef.java:1601)[:]

I think this is because encode-for-uri is only available in XSLT 2.0 and xalan is trying to process my .xsl using XSLT 1.0

How can I force the Saxon processor to be used (rather than xalan)?

Thanks

James



Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.

[BURN, James]

Hi

Another test and this isn't an issue with ServiceMix 7.0.0.M1 !

Is Saxon somehow being missed from the classpath with ServiceMix 7.0.0.M2 ?

James

-----Original Message-----
From: BURN, James [mailto:***@oup.com]
Sent: 28 September 2016 15:31
To: ***@servicemix.apache.org
Subject: ServiceMix 7.0.0.M2 saxon for XSLT

Hi

I'm testing/developing with ServiceMix 7.0 to use some of the latest Camel 2.16.3 features.

We need to do XSLT transformations using ServiceMix.

I install camel-saxon feature, but when I deploy a route calling an XSLT which works in other versions of ServiceMix, it would appear that ServiceMix is trying to run with a xalan XSLT 1.0 processor.

So I get errors like:

Caused by: javax.xml.transform.TransformerException: Could not find function: encode-for-uri
at org.apache.xalan.processor.XSLTAttributeDef.processEXPR(XSLTAttributeDef.java:769)[:]
at org.apache.xalan.processor.XSLTAttributeDef.processValue(XSLTAttributeDef.java:1405)[:]
at org.apache.xalan.processor.XSLTAttributeDef.setAttrValue(XSLTAttributeDef.java:1601)[:]

I think this is because encode-for-uri is only available in XSLT 2.0 and xalan is trying to process my .xsl using XSLT 1.0

How can I force the Saxon processor to be used (rather than xalan)?

Thanks

James



Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.
Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.

[BURN, James]

Hmm, sorry, scratch that out. I was muddled - I get same errors in M1 version.

So. Any thoughts on what I'd need to do to get Saxon >9.5 to work?

-----Original Message-----
From: BURN, James [mailto:***@oup.com]
Sent: 28 September 2016 16:02
To: ***@servicemix.apache.org
Subject: RE: ServiceMix 7.0.0.M2 saxon for XSLT

Hi

Another test and this isn't an issue with ServiceMix 7.0.0.M1 !

Is Saxon somehow being missed from the classpath with ServiceMix 7.0.0.M2 ?

James

-----Original Message-----
From: BURN, James [mailto:***@oup.com]
Sent: 28 September 2016 15:31
To: ***@servicemix.apache.org
Subject: ServiceMix 7.0.0.M2 saxon for XSLT

Hi

I'm testing/developing with ServiceMix 7.0 to use some of the latest Camel 2.16.3 features.

We need to do XSLT transformations using ServiceMix.

I install camel-saxon feature, but when I deploy a route calling an XSLT which works in other versions of ServiceMix, it would appear that ServiceMix is trying to run with a xalan XSLT 1.0 processor.

So I get errors like:

Caused by: javax.xml.transform.TransformerException: Could not find function: encode-for-uri
at org.apache.xalan.processor.XSLTAttributeDef.processEXPR(XSLTAttributeDef.java:769)[:]
at org.apache.xalan.processor.XSLTAttributeDef.processValue(XSLTAttributeDef.java:1405)[:]
at org.apache.xalan.processor.XSLTAttributeDef.setAttrValue(XSLTAttributeDef.java:1601)[:]

I think this is because encode-for-uri is only available in XSLT 2.0 and xalan is trying to process my .xsl using XSLT 1.0

How can I force the Saxon processor to be used (rather than xalan)?

Thanks

James



Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.
Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.
Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.