I thought this is in his private 1.3 branch
On 9/26/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> we have been talking about letting it access private fields directly so you
> dont have to implement the pesky getters/setters.
>
> not sure if that has been committed yet. johan?
>
>
> -Igor
>
>
>
we have been talking about letting it access private fields directly so you dont have to implement the pesky getters/setters.not sure if that has been committed yet. johan?-Igor
On 9/26/06, Patrick Angeles <[EMAIL PROTECTED]> wrote:
Thanks... that's exactly what I was looking for ;)So I take it, Co
Thanks... that's exactly what I was looking for ;)So I take it, CompoundPropertyModel does not require get/set methods to access/mutate properties? (I think I have to make "login" public, in this case?)
On 9/26/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
it really depends on the reusability you wa
it really depends on the reusability you want.do you want loginform to be reusable?do you want loginmodel to be reusable?if the answer to both is no then you can just doclass Login extends WebPage {
private String login; private String password; public Login() { Form form=new Form("form
I wrote the following code with Forms and Models... is there a more compact
way of doing this? Would it be a bad idea to combine the form class and the
model class into one and have it reference itself as a Model object?
Also, since I am not so concerned about holding on to the model's state
(log
