[jboss-cvs] JBossAS SVN: r78565 - projects/demos/trunk/docs.

[jboss-cvs-commits at lists.jboss.org]

Author: alesj
Date: 2008-09-16 04:49:50 -0400 (Tue, 16 Sep 2008)
New Revision: 78565

Modified:
   projects/demos/trunk/docs/models.txt
Log:
2nd cycle.

Modified: projects/demos/trunk/docs/models.txt
===================================================================
--- projects/demos/trunk/docs/models.txt	2008-09-16 06:52:22 UTC (rev 78564)
+++ projects/demos/trunk/docs/models.txt	2008-09-16 08:49:50 UTC (rev 78565)
@@ -1,4 +1,4 @@
-JBoss Microcontainer - Component modules 
+JBoss Microcontainer - Component models 
 
 [Intro]
 
@@ -78,7 +78,7 @@
 
 <spring-beans.xml>
 
-As you can see, file's namespace is different from previous Microcontainer beans security-beans.xml file.
+As you can see, file's namespace is different from previous Microcontainer beans plain-beans.xml file.
 urn:jboss:spring-beans:2.0 namespace points to our version of Spring schema port,
 meaning you can describe your beans Spring style, but it's the Microcontainer that's gonna deploy then, not Spring's bean factory notion.
 
@@ -144,4 +144,16 @@
 
 Here we map SpringPojo name to springPojo alias.
 The beauty of having alias as true compoment model is that it doesn't matter when real bean is deployed.
-Meaning alias will wait in non-installed state until real bean triggers it.
\ No newline at end of file
+Meaning alias will wait in non-installed state until real bean triggers it.
+
+We're done!
+
+We've seen how we can deploy simple Microcontainer beans, legacy MBeans, Guice POJOs, Spring beans and aliases.
+And since all of this is controlled by Microcontainer, we saw how easy we can mix and match this different component models.
+Injecting POJOs into MBeans and vice versa. Looking up Guice beans and injecting them into Microcontainer beans, using Microcontainer beans to wire Guice beans.
+Deploying Spring custom xml - apart from changing namespace - with Microcontainer and then using this beans as if they were Microcontainer beans.
+
+I can easily say, with the level of abstraction we put in our component model design, sky is the limit on what we can handle. :-)
+An example of this is the upcoming OSGi services, but that's another story, another article.
+
+Stayed tuned for detailed Microcontainer IoC article.