You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were using object-client 3.3.2 in a inhouse custom web application
Recently we upgraded the app framework to spring boot 2.7, which indirectly brings the upgrade of jackson 2.13
The jackson upgrade broke all functionalities of object-client due to the missing class javax/ws/rs/core/NoContentException (only appears jaxrs v2)
I notice that there is a commit to downgrading the jackson dependencies to 2.12 33f7674
The root cause of both issues are due to the fact that the object-client is still using jaxrs (Jersey) v1
Any roadmap or migration plan for upgrading to jaxrs / Jersey v2?
The text was updated successfully, but these errors were encountered:
@neowcng@code4t2@eljakimlindenburg Hello, object client version 4.0.0-rc.1, with Jersey 2.40, is for your Alpha Testing. Feel free to let us know if any issues are remaining from your side. Please note that it is not recommended to use it on any production environment. We will soon have a GA release.
Greetings
We were using object-client 3.3.2 in a inhouse custom web application
Recently we upgraded the app framework to spring boot 2.7, which indirectly brings the upgrade of jackson 2.13
The jackson upgrade broke all functionalities of object-client due to the missing class javax/ws/rs/core/NoContentException (only appears jaxrs v2)
I notice that there is a commit to downgrading the jackson dependencies to 2.12
33f7674
The root cause of both issues are due to the fact that the object-client is still using jaxrs (Jersey) v1
Any roadmap or migration plan for upgrading to jaxrs / Jersey v2?
The text was updated successfully, but these errors were encountered: