[
https://issues.apache.org/jira/browse/QPIDJMS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940680#comment-16940680
]
Stephan Siano commented on QPIDJMS-441:
---------------------------------------
I have had a look into this: The implementation does not look too difficult to
me, most effort is likely writing the tests.
My idea would be to add a PROXY_HANDLER to the JmsConnectionExtensions enum, a
setter for a ProxyHandler to the JmsConnectionFactory class, and another
attribute (with getter and setter) to the TransportOptions (similar to the
SSLContext). In the AMQPProvider class you could set the transport option if
the JMS connection extension is set on the connectionInfo, and in the
NettyTcpTransport one could finally set this proxy handler to the pipeline of
the channel.
Before I implement this for serious and invest time in testing this: Would you
be interested in a contribution for this feature? How do you think should the
tests for this look like, in particular, which additional test dependencies
could I include in order to set up a test proxy?
> Using QPID JMS behind a proxy
> -----------------------------
>
> Key: QPIDJMS-441
> URL: https://issues.apache.org/jira/browse/QPIDJMS-441
> Project: Qpid JMS
> Issue Type: Wish
> Components: qpid-jms-client
> Affects Versions: 0.40.0
> Reporter: morten
> Priority: Blocker
>
> I actually did not find a possibility to use the jms qpid client behind a
> proxy. I guess there will be a lot of people who needs to run the library
> behind a proxy. It would be nice to have the possibility to set a proxy
> somehow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
