Comment 10 for bug 500163
Revision history for this message
| Timo Westkämper (timo-westkamper) wrote | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Ok, maybe the entityAccessors flag could set the visibility of the entity fields to protected.
Anatoly and Cyberax, what do you think? Does this approach fit your Querydsl usage style?
We had accessors for entity fields in earlier version of Querydsl, but removed them, because we wanted a consistent way to access properties in Querydsl types.
QueryInit is a good tool to avoid NPE:s, but entity accessors can be activated as well. Protected entity fields would be consistent with this approach, IMHO. Literal fields will stay fields, they are eagerly initialized anyway.