You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by ad...@apache.org on 2016/07/12 19:41:41 UTC
wicket git commit: WICKET-6199 Update Guide: Pagemaps are gone
Repository: wicket
Updated Branches:
refs/heads/master b2f715421 -> 1dac2e866
WICKET-6199 Update Guide: Pagemaps are gone
Project: http://git-wip-us.apache.org/repos/asf/wicket/repo
Commit: http://git-wip-us.apache.org/repos/asf/wicket/commit/1dac2e86
Tree: http://git-wip-us.apache.org/repos/asf/wicket/tree/1dac2e86
Diff: http://git-wip-us.apache.org/repos/asf/wicket/diff/1dac2e86
Branch: refs/heads/master
Commit: 1dac2e866cd26156e18726718bfd76f009943046
Parents: b2f7154
Author: Andrea Del Bene <ad...@apache.org>
Authored: Tue Jul 12 21:41:04 2016 +0200
Committer: Andrea Del Bene <ad...@apache.org>
Committed: Tue Jul 12 21:41:04 2016 +0200
----------------------------------------------------------------------
.../src/docs/guide/bestpractices/bestpractices_2.gdoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/wicket/blob/1dac2e86/wicket-user-guide/src/docs/guide/bestpractices/bestpractices_2.gdoc
----------------------------------------------------------------------
diff --git a/wicket-user-guide/src/docs/guide/bestpractices/bestpractices_2.gdoc b/wicket-user-guide/src/docs/guide/bestpractices/bestpractices_2.gdoc
index 9531968..63e99f0 100644
--- a/wicket-user-guide/src/docs/guide/bestpractices/bestpractices_2.gdoc
+++ b/wicket-user-guide/src/docs/guide/bestpractices/bestpractices_2.gdoc
@@ -1,3 +1,3 @@
-In contrast to Struts, Wicket pages and components are no singletons, they are stateful and session-scoped. This enables us to store user-specific information within pages and components. The information should be stored in fields. This way you can access the information within a class while avoiding long method signatures only for passing the same information around. Instances of components can exist for several requests. For example, a page with a form which gets submitted and produces validation errors uses the same page instance. Furthermore the same page instance gets used when the user presses the back button of the browser and resubmits this formular again. Information which gets passed by the constructor should be assigned to fields (normally this must be models). When storing information in fields you should consider that the information is serializable, because the pages are stored in Wicket's page map. By default the page map stores the pages on the hard disk. A non-seria
lizable object leads to @NullPointerExceptions@ and @NonSerializableExceptions@. Additionally, big data (like binary stuff) should not be stored directly in fields because this can cause performance losses and memory leaks during serialization and deserialization. In this case, you should use the @LoadableDetachableModel@ which can be assigned to a field because this provides an efficient mechanism to load and detach data.
\ No newline at end of file
+In contrast to Struts, Wicket pages and components are no singletons, they are stateful and session-scoped. This enables us to store user-specific information within pages and components. The information should be stored in fields. This way you can access the information within a class while avoiding long method signatures only for passing the same information around. Instances of components can exist for several requests. For example, a page with a form which gets submitted and produces validation errors uses the same page instance. Furthermore the same page instance gets used when the user presses the back button of the browser and resubmits this formular again. Information which gets passed by the constructor should be assigned to fields (normally this must be models). When storing information in fields you should consider that the information is serializable, because the pages are stored using Java serialization. By default the page map stores the pages on the hard disk. A non-s
erializable object leads to @NullPointerExceptions@ and @NonSerializableExceptions@. Additionally, big data (like binary stuff) should not be stored directly in fields because this can cause performance losses and memory leaks during serialization and deserialization. In this case, you should use the @LoadableDetachableModel@ which can be assigned to a field because this provides an efficient mechanism to load and detach data.
\ No newline at end of file