On Aug 18, 2009, at 2:46 AM, Craig McClanahan wrote:
>> Or just fork the grizzly container code directly.
>>
>> We could modify the containers so that they can be cast to a
>> special interface to get access to the WebApplication?
>>
> How about just adding a new create method to
> GrizzlyWebContainerFactory:
>
> public SelectorThread create(String u, WebApplication a);
>
> ? That way, I could supply a preconfigured and initialized
> WebApplication (which therefore already knew about the
> GuiceComponentProviderFactory instance wrapping the Guice injector I
> want to use).
>
Can you log an issue?
I think to do this properly is going to require some more thought
about how to integrate with the Servlet layer. For example allowing
one to construct a ServletContainer with a WebApplication and/or
ResourceConfig. I need to do something like this for the latter with
Servlet 3.0 integration so there might be some common overlap.
The lower-level layer is probably easier to integrate with.
In the interim you may be able to use the same tricks that Richard did
by extending the Servlet support.
Paul.