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.
One of the biggest complaints about aspect-oriented programming is that is makes it hard to know what the compiled code will actually look like. When looking at source code, developers invariably ask, “What aspects affect this?” For .NET developers, PostSharp has the answer.
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?
Guice, a lightweight Java dependency injection framework created by Google, recently released version 2.0. InfoQ spoke with Google Developer Team member Jesse Wilson to learn more about this release and what capabilities it adds to Guice.
In this article Manjunath R. Naganna introduces a strategy for overriding the default fetching pattern in the Repository/DAO class with a different fetching pattern based on the specific use case as defined with Aspect Oriented Programming. Aspect helps in deciding which fetching strategy needs to be used in a particular business use case.
PostSharp, the popular .NET AOP framework, has a new release available: 1.5 CTP 3. This release builds on the previous features and adds significant performance improvements.
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.
This article provides a practical example of light-weight workflow orchestration using Spring AOP and AspectJ.
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.
Custom annotations are a great way to add common reusable behavior to Java applications. John Heintz from New Aspects discussed at the recent No Fluff Just Stuff (NFJS) Java Symposium, the design techniques for adding behavior to Java Annotations.
The AOP framework PostSharp now supports Silverlight, Mono, and .NET Compact Framework.
Managing commonality and variability is the core of product line engineering. In this presentation, Markus Völter illustrates how model-driven and aspect oriented software development help addressing the challenge of managing variability in product line engineering.
Orbitz Worldwide, a leading global online travel company, has open sourced two monitoring tools Extremely Reusable Monitoring API (ERMA) and Graphite, a persistence and visualization component. ERMA is a home grown Java API and library that has been used in several web applications at Orbitz to capture monitoring statistics in the applications at run-time.
Domain-Driven Design is a subject where there currently are very few examples of how to actually do it in practice. In this article, Srini Penchikala gives you guidelines, practices, frameworks and tools that technical leads and architects can use in the effort of implementing a system in a Domain-Driven way.
InfoQ.com is a next generation web portal combining the latest advancements in portal technology and web development. In this presentation, Alexandru Popescu and Floyd Marinescu walks through the good, the bad, and the ugly of building InfoQ.com; from initial (lack of) requirements, designs, implementation choices, and deployment issues, and all the lessons learned along the way.