[ajug-members] j2ee design patterns?

[J. Talafous]

My two cents with an automotive analogy.  Design patterns are "how-to's"
that are proven to work successfully.  When I was a teenager with an
American car, I was very suprised to find that the engines under the hoods
of those new Japanese import cars were very similar to the American ones.
Why was that? Because they used the equivalent of design patterns while
building their engines.  The same is true of successful software, some
"arrangements" of software just work well and should be identified and
characterized so they can be reused.


On 2/24/06, J. Talafous <jtalafous at gmail.com> wrote:
>
> http://java.sun.com/blueprints/corej2eepatterns/Patterns/index.html
>
> On 2/24/06, Eric Friedman <efried at bellsouth.net> wrote:
> >
> > This is good start:
> >
> > http://java.sun.com/blueprints/patterns/index.html
> >
> > Eric
> >
> > At 08:23 AM 2/24/2006, you wrote:
> > >What exactly are j2ee design patterns?
> > >
> > >I know of the design patterns book (gof) design
> > >patterns and j2ee best practices and structuring j2ee
> > >applications, but I don't understand what are j2ee
> > >specific design patterns?
> > >
> > >thanks,
> > >
> > >Kammy
> > >_______________________________________________
> > >ajug-members mailing list
> > >ajug-members at ajug.org
> > > http://www.ajug.org/mailman/listinfo/ajug-members
> >
> >
> > _______________________________________________
> > ajug-members mailing list
> > ajug-members at ajug.org
> > http://www.ajug.org/mailman/listinfo/ajug-members
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ajug.org/pipermail/ajug-members/attachments/20060224/2295a0fc/attachment.html