Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of ronny.aerts@intris.be
 designates 213.199.154.77 as permitted sender)
From: Ronny Aerts <ronny.aerts@intris.be>
To: "users@camel.apache.org" <users@camel.apache.org>
Subject: RE: can I set a message header or exchange property inside an xslt?
Thread-Topic: can I set a message header or exchange property inside an xslt?
Thread-Index: Ac8g6kgR1sKjQ6dfQ5SktzGlGYE2+gAH31+AAB5wcqAAA+T28A==
Date: Tue, 4 Feb 2014 10:35:20 +0000
Message-ID: 
 <6a24062ca8dd48a59899e8253035613d@DB3PR01MB300.eurprd01.prod.exchangelabs.com>
References: 
 <b322760a9ca246ff86fde910d6a69a6b@DB3PR01MB300.eurprd01.prod.exchangelabs.com>
 <CAGB5yNnq8xoEqq4xNP0bmVuuMq4KG7UHuFpWD7XkqZ6Me-2nvA@mail.gmail.com>
 <c25f93b0f8ed42568d95dedc882c635c@DB3PR01MB300.eurprd01.prod.exchangelabs.com>
In-Reply-To: 
 <c25f93b0f8ed42568d95dedc882c635c@DB3PR01MB300.eurprd01.prod.exchangelabs.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hello,

I figured it out and yes it is possible to set message headers and exchange=
 properties in camel xslt.

I created a separate java file with content (see the methods that are marke=
d static):
package com.intris.camel.component.xslt;

public class xsltmsg {

public static void setHeader (org.apache.camel.Message message, String name=
, String value) {
message.setHeader(name, value);
}

public static void setProperty (org.apache.camel.Exchange exchange, String =
name, String value) {
exchange.setProperty(name, value);
}
}

I created a xslt file:
<?xml version=3D'1.0'?>
<xsl:stylesheet
version=3D"1.0"
xmlns:xsl=3D"http://www.w3.org/1999/XSL/Transform"
xmlns:xsltmsg=3D"java:com.intris.camel.component.xslt.xsltmsg"
exclude-result-prefixes=3D"xsltmsg" >

<xsl:param name=3D"in"/>
<xsl:param name=3D"out"/>
<xsl:param name=3D"exchange"/>

<xsl:template match=3D"/">
<!-- <test>ronny aerts</test> -->
<!-- setting message headers on the "in" does not seem to work -->
<xsl:value-of select=3D"xsltmsg:setHeader($in, 'bbb-1', 'ronny.aerts.1')"/>
<xsl:value-of select=3D"xsltmsg:setHeader($out, 'bbb-2', 'ronny.aerts.2')"/=
>
<xsl:value-of select=3D"xsltmsg:setProperty($exchange, 'aaa', 'ronny en ger=
d')"/>
<!-- <test2>after</test2> -->
</xsl:template>
</xsl:stylesheet>

My route looks like:
<route id=3D"test-xslt">
<from uri=3D"timer://xslt-timer?repeatCount=3D1" />
<pollEnrich uri=3D"file://example-data?fileName=3Dtest.xml&amp;noop=3Dtrue"=
 timeout=3D"2500" />
<convertBodyTo type=3D"java.lang.String" />
<to uri=3D"log://before?showExchangePattern=3Dfalse&amp;showHeaders=3Dtrue&=
amp;showProperties=3Dtrue&amp;multiline=3Dtrue" />
<to uri=3D"xslt://classpath:test.xsl?saxon=3Dfalse" />
<to uri=3D"log://after?showExchangePattern=3Dfalse&amp;showHeaders=3Dtrue&a=
mp;showProperties=3Dtrue&amp;multiline=3Dtrue" />
<log message=3D"${routeId} end of route" />
</route>

There is still one problem with the above:
net.sf.saxon.trans.XPathException: Cannot find a matching 3-argument functi=
on named {java:com.intris.camel.component.xslt.xsltmsg}setHeader(). Note th=
at direct calls to Java methods are not available under Saxon-HE

It seems that camel uses the saxon home edition and with the home edition i=
t not possible to call java from xslt.

