Resolve properties using reflection
-----------------------------------
Key: WICKET-2347
URL: https://issues.apache.org/jira/browse/WICKET-2347
Project: Wicket
Issue Type: Improvement
Reporter: Ricardo Mayerhofer
PropertyResolver uses getter and setter to resolve attributes. This has some
disavantages, because it forces application model to follow java bean spec.
In a CRUD application it's nice. But you may face some trouble in more complex
application, mainly because java beans leads to anemic domain models and
encapsulation violation.
Some times you may have a class that has a immutable field ( e.g. value object
from P of EAAA). So it is interesting to use constructor to set this field.
Take money for example:
class Money
{
Money( double value )
{
this.value = value;
}
...
}
If I need to create a front-end for this class I will have problems, because it
doens't have a setter and so I will have to change my model for wicket purposes.
I find pretty interesting hibernate concept of transparent persistent, this
means that I do not have to change my model to fit hibernate. The same idea
applied to wicket would be nice.
What do you think?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
