At 02:15 22/3/01 -0800, James House wrote:
>I'm interested in starting an open source project or two, and would like
>them to fall under an Apache style license.
>
>I'd also be happy for them to fall under the Jakarta umbrella, and am
>curious what I'd need to do to have them do so
>(otherwise I'll slap them up on sourceforge or somewhere).
see end of jakarta.apache.org/site/management.html
Basically the conditions in simplified form are;
1. must be done with the "Apache spirit"
2. must have some guarentee that it will be successful
For (2) I was originally led to believe that the projects must be ready
established but recent actions indicates that this is not so. It seems that
projects with enough support internal to Apache may be created but I assume
they are not allowed to be advertised as Apache projects until they mature.
>Project 1: an Enterprise Job Scheduler
>=====================================
>Description:
>
>A job scheduling system that can handle the scheduling of thousands
>(hopefully millions) of jobs, and cause them to be processed via a variety
>of J2SE and J2EE mechanisms.
Hey !!!
A few months a company got me to build one of these. I retain some of the
copyright on product and for the remainder I plan to reimplement it. A lot
of the parts are already in Avalon CVS. (Namely the priority queue
interface + binary heap implementation + cron time trigger/scheduler +
delayed/periodic scheduler).
The strategy I used for writing jobs was based on ant. Jobs were defined like
<job name="foo">
<task1 .../>
<task2 .../>
<task3 .../>
<task4 .../>
</job>
Thus I am waiting for ant2 design to finalize before re-hacking at it.
>Basic Desired Features:
>
>* Scalable & Robust (duh :)
>* Able to handle hundreds of thousands or even millions of jobs
>* Job persistence (survives crashes, reboots, etc.)
>* Light-weight enough to be impeded within a simple stand-alone java app
>* Able to be contained within a J2EE app-server environment
>* Able to be used remotely from any Java environment (scheduler runs
>stand-alone)
>* Jobs are scheduled to run once at a given time, or recurring with
>Cron-like expressions
>* When the time arrives for a job to fire, the scheduler should be able to:
> - call any Java object implementing a specific 'listener' interface
My goals were all of the above. I also had the goal that jobs had to be
executed with a particular set of permissions. ie you may execute job foo
with Principle Fred (under jdk1.2) or under Subject Barney (jdk1.3+jaas).
>I found a similar product this morning called "Flux" - it has most of the
>features I'm looking for, but it is commercial. They do however publish a
>public interface for job scheduling that they suggest other projects should
>implement (they're proposing a standard API).
Flux is apparently really nice and there is another commercial job
scheduler aaswell but I forget it's name at the moment. There is also
low-end schedulers in a number of other opensource projects. Turbine has a
databased scheduler and Avalon has a primitive scheduler. Neither are
sufficient though as they lack significant required features.
>Does anyone else know of a standard / api for doing job scheduling in Java?
ant ! ;)
>Project 2: a Workflow Engine / Process Automator
>=====================================
>Description:
>
>An engine for doing Workflow and Process Automation within or without a J2EE
>application server.
>
>Desired Features:
>
>* I haven't put much thought into this yet, but I feel this is a real need
>in the open source world unless someone can tell me of an existing one?
>
>In case you're not sure what I'm referring to, here's a product of BEA's
>that is similar to what I'm envisioning:
>http://www.bea.com/products/weblogic/integrator/datasheet.shtml
I don't follow this but Berin from Avalon / Cocoon was talking about this a
lot (I had no idea what he was nattering on about though). So you may want
to ask him ;)
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
