cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vedran Pavic (JIRA)" <>
Subject [jira] [Commented] (CXF-6869) Consider adding Spring Boot starter
Date Mon, 18 Apr 2016 07:30:25 GMT


Vedran Pavic commented on CXF-6869:

Sergey, I'll be glad port it.
Hopefully will be able to fit that to my schedule within the next week or two.

Since this will result in a new CXF artifact(s), I need you to point me to place where to
put my code.
At first look, it looks to be a fit under integration modules.

Artifacts should be named with respect to Spring Boot's guidelines for 3rd party starters:

Assuming the integration assumption from above was correct, the modules would be named {{cxf-integration-spring-boot-autoconfigure}}
and {{cxf-integration-spring-boot-starter}}. Would it be possible to omit the {{integration}}
Regarding sample application, I've seen your already have a space for that.

> Consider adding Spring Boot starter
> -----------------------------------
>                 Key: CXF-6869
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>          Components: Integration
>            Reporter: Vedran Pavic
> I've recently authored a PR in Spring Boot to add support for auto-configuration of {{CXFServlet}}
and default CXF's configuration:
> 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
> 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

View raw message