Hi Igor and Eelco,
Sorry, for interventing in your discussion :)
May java annotations can help us?
Say [EMAIL PROTECTED]/Write
or [EMAIL PROTECTED] or ever to protect all bean.
It would protect the field from accidently access in Wicket models
without any assumption on set/get functions.
How it lead to additional lag on processing the model, i can't estimate.
Cheers,
Oleg
>> all i asked johan to do was to tweak property resolver to allow access to
>> private stuff. i was under the impression that the property resolver always
>> tries to access the getter/setter first, then the field.
>> half of this thread you are arguing that we shouldnt allow access to private
>> fields/methods and half of it you are arguing that we should but try the
>> getter first, so im pretty confused.
> No, again, I'm arguing to *either* allowing access to all private, or
> don't allow it at all. I am not against private member access per se,
> just want it to be consistent.
> Eelco
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
С уважением,
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]