[
https://issues.apache.org/jira/browse/CXF-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937858#comment-13937858
]
Daniel Kulp commented on CXF-5610:
----------------------------------
The commit for this change breaks the WS-N tests. Thus, I'm going to back
this out so the builds can proceed why this is improved.
I also disagree with the bug. Those two URL's are different and thus they
SHOULD work. You should be able to publish a different service on each of
those URL's and have it work. If it doesn't, THAT is the bug, not that it
should throw an error.
> Jetty transport should warn the user if the endpoint address conflicts with
> published service
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-5610
> URL: https://issues.apache.org/jira/browse/CXF-5610
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 3.0.0, 2.7.11, 2.6.14
>
>
> When the user want to publish endpoint with address
> "http://localhost:9000/foo/bar"; and "http://localhost:9000/foo/bar/bar";, he
> should be get an error as these two address are conflict with each other.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
