I have an Entity A which is Immutable, and an Entity B which is mutable. There is a many to many relationship defined between A and B. Now I have a collection of Entity B which I have to associate with Entity A.
If I write
session.update(a)
where a is an instance of Entity A
my relationship is not getting saved as it doesnt fire any insert queries for relationship. I know I can do it other way round(saving Entity B one by one). But I just wanted to know if there is any smoother way to do this.
I hope I am not missing any point here.

Thanks
Lal

Mind posting your code + mapping?

And while you're coming up with that, I'll go ahead and direct you to some cascading documentation because it sounds like it might help. You might also read about the "inverse" attribute in Chapter 7 of the reference guide.

Actually my assumption was wrong. I was thinking that the cause for this issue is Immutablity of the Entity A.
But this was happening because of the inverse attribute in the A.hbm.xml which has the value true.
But again I can't modify the value for inverse, as in my case, *hbm.xml files are autogenerated (with Andromda). And it seems andromda doesnt provide a good logical implementation for that. So I am saving the relationship from Entity B side now, which works.

Thanks for the help.

By the way, if anybody knows how to fix this issue with Andromda, please let me know.

Thanks.

Lal[/b]