Java Enterprise Edition (JEE) “Core Design Patterns” JEE Core Design Patterns

Java Enterprise Edition (JEE) “Core Design Patterns” JEE Core Design Patterns

Java Enterprise Edition (JEE) ªCore Design Patternsº JEE Core Design Patterns Presentation Business Integration Tier Tier Tier Intercepting Filter Business Delegate Data Access Object Front Controller Service Locator Service Activator Context Object Session Facade Domain Store App Controller Application Service Web Service Broker View Helper Business Object Composite View Composite Entity Service to Worker Transfer Object Dispatcher View TO Assembler Value List Handler Front Controller Intent ● provide a single point for processing user requests http://java.sun.com/blueprints/corej2eepatterns/Patterns/FrontController.html Front Controller Motivation ● single processing point for all client requests – across views & session – can be used to inject cross-cutting concerns ● logging ● security ● separation of business code from presentation code ● provides logical resource mapping – http://server/resource.jsp – http://server/servlet/resourceController – actually we can map multiple requests to the same controller Front Controller Motivation ● reusability & organic growth – controllers can be specialized (sub-classing) – dynamically or declaratively mapped – what is declarative mapping – why do we care? Intercepting Filter Intent ● preprocessing & post processing of user requests http://java.sun.com/blueprints/corej2eepatterns/Patterns/InterceptingFilter.html Intercepting Filter Filter chain request request request controller filter1 filter2 response response response How is this different from pipes & filters? Intercepting Filter Motivation ● functionality injection ● improved reusability – filter chains can be defined in a number of ways ● declarative configuration Difficulties ● information sharing ● fault-tolerance Data Access Object (DAO) Intent ● abstract access to data repository http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html DAO - Example Concerns Mapping ● object to persistence mapping – identifier, foreignkey – object to single table – how do we map associations ● object to object ● object to list of objects ● object to map of objects – how do we map inheritance Concerns Mapping ● deletions – single object deletions are easy – deleting associated objects could cause violations ● mappers – allow to vary schema differently from object model DAO Mappers ● allow to vary schema differently from object model belongs id id User Group fname name lname DAO ER translates into ● tables, columns ● each table row represents an entity.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    14 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us