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.
Late last month Google released Guice 3.0, a Java framework that implements the dependency injection (DI) design pattern. The motivation behind Guice was to make it easier for programmers to write DI code by reducing the need to write boilerplate factories. This article examines the new 3.0 features, loks at how Guice 3.0 supports Spring DI, and introduces Guice 4.1 (a.k.a. MiniGuice).
A new version of the Spring.NET framework, version 1.3, was recently released. InfoQ spoke with Mark Pollack, founder and lead of the Spring.NET project, to learn more about this release and what new capabilities it brings, and also to learn more about the new Spring Integration.NET project.
Bruce Eckel, Michael Feathers, Niclas Nilsson, Keith Braithwaite, and others on the question: should languages be fully flexible, allowing the developers to tweak them as they like, and trusting they will be responsible in their work, or should there be clear constraints set in the language from its design phase to avoid mistakes that create bad code, hard to maintain or to read?
Spring AOP/AspectJ combination offers many choices, whether they are AOP system, syntax or weaving related options, and a clear understanding of all those choices is important to apply them pragmatically when using Aspects in enterprise applications. Ramnivas Laddad said just one kind of AOP won't fit all applications and choosing the right combination will help developers be successful with AOP.
While many think of Aspects for cross-cutting concerns such as transaction management, persistence and role based security, another key value for them has been as an enabler for Annotations for ordinary projects. Using Aspects as a way to implement annotation handlers is a different way to think of them than as the traditional architect's "cross cutting concerns" view.
In this article, Srini Penchikala discusses Domain Driven Design and Development from a practical stand-point. The article looks at architectural and design guidelines and best practices that can be used in a DDD project. It also talks about the impact of various design concerns like Persistence, Caching, Transaction Management, Security, Code Generation etc in domain model implementation effort.
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.
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.
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.
