Fwd: Remote JNDI access to JMS resources

[Romain Manni-Bucau <rm...@gmail.com>]

Hi!

wonder what we should put behind such a need (client lookup of server
resource).

One constraint is to not need any impl (amq for instance).

I thought to create a ResourceMetaData class transporting properties of the
server but that's not enough. We really have 2 worlds for some resources
and client and server logic are different. The connection factory is the
right example for this: in the server you are linked to the tx mgr, in the
client often not.

So the question is what do we expect? Using the server resource (= proxying
all the API, not complicated but not logical, moreover perf will be poor
:s) or using a real client resource. If the last one getting the conf can
only be done by a lot of reflection + client system properties usage (for
overriding)....nothing perfect

well i'm kind of mind-blocked on it, any opinion will be welcomed.


- Romain


---------- Forwarded message ----------
From: Romain Manni-Bucau <rm...@gmail.com>
Date: 2012/8/10
Subject: Re: Remote JNDI access to JMS resources
To: users@openejb.apache.org


well to be complete, currently you'll need such a system property in your
client:

-DResource/javax.jms.ConnectionFactory=connectionfactory:org.apache.activemq.ActiveMQConnectionFactory:tcp://localhost:61616

- Romain



2012/8/10 Romain Manni-Bucau <rm...@gmail.com>

> Hi,
>
> currently that's not supported, we'll work on it quickly i think. Maybe
> you can open a jira to track the issue?
>
> - Romain
>
>
>
> 2012/8/9 ymaraner <tp...@gmail.com>
>
>> If I configure my JMS resources as described in the documentation:
>>
>>
>>
>> How do I access these resources from a java client running in a separate
>> JVM?
>>
>> I've tried to get an initial context using these properties:
>>
>>
>> and then calling
>>
>>
>> but I get a NameNotFoundException.
>>
>>
>>
>>
>>
>> -----
>> - Tim
>> --
>> View this message in context:
>> http://openejb.979440.n4.nabble.com/Remote-JNDI-access-to-JMS-resources-tp4656767.html
>> Sent from the OpenEJB User mailing list archive at Nabble.com.
>>
>
>