On 13/01/2013 12:24, Simone Tripodi wrote:
Salut Eric!
Well, we are talking here about configurating the injection.
It can be injecting the expiration time for a memory cache entries, about
choosing Visa vs MasterCard...
So I still like to think about injection configuration.
Does it make sense?
sure that it does! we created indeed a separated module for that
purpose, see the Onami Configuration module
<http://onami.incubator.apache.org/configuration/>
What Onami Configuration misses is the configuration
watchdog/reload/update injections, that I would discuss in a separate
thread - every suggestion is more than welcome! :)
+1 to discuss watchdog/reloading/updating injections. I really need this.
The approach we followed, while creating Onami extensions, is
splitting functionalities in small reusable modules, rather than build
a big monolithe, in order that our users can include just the
feature(s) they are interested and not a complete framework.
Another concept we kept in mind, is being strict as much as possible
to Guice SPIs, in oder to make extensions collaborate even if they are
not aware each other, I mean you can still discover&bind services via
Onami SPI and inject configuration properties via Onami Configuration.
+1 for modularity. Each one should be able to pick any subset he likes.
But all those modules have to collaborate to provide to a user a
first-class coherent platform. That's why Onami has been created and
that's great.
My only 2-cent is that the release process would be much easier if all
the trunk was released as one at the same time. Yes, modules would be
upgraded to a newer version even if no change has been committed, but
that's a non-issue to me.
Thanks a lot!
Thx to You for all you work, vision, great ideas and didactic explanations!
Eric
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
