On 2010-10-26 20.19, Paul Merlin wrote:
Sure, would be nice to have a UnitOfWorkConcern and an
OptimisticLockRetryConcern so we can keep control on what is done where and
when.
Good point, they are actually orthogonal, so that would be easy.
Ordering is crucial though :-)
- a type safe task scheduler to enqueue batch / background jobs ;
As a wrapper of an existing library like Flux? Or a completely new thing?
I forgot Flux, thanks for remiding it to me. However I think something like Flux
but Apache licenced or another business compatible licence would be better for
adoption. Plus it seems Flux needs it's own database where a Qi4j task scheduler
could use an ES and thus simplify deployment and exploitation.
Anyway, I was thinking at something really smaller than Flux.
Fair enough.
- a unit test support that allows to run the very same set of tests on
different assemblies ;
Yeah, the unit test baseclasses could definitely be updated.
Maybe we could start to collect "use cases" wanted for theses, wdyt ?
That would be a good start, yes.
Awesome ! :)
Writing a small shell in say, sh/curl, ruby or python, on top of this would be
very quick and friendly. That's definetely something I could contribute once
Console is available.
Ok, good to hear!
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
