Hi,
>
> Everywhere in the Grizzly support, it seems that org.apache.coyote.Adapter was used in place of com.sun.grizzly.tcp.Adapter.
Right. Jersey is build on top of Grizzly 1.0.x. com.sun.grizzly classes
are the new Grizzly, which is 1.5 and up (next official release will be
1.7.0).
That includes the ContainerProvider and the GrizzlyContainer, at least.
>
> Also, no attempt has been made to catch exceptions when a ContainerProvider throws one (in the case of the jaxws ProviderContainerProvider, which throws a ClassDefNotFound exception on the missing Coyote Adapter class, instead of simply returning null, which is what the ContainerFactory expects).
Can you explain exactly how you started Grizzly? I'm pretty sure 1.5.x
will not work with Jersey (quite easy to port if the community is
interested :-)). Have you try with Grizzly 1.0?
>
> So right now, only the Lightweight container works, and then only in certain circumstances (it hangs on a simple Hello World resource when I run it in prod, but it doesn't in Debug; a sure sign of deadlock). I haven't tried the jaxws ContainerProvider, because I simply don't see the point. Grizzly, being a Glassfish technology, should be supported sooned rather than later.
Agree :-)
Again if the community wants Grizzly 1.5/1.7 support, I can submit a
patch. You not only get Grizzly new runtime, you also get to run as a
Container in GlassFish v3 :-)
P.S I'm not yet on the user list so make sure you cc me :-)
Thanks
-- Jeanfrancois
>
> Thanks.
>
> *************************************************************
> Denis Robert
> Senior Technical Architect
> BF&M Insurance Group
> Phone: (441) 298-0344
> Email: drobert_at_bfm.bm
> *************************************************************
> This email and any files transmitted with it are
> confidential and intended solely for the use of the
> individual or entity to whom they are addressed.
> If you have received this email in error please notify
> the system manager.
> *************************************************************