git://wamblee.org
/
utils
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
bd19731
)
(no commit message)
author
Erik Brakkee
<erik@brakkee.org>
Tue, 6 Jul 2010 08:56:23 +0000
(08:56 +0000)
committer
Erik Brakkee
<erik@brakkee.org>
Tue, 6 Jul 2010 08:56:23 +0000
(08:56 +0000)
src/site/xdoc/index.xml
patch
|
blob
|
history
diff --git
a/src/site/xdoc/index.xml
b/src/site/xdoc/index.xml
index 7b5dfe51e78e64064e8c449fab16113aeeb2e020..fe31114573bb0b90899e5f603ae1751f51f712da 100644
(file)
--- 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
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>
+ 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. </p>
<p>Apart from this, there are many other interesting developments going on: </p>
<ul>
<li><em>Java EE 6 dependency injection:</em> Java EE 6 provides a powerful dependency
<p>Apart from this, there are many other interesting developments going on: </p>
<ul>
<li><em>Java EE 6 dependency injection:</em> 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
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>
+ use <a href="http://wicket.apache.org">Wicket</a> anyday if it
were
up to me. </p>
</section>
</body>
</section>
</body>