I added a dependency to my project pom and now it works fine.
<dependency>
<groupId>net.sf.saxon</groupId>
<artifactId>saxon</artifactId>
<version>[8.7,)</version>
</dependency>
A part of the output is:
, Properties: {aaa=3Dronny en gerd, ...
, Headers: {bbb-2=3Dronny.aerts.2, ...

The setting of a header on the in does not seem to have an effect.

I would be very handy if there would such a xslt wrapper class for settings=
 message headers, similar to one I created.
--
Kind regards,
Ronny Aerts - Intris nv - Wapenstilstandlaan 47, 2600 Berchem, Belgium
R&D Integration Architect
Prince II certified
Tel: +32-3-326.50.75


-----Original Message-----
From: Ronny Aerts [mailto:ronny.aerts@intris.be]
Sent: dinsdag 4 februari 2014 9:41
To: users@camel.apache.org
Subject: RE: can I set a message header or exchange property inside an xslt=
?

Hello Claus,

Thank you for the feedback.

I searched in the xslt test files and found the org.apache.camel.component.=
xslt.XsltTransformingExceptionTest.java in combination with org.apache.came=
l.component.xslt.MyEcho.java and org/apache/camel/component/xslt/transformC=
allEcho.xsl.

The xsl file declares xmlns:echo=3D"xalan://org.apache.camel.component.xslt=
.MyEcho" and later on the <xsl:value-of select=3D"echo:echoString(string(na=
me))"></xsl:value-of> statement is called to activate the java code.
As far as I known, this approach is only possible with static methods (in t=
he java code) and therefore it does not seem possible with camel out of the=
 box. I will try to work something.

--
Kind regards,
Ronny Aerts - Intris nv - Wapenstilstandlaan 47, 2600 Berchem, Belgium R&D =
Integration Architect Prince II certified
Tel: +32-3-326.50.75


-----Original Message-----
From: Claus Ibsen [mailto:claus.ibsen@gmail.com]
Sent: maandag 3 februari 2014 19:00
To: users@camel.apache.org
Subject: Re: can I set a message header or exchange property inside an xslt=
?

Hi

You likely can.
Though I can remember how that is possible.

Try look at the unit tests
https://github.com/apache/camel/tree/master/camel-core/src/test/java/org/ap=
ache/camel/component/xslt

And we love contributions. People is welcome to add details on the xslt doc=
s how to do this http://camel.apache.org/contributing

On Mon, Feb 3, 2014 at 3:16 PM, Ronny Aerts <ronny.aerts@intris.be> wrote:
> Hello camel community,
>
> I'm working on a project where it would be very handy to me if I can set =
a message header or exchange property inside the execution of an xslt produ=
cer. Is this possible?
>
> I know that the "exchange" and "in" are passed as parameter to the transf=
ormation.
>
> --
> Kind regards,
> Ronny Aerts<mailto:ronny.aerts@intris.be> - Intris nv -
> Wapenstilstandlaan 47, 2600 Berchem, Belgium R&D Integration Architect
> Prince II certified
> Tel: +32-3-326.50.75
>
>
> Intris nv
> Wapenstilstandlaan 47
> B-2600 Berchem
>         Tel.  +32 3 326 50 75
> Fax  +32 3 326 42 23
> www.intris.be<http://www.intris.be/>
>
> DISCLAIMER
> This is an e-mail from Intris. The information contained in this communic=
ation is intended solely for use by the individual or entity to whom it is =
addressed.
> Use of this communication by others is prohibited. If the e-mail message =
was sent to you by mistake, please notify support@intris.be<mailto:support@=
intris.be>, destroy it without reading, using, copying or disclosing its co=
ntents to any other person.
> We accept no liability for damage related to data and/or documents which =
are communicated by electronic mail.


--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen Make your Camel app=
lications look hawt, try: http://hawt.io Intris nv Wapenstilstandlaan 47
B-2600 Berchem
        Tel.  +32 3 326 50 75
Fax  +32 3 326 42 23
www.intris.be<http://www.intris.be/>

DISCLAIMER
This is an e-mail from Intris. The information contained in this communicat=
ion is intended solely for use by the individual or entity to whom it is ad=
dressed.
Use of this communication by others is prohibited. If the e-mail message wa=
s sent to you by mistake, please notify support@intris.be<mailto:support@in=
tris.be>, destroy it without reading, using, copying or disclosing its cont=
ents to any other person.
We accept no liability for damage related to data and/or documents which ar=
e communicated by electronic mail.
Intris nv
Wapenstilstandlaan 47
B-2600 Berchem
        Tel.  +32 3 326 50 75
Fax  +32 3 326 42 23
www.intris.be<http://www.intris.be/>

DISCLAIMER
This is an e-mail from Intris. The information contained in this communicat=
ion is intended solely for use by the individual or entity to whom it is ad=
dressed.
Use of this communication by others is prohibited. If the e-mail message wa=
s sent to you by mistake, please notify support@intris.be<mailto:support@in=
tris.be>, destroy it without reading, using, copying or disclosing its cont=
ents to any other person.
We accept no liability for damage related to data and/or documents which ar=
e communicated by electronic mail.