I'm just going through Spring xml schema and there are a couple of features that need
to be discussed if we really want to support them.
First here are some that I think are useful to be added to existing bean metadata
support:
- parent
(
http://www.springframework.org/docs/reference/beans.html#beans-child-bean...)
- abstract (same link as parent)
After you have these previous two, there is a 'merge' option on collections:
-
http://www.springframework.org/docs/reference/beans.html#beans-collection...
Which is probably trivial to implement.
There are two that fit in the ConfigureAction:
- autowire
(
http://www.springframework.org/docs/reference/beans.html#beans-factory-au...)
- dependency-check
(
http://www.springframework.org/docs/reference/beans.html#beans-factory-de...)
I already added support for optional 'autowire-candidate' aka
'contextual-injection-candidate'.
'scope' element will probably be handled by our kernel scoping impl - additional
API on top of deployers?
And two more which can probably be handled by our aspectized MC configuration:
- lookup-method
(
http://www.springframework.org/docs/reference/beans.html#beans-factory-lo...)
- replaced-method
(
http://www.springframework.org/docs/reference/beans.html#beans-factory-ar...)
Kabir?
How to integrate this with Joinpoint instantiation?
Some of them have a 'global' deployment default value.
What's the deal with all those lifecycle, aware, post-callback interfaces:
-
http://www.springframework.org/docs/reference/beans.html#beans-factory-na...
-
http://www.springframework.org/docs/reference/beans.html#beans-factory-ex...
We can probably wrap most of them into MC features.
How to get classes into classpath? Meaning, can we ship our own small artifact/jar with
just those interfaces?
So that the notion of not needing full blown Spring IoC is still there. ;-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049608#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...