EditView: handling of orphan removal & ignoring errors for hidden fields

[ikostenko]

When editing a record of an entity where @OneToMany field has orphanRemoval = true, an alert is displayed containing the following message
"A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance: org.lightadmin.demo.model.Customer.addresses; nested exception is org.hibernate.HibernateException: A collection with cascade="all-delete-orphan" was no longer referenced by the owning entity instance: org.lightadmin.demo.model.Customer.addresses"

To reproduce, try to save any entry of "Customer" entity.

Question 1. What should be the expected result?
Question 2. adresses field is not specified in Form View of CustomerAdministration. Shouldn't errors for fields hidden from Form View be ignored?

[aliubunia]

Fixed by dd430fb
We will experience constraint violation if orphanRemoval=true and any element removed from the association is still referenced from other areas of the schema (no implicit cascading)