Well, for me is indispensable :D, because my users can create/delete workspaces theirselves.
But, don't worry, I'll do some hack to directly delete the directories. I hope that doing this does not cause inconsistencies. Regards. On 10/30/05, Stefan Guggisberg <[EMAIL PROTECTED]> wrote: > > On 10/30/05, Martin Perez <[EMAIL PROTECTED]> wrote: > > Hi Stefan. > > > > Is this support planned? For me, it seems a clear TODO. Maybe a fast > > solution could be tag the workspace as "deleted" and then modify the > > login/get repositories list methods. > > > > Well, who knows. I'm talking being relatively new to jackrabbit. So > forgive > > me, if what I'm saying is not so trivial. > > don't worry martin. your suggestion would indeed be a trivial solution. > 'disabling' a workspace could also be accomplished with access control > (by denying access to a given workspace for everyone). > > i thought you meant physically removing a workspace and all its content > which IMO would be non-trivial to implement properly. > > workspace management is something that will be addressed in jsr-283. > jackrabbit will sooner or later support programmatic workspace removal. > i don't think that it will make it into jackrabbit version 1.0 though > (unless > a lot of people deem it an indispensible 1.0 feature of course). > > cheers > stefan > > > > > Regards. > > > > On 10/30/05, Stefan Guggisberg <[EMAIL PROTECTED]> wrote: > > > > > > hi martin > > > > > > On 10/30/05, Martin Perez <[EMAIL PROTECTED]> wrote: > > > > Creating a workspace is a very easy task, but how can a jackrabbit > > > workspace > > > > be deleted programatically? > > > > > > currently there's no programmatic way to do that, sorry. the reason is > > > that it > > > would be quite complicated to implement it properly, just think of > > > access control > > > & versioning issues. > > > > > > cheers > > > stefan > > > > > > > > > > > Thanks. > > > > > > > > > > > > > > > >
