Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <5147811.post@talk.nabble.com>
Date: Mon, 3 Jul 2006 00:51:15 -0700 (PDT)
From: Kuppe <kuppe@360t.com>
To: activemq-users@geronimo.apache.org
Subject: Configuration for topic/queue and persistence selection
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I was reading about your support for jndi using the jndi.properties file. I
assume that this provides a generic way to get a configured destination by
name, so that the type of destination (topic/queue) will be transparent to
the user of the destination. The destination will be looked up in the jndi
context and returned as configured in the property file.

Is it possible to somehow externalize other aspects such as transacted
sessions, persistent producers etc??? Of course it would be ideal if one
could somehow configure outside of the code whether or not a producer
created for a specific destination is going to be producing persistent
messages or not...

Perhaps there is another more elegant way to handle this???

Thanks in advance...
-- 
View this message in context: http://www.nabble.com/Configuration-for-topic-queue-and-persistence-selection-tf1883129.html#a5147811
Sent from the ActiveMQ - User forum at Nabble.com.