This is, I believe, fixed in later versions of Tapestry 5.3.
Great. Thanks you tow for the input!
Regards,
René
On 07.09.2012 22:14, Muhammad Gelbana wrote:
I remember when I faced a similar case I debugged and reached that method *
org.apache.tapestry5.corelib.components.Form.preallocateName
I remember when I faced a similar case I debugged and reached that method *
org.apache.tapestry5.corelib.components.Form.preallocateNames(IdAllocator)*
which
looks like it's still pre-allocating IDs and have the JIRA issue's link
commented on it. And I can see the pre-allocating logic in v5.3.5
O
This is, I believe, fixed in later versions of Tapestry 5.3.
On Fri, Sep 7, 2012 at 12:05 PM, Muhammad Gelbana wrote:
> Check this old thread
> http://tapestry.1045711.n5.nabble.com/t5-3-1-Heads-up-for-special-form-field-names-similar-to-InternalSymbols-PRE-SELECTED-FORM-NAMES-td5101482.html
>
>
Check this old thread
http://tapestry.1045711.n5.nabble.com/t5-3-1-Heads-up-for-special-form-field-names-similar-to-InternalSymbols-PRE-SELECTED-FORM-NAMES-td5101482.html
I understand you are saying that when the TextField id is changed,
everything else works, including the ajax part. Well althou
