"That's not going to happen anytime soon. First we have to finish the SVN reorg. Then we need to address the problem. A ways down the line we will end up testing all of the examples against the RI but that is a lower priority."
I can do this for you and update in a document. "Why not help us fix the MyFaces version instead?" If you have any directions at fixing the NPE in commandlink renderer, I can work on it. I'm not sure if only because of the different implementations than adhering to the specs. -Bala -----Original Message----- From: Sean Schofield [mailto:[EMAIL PROTECTED] Sent: Monday, June 27, 2005 5:54 PM To: MyFaces Discussion Subject: Re: Troubles with trees on MyFaces with Sun RI > I needed a tree component for my Sun RI-based application and spent > several hours today trying to make MyFaces trees work. Here's a small > list of problems that I met: > > 1. Tree2. > Does not work with Sun RI. NPE with command links, this problem was > recently reported in the list. Known issue. (MYFACES-291) > 2. Tree. > I had to disable Javascript in web.xml otherwise, some javascript was > rendered in the page, with a reference to clear_helloForm() function, > which was not rendered. This sounds like a new one. > 3. Tree. > Duplicate component identifier. Recently Fixed (MYFACES-281) > 4. Tree. > Simply not reacting. Well obviously it won't work until issues #1,#2 and #3 are resolved. > So I'd be greateful if anyone could send me a working MyFaces + Sun RI > example. WAR file maybe? That's not going to happen anytime soon. First we have to finish the SVN reorg. Then we need to address the problem. A ways down the line we will end up testing all of the examples against the RI but that is a lower priority. > Does anyone know if there are good free tree implementations outside > MyFaces? (sorry to ask it here, but I'm a bit desperate, guys) Nope. Why not help us fix the MyFaces version instead? > /lexi sean Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.
