Hi All,


With you all guys' help and explanations, I'm "almost" done to my basic needs on setting one-to-many relationships.


My Class ....
public class LegalPerson
{

private Address[] _addresses;

public virtual Address[] addresses
{
get { return _addresses; }
set { _addresses = value; }
}

}


Implementation code of the class..............The error is at the line : "Address[] addrs = new Address[]{ad1, ad2};":

LegalPerson lp = new LegalPerson();
lp.name = "LegalPersonFact";

Address ad1 = new Address();
ad1.bldg = "Build1";
Address ad2 = new Address();
ad2.bldg = "Build2";

sess.Save(ad1);
sess.Save(ad2);

Address[] addrs = new Address[]{ad1, ad2};
lp.addresses = addrs;

sess.Save(lp);
.............................

I'm not familiar with C#. Should I set value to an object array like this?

Maybe is it necessary that I need to follow some other book's getter/setter approach like :

public Address[] getAddresses() {
return addresses;
}

public Address[] setAddresses(Address[] addresses) {
this.addresses = addresses;
}

Is it a must in my case? Even so, I don't know my NHibernate seems not working when I using the that approach (vs. my approach just to assign values to the properties themselves)


Thanks a lot!
jL

NHibernate requires the property to be from "correct" type in case of association, depending on the mapping, ILIst, ICollection, Iesi.Collection.ISet, IDictionary, ... (maybe I missed something)

Anyway, it is not adviseable to to use array proeprties like You do. In followng code

Address[] addrs = person.addresses;
addr[0] = new Address();

the content of person.addresses is changed.

You might want to run fxcop on Your assembly and see what it thinks about different constructs.

Gert

You also shouldnt use a setter for the collection property (almost always). Use a read-only property and use access="nosetter.camelcase" (for example) in your mapping file.