Current camel-xslt endpoint will not try to load the xslt file until
the endpoint is processing the first exchange.
I think we need to let the camel-xslt endpoint load the xslt file when
it is created to let the user know what is wrong about the endpoint
configuration.
It could save lots of trouble shooting time if we know some thing is
wrong when the route is started.
Any thoughts ?
On Mon Nov 21 15:45:33 2011, Claus Ibsen wrote:
Hi
We have a failure on trunk in 1 unit test in camel-saxon
Failed tests:
testInvalidStylesheet(org.apache.camel.component.xslt.SaxonInvalidXsltFileTest):
Should have thrown an exception due XSL compilation error
https://builds.apache.org/job/Camel.trunk.fulltest/org.apache.camel$camel-saxon/559/testReport/
It's due some recent improvement to load the stylesheet from a header.
If anyone got cycles to look into this today or tomorrow that would be great.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
