Spring Framework: Difference between revisions

Revision as of 05:32, 29 July 2023

Revision as of 05:35, 29 July 2023

Line 125:

===Aspect-oriented programming framework===

The Spring Framework has its own [[Aspect-oriented programming]] (AOP) framework that modularizes cross-cutting concerns in [[Aspect (computer science)|aspects]].{{sfn | Deinum | Rubio | Long | Mak | 2014 | loc=§2-12 Aspect Orientated Programming |pp=99-104}} The motivation for creating a separate AOP framework is to provide basic AOP features without too much complexity in either design, implementation, or configuration. The [https://javagyansite.com/2018/08/19/aop/ Spring AOP] framework takes full advantage of the Spring container.

The Spring AOP framework is [[Proxy pattern|proxy pattern-based]].{{sfn | Deinum | Rubio | Long | Mak | 2014 | loc=§11-6 Managing Transactions Declaratively with the @Transactional Annotation | pp=492-494}}{{sfn | Deinum | Cosmina | 2021 | loc=§2 Spring Framework Fundamentals - The Spring Framework | pp=22-25}} It is configured at [[run time (program lifecycle phase)|run time]].{{Citation needed|date=June 2023}} This removes the need for a compilation step or load-time weaving.{{Citation needed|date=June 2023}} On the other hand, interception only allows for public method-execution on existing objects at a [[join point]].{{Citation needed|date=June 2023}}

Line 295:

* Create stand-alone Spring applications

* Embed [[Apache Tomcat|Tomcat]] or [[Jetty (web server)|Jetty]]{{sfn|Walls|2016|loc=§1.1.3|p=7}} directly (no need to deploy [[WAR (file format)|WAR]] files)

* Provide opinionated '[https://javagyansite.com/2020/02/17/spring-boot-starters/ starter]' [[Project Object Model]]s (POMs) to simplify your [[Maven (software)|Maven]]/[[Gradle]] configuration{{sfn|Walls|2016|loc=§Preface|p=x}}

* Automatically configure Spring whenever possible{{sfn|Walls|2016|loc=§1.1.2|pp=4-5}}

* Provide production-ready{{sfn|Walls|2016|loc=§foreword|p=vii}} features such as [[software metrics|metrics]],{{sfn|Walls|2016|loc=§7|pp=124-139}} health checks {{sfn|Walls|2016|loc=§7|pp=124-139}} and externalized configuration{{sfn|Walls|2016|loc=§3.1-§3.2.3|pp=49-69}}