Welcome!

SOA & WOA Authors: Dana Gardner, Kira Makagon, Elizabeth White, Mike Hicks, Carmen Gonzalez

Related Topics: Websphere, Java

Websphere: Article

12 Best Practices for J2EE Developers Named

12 Best Practices for J2EE Developers Named

Kyle Brown and Keys Botzum, from IBM Software Services for WebSphere, together with Ruth Willenborg, Senior Manager, IBM WebSphere Performance, set out to come up with the list of what they consider to be the Top Twelve Best Practices for anyone involved in J2EE application development.

For the full details of each one, see their paper on the subject. WJ News Desk bring you here the overall summary list though, which reads as follows:

  1. Always use MVC.
  2. Apply automated unit tests and test harnesses at every layer.
  3. Develop to the specifications, not the application server.
  4. Plan for using J2EE security from Day One.
  5. Build what you know.
  6. Always use Session Facades whenever you use EJB components.
  7. Use stateless session beans instead of stateful session beans.
  8. Use container-managed transactions.
  9. Prefer JSPs as your first choice of presentation technology.
  10. When using HttpSessions, store only as much state as you need for the current business transaction and no more.
  11. In WebSphere, turn on dynamic caching and use the WebSphere servlet caching mechanism.
  12. Prefer CMP Entity beans as a first-pass solution for O/R mapping due to the programmer productivity benefits.

The motivation for compiling the list, say the authors, was paradoxically not a lack of material on the subject, but rather the opposite.

"There now are probably 10 or more books, along with dozens of articles that provide insight into how J2EE applications should be written," they state, adding: 

"In fact, there are so many resources, often with contradictory recommendations, navigating the maze has become an obstacle to adopting J2EE itself."

Brown, Botzum, and Willenborg say that they hope their efforts may assist with finding the best way through that maze. 

More Stories By WebSphere News Desk

WebSphere Journal News Desk trawls the world of e-commerce technologies for news and innovations and presents IT professionals with updates on technology trends, products, and services in the WebSphere family.

Comments (3) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Robert Wilson 08/02/04 09:17:51 AM EDT

A coldfusion front end would be easier and more cost effective to implement than jsp

Bruce Cote 06/24/04 11:50:54 AM EDT

I wouldn''t go around bashing Netegrity SiteMinder. It''s a far better security product than anything IBM ever launched.

Serguei Bakhteiarov 06/11/04 08:59:24 AM EDT

I would not publish these practices. This is a really bad move that creates myths. Though the importance for the automated regression tests is an invariant for EVERY software development, not only for J2EE, others so called "best practices" are very questionable and vary from app to app.

For instance, MVC implementation caused a wide spread usage of Singletons... And the Singleton pattern is not very good OO pattern at all, it violates lots of OO principles.

The JSP usage is a very short sighted too (consider voice or handhelds web applications).

Now, I envision that IT managers and companies that make the "interview test software" will incorporate these "12 best J2EE practices" into their arsenal and we, developers, will be forced to repeat them and finally, who knows start thinking that these practices are true....