Spring Recipes A Problem-Solution Approach

The Spring framework is growing. It has always been about choice. Java EE focused on a few technologies, largely to the detriment of alternative, better solutions. When the Spring framework debuted, few would have agreed that Java EE represented the best-in-breed architectures of the day. Spring deb...

Full description

Bibliographic Details
Main Authors: Mak, Gary, Rubio, Daniel (Author), Long, Josh (Author)
Format: eBook
Language:English
Published: Berkeley, CA Apress 2010, 2010
Edition:2nd ed. 2010
Subjects:
Online Access:
Collection: Springer eBooks 2005- - Collection details see MPG.ReNa
LEADER 02927nmm a2200337 u 4500
001 EB000360877
003 EBX01000000000000000213929
005 00000000000000.0
007 cr|||||||||||||||||||||
008 130626 ||| eng
020 |a 9781430225003 
100 1 |a Mak, Gary 
245 0 0 |a Spring Recipes  |h Elektronische Ressource  |b A Problem-Solution Approach  |c by Gary Mak, Daniel Rubio, Josh Long 
250 |a 2nd ed. 2010 
260 |a Berkeley, CA  |b Apress  |c 2010, 2010 
300 |a XLIV, 1104 p  |b online resource 
505 0 |a to Spring -- Advanced Spring IoC Container -- Spring AOP and AspectJ Support -- Scripting in Spring -- Spring Security -- Integrating Spring with Other Web Frameworks -- Spring Web Flow -- Spring @MVC -- Spring REST -- Spring and Flex -- Grails -- Spring Roo -- Spring Testing -- Spring Portlet MVC Framework -- Data Access -- Transaction Management in Spring -- EJB, Spring Remoting, and Web Services -- Spring in the Enterprise -- Messaging -- Spring Integration -- Spring Batch -- Spring on the Grid -- jBPM and Spring -- OSGi and Spring 
653 |a Programming Techniques 
653 |a Computer science 
653 |a Computer programming 
653 |a Computer Science 
653 |a Java 
653 |a Java (Computer program language) 
700 1 |a Rubio, Daniel  |e [author] 
700 1 |a Long, Josh  |e [author] 
041 0 7 |a eng  |2 ISO 639-2 
989 |b Springer  |a Springer eBooks 2005- 
028 5 0 |a 10.1007/978-1-4302-2500-3 
856 4 0 |u https://doi.org/10.1007/978-1-4302-2500-3?nosfx=y  |x Verlag  |3 Volltext 
082 0 |a 005.133 
520 |a The Spring framework is growing. It has always been about choice. Java EE focused on a few technologies, largely to the detriment of alternative, better solutions. When the Spring framework debuted, few would have agreed that Java EE represented the best-in-breed architectures of the day. Spring debuted to great fanfare, because it sought to simplify Java EE. Each release since marks the introduction of new features designed to both simplify and enable solutions. With version 2.0 and later, the Spring framework started targeting multiple platforms. The framework provided services on top of existing platforms, as always, but was decoupled from the underlying platform wherever possible. Java EE is a still a major reference point, but it’s not the only target. OSGi (a promising technology for modular architectures) has been a big part of the SpringSource strategy here. Additionally, the Spring framework runs on Google App Engine. With the introduction of annotation-centric frameworks andXML schemas, SpringSource has built frameworks that effectively model the domain of a specific problem, in effect creating domain-specific languages (DSLs). Frameworks built on top of the Spring framework have emerged supporting application integration, batch processing, Flex and Flash integration, GWT, OSGi, and much more