I'd be +1 for that. Now that Hibernate, Spring, etc all allow access
to private fields, I wouldn't feel bad about supporting that.
Eelco
On 9/4/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> should we let our property models access to private fields?
>
> often i have constructs like
>
> class MyPage .... {
> private String str;
>
> ....
>
> new PropertyModel(this, "str");
>
> }
>
> it sucks to have public getters and setters for "str" because it breaks
> encapsulation and beacuse i hate that they take up space in my files :)
>
> what do you all think?
>
> -Igor
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
> _______________________________________________
> Wicket-develop mailing list
> Wicket-develop@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
>
>
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
