We try to run the Getting started with jboss 4.0 example/ejb/simplemessage on two different hosts. We modified the compile-build-deploy jboss-build.xml to deploy the mdb on one side and the client on the other side. And it seems to work. The mdb side is working but the MyQueue queue was created locally and we reckon that it should not be created.

On the mdb side we are using the following settings:
jms_ds.xml

<connection-factories>

<!-- The JMS provider loader -->

QueuehostJMSProvider
org.jboss.jms.jndi.JNDIProviderAdapter
<!-- The queue connection factory -->
XAConnectionFactory
<!-- The topic factory -->
XAConnectionFactory
<!-- Connect to JNDI on the host "queuehost" port 1099-->

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=192.168.1.103:1099



</connection-factories>
...

standard_jboss.xml

<invoker-proxy-bindings>
<invoker-proxy-binding>
my-mdb-invoker
<invoker-mbean>does-not-matter</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
QueuehostJMSProvider
StdJMSPool
1
30000
15
1

10

queue/MyQueue
10
0


</proxy-factory-config>
</invoker-proxy-binding>

jboss.xml


<enterprise-beans>
<message-driven>
<ejb-name>SimpleMessageEJB</ejb-name>
<destination-jndi-name>queue/MyQueue</destination-jndi-name>
</message-driven>

<invoker-proxy-binding-name>my-mdb-invoker</invoker-proxy-binding-name>

</enterprise-beans>