Alef Arendsen, SpringSource, the NetherlandsAlef Arendsen is VP and Principal Consultant at SpringSource. Originally, Alef joined the development team of the Spring Framework in early 2003. Currently, Alef is responsible for several strategic SpringSource clients and he helps them achieve great results using some of the Spring Portfolio products. Furthermore, Alef is responsible for several activities related to technical marketing.
Alef is based out of Utrecht, the Netherlands.
Five Aspects You've Never Heard AboutAspect-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. This session will trigger your imagination when it comes to using aspects in parts of your application you haven't applied AOP before.
Most of the aspect will involve Spring AOP, AspectJ and other parts of Spring. Aspects covered can be found in the world of diagnostics, complex data access and versioning.
Spring == XML, XML == sucks, therefore Spring == sucks??
Last November, Spring 2.5 was released. This version of Spring, the de-facto Java EE application platform marks the beginning of the introduction of alternative ways to configure components. In the, we've mainly focused on provided XML as the main language to perform Dependency Injection on object. Since 2.5, Spring has introduced several new ways to doing this.
This session focuses on the various ways of using the Spring container to Dependency Inject objects such as the traditional <beans> XML language, the extensible namespaces, the @Autowired and @Component annotations, but also the innovative JavaConfig project that is capable of configuring Java objects using @Bean annotations.
Each has drawbacks and advantages and this session will discuss which one you should choose in what scenario. After this code-intensive session, you will walk away with a clear understanding of when XML is a good choice for configuration and when to opt for one of the annotation-based options.
Special knowledge required:
- a bit of Spring knowledge (but not much)
- a bit of data access knowledge (JDBC) is nice to have
