Right, and maybe then we will have support for @Current @MyQueue
BlockingQueue<MyQueueItem> also.
Yeah, the (remote) service/servlet stuff will be cleaner with that syntax.
On Tue, May 19, 2009 at 9:13 AM, Scott Ferguson <f...@caucho.com> wrote:
>
> On May 18, 2009, at 10:51 PM, Scott Hernandez wrote:
>
>> I was going to start converting a bit of the config from the xml
>> mapped names to the actual class names in our resin-web.xml . However
>> the names have changed; Is there an example of how this works?
>>
>> <!-- Doesn't work because the destination cannot be found -->
>> <ejb:MessageBeanConfig destinationName="delivery"
>> class="org.subethamail.core.queue.DeliveryListener"/>
>
> ejb-message-bean is a complicated case because the real bean is your
> DeliveryListener. A similar kind of issue applies to remote service
> configuration, and bam-service and even Servlets.
>
> I think the right solution is to configure the DeliveryListener with
> annotations:
>
> <subethamail:DeliveryListener>
> <MessageBean destinationName="delivery"/>
> </subethamail:DeliveryListener>
>
> Or for servlets:
>
> <mypkg:MyServlet>
> <WebServlet url-pattern="/foo"/>
> </mypkg:MyServlet>
>
> Where @MessageBean and @WebServlet are known annotations. The CanDI
> spec's SPI has just changed radically in the last 3 weeks, making that
> kind of configuration possible (it's still a few weeks before Resin
> supports it, though.)
>
> So, until that's supported, you'll want to stick with <ejb-message-
> bean>.
>
> -- Scott
>>
>>
>>
>> <!-- works -->
>> <ejb-message-bean
>> class
>> =
>> "org
>> .subethamail.core.queue.DeliveryListener"><destination>#{delivery}</
>> destination></ejb-message-bean>
>>
>> Thanks in advance,
>> Scott
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
