hi, this is probably not an issue with the contentProvider, but the initialization sequence of the tree "state" binding. there was a small bug in the tree component regarding this: the component tried to default a persistent binding a bit too late - this should be fixed in CVS head - try building from there. alternatively, try these scenarios (with the last release):
1) no state param supplied at all 2) state supplied from page property (persistent=yes, but no initial-value) 3) state supplied from page (persistent=yes, initial-value="java.util.HashMap"). regards, viktor On Apr 12, 2005 3:21 AM, John Gordon <[EMAIL PROTECTED]> wrote: > Hi All, > > I've been banging my head on this one: I keep running into the following > error in the rendering of a page when trying to use the tacos:Tree > component: > > Page recorder for page [my page name] is locked after a commit() > > I must be getting something confused between setting persistence on abstract > classes correctly or not fully understanding the rewind/record process > entirely. The Tacos:Tree examples are not a whole bunch of help here as they > creat static final ITreeContenProvider fields in the page classes. I'm > dynamically generated my ITreecontentProvider with a List of objects that > are returned from the hibernate API. > > All the code that creates my ITreeContentProvider is done in the > beginPageRender() method. > > Does anyone have an example of using the tacos:Tree component with a > non-static ITreeContentProvider? > > Thanks, I really appreciate it. > > John > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
