Re: Unit test failure on trunk in camel-saxon

Great! now the referee on the Wiki [1] is also up-to-date as well. [1] https://cwiki.apache.org/confluence/display/CAMEL/Building (@ the line "You can also find some helpful notes on usage here." ) Babak -- View this message in context: http://camel.465427.n5.nabble.com/Unit-test-

Re: Unit test failure on trunk in camel-saxon

el_java_templates.xml > [3] > > https://svn.apache.org/repos/asf/camel/trunk/etc/eclipse/camel_xml_templates.xml > > Babak > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-saxon-tp5009713p5013883.html >

Re: Unit test failure on trunk in camel-saxon

es.xml [3] https://svn.apache.org/repos/asf/camel/trunk/etc/eclipse/camel_xml_templates.xml Babak -- View this message in context: http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-saxon-tp5009713p5013883.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: Unit test failure on trunk in camel-saxon

a/browse/CAMEL-4700> https://issues.apache.org/**jira/browse/CAMEL-4700> http://issues.apache.org/jira/**browse/CAMEL-4700> https://issues.apache.org/jira/browse/CAMEL-4700> Babak -- View this message in context: http://camel.465427.n5.nabble.** com/Unit-test-failure-on

Re: Unit test failure on trunk in camel-saxon

ould be default as the old behavior of loading the >>>>>> resource on startup. >>>>>> Wonder what a good name for such an option would be? >>>>>> - lazyLoadResource >>>>>> - loadResourceOnStartup >>>>>> ?? >>>>>> >>&g

Re: Unit test failure on trunk in camel-saxon

00<https://issues.apache.org/**jira/browse/CAMEL-4700> https://issues.apache.org/jira/browse/CAMEL-4700> Babak -- View this message in context: http://camel.465427.n5.nabble. com/Unit-test-failure-on-trunk-in-camel-saxon-**** tp5009713p5012820.html<http://**camel.465427.n5.nab

Re: Unit test failure on trunk in camel-saxon

gt;>>> >>>> Fail fast is IMHO especially needed to allow people to know something >>>> is wrong. We have seen many issues with loading resources in classpath >>>> on various servers of all sorts, and the likes of Java WebStart, >>>> JBoss, OSGi etc. &

Re: Unit test failure on trunk in camel-saxon

l.465427.n5.nabble.** com/Unit-test-failure-on-**trunk-in-camel-saxon-**tp5009713p5012820.html<http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-saxon-tp5009713p5012820.html> Sent from the Camel Development mailing list archive at Nabble.com. -- Hadrian Zbarcea Prin

Re: Unit test failure on trunk in camel-saxon

there is a issue compiling/parsing the stylesheet you get this >> error up front, which can be very important to know. >> >> >> >> >> [1] >> https://builds.apache.org/job/**Camel.trunk.fulltest/564/<https://builds.apache.org/job/Camel.trunk.fulltest/564

Re: Unit test failure on trunk in camel-saxon

know. [1] https://builds.apache.org/job/Camel.trunk.fulltest/564/ [2] https://issues.apache.org/jira/browse/CAMEL-4700 Babak -- View this message in context: http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-saxon-tp5009713p5012820.html Sent from the Camel Development

Re: Unit test failure on trunk in camel-saxon

gt; > Babak > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-saxon-tp5009713p5012820.html > Sent from the Camel Development mailing list archive at Nabble.com. > -- Claus Ibsen - F

Re: Unit test failure on trunk in camel-saxon

] https://builds.apache.org/job/Camel.trunk.fulltest/564/ [2] https://issues.apache.org/jira/browse/CAMEL-4700 Babak -- View this message in context: http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-saxon-tp5009713p5012820.html Sent from the Camel Development mailing list

Re: Unit test failure on trunk in camel-saxon

On Mon, Nov 21, 2011 at 3:23 PM, Willem Jiang wrote: > 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 a

Re: Unit test failure on trunk in camel-saxon

So that by [1] I simply mimicked the same changes done on unit-tests by [2] [1] https://issues.apache.org/jira/browse/CAMEL-4700 [2] https://issues.apache.org/jira/browse/CAMEL-4689 Babak -- View this message in context: http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel

Re: Unit test failure on trunk in camel-saxon

1202819 Babak -- View this message in context: http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-saxon-tp5009713p5010674.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: Unit test failure on trunk in camel-saxon

Hi, https://issues.apache.org/jira/browse/CAMEL-4700 Babak -- View this message in context: http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-saxon-tp5009713p5010536.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: Unit test failure on trunk in camel-saxon

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 trou

Unit test failure on trunk in camel-saxon

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/55