Quoting Rickard Öberg <[email protected]>: > On 2010-10-26 18.19, Paul Merlin wrote: > > Quoting Rickard Öberg<[email protected]>: > >> Are there any other features or libraries that you see are > >> missing, to help production usage or development? > > > > I'm writing as I think, just a few thoughts: > > - an OptimisticLock handling library for retries, maybe as a Concern ; > > How about improving the existing UnitOfWorkConcern to do retries on > concurrency exception? Is that what you would want?
Sure, would be nice to have a UnitOfWorkConcern and an OptimisticLockRetryConcern so we can keep control on what is done where and when. > > - 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. > > - 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 ? > > I'm wondering about the beanshell console exposed through restlet. Is it > > exposed in an interactive web page, as a http service usable from a > > command line client, both ? > > I use it as an interactive web page, but you can post scripts to it from > commandline, of course. 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. Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
