geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: message-destination-ref's
Date Tue, 12 Oct 2004 15:56:38 GMT
that's my understanding of the spec.  What does the spec say about 
jsr-77 names for admin-objects? do they include application or module?

david jencks

On Oct 12, 2004, at 8:59 AM, Aaron Mulder wrote:

> 	Well let's say you set it up like this:
>
> <message-destination-ref>
>   <message-destination-ref-name>Foo</message-destination-ref-name>
>   <...>
>   <message-destination-link>Bar</message-destination-link>
> </message-destination-ref>
>
> <message-destination>
>   <message-destination-name>Bar</message-destination-name>
> </message-destination>
>
> 	Then how do you map the message destination "Bar" to a specific
> JMS Queue or Topic?  I guess we require that somewhere in your server,
> application, or module deployment plans you deployed an AdminObject 
> with
> the message-destination-name of "Bar"?  It could be at any of those
> levels, though, right?
>
> Thanks,
> 	Aaron
>
> On Tue, 12 Oct 2004, David Jencks wrote:
>> unlike resource-env-ref, which it replaces, message-destination-ref is
>> designed to not need any input from a vendor plan.  IIRC you need to
>> also refer to message-destination-link.  I believe that there are some
>> tests that show it works.
>


Mime
View raw message