users@grizzly.java.net

Servlet deployment: was [Jean-Francois Arcand's Blog] New Comment Posted to 'Extending the Grizzly HTTP Runtime part V: Programatically configuring Servlet and GrizzlyAdapter'

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Fri, 09 Jan 2009 17:34:08 -0500

Salut,

foo_at_bar.com wrote:
> A new comment has been posted on your blog Jean-Francois Arcand&#39;s
Blog, on entry #10977 (Extending the Grizzly HTTP Runtime part V:
Programatically configuring Servlet and GrizzlyAdapter).
>
>
> View this comment:
<http://weblogs.java.net/blog/jfarcand/archive/2009/01/extending_the_g_5.html>
> Edit this comment:
<http://weblogs.java.net/mt/mt.cgi?__mode=view&blog_id=258&_type=comment&id=52735>
>
> IP Address: 64.125.132.43
> Name: greeneyed
> Email Address: foo_at_bar.com
> URL: Comments:
>
> Is it possible to have an embedded version but that reads the
configuration from files like a regular container would do? <br />

Yes, we have an exploratory implementation described here:

http://weblogs.java.net/blog/survivant/archive/2008/12/read_webxml_wit.html

but this is not yet an official project/sub project. We still discussing it.


  <br />
> I say so because I currently use Jetty embedded and I use always the
same "Jetty launcher" code and I just point it to the proper directory
to be mounted and it reads the web.xml and deploys the application, etc.
<br />

Yes that's quite nice.


  <br />
> This was I can re-use the same code for every tiny application I want
to, without harcoding the servlets, filters etc. that I need. And at the
same time, the web application can be mounted in a regular container
without a change. <br />
> I understand how doing everything in code can be very useful
sometimes, but in my case I'd rather do it like that.. <br />

I agree. We will work on a solution soon :-)


> Salute and good job!

Thanks!!!

-- Jeanfrancois
>