On Tue, Nov 22, 2011 at 9:04 AM, bvahdat <babak.vah...@swissonline.ch> wrote: > Hi > > looking at the build of this morning [1] the test failure issue is now > fixed, however like Willem I think the pre-existing fail-fast behaviour > should be brought back as it used to be there. This however would require > another JIRA-Ticket than [2] having the corresponding description / goal.
+1 However I think we could consider adding a new option to ResourceEndpoint to support to control if the resource should be loaded on startup or lazy loaded upon first request. The former has fail fast, and the latter would defer loading the resource once its demanded, but with the penalty of compiling/parsing the template overhead. Then the option could 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 ?? The mina component have a laztCreateSession option, so the lazy name could be a good name http://camel.apache.org/mina 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. Also if 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/ > [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 archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
