users@grizzly.java.net

Re: First comment about Servlet auto-deployer

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Thu, 02 Apr 2009 10:26:59 -0400

Salut,

Survivant 00 wrote:
> Here a comment that I received.
>
> ---------------------------------------------------------------------------------------------------
> Is it possible to use a mixed approach?
> I mean, use code to specify the port, context name, the web application
> directory, some extra classpath and then start/stop the server.
> I'm using this approach with Jetty/Tomcat/Resin embedded and I found it
> quite useful.

Yes we can probably start working on that, e.g. adding:

+ WarAdapter support, which watch a directory and autodeploy war file
deployed inside
+ lib directory: library added there are automatically appended to the
classpath

>
> In fact, I'm working on a project to be able to use different embedded
> containers, for testing purposes, and those are the common things many
> implement.
> If I'm not mistaken, I could simply use the GrizzlyWebServerDeployer
> class passing the appropriate parameters, but I'm missing the option of
> having some extra classpath (not in WEB-INF/lib and not in the "launch
> classpath".

Yes you filed an issue about that one, right? I propose we start a new
thread on dev_at_grizzly and try to come with a roadmap with the Servlet
Container.

>
> In any case, good job!

Yes Sebastien, great work!

-- Jeanfrancois

> D.
>
> PD: For an example of what I mean, this is the code to use the Jetty
> implementation:
> http://kenai.com/projects/wembed/sources/source-code-repository/content/trunk/src/jetty/classes/org/wembed/impl/JettyEmbeddedContainer.java?rev=42
> S!
>
>
> ---------------------------------------------------------------------------------------------------
>
> We can specify the port, we tough of adding a param to force the context
> name and classpath. You still can pass classpath using java
> --classpath ...
>
> but another param like that : -a hudson.war -classpath
> /lib/;/others_lib; ..
>
> I could easily use the Loader with any WebServer, but I don't see why
> yet. Jetty, Tomcat.. already load the web.xml (you don't have control
> on what they are doing.. but it's there)..
>
>