• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

lets share design pattern questions tips

 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi

can anybody tell me how to do the questions of design pattern.
what are the tips and traps while solving question .

generally people says while doing question see the phrases:

for front controller we have " managing the work flow"

so lets discuss the various phrases
please tell if anybody of u know


1.mvc :
2.front controller : "managing the workflow"
3.data access object :
4.transfer object :
5.business delegate :
6.intercepting filter :
7.session facade :


 
Ranch Hand
Posts: 783
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The best tip I can give you regarding the design patterns is to simply understand how to use them. If you have questions about what a specific pattern does or how to use it, post them. I would steer away from any type of "if you see this, then the pattern is that" strategy.
 
Ranch Hand
Posts: 445
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yatesh,
I think, though it is not bad idea for the exam to remember the phrases and get some good score on design patterns, I personally prefer to learn details on desing patterns like what scenarios we use, how to use, what are the consequences, etc..
Any way, here are some key words from me..
"reducing network traffic" : value objects
"caching remote objects" : service locator
"multiple clients" : mvs
"separation of client from business logic": business delegate
anything db related: dao
 
Ranch Hand
Posts: 536
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

"caching remote objects" : service locator


shudnt that be transfer object? i thought service locator is only used for doing a jndi lookup
 
Sheriff
Posts: 14691
16
Eclipse IDE VI Editor Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Such important keywords are actually already listed in the "Consequences" part of the Core J2EE Patterns
 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all

In the exam I had approximately 5 questions about patterns. Some of them presented a scenario or a problem and asked about one or two patterns we could use to help solve the problem or improve the situation.

I remember one question where they asked about benefits of one specific pattern.

I believe most of the questions are based in these main ideas:

1) Transfer object: used to reduce network traffic and to reduce coupling. But its use demands more complex software to handle synchronization and concurrency.
2) Intercepting filter: used to do modify requests before they arrive at a servlet or to modify responses before they go to the client. And filters can be added or put out of the application without changing the code, only accessing the DD.
3) Service locator: used to centralize the responsibility of finding objects over the net. Mainly if you have many different clients, each one of them with different locator systems.
4) MVC: it decreases coupling and separates business and view duties.
5) Front controller: it reduces redundant code.
6) Business delegate: used to reduce coupling and to reduce complexity (while accessing objects in different machines).

Jayne.
SCJP 1.5 SCWCD 1.4
 
a fool thinks himself to be wise, but a wise man knows himself to be a fool - shakespeare. foolish tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
reply
    Bookmark Topic Watch Topic
  • New Topic