The behaviour has changed, but the problem still exists. It now just
says that it can't find a registered bean. However, in walking through
the code (at runtime), I can see there are valid beans in the (parent)
I'm guessing there is a classloader issue, and that the classes are
not equal (even thought they are the same textual name).
The bindings on my field (java.util.concurrent.BlockingQueue
And there are two Queue(s) in the (parent) manager that look like this:
@Production, name=delivery, @ApplicationScope]
@Production, name=injection, @ApplicationScope]
It sure seems like it should be matching the first one.
On Mon, Apr 13, 2009 at 9:13 AM, Scott Ferguson <f...@caucho.com> wrote:
> On Apr 12, 2009, at 6:27 PM, Scott Hernandez wrote:
>> (working against 03/18/09 snapshot of resin)
>> It seems like there is a class-loader problem in my definition for my
>> Queue (and I expect any global bean with an annotation class from the
>> The first time through everything seems to work just fine, but in
>> subsequent updates (webapp reloads) this error comes up. If I l start
>> resin up with the app deployed, or deploy the app with it not existing
>> yet, then things load fine. But once I have touched the resin-web.xml
>> (or made any change causing the webapp to stop-start) of the deployed
>> webapp then this error comes up.
>> WEB-INF/resin-web.xml:24: java.lang.IllegalArgumentException:
>> interface resinscratchspace.annotations.UserUpdate is not visible from
>> class loader
> This is a regression issue that should be fixed in the next snapshot.
> The exception is from the java.util.reflect.Proxy class.
> -- Scott
>> 22: <jms:MemoryQueue>
>> 23: <Named>userUpdates</Named>
>> 24: <rssa:UserUpdate />
>> 25: </jms:MemoryQueue>
>> The rssa namespace is set in the resin-xml file as a package in the
>> classes directory of the webapp.
>> Do these annotations need to be in the resin-dir/lib or someplace
>> Thanks in advance,
>> resin-interest mailing list
> resin-interest mailing list
resin-interest mailing list