I just commited my latest changes to my GWS autodeployer : servlet, war,
multiplewar.
the code is in the branch : war-deployer
contrib/grizzly-servlet-webserver-deployer
The application support this :
* #1 - war
* #2 - web.xml
* #3 - folder that contains at least one war
* #4 - folder of a deployed war (will use the /WEB-INF/web.xml)
so if you have a folder like this :
/multiplewar/hudson.war
/multiplewar/demo.war
/multiplewar/WEB-INF (that contains web.xml)
/multiplewar/deployedapps (that contains WEB-INF/web.xml)
they will all be deploy
you can pass a simple servlet
GrizzlyWebServerDeployer -a /servlet/web.xml (it will deploy it) (but I
think I didn't finish this one :) oh ya.. it's finish... the problem is
that you need to pass the libs into the classpath like
java -classpath ....jar GrizzlyWebServerDeployer -a /servlet/web.xml
what else
oh ya the limitations of this implementation.
We only have one classloader, so all the jars from all the webapps will be
available to others wars.. so if you have the same libs twice but different
versions.. it won't like it at runtime :(
and the other if that the classpath for a expanded war didn't work
completyl.. if you have folders in WEB-INF/otherstuff it won't be found
at runtime..
I think it's all for now.. I'll blog about that as soon as I get a review
for this.. Don't want to put it in the trunk without a approval..
I'll change the System.out to Logger later this week.. I'm tired right now.
2009/2/26 Jeanfrancois Arcand <Jeanfrancois.Arcand_at_sun.com>
> Salut,
>
> Survivant 00 wrote:
>
>> je recommence a tester avec hudson et là ca marche pas exactement :(
>>
>> #1 : le servlet répond seulement si je met un slash a la fin
>>
>> htpt://localhost:8080/hudson/
>>
>> c:/temp/hudson
>> context = /hudson
>> deployed application path=c:/temp/hudson/WEB-INF/web.xml
>> sa context=/hudson
>> sa servletPath=/
>> sa alias=/hudson/
>>
>> est-ce que je dois enlever le dernier slash dans "sa alias" ou bien SA
>> devrait etre capable de gérer ca ?
>>
>
> Oui SA devrait etre capable de gerer ca. Encore un issue a entrer!
>
>
>
>>
>> là me reste un petit glish dans mon GWSdeployer. il gere mal le
>> classpath quand je lui donne un repertoire deployé au lieu du .war
>>
>> je corrige ca et je serais prêt a migrer ca dans le trunk.
>>
>
> genial!!!
>
> A+
>
>