On Thu, 10 May 2001, Immanuel, Gidado-Yisa wrote:
> > > I suppose it could be implemented entirely separate to
> > Struts, however, it
> > > would make a nice addition.
> > >
> >
> > It seems to me that a generic "background job scheduling"
> > class library
> > would be the way to do this, with a Struts-based administration front
> > end. The back end part of this might also be appropriate to
> > consider for
> > the Jakarta Commons project
> <http://jakarta.apache.org/commons> so that it
> could be used (and enhanced by users of ;-) other environments as well.
>
> It seems like the best place to put this would be in
> the servlet container. Anything like this planned for
> Servlet 2.4+ ?
>
I would not expect so, because it doesn't really have anything to do (or
only to do) with the servlet API.
What I believe makes sense is a generic job scheduling class library that
exposes its configuration and management capabilities through standard
Java interfaces. You could then write a user interface for this library
as a web app (using your favorite framework :-), as a JINI service, behind
a Swing GUI, or any other way(s) you would like.
Now, what would be really interesting, is if someone wanted to submit a
Java Specification Request (JSR) to create a *standard* API for job
scheduling systems. Then you could plug in any back end you wanted --
just like you can use JAXP APIs with any conformant parser, or JDBC APIs
with any conformant driver.
> - Gidado
>
Craig
