James.Strachan wrote:
>
> On 1/23/07, Paul Moser <[EMAIL PROTECTED]> wrote:
>> I'm having problems looking up connection factories via JNDI, from a
>> standalone Java client when ActiveMQ is integrated with JBoss using a
>> RAR.
>
> ....
>
> Also the ActiveMQ Resource Adapter should not be used from a stand
> alone client - its only to be used inside a J2EE container (or MDP
> container like Jencks).
>
>
Sorry, I think I may have explained what I was trying to do badly. I've used
the ActiveMQ Resource Adapter to integrate ActiveMQ with JBoss so that my
MDBs use queues/topics actually on the embeded ActiveMQ broker rather than
JBossMQ/Messaging.
I also need to be able to submit/receive messages from one of the
queues/topics via a stand alone Java client, for this I've used standard
JMS/JNDI code, it knows nothing of the ActiveMQ RAR at all. It's the JNDI
lookup of the connection factory from this client to the J2EE server that
produces the strange result. Unfortunately I don't have much control over
the clients, they are expecting to be able to find the connections
factories/topics/queues in the same JNDI tree as several EJB remote home
interfaces.
Are the connection factories/queues/topics just exposed by the RAR for use
within the J2EE server only.
Paul
--
View this message in context:
http://www.nabble.com/JBoss-integration-and-lookup-of-connection-factories.-tf3061463.html#a8518676
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
