[
https://issues.apache.org/jira/browse/QPID-6556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558317#comment-14558317
]
Rob Godfrey commented on QPID-6556:
-----------------------------------
Is there any reason not to use the pooled connection factory rather than the
non-pooled version?
Also, I wonder if we should add alternative getters/setters to the factory to
allow the setting of individual attributes rather than having to set the whole
URL (obviously this would be a seperate JIRA :-) )
> Document how to bind JMS client destinations and connection factories into
> Tomcat JNDI
> ---------------------------------------------------------------------------------------
>
> Key: QPID-6556
> URL: https://issues.apache.org/jira/browse/QPID-6556
> Project: Qpid
> Issue Type: Task
> Components: Documentation
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Fix For: 6.0 [Java]
>
>
> Qpid JMS client AMQConnectionFactory implements
> javax.naming.spi.ObjectFactory allowing a creation of connection factory
> instances and destination instances in external JNDI container.
> There is no documentation at the moment about how to integrate Qpid JMS
> client into JNDI containers. The aim of this JIRA is to add an section into
> Qpid JMS client documentation about how to integrate Qpid JMS client into
> Tomcat Web container JNDI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
