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

Sergey Beryozkin commented on CXF-6869:
---------------------------------------

Hi Vedran, 
FYI we've updated CXF 3.2.0-SNAPSHOT CxfAutoConfiguration to 

org.springframework.boot.web.servlet.ServletRegistrationBean

which is not available in SpringBoot 1.3.x to make sure CXF starters can be run 
with SpringBoot 1.5.

CXF 3.1.x users would like to run the starters with SpringBoot 1.5 and I think 
it is reasonable to assume, given that
SpringBoot 1.3.x, 1.4.x and 1.5.x now exist that most users are now with 1.4.x.

Would it affect your CXF code if we removed the support for SpringBoot 1.3.x in 
CXF 3.1.11-SNAPSHOT and if yes then would you be OK to migrating to SpringBoot 
1.4.x  once CXF 3.1.11 is out ?

Thanks, Sergey

> 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
>             Fix For: 3.1.7, 3.2.0
>
>
> 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.15#6346)

Reply via email to