On Mon, 8 Nov 2004 20:17:13 +0100, "Vincent Massol" <[EMAIL PROTECTED]> wrote: > > I'd prefer we do not do this in jelly script but rather in java code as we > also need to support this for the ServletRunner (browser integration) and > it's cleaner not to do it in a scripting language... (same reason as Maven > is moving from jelly to java) :-)
I'm fine with moving the plugins to Java, but only if we move everything at once (and then the Jelly code on the plugin is just a wrapper to the Java code, as it happens on hibernate). I mean, I think the partiall implementation of Java code has 2 disadvantages: - makes it harder to implement. From instance, I have no idea how I would do it on Java and wouldn't have enough time to figure it out - makes the plugin difficult to maintain, as you need to analyze more code until you realize if the feature is implemented on java or jelly. So, if it dependend on me, I would opt for implement it as Jelly and then refactor it later, when we un-jellyfy the whole plugin (in fact, that's what I would propose for CACTUS-90 too). -- Felipe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
