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 Tue, 28 Jun 2016 05:55:57 GMT


Vedran Pavic commented on CXF-6869:

Hi Sergey!

I've originally modeled the names of configuration properties to be consistent with [Spring
Boot properties|]
that register additional servlets, namely with:

spring.webservices.path=/services # Path that serves as the base URI for the services.
spring.h2.console.path=/h2-console # Path at which the console will be available.

You are of course free to adjust these to match your preferences, if the originally chosen
names aren't descriptive enough.
Among your suggested alternatives, {{cxf.servlet-path}} makes more sense to me.

> Consider adding Spring Boot starter
> -----------------------------------
>                 Key: CXF-6869
>                 URL:
>             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:
> 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