[
https://issues.apache.org/jira/browse/CXF-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006660#comment-14006660
]
Jason Pell commented on CXF-5740:
---------------------------------
We use multiple org.eclipse.jetty.server.handler.AbstractHandler attached to
the same address and can check the post parameters and even the content to
decide to handle them or let the next handler in the chain handle them. This
is pretty standard jetty use case. I think I can work around it, but would be
easier not to have to. So good to see a property, although would have been
better if it were not a system property and instead a config parameter that
could be passed into the jetty factory.
> 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
>
> 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)
