Hmmm.. let's see...
It means that I could edit domain.xml to remove the /files, /users and /actions
folders (or collections, right?) and create another one called MyFolder... or, even
better, I could configure the root folder to use a custom class, like this:
<data>
<objectnode classname="org.acme.MyNewNodeType" uri="/" />
</data>
Doing this I could use my custom class to determine what folders I'll show for
each user. Is it right ? Could I know how is the user connected in this new class
(then I could check what folders to make available) ?
But there's something strange here... If the [root] folders are defined in the
data section (or slide.data), then what is slide.def configuration file configuring at
all ? I thought it was there where I would configure custom classes to access my ECM
system and return the folder's structure, permissions, content, etc., but now I can't
see where I'd start using the store since the folders seems to be based on the data
section (like above).
Am I going the right direction or I just messed it all up ?
By the way, ECM means Enterprise Content Management. :-)
-----Original Message-----
From: Martin Holz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 30, 2003 11:05 AM
To: [EMAIL PROTECTED]
Subject: Re: Starting using slide
"Flavio Eduardo de Cordova" <[EMAIL PROTECTED]> writes:
> But now I've got another question... When I connect using IE it shows me three
> folders in the root - actions, files and users. What are they exactly ? How are they
> created ?
In /files you find your data, /users represents all Users known to slide and /actions
represents
operations, that are subject to security restrictions, eg. read, write, lock. The
collections are
created in the data section of Domain.xml.
> I plan to use Slide as a framework to create a layer to access the documents
> in an ECM system through WebDAV.
What does ECM mean?
>It means that all the structure information, as well as users, security and even
>content are going to be taken from this system. So, when a user connect to Slide it
>will show only the folders and documents he or she actually can access, just like
>when the same system is accessed by the web (HTML).
>
> But, by now, it seems to me there are too much configuration files to make it
> work. If I want a new user I've got to insert it in a Tomcat's conf file. Then I've
> got to edit permissions in the namespace... and I still have restart tomcat... Wow !!
> OK, I think it's possible to configure Tomcat and Slide to use custom classes
> for all of this... but I'm not sure yet how easy it is, or if it'll work the way I
> want (those defaut folders - actions, files, etc - for example) and, more important,
> if it will not be hard to the administrator to keep it running.
User management can be done by custom classes, so no need to restart tomcat. However
this will require
some programming work. One way is to write a custom store mapped to the the /users
URL, which
makes your user database visible to slide.
Martin
---------------------------------------------------------------------
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]
