Struts Training in Chennai - Login360

SPRING VS SPRING BOOT Java Frameworks SPRING CONFIGURATION To design any spring based application , the developer needs to be taken care of manual set up Hibernate data source , Entity Manager , Session Factory , Transaction Management everything . XML Spring MVC application some of the XML definition mandatory to manage . Controlling As configuration can be easily handled manually , Spring or Spring MVC can manage to not load some of the unwanted default features for that specific application . Use Better to use if application type or characteristics are purely defined . ( 1 ) spring boot SPRING BOOT CONFIGURATION To Design all those common sets up , developers don't need to define everything individually , Spring Boot Configuration annotation is enough to manage everything at the time of deployment . XML Configuring Spring Boot Application nothing needs to be managed , only annotation managed everything . Controlling In the case of Spring Boot , it automatically handled on default loading part , so developer don't have as such concept of not loading some of the specific unusable spring default features . Use Better to use where the application type of functionality of future use is not properly defined . As integrating any Spring specific feature will be auto - configured here , so no need for any additional configuration . SPRING VS SPRING BOOT Java Frameworks SPRING CONFIGURATION To design any spring based application , the developer needs to be taken care of manual set up Hibernate data source , Entity Manager , Session Factory , Transaction Management everything . XML Spring MVC application some of the XML definition mandatory to manage . Controlling As configuration can be easily handled manually , Spring or Spring MVC can manage to not load some of the unwanted default features for that specific application . Use Better to use if application type or characteristics are purely defined . ( 1 ) spring boot SPRING BOOT CONFIGURATION To Design all those common sets up , developers don't need to define everything individually , Spring Boot Configuration annotation is enough to manage everything at the time of deployment . XML Configuring Spring Boot Application nothing needs to be managed , only annotation managed everything . Controlling In the case of Spring Boot , it automatically handled on default loading part , so developer don't have as such concept of not loading some of the specific unusable spring default features . Use Better to use where the application type of functionality of future use is not properly defined . As integrating any Spring specific feature will be auto - configured here , so no need for any additional configuration .