What's the relevance of J2EE Design Patterns?

I'm already familiar of GoF's patterns, and I've been reading on J2EE Design Patterns (specifically, browsing this index). Now, many of them are strikingly similar to either GoF's patterns and the ones in Fowler's PEAA book, what brings me to the question: besides being specific to a platform, aren't these patterns redundant? What makes J2EE patterns better suited for 开发者_JAVA百科Java applications, since design patterns are intrinsically platform/language agnostic?

While the patterns in the GoF book address general OO design patterns, the J2EE design patterns address - well - enterprise/server-side/distributed applications. Some patterns were more related to work around shortcomings of the J2EE platform. But things improved since Java EE 5 (POJOs + annotations).

Have a look at this book:

http://www.amazon.com/Real-World-Patterns-Rethinking-Practices/dp/0557078326/ref=sr_1_1?ie=UTF8&qid=1297032756&sr=8-1

http://www.adam-bien.com/roller/abien/entry/real_world_java_ee_patterns

These patterns are still targeted at the Java EE stack, but I guess you could adapt them to other frameworks as well.