-
1. Re: Command link bug
alexanderbelov May 22, 2007 6:46 AM (in response to alexanderbelov)If I refresh page everything works good. And if I refresh my page by standard method where is no errors. If I refresh only part of the page by Ajax - there is a bug.
-
2. Re: Command link bug
alexsmirnov May 22, 2007 12:26 PM (in response to alexanderbelov)This is a known problem, occurs in any implementations. In Firefox, even if tag succesfuly updated, "document.forms" collection is not updated. As a result, acces to form instance by this collection ( such code used in any implementations to clear hidden fields before submit form by button ) cause error.
Can you avoid to update h:form component by AJAX ? ( try to move it around updatable elements ). -
3. Re: Command link bug
alexanderbelov May 23, 2007 1:15 AM (in response to alexanderbelov)Thanks for your reply. I'll try.
-
4. Re: Command link bug
alexanderbelov May 23, 2007 4:34 AM (in response to alexanderbelov)I have one form for my tree and the second form for my page to display. I have parent table component. It's parent is . I refresh parent table, but error is occured.
All pages, which is included in this page, have form inside. That's why I suppose that updating panelGroup component with id="content" must work. -
5. Re: Command link bug
ilya_shaikovsky May 23, 2007 8:06 AM (in response to alexanderbelov)It would be better to send us your example for investigations.
attach please to http://jira.jboss.com/jira/browse/AJSF-67 -
6. Re: Command link bug
alexsmirnov May 24, 2007 6:20 PM (in response to alexanderbelov)We have special a4j:form component to avoid this problem. It have own JavaScript code , worked properly for a ajax updates. Also, it can be used in pair with a4j:htmlCommandLink, full equivalent of the h:commandLink, but safe for a ajax updates.
-
7. Re: Command link bug
alexanderbelov May 25, 2007 1:23 AM (in response to alexanderbelov)To tell the truth I used a4j:form too. There are a4j:commandButtons in my tree. And I can not use a4j:htmlCommandLink in my page, because commandLinks are generated by other components (another liblary, built on JSF 1.2). I can write custom renderers for these library, but I am not sure that it will resolve my problem. If so, I'll do it.
-
8. Re: Command link bug
alexanderbelov May 25, 2007 1:24 AM (in response to alexanderbelov)I am sorry, there are a4j:commandLink components in my tree, of course.