Deployer can run unlimited servlets. See this blog
http://weblogs.java.net/blog/2009/08/07/gws-deployer-1917-reloaded-new-features-part-1
that explain the command line parameters.
I think you looking for that :
-a, --application=[path]* Application(s) path(s).
Application(s) deployed can be :
Servlet(s), war(s) and expanded war folder(s).
To deploy multiple applications
use File.pathSeparator
Example : -a /app.war:/servlet/web.xml:/warfolder/
2009/9/8 Jeanfrancois Arcand <Jeanfrancois.Arcand_at_sun.com>
> Salut,
>
> smurugu wrote:
>
>> Justin,
>>
>> I want to use Grizzly embedded mode and integrate JAX-WS. Here are the
>> problems i am running into
>>
>> - The ServletAdapter is primitive - you can set the web.xml parms
>> programmatically which is a plus but integrating JAX WS servlet does
>> require
>> you to load JAX WS specific config files such as sun-jaxws.xml
>>
>
> Ok I'm not sure why this file is required. I need to take a look.
>
> - The ServletDeployer is good but i can not run more than 1 servlet
>>
>
> I didn't know that. I was under the impression you can deploy much more
> than one. Sebastien?
>
> - The samples that Jitu provided are good (refer to last week status
>> update
>> post) but does not offer much flexibility (spring dependency,tied to a
>> particular endpoint). I am sure if i spend some more time
>> i can customize it to my needs but unfortunately i am working on tight
>> timeline
>> - I looked into GF embedded version but the feature is available only in
>> GFv3 which is a preview now
>>
>
> Right but the features are almost all in. The biggest difference you will
> face with v3 embed will be the size and a lot of functionality you might not
> need. If the size doesn't matters, I would also recommend v3 embed. v3
> **totally** build on top of the GrizzlyAdapter interface so you will get
> Grizzly + extra Grizzly Adapter (like the ServletAdapter).
>
> On the other side, I didn't have a chance to run JAX WS but I'm pretty sure
> it will works on top of Grizzly. Alexey and I are planning to gives it a try
> once we have a chance. My goal is to have specific JAXWSAdapter you can use
> with the GrizzlyWebServer API. Jersey as one and it is quite popular and
> widely used. I suspect the same will apply for JAXWS.
>
> A+
>
> -- Jeanfrancois
>
>
>
>
>> Thanks
>> Sendhil
>>
>>
>>
>> Justin Lee-3 wrote:
>>
>>> You'd be better off just using glassfish at that point. The dependencies
>>> between that container and glassfish itself aren't exactly simple.
>>>
>>> smurugu wrote:
>>>
>>>> Hi,
>>>>
>>>> Is it possible to integrate Glassfish's ServletContainer into Grizzly. I
>>>> understand that Glassfish internally use Grizzly?
>>>>
>>>> Is it very tough to integrate Glassfish ServletContainer into Grizzly in
>>>> embedded mode?
>>>> Thanks in advance
>>>>
>>>> Sendhil
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>
>>>
>>>
>>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>
--
Vous pouvez me suivre sur Twitter / You can follow me on Twitter :
http://twitter.com/survivant