cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-5410) Auto-registration of HTTP destinations in Blueprint should be optional
Date Thu, 24 Apr 2014 12:51:19 GMT

     [ https://issues.apache.org/jira/browse/CXF-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergey Beryozkin resolved CXF-5410.
-----------------------------------

    Resolution: Fixed
      Assignee: Sergey Beryozkin

>  Auto-registration of HTTP destinations in Blueprint should be optional  
> -------------------------------------------------------------------------
>
>                 Key: CXF-5410
>                 URL: https://issues.apache.org/jira/browse/CXF-5410
>             Project: CXF
>          Issue Type: Bug
>          Components: OSGi, Transports
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>             Fix For: 3.0.0
>
>
> 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 
>  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message