Java Reference
In-Depth Information
Don't push the cool technologies (JSF, EJB, JPA etc)
everywhere and don't do or avoid doing something because in
general it is considered to be a good or bad practice. One has
to decide based on the capabilities of existing framework and
a rational consideration of the pros and cons. For example
even using JSP with JSTL tags to do database queries may be
the most suitable solution in some special case.
Don't reinvent the Wheel
Use common, proven frameworks like Apache Struts,
JavaServer Faces, and Eclipse RCP. Use proven patterns.
Back when we first started helping educate our clients in how
to use the then-emerging Java EE standards, we discovered
that developing a framework for user-interface development
significantly improved developer productivity over building
UI applications directly to the base servlet and JSP
specifications. As a result, many companies developed their
own UI frameworks that simplified the task of interface
development.
As open-source frameworks like Apache Struts began
development, the switchover to these new frameworks would
be automatic and quick. The benefits of having an
open-source community supporting the framework would be
readily apparent to developers, and that they would gain
universal
acceptance
very
rapidly
--
not
only
for
new
development, but in retro-fitted applications as well.
What has proven surprising is that this turned out otherwise.
We still see many companies maintaining or even developing
new
user-interface
frameworks
that
are
functionally
Search WWH ::




Custom Search