Re: Accessing autoconnect-parameter by reference, not by value

2009-11-09 Thread Alexey Hanin
Oh, I finally found what I was doing wrong :) Just misread the documentation. The parameter bound to the property which is named exactly as component. In fact only one property can be bound. On Mon, Nov 9, 2009 at 2:14 PM, Alexey Hanin wrote: > Seriously, guys? Anyone? > > On Sun, Nov 8, 2009 at

Re: Accessing autoconnect-parameter by reference, not by value

2009-11-09 Thread Alexey Hanin
Seriously, guys? Anyone? On Sun, Nov 8, 2009 at 8:55 AM, Alexey Hanin wrote: > Hmm... Seems like autoconnect does not work for me as I expect. > > I checked in setupRender() inside EditorComponent and found that > 'entity' is null, while Page.setupRender() assigns new value to its > same named pr

Re: Accessing autoconnect-parameter by reference, not by value

2009-11-07 Thread Alexey Hanin
Hmm... Seems like autoconnect does not work for me as I expect. I checked in setupRender() inside EditorComponent and found that 'entity' is null, while Page.setupRender() assigns new value to its same named property. What am I doing wrong? On Sat, Nov 7, 2009 at 7:50 PM, Alexey Hanin wrote: >

Accessing autoconnect-parameter by reference, not by value

2009-11-07 Thread Alexey Hanin
Hello, Recently I found that autoconnect-parameters are being copied instead of being set as reference to parent parameter. What I want is to implement various editor-components containing BeanEditForm accessing parent property. class Page { @Property private EntityObject entity; void onSuc

Accessing autoconnect-parameter by reference, not by value

2009-11-07 Thread Alexey Hanin
Hello, Recently I found that autoconnect-parameters are being copied instead of being set as reference to parent parameter. What I want is to implement various editor-components containing BeanEditForm accessing parent property. class Page { @Property private EntityObject entity; void on