|
|
|
|
| Java Articles Home » J2EE » [ Busniness Logics ] |
|
| 1. Get down to business | |
| Author: | James Carman |
| URL: | http://www.javaworld.com/javaworld/jw-07-2003/jw-0718-factory.html? |
| Summary: | Numerous projects today start small and grow into larger, more scalable architectures. However, when the architecture changes, the business logic implementation changes too. The user interface might not change, but for scalability, the business logic must migrate from a simplistic JavaBean implementation to an Enterprise JavaBeans (EJB) implementation. If the application is not designed to accommodate changes in the business logic implementation, much of the user interface code may also need to migrate to consume the business logic services. In this article, using a simple framework for accessing your business objects, you will learn how to structure your applications such that modifications to the business object implementation do not require changes to the user interface. (2,800 words; July 18, 2003) | /tr>
| 2. Get down to business | |
| Author: | James Carman |
| URL: | http://www.javaworld.com/javaworld/jw-07-2003/jw-0718-factory.html? |
| Summary: | Numerous projects today start small and grow into larger, more scalable architectures. However, when the architecture changes, the business logic implementation changes too. The user interface might not change, but for scalability, the business logic must migrate from a simplistic JavaBean implementation to an Enterprise JavaBeans (EJB) implementation. If the application is not designed to accommodate changes in the business logic implementation, much of the user interface code may also need to migrate to consume the business logic services. In this article, using a simple framework for accessing your business objects, you will learn how to structure your applications such that modifications to the business object implementation do not require changes to the user interface. (2,800 words; July 18, 2003) | /tr>
| 3. Bring business logic to light | |
| Author: | James Owen |
| URL: | http://www.javaworld.com/javaworld/jw-09-2003/jw-0919-iw-jrules.html? |
| Summary: | A business rule management system (BRMS) extracts and isolates business logic from procedural code. A well-rounded BRMS gives programmers effective tools for creating the rule base and deploying applications and analysts easy-to-use tools for building and changing rules. ILOG's JRules 4.5 offers enterprise developers and business analysts everything they need in a BRMS. (1,500 words; September 19, 2003) | /tr>
| 4. Search business objects in enterprise applications using J2EE | |
| Author: | Rajesh Manickadas |
| URL: | http://www.javaworld.com/javaworld/jw-04-2004/jw-0405-search.html |
| Summary: | Along with the main line transaction-handling component, searching is a needed application component for any distributed enterprise application. This component searches across complex business-object relationship hierarchies involving large result sets. Search provides better control over the result sets to design the presentation/view, tight security, and quicker response time (distributed systems). This article presents a detailed overview of what search is, J2EE design patterns for search, and discusses those patterns best for adding search to distributed enterprise applications. (1,400 words; April 5, 2004) | /tr>