SpringSource

Presentation: "Making sense of AOP choices"

Time: Wednesday 15:45 - 17:00

Location: Volmer Room

Abstract:

One-size-fit-all fits nothing. Just one kind of AOP won't fit all applications, either. Therefore, there are many choices available when using Spring-AspectJ combination. First, there is a choice about AOP system: proxy-based AOP or bytecode-based AOP.

Then there is a syntax choice: traditional AspectJ, @AspectJ, and XML syntax. Within bytecode-based weaving, there are weaving choices: build time weaver or load-time weaver (LTW).

If you choose LTW, you have further choices of AspectJ agent-driven or Spring-driven LTW. Confused? Don't be. These choices, while confusing at first, exists for a reason. This session explores all these choices and provides guideline on choosing the right combination to make you successful with AOP.

Senior Consultant Joris Kuipers, SpringSource

Senior Consultant Joris Kuipers

Joris Kuipers is a Senior Consultant for SpringSource in The Netherlands. Starting out in 1999 as one of the core members of a Research & Development team, he investigated amongst other things the IBM SanFrancisco framework (a J2EE predecessor) and the use of various XML-related technologies.

Joris specialized in J2EE technology and became the Java Technical Consultant for the Dutch Central Bank in 2003. In this role, he was responsible for all development technologies and processes used in the Java department.

He streamlined the software configuration management process by introducing automated builds and continuous integration, migrated system development from a traditional EJB-based environment to a modern, light-weight stack based on Spring and Hibernate and supported developers in their day-to-day work as the local Java guru.