Domain Driven Design
An excellent article on Domain Driven Design with a Java example, it emphasizes capturing your domain into POJO and not creating fat objects that mix implementation specific features such as caching with the domain code.
Spring Framework
Spring is a J2EE framework and aims to simplify J2EE development Lightweight – A non invasive container that can assemble set of loosely coupled POJOs. This allows software components to be tested in isolation Abstract Transaction Manager – Allows for pluggable transaction managers, not tied to J2EE environments JDBC abstratcion layer – meaningfull exception hierarchy (no need to extract vendor codes from SQLException) simplified error handling. Integrartes with Toplink, Hibernate, JDO and iBATIS SQL maps AOP functionality – can AOP any object and add aspects such as declarative transaction management. Transaction management can be done without EJB or JTA A flexible MVC architecture – Can work with Struts, WebWork or Tapestry and accomodates multiple view techonlogies like JSP, Velocity, Tiles, iText and POI Spring uses a setter based dependancy injection pattern (Inversion of Control) See my Spring AOP Sample Book Reference: Pro Spring by Rob Harrop Jan Machacek
Comments