Hi Brian, what is your problem with Domain.xml? Starting from the one delivered with WCK just leave it untouched and things should work. There is *no* redundant stuff in it. You might not need it, but Slide does.
Judging from what you want to achieve WCK seems to be right for you. Concerning the releation to Slide WCK is a special Slide store abstraction plus some helper code for JAAS. Oliver On Fri, 17 Dec 2004 10:55:05 -0800, Brian Lee <[EMAIL PROTECTED]> wrote: > WCK Question > > First I'd like to say that WCK is a Godsend. It is very useful. > Unfortunately I still don't have a full grasp of SLIDE and WCK's full > relationship with it... (My time off our company webdav project didn't > help...) > > Goal: > My system does not use anything from the domain.xml besides specifying > my custom store. > My system handles everything - user adminstration, etc... > Moreover with this system, I want display files to a user based on > arbitrary logic my > system determines (security/permissions). > > I do not want to display files how they are really laid out in terms of > path and even filename. > Basically I want to use a 'virtual file system' with WCK, but I am > having problems due to things in > Domain.xml (user folders, action folders). > > Question: > Given the above requirements, what is the absolute minimum elements that > I can have in domain.xml? > > How should I go about implementing my system with WCK? > > Is WCK the best way to go? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
