[
http://jira.jboss.com/jira/browse/EJBTHREE-774?page=all ]
Emmanuel Bernard resolved EJBTHREE-774.
---------------------------------------
Fix Version/s: EJB 3.0 RC11 - FD
Resolution: Done
Assignee: Emmanuel Bernard
We generally don't describe inernal algorithms since they may change and since the
user should not consider them as "public API" .I've added that the user must
to mess up with the version number. Fixed for HAN 3.2.2
Please update the hibernate annotation documentation for @Version to
indicate behaviour of null attribute
---------------------------------------------------------------------------------------------------------
Key: EJBTHREE-774
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-774
Project: EJB 3.0
Issue Type: Task
Components: Documentation
Affects Versions: EJB 3.0 RC9 - FD
Environment: all
Reporter: Chris Hornsey
Assigned To: Emmanuel Bernard
Priority: Minor
Fix For: EJB 3.0 RC11 - FD
The hibernate annotation documentation has the following section:
2.2.1.2. Versioning for optimistic locking
Please indicate in this documentation, that if an attribute that is versioned has a null
value the entity will always be considered transient irregardless of other values
typically analyzed to make the transient determination.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira