Service to Worker Pattern

Question

Hi all
I want to ask you an explanation about Service To Worker Pattern
Looking at http://java.sun.com/blueprints/corej2eepatterns/Patterns/ServiceToWorker.html , we can see the example that uses this pattern, I want to know if we can invoke directly business service and store request data in the execute() method, so without create the adapter to store data and passing request helper.The code would be such this:
class MyCommand implements Command
  public string execute(RequestHelper helper)
     Object data = MyBusinessService.getData();
     helper.getRequest().setAttribute('data',data);
     return 'myview.jsp';
}Would this way be correct ? What is the difference/benefit using or not the adapter class?
Thanks

Answer 1

iapazmino wrote:
http://java.sun.com/blueprints/corej2eepatterns/Patterns/ServiceToWorker.html
Are you the original poster or just curious?
At any rate now that I have the source.....
"View management logic is relatively sophisticated, with multiple views potentially mapping to the same request. "
The first part refers to the GUI. That latter refers to request servicing.
As an example consider a system where some users are authorized to view/change data and others are not. A specific example of that is.
- Sales rep is allowed to change contact information for a customer. Sales rep can see but no change commission.
- Management (boss of sales rep) is allowed to change sales rep for customer and commision for account (which goes to sales rep.)
- Customer service rep is allowed to see customer, contact information, sale rep but not change any of it. The customer service rep can't see the commission at all.
(Simple implementation). The request input consists of the following
- Customer number
So 'response' to the above would be to return customer information consisting of the following
- customer name
- sales rep
- commission
- contact.
The GUI logic logic could be written generically such that
- Customer service rep application hides commission (can't be seen) and makes other fields viewable only
- Sales rep application allows contact to be edited but all other fields are viewable only.
- Management screen can edit all fields.
Keep in mind that there are all sorts of possible variations on the above. Such as not returning the commision data at all to the support gui (field exists but it empty in response.) Or handling the screen generically and returning attributes that define access based on the user.