Java EE 5
12 Best Practices for J2EE Developers Named
What are the most important best practices for J2EE, when you include Web services development as a part of J2EE? Three IBM staffers recently had a shot at coming up with a Top Twelve.
Reader Feedback: Page 1 of 1
#3 |
Robert Wilson commented on 2 Aug 2004
A coldfusion front end would be easier and more cost effective to implement than jsp
|
#2 |
Bruce Cote commented on 24 Jun 2004
I wouldn''t go around bashing Netegrity SiteMinder. It''s a far better security product than anything IBM ever launched.
|
#1 |
Serguei Bakhteiarov commented on 11 Jun 2004
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....
|