>> Project 1: an Enterprise Job Scheduler
>> =====================================
>
>> Project 2: a Workflow Engine / Process Automator
>> =====================================
>
>This is something we need as well.
>
>For #1: Taking the best parts from Avalon and Turbine and merging them into
>a Commons would be good.
>
I have not looked far into the Schedulers in Avalon or Turbine - but I think
that they currently fall quite short of the features features I listed. I
also don't beleive they are 'organized' in a way that easily fators into
what I want to build (not to say they wouldn't offer a wealth of code to
start out with).
I'm looking to build something that can act much the same way as a JMS
provider, or an EJB container, but also can just be used in a simpler form
within stand-alone applications.
Flux (http://www.simscomputing.com) is similar to what I had in mind.
Perhaps I better get to drawing up my plans.
>For #2: It certainly could start in the Commons.
Maybe I'm still unsure of the purpose of "the commons" but, do you really
want something as huge as a process automator in there? -- We're talking
about something on the scale of a full-blown EJB container here. It's not
something somebody would want packaged along with a handy 'Collections'
library.
I really am open to whatever - I personally just think these projects (and
especially #2) are too big, and to likely to be used on their own, to want
them to be part of a framework.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
