Hi !

I'm a beginner with nhibernate and i try to use it in one of my projects. I get some trouble because my business class was not visible outside of my assembly. I accessed to them thanks to interface.
My first question is the following :

Is it possible to persist object defined by an interface ?

To avoid this, I changed the visibility of my business classes. Then i tried to create my hbm.xml files and i'm using some attributes that i don't understand :

cascade

inverse

lazy

My second question :

Is it possible to explain me what these attributes really do ?

Thanks in advance

Vincent.

PS : I'm using v1.2 Alpha1

I guess it would be wise to consult the documentation for those attributes http://nhibernate.sourceforge.net/nh-do ... ation.html

Yes I've already printed it but i can't find a clear definition of these terms.
Here is what i found for "cascade" :

What does 'cascaded' mean ?

For inverse :

What is an end of bidirectionnal association ... If it is bidirectionnal, there is no end ?

....


And i didn't find anything about interface. Is it possible de make it persistent ?

Thanks,

Vincent.[/quote]

"Cascade" is essentially a strategy you choose for persisting the Object Graph in your entities. So if you have a Person class that has an IList of Phone objects, you only need to ISession.SaveOrUpdate(personObject) and the child objects will be persisted also (if you selected Cascade="all"). I

t is important for you to understand who "owns" a relationship in a bidirectional relationship. In our example, "Person" would either .Add or .Remove the Phone objects to its Phones collection and so persist just fine. If you tried to simply make Person = personObject within your Phone object, you'll get an exception because Phone isn't the owner on the relationship.

You don't persist interfaces per se since they obviously don't hold values...they are contracts. The implementations of those interfaces are what are persisted.

Hope this helps
MIKE

Thanks a lot for your help :)

Vince.

Youre welcome!