From cb091204f4bfc7f9971fc296903f7bc2a163f085 Mon Sep 17 00:00:00 2001
From: Reinier Zwitserloot <reinier@tipit.to>
Date: Tue, 1 Sep 2009 00:19:28 +0200
Subject: Fixed documentation, specifically: added eclipse help system fix to
 the changelog, and added some documentation on the special handling of
 @NonNull/@NotNull/@Nullable for Data and Getter/Setter on the website docs.

---
 website/features/GetterSetter.html | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'website/features/GetterSetter.html')

diff --git a/website/features/GetterSetter.html b/website/features/GetterSetter.html
index 2ad0f1ec..618a6b0a 100644
--- a/website/features/GetterSetter.html
+++ b/website/features/GetterSetter.html
@@ -51,6 +51,10 @@
 				</p><p>
 				Any variation on <code>boolean</code> will <em>not</em> result in using the <code>is</code> prefix instead of the <code>get</code> prefix; for example,
 				returning <code>java.lang.Boolean</code> results in a <code>get</code> prefix, not an <code>is</code> prefix.
+				</p><p>
+				Any annotations named <code>@NonNull</code> or <code>@NotNull</code> (case insensitive) on the field are interpreted as: This field must not ever hold
+				<em>null</em>. Therefore, these annotations result in an explicit null check in the generated setter. Also, these
+				annotations (as well as any annotation named <code>@Nullable</code>) are copied to setter parameter and getter method
 				</p>
 			</div>
 		</div>
-- 
cgit