A bug has been opened (number 1441312) and recently
deleted on this subject.
The problem can be explained with the following mapping :
In this example, the custom set method is supposed to
be defined for the "addresses" attribute (this is the
way we interpreted it) and no custom methods can be
defined for the society attribute.
As Franz said in the bug 1441312 comments, there is no
way to detect if a custom set or get method has been
defined for the intermediate attributes of the
deep-mapping (only "society" here). So for those, only
standard javabean accessors can be accepted.
Currently, mixed deep-mapping and custom set methods is
not allowed (it does not works).
Is it possible to accept set/get methods on a
deep-mapping field and use these methods only for the
last attribute of the deep-field chain of attributes
(all intermediate attributes must then respect javabean
rules for get/set methods) instead of prevent the mix ?
Such a rule would be sufficient for us.
Log in to post a comment.