Advantages or Benefits discussed Business Delegate J2EE Design Patterns Example

\| Interview Questions on Java \|	\| Coding Tips on Java \|	\| Your Questions on Java \|	\| EJB \|	\| Servlet and JSP \|	\| Hibernate Tutorial \|	\| Spring Tutorials \|	\| Java Design Patterns \|	\| J2EE Design Patterns \|	\| Apache ANT \|
\| Apache DBCP \|	\| Struts Struts 2 Example Tutorial \|	\| Apache Beehive JdbcControl \|	\| Apache Log4j \|	\| Apache Axis \|	\| Open Source Project Ideas \|	\| Web Technology \|	\| J2EE Technology \|	\| Java News \|	\| Spring Hibernate Example \|
\| JavaScript Tips \|

Struts Tutorials: Struts2 Tag CheckBoxList
, Checkbox, Iterator, IF Struts2 Tag Library Example Struts2 Tiles Example Struts2 Tiles I18N Example Struts2 Questions Struts Tiles I18N Example Struts Eclipse MVC Struts2 Tags Struts2 Example and Tutorial Struts MVC Struts2 Validation
Hibernate Tutorials: Hibernate Case Study Class Hierarchy Persist Example Using Hibernate Interceptor Hibernate Questions with Answer Hibernate Many-to-Many Mapping Example Hibernate one-to-many Mapping Example Hibernate and ORM tools Spring Hibernate Example Hibernate SessionFactory Example Hibernate Mapping Class Hierarchy Hibernate Questions Hibernate SessionFactory Questions Spring Hibernate Example: Spring Hibernate Case Study

Tags/Keywords : Advantages-or-Benefits-discussed - Business-Delegate - J2EE-Design-Patterns Example
Author : ISHTEK
Date (Year/Month/Date): 2009-05-26 Advantages or Benefits of Business Delegate J2EE Design Pattern What are the benefits or advantages of Business Delegate J2EE Design Pattern ? I think, 1. Business Delegate Design Pattern can de-couple business side implementation from the client side code or implementation. Thus making any future change or replacement of additional business service with the old business service, easy to manage. 2. Business Delegate Design Pattern can hide complex Remote exception and runtime exceptions or unchecked exceptions from licking or sneaking into client tier or code. Client or caller code might have no knowledge of how to handle this type of exception, and eventually will be exposed to use, thus making system vulnerable. 3. Business Delegate Design Pattern can provide coarse-grain business method or service, thus reducing number of remote method calls. 4. Business Delegate Design Pattern is easy to mock business delegate with a test business service for testing client code, thus making client code idependent of business layer, and in absense of /unavailabiulity of business side implementation, cann't stop testers or unit testing to happen. One can provide mock business layer with hard coded values for testing purposes. 5. Business Delegate Design Pattern can provide a protocol independent / POJO (Plain Old Java Object) view to client side code for supporting reusability or portability, in case of future addition of new or existing communication protocols into system. 6. Business Delegate Design Pattern can provide hidden re-try behavior in case services are temporarily down or not functional and caching mechanism can be implemented for data those never change, for faster performing code 7. Business Delegate Design Pattern should be stateless and should just call respective business services, without holding any data that might change over time. This will help in providing a highly scalable and concurrent system. 8. Business Delegate Design Pattern can use Adaptor and Data Access Object Design Patterns to call Remote services in form of webservices or LDAP context etc. 9. Business Delegate Design Pattern can provide Global Transaction (like JTA Transaction) and single point / unit of work view to the business objective, thus preserving easy commit/rollback policy. 10. As Business Delegate Design Pattern is generally a POJO (Plain Old Java Object) it can use inheritence principle into consideration to move any common functionality to the super business delegator class, without duplicating common code across all business delegates. These are my own understanding only, If you are interested in adding or contracting any of these, you are most welcome to do so just by writing or commenting on this Page.

Terms of Use and Disclaimer : This web site provides some of the information about various technologies, example code, tips, tutorials etc. Like any printed materials, content of these pages may become out of date over a period of time. Therefore all visitor/users of this web site are requested/advised to refer to the originating parties/sources for the latest changes and happenings for detailed information. This information is not intended to be a substitute for the original reference provided by the originating parties/sources. By accessing and using this website in any ways, including, without limitation, browsing the website pages, using any information, using any content and/or downloading any materials, you agree to and are bound by the terms of use described in this page and Usage Terms and Conditions. If you do not agree to all of the terms and conditions contained in the terms of use described in this page and Usage Terms and Conditions, do not use this website in any manner. If you are using the website on behalf of your employer, you represent that you are authorized to accept these Terms of Use on your employer's behalf. All Trademarks are property of their respective owner. Appropriate measure is being taken for providing accurate and up-to-date information but like any printed materials, these blog(s)/contents may eventually be outdated one day, so if you are using any of these information, please refer original content/documentation from respective sources. And under no circumstances shall the Author of these contents and/or this web site be liable for any loss, damage, expense incurred or suffered which is claimed to have occurred because of usage of the contents of this web site. If you have any questions/queries/feedback/suggestions then please write to this web site owner at contact.