Hi,

I am building an application that uses NHibernate.

The web layer makes a remote call to the business layer through remoting for a business object. The business object is passed by value back to the web layer where it is modified, after which I want to send it back to the remote business layer so that I can call session.update() on the business object.

The problem I get is that NHibernate does not recognize that the items in the collection (which is marked lazy=false) are not brand new but should also be updates.

A primary-key already exists exception gets thrown.

Is there any way to correctly do updates across sessions with remoting and cascading collections?

neverming, I found the problem. It had to do with the composite key unsaved-value property. The work around I did was to use an autogenerated id for the primary key and use a unique constraint to make sure the composite key was unique.