If you need a servlet container - it'd make sense to use Glassfish (I'd
recommend the latest 3.1 RC, with the latest Grizzly integrated). The
web profile, as Justin mentioned, should be enough.
Here are instructions [1] how comet should be enabled on GF.
Grizzly comet samples are here [2].
I remember you asked about CometContext-per-Client, not sure it's good
idea :(
If you can describe your usecase, may be we can discuss better approach.
Thanks.
WBR,
Alexey.
[1]
http://download.oracle.com/docs/cd/E19798-01/821-1752/ggrla/index.html
[2]
http://java.net/projects/grizzly/sources/svn/show/trunk/code/samples/comet
On 02/08/2011 07:43 PM, goberman_at_msn.com wrote:
> Alexey, I looked at docbook documentation last week. It shows how to
> run a standalone Java sample that is configured to listen on port 80
> for incoming connection requests.
> I am looking for a way to integrate grizzly with a "servlet container",
> like Tomcat (or Glassfish) and I am struggling to fund any
> documentation addressing it.
> It should confirm to the following requirements:
>
> 1) Server port should be configured in the "servlet container", not in
> grizzly. Grizzly should be "plugged into" container.
> 2) I should be able to serve both static web pages and handle HTTP
> Comet requests via Grizzly on the same server port. This is what
> Tomcat/Comet allows me to do now. I do not want to serve web pages on
> port X and Grizzly requests on port Y.
>
> Any chance of a quick guide on how to accomplish it? Or it is not
> possible?