You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2013/07/25 12:53:50 UTC

[jira] [Updated] (CXF-5153) Consider updating ServletController to disable address overwrites by default

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

Sergey Beryozkin updated CXF-5153:
----------------------------------

    Summary: Consider updating ServletController to disable address overwrites by default  (was: Consider disabling ServletController disabling address overwrites by default)
    
> Consider updating ServletController to disable address overwrites by default
> ----------------------------------------------------------------------------
>
>                 Key: CXF-5153
>                 URL: https://issues.apache.org/jira/browse/CXF-5153
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>            Reporter: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> By default ServletController overrides the endpoint address - historically this was needed to support the correct WSDL and service page generation. This is not needed for the latter any more and I believe is not needed to WSDL gen too. Not needed for RS as well.
> With this overriding done by default what happens is that if we have CXFServlet accessed over multiple IP connections or multiple CXFServlets covering the same endpoint we have an issue.
> The user can of course can disable this feature - but if it works just fine without the overrides then it is an extra work for a user. 
> Thus I propose to disable it by default on the trunk only , so that the user re-enables only when really needed, we only need to double check WS code won't be affected   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira