Win a copy of Beginning Java 17 Fundamentals: Object-Oriented Programming in Java 17 this week in the Java in General forum!

Adam L Davis

+ Follow
since Sep 24, 2019
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Adam L Davis

It's a very large book and covers a lot. Problem solving is not mentioned directly but fundamentals of Java are covered including why certain features even exist.
21 hours ago
I agree that modules could be the biggest, but maybe it's record. The introduction of record is a huge change to the language as it sits next to class and interface as a fundamental type of thing. This book does cover modules and has a very large chapter on it.
21 hours ago
Hi! It's not specific to passing the exam but it has many topics that would help you pass.
21 hours ago
Yes it covers testing specific to Spring as well. It covers Spring Boot Testing and Reactor's built-in classes for testing support.
7 months ago
The code is available to download: Spring Quick Reference Guide
7 months ago
Spring Boot should work great with WebClient. The makers of Spring actually suggest everyone use WebClient going forward instead of RestTemplate.

However, it requires a shift in your mental model to understand how reactive works (Mono is a reactive type, and part of project Reactor) - the book covers Reactor and WebFlux including WebClient.

Calling .block() should only block until the Mono produces an output value. Without seeing the code I can't give much more than that.
7 months ago
Yes this book does attempt to say when each project/module should be used. The covered modules are described in the list of chapters.
7 months ago
Good question. It is really big and I didn't cover every single Spring project. My goal was to cover what I think are some of the best projects and most useful.

No I don't expect the reader to already know Spring. The first chapter is on dependency injection. However, this book strives to be so comprehensive that even seasoned developers should get something out of it. I myself have gone back to reference it many times.
7 months ago
Hi, Thanks for the question.

I'm not sure which challenges you are referring to. In my experience the biggest challenge is understanding all of the features Spring brings to a project, and how to use them to your advantage without seeming too "magical" - you can do this much easier if you are have the complete picture of how Spring works, and are not just copy pasting things from the internet. Also make sure you have a really good reason for each library or framework you use.

The source code that comes with the book has over a dozen working example projects that demonstrate how to use each Spring project that is covered, such as Spring AOP, Spring Batch, Reactor, Spring Data JPA, Spring Mobile, and others.

7 months ago
Yes, this book does not assume any previous knowledge of Spring, although you should at least have a good background in Java.

This book is about Spring framework, not just Spring Boot, although it also covers Spring Boot.
7 months ago
Great question. The main factor I thought about was what someone would need to know to write a web service from scratch using the Spring framework.

You should take away from it the knowledge of how to build a web service or microservice, and as the name implies a book to reference back to many times.
7 months ago
No. This book is mostly for beginners to programming.
1 year ago
Hi Brett,

It really depends on what you enjoy doing most. Do you enjoy back-end server development or batch jobs? Then I would recommend getting back into Java. There are a lot of great books out there and freely available websites. The Spring framework seems to be extremely popular so I recommend learning about it.

If you prefer front end (browser) development, then I recommend learning the latest JavaScript and React for the front-end (codecademy has a good course). The problem with that is JavaScript shares very little with Java - some surface level syntax but that's it. Another point it seems like a lot of energy/popularity is going into JavaScript right now.

I highly recommend using IntelliJ IDEA if you do go back into Java. It has great automatic suggestions for how to update your Java code to more recent standards.

Wish I had a better answer.

Good Luck,

1 year ago

Good question. It doesn't go too much into that. That's a highly subjective topic though. JavaScript for example could be used in both the front-end (browser) and back-end (using Node.js)

Groovy can be useful in many contexts although it's most traction seems to be in Gradle builds, scripting, and the Jenkins build DSL. You could build everything in Groovy, including the front-end with grooscript.
1 year ago