You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Peter Palaga (Jira)" <ji...@apache.org> on 2022/05/05 13:28:00 UTC

[jira] [Commented] (CAMEL-9627) Splitup camel-cxf into modules so REST dont pull in old SOAP stuff

    [ https://issues.apache.org/jira/browse/CAMEL-9627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532247#comment-17532247 ] 

Peter Palaga commented on CAMEL-9627:
-------------------------------------

Yeah, this is blocking us from accepting [~javaduke]'s PR that wants to add a support for CXF client https://github.com/apache/camel-quarkus/pull/3727

It would be nice if the future camel-cxf-ws could be free of Spring dependencies.

Another related topic: We'd initially like to support only the CXF client (through [~javaduke]'s contribution) in Camel Quarkus. This is because we do not want to commit to supporting Jetty or Undertow transports CXF server depends on. I wonder whether it would be possible to split CXF-WS further into CXF-WS consumer and CXF-WS producer artifacts?


> Splitup camel-cxf into modules so REST dont pull in old SOAP stuff
> ------------------------------------------------------------------
>
>                 Key: CAMEL-9627
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9627
>             Project: Camel
>          Issue Type: Improvement
>          Components: karaf, osgi
>            Reporter: Claus Ibsen
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: Future
>
>
> To make camel-cxf feature less bloated and not include this seldom used component which you can install as its own feature.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)