While the J2EE Design Patterns were originally
conceived to solve problems encountered
with J2EE application development, is the use
of the term "J2EE" patterns misleading. Is it
not more appropriate to call these patterns
Distributed Application Design Patterns? Its
been my experience that most, if not all of the
J2EE Design Patterns solve problems related to
distributed and component based application
Could not most of the core J2EE patterns be
applied to an environment like .NET?
By putting the focus purely on the J2EE
environment, do we limit ourselves to new
new patterns that can be used and identified?
I would like to hear everyone's thought on this. Design Patterns are supposed to be technology
independent? How does this fit with a topic like
"J2EE" Design Patterns?
In reality, a three tier architecture is a logical splitting. We should be designing our applications so that they are cleanly split between the presentation, business and data logic tiers, but more importantly we do not expose the underlying implementation details.
Along time ago, I used to do some VB programming and use to freak out the VB developers when I would start implementing design patterns in VB. Some of my co-workers were just amazed when I implemented a Model-View-Controller framework using a single ASP page, COM components, XML and XSLT :,>