message-destination-link elements with path info don't work.

<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?