If the only reason you want WebDAV is to give designers direct access to
product descriptions, you could write a custom Store over your database.
This would give you direct database access to the information (which
seems to be a priority) while retaining the benefits of WebDAV.
If I were in your
I am writing an open source cart, a real one, one that someone can
actually use;)
Currently, my product descriptions are stored in a RDBMS, but I would
rather store the images and product descriptions on a webdav server.
My java-based tapestry application will communicate with the webdav
server
