Hi Mikhail,
Click uses OGNL to bind the field's value which coerces the value to 0.
Do note that in my exp Bindable has proven very problematic in practice. One of
those things
implicit behaviors which looks great at face value but hinders maintenance. I
suggest you don't use
it. In click.xml you can switch it off with autobinding="none".
kind regards
Bob
On 2011/03/18 20:23 PM, Ingie wrote:
> Hi all,
>
> First of all i like Click, thank you for great work guys.
>
> Can't understand @Bindable behavior:
>
> class MyPage extends BorderPage {
>
> @Bindable protected Long id;
>
> public void onInit() {
> sout(id);
> }
>
> }
>
> Output:
>
> for my-page.htm?id=0 -> 0 (it's ok)
> for my-page.htm -> 0 (why?)
>
> Is it bug or feature?
>
> I run 2.3.0-RC1
>
> Kind regards,
> Mikhail
>
