What are we going to do with this?
In my opinion these things should be fixed in CompoundPropertyModel:
* Use consistent naming. Currently, the field is called target, but
the the constructor argument is called model. We need to find the best
name and use this throughout the class.
* Once we
getObject() of CompoundPropertyModel itself == the target.
On 3/21/07, Nathan Hamblen [EMAIL PROTECTED] wrote:
Now that 2.0-style compound models are in 1.x snapshots, I have a
question for people that have been using them: how do you work without
CompoundPropertyModel.getNetstedModel()? For
ahh wait i see that the getObject does a recursive call if it is a model
So you want the internal model instead of the real model object ?
johan
On 3/21/07, Johan Compagner [EMAIL PROTECTED] wrote:
getObject() of CompoundPropertyModel itself == the target.
On 3/21/07, Nathan Hamblen
Yes, that's it.
Johan Compagner wrote:
ahh wait i see that the getObject does a recursive call if it is a model
So you want the internal model instead of the real model object ?
johan
On 3/21/07, * Johan Compagner* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
getObject()
Now that 2.0-style compound models are in 1.x snapshots, I have a
question for people that have been using them: how do you work without
CompoundPropertyModel.getNetstedModel()? For me, this is often a special
model that I want to do something with, but in the newer style it's
called the
