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
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>