Discover how AppDynamics steps in to upgrade your performance game and prevent your enterprise from these top 10 Java performance problems, brought to you in partnership with AppDynamics.
I just reviewed my past projects and noticed that for about two
years I've almost completely managed to get rid of XML configuration and deployment
descriptors. It really works well, is efficient to develop, maintain,
and test. I especially appreciated working with:
- Wicket (Apache's Web Framework, from conceptual point of view similar to JSF)
- Google's Guice (I like especially the fluent configuration and only 22 pages of documentation)
- EJB 3 - No XML and just works. EJB 3.1 would be even better.
- [JPA] it rocks but comes with very small XML-configuration - so it should be out of scope here.
the integration between EJB 3 and Wicket and EJB 3 and Google's Guice
are superb (I will write some more about that soon). I like JSF as well,
however the amount of XML configuration is still huge. JSF was designed
from the tool perspective, so it isn't a problem with a good tool (like
NetBeans IDE or JDeveloper). ...already looking forward to JSF 2.0 :-).
The Java Zone is brought to you in partnership with AppDynamics. AppDynamics helps you gain the fundamentals behind application performance, and implement best practices so you can proactively analyze and act on performance problems as they arise, and more specifically with your Java applications. Start a Free Trial.