This week's book giveaway is in the Android forum.
We're giving away four copies of Android Programming: The Big Nerd Ranch Guide and have Bill Phillips & Chris Stewart on-line!
See this thread for details.
Win a copy of Android Programming: The Big Nerd Ranch Guide this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Question about design pattern  RSS feed

 
Renato Carauta
Greenhorn
Posts: 8
Eclipse IDE Java Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't understand the question bellow

Which design pattern, when used, may introduce stale business data in the presentation tier?

A) Business Delegate

B) Transfer Object

F) Front Controller

The right answer is letter B. I don't understand this design pattern.

The source of this question is this mock exam OCEWCD (Java EE 6 Web Component) Training Lab
 
Sanjay Singh
Ranch Hand
Posts: 37
Hibernate Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The Transfer Object is the copy of remote entity so during the time we data is send to view layer over the network it might be altered by some other program. So Transfer Object might have the stale state. E.g. the view requests for Employee details. The employee data is sent to view in a Transfer Object EmployeeDTO object. While the view gets it and process it some other program can update the Employee data and hence stale state of EmployeeDTO. I hope this helps.
 
Renato Carauta
Greenhorn
Posts: 8
Eclipse IDE Java Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I understand you can have a stale state when you using a Transfer Object. Thank you for your answer.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!