A number of people have suggested basing the RI on the JBoss MC.
As I see it, the core services we need in WB:
* Defining scoped components, backed by EJBs if needed
* Defining bindings
* Defining (custom) scopes
* Managing lifecycle of components through contexts
* Integration with EL
* Resolution of components
* Support for interceptors
* Observer/observable
* Deployment of Web Beans jars
If we use the MC we get ootb:
* flexible deployment system
* Defining components
* DI (inc into constructors)
* Support for building custom XML deployment descriptors
* Support for applying AOP
which will get us going pretty quick
But
* it introduces quite a lot of dependencies which we don't directly
control (JBoss MC, JBoss XB etc.)
* it still seems to be under pretty heavy development (docs are very
incomplete)
* what happens if WB RI uses one version of MC and the AS uses
another?
WDYT?
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev