(no commit message)

[utils] / src / site / xdoc / index.xml

diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml
index ac209fc82615f280ce99beef6ff435293395585e..7b5dfe51e78e64064e8c449fab16113aeeb2e020 100644 (file)
--- a/src/site/xdoc/index.xml
+++ b/src/site/xdoc/index.xml
@@ -31,8 +31,9 @@
       <p> Some parts in the utilities library may seem familiar to users of other popular frameworks
         such as <a href="http://www.springframework.org">Spring</a> and <a
           href="http://code.google.com/p/google-guice/">Guice</a>. This is not always a coincidence.
-        It is my view that Spring is just another IOC framework and that there can be many IOC
-        frameworks. Also, the support that one actually needs to develop applications and in
+        It is my view that there many good IOC
+        frameworks but that it is not a good idea to tie into any one of them 
+        specifically. Also, the support that one actually needs to develop applications and in
         particular enterprise applications efficiently only requires a few basic support utilities
         and typically not a big framework. </p>
       <p>Apart from this, there are many other interesting developments going on: </p>
@@ -49,7 +50,7 @@
           23rd 2010 and Glassfish V3 is already partly using it. </li>
       </ul>
       <p> In particular, I believe that Java EE 6 with new powerful concepts such as singleton
-        beans, lifecycle management, Contexts and Dependency Injection, and Enterprise OSGI will
+        beans, lifecycle management, Contexts and Dependency Injection, used in combination with Enterprise OSGI will
         provide the most powerful way to develop applications in the future. In this. I am making
         only an exception for web frameworks to which I think JSF is not a good solution. I would
         use <a href="http://wicket.apache.org">Wicket</a> anyday if it's up to me. </p>