Standalone JMS client in J2EE 1.4 Beta

Question

Hi,
I expected it should be possible to deploy an MD Bean and to send message to it from outside the server - using "runclient". It does not work for me. During "runclient" it can not find the queue - defined with "message-destination". Can anybody tell me - is it supposed to work this way?
I do runclient -client m01mclient.ear -name MDClient
I have .ear with application.xml and sun-j2ee-ri.xml and .jar in it with application-client.xml. Here are the descriptors:
application-client>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<?xml version="1.0" encoding="UTF-8"?>
<application-client version="1.4"
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/application-client_1_4.xsd">
<display-name>MDClient</display-name>
<resource-ref>
<res-ref-name>jms/KnownConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<message-destination-ref>
<message-destination-ref-name>jms/KnownQueue</message-destination-ref-name>
<message-destination-type>javax.jms.Queue</message-destination-type>
<message-destination-usage>Produces</message-destination-usage>
<message-destination-link>NameForKnownQueue</message-destination-link>
</message-destination-ref>
<message-destination>
<message-destination-name>NameForKnownQueue</message-destination-name>
</message-destination>
</application-client>
sun-j2ee-ri.xml>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE j2ee-ri-specific-information
PUBLIC "-//Sun Microsystems Inc.//DTD J2EE Reference Implementation 1.4//EN"
"http://localhost:8000/sun-j2ee-ri_1_4.dtd">
<j2ee-ri-specific-information>
<app-client>
<module-name>mdclient.jar</module-name>
<resource-ref>
<res-ref-name>jms/KnownConnectionFactory</res-ref-name>
<jndi-name>jms/QueueConnectionFactory</jndi-name>
<default-resource-principal>
<name>j2ee</name>
<password>j2ee</password>
</default-resource-principal>
</resource-ref>
<message-destination>
<message-destination-name>NameForKnownQueue</message-destination-name>
<jndi-name>jms/Queue</jndi-name>
</message-destination>
</app-client>
</j2ee-ri-specific-information>

Answer 1

Sorry for the false alarm. In fact it works fine with these same deployment descriptors.
But in the last J2EE Tech Tips the client is packaged much simpler.