[
https://issues.jboss.org/browse/JBWS-3237?page=com.atlassian.jira.plugin....
]
Alessio Soldano edited comment on JBWS-3237 at 5/27/11 6:09 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 (allows users to) set custom
ConduitInitiator/ConduitSelector on the bus).
was (Author: asoldano):
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).
Set an HTTP proxy host/port for an individual WS-stub
-----------------------------------------------------
Key: JBWS-3237
URL:
https://issues.jboss.org/browse/JBWS-3237
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-cxf, jbossws-native
Affects Versions: jbossws-native-3.4.1
Environment: EAP 4.3.X and EAP 5.x
Reporter: Roger Hui
Priority: Minor
Fix For: jbossws-native-4.1, jbossws-cxf-4.1
We would like to set an HTTP proxy host/port for an individual WS-stub.
We found [1], but the link goes to a dead page [2], and we found a valid JBoss Remoting
page [3]. In [3] it shows that the proxy host/port can be configured in the client
metadata. However, we don't see how to set this from JBossWS. We would like this to
be a new feature.
[1]
http://community.jboss.org/wiki/JBossWS-FAQ#How_can_I_setup_my_client_to_...
[2]
http://labs.jboss.com/jbossremoting/docs/guide/ch05.html
[3]
http://docs.jboss.org/jbossremoting/docs/guide/2.5/html/index.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira