we are currently trying to make our store binding enabled. It occurs to me that we will not only have to adapt our own store, but also have to replace org.apache.slide.store.StandardStore. This is quite a drastic change as this class implements one of Slides most prominent features: delegation of requests to several different services or stores.
This makes me wonder, do you still use all the central classes for your Tamino store? Am I getting all this wrong, in the first place? Could you please provide me with some more hints?
Thanks in advance, Oliver
Nevermann, Dr., Peter wrote:
Hi Sliders,
we have been working on adding support for Binding in Slide (server) and I
just checked-in a bunch of changes. The main part comes in the class
org.apache.slide.structure.ObjectNode.java. For the specification of the
WebDAV Binding Extension see http://www.webdav.org/bind/.
There are 2 switches for enabling/disabling binding: a global one (property org.apache.slide.binding in slide.properties) and one at store level (method useBinding() in org.apache.slide.store.Store.java). Both switches are currently *disabled* by default ... so everything should work as before if you do not explicitly enable binding.
To make use of the binding extensions it is *not* enough to switch-on binding. The store implementation must be adapated to become binding-enabled. Roughly speaking, a binding-enabled store implementation must *not* use the (hierarchical) URI as unique ID, but instead, a different non-hierarchical URI which corresponds to the new property DAV:resource-id. Moreover, it must implement a "resolve" mechanism which, at store interface, transforms hierarchical URIs into unique resource IDs. That is mainly what we have done in our Tamino-based store implementation. Details will follow.
Hope the changes do not cause any inconveniences. At all events, I created a CVS tag "SLIDE_2_0_0" before check-in.
Regards, Peter
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
