[CXF-3510] wrong destination determination by OSGi based CXF entry point (regarding its fallback logic)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4, 2.3.4
• Fix Version/s: 2.4.1, 2.3.5
• Component/s: Transports
• Assignee: Akitoshi Yoshida
• Reporter: Akitoshi Yoshida
• Created: 11/May/11 16:00
• Updated: 08/Aug/11 14:43
• Resolved: 23/May/11 14:28

Description

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.

Issue Links

• relates to: CXF-3559 Merge patch of CXF-3510 into ServletControl