it's not hard at all.. just one more loop :)
for OSGI.. I think it can be use to manage module right ? so.. maybe we
could consider webapp as module ?
2009/2/10 Hubert Iwaniuk <neotyk_at_kungfoo.pl>
> Hello,
> Would it be hard to enable deployment of multiple war files?
> Something like webapps directory with multiple wars and or exploded wars.
>
> Not sure what you mean by "put that on a OSGI module and be able to
> disabled a servlet at runtime" could you describe it a bit more?
>
> H.
>
> On Tue, Feb 10, 2009 at 1:48 AM, Survivant 00 <survivant00_at_gmail.com>wrote:
>
>> this program is based on contrib : http-servlet-deployer :
>> ServletWarDeployer.java
>>
>> but this version will support multiple ServletAdapter.
>>
>> Everything will be done by magic :)
>>
>> GrizzlyWebServerDeployer -a /Temp/hudson.war
>>
>> things that will be added :
>>
>> - use war file as default context : localhost:8080/hudson .. now it's
>> http://localhost:8080/
>> - support static files : now I got a exception because I didn't set the
>> flag to load static resources (or it's a bug)..
>> - testcases (of course)
>> - will add a sample application that contains all the attributes available
>> in web.xml (2.3)
>> - add logging too.. didn't had time yet.
>> - oh ya... it will support a file.war or a webapp already deployed.
>>
>> any suggestion is welcome.. let's have a beast within the beast :)
>>
>> do you think we can put that on a OSGI module and be able to disabled a
>> servlet at runtime ? (never tried that)
>>
>>
>> I think for most users that use servlet.. it will be easy to launch it
>> with that program. they could just create a web.xml and that's it..
>>
>> go I'm waiting for your comments.
>>
>> when I will commit that, I'll blog about this baby.
>>
>