By the way, I was able to work past the lazy-init issue (presumably)
by using this block instead:
<cfg:MessageBeanConfig>
<cfg:class>test.DeliveryListener</cfg:class>
<cfg:destination>#{delivery}</cfg:destination>
</cfg:MessageBeanConfig>
However, enqueueing a message doesn't produce calls on my Listener.
It seems to produce some sort of spin-loop inside Resin.
Jeff
On Tue, Jul 20, 2010 at 1:17 PM, Jeff Schnitzer <j...@infohazard.org> wrote:
> On Tue, Jul 20, 2010 at 12:21 PM, Scott Ferguson <f...@caucho.com> wrote:
>> Thanks. It's a timing issue in CanDI. The jms:FileQueue was added to a
>> lazy-init which wasn't being evaluated when the #{delivery} was
>> processed. The fix will be in the next snapshot.
>
> Cool. If you get to a point where this is checked into Resin trunk,
> I'd love to help you test it :-)
>
> Jeff
>
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
