https://github.com/codesmell/camelmigrationjavaconfig
Migrate a small Camel 2.x application to Camel 3.x (Camel Java-Config)
https://github.com/codesmell/camelmigrationjavaconfig
apache-camel java migration spring spring-boot springboot
Last synced: 11 months ago
JSON representation
Migrate a small Camel 2.x application to Camel 3.x (Camel Java-Config)
- Host: GitHub
- URL: https://github.com/codesmell/camelmigrationjavaconfig
- Owner: CodeSmell
- Created: 2022-07-07T19:53:31.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2022-08-09T13:01:11.000Z (over 3 years ago)
- Last Synced: 2025-02-16T09:20:24.578Z (about 1 year ago)
- Topics: apache-camel, java, migration, spring, spring-boot, springboot
- Language: Java
- Homepage:
- Size: 214 KB
- Stars: 1
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: ChangeTheJDK.png
Awesome Lists containing this project
README
# Camel Migration
Exploring how to migrate a small Camel 2.x application to Camel 3.x
**For details on each phase see the GitHub wiki**
Camel is a very flexible framework that is designed around [Enterprise Integration Patterns (EIP)](https://www.enterpriseintegrationpatterns.com/).
The transition from the 2.x to 3.x represents a major and non-backward compatible change. The 3.0.0 release came out in November 2019.
This repo will explore how to use the various Camel migrations guides to migrate from Camel 2.x to Camel 3.x using a small application.
The application will be built using the Spring Java-Config capability to configure the `CamelContext`.
This expects a configuration class to extend the `CamelConfiguration` which will allow configuration of Camel context.
The starting point:
- a small Camel 2.x application
- using Spring 5.x
- using JDK 8
The goal:
- a small Camel 3.x application
- using Spring 5.x
- using JDK 17
This application will consume EDI X12 messages from a directory and write them to a directory as JSON
(using [the Gozer parser](https://github.com/walmartlabs/gozer) and object model).
## Camel LTS releases
With 3.x Camel [moved to an LTS model like the JDK](https://camel.apache.org/blog/2020/03/LTS-Release-Schedule/).
The LTS versions will be supported for 1 year, be more stable and will not get new features.
The non-LTS versions will not have patch releases and will feature more innovations.
The LTS versions:
- 3.4.0 (EOL in June 2021)
- 3.7.0 (EOL in Dec 2021)
- 3.11.0 (EOL in June 2022)
- 3.14.0 (EOL in Dec 2022)
- 3.18.0 (EOL in July 2023)
Some major changes start with the non-LTS release of Camel 3.15.0
- [removes support for JDK 8](https://camel.apache.org/releases/release-3.15.0/)
- [removes support for spring-java-config](https://issues.apache.org/jira/browse/CAMEL-17354)
In addition, Camel 3.17 (non-LTS) will support JDK 17 as well as JDK 11
# The Migration Plan
- (**Starting point**) A Camel 2.24.x application
- (**Phase 1**) Migrate the Camel application from 2.24.x to Camel 3.14.x.
- this moves the application to the current LTS (prior to major changes in 3.15)
- it holds off on dealing with the JDK and Java-Config changes
- (**Phase 2**) Migrate the application from 3.14.0 to Camel 3.18.0
- move to the latest LTS
- move to JDK 17
- evaluate options with Java-Config removal
- (**Phase 3**) Migrate the testing in the application from jUnit 4 to jUnit 5
- remove need for deprecated Camel testing
- (**Phase 4**) Migrate the application to use Spring Boot
- replace Camel Main w/ Spring Boot
**For details on each phase see the GitHub wiki**