Hi, If you don't mind me following up on your comment...
> Personally, I rarely encounter serialization issues. None of our domain > objects implement Serializable. They can only be used with > LoadableDetachableModels that only store the identifier. > >> >> Would you mind to elaborate on this a bit? What do you do in your forms? How do you handle state there? Do you use view models that are serializable? Do you keep state in local variables and propagate it to the domain object in every request after it is reloaded? We often use serializable domain objects so that keeping state on the object is simple. For example if you have an ajax link that increments a property of the domain object, you simply increment the property and rely on the object being serialized for keeping state. Cheers Marios
