Yes, I think the messaging settings are OK.
But it will work with the internal HSQLDB, you should change this to your prefered database. I think this will not be a big issue (see the docs/examples/jms for this).
You might check whether the tables are created and, if you only send a message a row in the table is created.
After this you are able to run you JMS app.
The port is another story, you should look after the network topologie ...
Hello Wolf-Dieter,
It is not very smooth, I met one problem during update client codes which try to setup connection to the Queue:
{code}QueueMBean queueMbean = (org.jboss.mq.server.jmx.QueueMBean) ServiceLocator.getInstance().MbeanLookup("jboss.messaging.destination:name=testQueue,service=Queue", org.jboss.mq.server.jmx.QueueMBean.class);{code}
as you know, we have no jbossmq.jar, so i don't know what is in jboss messaging corresponding to the org.jboss.mq.server.jmx.QueueMBean.
thanks,
Emre
Any special why you need the QueueMBean?
For normal JMS handling QueueSender QueueReceiver should fit.
For the existent application migration...