DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43136>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43136

           Summary: sitetree was modified after it was locked
           Product: Lenya
           Version: Trunk
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: major
          Priority: P2
         Component: Miscellaneous
        AssignedTo: dev@lenya.apache.org
        ReportedBy: [EMAIL PROTECTED]


Still having some issues with multiple people trying to edit the sitetree at the
same time, or close anyway. I login with two users. Have both create a new xhtml
page. Put everything in, hit create. One will create, one will throw this error:

The object [node lenya://lenya/pubs/default/content/authoring/sitetree.xml] was
modified after it has been locked.

If I was creating an xhtml document, hitting cancel will ask me if I want to
create the document I was trying to create. Hitting cancel on a media type
throws a NPE that I will take a look at, or post a different bug. 

I can also get this sitetree modified error to fire by going to create a page.
Nudging from a different session, then hitting create on my page creation. 

It would appear that we need either stronger or weaker locking. Either we
strongly lock the sitetree on any operation, including going to create. Or we
don't lock the sitetree until create is hit. People can't fill out the create
form as quickly as a script can. At least it is no longer creating entries in
the sitetree without the content being present.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to