cj2eep Business Tier (33) Patterns Roadmap Flash Cards

Play Memory | Create Card File | Append to Card File
Title: cj2eep Business Tier (33) Patterns Roadmap
Description: Maps motivations to particular patterns cj2eep Business Tier patterns (or designs, or refactorings).

A list of 33 common Business Tier requirements (or, motivations) that architects often encounter when creating solutions with the J2EE. Each flash card presents a requirement in a brief statement then matches it with one or more patterns that addresses that requirement.
Number of Cards: 32
Save Count: 5
Author: javatom449
Created: 2002-01-06
Tags: tech applications
Private No

Save Count represents the number of people who have saved this card set to their flashcard list. Consider this an endorsement!

    • Question
    • Answer
    • Side 3
    • "Coding business logic in entity beans"
    • "Business Logic in Entity Beans" page 106 DESIGN
      "Move Business Logic session" page 112 REFACTORING
    • "Minimize coupling between presentation and business tiers"

    • "Business Delegate" page 248 PATTERN
    • "Reduce or eliminate entity bean to entity bean relationships"

    • "Composite Entity" page 310 PATTERN
      "Session Facade" page 291 PATTERN
    • "Trade-offs between using stateful and stateless session beans"

    • "Session Bean--Stateless vs Stateful" page 56 DESIGN
    • "Provide query-results caching for clients on the server-side with forward and backward navigation"

    • "Value List Handler" page 353 PATTERN
    • "Isolate vendor and technology dependencies for services lookup"

    • "Service Locator" page 367 PATTERN
    • "Hide the complexity and dependencies for enterprise bean and JMS component lookup"

    • "Service Locator" page 367 PATTERN
    • "Minimize code duplication between entity beans and Value Object classes"

    • "Value Object" page 261 PATTERN
    • "Reduce remote method invocations by providing coarse-grained method access to business tier solutions"

    • "Session Facade" page 291 PATTERN
    • "Provide uniform boundary access to business tier components"

    • "Session Facade" page 291 PATTERN
    • "Design coarse-grained entity beans"

    • "Composite Entity" page 310 PATTERN
    • "Reduce number of entity beans and improve manageability"

    • "Composite Entity " page 310 PATTERN
    • "On the fly construction of the data model"

    • "Value Object Assembler" page 339 PATTERN
    • "Provide business tier query and results list processing facility"

    • "Value List Handler" page 353 PATTERN
    • "Transfer data between objects and clients across tiers"

    • "Value Object" page 261 PATTERN
    • "Use session beans as business tier facades"

    • "Session Beans as Business-Tier Facades" page 57 DESIGN
    • "Provide protection to entity beans from direct client access"

    • "Wrap Entities With Session" page 56 REFACTORING
    • "Cache business sevices for clients"

    • "Business Delegate" page 248 PATTERN
    • "Encapsulate business services to hide the implementation of the business tier"

    • "Introduce Business Delegate" page 106 REFACTORING
    • "Provide uniform method for business service lookup and creation"

    • "Service Locator" page 367 PATTERN
    • "Minimize and/or eliminate network and container overhead due to entity-bean-to-entity-bean communication"
    • "Eliminate Inter-Entity Bean Communication" page 110 REFACTORING
    • "Hide implementation details of business service lookup/creation/access"

    • "Business Delegate" page 248
      "Service Locator" page 367
      PATTERN
    • "Minimize the overhead of using entity bean finder methods"

    • "Value List Handler" page 353 PATTERN
    • "Partitioning Data Access Code"
    • "Separate Data Access Code" page 113 REFACTORING
    • "Provide simpler uniform interfaces to clients"

    • "Business Delegate" page 248 PATTERN
    • "Provide session beans coarse-grained business services"

    • "Merge Session Beans" page 108 REFACTORING
      "Wrap Entities with Session" page 104 REFACTORING
    • "Hide the complexity of data model construction from the clients"

    • "Value Object Assembler" page 339 PATTERN
    • "Manage relationships between enterprise bean components and hide the complexity of interactions"

    • "Session Facade" page 291 PATTERN
    • "Protect the business tier components from direct exposure to clients"

    • "Session Facade" page 291 PATTERN
      "Business Delegate" page 248 PATTERN
    • "Design complex enterprise beans"

    • "Composite Entity" page 310 PATTERN
    • "Obtain the data model for the application from various business tier components"

    • "Value Object Assembler" page 339 PATTERN
    • "Identify coarse-grained objects and dependent objects for entity bean design"

    • "Composite Entity" page 310 PATTERN