-
1. Second click problem resolved
boy18nj Mar 8, 2011 10:30 PM (in response to geschtli)good to know. You resolved your issue.
-
2. Re: Second click problem resolved
nimo22 Mar 9, 2011 2:43 AM (in response to boy18nj)Why is that so?
Why do I have to put two different ajax calls of a page within the SAME form ?
I have had the same problem. When using two different forms and submitting a selectOneMenu of the second form via ajax by selecting an item nothing happens. When selecting again, the item is being selected successfully. So I have to select twice because the first select is ignored. Why is that so?
When putting the selectOneMenu of the second form into the first form and do the ajax-select, then it works
-
3. Second click problem resolved
geschtli Mar 9, 2011 3:28 AM (in response to boy18nj)Good joke:-)
But i thing, other developer have also that nasty handling
with that.
-
4. Re: Second click problem resolved
nimo22 Mar 9, 2011 3:55 AM (in response to geschtli)It should be best practice to minimize the content within a form - why I am forced to wrap ALL my input-fields and the like within ONE form only to make ajax-calls? Of course, I can minimze the execute-tags but normally I want to logically group views into different forms and not into one whole form.
-
5. Re: Second click problem resolved
geschtli Mar 9, 2011 7:37 AM (in response to nimo22)It's logically not always a good solution.
If you have all in separate files, think about this.
If you have a conditionally rendering, so that only
one component is rendered, the you can have to much
tags in your end script.
Suddenly in your client html script,
you can have such :
<form>
--- the rendered part ---
</form>
<form>
--- the not rendered part ---
</form>
But we need is only such:
<form>
--- the rendered part ---
</form>