cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vedran Pavic (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CXF-6869) Consider adding Spring Boot starter
Date Wed, 08 Jun 2016 07:53:21 GMT

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

Vedran Pavic edited comment on CXF-6869 at 6/8/16 7:53 AM:
-----------------------------------------------------------

Hi Sergey,

Sorry for the delay - I don't see any reason to stray away from the approach we have initially
taken and what is the recommended way of doing Spring Boot integration. I've deliberately
linked the contents of Boot's own auto-configuration module few comments back to demonstrate
that there are many different technologies in there, all of which are optional to use/activate.

{quote}
Alternatively, we could have this conditional on a configuration property, for example {{cxf.jax-rs.component-scan}}.
If you prefer not to discover and register JAX-RS resources automatically, the default for
that property would be {{false}} and user which like that approach would just have to add
{{cxf.jax-rs.component-scan=true}} to their configuration properties.
{quote}

Do you have any feedback/preference on this?

Regarding the Spring Cloud integration, I'm not that much into that project. Maybe we could
revisit that after Boot integration is finalized.

Thanks for renaming the starter modules and insight into release schedule!


was (Author: vpavic):
Hi Sergey,

Sorry for the delay - I don't see any reason to stray away from the approach we have initially
taken and what is the recommended way of doing Spring Boot integration. I've deliberately
linked the contents of Boot's own auto-configuration module few comments back to demonstrate
that there are many different technologies in there, all of which are optional to use/activate.

{quote}
Alternatively, we could have this conditional on a configuration property, for example {{cxf.jawrs.component-scan}}.
If you prefer not to discover and register JAX-RS resources automatically, the default for
that property would be {{false}} and user which like that approach would just have to add
{{cxf.jawrs.component-scan=true}} to their configuration properties.
{quote}

Do you have any feedback/preference on this?

Regarding the Spring Cloud integration, I'm not that much into that project. Maybe we could
revisit that after Boot integration is finalized.

Thanks for renaming the starter modules and insight into release schedule!

> Consider adding Spring Boot starter
> -----------------------------------
>
>                 Key: CXF-6869
>                 URL: https://issues.apache.org/jira/browse/CXF-6869
>             Project: CXF
>          Issue Type: New Feature
>          Components: Integration
>            Reporter: Vedran Pavic
>            Assignee: Sergey Beryozkin
>
> I've recently authored a PR in Spring Boot to add support for auto-configuration of {{CXFServlet}}
and default CXF's configuration:
> https://github.com/spring-projects/spring-boot/pull/5659
> The PR was closed with "won't fix" resolution since Boot team are unwilling to add CXF
as a dependency to the project. Instead a 3rd party starter was suggested.
> The concept of a 3rd party starter is generally encouraged for technologies that don't
have first-class support in projects from Spring portfolio. Such 3rd party starters are listed
here:
> https://github.com/spring-projects/spring-boot/blob/master/spring-boot-starters/README.adoc
> If CXF team is interested, I'm willing to port my PR to CXF.
> Note that the original PR was focused around JAX-WS support, but can be easily expanded
to include JAX-RS support as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message