Is the intended result:
1. A new domain object called Address
2. Address has a state property with getters/setters
3. An address property in the "outer" domain object with getters/setters
4. The outer object creates a new Address object in its constructor
Seems like a lot to infer from a column override. I think I'd rather have some more robust syntax - but I want to make sure I understand the basic idea first.
Jeff Butler
On 3/1/06, Mark Bennett <[EMAIL PROTECTED]> wrote:
DISCLAIMER: I know that the address information should have been in a different table but that is the reason that I need iBatis.
I would like to be able to define a column override like this.
<columnOverride column="ST" property="address.state"/>
If I do this it will generate the mappings and sql statements that I *do* want.
...
<result column="ST" jdbcType="VARCHAR" property="address.state"/>
...
ST = # address.state:VARCHAR#,
...
But is has a side effect of doing this to my class.
private String address.state;
I think this could be useful for a lot of people that want to push data down into other objects. Also it doesn't seem too far from being able to do it.
Thanks much again!
Mark
