Yan:
Aha! Client-side proxy - didn't think to ask you about that.
The deployment piece is a separate download. The deployment receiver available with Community Final on SourceForge unfortunately is broken - there's been a few forum posts related to this. The receiver itself works fine - the code in our web app to parse the deployment path to kick off the deployment was the issue.
That code has been fixed since last week and checked into the v2.1 Enterprise branch. That fix is also incorporated in the 2.1.0 Enterprise BETA that is available for anyone to sign-up for for a trial period.
We will do an update for the general Community release as soon as we clear out remaining bugs on 2.1.0. I would expect that update within two weeks.
If you cannot wait until then, like I said, I recommend requesting an Enterprise Trial. Then you can get access to the functioning version of the web app code today to test file-system deployment.
For all those on the forums that helped discover this issue, thank you, and we will get you that fix as soon as we can.
Lastly, for Struts, we did make some enhancements to the virtualization server in the process of fixing another issue. As a result of this fix, we believe we now properly support virtualization of Struts-based sites (yeah! I think this is quite important). We have not yet had time to test, and we would appreciate anyone out there in the Community assisting us here.
Now, once again the bad news: that virt server bug was checked-in to the v2.1.0 branch. So it is available in the 2.1.0 Enterprise BETA. This fix will also roll back into Community, but once again it will probably be a couple of weeks.
Let us know if you've any further questions, and I do hope you get the Enterprise BETA and help us test out virtualizing your Struts-based web app! (we are eager to make this work).
Kevin
