> -----Original Message-----
> From: Ceki G�lc� [mailto:[EMAIL PROTECTED]
> Sent: jeudi 13 janvier 2005 14:12
> To: Cactus Users List
> Subject: RE: Testing web-application recycling?
> 
> Hi Vincent,
> 
> Sorry, I was not very clear. By recycling, I meant the "redeployment"
> of the whole web-application. This happens when a web application
> which has been deployed from a WAR
> 
> - has its WAR file updated: the expanded web application is removed,
>    and the WAR is expanded again.
> 
> - has its /WEB-INF/web.xml file updated.
> 
> - when the reload command is issued for the web application
> 
> For more details see for example: http://tinyurl.com/5mln2
> 
> Any serious web-application needs to make sure that when redeployed
> resources are recycled properly, e.g. files released, db connections
> closed, etc. This redeployment problem is also closely related to
> hot deployment as well as clustering and session replication.
> 
> Given the tight coupling with the App Server, redeployment tests
> require in-container testing.

I don't know. I guess it depends how you wish to check that the redeployment
has worked. It seems to me it should be easier to do the check at the
functional level (i.e. from the outside of the application). For example,
for a web application you could call a URL, verify it works, then do some
hot deployment with a newer version that changes the behavior of this
method, call that URL again and verify that the new result is the expected
one.

Do you have a specific use case in mind on which we could work and see
whether functional or unit level testing would be easier to achieve?

In any case, if you find that you can test the hot deployment change at the
unit level then Cactus will be able to do it. However you'll need to do the
hot redeployment by hand as the Cactus front end tools (Ant task, Maven
plugin, Web Test Runner) do not currently support doing a hot redeploy (and
we have started implementing this in Cargo but it's not ready yet).

[snip]

Thanks
-Vincent




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to