So far everything but the client side changes is working great. I was able to make very small mods to my original TreeModelAdapter to the new TreeNode version. Again, other than the logging and client-side saving, I have not run into any problems. Works great so far. You mention a new version with the client-side toggling issue resolved... is this up on the trunk yet? I would really like to get it and try it out when it is available.
PS.... I really appreciate yor quick response to my problem.. you rock!!!!! Tim On Fri, 2005-02-25 at 10:12, Sean Schofield wrote: > Let me look into it. There are definitely ways to cut down on the log > messages. Come to think of it, I'm not sure I have logging configured > when I run my examples. Anyways, there are ways to filter out log > messages of certain levels, from certain classes, etc. > > In the meantime, I'd appreciate any feedback on tree2. Also, I have > already implemented an improvement so that if you are using > client-side toggling it can remember your client side toggle changes > between page requests (if you have session cookies enabled.) > > sean > > > On Fri, 25 Feb 2005 10:07:25 -0600, Tim Pyle <[EMAIL PROTECTED]> wrote: > > I am indeed using myfaces implementation. I did not get these warnings > > with the first tree, but I was also using older version of myfaces. I am > > using the latest source from CVS. The tree works great, and well, > > everything works great.... just wish I could kill the warning message > > about myfaces having to assign an ID. So this might not be as much of a > > question for the tree2 component as much as it is for the myfaces engine > > itself. And I get one of those warnings for each node in the tree, so I > > would just like to be able to turn that off so it doesn't waste log > > space. > > > > Tim > > > > On Fri, 2005-02-25 at 09:54, Sean Schofield wrote: > > > Are you using myfaces for JSF implementation or are you using another > > > implementation? > > > > > > There are a lot of dynamically generated components inside the tree > > > that use JSF's ability to generate an ID if none is specified. I > > > haven't seen this message though, so that is why I am asking. > > > > > > Have you ever used h:dataTable (any implementation) before? I would > > > imagine you would get similar messages. Tree2 is very similiar to > > > dataTable in terms of how it has a few components that it uses by > > > iterrating over lots of data (creating new ids for each row, column.) > > > > > > sean > > > > > > > > > On Fri, 25 Feb 2005 09:10:54 -0600, Tim Pyle <[EMAIL PROTECTED]> wrote: > > > > With the new tree2 component, I get alot of these type of warnings: > > > > > > > > [exec] 17:28:48,873 INFO [Engine] StandardContext[/jport]WARNING: > > > > Component treeForm2:tims_tree2:0:0:25:_id81 just got an automatic id, > > > > because there was no id assigned yet. If this component was created > > > > dynamically (i.e. not by a JSP tag) you should assign it an explicit > > > > static id or assign it the id you get from the createUniqueId from the > > > > current UIViewRoot component right after creation! > > > > > > > > Is there anyway to add an id to whatever isn't getting one? Or can I > > > > just turn off this warning message altogether? > > > > > > > > Tim > > > > > > > > > > > >
