Crista Lopes writes a program in multiple styles -monolithic/OOP/continuations/relational/Pub-Sub/Monads/AOP/Map-reduce- showing the value of using more than a style in large scale systems.
Joe Kuemerle demoes using AOP to separate some of the concerns –logging, exception handling, security, etc. - from a codebase.
Donald Belcham presents how to use AOP to avoid code repetition without following the decorator pattern along with frameworks supporting such aspects.
In this presentation from SpringOne/2GX 2010, Rod Johnson and Stefan Schmidt introduce Spring Roo, how to build a sample application with Spring Roo and SpringSource Tool Suite, unit and integration tests, AspectJ utilization by Spring Roo, automatic query generation, configuring entities, dependency injection, controller/view generation, GWT integration and domain generation from an existing DB.
In this presentation from SpringOne 2009, Christian Dupuis discusses the SpringSource Tool Suite (STS), the philosophy behind STS, the requirements behind STS, the STS 2.1 and 2.2 featureset, several demos of STS capabilities, Groovy and Grails, Spring 3.0, autowiring, namespaces, REST, cross-cutting annotations, AJDT, Spring Roo, Cloud Foundry, tc Server, dm Server, VMWare, and the STS roadmap.
This presentation attacks the problem of software complexity and how various modularity paradigms (e.g., object, functions, aspects) simplify complexity and help separate concerns. This talk explores the design problems where these paradigms are most applicable and extract rules of thumb for when to use them. We will also look at language support for these paradigms.
In this talk, Markus Völter illustrates how model-driven and aspect oriented software development help addressing the challenge of managing variability in product line engineering. Both the problem space and the solution space are described by models, using a model-to-model transformation to map problem space variability to solution space variability.
InfoQ.com is a web app/portal implemented with the latest in portal technology and web development. This session shows the good, the bad, and the ugly of building InfoQ.com; from (lack of) initial requirements, design/implementation choices, deployment issues, and lessons learned along the way. The talk examines features of the site and their implementation in the web layer, domain model, and DB.
Mark Pollack provides an introduction to Spring.NET which can help developers more easily implement and design loosely coupled application architectures. The core concepts in the Spring Framework extend beyond the Java platform and are applicable to .NET. Spring.NET combines the Spring Framework's proven architectural concepts and patterns with additional features specific to .NET.
SpringSource CTO and AspectJ project lead Adrian Colyer discusses where Aspect-Oriented Programming (AOP) should be used, practical applications of AOP in enterprise situations such as Hibernate exception translation and automatic operation retry on nonfatal exceptions, and AOP mechanisms in Spring 2.5.
We've come a long way from the first versions of J2EE. We've learned to avoid invasive programming models, we've developed a rich set of frameworks and APIs, we know how to develop apps based around simple objects. Are we there yet? Most of us would answer no. If we're not there yet, then where are we headed next? Spring founder Rod Johnson explores this issue. Recorded at JAOO Sept 2006.
This talk goes beyond myths surrounding AOP and shows the real deal. It examines many practical applications implemented with and without aspects, providing a context for scrutinizing AOP. It also discusses ways to adopt AOP in pragmatic, risk-managed ways allowing developers to try AOP in their own system and gain understanding at the experiential level without exposing them to undue risk.