[
https://issues.apache.org/jira/browse/CAMEL-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687103#comment-17687103
]
Piotr Klimczak edited comment on CAMEL-19024 at 2/10/23 2:53 PM:
-----------------------------------------------------------------
Thanks [~jbonofre] for your update, it is very helpful.
[~davsclaus] basing on above answer I think it would make sense to reopen this-
hope you don't mind.
TBH I was considering reopening it anyway (or creating new jira) since all
above spring projects define osgi imports and there are some mistakes there too.
I appreciate that Spring+Karaf support might not be your main focus, but since
those modules has some level of OSGi support, it sounds sensible to keep it
there and fix it.
I will be more than happy to provide PR with fixes as we make those fixes
anyway.
Just give us few more days to finish testing and submit some PR which fixes all
issues- like said we have approx 200 Karaf + Camel + Spring integrations, so we
should be able to come up with nice test sample for this functionality and all
fixes needed.
Also just to keep us on the same page:
In vanilla Karaf indeed there is Blueprint Spring project which is responsible
for discovering Spring contexts in META-INF.
Then there is Blueprint Spring Extender which serves same purpose like Spring
DM.
>From that perspective Karaf does support Spring.
[~jbonofre] or do you mean some other way of using Spring context?
Thanks both for your contribution so far.
Really appreciated.
was (Author: nannou9):
Thanks [~jbonofre] for your update, it is very helpful.
[~davsclaus] basing on above answer I think it would make sense to reopen this-
hope you don't mind.
TBH I was considering reopening it anyway (or creating new jira) since all
above spring projects define osgi imports and there are some mistakes there too.
I appreciate that Spring+Karaf support might not be your main focus, but since
those modules has some level of OSGi support, it sounds sensible to keep it
there and fix it.
I will be more than happy to provide PR with fixes as we make those fixes
anyway.
Just give us few more days to finish testing and submit some PR which fixes all
issues- like said we have approx 200 Karaf + Camel + Spring integrations, so we
should be able to come up with nice test sample for this functionality and all
fixes needed.
Also but of explanation:
In vanilla Karaf indeed there is Blueprint Spring project which is responsible
for discovering Spring contexts in META-INF.
Then there is Blueprint Spring Extender which serves same purpose like Spring
DM.
>From that perspective Karaf does support Spring.
[~jbonofre] or do you mean some other way of using Spring context?
Thanks both for your contribution so far.
Really appreciated.
> Camel Karaf Features missing camel-cxf-spring-*
> -----------------------------------------------
>
> Key: CAMEL-19024
> URL: https://issues.apache.org/jira/browse/CAMEL-19024
> Project: Camel
> Issue Type: Bug
> Components: karaf
> Affects Versions: 3.20.2
> Reporter: Piotr Klimczak
> Priority: Major
>
> 1st of all wanted to thank Apache Camel community for keeping Camel Karaf
> going.
> Blow were introduced in camel 3.18, in this PR:
> [https://github.com/apache/camel/pull/7904]
>
> org.apache.camel/camel-cxf-spring-common
> org.apache.camel/camel-cxf-spring-rest
> org.apache.camel/camel-cxf-spring-soap
> org.apache.camel/camel-cxf-spring-transport
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
