Speakers
- Ben Alex
- Michael Alford
- Andres Almiray
- Scott Andrews
- Alex Antonov
- Alef Arendsen
- Mattias Arthursson
- Shay Banon
- Antranig Basman
- Chris Beams
- Burt Beckwith
- Jonas Boner
- Ed Burns
- Andy Clement
- Adrian Colyer
- Hamlet D'Arcy
- Scott Davis
- Hans Dockter
- Keith Donald
- Christian Dupuis
- Justin Edelson
- Mike Esler
- Mike Evans
- Danno Ferrin
- Robert Fischer
- Mark Fisher
- Adam Fitzgerald
- Andrew Glover
- Jeremy Grelle
- Rob Harrop
- Jennifer Hickey
- Pete Higgins
- Hal Hildebrand
- Juergen Hoeller
- Jim Jagielski
- Rod Johnson
- Mike Keith
- Jack Kennedy
- Mik Kersten
- Paul King
- Dave Klein
- Mark Kralj-Taylor
- Guillaume LaForge
- Costin Leau
- Scott Leberknight
- Charles Lee
- John Lewis
- Patrick Linskey
- Martin Lippert
- Mat Lowery
- Wayne Lund
- Ross Mason
- Tom McCuch
- Richard McDougall
- Marty Messer
- Russell Miles
- Jim Moore
- Ryan Morgan
- Billy Newport
- Glyn Normington
- Joseph Nusairat
- Brian Oliver
- Pratik Patel
- Mark Pollack
- Alexandru Popescu
- Arjen Poutsma
- Yan Pujante
- Cameron Purdy
- Matt Raible
- Mark Richards
- Thomas Risberg
- Jared Rodriguez
- John Rymer
- Stefan Schmidt
- Mark Schwartz
- Aleksandar Seovic
- Nati Shalom
- Ken Sipe
- Brian Sletten
- Randy Stafford
- Mike Stenhouse
- Matt Stine
- Rossen Stoyanchev
- Venkat Subramaniam
- Dave Syer
- Matt Taylor
- Mark Thomas
- Greg Turnquist
- Thomas Van de Velde
- Erwin Vervaet
- Scott Vlaminck
- Alexander von Zitzewitz
- Chris Wall
- Craig Walls
- Lucas Ward
- Kevin Whinnery
- David Winterfeldt
- Chip Witt
- Eberhard Wolff
- Aaron Zeckoski
- Oleg Zhurakousky
- Ari Zilka
- Kris Zyp
Colin Sampaleanu
Original Spring Developer & Director of Sales Engineering, SpringSource
Colin has had a long and varied career, including experience developing for and managing his own retail software company, other experience in the C++ shrinkwrap and enterprise software space, experience with Java since '97, and a complete focus on enterprise Java since '99.
Prior to SpringSource, Colin spent more than 4 years as architect then chief architect at a leading software incubator / VC. Colin's role was split between one part hands on architecture, design, and coding, another part mentoring and teaching best practices at the code and process level, and a final part performing technical due diligence and consulting for the VC arm. Throughout this period, Colin gained experience with and an appreciation for agile development practices as a vital part of software success.
Throughout his career, Colin's experience, wide ranging interests and general knowledge in the technology space have led him to be a resource that others have been able to draw on for advice. In general, Colin's background has left him with a deep knowledge of all it takes to successfully put out good software, at the code, process, and business level.
Along with client-facing work at SpringSource, Colin also spends significant time on Spring evangelism, having spoken on many occasion on Java EE and Spring Framework at conferences and JUGs.
Blog
Spring 2.0 RC4 Released: Heads-up on DTD/Schema Renaming, Scope Attribute
Posted 2006-09-17 15:16:00.0
S more »The Rewards of Being an Open-Source Developer
Posted 2006-05-09 14:50:55.0
Basing your business around open-source is pretty tough sometimes, but it all becomes worth it when you get a private forum message like this: “You guys are clowns for making me register to be able to browse your archives. more »Spring Framework at EclipseCon 2006: Stop by and Say Hello!
Posted 2006-03-20 15:18:22.0
EclipseCon have graciously offered Spring Framework one of the 10 ‘pods’ in the open-source pavilion at EclipseCon 2006. The closest tie right now between Spring and Eclipse is probably the Spring-IDE plugin for Eclipse more »Presentations
Leaving Legacy: Strategies (and Justifications) in moving to Spring
Organizations and individuals considering the use of Spring may face a number of concerns which can impact their ability to execute: there may be an existing legacy codebase which needs to be migrated, a lack of familiarity with the new technology, or a n more »Migrating to Tomcat or tc Server
SpringSource tc Server can offer a compelling alternative to traditional (legacy) full stack Java EE application servers, based on a number of factors including performance, licensing cost, resource utilization, usability for agile development environment more »Leaving Legacy: Strategies (and Justifications) in moving to Spring
By Colin Sampaleanu
Organizations and individuals considering the use of Spring may face a number of concerns which can impact their ability to execute: there may be an existing legacy codebase which needs to be migrated, a lack of familiarity with the new technology, or a need to justify the use of Spring instead of continued use of older technologies or use of other alternatives.
This session focuses on strategies and justifications when moving from legacy technologies such as full stack Java EE 1.4 or earlier (with or without EJB 2.x) to the Spring platform. This session will also be of use for those considering the use of Spring with or without full stack Java EE 5.
Topics covered in this session include:
- How Spring integrates with, and builds on Java EE, while offering a number of compelling benefits
- A look at Spring in comparison to EJB 2.5
- The impact of migrating a legacy, full-stack Java EE 1.4 or 1.3 application ((with or without EJB)) to the Spring platform including:
- When and why a migration makes sense
- Factors leading to greater or lesser complexity
- Strategies and techniques when migrating an existing legacy application to Spring, including the transition period as well as the final goal
- Case study: a discussion of one customer's experience in moving a full stack, traditional Java EE 1.4 application (including the use of EJBs and messaging), originally deployed on WebLogic, to a Spring-based architecture with deployment on Tomcat
- Appendix to presentation: Detailed Spring 2.5 & EJB 3.0 comparison
Migrating to Tomcat or tc Server
By Colin Sampaleanu
SpringSource tc Server can offer a compelling alternative to traditional (legacy) full stack Java EE application servers, based on a number of factors including performance, licensing cost, resource utilization, usability for agile development environments, and cost of management, among others. However, for organization looking to move existing applications to tc Server, it is not always clear what the effort and impact will be, to move individual applications. This session outlines a clear set of criteria, strategies, and steps (including any needed refactoring) in deciding to move applications to tc Server, and then making the move. The SpringSource Migration Impact Analys Tool is also covered in this session, along with the optional use of Spring Framework.
Session Detail