Setting Up Your Development Environment

Transcription

1 APPENDIX A Setting Up Your Development Environment This appendix helps you set up the development environment that you will use to write, compile, and execute the Spring applications discussed in this book. Introducing Project pro-spring-15 Project pro-spring-15 is a three-level Gradle project. pro-spring-15 * is the root project and is the parent of the projects named chapter02 through chapter18. Each of these chapter** projects is also a parent project for the module projects nested under it. The project was designed in this way to help you get oriented with the code and easily match each chapter to the source code associated with it. * At the time when this Appendix was being written, the project was still in raw form. It was later completed, renamed to pro-spring-5 and hosted on the Apress official repository located at: All written above is still valid, except for the project name. Iuliana Cosmina, Rob Harrop, Chris Schaefer, and Clarence Ho 2017 I. Cosmina et al., Pro Spring 5, 829

2 APPENDIX A Setting Up Your Development Environment Figure A-1 shows the project structure. Figure A-1. pro-spring-15 project structure in Intellij IDEA 830

3 Understanding the Gradle Configuration APPENDIX A Setting Up Your Development Environment The pro-spring-15 project defines a set of libraries available for the child modules to use, and it has the Gradle configuration in a file typically named build.gradle. All the modules on the second level (in other words, the chapter** projects) have a Gradle configuration file named [module_name].gradle (for example, chapter02.gradle) so you can quickly find the configuration file with the settings that are common to the projects for that chapter. Also, there s a closure element in pro-spring-15/settings.gradle that verifies at build time that all chapter modules have their configuration file present. rootproject.children.each { project -> project.buildfilename = "${project.name.gradle" assert project.projectdir.isdirectory() assert project.buildfile.exists() assert project.buildfile.isfile() If a Gradle build file is not named the same as the module, then when executing any Gradle task, an error is thrown. The error is similar to the one depicted in the following code snippet, where the chapter02. gradle file was renamed to chapter02_2.gradle: $ gradle clean FAILURE: Build failed with an exception. * Where: Settings file '/workspace/pro-spring-15/settings.gradle' line: 328 * What went wrong: A problem occurred evaluating settings 'pro-spring-15'. > assert project.buildfile.exists false /workspace/pro-spring-15/chapter02/chapter02.gradle :chapter02 * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED in 0s This was a development choice; the configuration file of a chapter module is more visible in an editor this way. Plus, if you want to modify the configuration file for a chapter module, you can easily find the file in IntelliJ IDEA using a unique name. In the pro-spring-15 project, each module on the third level (in other words, the children of chapter**) has a Gradle configuration file named build.gradle. This was also a development choice; in Gradle, having uniquely named Gradle configuration files is not possible at this level in this particular configuration. Another approach for a multimodular project would have been to have in the main build.gradle file specific closures to customize the configuration for each module. But in the spirit of good development practices, we decided to keep the configurations for the modules as decoupled as possible and in the same location as the module contents. 831

4 APPENDIX A Setting Up Your Development Environment The pro-spring-15/build.gradle configuration file contains a variable for each software version being used. These variables are used to customize the dependency declaration strings that are grouped in arrays named for a specific purpose or technology. This file also contains a list of public repositories from where the dependencies are downloaded. In the following configuration, you can see the versions and the array for the persistency libraries used in the project: ext {... //persistency libraries hibernateversion = ' Final' hibernatejpaversion = '1.0.0.Final' hibernatevalidatorversion = '5.4.1.Final' //6.0.0.Beta2 atomikosversion = '4.0.4' hibernate = [ validator : "org.hibernate:hibernate-validator:$hibernatevalidatorversion", jpamodelgen: "org.hibernate:hibernate-jpamodelgen:$hibernateversion", ehcache : "org.hibernate:hibernate-ehcache:$hibernateversion", em : "org.hibernate:hibernate-entitymanager:$hibernateversion", envers : "org.hibernate:hibernate-envers:$hibernateversion", jpaapi : "org.hibernate.javax.persistence:hibernate-jpa-2.1-api: $hibernatejpaversion", querydslapt: "com.mysema.querydsl:querydsl-apt:2.7.1", tx : "com.atomikos:transactions-hibernate4:$atomikosversion" ]... subprojects { version '5.0-SNAPSHOT' repositories { mavenlocal() mavencentral() maven { url " maven { url " maven { url " maven { url " maven { url " tasks.withtype(javacompile) { options.encoding = "UTF-8" In the projects on the second level of the hierarchy (in other words, the chapter** projects), you ll find the chapter**.gradle configuration files. These dependencies are referred to by their array name and the name associated with then. These files also contain the project group name that is specific to that chapter, additional plug-ins, and extra Gradle tasks. Here you can see the chapter08.gradle file: 832

5 APPENDIX A Setting Up Your Development Environment subprojects { group 'com.apress.prospring5.ch08' apply plugin: 'java' /*Task that copies all the dependencies under build/libs */ task copydependenciestype: Copy { from configurations.compile into 'build/libs' dependencies { if!project.name.contains"boot" { compile spring.contextsupport { exclude module: 'spring-context' exclude module: 'spring-beans' exclude module: 'spring-core' compile spring.orm, spring.context, misc.slf4jjcl, misc.logback, db.h2, misc.lang3, hibernate.em testcompile testing.junit The if (!project.name.contains("boot")) is necessary here because under project chapter08 one or more Spring Boot projects are nested, and as Spring Boot comes with its own fixed set of dependencies and versions for them, you do not want the configuration defined in this file to be inherited, which can lead to conflicts or unpredictable behavior. For projects on the third level, you can further customize the configurations inherited from the chapter** parent by adding their own dependencies and declaring their own manifest file specifications, their own plug-ins, and their own tasks. The following is a simple file called chapter12\spring-invoker\ build.gradle (if you want to check out a heavily customized Gradle configuration, check out the chapter08\jpa-criteria\build.gradle file): apply plugin: 'war' dependencies { compile project(':chapter12:base-remote') compile spring.webmvc, web.servlet testcompile spring.test war { archivename = 'remoting.war' manifest { attributes("created-by" : "Iuliana Cosmina", "Specification-Title": "Pro Spring 5", "Class-Path" : configurations.compile.collect { it.getname().join(' ')) 833

6 APPENDIX A Setting Up Your Development Environment Building and Troubleshooting After you clone the source code (or download it), you need to import the project in the IntelliJ IDEA editor. To do this, follow these steps: 1. Select from the Intellij IDEA menu File New Project from Existing Sources (as shown in Figure A-2). Figure A-2. Project import menu options in Intellij IDEA After selecting the proper option, a pop-up window will appear requesting the location of the project (as shown in Figure A-3). Figure A-3. Selecting the project root directory pop-up in Intellij IDEA Select the pro-spring-15 directory. A pop-up will ask for the project type. Intellij IDEA can create its own type of project from the selected sources and build it with its internal Java builder, but this option is not useful here because pro-spring-15 is a Gradle project.

7 APPENDIX A Setting Up Your Development Environment 3. Check the Import project from external model radio button and select Gradle from the menu, as depicted in Figure A-4. Figure A-4. Selecting the project type Intellij IDEA 4. The last pop-up window will appear and ask for the location of the build.gradle file and the Gradle executable. The options will be already populated for you (as shown in Figure A-5). If you have Gradle installed on the system, you might want to use it. Figure A-5. Last pop-up for project import in Intellij IDEA Before getting to work, you should build the project. This can be done from Intellij IDEA by clicking the Refresh button, as shown by the (1) in Figure A-6. Clicking this button will cause IntelliJ IDEA to scan the configuration of the project and resolve dependencies. This includes downloading missing libraries and doing an internal light build of the project (just enough to remove compile-time errors caused by missing dependencies). 835

8 APPENDIX A Setting Up Your Development Environment The Gradle compilejava task, marked with (3) in Figure A-6, executes a full build of the project. You can also do the same this from the command line, by executing the Gradle build command, as depicted below:.../workspace/pro-spring-15 $ gradle build Or you can do this from Intellij IDEA, by double clicking the build task, as depicted by the (2) in Figure A-6. Figure A-6. Last pop-up for project import in Intellij IDEA 836

9 APPENDIX A Setting Up Your Development Environment This will execute the following set of tasks on every module: :chapter02:hello-world:compilejava :chapter02:hello-world:processresources :chapter02:hello-world:classes :chapter02:hello-world:jar :chapter02:hello-world:assemble :chapter02:hello-world:compiletestjava :chapter02:hello-world:compiletestresources... In the previous example, the tasks were depicted only for module chapter02. The Gradle build task will execute all the tasks it depends on. As you can see, it does not run the clean task, so you need to make sure to run this task manually multiple times when building a project to make sure the most recent versions of the classes are used. Because this project contains tests that were designed to fail, executing this task will fail. You can instead just execute tasks clean and compilejava. Another option is to execute the Gradle build task, but to skip the tests using "-x" argument:.../workspace/pro-spring-15 $ gradle build -x test Deploy on Apache Tomcat There are a few web applications under the pro-spring-15 project. Most of them are Spring Boot applications that run on an embedded server. But there are certain advantages in using an external container like the Apache Tomcat server. Starting the server in debug mode and using breakpoints to debug an application is much easier to do, but that s only one advantage. An external container can run multiple applications at a time without the need to stop the server. Embedded servers are useful for testing, fast development, and educational purposes, like Spring Boot is, but in production, application servers are preferred. 837

10 APPENDIX A Setting Up Your Development Environment Here is what you have to do if you are interested in using an external server. First download the latest version of Apache Tomcat from the official site. 1 You can get version 8 or 9; they will both work with the sources of this book. Unpack the archive somewhere on your system. Then configure an IntelliJ IDEA launcher to start the server and deploy the chosen application. This is quite easy to do; follow these steps: 1. From the runnable configuration menu, choose Edit Configurations, as shown by (1) in Figure A-7. A pop-up window will appear and list a set of launchers. Click the plus (+) sign and select the Tomcat Server option. The menu will expand; select Local, as shown by (2) in Figure A-7, because you are using a server installed on your computer. Figure A-7. Menu options to create a Tomcat launcher in Intellij IDEA 2. A pop-up window like the one in Figure A-8 will appear and will request some information. 1 The Apache Tomcat official site is at 838

11 APPENDIX A Setting Up Your Development Environment Figure A-8. Pop-up to create a Tomcat launcher in Intellij IDEA In Figure A-8, you ll see that some items are numbered. Here is what the numbers mean: 1 is the launcher name. You can put anything here, preferably the name of the application you are deploying. 2 is the Tomcat instance name. 3 is the button that will open the pop-up window to insert the Tomcat instance location, as depicted in Figure A-9. Figure A-9. Configuring the Tomcat instance in Intellij IDEA 839

12 APPENDIX A Setting Up Your Development Environment 4 is the URL where the Tomcat server can be accessed. 5 is the Fix button, which is used to choose an artifact to deploy on the Tomcat instance. If there is no web archive set to be deployed to Tomcat, this button will be displayed with a red lightbulb icon on it. 3. Click the Fix button and select an artifact. IntelliJ IDEA will detect all artifacts available (Figure A-10) and present them to you in a list. If you intend to open the server in debug mode and use breakpoints in the code, select an artifact with the name postfixed with (exploded); this way, Intellij IDEA manages the contents of the exploded WAR and can link the actions in the browser with the breakpoints in the code. Figure A-10. Deployable artifact list in Intellij IDEA 4. Complete the configuration by clicking the OK button. You can specify a different application context by inserting a new value in the Application Context field. Choosing a different application context will tell Tomcat to deploy the application under the given name. The application will be accessible via this URL: Other application servers can be used in a similar way as long as IntelliJ IDEA provides plug-ins for them. Launcher configurations can be duplicated, and multiple Tomcat instances can be started at the same time as long as they function on different ports, which can make for faster testing and comparisons between implementations. IntelliJ IDEA is really flexible and practical, and that s why we recommend it for practicing the exercises in this book. The Gradle projects can also be imported in Eclipse and other Java editors that support Gradle. 840

13 Index A Advanced Message Queuing Protocol (AMQP) JMS, 606 rabbitlistenercontainerfactory, RabbitMQ, 608, 611 RPC calls, 608 Spring Boot, WeatherService, XML configuration, 609 After-returning advice KeyGenerator, SimpleAfterReturningAdvice, ApplicationContext interface ApplicationEvent, event usage, features, 167 getmessage(), 170 MessageSource, 168, 170 ApplicationContextAware interface, Application programming interfaces (APIs), 10 Around advice MethodInterceptor, 227 ProfilingDemo, ProfilingInterceptor, AspectJ AnnotationAdvice, aop namespace, 286 AOP configuration, 291 configuration, Java configuration, pointcut expression, 246 singleton aspects, Spring Boot, test methods, Aspect-oriented programming (AOP), 2, 10 advice types, 218 after-returning, around, before, throws, AgentDecorator, alliance, 214 aop namespace advice class, 278 configuration, 281 MethodBeforeAdvice, 278 MethodInterceptor, 282 pointcut, 283 simplebeforeadvice, 279 sing(), 280 declarative configuration, 271 definition, dynamic, 213 introductions (see IntroductionInterceptor) joinpoints, 216 OOP, 211 ProxyFactory class, 217 static, 213 AssertTrue, 534 Auditing strategies, B BatchSqlUpdate class insertwithalbum(), test method, Bean life-cycle management ApplicationContext, 130 default-init-method, 131 destruction, 139 initialization callback, 128 InitializingBean, init-method, interface mechanism, 127 JSR-250, post-initialization and pre-destruction, 127 Bean-managed transactions (BMTs), 467 Before advice SecureBean, 221, SecurityAdvice, Iuliana Cosmina, Rob Harrop, Chris Schaefer, and Clarence Ho 2017 I. Cosmina et al., Pro Spring 5, 841

14 INDEX Before advice (cont.) SecurityManager, SimpleBeforeAdvice, 219 sing(), 220 BookwormOracle class, 43 C Castor 586 field handler, mapping file, properties, 586 SingerController, Spring web application, CGLIB, ClassPathXmlApplicationContext, 34 Closure, 639, Container-managed transactions (CMTs), 467 Contextualized dependency lookup (CDL), curl command, D Data Access Object (DAO), 2 components, 317 JdbcSingerDao, service layer, 735 Spring Boot, Spring Security, web layer, Database connections. See DataSource Database operation. See Query data DataSource configuration, DAO (see Data Access Object (DAO)) DriverManagerDataSource, 310 embedded database, JNDI data source, 314 test class, DbUnit, DefaultPointcutAdvisor, 236 Dependency injection (DI) annotations, bean naming, AOP, 10 ApplicationContext, 48, 49 autowiring, BeanFactory Implementations, bean inheritance, bean instantiation mode, bean-naming structure, bean scope, 108 collection injection, components, 50 52, 54 configuration options, 49 constructor, 40 constructor injection, EL, 11 field injection, injecting beans, injecting simple values, injection and ApplicationContext nesting, injection parameters, 66 interface-based design, 8 Java 9, 10 JavaBeans (POJOs), 8 Java configuration, Lookup Method Injection, Method Injection, 84 Method Replacement, resolve dependencies, setter injection, 41, SpEL, XML configuration, 49 Destroy-method destructivebean, DisposableBean, GenericXmlApplicationContext, shutdown hook, 146 Development environment gradle configuration file, Intellij IDEA application, 838 deployable artifact, 840 pop-up window, 834, project import, project type, 835 Tomcat launcher, 838 project pro-spring-15, displayinfo() method, 78, 88 dosomething() method, 86 DyanmicMethodMatcherPointcut, Dynamic language code, 652, 654 E Enterprise integration patterns (EIP), 17 Enterprise JavaBeans (EJB), 2 EntityManagerFactory, 479 Entity Versioning. See Hibernate Envers Environment abstraction. See PropertySource abstraction Expression Language (EL),

15 INDEX F FactoryBeans accessing, 156 factory-method attributes, MessageDigester configuration, implementation, 152 issingleton() property, 153 Java configuration, 155 factory-method attributes, Field formatting ConversionServiceFactoryBean, custom formatter, Field injection, 41, formatmessage() method, 92 Front-end unit test, 637 G GenericXmlApplicationContext, 54, 88 getfriendlyname() method, 81 getmysinger() method, 86 Google Web Toolkit (GWT), 13 Groovy, closure, dynamic typing, 642 Spring age category rule, DSLs, dynamic language code, 652, 654 rule engine, rule factory, syntax, 643 H Hibernate Envers adding tables, auditing strategies, 452 EntityManagerFactory, history retrieval, properties, testing, Hibernate module AbstractEntity, annotating entity and fields, 390 configuration DatabasePopulator, 388 data source, DbIntializer, 389 entities, 386, 389 in-memory database, 388 data model, deleting data, 384, 386 inserting data, internal mechanism, 391 JCP, 355 mapping (see Object-relational mapping (ORM)) properties, SessionFactory, session interface (see Session interface) updating data, Hibernate Query Language (HQL), 372 I InitializingBean afterpropertiesset(), 138 init-method, Integration test configuration class, dependencies, 623 infrastructure classes, 627 Java configuration, service-layer testing, TestExecutionListener, IntelliJ IDEA, 831 Interface-based design evolution, 8 9 IntroductionInterceptor Advisor, Contact, 264 interface structure, 264 IsModified, 266 mixin, object modification detection, per-instance, PointcutAdvisor, 264 Inversion of control (IoC), 1 capabilities bean life cycle, 125 configuration enhancements, 126 FactoryBeans, 125 Groovy, 126 JavaBeans PropertyEditors, 125 Java classes, 126 portability, Spring ApplicationContext, 126 Spring aware, 125 Spring Boot, 126 CDL, dependency injection, 45 dependency pull, 38 injection vs. lookup, setter injection vs. constructor injection, IsModified interface,

16 INDEX J Java 9, 10 interoperability, 774, 811 reactive programming with, support for, 10 Java classes ApplicationContext AppConfigOne, MessageRenderer, StandardOutMessageRenderer, static internal class, XML configuration, Spring mixed configuration, Java Community Process (JCP), 8 Java Database Connectivity (JDBC), 2 extensions, 350 generated key, implementation, 297 lambda expression, 329 MySQL, 305 ORM, 350 PlainSingerDao, 307 relational database, 297 simple data model database, 300 DEBUG level, 303, 304 entities, entity-relationship, 298 MySQL, 299 resources, 299 SingerDao, Spring Boot, used packages, Java Data Objects (JDO), 2, 355 Java Development Kit (JDK), 21 proxies, 250 Java Enterprise Edition (JEE), 1 Java Management Extensions (JMX) monitoring hibernate statistics, JEE applications, 655 managed beans, 655 Spring bean, Spring Boot, , 664 VisualVM, Java Message Service (JMS) configuration classes, Gradle configurations, 570 HornetQ, queue, 570 sending messages, topic, 570 Java Persistence API (JPA), 355 criteria API CriteriaBuilder, 426 CriteriaQuery.from(), 426 CriteriaQuery.select(), 426 execution, 428 findbycriteriaquery(), meta-model class, predicate, 426 Root.fetch(), 426 testing, 427 Spring Boot adding dependencies, configuration, DBInitializer, InstrumentRepository, run(), 465 SingerRepository, Java Runtime Environment (JRE), 21 Java Standard Tag Library (JSTL), 13 Java Transaction API (JTA) transactions configuration, 491, EntityManagerFactory, 494 findall(), 498 infrastructure, 491 principle, 507 rollback, save(), ServicesConfig, 494, 496 Spring Boot, 501, testing, 499 UserTransactionService, 496 Java Transaction Service (JTS), 469 Java virtual machine (JVM), 21 JdbcTemplate class DAO class, DAO implementation, 331 datasource, 332 JSR-250 annotation, 331 named parameters, 324 RowMapper<T>, JEE 7 container 7, 18 JPA 2.1 component scan, 398 datasource bean, 398 EntityManagerFactory, native queries, ORM mapping, 398, 400 query data createquery(), deleting data, findall(), 404 findallwithalbum(), 406,

17 INDEX findbyid(), 409 getsingleresult(), 409 inserting data, SingerService, SingerSummary, testfindall(), 406 testfindallwithalbum(), 408 TypedQuery.getResultList(), 405 untyped results, updating data, transactionmanager bean, 398 JpaRepository, 436 jquery and jquery UI CKEditor, jqgrid, pagination SingerController, SingerGrid, SingerService, 718 view, JSR-352, JSR-250 annotations, JSR-330 annotations, 201 MessageProvider and ConfigurableMessageProvider, 198 MessageRenderer and StandardOutMessageRenderer, 199 JSR-349 bean validation, 527 K KeyHelper instance, 85 L Logic unit tests create(), dependencies, 619 listdata(), MVC controllers, 620 M Many-to-many mappings, MappingSqlQuery<T> SelectAllSingers, setdatasource(), SqlUpdate, test method, Message-oriented middleware (MOM), 606 MessageSourceResolvable interface, 171 Mixin, Model-View-Controller (MVC), 2, N Native queries create and execute, 421 SQL ResultSet mapping findallbynativequery(), 421 NewsletterSender interface, 44 O Object modification detection, Object-relational mapping 364 data model, 364 JPA annotations, 398, 400 libraries, 355 many-to-many mappings, one-to-many mappings, simple mapping, 364 Album class, Singer class, Object/XML Mapping (OXM), 12, 23 One-to-many mappings, P performlookup(), 40 PicoContainer, 17 PlatformTransactionManager, Pointcuts Advisors and, AnnotationMatching Pointcut, AspectJ s pointcut expression, 246 ClassFilter, 234 composable, control flow, DefaultPointcutAdvisor, 236 DyanmicMethodMatcher Pointcut, implementations, name matching, ProxyFactory, 233 regular expressions, StaticMethodMatcherPointcut, Project object model (POM), 20, 362 PropertyEditor configuration, custom, 164, implementations, spring-beans, String,

18 INDEX PropertySource abstraction ApplicationContext, 193 AppProperty, 196 MutablePropertySources, 195 ProxyFactoryBean class ApplicationContext, 274 configuration, implementation, introductions, ProxyFactory class CGLIB, JDK, 250 performance, testing, 255 Q Query data createquery(), deleting data, findall(), 404 findallwithalbum(), 406, 408 inserting data, SingerService, SingerSummary, testfindall(), 406 testfindallwithalbum(), TypedQuery.getResultList(), 405, 406 updating data, R RabbitMQ connection, 608 Refreshable beans, 648 Remoting support AMQP (see Advanced Message Queuing Protocol (AMQP)) ContactService configuration, HttpInvokerConfig, 567 SingerService, Spring HTTP invoker, data model, dependencies, RESTful-WS curl, dependencies, 580 manipulating resources, 580 RestTemplate, Spring Boot, Spring MVC, Spring security, XMLHttpRequest and properties, 581 RestTemplate class, ResultSetExtractor interface findallwithalbums(), lambda expressions, 329 test class, Rich Internet applications (RIAs), 13 S Scripting support Groovy (see Groovy) in Java, Selenium, 638 Service layer DAO, 670 data model, SingerService, Session interface querying associations fetching, HQL, 372 lazy fetching, SingerDaoImpl class, 371 setdependency() method, 41 setoracle() method, 74 Simple (or Streaming) Text-Oriented Message Protocol (STOMP) MVC controller, , 769 stock-ticker application, WebConfig, Spring community, 15 Context, 2 data access, 12 description, 1 dynamic scripting support, 14 GitHub, 20 Google Guice, 17 guides, 19 inversion of control, 1 JAR files, 19 Java developers, 1 JBoss Seam Framework, 17 JDK, 21 JEE, 13 JEE 7, 18 job scheduling support, 14 mail support, 14 MVC, web tier, 13 object/xml mapping, 12 origins of spring, 15 packaging options, 19 PicoContainer, 17 remoting support,

19 INDEX simplified exception handling, 15 Spring 0.9, 2 Spring Batch and integration, 17 Spring Boot, 16 Spring Core, 2 Spring GitHub repository, 20 Spring Security project, 16 Spring 1.x, 2 Spring 2.x, 2 Spring 2.5.x, 3 4 Spring 3.0.x, 4 Spring 3.1.x, 5 Spring 3.2.x, 5 Spring 4.0.x, 6 Spring 4.2.x, 6 7 Spring 4.3.x, 7 Spring 5.0.x, 7 STS, 16 test suite and documentation, 19 transaction management, 13 validation, 11 WebSocket support, 14 Spring aware ApplicationContext, 147 BeanNameAware, Spring Batch chunk-oriented processing, 774 configuration, DataSourceConfig, Gradle configuration, ItemProcessor, JSR-352 (see JSR-352) scaling and parallel processing, 775 Spring Boot, 16, ApplicationContext, 206 Artemis, configurations, 205 Gradle Projects, 205, opinionated approach, 204 RESTful-WS, Spring Data JPA custom queries AuditorAwareBean, 444, 437 SINGER_AUDIT, SingerAuditRepository, 447 SingerAuditService, testing, 439, library dependencies, 429 repository abstraction, Spring Expression Language (SpEL), 4, Spring Framework features, 798 functional web framework content-type text/ event-stream, 809 handler function, repository implementation, REST controller, RouterFunctions, 807 types of data streams, 799 WebFlux, Java 9, 811 WebFlux, Spring Integration configuration, JUnit 5 FluxGenerator, TestEngine, WebTestClient, Message, Spring modules application, 24 ApplicationContext configuration, 32 configuration classes, getbean() method, 33 Gradle, 26 Hello World application, JAR files, ListableBeanFactory, 31 Maven repository, MessageProvider interface, 32 MessageRenderer interface, 28, 31 spring-context.jar, 33 spring documentation, 26 StandardOutMessageRenderer, Spring MVC configuration, DispatcherServlet, file upload support configuration, modifying controllers, modifying views, folder structure, 686 life cycle, list view, SingerController, Tiles, view, WebApplicationContext, Spring profiles FoodProviderService, Java configuration, Spring Security,

20 INDEX configuration, login functions, project, 16 secure controller methods, 731 Spring testing annotations, 618 categories, DbUnit, front-end unit test, 637 integration test configuration class, dependencies, 623 infrastructure classes, 627 Java configuration, service-layer testing, TestExecutionListener, logic unit tests create(), dependencies, 619 listdata(), MVC Controllers, 620 unit test, service layer, Spring Tool Suite (STS), 16 Spring transaction abstraction layer, Spring type conversion arbitrary types, ConversionService, configure, custom converter, PropertyEditors, Spring XD, SQLException class, SqlFunction class, StandardLookupDemoBean class, 89 StaticMethodMatcherPointcut class, T Task Scheduling annotation, AppConfig, 546 asynchronous task execution, CarService, 544 CrusRepository, 543 DBInitializer, dependencies, execution, JPA entity, TaskExecutor, task-namespace, 545 TaskScheduler abstraction, 539 trigger, task, and scheduler, 539 Theming and templating, Throws advice, Thymeleaf extensions, fragments, Spring Boot, Webjars, Transaction management AOP configuration, data model classes, , 480 countall(), 485 findall(), 482 findbyid(), 484 save(), 483 Spring JPA project, 473 annotation, declarative approach, 490 global transactions JTA transactions (see Java Transaction API (JTA) transactions) PlatformTransactionManager, programmatic transactions, Spring transaction abstraction layer, TransactionDefinition interface, TransactionStatus interface, U Unit test, service layer, UnsatisfiedDependencyException, 116 V Validation, Spring AssertTrue, 534 bean validation, custom validator, dependencies, 510 JSR-349, 527, 535 object properties, Spring validator interface, testing, W, X, Y, Z Web applications DAO (see Data Access Object (DAO)) i18n configuration, List View, JSR-349, requirements, 665 service layer, 735 SingerService, singer view 848

21 INDEX adding, 708 edit, show(), Spring Boot, Thymeleaf views (see Thymeleaf) URLs views, 699 view templating, WebSocket API front-end application, Java configuration, 753 SockJS, Spring MVC, TextWebSocketHandler, 757 WebSocketConfigurer, STOMP,