Object-oriented software design patterns are not based on specific implementation technologies such as Java, or specific version numbers of an implementation technology. Furthermore, a branding of any set of design patterns such as "JEE Patterns" is a deviation from the concept of object-oriented software design patterns. What you mean by "dropped" is unclear? If an individual feels that something can be designed in a better way, then they are free to do as they please. This is only someone's opinion and not an industry fact.
Arnold Reuser
Ranch Hand
Joined: Nov 20, 2003
Posts: 190
posted
0
There is actually a book written on Real World Java EE Patterns.
It is about Rethinking Best Practices and an example of such a pattern is the Service Locator.
Actually, Sun long ago established an entire set of J2EE-specific design patterns, including DTOs, Front Controllers and more - roughly a dozen patterns that specifically addressed the strengths and limitations of designing for Java in a web application server environment. They had a poster and a book.
I haven't seen anything specific regarding JEE5, but the DTO is pretty much obsolete thanks to EJB3/JPA.
One of the most odious afflictions that Business has inflicted on the modern English language is "pro-active". Most of the time it's simply redundantly used in place of the simple old word "active". And a good deal of the rest of the time it means "You're not overworked enough yet, so go out and find more!"
Arnold Reuser
Ranch Hand
Joined: Nov 20, 2003
Posts: 190
posted
0
The book Real World Java EE Patterns Rethinking Best Practices of Adam Bien is based on Java EE 5.
With the advent of Java EE 5, he was able to remove a remarkable amount of patterns, indirections, and layers without sacrifcing the functionality.
He provides arguments on why several patterns can be considered deprecated. Read the book if you would like to know more about his findings.
Arnold Reuser wrote:The book Real World Java EE Patterns Rethinking Best Practices of Adam Bien is based on Java EE 5.
With the advent of Java EE 5, he was able to remove a remarkable amount of patterns, indirections, and layers without sacrifcing the functionality.
He provides arguments on why several patterns can be considered deprecated. Read the book if you would like to know more about his findings.
0
