[
https://jira.jboss.org/jira/browse/JBIDE-3842?page=com.atlassian.jira.plu...
]
Vitali Yemialyanchyk commented on JBIDE-3842:
---------------------------------------------
"255 is the default" in the label - just a hint to the user - empty field means
255, I think - there is a place - so we can put hint where -
if you find this excessive - i'll exclude this;
"What are the rules for the "optimistic locking" generation?"
"Enable optimistic locking" - sounds to general for just add annotation for
version property - so currently the rules are:
if "Enable optimistic locking" checked:
a) if there is property "version" - i annotate it or getter
b) if there is no property "version" - i create it and getter/setter and
annotate it or getter
c) if there is @MappedSuperclass with "version" - base class for the current
class - i do not insert "version" into the current class
I'll create new issue for this - when it be ready - still I should test this
functionality.
Additional annotations support for "Generate Hibernate/JPA
annotations"
-----------------------------------------------------------------------
Key: JBIDE-3842
URL:
https://jira.jboss.org/jira/browse/JBIDE-3842
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.0.0.CR2
Reporter: Vitali Yemialyanchyk
Assignee: Vitali Yemialyanchyk
Priority: Minor
Fix For: LATER
Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg
currently I see the sence add @MappedSuperclass annotation for base class instead of or
together with @Entity annotation;
in case when the class has offsprings - there is a big sence to have @MappedSuperclass
annotation by default.
Some other ideas?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira