NH-3491 - Component mapping when mapping by code doesn't allow leaving unmapped properties in the component that were mapped somewhere else

[nhibernate-bot]

Fredy Treboux created an issue — 29th June 2013, 0:42:43:

Currently, when mapping a Component by code (conformist, at least), the mapping assumes that all properties of the component class that are ever mapped will be mapped every time. Of course, properties of the component that are not mapped are not taken into account.
This is a problem, because if in one case we map a property of a component and in another we don't, the mapping assumes it has to fill it anyways but leaving all properties (e.g. Column) as default, which may crash everywhere, for example in queries.

My current "workaround" for this is to map every property of the component that is mapped elsewhere and doesn't apply to this mapping as a null formula.

It may seem that the requirement to partially fill a component class may be odd, but still this seems like a bug, specially since it works as expected with xml mappings.

Test case coming shortly.

---

Fredy Treboux added a comment — 29th June 2013, 0:49:55:

Adding a test case for the behavior explained earlier.

---

Alexander Zaytsev added a comment — 24th November 2014, 10:44:19:

PR with test case #381

[SlyNet]

If its that trivial would it rude to ask fixing it? Its very annoying one

[fredericDelaporte]

NHibernate is open source software, fully contributed by volunteers. You are more than welcome to contribute a fix yourself, especially since no other volunteer seems to have fixing this one on its own personal list.

See Contributing.

p:Trivial means it has the lowest priority. It does not mean that it is trivial to fix.

[gliljas]

Maybe we should rename that tag, since the word "trivial" really can't have any other meaning than that is easy to fix. :)

[hazzik]

Done @gliljas @fredericDelaporte