Support SpringBoot 3 with `jakarta` api

[UkonnRa]

Currently crnk-setup-servlet are heavily based on javax.servlet api so it's not compatible with jakarta api at all. All the servlet filters are failed in Spring Boot 3.

So any plan so migrate to the new jakarta API? I tried a little bit, but it seems to reweite all the crnk-setup-servlet and crnk-setup-spring-boot2 modules, which is too redundant for users.

So hope the maintainer can add the support on the code side.

[MrTomato]

second that request!

[InNeedOfStreetCred]

Without support for Spring Boot3 this will be very quickly abandonware.

[remmeier]

PRs are welcomed InNeedOfStreetCred ***@***.***> schrieb am Do., 22. Dez. 2022, 12:13:

…

Without support for Spring Boot3 this will be very quickly abandonware. — Reply to this email directly, view it on GitHub <#869 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5DJFJ3IAJKFD4FNILEWFTWOQZV5ANCNFSM6AAAAAAS27G6HY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[kdejaeger]

I would like to stick with this library as well. I don't find the other alternatives mentioned on https://jsonapi.org/implementations/#client-libraries-java better. It's sad to see this one perish. But I understand if you don't have time @remmeier . Life is changing all the time right.

[ruzkant]

I am new to CRNK and haven't delved into spring boot 3 yet, but planning to in the coming months. How much guidance would you be able to provide for something like this.

The servlet aspect looks straightforward. I imagine one only needs to duplicate the crnk-setup-servlet module and change the package names and fix small issues.

I am not sure how much of the crnk-setup-spring-boot2 module would be reusable but that code base is more sizable.

The bigger issue is probably the java 17 baseline. It seems to me crnk would have to create a new major version and maintain both streams the way spring did. This could escalate the development to other modules of CRNK, depending on how much breaks compiling in 17. [Edit] I guess a start would be to just compile the spring-boot3 module in 17. Rough thoughts.

@remmeier Do you have any thoughts on this and how a PR could work? How much guidance are you able to provide?

[remmeier]

a new major version seems good to me. upgrade everything to the latest versions and new packages. in the past we have been more careful at maintaining backwards compatibility. but with javaee/jakarta/... many things change. everything else would be too much effort. a simple upgrade would be quick to do

[przeemek]

Happy to help as well with the migration.

[dennisvonk]

For our project we want to have the SpringBoot v3 dependency, so I created a fork and want to have a go at it.
If anyone has pointers, specific things to take into account, please let me know.
And some reviewers later on when it is ready to merge back would also be appreciated.

[whgibbo]

Is there a branch for the Java17 / Spring Framework 6.x / Spring Boot 3.x work .
As would like to contribute if I can

[dennisvonk]

Nice that you want to help. As priorities at my assignment have changed, I haven't done anything to this fork.
I have send you an invitation.

[whgibbo]

Nice that you want to help. As priorities at my assignment have changed, I haven't done anything to this fork. I have send you an invitation.

So which branch should I look at ?

[dennisvonk]

sorry for the late reply, I had a short holiday.
There is no work done yet, only a fork of the original master branche is made. So any work you do can be done in your own branch.

[Yosuva]

Currently I am trying to migrate spring boot 3. My crnk API application is returning 404 message after upgrading spring boot 3. Do anyone have idea about this issue? or will Crnk support spring boot 3 ?

[whgibbo]

@remmeier / @dennisvonk so any plans / list of tasks as would like to help if I can.
I can think of the following:

1. Java 8 -> Java 17 (due to spring boot / framework min supported) Change Gradle version from 6 - > 7.3/8.3
2. Change Gradle version from 6 - > 8.2.1 ? Java 8 -> Java 17 (due to spring boot / framework min supported)
3. Update spring packages to version 3.x
4. update the servlet code from javax -> jakarta
5. review 3rd party libraries and update as required.

reference links

• https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.0-Migration-Guide
• https://www.baeldung.com/spring-boot-3-migration
• https://docs.gradle.org/current/userguide/compatibility.html
• https://docs.gradle.org/current/userguide/upgrading_version_6.html
• https://docs.gradle.org/current/userguide/upgrading_version_7.html
• https://docs.gradle.org/current/userguide/upgrading_version_8.html

[dennisvonk]

Hi whgibbo, that looks like a good plan. Step 2 might not be needed, but other steps I totally agree with. As you can see, not a lot has changed, which has to do with the amount of work on my day-job. Hopefully you and others can pickup these tasks. Dennis Vonk Op za 12 aug 2023 om 22:25 schreef whgibbo ***@***.***>:

…

@remmeier <https://github.com/remmeier> / @dennisvonk <https://github.com/dennisvonk> so any plans / list of tasks as would like to help if I can. I can think of the following: 1. Java 8 -> Java 17 (due to spring boot / framework min supported) 2. Change Gradle version from 6 - > 8.2.1 ? 3. Update spring packages to version 3.x 4. update the servlet code from javax -> jakarta 5. review 3rd party libraries and update as required. reference links - https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.0-Migration-Guide - https://www.baeldung.com/spring-boot-3-migration — Reply to this email directly, view it on GitHub <#869 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHZXH5VWITEQHFCKAYNDDHLXU7RE3ANCNFSM6AAAAAAS27G6HY> . You are receiving this because you were mentioned.Message ID: ***@***.***>