[
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.
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
Affects Versions: jbossws-native-3.4.1
Environment: EAP 4.3.X and EAP 5.x
Reporter: Roger Hui
Assignee: Alessio Soldano
Priority: Minor
Fix For: 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira