[ https://issues.jboss.org/browse/JBWS-3750?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3750 at 4/24/14 4:58 AM: ---------------------------------------------------------------- Rebecca, I'm not sure I follow your analysis here, perhaps you can clarify it a bit. My idea would be this new feature to be something in JBossWS / WFLY / EAP, possibly with no changes to CXF, unless that's strictly required. This would likely be an extension to the current address rewrite mechanism we have in JBossWS, see org.jboss.wsf.stack.cxf.metadata.MetadataBuilder#processAddressRewrite(...) method. If we had a "path" element in the ServerConfig that comes from the AS webservices subsystem management model, that could be used by the SoapAddressRewriteHelper to create the rewritten address. The problem I can see with this approach, atm, is that it won't work properly for the scenario in which auto rewrite is on (that is when the webservice host in the server config is "jbossws.undefined.host"), but we could probably accept this limitation. was (Author: asoldano): Rebecca, I'm not sure I follow your analysis here, perhaps you can clarify it a bit. My idea would be this new feature to be something in JBossWS / WFLY / EAP, possibly with no changes to CXF, unless that's strictly required. This would likely be an extension to the current address rewrite mechanism we have in JBossWS, see org.jboss.wsf.stack.cxf.metadata.MetadataBuilder#processAddressRewrite(...) method. If we had a "path" element in the ServerConfig that comes from the AS webservices subsystem management model, that could be used by the SoapAddressRewriteHelper to create the rewritten address. The problem I can see with that approach, atm, is this won't work properly for the scenario in which auto rewrite is on (that is when the webservice host in the server config is "jbossws.undefined.host"), but we could probably accept this limitation. -- 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