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/07/16 08:10:10 UTC
[jira] Created: (GERONIMO-767) message-destination-link elements with path info don't work.
message-destination-link elements with path info don't work.
------------------------------------------------------------
Key: GERONIMO-767
URL: http://issues.apache.org/jira/browse/GERONIMO-767
Project: Geronimo
Type: Bug
Components: deployment
Versions: 1.0-M3
Reporter: David Jencks
Assigned to: David Jencks
<message-destionation-link>component.jar#actualAdminObject</message-destination-link>
does not resolve properly to much of anything, at least in an app client. some issues:
if this occurs in an app client, should we automatically deploy the admin object on the client? does this make sense?
just how should we interpret the # when interpreting the admin--object-name in the resource config?
--
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
[jira] Closed: (GERONIMO-767) message-destination-link elements with path info don't work.
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-767?page=all ]
David Jencks closed GERONIMO-767:
---------------------------------
Fix Version: 1.0-M5
Resolution: Fixed
duplicate of 892
> message-destination-link elements with path info don't work.
> ------------------------------------------------------------
>
> Key: GERONIMO-767
> URL: http://issues.apache.org/jira/browse/GERONIMO-767
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0-M3
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> <message-destionation-link>component.jar#actualAdminObject</message-destination-link>
> does not resolve properly to much of anything, at least in an app client. some issues:
> if this occurs in an app client, should we automatically deploy the admin object on the client? does this make sense?
> just how should we interpret the # when interpreting the admin--object-name in the resource config?
--
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