We use MyFaces 1.2.2, JSF 1.2, facelets 1.1.13, Spring 2.5, Hibernate 3.2 50% of the code is already written using JSF, Spring,Hibernate. Next we need to work on the most complex module of the system which has more than 80 business rules. We plan to have 2-3 developers working on this module
Problem Statement: •Redundant implementation of the same business rules for web application and external web application Business rules are implemented in many different ways (e.g., in-line, utility methods, utility classes) and are difficult to distinguish from other code. •Variants of a business rule depend on the context (e.g., operation, object type, user). For example, the rule varies on the whether the caller is the GUI, or other web service user. •Large number of business rules that need to be implemented, unit tested, and eventually maintained Solution Goals: Business rules are implemented in only one piece of code. Business rules have an consistent, identifiable form. Variants of a business rule are selected by the calling code based on the context. This will eliminate if statements in the caller. Developers are able to work in parallel on business rules without stepping on each other. Proposed Solution: Use Strategy Design Pattern ??? Does it make sense to have each business rule is encapsulated in a single class. Any pointers/suggestions will be greatly appreciated -- View this message in context: http://www.nabble.com/Business-Rule-Framework-tp18783182p18783182.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
