Here is my jndi.properties:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming.client
j2ee.clientName=si.avris.prevoznik.SimpleMessageClient
But in the mean time I have the solution. Look to the previous client code:
connectionFactory = (ConnectionFactory)
jndiContext.lookup("jms/QueueConnectionFactory");
| destination = (Queue) jndiContext.lookup("avrisQueue");
|
The working version has queue/avrisQueue instead of avrisQueue:
connectionFactory = (ConnectionFactory)
jndiContext.lookup("jms/QueueConnectionFactory");
| destination = (Queue) jndiContext.lookup("queue/avrisQueue");
And now it works. I think my example (client running outside JBoss and MDB
running within JBoss) is more common for real situations where one programmer
works on client code while another one works on the EJB code.
I have one more question.
I have seen examples where people use jndi properties in different ways.
My setting is the default one (from Getting started example):
java.naming.provider.url=jnp://localhost:1099
Where on the JBoss is the port 1099 specified?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861530#3861530
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861530
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
