You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/08/26 10:21:46 UTC
[jira] Created: (GERONIMO-921) figure out if message-destination-refs from an app client to a different module make sense
figure out if message-destination-refs from an app client to a different module make sense
------------------------------------------------------------------------------------------
Key: GERONIMO-921
URL: http://issues.apache.org/jira/browse/GERONIMO-921
Project: Geronimo
Type: Bug
Components: naming
Versions: 1.0-M5
Reporter: David Jencks
Fix For: Wish List
If you have say an app client "client.jar" and some ejbs in "ejb.jar" you can write down a message-destination-link
ejb.jar#myQueue
in the client jar.
Currently we don't handle this, and I'm not sure we should or what this should mean. The spec does not discuss what this might mean AFAICT. For us annyway it would require finding a correct jms plan on the client and adding a copy of the admin-object-instance from the server's plan to the client jms plan. I'm not sure this is a plausible thing to try to do.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira