From 8d321e0d26d7d1d8c461fc9ca8bd7105e86e6ac2 Mon Sep 17 00:00:00 2001
From: Erik Brakkee
Date: Tue, 6 Jul 2010 08:56:23 +0000
Subject: [PATCH]
---
src/site/xdoc/index.xml | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml
index 7b5dfe51..fe311145 100644
--- a/src/site/xdoc/index.xml
+++ b/src/site/xdoc/index.xml
@@ -35,7 +35,9 @@
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.
+ and typically not a big framework. Therefore, you will find a couple of small
+ utilities that may be familiar in the functionality they offer to what is found
+ in other frameworks.
Apart from this, there are many other interesting developments going on:
- Java EE 6 dependency injection: Java EE 6 provides a powerful dependency
@@ -53,7 +55,7 @@
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 Wicket anyday if it's up to me.
+ use Wicket anyday if it were up to me.