In the Spotlight - Colin Sampaleanu
Original Spring Developer & Director of Sales Engineering, SpringSource
Colin is Director of Sales Engineering at SpringSource. He is a co-founder of the company, and one of the original core committers on the Spring Framework project (gaining commit status in mid-2003). Since starting the company he has served in a number of roles, usually combining both technical as well as business and customer facing aspects. He is a hands-on architect with 20+ years of experience in developing commercial software, including all aspects of the software development lifecycle. Colin is co-author of 'Professional Java Development with Spring'.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.
Presentations by Colin Sampaleanu
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 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."
Books by Colin Sampaleanu
by Rod Johnson, Juergen Hoeller, Alef Arendsen, Thomas Risberg and Colin Sampaleanu
-
This in-depth, authoritative book-written by the lead developers of the Spring Framework-describes common types of problems faced by Java developers and then shows how Spring can help solve them.
Covering the complete spectrum of Java development, the book introduces well-known techniques (such as design patterns) to solve problems as well as new and innovative approaches that can be used in conjunction with other popular open source technologies like Hibernate and Velocity.
Lead author Rod Johnson's two previous books introduced readers to the concepts of the Spring Framework, and this title goes further to explain how the Spring Framework provides a set of functions and tools that can greatly simplify development and testing.
- Available At: http://www.amazon.com/exec/obidos/ASIN/0764574833/102-350004..
SpringSource Team Blog
The voice of SpringSource
Sunday, September 17, 2006
Spring Framework 2.0 RC4 has been released. This is the last release candidate before Spring 2.0 final, and you may find out more about it from the release announcement itself as well as the JIRA issue list for a complete list of changes in this release.
Possibly the most important thing to watch out for is that this release introduces versioned file/location names for the 2.0 DTD and Schemas (XSDs). This was necessary since the XML bean definition format was significantly enahnced for 2.0, but 1.2.x users still need to be able to refer to the 1.2.8 DTD. Here is an example of using the 2.0 "beans" schema (2.0 ships with a number of other new schemas as well, representing various special namespaces):
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
<!– Define your beans here –>
</beans>
Here is an example of using the 2.0 DTD (there is only one DTD, you must switch to schema to get the various new namespaces):
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN 2.0//EN"
"http://www.springframework.org/dtd/spring-beans-2.0.dtd">
<beans>
<!– Define your beans here –>
</beans>
One important thing to watch out for: any existing 1.2.x bean definition file should continue to work as is, since it is pointing to the 1.2 DTD, and all functionality is still supported. To get new 2.0 functionality supported by the new 2.0 DTD or schemas, you need to update your definition files as per the above examples. You also must switch from using the
attribute to define bean scopes, to using the new
attribute instead. The old singleton and scope attributes overlap, and it was considered acceptable to remove the singleton attribute completely in the new DTD/schema definiitons, since the only people affected are people already changing their bean definition files to point to the new DTDs and schemas anyway. So if all you do is modify your existing bean definition files to point to the new DTD or schemas, without fixing up any use of singleton, you will get validation errors!
The new versioned DTD and schemas have been uploaded and are available online. While Spring itself finds the definitions within its own jar file (from the classpath) using an entity resolver, these definitions are needed online for XML Editors and other external users.
Tuesday, May 9, 2006
“You guys are clowns for making me register to be able to browse your archives.
CLOWNS.” –AnnoyedInSF
Of course, this genius couldn’t figure out that in fact you don’t have to [...]