We want to restrict visibility for some @Entity setters, declaring them with private or package level accessibility.
IDEA marks the setters as unused.
However, they are used by Hibernate. When the entity is loaded, Hibernate will initialize the entity using the (restricted scope) setters.
It would be better if setters referring to a persistent property of an entity were excluded from usage checks.
Description
Using Hibernate 3.x with JPA annoatations.
We want to restrict visibility for some @Entity setters, declaring them with private or package level accessibility.
IDEA marks the setters as unused.
However, they are used by Hibernate. When the entity is loaded, Hibernate will initialize the entity using the (restricted scope) setters.
It would be better if setters referring to a persistent property of an entity were excluded from usage checks.
Agree, but of course only for persistent properties where the accessors are annotated.
If the entity uses annotations on the fields then the setters are indeed unused.
Stephen Friedrich - 15 Aug 08 11:24 Agree, but of course only for persistent properties where the accessors are annotated.
If the entity uses annotations on the fields then the setters are indeed unused.
Usability Problem
Open
Don't mark unused setters grey for entity persistent properties
If the entity uses annotations on the fields then the setters are indeed unused.