Hello,
There is an orm.xml mapping with xml-mapping-metadata-complete and
access specified as "PROPERTY".
The persistence class mapping is defined and working.
Now when some getter is added to the persistent entity class, it gets
picked up and mapped by default to a column which does not exist. This
can be fixed using transient element in the entity definition or by
adding @Transient annotation to the getter.
The question is, is there a way to prevent this w/o using transient?
Since the meta data is complete, and is really completely defined in the
entity element, why is anything not defined in the attributes element of
the mapping being picked up?
In other words, when the mapping is explicitly and completely defined in
the orm.xml, why is it trying to map other unmapped properties over
zealously and can this be avoided such that anything not defined in the
mapping should be treated as transient automatically.
Thanks,
Prashant