I don't know if it's even allowed, but I can't imagine trying to make an "instakit" verticle app that includes a jdk. There are just too many variables with different operating systems and vendors, and different jdk vendors and versions. In such a scenario, potential users would have to download a compatible jdk, which throws a wrench in the concept of an "instakit".
One thing to consider is implementing such services through a service contract, so that if a native aolserver version of something like webdav does arrive later, then it is easy to make the switch. We do that now with search services and payment gateways, and I can't imagine that it would be too difficult to do the same with Soap services and possibly webdav.
With regards to the lock contention issue, was that with respect to jvm internal locks or was that due to user-defined locks in application code?
