BAEL-9185: Introduction to Solon - #19314
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the approved
solon-introductionmodule for BAEL-9185. The example starts with a greeting endpoint and builds a task REST API with Solon 4.1.0, MyBatis-Flex 1.11.8, HikariCP 7.1.0, and H2 2.5.250.The module targets Java 21 and participates in the repository's
defaultandintegrationprofiles. It inheritscom.baeldung:parent-modulesand importssolon-parentas a BOM. Unit/integration test selection uses the shared parent's standard filters; there is no customtest.includesproperty. Compiler parameter metadata is retained for HTTP binding. JUnit 5.14.4, the test-scoped Platform launcher 1.14.4, and Surefire 3.5.5 are aligned to avoid test discovery failures.Tests cover service validation, the CRUD lifecycle over real HTTP, invalid input, missing resources, and transaction rollback verified before cleanup. Integration tests allocate an available port and use a separate in-memory database. The public integration test class and public rollback method are required by Solon's test extension and proxy interception.
Validation with Temurin 21.0.12.1+1 and Maven 3.9.16:
mvn -B -ntp -f solon-introduction/pom.xml -Pdefault clean install: 7 unit tests passedmvn -B -ntp -pl solon-introduction -Pintegration clean install: 5 integration tests passed, including actual HTTP startup and requestsgit diff --check: passedJava application/test sources required no changes for this build alignment. The redundant usage README was removed; the article explains execution and testing. The diagram's DOT source and regeneration instructions remain in
diagrams/info.txt, preserving the author's subsequent cleanup commits.