Forum OpenACS Development: Re: acs_sc::impl::new_from_spec fails if an optional service contract is not insalled

Well, the other option is to require WebDAV support be installed even if you never plan on using it.

The idea is that file-storage is installed, but WebDAV support is not installed because it is not used anywhere.

If at a later time, WebDAV support was installed, the service contract and implementations need to be activated.

Previously to install the bindings, it was recommened to vist the acs-service-contract page of an installation. I can understand why automatic install of bindings is preferred.

What does installing webdav support entail?

I'd be inclined to suggest that we include the webdav service contract in core, if we expect packages to implement it.

And whatever webdav entails in addition to just the service contract could be installed separately later, and you wouldn't have to manually go bind the service contracts.

Is that possible?

/Lars