[
https://issues.apache.org/jira/browse/QPIDJMS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964346#comment-16964346
]
Clement Pellerin commented on QPIDJMS-441:
------------------------------------------
I understand the proxy is configured as an extension to avoid a dependency in
the JmsConnectionFactory, unfortunately this makes it impossible to configure
through JNDI. Can we define a JmsProxiedConnectionFactory that would take the
proxy configuration as regular options to make it compatible with JNDI? The
second factory could be in its own jar. Users of that factory would not mind
the extra proxy dependencies since that's the whole point of using that factory.
> Using QPID JMS behind a proxy
> -----------------------------
>
> Key: QPIDJMS-441
> URL: https://issues.apache.org/jira/browse/QPIDJMS-441
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
> Affects Versions: 0.40.0
> Reporter: morten
> Priority: Minor
> Fix For: 0.47.0
>
>
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
