[
https://issues.apache.org/jira/browse/CXF-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352776#comment-15352776
]
Sergey Beryozkin commented on CXF-6869:
---------------------------------------
Hi Vedran
Right, I see, I suppose we can keep cxf.path as is.
The reason I kind of liked cxf.servlet.path is because it would look
neat/well-structured in application.yml, given that we use cxf.servlet.init to
pass the init parameters, with both "cxf.servlet.path" and "cxf.servlet,init"
related to configuring "CXFServlet":
{noformat}
cxf:
servlet:
path: /custom
init:
services-list-path: /serviceslist
{noformat}
FYI, I've updated one of the demos to use YAML:
https://github.com/apache/cxf/blob/master/distribution/src/main/release/samples/jax_rs/spring_boot_scan/application/src/main/resources/application.yml
I'm OK with keeping cxf.path as is but if you happen to warm up a bit to a
"cxf.servlet.path" idea, then let me know
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.4#6332)
