wrong destination determination by OSGi based CXF entry point (regarding its
fallback logic)
--------------------------------------------------------------------------------------------
Key: CXF-3510
URL: https://issues.apache.org/jira/browse/CXF-3510
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 2.3.4, 2.4
Reporter: Aki Yoshida
Assignee: Aki Yoshida
Fix For: 2.4.1, 2.3.5
This problem is described in cxf-user thread
http://cxf.547215.n5.nabble.com/strange-destination-determination-logic-used-by-the-osgi-based-cxf-entry-point-td4385312.html
In summary, the http entry point in the OSGi container uses the destination
determination logic using a simple request path matching when there is no exact
match of the request URL path to one of the registered destination paths.
Consequently, when you have a service registered at "/abc", a request to any
URL path starting with this string, for example, "/abc2", "/abctest" is also
fowarded to this service. And this is not intended.
The intention of this fallback logic was for the rest based calls to forward a
request with an additional path argument to its correct service. For examples,
requests to "/abc/def" or "/abc/1/2" should be forwarded to the service
registered at "/abc".
I'll be suggesting the change required in
org.apache.cxf.transport.http_osgi.OsgiServletController for 2.3.x and
org.apache.cxf.transport.http.DestinationRegistryImpl for 2.4.x.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
