Community
Participate
Working Groups
i'm not exactatly sure where to place this bug, as this is a bug between to plugins. save actions allows you to append final keyword on fields which it recognizes re only initilized once. while this is true in most case, trying to do so on an entity would yield an error from dali complianing that you cannot set final on attributes. since jpa is a standard in se, i believe it's jdt's resposibility to identify it's inside an entity and not apply these rules on it. (or at least allow prefrences swich to it), i also think that it should open up extension point to allow other providers define if should be modifed as well.
> since jpa is a standard in se, JPA is part of EE not SE. There's not much we can do here. I suggest you disable that save action. Markus, I suggest to close as WONTFIX.
while it may part of jee, it can be used as part of desktop applications.
(In reply to comment #1) > Markus, I suggest to close as WONTFIX. +1. We will not add JPA specific features to JDT. elhanan, don't the attributes (which are private fields) have getters and setters ? If a private field has a setter the save action or cleanup should anyway skip that field.
