Tracking change and innovation in the enterprise software development community
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
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.
n a recent article on Java.net Eric Batzdorff considers the application of AOP in respect to singletons versus domain objects. Batzdorff points out that the weight of using such technologies can be much more noticeable when advising domain objects versus singletons.
Rod Johnson recently blogged on configuring Spring via Java instead of XML. While the implementation uses annotations it is unique in the fact that they are in a separate configuration class and not in the core business classes themselves.
Using a domain model is rarely as easy as just creating the actual domain model classes and then using them. Soon enough one discovers that sizable amounts of infrastructure code will also be required in support of the domain model. In this article, Mats Helander explains how to use Domain Model Management to handle this complexity in a simple way.
Vigil Bose shows how a business transaction can trigger business events dynamically for subsystem processing. The examples shown in this article uses Spring framework 2.0 and Spring AOP effectively to decouple the business service from the subsystem processing functionality.
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 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.
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.
