« StrutsCX - Updated... | Main | [JSPWiki] Sweet... »
20031204 Thursday December 04, 2003

J2EE Patterns Catalog J2EE is simple to learn, simple to develop - especially when Sun recommends you follow a mere handful of patterns. Heh. Posted in Java at Dec 04 2003, 08:53:25 PM MST 9 Comments

Comments:

I know you are being sarcastic. It is a shame that people like you who call themselves J2EE architects and consultants do not understand all these patterns and continue to write average quality code. No wonder the industry is suffering and jobs are being imported elsewhere. These patterns and the book behind them are great. Now you can go ahead and delete this comment .

Posted by Unknown on December 05, 2003 at 12:03 AM MST #

I agree the patterns are great, and I'm far from an architect - but J2EE can be quite intimidating for newbies. It definitely was (and still is) for me when I came from the HTML/JavaScript world. That's all I'm trying to say...

Posted by Matt Raible on December 05, 2003 at 12:50 AM MST #

I agree with Matt. Have you every worked with .NET Anonymous? Not even an Microsoft .dot MVP would know what an MVC architecture is, if they do they don't suggest using it. Seems like the KISS principle is working for them. Matt, how are you seeing .NET influencing J2EE? I'm an experienced J2EE developer and I cannot be as productive in J2EE as in .NET. Not even mentioning the J2EE learning curve for newbies!

Posted by John Cartner on December 05, 2003 at 02:26 AM MST #

John, have you read patterns of enterprise application architecture? Didn't think so. Core J2EE patterns is based on a lot of these patterns and the patterns of enterprise application architecture is not J2EE centric it's .NET and J2EE. Now John go back on coding you hello world program and come back when you want to build a real life application.

Posted by Unknown on December 05, 2003 at 03:12 AM MST #

I think J2EE patterns have their place, and obviously some are the basis of the good frameworks out there. Even Microsoft is using patterns now for .NET development. What they are doing is releasing "application blocks" which implement certain patterns (or combos of patterns) to achieve the plumbing for you, that way the user does not have to dig to deep in order to implement best practices. I guess abstraction is always the key at some point. KISS and keep your level of abstraction at a managable level. I think .NET and J2EE are great to learn together and INTEGRATE, not compete. Web Services will facilitate this trend in the near future. Look for Linux/Mono, J2EE/Linux, .NET/Windows 2003/Longhorn to become more integrated. Learn .NET now if you are a J2EE developer, cause you will have the upper hand when your bosses want you the help out with some .NET integration.

Posted by dsuspense on December 05, 2003 at 06:35 AM MST #

J2EE is simple to learn? Well easier said than done.

Posted by Unknown on December 05, 2003 at 12:15 PM MST #

For what it's worth. I ran across an MVC architecture for .NET. It's a port of Maverick called Marverick.NET. I haven't had a chance to play with it at all, so I don't know if it is any good. http://sourceforge.net/projects/mavnet/

Posted by Brian Burke on December 05, 2003 at 03:43 PM MST #

I've tried for a long time to convince organisations to do even a handfull of the stuff in PEAA. Even having Flowers name on it makes little difference. Somehow now that they've been ripped off and put into J2EE core patterns, people seem to think they're new! Sounds just like what goes in the M$ world to me. IMHO, the core J2EE patterns book could largely be re-published as "Core J2EE workarounds" :)

Posted by Simon Harris on December 05, 2003 at 08:14 PM MST #

Oops. Make that "Fowlers" not "Flowers" hahaha. Wish I could type!

Posted by Simon Harris on December 05, 2003 at 08:14 PM MST #

Post a Comment:
  • HTML Syntax: Allowed