Re: [Springframework-developer] Scheduler update #2

[Ivan R. <iv...@we...>]

jürgen höller [werk3AT] wrote:

Jürgen,

I admire your ability to write long and interesting emails. Thank you
for informing us about the interesting work that you're doing :)


> - A CommandTaskDefinition (implements Runnable) takes a class name,
 > bean property values, and an execute method (plus optional
 > arguments). On run, it would simply instantiate the class, populate
 > the bean properties, and invoke the execute method.

   This sounds appealing but we effectively already have it with the
   combination of bean definition and SpringBeanTask definition.

   Personally, I don't mind having to do it in two steps. It also
   gives you the flexibility to reference the bean you are scheduling,
   and to schedule beans more than once if required.


 > - An EjbTaskDefinition (implements Runnable) takes a JNDI name and
 > method name plus arguments. Other such convenience classes can be
 > added, of course.

   And many other come to mind: native exec, HTTP, BeanShell, etc. We
   could group these in a separate package because they would apply
   to all scheduler implementations through the power of abstraction.

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]