L.S.,
If you route a message exchange into the Saxon XSL-T endpoint, it will
send the transformation result as the out message. If you look at
http://incubator.apache.org/servicemix/creating-a-protocol-bridge.html,
you can see an example: it receives an HTTP request, transforms the
message using XSL-T and forwards it to a JMS queue.
Gert
[EMAIL PROTECTED] wrote:
Thanks Gert
How Saxon component gets triggered,does it work like other self driven
components like Quartz ,if i put my po-parser.xsl file in root of my SU, how
should i route the output to other components like Groovy.Please suggest.
Thanks in advance
Gert Vanthienen wrote:
L.S.,
You can put your po-parser.xsl file in the root of your SU archive, next
to the xbean.xml file.
Gert
VishalKumarNalla wrote:
Hi,
Can anybody give me clues on how exactly Saxon Component works.I have
tried
the following, here is the configuration file:
<beans xmlns:sm="http://servicemix.apache.org/config/1.0";
xmlns:test="http://servicemix.apache.org/test/1.0/";
xmlns:saxon="http://servicemix.apache.org/saxon/1.0"";>
<saxon:xslt service="test:saxon-component" endpoint="endpoint"
resource="classpath:po-parser.xsl" />
</beans>
I have put the xsl file under conf directory.
Thanks in advance
Quoted from:
http://www.nabble.com/Help%3AHow-Saxon-Component-Works--tf4508410s12049.html#a12896241
