EJB Patterns vs other Design Patterns

[Barry Brashear]

Could someone explan the difference between EJB patterns and other
design patterns?
Thanks.

[Maulin Vasavada]

Hi Barry,
I think that we should not try compare EJB and other Design patterns because there is only one thing "design patterns" in general. Now, some of those patterns are applicable to EJBs ONLY (hence we name it EJB patterns) and thats all. They are not comparable items according to me
EJB Patterns describes general pattern based behavior in EJB world and other design patterns describes patterns in non-EJB world.
Thanks
Maulin

[Barry Brashear]

Aren't there some that apply to both, such as the MVC pattern? I think
that's the reason for my confusion.
Thanks,
Barry

[Paul Sturrock]

There are some design patterns that can be applied to pretty much any
technology - they are completely language and environment agnostic. MVC is one of them.
[ April 28, 2004: Message edited by: Paul Sturrock ]

[Ajith Kallambella]

EJB design patterns specifically deal with strategies that make using EJBs efficient, and some of them are antidotes for pitfalls in EJB technology. For instance, Session Facade and ValueObject ( although documented as a J2EE pattern ) were born to address "everything is remote" problem.
It is interesting to note that some of EJB design patterns are mere extensions of GOF design patterns. SessionFacade is actually a specialization of the GOF Facade pattern. So is EJBCommand extending from the GOF Command pattern.