dev@glassfish.java.net

Re: upcoming grizzly-config merge

From: Ludovic Champenois <Ludovic.Champenois_at_Sun.COM>
Date: Thu, 16 Apr 2009 14:48:51 -0700

On 4/16/09 2:22 PM, Jeanfrancois Arcand wrote:
>
>
> Lloyd Chambers wrote:
>> Justin,
>>
>> The new AMX is working on the grizzly config generically with one
>> problem:
>>
>> The @Configured Protocol interface does not specify key=true for the
>> getName(), which makes AMX think it's a singleton. All
>> non-singletons must have a 'key' value on one of the attributes; this
>> is used as the 'name' field of the ObjectName.
>>
>> Can you fix...quickly? I want to commit today and this is causing
>> problems.
>
> I've filled:
>
> https://grizzly.dev.java.net/issues/show_bug.cgi?id=546
>
> to track the issue.
>
> Thanks!
>
I am working on a RESTFul generator...Same issue with ProtocolFilter,
Transport, SelectionKeyHandler , ProtocolFinder

On non grizzly beans we need keys on ServerRef, ThreadPool,
MessageSecurityConfig unless my generator is broken...
All these config beans can be a member of a List, so we need to be able
to find one, by its key.

Ludo