This discussion came out of the recent hibernate wicket-stuff activity. For my behaviors/validators/listeners to work, I need to have visibility into the PropertyModel's internal configuration. In particular, I need access to the: * propertyExpression configured for a particular form component * targetClass that this model is using
I've worked around this for now by creating a subclass (HibernateAnnotationPropertyModel), but it's pretty restrictive and unfortunate that users are forced to use this non-standard property model. Any opinions on a better way to go about this, or change the wicket-core to support this use case? http://wicket-stuff.svn.sourceforge.net/viewvc/wicket-stuff/trunk/wicketstuff-hibernate-behavior/
