Agile communities consider stories “done” when the acceptance tests (also called story tests) are shown to the customer. Originally, this was a manual process, but in recent years, several frameworks have been created to automate this process, providing acceptance testing all the benefits of automated unit testing. One of the most popular of these if called FIT, created by Ward Cunningham.
At NFJS Venkat Subramaniam, author with Andy Hunt of "Practices of an Agile Developer," shared his pragmatic approach to some of the important technical and non-technical factors contributing to project success, including: coding, developer attitude, debugging, mentoring and feedback.
A core part of Spring's middle tier support is the transaction management support. This session presents several interesting "mission critical" cases and shows you how to properly handle them using transactions driven by Spring 2. You'll learn the ins-and-out of the "dark art" that is transaction management within a high-volume mission-critical JEE application.
In this presentation, Scott Davis provides a pragmatic, down-to-earth introduction to Web services as used in the real world by public sites, including SOAP-based, REST and POX-style examples. While the buzzword density leaves nothing to be desired, the presentation contains a very accessible introduction to the core Web services standards.
When it comes to system integration testing Spring adds real value. In this session, Rod Johnson (Spring creator) discusses: integration testing and the support that Spring provides for it, issues around testing the persistence layer, testing web applications.
Juergen Hoeller shares his experiences working on large projects (including his role as chief architect of the Spring Framework) to provide general guidelines on Packaging and package interdependencies, Layering and module decomposition, Evolving a large code base. Juergen will also discuss how tools can play a role in enforcing architectural soundness.
Mark Richards tells us what an ESB is, its role, what capabilities it provides, and the various ways an ESB can be implemented. He takes a close look at the JBI specification (JSR-208) and explains what impact it will have with the ESB world. This will teach you how to determine your own specific requirements for an ESB and then match these requirements to the product space.
This talk goes beyond myths surrounding AOP and shows the real deal. It examines many practical applications implemented with and without aspects, providing a context for scrutinizing AOP. It also discusses ways to adopt AOP in pragmatic, risk-managed ways allowing developers to try AOP in their own system and gain understanding at the experiential level without exposing them to undue risk.