InfoQ Homepage AOP Content on InfoQ
-
Crista Lopes on Constraints and Styles of Programming
Crista Lopes discusses the idea of using constraints to define styles of programming and architecture. Also: large scale static analysis of open source code, Open Simulator and VR, and much more.
-
Mik Kersten: A Developer's View of ALM
Mik Kersten, the community team lead for the Eclipse Mylyn project and Eclipse Board Member, discusses the inspiration behind Mylyn, his surprise at its quick success in open source community, and its influence on other development tools. Taking place at Agile 2012, Mik also discusses the role of developers in Agile Lifecycle Management and recent changes in the DevOps movement.
-
Christian Colombo on FSM-based Monitoring and Runtime Verification
Larva is a runtime monitoring system that uses AspectJ to weave monitoring into Java code and can check the correctness of the program using an FSM; Elarva is an Erlang version of the tool.
-
Inside SpringSource with Rod Johnson
In this interview conducted at the SpringOne 2GX conference, Rod Johnson talks about the new advancements SpringSource is bringing to the enterprise Java space, including new cloud options. Johnson discusses open-source Java in general, including the flap over the direction of OpenJDK and Apache Harmony. And he delves into the new Code2Cloud effort from SpringSource and Tasktop, and much more.
-
Dean Wampler on Programming Languages
This interview begins with a discussion of functional programming, the use of Scala by programmers trained in Java and the differences between purely functional languages like Haskell and hybrids like Scala. Later in the interview other programming languages are discussed along with the notion of programming paradigms and the need for combining both paradigms and languages to best solve problems.
-
Adrian Colyer on AspectJ, tc Server and dm Server
SpringSource CTO Adrian Colyer talks to InfoQ about AspectJ. The interview explores how products such as Spring Roo are using AspectJ, and how ideas from AspectJ helped SpringSource improve the Groovy compiler inside Eclipse. Colyer also discusses SpringSource's two server offerings, dm Server and tc Server, OSGi and Scrum.
-
Mark Pollack on Spring.NET 1.3 and 2.0
Mark Pollack talks about the features coming in Spring.NET 1.3 and 2.0. He also covers Spring.NET Integration, the Stonehenge project and the relationship with Spring Java.
-
Greg Young Discusses State Transitions in Domain-Driven Design and DDD Best Practices
In this interview, Greg Young talks about managing state transitions in a Domain-Driven Design project using two separate models, one for reading data from datastore and the other for write-only command operations. He also discussed Command Query Separation to keep the design cleaner and easier to test and maintain and the best practices that developers can use when working on DDD projects.
-
Mark Pollack on Spring and Spring.NET
Mark Pollack, founder of Spring.NET, talks about shares ideas between the Java and .NET communities and the history of Spring.NET. Topics include how to use dependency injection and AOP for more than just logging and where Spring.NET overlaps with WCF.
-
AOP Refactoring with Ramnivas Laddad
AOP expert Ramnivas Laddad explains how to use Aspects for refactoring cross-cutting concerns within classes (not just across classes) for things like reducing boiler plate code and potential for mistakes. How to recoganize and refactor such logic into aspects is covered, as well as applying aspects for resource management and concurrency control.
-
Ramnivas Laddad on AOP Design, Modelling, and Policy Enforcement
Ramnivas Laddad talks about domain aspects, how aspects fit in the design phase, how to model aspects in UML, how to enforce policies with Aspects, how he used Aspects to diagnose production problems including touch threading problems, and using aspects to simplify design pattern implementation.
-
Adrian Colyer on Domain Specific Aspects
AspectJ lead and AOP expert Adrian Colyer briefly talks about Domain Specific Aspects, where business rules and policies and can map to an aspect like solution. Adrian also discusses using AOP to implement design patterns such as Observer/Observable, and AOP adoption.