[ https://issues.jboss.org/browse/JBWS-3237?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3237: --------------------------------------- See http://anonsvn.jboss.org/repos/jbossws/stack/cxf/trunk/modules/testsuite/... : public void testHttpProxyUsingHTTPClientPolicy() throws Exception { ... HelloWorld port = getPort(getResourceURL("jaxws/cxf/httpproxy/HelloWorldService.wsdl"), testHost); Client client = ClientProxy.getClient(port); HTTPConduit conduit = (HTTPConduit)client.getConduit(); HTTPClientPolicy clientPolicy = conduit.getClient(); clientPolicy.setProxyServerType(ProxyServerType.HTTP); clientPolicy.setProxyServer(proxyHost); clientPolicy.setProxyServerPort(proxyPort); ProxyAuthorizationPolicy authPolicy = new ProxyAuthorizationPolicy(); authPolicy.setAuthorizationType("Basic"); authPolicy.setUserName(PROXY_USER); authPolicy.setPassword(PROXY_PWD); conduit.setProxyAuthorization(authPolicy); ... port.echo("Hi!"); } to me at this point (from a cxf stack point of view), this jira basically boils down to the mapping between given ports/stubs and their HTTPClient/HTTPConduit. I need to check, but if HTTPConduit are shared by ports (perhaps with same endpoint address), we might need to tune their creation (it should be possible to (allows users to) set custom ConduitInitiator/ConduitSelector on the bus). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBWS-3237?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3237 at 5/27/11 6:10 AM: ---------------------------------------------------------------- See http://anonsvn.jboss.org/repos/jbossws/stack/cxf/trunk/modules/testsuite/... : {code:title=HTTPProxyTestCase.java|borderStyle=solid} public void testHttpProxyUsingHTTPClientPolicy() throws Exception { ... HelloWorld port = getPort(getResourceURL("jaxws/cxf/httpproxy/HelloWorldService.wsdl"), testHost); Client client = ClientProxy.getClient(port); HTTPConduit conduit = (HTTPConduit)client.getConduit(); HTTPClientPolicy clientPolicy = conduit.getClient(); clientPolicy.setProxyServerType(ProxyServerType.HTTP); clientPolicy.setProxyServer(proxyHost); clientPolicy.setProxyServerPort(proxyPort); ProxyAuthorizationPolicy authPolicy = new ProxyAuthorizationPolicy(); authPolicy.setAuthorizationType("Basic"); authPolicy.setUserName(PROXY_USER); authPolicy.setPassword(PROXY_PWD); conduit.setProxyAuthorization(authPolicy); ... port.echo("Hi!"); } {code} to me at this point (from a cxf stack point of view), this jira basically boils down to the mapping between given ports/stubs and their HTTPClient/HTTPConduit. I need to check, but if HTTPConduit are shared by ports (perhaps with same endpoint address), we might need to tune their creation (it should be possible to (allow users to) set custom ConduitInitiator/ConduitSelector on the bus). was (Author: asoldano): See http://anonsvn.jboss.org/repos/jbossws/stack/cxf/trunk/modules/testsuite/... : {code:title=HTTPProxyTestCase.java|borderStyle=solid} public void testHttpProxyUsingHTTPClientPolicy() throws Exception { ... HelloWorld port = getPort(getResourceURL("jaxws/cxf/httpproxy/HelloWorldService.wsdl"), testHost); Client client = ClientProxy.getClient(port); HTTPConduit conduit = (HTTPConduit)client.getConduit(); HTTPClientPolicy clientPolicy = conduit.getClient(); clientPolicy.setProxyServerType(ProxyServerType.HTTP); clientPolicy.setProxyServer(proxyHost); clientPolicy.setProxyServerPort(proxyPort); ProxyAuthorizationPolicy authPolicy = new ProxyAuthorizationPolicy(); authPolicy.setAuthorizationType("Basic"); authPolicy.setUserName(PROXY_USER); authPolicy.setPassword(PROXY_PWD); conduit.setProxyAuthorization(authPolicy); ... port.echo("Hi!"); } {code} to me at this point (from a cxf stack point of view), this jira basically boils down to the mapping between given ports/stubs and their HTTPClient/HTTPConduit. I need to check, but if HTTPConduit are shared by ports (perhaps with same endpoint address), we might need to tune their creation (it should be possible to (allows users to) set custom ConduitInitiator/ConduitSelector on the bus). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBWS-3237?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3237: --------------------------------------- This can be considered as a duplicate of JBWS-2941 for the jbws-cxf stack. See the previous comment as well as the test case for JBWS-2941 for examples on how to setup proxy info. It is also possible to control the proxy setup of any client stub/proxy by either using the spring based approach (declare a http:conduit element with name _portQName_.http-conduit) or by leveraging the org.apache.cxf.Configurer (you can install a custom configurer that detects HTTPConduit instances being configured and set the proxy info in them if the conduit name matches your _portName_.http-conduit one). In particular, a convenient approach for the latter is to extend the org.jboss.wsf.stack.cxf.client.configuration.BeanCustomizer that's in the JBossWSCXFConfigurer, which is the configurer installed by default in the Bus when JBossWS integration is in use. -- 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