Repository: wicket Updated Branches: refs/heads/master 0c089b482 -> 0b810892d
http://git-wip-us.apache.org/repos/asf/wicket/blob/8929074f/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_2.gdoc ---------------------------------------------------------------------- diff --git a/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_2.gdoc b/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_2.gdoc index d8c153e..268b1ed 100644 --- a/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_2.gdoc +++ b/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_2.gdoc @@ -49,7 +49,7 @@ If we press the back button the page version previously rendered (and serialized For more details about page storing you can take a look at paragraph "Page storing" from chapter "Wicket Internals". The content of this paragraph is from wiki page https://cwiki.apache.org/confluence/display/WICKET/Page+Storage. {note} -As we have stated at the beginning of this chapter, page versions are stored using Java serialization, therefore every object referenced inside a page must be serializable. In paragraph 9.6 we will see how to overcome this limit and work with non-serializable objects in our components using detachable Wicket models. +As we have stated at the beginning of this chapter, page versions are stored using Java serialization, therefore every object referenced inside a page must be serializable. In [paragraph 11.6|guide:modelsforms_6] we will see how to overcome this limit and work with non-serializable objects in our components using detachable Wicket models. h3. Using a specific page version with PageReference @@ -62,7 +62,7 @@ PageReference pageReference = new PageReference(3); Page page = pageReference.getPage(); {code} -To get the related page instance we must use method getPage. +To get the related page instance we must use the method getPage. h3. Turning off page versioning @@ -136,4 +136,4 @@ public void init() } {code} -The page class provided as custom error page must have a public constructor with no argument or a constructor that takes as input a single PageParameters argument (the page must be bookmarkable as described in paragraph 8.1.1). +The page class provided as custom error page must have a public constructor with no argument or a constructor that takes as input a single PageParameters argument (the page must be bookmarkable as described in [paragraph 10.1.1|guide:urls_1]). http://git-wip-us.apache.org/repos/asf/wicket/blob/8929074f/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_3.gdoc ---------------------------------------------------------------------- diff --git a/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_3.gdoc b/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_3.gdoc index 3004164..ee00716 100644 --- a/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_3.gdoc +++ b/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_3.gdoc @@ -1,10 +1,10 @@ -Wicket makes it very easy to build stateful pages, but sometimes we might want to use an âold schoolâ stateless page that doesn't keep memory of its state in the user session. For example consider the public area of a site or a login page: in those cases a stateful page would be a waste of resources or even a security threat, as we will see in paragraph 10.9. +Wicket makes it very easy to build stateful pages, but sometimes we might want to use an âold schoolâ stateless page that doesn't keep memory of its state in the user session. For example consider the public area of a site or a login page: in those cases a stateful page would be a waste of resources or even a security threat, as we will see in paragraph [paragraph 12.10|guide:forms2_10]. In Wicket a page can be stateless only if it satisfies the following requirements: -# it has been instantiated by Wicket (i.e. we don't create it with operator new) using a constructor with no argument or a constructor that takes as input a single PageParameters argument (class PageParameters will be covered in chapter 8). +# it has been instantiated by Wicket (i.e. we don't create it with operator new) using a constructor with no argument or a constructor that takes as input a single PageParameters argument (class PageParameters will be covered in [chapter 10.1|guide:urls_1]). # All its children components (and behaviors) are in turn stateless, which means that their method isStateless must return true. The first requirement implies that, rather than creating a page by hand, we should rely on Wicket's capability of resolving page instances, like we do when we use method setResponsePage(Class page). http://git-wip-us.apache.org/repos/asf/wicket/blob/8929074f/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_4.gdoc ---------------------------------------------------------------------- diff --git a/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_4.gdoc b/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_4.gdoc index 18d2c2d..381820f 100644 --- a/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_4.gdoc +++ b/wicket-user-guide/src/docs/guide/versioningCaching/versioningCaching_4.gdoc @@ -2,4 +2,4 @@ In this chapter we have seen how page instances are managed by Wicket. We have learnt that pages can be divided into two families: stateless and stateful pages. Knowing the difference between the two types of pages is important to build the right page for a given task. -However, to complete the discussion about stateless pages we still have to deal with two topics we have just outlined in this chapter: class PageParameters and bookmarkable pages. The first part of chapter 10 will cover these missing topics. \ No newline at end of file +However, to complete the discussion about stateless pages we still have to deal with two topics we have just outlined in this chapter: class PageParameters and bookmarkable pages. The first part of [chapter 10|guide:urls] will cover these missing topics. http://git-wip-us.apache.org/repos/asf/wicket/blob/8929074f/wicket-user-guide/src/docs/guide/wicketstuff/wicketstuff_5.gdoc ---------------------------------------------------------------------- diff --git a/wicket-user-guide/src/docs/guide/wicketstuff/wicketstuff_5.gdoc b/wicket-user-guide/src/docs/guide/wicketstuff/wicketstuff_5.gdoc index 0a810a1..f3647b3 100644 --- a/wicket-user-guide/src/docs/guide/wicketstuff/wicketstuff_5.gdoc +++ b/wicket-user-guide/src/docs/guide/wicketstuff/wicketstuff_5.gdoc @@ -2,7 +2,7 @@ Module wicketstuff-inmethod-grid implements a sophisticated grid-component with class com. inmethod.grid.datagrid.DataGrid. -Just like pageable repeaters (seen in paragraph 11.4) DataGrid provides data pagination and uses interface IDataProvider as data source. In addition the component is completely ajaxified: +Just like pageable repeaters (seen in [paragraph 13.4|guide:repeaters_4]) DataGrid provides data pagination and uses interface IDataProvider as data source. In addition the component is completely ajaxified: !inmethod-grid1.png!
