« Return to Thread: [Bug 668] New: grouped collection w/ accessname throws up in certain case

[Bug 668] New: grouped collection w/ accessname throws up in certain case

by Bugzilla from bugzilla-daemon@helma.at :: Rate this Message:

Reply to Author | View in Thread

http://dev.helma.org/bugs/show_bug.cgi?id=668

           Summary: grouped collection w/ accessname throws up in certain
                    case
           Product: Helma
           Version: CVS trunk
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Database Layer
        AssignedTo: helma-dev@...
        ReportedBy: nostalgiker@...


Created an attachment (id=112)
 --> (http://dev.helma.org/bugs/attachment.cgi?id=112)
demo app for groupedcollection NPE-on-add bug

I get NPE "error retrieving node" when *adding* an object to a grouped
collection, right after removing a similar object (belonging to same group)
from this collection, which was added in the same request. before the
NPE-provoking add i do removeChild(addedObject) on everything that makes
remotly sense and the collection isn't even aggressivly cached.

I modified the demo-generic-references app to show the problem - see
attachment. Root.main_action is where it all happens.

see also
http://groups.google.com/group/helma/browse_thread/thread/577854d4c4f7c2f7

--
Configure bugmail: http://dev.helma.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Helma-dev mailing list
Helma-dev@...
http://helma.org/mailman/listinfo/helma-dev

 « Return to Thread: [Bug 668] New: grouped collection w/ accessname throws up in certain case