Salut,
Survivant 00 wrote:
> Multiple war deployment might be a nice contribution :-)
>
> I tough it was called Glassfish :)
LOL :-) i think they are complimentary. Grizzly is much more easier to
embed than GF right now and do simple things. GF is more complicated
althrought they are working on something (still not what I would use,
but they seems to know what they are doing ;-) ;-))
>
>
> if you give me some head up, I could look at that on my free time. I
> could do a sample that you could repackage later.
The idea would consist of either supporting a xml file and do:
java -jar grizzly-webserver.jar --config grizzly.xml
and in grizzly.xml, have a way to define the war location, it's servlet
name and context path, or the adapter associated with the application.
We need to keep it quite simple.
We are currently working on something similar for GlassFish v3 where we
want to be able to deploy a Grizzly based application (an implementation
of Adapter or GrizzlyAdapter + code) inside GlassFish v3. The
glassfish.xml contains the adapter class name and the context path,
that's it. So grizzly fans can now enjoy v3 :-)
>
> to add meat to your port :
> http://weblogs.java.net/blog/jfarcand/archive/2009/01/extending_the_g_5.html
>
> someone could take the sample : war-on-grizzly from the contribs and
> complete it.
Yes that's on my radar to take a look :-) But that's one is problematic
(in terms of politics :-)). We may decide to pursue the project (if
people are interested) using another project (on java.net or whatever) :-)
Could be a nice extension to Grizzly. In war-on-grizzly,
> I was xmlbeans to read the web.xml, but I add JAXB in my blog :
> http://weblogs.java.net/blog/survivant/archive/2008/12/read_webxml_wit.html
I think using JAXB is politically easier to sell :-)
>
>
>
>
> en passant ta grange est croche sur ta photo :)
Trop drole...et elle est comme ca depuis tres tres longtemp. Faut juste
pas y toucher :-)
A+
-- Jeanfrancois
>
>
>
>
> 2009/1/8 Jeanfrancois Arcand <Jeanfrancois.Arcand_at_sun.com
> <mailto:Jeanfrancois.Arcand_at_sun.com>>
>
> Salut,
>
> thanks to Sébastien who raised the problem:
>
> https://grizzly.dev.java.net/issues/show_bug.cgi?id=366
>
> I've prepared a bundle that contains Comet, Bayeux, MessagesBus and
> Servlet supports. You can now use that bundle directly by doing:
>
> java -jar grizzly-webserver-1.9.4.jar -p 8080 -a grizzly-twitter.war
> com.sun.grizzly.sample.twitter.TwitterServlet
>
> That command will 'deploy' the war file and make it ready for
> servicing requests. Bayeux will also be available under /cometd
> (fixed url for now).
>
> If you are interested to contribute, take a look at some example
> from here:
>
> http://weblogs.java.net/blog/jfarcand/archive/2009/01/extending_the_g_5.html
>
> Multiple war deployment might be a nice contribution :-)
>
> A+
>
> -- Jeanfrancois
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> <mailto:users-unsubscribe_at_grizzly.dev.java.net>
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
> <mailto:users-help_at_grizzly.dev.java.net>
>
>