On a slightly different topic, the Core J2EE patterns— the book with the Sun logo splashed all over its cover— **mostly** documents "patterns" (used extremely loosely because I content that the only real patterns were those introduced by the classic GoF book) that were often fixes or work-arounds for missing functionality in the J2EE spec and/or container design flaws. This isn't meant to belittle the engineers that worked on the related J2EE specs, but merely that you have to start somewhere and there were gaps along the way— the core J2EE patterns helped plug the proverbial holes.
Nothing to add. That is exactly what I think based on my experience. Spring, new persistency APIs and MVC frameworks has removed need of the "Core J2EE patterns" however I know lots of application were build on top of them. Without them EJB would go out of usage much earlier. So statement "Cairngorm is based on the Core J2EE patterns" does not impress me but rather make me think that there should exist some more lightweight approach :). However any approach is better than no approach at all.
WBR, Mykola
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
