You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Xu ShiChang Desmond (JIRA)" <ji...@apache.org> on 2014/05/26 05:37:02 UTC
[jira] [Comment Edited] (CXF-5740) CXF-5610 is preventing
applications from using the same endpoint url for multiple hadlers
[ https://issues.apache.org/jira/browse/CXF-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008543#comment-14008543 ]
Xu ShiChang Desmond edited comment on CXF-5740 at 5/26/14 3:36 AM:
-------------------------------------------------------------------
simple test case attached CXF5740Demo
was (Author: xushichang):
simple test case
> CXF-5610 is preventing applications from using the same endpoint url for multiple hadlers
> -----------------------------------------------------------------------------------------
>
> Key: CXF-5740
> URL: https://issues.apache.org/jira/browse/CXF-5740
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.7.11
> Reporter: Xu ShiChang Desmond
> Assignee: Willem Jiang
> Attachments: CXF5740Demo.java
>
>
> I'm having a bad day with the changes made for this jira issue https://issues.apache.org/jira/browse/CXF-5610.
> Jetty allows having multiple handlers for the same url, and jetty itself have its own means of handing the issue of how to handle such scenarios.
> See http://www.eclipse.org/jetty/documentation/current/writing-custom-handlers.html#passing-request-and-response/
> Before this jira issue came about, cxf also allowed this, and I have some applications that have depended on such functionality. This is stopping me from adopting cxf 2.7.11.
> I feel that at most, there should be a warning (even that is debatable), but at the moment this is an error which I cannot get around in any good manner.
--
This message was sent by Atlassian JIRA
(v6.2#6252)