File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes Design Patterns & J2EE Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Design Patterns & J2EE" Watch "Design Patterns & J2EE" New topic
Author

Design Patterns & J2EE

Malhar Barai
Author
Ranch Hand

Joined: Aug 17, 2001
Posts: 399
Hi Authors,

Nice to see you here.
Well with variety of Design Patterns available for J2EE based development, dont you think its high time that some of the patterns get standardised else there will be n number of patterns available to do a particular task, & we could find that the development becoming more clumsy instead of easing out.

TIA
MB


Malhar Barai
SOA & Java Book
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

Well with variety of Design Patterns available for J2EE based development, dont you think its high time that some of the patterns get standardised else there will be n number of patterns available to do a particular task, & we could find that the development becoming more clumsy instead of easing out.


I did not understand by "Standardizing patterns" ? Are you talking about the implementation of pattern? Could you please provide some examples.


Groovy
somkiat puisungnoen
Ranch Hand

Joined: Jul 04, 2003
Posts: 1312

"Standardizing patterns"



I thing , "Standardizing patterns" is reference to J2EE Patterm are extends GOF Pattern or not ???


SCJA,SCJP,SCWCD,SCBCD,SCEA I
Java Developer, Thailand
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

What is wrong in extending pattern. Patterns do not dicate the implemenatation strategy.
Nicholas Cheung
Ranch Hand

Joined: Nov 07, 2003
Posts: 4982

we could find that the development becoming more clumsy instead of easing out.

Sometimes, if you find adopting certain design patterns makes the system becomes more complex, then you may adopt a wrong pattern.

And coding isnt the only consideration. You also need maintainance and enhancement. Why we use Service Locator becos we dont wanna hardcode the IP in the program. If you dont adopt this pattern, if the IP of the machine changes, you need to change lots of codes!

What I can say is, try to adopt the suitable patterns, and NOT all patterns are useful to certain projects, we need a cool selection mechanism.

Nick


SCJP 1.2, OCP 9i DBA, SCWCD 1.3, SCJP 1.4 (SAI), SCJD 1.4, SCWCD 1.4 (Beta), ICED (IBM 287, IBM 484, IBM 486), SCMAD 1.0 (Beta), SCBCD 1.3, ICSD (IBM 288), ICDBA (IBM 700, IBM 701), SCDJWS, ICSD (IBM 348), OCP 10g DBA (Beta), SCJP 5.0 (Beta), SCJA 1.0 (Beta), MCP(70-270), SCBCD 5.0 (Beta), SCJP 6.0, SCEA for JEE5 (in progress)
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Design Patterns & J2EE