  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
  | | | Business Delegate and Web Services | Business Delegate and Web Services 2006-02-21 - By Nelio Pereira
Back Hi list.
Briefly, our architecture follows:
Business Delegate -> Session Fa?ade -> Business Object -> DAO -> DB
Our Use Cases are implemented in the BusinessObject layer.
The problem:
We have to call a webservice from our Business Object layer. This webservice is hosted outside our company. I suggested to create a BusinessDelegate to encapsulate this call, so our business rules wouldn't be mixed with those xml/soap technical details. In this situation, our system would be designed as:
Business Delegate -> Session Fa?ade -> Business Object -> Business Delegate -> Web Service
Others think that BusinessDelegate is not an integration pattern, and the DAO should be used instead:
Business Delegate -> Session Fa?ade -> Business Object -> DAO -> Web Service
What does the list think?
Cheers __ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ Nelio Pereira Natura Cosm?ticos S/A +55 -11 4446-2808 neliopereira@(protected)
===================================================================Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
 |