• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Scott Selikoff
Bartenders:
  • Piet Souris
  • Jj Roberts
  • fred rosenberger

Confusion with Design Pattern names

 
Ranch Hand
Posts: 169
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello All,
I'm little comfused about different names for the same design pattern. Here is a list that I have prepared, pls correct me I i'm wrong:

1. MVC- Model View Controller/Component (after all a servlet is a web component!)
2. DTO- Data Transfer Object, I hope the other name is Value Object (VO), Transfer Object and Replicate Object
3. Front Controller/Component (controller or a component is one and the smae thing!)
4. The Data Access Component (also known as the Data Access Object- DAO)


Thanks
Reema
 
Ranch Hand
Posts: 256
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
1.MVC -- Model View Controller is right, as Model is also a component, view is also a component and controller is also a component
Three components are working together to perform specific functionality.
But cannot say the name of pattern as
Model View Component(which component)

2. DTO- Data Transfer Object, I hope the other name is Value Object (VO), Transfer Object and Replicate Object

Yes all refer to same pattern

3.Front Controller/Component (controller or a component is one and the same thing!)

Here yes we can refer to Front Controller as Front Component, as we are specific to particular component

Check this

4.The Data Access Component (also known as the Data Access Object- DAO)

Pattern is Data Access Object, not Data Access Component

Is this a part of Exam

Experts Comments Please ???
 
Reema Patel
Ranch Hand
Posts: 169
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Gaurav,
Thanks for the prompt reply.

Although DAO pattern is not mentioned in cert objectives, but I have come across some mock exams covering this pattern.

Thanks,
Reema
 
Ranch Hand
Posts: 380
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Infact when I read HFJS I saw only 5/6 patterns.

There was a question at the end of pattern chapter which talked of Composite Entity etc. - something which was not talked of in the chapter.

My question is - are we supposed to study all the J2EE Design Patterns?

:
 
pie sneak
Posts: 4727
Mac VI Editor Ruby
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Shivani Chandna:
My question is - are we supposed to study all the J2EE Design Patterns?


For the exam you only need to know the "Big 6", as listed in the objectives:
Intercepting Filter, Model-View-Controller, Front Controller, Service Locator, Business Delegate, and Transfer Object

Other patterns (even fake ones) may be listed as answer options, but only the Big 6 will ever be correct answers.
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic