OK, so if we accept the change I just made to build.xml, the binary distribution will have a working .war file distribution. This is great in that it's pretty much "drop in deployment" for most servlet engines. The problem now is that the source distribution has no .war file, and in fact doesn't even build the right directory structure for webapp deployment. This is too bad. A lot of problems with our library are related to classpath issues, and packaging things in webapp style leverages the servlet spec to avoid the need to change classpaths. I'm not sure what to do about the source dist, but it would be nice if the people downloading the source didn't have a much more complicated deployment experience than the binary folks. It's probably too late to really change this, but I'd suggest we generate build/soap.war on every compile. Include the samples if they're built, and don't if not. Alternately building into build/webapps/soap would also work. Fixing this would obliviate the need for a lot of verbiage and potential confusion in the install docs. Anyway, I don't really expect this to get fixed, it's just that it would make things a lot simpler if it was. --Glen
