Arthur; Refreshing the TBL workspace, Admin > Refresh Workspace,
should re-synch the ACL.  If not, Reset effectively re-starts TBL.  Re-
deploy should not be necessary in this case.

<<What is strange about this, is that the repeated projects don't
always contain the same substructure... TBL Access Control Editor
continues to display the duplicate projects even though they are no
longer in the workspace.>>

I take it the procedure was to upload/deploy a project, edit
permissions, delete project, upload/deploy a project with the same
name?  As stated, refresh workspace should do the trick.  This is
assuming the project is being uploaded via Project Upload or Composer
> Export... > Deploy.

-- Scott

On May 20, 3:09 pm, Arthur Keen <[email protected]> wrote:
> I ran into an issue with the TBL Access Control Editor in TBL showing each 
> workspace project twice (including topbraid projects).  What is strange about 
> this, is that the repeated projects don't always contain the same 
> substructure, for example one of the projects "src-apps" contains the entire 
> project structure, whereas it's doppelganger contains part of the project 
> (see attached image).  Is this a known issue?  I deleted the projects through 
> the console with the intent of re-deploying them, but the TBL Access Control 
> Editor continues to display the duplicate projects even though they are no 
> longer in the workspace.  I eventually resorted to 
> un-installing/re-installing tbl to get the Access Control Editor to synch 
> with the workspace and now after re-deploying the projects it seems to be in 
> perfect harmony.  
>
> Arthur

-- 
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en

Reply via email to