Downloaded 876 times
![Evolution of Spring [ 1.0, 2.0, 2.5, 3.0, 3.1]8](https://image.slidesharecdn.com/javaeevsspringshootout-111009212603-phpapp02/85/Java-EE-vs-Spring-Framework-10-320.jpg)
![Evolution of Spring [ 1.0, 2.0, 2.5, 3.0, 3.1]8](https://image.slidesharecdn.com/javaeevsspringshootout-111009212603-phpapp02/75/Java-EE-vs-Spring-Framework-10-2048.jpg)
Uploaded byRohit Kelapure
Java EE vs Spring Framework
The document presents a detailed comparison and evolution of Java EE and Spring Framework, highlighting their features, specifications, and coexistence in software development. Key topics include updates from Java EE 6 and Spring 3.1, dependency injection, integration techniques, and ecosystem support. It also provides references for further reading and best practices for integration between the two frameworks.
More Related Content
![【旧版】Oracle Database Cloud Service：サービス概要のご紹介 [2021年7月版]](https://cdn.slidesharecdn.com/ss_thumbnails/ocidatabaseoverview210709-210709093949-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Java EE vs Spring Framework
- 1. Java EE andSpring Framework ShootoutRohit Kelapure IBM Advisory Software Engineer, http://wasdynacache.blogspot.com/Reza RahmanIndependent Consultant, Author, Java EE Expert http://www.rahmannet.net/Presentation can be downloaded from http://db.tt/1q9us2JH
- 2. Important DisclaimersTHE INFORMATIONCONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILST EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. ALL PERFORMANCE DATA INCLUDED IN THIS PRESENTATION HAVE BEEN GATHERED IN A CONTROLLED ENVIRONMENT. YOUR OWN TEST RESULTS MAY VARY BASED ON HARDWARE, SOFTWARE OR INFRASTRUCTURE DIFFERENCES.ALL DATA INCLUDED IN THIS PRESENTATION ARE MEANT TO BE USED ONLY AS A GUIDE.IN ADDITION, THE INFORMATION CONTAINED IN THIS PRESENTATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM, WITHOUT NOTICE. IBM AND ITS AFFILIATED COMPANIES SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF: - CREATING ANY WARRANT OR REPRESENTATION FROM IBM, ITS AFFILIATED COMPANIES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS2
- 3. Copyright and Trademarks©IBM Corporation 2011. All Rights Reserved. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., and registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web – see the IBM “Copyright and trademark information” page at URL: www.ibm.com/legal/copytrade.shtml3
- 4. Outline Evolution of JavaEE and SpringJava EE 6 & Spring 3.0, 3.1 highlightsSpring 3.1 feature comparison with Java EE 6CDI and Spring ecosystemSpring and Java EE coexistenceConclusion4
- 5. J2EE Java EE Specifications* Introduced in spec.
- 6. Evolution of J2EEJavaEE6 (Dec 09)New specs (JAX-RS, CDI, Bean Validation)Prune dead woodEJB 2.x, JAX-RPC, JAXR, JEE App. Deploy, JEE App mgmt.Extensibility Easy Framework Pluggability (web fragments & CDI Extensions)Enhanced ease of developmentPOJO annotation based Servlets, Asynchronous processing (Servlet 3.0 & EJB 3.1)EJB 3.1EJB-in-WAR, No-interface view, Singleton, EJB-lite, TimersContextual Dependency Injection (CDI)RESTful servicesPortable JNDI namesJSF2.0Facelets, built-in-AJAX, Skins, Annotations, Resource handlingSimplified Navigation, Easier custom components, View & Page scopesBookmarkable pages, Project Stage, Expanded event modelJPA 2.0Mapping enhancements, JPAQL, Criteria Query API, Pessimistic lockingProfiles reduce platform size Web Profile 12 specsVendor supportWebSphere AS 8 JBOSS AS 7 Oracle WebLogic 11g Glassfish 36
- 7. JSR 299 Contexts and Dependency Injection (CDI)Adds dependency injection to JEE and makes it type-safe.
- 8. Hollywood principle -Don’t call us, we will call you
- 9. No hard codeddependencies on other specificationsAssists in unifying the Bean modelWell defined contexts, the ability to bind beans statefully to them & manage their lifecycle.Introduces an event notification system to decouple producers & consumersUses interceptors to foster loose coupling Extend behavior with type safe interceptor bindingsRefines interceptors into decorators for finer grained controlIntegrates with the Unified EL to bridge JSFEnables use of EJB 3.0 components as JSF managed beansIntroduces an SPI to extend JEE – Roll your own JEE7!Not only an API but also a SPIRich ecosystem of CDI extensionsAdds the Web conversation contextSpring does NOT provide support for CDI7
- 10. Evolution of Spring [ 1.0, 2.0, 2.5, 3.0, 3.1]8
- 11. Spring Framework9Lightweight dependencyinjection Aspect orientedLayered application & container frameworkWell defined modules on top of the core containerNOT an all-or-nothing solution
- 12.
- 13. Java EE vs. Spring Framework Features/APIs Overview11
- 14. Java EE vs.Spring Business Component12
- 15. Spring XML forBusiness Component Injection13
- 16. Spring XML forBusiness Component Injection14
- 17. Spring JavaBased Configuration15
- 18. Spring JavaBased Configuration16
- 19. Java EE Interceptorvs. Spring Aspects17
- 20. Java EE vs.Spring Injection18
- 21. Java EE vs.Spring Injection – Spring configuration19
- 22. Facelet Component20JSF 2vs. Spring MVC Front Controller
- 23. 21JSF 2 vs.Spring MVC Front ControllerFacelet
- 24. 22JSF 2 vs.Spring MVC Front ControllerEntityJSF Event Handler
- 25. JSF 2 vs.Spring MVC23Spring MVC JSP
- 26.
- 27.
- 28. Spring MVC web.xmlconfiguration26
- 29. Java EE vs.Spring Scheduling27
- 30. Java EE vs.Spring Scheduling28
- 31. Java EE vs.Spring Messaging29
- 32. Spring JMS Configuration30
- 33.
- 34. Java EE MessageProducer & JMS Abstraction32
- 35. Java EE MessageProducer & JMS Abstraction33
- 36. Hacking the JavaEE Platform - CDI ExtensionsActivated by dropping jars on the application classpathLoaded by the java.util.ServiceLoader SPIIntegrate with container through container lifecycle events byRegister additional beans, interceptors and decoratorsInjecting dependencies into its own objectsIntroduce custom scope with backing contextAugment or override bean annotation-based metadata with other source Tools/utilities, extending Java EE, integration with Java EE APIs, integrating with non-standard APIs, making Java EE features available in non-Java EE 34
- 37.
- 38. CDI Ecosystem Snapshot36RuntimesImplementationsPortableExtensionsWeldCanDITools
- 39. Spring & JavaEE CoexistenceIntegration with Java EE APIs Spring beans can be injected into JSF Managed BeansSpring beans can be referenced in EL with no JSF Backing beansSpring JmsTemplate can be used on top of raw JMS API for convenienceSpring Listeners similar to EJB MDBs especially JCA rather than JMS listenersHibernate validator standardized as Bean Validation (JSR 303) Spring 3 supports excellent bi-directional integration with EJBsCDI and Spring Integration through the Spring Bridge to CDINative support for Java EEJava EE5 and Java EE6 annotations supported by SpringSpring can use JPA / Hibernate nativelyApplication server integrationDataSourcescan use application server QoS like pooling, transactions, statement caching, debugging, monitoring and security37
- 40. Java EE coexistencewith Spring38
- 41.
- 42. ReferencesEvolution of JavaEE http://en.wikipedia.org/wiki/Java_EE_version_historyJava EE 6 Tutorial http://download.oracle.com/javaee/6/tutorial/doc/Spring Docs http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/Spring Projects http://www.springsource.org/projectsMiscellaneous CDI Extensions https://github.com/softwaremill/softwaremill-commonMigrating Spring to Java EE https://github.com/paulbakker/migrating-spring-to-javaeehttp://ocpsoft.com/java/spring-to-java-ee-a-migration-guide-cdi-jsf-jpa-jta-ejb/CDI- Spring Bridgehttp://rick-hightower.blogspot.com/2011/04/cdi-and-spring-living-in-harmony.htmlhttp://niklasschlimm.blogspot.com/2011/08/jsr-299-cdi-interceptors-for-spring.htmlhttp://niklasschlimm.blogspot.com/2011/08/jsr-299-cdi-decorators-for-spring-beans.htmlBest practices integrating Spring with WebSphere Application Serverhttp://www.ibm.com/developerworks/websphere/techjournal/0609_alcott/0609_alcott.htmWhat’s new in Spring 3.1 http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/htmlsingle/spring-framework-reference.html#new-in-3.140
- 43. References continued SEAM 3http://seamframework.org/Seam3CODI http://myfaces.apache.org/extensions/cdi/Weld http://seamframework.org/WeldCanDIhttp://www.caucho.com/resin/candi/OpenWebBeanshttp://openwebbeans.apache.org/owb/index.html41
Editor's Notes
- #6 http://www.ibm.com/developerworks/websphere/library/techarticles/0707_barcia/0707_barcia.htmlhttp://en.wikipedia.org/wiki/Java_EE_version_historyA brief history of J2EE / Java EEBefore J2EE (Mid 1990s)Many competing products, In-house frameworks, Fragmented server side market, real danger of vendor lock-in, expensive solutionsGlory days of J2EE (1999-2003)Release of J2EE 1.2, 1.3 & 1.4Specifying first and then implementingStandardization of server side java enterprise technologiesEnterprise Java gains a reputation of complexityDecline of J2EE (2004- 2008)Projects fail due to flaws in platformRise of open source – Spring Framework, Seam, AspectJ, HibernateMove towards lighter weight solutionsRise of Java EE (2007 - Present)Emphasis on user Component model not just a deployment platformDeveloper productivity & ease of use enhancements Extensibility and right sizingTraps that created complexityDesign by committeeEverything has to be standardizedTools can make complexity acceptableLack of openness to other platforms, sources of ideasLack of developer freedom to hack the platformIvory tower architectureEJB Programming model was the worst offenderNaïve ORM solution & Broken persistence modelIdea that all business objects should be distributedRigid API interfaces, Difficult to unit test, Needed IDE toolingGlutton for XML & boilerplateJSF 1.2 ShortcomingsNo integration with EJBsNo templating support (before 1.2) Transparent to HTTP RequestsDifficult to create custom componentsLacks conversation scope & advanced componentsWeak page oriented supportOverly complex lifecycleJSP & JSF inherent mismatchJava EE pioneers innovations in server-side JavaA widely deployed but much maligned platformSpring, along with Hibernate, brings POJO programming, IoC and testability to the mainstreamJava EE 5 adopts ideas, as well as annotations and convention-over-configurationHibernate standardized into JPA, Spring remains nonstandard but adopts Java EE features to a degreeJava EE 6 matures ideas in Java EE 5 in addition to pruning and profilesCDI, JSF 2, JPA 2, EJB 3.1, Servlet 3, JAX-RS major API changes
- #8 Context abuse HttpSessionSo many beans so little common groundAddresses long standing challenges with Java EE
- #9 http://blog.springsource.com/2011/02/11/spring-framework-3-1-m1-released/Bean definition profilesUnified property management through Spring's new Environment abstractionEnhancements to Java-based configuration with @Feature methodsExpanded MVC namespace support and a Java-based configuration equivalentStreaming support and new interception model for the RestTemplate APIComprehensive caching supportNew c: XML namespace for concise configuration of constructor injection
- #10 Applications developed against commonframework(s)– common programming model– common configuration model• Adapted onto target platform at runtime– using common service abstractions– thread pooling, service lookups, etc• Strict separation between applicationcomponent model and platform services– clear boundaries and separation of responsibilitieshttp://www.springsource.org/aboutThe most complete lightweight container, providing centralized, automated configuration and wiring of your application objects. The container is non-invasive, capable of assembling a complex system from a set of loosely-coupled components (POJOs) in a consistent and transparent fashion. The container brings agility and leverage, and improves application testability and scalability by allowing software components to be first developed and tested in isolation, then scaled up for deployment in any environment (J2SE or J2EE). A common abstraction layer for transaction management, allowing for pluggable transaction managers, and making it easy to demarcate transactions without dealing with low-level issues. Generic strategies for JTA and a single JDBC DataSource are included. In contrast to plain JTA or EJB CMT, Spring's transaction support is not tied to J2EE environments. A JDBC abstraction layer that offers a meaningful exception hierarchy (no more pulling vendor codes out of SQLException), simplifies error handling, and greatly reduces the amount of code you'll need to write. You'll never need to write another finally block to use JDBC again. The JDBC-oriented exceptions comply to Spring's generic DAO exception hierarchy. Integration with Toplink, Hibernate, JDO, and iBATIS SQL Maps: in terms of resource holders, DAO implementation support, and transaction strategies. First-class Hibernate support with lots of IoC convenience features, addressing many typical Hibernate integration issues. All of these comply to Spring's generic transaction and DAO exception hierarchies. AOP functionality, fully integrated into Spring configuration management. You can AOP-enable any object managed by Spring, adding aspects such as declarative transaction management. With Spring, you can have declarative transaction management without EJB... even without JTA, if you're using a single database in Tomcat or another web container without JTA support. A flexible MVC web application framework, built on core Spring functionality. This framework is highly configurable via strategy interfaces, and accommodates multiple view technologies like JSP, Velocity, Tiles, iText, and POI. Note that a Spring middle tier can easily be combined with a web tier based on any other web MVC framework, like Struts, WebWork, or Tapestry.
- #11 Both are competent middleware stacks with mostly equivalent functionality but very different approachesJava EE provides a well-integrated solution stack that makes sensible default choices for you and minimizes the amount of configuration requiredSpring is a pluggable framework with explicit configuration, fine grained control and wide-variety of integration with overlapping technologiesJava EE is an open standard, while Spring is an open source tool from a commercial vendorCDI and 3rd party Extensions have provided a standard compliant way to hack the Java EE platformSpring framework weakens integration with application server runtime QoS, such as security, workload management, and high availabilitySeveral implementations of Java EE specifications are available whereas Spring has only ONE implementationPace of innovation is faster in the Spring Framework since Spring is Community driven vs Java EE that is driven by the JCP
- #36 MyFaces CODI is your best friend for CDI based projects.The Apache MyFaces Extensions CDI project (aka CODI) hosts portable extensions for Contexts and Dependency Injection (CDI - JSR 299) for the Java-Platform (SE and EE). CODI is a toolbox for your CDI application (it provides advanced and convenient features e.g. for JSF and Bean-Validation). Like CDI itself CODI is focused on type-safety. It is a modularized and extensible framework. So it's easy to choose the needed parts to facilitate the daily work in your project.The main focus is to provide superior tools which will support you on solving your daily needs of software development with CDI, JSF, BV and JPA. However, you will also find modules which are independent of JSF as well as modules which improve the compatibility with other MyFaces frameworks like MyFacesExtVal. Maybe the most important feature of MyFaces CODI is that it allows you to build a concise and efficient application-architecture.