[
https://issues.apache.org/jira/browse/KARAF-7668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832003#comment-17832003
]
Piotr Klimczak edited comment on KARAF-7668 at 3/29/24 12:26 AM:
-----------------------------------------------------------------
Thanks for your answer [~jbonofre]
We can’t justify migrating ~200 integrations to blueprint, not to mention
trainings, change of practices, rewriting integration tests etc.
Unfortunately we would rather stop using karaf than migrate everything to
blueprint- this also reason why we were implementing Came Spring support
ourselves including in latest Karaf releases.
I wouldn’t be surprise if there would be more people with similar views.
Especially those who developed many of their services in times of
ServiceMix/Fuse source/RedHat Fuse (up to 6.x)
Shame as otherwise Karaf is amazing app container.
Always loved it and always will 😌
was (Author: nannou9):
Thanks for your answer [~jbonofre]
We can’t justify migrating ~200 integrations to blueprint, not to mention
trainings, change of practices, rewriting integration tests etc.
Unfortunately we would rather stop using karaf than migrate everything to
blueprint- this also reason why we were implementing Came Spring support
ourselves including in latest Karaf releases.
I wouldn’t be surprise if there would be more people with similar views.
Especially those who developed many of their services in times of
ServiceMix/Fuse source/RedHat Fuse (up to 6.x)
> Reintroduce Karaf Spring support like with Spring 3/DM (we have it working
> for 4.2, 4.3 and 4.4 Karaf)
> ------------------------------------------------------------------------------------------------------
>
> Key: KARAF-7668
> URL: https://issues.apache.org/jira/browse/KARAF-7668
> Project: Karaf
> Issue Type: Wish
> Components: karaf
> Affects Versions: 4.4.3
> Reporter: Piotr Klimczak
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> 1st of all, massive thanks to all Karaf devs for keeping it going and getting
> better.
> Back to subject, official Spring support has been dropped due to Spring
> community dropping Spring-DM.
> The Spring itself actually still works in OSGi environment via Blueprint
> Spring bridge (which is part of Aries project).
> We have it working with latest Spring 5 in production for years now with
> Karaf 4.2, 4.3 and now migrating to latest 4.4 with Apache CXF, AMQ and Camel
> (~200 integrations).
> In practice we have Spring 3/Spring-DM like behaviour, which is just few PRs
> away to get it supported in Karaf out of the box.
> I have started creating some Jiras and PRs in this direction over year ago.
> Sadly there is not even a comment in Jira nor PR: ARIES-2045 and ARIES-2046.
> Is it possible to open discussion somehow on this subject?
> Reality is that there are still people using old Karaf/Fuse, who do not
> upgrade because they want to stay on Spring. Currently there is no way out
> for them other than migrate away completely from Karaf if they are not keen
> on Blueprint (like I am).
> WDYT guys?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
