Spring boot - is a Java framework, which claims to retrieve the default configurations from the libraries loaded to the path.

Logging the exposed endpoints. To log the exposed endpoints the change in the application.properties is required:

application.properties

logging.level.web=TRACE
logging.level.org.springframework.web=TRACE

Example output

12:14:48.398 [main] TRACE o.s.w.s.m.m.a.RequestMappingHandlerMapping  
	i.d.l.d.g.RestGroupController:
	{GET [/rest/, /rest/groups]}: index(String,Optional)
	{POST /rest/groups, consumes [application/json]}: createGroup(Group)
	{POST /rest/groups/{groupId}/member}: addUserToGroup(String,String)
	{DELETE /rest/groups, consumes [application/json]}: deleteRole(String)
	{GET [/rest/, /rest/groups/member/{memberId}]}: groupsByMember(String)
	{GET [/rest/, /rest/groups/{id}]}: groupById(String)
	{DELETE /rest/groups/{groupId}/member}: removeUserFromGroup(String,String)
12:14:48.418 [main] TRACE o.s.w.s.m.m.a.RequestMappingHandlerMapping  
	i.d.l.d.r.RestRoleController:
	{GET [/rest/, /rest/roles]}: index(String,Optional)
	{POST /rest/roles/{roleId}/member}: addMemberToRole(String,String,String)
	{DELETE /rest/roles, consumes [application/json]}: deleteRole(String)
	{POST /rest/roles, consumes [application/json]}: createRole(Role)
	{DELETE /rest/roles/{roleId}/member}: removeUserFromRole(String,String,String)

Use Spring Initializr to generate a new project.

Import it to the Idea IDE via:

Spring boot is normally either

• packaged to an executable jar, together with dependencies, or
• packaged as a deployable war, so that it may be deployed to a Tomcat etc.

Running the app with gradle, choosing the port

./gradlew bootRun --args='--server.port=8888'

To create a Jar with gradle - add the following to build.gradle

to automagically resolve dependencies within the current spring boot version - you must apply a special plugin.
The dependencies will be resolved acording to the BOM - bill of materials.
Check https://docs.spring.io/spring-boot/docs/2.0.0.RELEASE/gradle-plugin/reference/html/#packaging-executable-jars

apply plugin: 'io.spring.dependency-management'

Build the jar by using gradlew.
This will produce a JAR e.g. under build\libs\PROJECTNAME\complete.jar

../../gradlew BootJar

Start the jar

java -jar complete.jar

build.gradle

apply plugin: 'io.spring.dependency-management'
apply plugin: 'war'

Build the jar by using gradlew.
This will produce a JAR e.g. under build\libs\PROJECTNAME\complete.war

../../gradlew BootWar

Spring profiles can be activated in multiple ways, e.g.

by setting the environment variable

export spring_profiles_active=dev

by passing an argument to the java virtual machine

-Dspring.profiles.active=dev

When activated - you get the option to create a profile dependant properties files.

• .properties files are located in /resources/application-{profile}.properties
  • ./resources/application-dev.properties
  • ./resources/application-stage.properties
  • ./resources/application-prod.properties *
• ./resources/application.properties - is the default file, which is active
• .properties files are additive

To pick a default profile - you need to set in in applicaiton.properties

application.properties

# the default profile which is used. Can be overridden by specifying the Spring profile as -Dspring.profiles.active or in another way.
# without that the "spring.profiles.active" will not fall back to the value "default"
spring.profiles.active=dev

Spring boot applications - can be configured to - react on file changes - rebuild the application e.g. to a jar - redeploy the jar, e.g. to the ThomCat

Add dev-tools to the dependencies, so that the rebuilt app is hot-swaped on the app server.

In build.gradle

dependencies {

	// makes Spring boot hot swap rebuilt jar to tomcat
	developmentOnly 'org.springframework.boot:spring-boot-devtools'
}

In a separate terminal, start the continuous build of application.

Do that in a separate terminal, because the command doesn't come back, but listens for file changes.

It works in Vagrant, in a Ubuntu guest-VM, on host-Windows, on a “shared-folder”.<br> But unfortunately, changes, originating form vagrant-host-machine - are NOT recognized.<br> To trigger rebuild, hot-swap - one needs to change some file in the vagrant-guest-machine.

Starts continuos build skipping the tests

./gradlew build -xtest --continuous

To propagate a change triggering a rebuild - you need to modify the file on the guest-system

echo "" >> HelloController.java

The app will be built and propagated

./gradlew bootRun --args='--server.port=8888'

# Prerequisites

Install java

# java open GraalVM from liberica "native image kit"
sdk install java 22.3.r17-nik < /dev/null

# switch
sdk use java 22.3.r17-nik

# set the Java_home
source "~/.sdkman/bin/sdkman-init.sh"

# Quickstart

Build a native image

./gradlew nativeCompile

[native-image-plugin] Native Image written to: /PROJECTDIR/throttling-enforcer/build/native/nativeCompile

Run

/PROJECTDIR/throttling-enforcer/build/native/nativeCompile/demo

CRUD repositories CrudRepository<Entity, Id>

can create queries by convention.

Just name the methods according to the convention https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#jpa.query-methods.query-creation and they will be mapped to queries.