Alef Arendsen

Presentations

Five Aspects You Don't Know About

Aspect-oriented programming has been around for quite some time now. Today, AOP is used in a wide range of applications to solve a wide variety of problems. However, some of those solutions are not very well-known to the general Java development community. In this session, Alef will explore several aspects he has seen used in real-world projects. Alef will explore innovative aspects that solve problems ranging from complex data-access scenarios, to security-related situations, to issues where concurrency plays an important role. You will be able to take away the solutions for the problems highlighted during this session immediately and use them in your own projects.

Simplifying CRUD Web Applications

CRUD (create/read/update/delete) actions on domain entities are a significant part of what database-backed web applications are about. Frameworks like Ruby on Rails apply useful conventions that simplify implementing CRUD functionality. These same conventions can be applied in a Spring Web environment to deliver great productivity gains. Come to this session to see how to efficiently implement CRUD actions end-to-end in your Spring Web application. Topics covered include:
- The HTTP contract for CRUD, including important URL and method conventions
- How to implement CRUD actions that are automatically detected and exposed at the proper URL endpoint
- How to apply declarative validation constraints to your CRUD forms
- Strategies for generating CRUD forms from domain model metadata
- Tools to support CRUD-style web application development

This session will cover implementation using Spring Framework 2.5 and Spring Web Flow 2.0.

Architecture Enforcement with AspectJ and Other Tools

Aspect-oriented programming (AOP) is a proven paradigm for enforcing broad organizational policies. In this session, Ramivas and Alef will explore the definition and enforcement of software architecture policies to help keep a code base clean. They will present several reusable examples you can apply within your own organization to catch architectural violations. They will also demo the best features of the leading off-the-shelf architectural enforcement tools. Architectural policies originate from a variety of sources: consensus among developer community about generally accepted programming idioms and best practices, your own ideas on what a good architecture looks like, requirements of the underlying framework, core architecture of the specific project, and specific design choices made by the team on a project. In short, policies represent accumulated knowledge to create better quality software. If there is no enforcement, the errors may go undetected during development and show up only in the deployed system. Often if one error is allowed to go undetected, the associate code often ends up mistaken as design pattern.

In this session, we look at ways to implement architectural enforcement policies along with many reusable examples. Attendees will learn to define policies, and ensure architectural violations are detected immediately upon their introduction into a code base leading to a solid implementation that is faithful to its design.