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

["Jason Winnebeck (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799079#comment-13799079 ] 

Jason Winnebeck commented on CXF-5153:
--------------------------------------

The issue doesn't mention the exact name of the parameter. It's called disable-address-updates. Here is an example web.xml:

{code:xml}
<servlet>
	<description>Apache CXF Endpoint</description>
	<servlet-name>cxf</servlet-name>
	<servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
	<init-param>
		<!-- Workaround issue https://issues.apache.org/jira/browse/CXF-5068 -->
		<!-- Remove if https://issues.apache.org/jira/browse/CXF-5153 is resolved -->
		<param-name>disable-address-updates</param-name>
		<param-value>true</param-value>
	</init-param>
</servlet>
{code}

> 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 was sent by Atlassian JIRA
(v6.1#6144)