I'm glad you are making progress. Can you consider this part of my
original reply?
Is this a standalone non-j2ee client? If so you will have to use
instructions from activemq to use activemq. In particular, the
openejb
jndi implementation only exposes ejbs, not any other resources. If
you
have a j2ee app client, and you wish to use jms, you need to deploy a
copy of the activemq adapter on the client. You can then use the j2ee
java:comp/env context to find your stuff.
thanks
david jencks
On Jul 29, 2005, at 10:00 PM, Sami Dalouche wrote:
OK, some news regarding my previous problem :
- I found a sample Ressource Adapter configuration file, so I can now
deploy my
resource adapter without any exception. (under the name
weather/Topics).
so, it should have deployes 2 topics :
jms/weatherTopic and jms/weatherRequestsTopic
- However, when I lookup "jms/weatherTopic" or
"jms/weatherRequestsTopic"
through my Spring-acquired JNDI context, it says
javax.naming.NameNotFoundException: jms/weatherRequestsTopic
So I'm wondering :
- Is there a waay to check that some JNDI entry is actually present ?
- Does activeMq register the names under something else as what we
specify ?
- Any idea regarding this problem ?
<big snip>
| 