[CXF-5410] Auto-registration of HTTP destinations in Blueprint should be optional

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Component/s: OSGi, Transports
• Estimated Complexity: Unknown
• Assignee: Sergey Beryozkin
• Reporter: Sergey Beryozkin
• Created: 20/Nov/13 21:38
• Updated: 22/Aug/14 13:11
• Resolved: 24/Apr/14 12:50

Description

CXF HTTP Transport offers an auto-registration support of HTTP destinations with a default CXF Servlet in OSGI Blueprint. This is generally useful when the users register JAXWS or JAXRS endpoints from Blueprint CXF extensions.

However it also catches the endpoint registrations done via the alternative mechanisms. For example, CXFBlueprintServlet can be used to register CXF Blueprint endpoints. Suppose CXFBlueprintServlet offers a "/a" servlet path, as the result the CXF endpoint will be accessible via "/a" and in addition, the default CXFServlet "/cxf" or other configured path.

This opens the extra path into the endpoint which will be unexpected for CXFBlueprintServlet users