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 2013/12/14 18:19:56 UTC
svn commit: r1550944 [2/3] - in
/wicket/common/site/trunk/_site/guide/guide/src/docs/guide: ./ chapter10/
chapter11/ chapter12/ chapter13/ chapter14/ chapter15/ chapter16/
chapter17/ chapter18/ chapter19/ chapter20/ chapter21/ chapter6/ chapter7/
chapt...
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_9.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_9.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_9.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_9.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-Wicket loads application's resources delegating this task to a resource locator represented by interface org.apache.wicket.core.util.resource.locator.IResourceStreamLocator. To retrieve or modify the current resource locator we can use the getter and setter methods defined by setting interface IResourceSettings:
+Wicket loads application's resources delegating this task to a resource locator represented by interface @org.apache.wicket.core.util.resource.locator.IResourceStreamLocator@. To retrieve or modify the current resource locator we can use the getter and setter methods defined by setting interface IResourceSettings:
{code}
//init application's method
@@ -17,7 +17,7 @@ The default locator used by Wicket is cl
The default implementation of IResourceFinder used by Wicket is ClassPathResourceFinder which searches for resources into the application class path. This is the implementation we have used so far in our examples. However some developers may prefer storing markup files and other resources in a separate folder rather than placing them side by side with Java classes.
-To customize resource loading we can add further resource finders to our application in order to extend the resource-lookup algorithm to different locations. Wicket already comes with two other implementations of IResourceFinder designed to search for resources into a specific folder on the file system. The first is class Path and it's defined in package org.apache.wicket.util.file. The constructor of this class takes in input an arbitrary folder that can be expressed as a string path or as an instance of Wicket utility class Folder (in package org.apache.wicket.util.file). The second implementation of interface IResourceFinder is class WebApplicationPath which looks into a folder placed inside webapp's root path (but not inside folder WEB-INF).
+To customize resource loading we can add further resource finders to our application in order to extend the resource-lookup algorithm to different locations. Wicket already comes with two other implementations of IResourceFinder designed to search for resources into a specific folder on the file system. The first is class Path and it's defined in package @org.apache.wicket.util.file@. The constructor of this class takes in input an arbitrary folder that can be expressed as a string path or as an instance of Wicket utility class Folder (in package @org.apache.wicket.util.file@). The second implementation of interface IResourceFinder is class WebApplicationPath which looks into a folder placed inside webapp's root path (but not inside folder WEB-INF).
Project CustomFolder4MarkupExample uses WebApplicationPath to load the markup file and the resource bundle for its home page from a custom folder. The folder is called markupFolder and it is placed in the root path of the webapp. The following picture illustrates the file structure of the project:
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter15/chapter15_2.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter15/chapter15_2.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter15/chapter15_2.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter15/chapter15_2.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-Our new component will extend the a built-in text field org.apache.wicket.extensions .markup.html.form.DateTextField which already uses a java.util.Date as model object and already performs conversion and validation for input values. Since the component must be self-contained, we must ensure that the JavaScript libraries it relies on (JQuery and JQuery UI) will be always available.
+Our new component will extend the a built-in text field @org.apache.wicket.extensions.markup.html.form.DateTextField@ which already uses a java.util.Date as model object and already performs conversion and validation for input values. Since the component must be self-contained, we must ensure that the JavaScript libraries it relies on (JQuery and JQuery UI) will be always available.
Starting from version 6.0 Wicket has adopted JQuery as backing JavaScript library so we can use the version bundled with Wicket for our custom datepicker.
@@ -83,7 +83,7 @@ Next, JQueryDateField tries to retrieve
To generate the relative URL for calendar icon, we load it as package resource reference and then we use Component's method urlFor to get the URL value (we have seen this method in paragraph 7.3.2).
-The last configuration instruction executed inside onInitialize is the instantiation of the custom converter used by our component. This converter is an instance of the built-in class org.apache.wicket.datetime.PatternDateConvert and must use the previously retrieved date format to perform conversion operations. Now to tell our component to use this converter we must return it overriding FormComponent's method getConverter.
+The last configuration instruction executed inside onInitialize is the instantiation of the custom converter used by our component. This converter is an instance of the built-in class @org.apache.wicket.datetime.PatternDateConvert@ and must use the previously retrieved date format to perform conversion operations. Now to tell our component to use this converter we must return it overriding FormComponent's method getConverter.
h3. Header contributor code
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_1.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_1.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_1.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_1.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-With class org.apache.wicket.behavior.Behavior Wicket provides a very flexible mechanism to share common features across different components and to enrich existing components with further functionalities. As the class name suggests, Behavior adds a generic behavior to a component modifying its markup and/or contributing to the header section of the page (Behavior implements the interface IHeaderContributor).
+With class @org.apache.wicket.behavior.Behavior@ Wicket provides a very flexible mechanism to share common features across different components and to enrich existing components with further functionalities. As the class name suggests, Behavior adds a generic behavior to a component modifying its markup and/or contributing to the header section of the page (Behavior implements the interface IHeaderContributor).
One or more behaviors can be added to a component with Component's method add(Behavior...), while to remove a behavior we must use method remove(Behavior).
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_2.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_2.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_2.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_2.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-With Wicket it's quite easy to build a callback URL that executes a specific method on server side. This method must be defined in a functional interface (i.e. an an interface that defines just one method) that inherits from built-in org.apache.wicket.IRequestListener and it must be a void method with no parameters in input:
+With Wicket it's quite easy to build a callback URL that executes a specific method on server side. This method must be defined in a functional interface (i.e. an an interface that defines just one method) that inherits from built-in @org.apache.wicket.IRequestListener@ and it must be a void method with no parameters in input:
{code}
public interface IMyListener extends IRequestListener
@@ -12,7 +12,7 @@ public interface IMyListener extends IRe
}
{code}
-To control how the method will be invoked we must use class org.apache.wicket.RequestListenerInterface. In Wicket is a common practice to instantiate this class as a public static field inside the relative callback interface:
+To control how the method will be invoked we must use class @org.apache.wicket.RequestListenerInterface@. In Wicket is a common practice to instantiate this class as a public static field inside the relative callback interface:
{code}
public interface IMyListener extends IRequestListener
@@ -33,7 +33,7 @@ Now that our callback interface is compl
Project CallbackURLExample contains a behavior (class OnChangeSingleChoiceBehavior) that implements a callback interface to update the model of an AbstractSingleSelectChoice component when user changes the selected option (it provides the same functionality of method want OnSelectionChangedNotifications).
-Instead of a custom callback interface, OnChangeSingleChoiceBehavior implements built-in interface org.apache.wicket.behavior.IBehaviorListener which is designed to generate a callback URL for behaviors. The callback method defined in this interface is onRequest() and the following is the implementation provided by OnSelectionChangedNotifications:
+Instead of a custom callback interface, OnChangeSingleChoiceBehavior implements built-in interface @org.apache.wicket.behavior.IBehaviorListener@ which is designed to generate a callback URL for behaviors. The callback method defined in this interface is onRequest() and the following is the implementation provided by OnSelectionChangedNotifications:
{code}
@Override
@@ -103,7 +103,7 @@ Implementing interface IBehaviorListener
h3. Wicket events infrastructure
-Starting from version 1.5 Wicket offers an event-based infrastructure for inter-component communication. The infrastructure is based on two simple interfaces (both in package org.apache.wicket.event) : IEventSource and IEventSink.
+Starting from version 1.5 Wicket offers an event-based infrastructure for inter-component communication. The infrastructure is based on two simple interfaces (both in package @org.apache.wicket.event@) : @IEventSource@ and @IEventSink@.
The first interface must be implemented by those entities that want to broadcast en event while the second interface must be implemented by those entities that want to receive a broadcast event.
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_3.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_3.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_3.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_3.gdoc Sat Dec 14 17:19:55 2013
@@ -2,7 +2,7 @@
Some components or resources may need to be configured before being used in our applications. While so far we used Application's init method to initialize these kinds of entities, Wicket offers a more flexible and modular way to configure our classes.
-During application's bootstrap Wicket searches for any properties file named wicket.properties placed in one of the classpath roots visible to the application. When one of these files is found, the initializer defined inside it will be executed. An initializer is an implementation of interface org.apache.wicket.IInitializer and is defined inside wicket.properties with a line like this:
+During application's bootstrap Wicket searches for any properties file named wicket.properties placed in one of the classpath roots visible to the application. When one of these files is found, the initializer defined inside it will be executed. An initializer is an implementation of interface @org.apache.wicket.IInitializer@ and is defined inside wicket.properties with a line like this:
{code}
initializer=org.wicketTutorial.MyInitializer
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_4.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_4.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_4.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_4.gdoc Sat Dec 14 17:19:55 2013
@@ -10,7 +10,7 @@ After we have established a JMX connecti
!JMX-console.png!
-JMX exposes application-specific informations using special objects called MBeans (Manageable Beans), hence if we want to control our application we must open the corresponding tab. The MBeans containing the application's informations is named org.apache.wicket.app.<filter/servlet name>.
+JMX exposes application-specific informations using special objects called MBeans (Manageable Beans), hence if we want to control our application we must open the corresponding tab. The MBeans containing the application's informations is named @org.apache.wicket.app.<filter/servlet name>@.
In our example we have used wicket.test as filter name for our application:
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_5.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_5.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_5.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter16/chapter16_5.gdoc Sat Dec 14 17:19:55 2013
@@ -2,7 +2,7 @@
So far, as markup source for our pages/panels we have used a static markup file, no matter if it was inherited or directly associated to the component. Now we want to investigate a more complex use case where we want to dynamical generate the markup directly inside component code.
-To become a markup producer, a component must simply implement interface org.apache.wicket.markup.IMarkupResourceStreamProvider. The only method defined in this interface is getMarkupResourceStream(MarkupContainer, Class<?>) which returns an utility interface called IResourceStream representing the actual markup.
+To become a markup producer, a component must simply implement interface @org.apache.wicket.markup.IMarkupResourceStreamProvider@. The only method defined in this interface is getMarkupResourceStream(MarkupContainer, Class<?>) which returns an utility interface called IResourceStream representing the actual markup.
In the following example we have a custom panel without a related markup file that generates a simple <div> tag as markup:
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_1.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_1.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_1.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_1.gdoc Sat Dec 14 17:19:55 2013
@@ -2,9 +2,9 @@
Wicket support for AJAX is implemented in file wicket-ajax-jquery.js which makes complete transparent to Java code any detail about AJAX communication.
-AJAX components and behaviors shipped with Wicket expose one or more callback methods which are executed when they receive an AJAX request. One of the arguments of these methods is an instance of interface org.apache.wicket.ajax.AjaxRequestTarget.
+AJAX components and behaviors shipped with Wicket expose one or more callback methods which are executed when they receive an AJAX request. One of the arguments of these methods is an instance of interface @org.apache.wicket.ajax.AjaxRequestTarget@.
-For example component AjaxLink (in package org.apache.wicket.ajax.markup.html) defines abstract method onClick(AjaxRequestTarget target) which is executed when user clicks on the component:
+For example component AjaxLink (in package @org.apache.wicket.ajax.markup.html@) defines abstract method @onClick(AjaxRequestTarget target)@ which is executed when user clicks on the component:
{code}
new AjaxLink("ajaxLink"){
@@ -58,7 +58,7 @@ new AjaxLink("ajaxLink"){
{code}
{warning}
-Repeaters component that have org.apache.wicket.markup.repeater AbstractRepeater as base class (like ListView, RepeatingView, etc...) can not be directly updated via AJAX.
+Repeaters component that have @org.apache.wicket.markup.repeater.AbstractRepeater@ as base class (like @ListView@, @RepeatingView@, etc...) can not be directly updated via AJAX.
-If we want to refresh their markup via AJAX we must add one of their parent containers to the AjaxRequestTarget.
+If we want to refresh their markup via AJAX we must add one of their parent containers to the @AjaxRequestTarget@.
{warning}
\ No newline at end of file
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_2.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_2.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_2.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_2.gdoc Sat Dec 14 17:19:55 2013
@@ -10,7 +10,7 @@ h3. Links and buttons
In the previous paragraph we have already introduced component AjaxLink. Wicket provides also the ajaxified versions of submitting components SubmitLink and Button which are simply called AjaxSubmitLink and AjaxButton. These components come with a version of methods onSubmit, onError and onAfterSubmit that takes in input also an instance of AjaxRequestTarget.
-Both components are in package org.apache.wicket.ajax.markup.html.form.
+Both components are in package @org.apache.wicket.ajax.markup.html.form@.
h3. Fallback components
@@ -18,11 +18,11 @@ Building an entire site using AJAX can b
h3. AJAX Checkbox
-Class org.apache.wicket.ajax.markup.html.form.AjaxCheckBox is a checkbox component that updates its model via AJAX when user changes its value. Its AJAX callback method is onUpdate(AjaxRequestTarget target). The component extends standard checkbox component CheckBox adding an AjaxFormComponentUpdatingBehavior to itself (we will see this behavior later in paragraph 16.3.3).
+Class @org.apache.wicket.ajax.markup.html.form.AjaxCheckBox@ is a checkbox component that updates its model via AJAX when user changes its value. Its AJAX callback method is onUpdate(AjaxRequestTarget target). The component extends standard checkbox component CheckBox adding an AjaxFormComponentUpdatingBehavior to itself (we will see this behavior later in paragraph 16.3.3).
h3. AJAX editable labels
-An editable label is a special label that can be edited by the user when she/he clicks on it. Wicket ships three different implementations for this component (all inside package org.apache.wicket.extensions.ajax.markup.html):
+An editable label is a special label that can be edited by the user when she/he clicks on it. Wicket ships three different implementations for this component (all inside package @org.apache.wicket.extensions.ajax.markup.html@):
* *AjaxEditableLabel*: it's a basic version of editable label. User can edit the content of the label with a text field. This is also the base class for the other two editable labels.
* *AjaxEditableMultiLineLabel*: this label supports multi-line values and uses a text area as editor component.
@@ -43,7 +43,7 @@ h3. Autocomplete text field
On Internet we can find many examples of text fields that display a list of suggestions (or options) while the user types a text inside them. This feature is known as autocomplete functionality.
-Wicket offers an out-of-the-box implementation of an autocomplete text field with component org.apache.wicket.extensions.ajax.markup.html.autocomplete.AutoCompleteTextField.
+Wicket offers an out-of-the-box implementation of an autocomplete text field with component @org.apache.wicket.extensions.ajax.markup.html.autocomplete.AutoCompleteTextField@.
When using AutoCompleteTextField we are required to implement its abstract method getChoices(String input) where the input parameter is the current input of the component. This method returns an iterator over the suggestions that will be displayed as a drop-down menu:
@@ -73,7 +73,7 @@ Wicket module wicket-examples contains p
h3. Modal window
-Class org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow is an implementation of a "modal window":http://en.wikipedia.org/wiki/Modal_window based on AJAX:
+Class @org.apache.wicket.extensions.ajax.markup.html.modal.ModalWindow@ is an implementation of a "modal window":http://en.wikipedia.org/wiki/Modal_window based on AJAX:
!modal-window-example-screenshot.png!
@@ -143,7 +143,7 @@ modalWindow.setWindowClosedCallback(new
h3. Tree repeaters
-Class org.apache.wicket.extensions.markup.html.repeater.tree.AbstractTree is the base class of another family of repeaters called tree repeaters and designed to display a data hierarchy as a tree, resembling the behavior and the look & feel of desktop tree components. A classic example of tree component on desktop is the tree used by nearly all file managers to navigate file system:
+Class @org.apache.wicket.extensions.markup.html.repeater.tree.AbstractTree@ is the base class of another family of repeaters called tree repeaters and designed to display a data hierarchy as a tree, resembling the behavior and the look & feel of desktop tree components. A classic example of tree component on desktop is the tree used by nearly all file managers to navigate file system:
!file-system-trees.png!
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_3.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_3.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_3.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_3.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-In addition to specific components, Wicket offers also a set of built in AJAX behaviors that can be used to easily add AJAX functionalities to existing components. As we will see in this paragraph AJAX behaviors can be used also to ajaxify components that weren't initially designed to work with this technology. All the following behaviors are inside package org.apache.wicket.ajax.
+In addition to specific components, Wicket offers also a set of built in AJAX behaviors that can be used to easily add AJAX functionalities to existing components. As we will see in this paragraph AJAX behaviors can be used also to ajaxify components that weren't initially designed to work with this technology. All the following behaviors are inside package @org.apache.wicket.ajax@.
h3. AjaxEventBehavior
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_4.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_4.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_4.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_4.gdoc Sat Dec 14 17:19:55 2013
@@ -4,7 +4,7 @@ One of the things we must take care of w
Wicket comes with a variant of components AjaxButton, AjaxLink and AjaxFallbackLink that display a default activity indicator during AJAX request processing. These components are respectively IndicatingAjaxButton, IndicatingAjaxLink and IndicatingAjaxFallbackLink.
-The default activity indicator used in Wicket can be easily integrated in our components using behavior AjaxIndicatorAppender (available in package org.apache.wicket.extensions.ajax. markup.html) and implementing the interface IAjaxIndicatorAware (in package org.apache.wicket.ajax).
+The default activity indicator used in Wicket can be easily integrated in our components using behavior AjaxIndicatorAppender (available in package @org.apache.wicket.extensions.ajax.markup.html@) and implementing the interface @IAjaxIndicatorAware@ (in package @org.apache.wicket.ajax@).
IAjaxIndicatorAware declares method getAjaxIndicatorMarkupId() which returns the id of the markup element used to display the activity indicator. This id can be obtained from the AjaxIndicatorAppender behavior that has been added to the current component. The following code snippet summarizes the steps needed to integrate the default activity indicator with an ajaxified component:
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_5.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_5.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_5.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_5.gdoc Sat Dec 14 17:19:55 2013
@@ -1,8 +1,8 @@
-Starting from version 6.0 Wicket has introduced two entities which allow us to control how an AJAX request is generated on client side and to specify the custom JavaScript code we want to execute during request handling. These entities are class AjaxRequestAttributes and interface IAjaxCallListener, both placed in package org.apache.wicket.ajax.attributes.
+Starting from version 6.0 Wicket has introduced two entities which allow us to control how an AJAX request is generated on client side and to specify the custom JavaScript code we want to execute during request handling. These entities are class @AjaxRequestAttributes@ and interface @IAjaxCallListener@, both placed in package @org.apache.wicket.ajax.attributes@.
-AjaxRequestAttributes exposes the attributes used to generate the JavaScript call invoked on client side to start an AJAX request. Each attribute will be passed as a "JSON":http://en.wikipedia.org/wiki/JSON parameter to the JavaScript function Wicket.Ajax.ajax which is responsible for sending the concrete AJAX request. Every JSON parameter is identified by a short name. Here is a partial list of the available parameters:
+AjaxRequestAttributes exposes the attributes used to generate the JavaScript call invoked on client side to start an AJAX request. Each attribute will be passed as a "JSON":http://en.wikipedia.org/wiki/JSON parameter to the JavaScript function @Wicket.Ajax.ajax@ which is responsible for sending the concrete AJAX request. Every JSON parameter is identified by a short name. Here is a partial list of the available parameters:
{table}
*Short name* | *Description* | *Default value*
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18.gdoc Sat Dec 14 17:19:55 2013
@@ -4,7 +4,7 @@ The first decade of 2000s has seen the r
All these new technologies are based on the concepts of container and dependency injection. Container is the environment where our enterprise resources are created and configured while "dependency injection":http://en.wikipedia.org/wiki/Dependency_Injection is a pattern implemented by containers to inject into an object the resources it depends on.
-Wicket can be easily integrated with enterprise containers using component instantiation listeners. These entities are instances of interface org.apache.wicket.application.IComponent InstantiationListener and can be registered during application's initialization. IComponentInstantiationListener defines callback method onInstantiation(Component component) which can be used to provide custom instantiation logic for Wicket components.
+Wicket can be easily integrated with enterprise containers using component instantiation listeners. These entities are instances of interface @org.apache.wicket.application.IComponentInstantiationListener@ and can be registered during application's initialization. IComponentInstantiationListener defines callback method onInstantiation(Component component) which can be used to provide custom instantiation logic for Wicket components.
Wicket distribution and project "WicketStuff":https://github.com/wicketstuff already provide a set of built-in listeners to integrate our applications with EJB 3.1 compliant containers (like JBoss Seam) or with some of the most popular enterprise frameworks like "Guice":http://code.google.com/p/google-guice/ or Spring.
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_2.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_2.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_2.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_2.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-If we need to inject dependencies with Spring we can use listener org.apache.wicket.spring. injection.annot.SpringComponentInjector provided by module wicket-spring.
+If we need to inject dependencies with Spring we can use listener @org.apache.wicket.spring.injection.annot.SpringComponentInjector@ provided by module wicket-spring.
For the sake of simplicity in the example project SpringInjectionExample we have used Spring class AnnotationConfigApplicationContext to avoid any XML file and create a Spring context directly from code:
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_4.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_4.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_4.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_4.gdoc Sat Dec 14 17:19:55 2013
@@ -1,5 +1,5 @@
-In this chapter we have seen how to integrate Wicket applications with Spring and with an EJB container. Module wicket-examples contains also an example of integration with Guice (see application class org.apache.wicket.examples.guice.GuiceApplication).
+In this chapter we have seen how to integrate Wicket applications with Spring and with an EJB container. Module wicket-examples contains also an example of integration with Guice (see application class @org.apache.wicket.examples.guice.GuiceApplication@).
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_1.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_1.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_1.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_1.gdoc Sat Dec 14 17:19:55 2013
@@ -4,7 +4,7 @@ The first step in implementing a securit
!wikipedia-login-form.png!
-Wicket supports form-based authentication with session class AuthenticatedWebSession and application class AuthenticatedWebApplication, both placed inside package org.apache.wicket.authroles.authentication.
+Wicket supports form-based authentication with session class AuthenticatedWebSession and application class AuthenticatedWebApplication, both placed inside package @org.apache.wicket.authroles.authentication@.
h3. AuthenticatedWebSession
@@ -158,7 +158,7 @@ The authentication logic inside authenti
h3. Redirecting user to an intermediate page
-Method restartResponseAtSignInPage is an example of redirecting user to an intermediate page before allowing him to access to the requested page. This method internally throws exception org.apache.wicket.RestartResponseAtInterceptPageException which saves the URL of the requested page into session metadata and then redirects user to the page passed as constructor parameter (the sign in page).
+Method restartResponseAtSignInPage is an example of redirecting user to an intermediate page before allowing him to access to the requested page. This method internally throws exception @org.apache.wicket.RestartResponseAtInterceptPageException@ which saves the URL of the requested page into session metadata and then redirects user to the page passed as constructor parameter (the sign in page).
Component's method redirectToInterceptPage(Page) works in much the same way as restartResponseAtSignInPage but it allows us to specify which page to use as intermediate page:
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_2.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_2.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_2.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_2.gdoc Sat Dec 14 17:19:55 2013
@@ -53,7 +53,7 @@ Most of the times we won't need to imple
h3. SimplePageAuthorizationStrategy
-Abstract class SimplePageAuthorizationStrategy (in package org.apache.wicket.authorization.strategies.page) is a strategy that checks user authorizations calling abstract method isAuthorized only for those pages that are subclasses of a given supertype. If isAuthorized returns false, the user is redirected to the sign in page specified as second constructor parameter:
+Abstract class SimplePageAuthorizationStrategy (in package @org.apache.wicket.authorization.strategies.page@) is a strategy that checks user authorizations calling abstract method isAuthorized only for those pages that are subclasses of a given supertype. If isAuthorized returns false, the user is redirected to the sign in page specified as second constructor parameter:
{code}
SimplePageAuthorizationStrategy authorizationStrategy = new SimplePageAuthorizationStrategy(
@@ -72,7 +72,7 @@ h3. Role-based strategies
At the end of paragraph 18.1.1 we have introduced AbstractAuthenticatedWebSession's method getRoles which is provided to support role-based authorization returning the set of roles granted to the current user.
-In Wicket roles are simple strings like âBASIC_USERâ or âADMINâ (they don't need to be capitalized) and they are handled with class org.apache.wicket.authroles.authorization.strategies. role.Roles. This class extends standard HashSet collection adding some functionalities to check whether the set contains one or more roles. Class Roles already defines roles Roles.USER and Roles.ADMIN.
+In Wicket roles are simple strings like âBASIC_USERâ or âADMINâ (they don't need to be capitalized) and they are handled with class @org.apache.wicket.authroles.authorization.strategies@. role.Roles. This class extends standard HashSet collection adding some functionalities to check whether the set contains one or more roles. Class Roles already defines roles Roles.USER and Roles.ADMIN.
The session class in the following example returns a custom âSIGNED_INâ role for every authenticated user and it adds an Roles.ADMIN role if username is equal to superuser:
@@ -246,7 +246,7 @@ public class AdminOnlyPage extends WebPa
h3. Catching an unauthorized component instantiation
-Interface IUnauthorizedComponentInstantiationListener (in package org.apache.wicket.authorization) is provided to give the chance to handle the case in which a user tries to instantiate a component without having the permissions to do it. The method defined inside this interface is onUnauthorizedInstantiation(Component) and it is executed whenever a user attempts to execute an unauthorized instantiation.
+Interface IUnauthorizedComponentInstantiationListener (in package @org.apache.wicket.authorization@) is provided to give the chance to handle the case in which a user tries to instantiate a component without having the permissions to do it. The method defined inside this interface is onUnauthorizedInstantiation(Component) and it is executed whenever a user attempts to execute an unauthorized instantiation.
This listener must be registered into application's security settings with method setUnauthorized ComponentInstantiationListener defined by setting interface ISecuritySettings. In the following code snippet we register a listener that redirect user to a warning page if he tries to do a not-allowed instantiation:
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_3.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_3.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_3.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_3.gdoc Sat Dec 14 17:19:55 2013
@@ -2,7 +2,7 @@
HTTPS is the standard technology adopted on Internet to create a secure communication channel between web applications and their users.
-In Wicket we can easily protect our pages with HTTPS mounting a special request mapper called HttpsMapper and using annotation RequireHttps with those pages we want to serve over this protocol. Both these two entities are in package org.apache.wicket.protocol.https.
+In Wicket we can easily protect our pages with HTTPS mounting a special request mapper called HttpsMapper and using annotation RequireHttps with those pages we want to serve over this protocol. Both these two entities are in package @org.apache.wicket.protocol.https@.
HttpsMapper wraps an existing mapper and redirects incoming requests to HTTPS if the related response must render a page containing annotation RequireHttps. Most of the times the wrapped mapper will be the root one, just like we saw before for CryptoManager in paragraph 8.6.6.
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_4.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_4.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_4.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_4.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-Wicket internally uses an entity called package resource guard to protect package resources from external access. This entity is an implementation of interface org.apache.wicket.markup.html. IPackageResourceGuard.
+Wicket internally uses an entity called package resource guard to protect package resources from external access. This entity is an implementation of interface @org.apache.wicket.markup.html.IPackageResourceGuard@.
By default Wicket applications use as package resource guard class SecurePackageResource Guard, which allows to access only to the following file extensions (grouped by type):
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_5.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_5.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_5.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter19/chapter19_5.gdoc Sat Dec 14 17:19:55 2013
@@ -2,9 +2,9 @@
In this chapter we have seen the components and the mechanisms that allow us to implement security policies in our Wicket-based applications. Wicket comes with an out of the box support for both authorization and authentication.
-The central element of authorization mechanism is the interface IAuthorizationStrategy which decouples our components from any detail about security strategy. The implementations of this interface must decide if a user is allowed to instantiate a given page or component and if she/he can perform a given action on it.
+The central element of authorization mechanism is the interface @IAuthorizationStrategy@ which decouples our components from any detail about security strategy. The implementations of this interface must decide if a user is allowed to instantiate a given page or component and if she/he can perform a given action on it.
-Wicket natively supports role-based authorizations with strategies MetaDataRoleAuthorization Strategy and AnnotationsRoleAuthorizationStrategy. The difference between these two strategies is that the first offers a programmatic approach for role handling while the second promotes a declarative approach using built-in annotations.
+Wicket natively supports role-based authorizations with strategies @MetaDataRoleAuthorizationStrategy@ and @AnnotationsRoleAuthorizationStrategy@. The difference between these two strategies is that the first offers a programmatic approach for role handling while the second promotes a declarative approach using built-in annotations.
After having explored how Wicket internally implements authentication and authorization, in the last part of the chapter we have learnt how to configure our applications to support HTTPS and how to specify which pages must be served over this protocol.
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_1.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_1.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_1.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_1.gdoc Sat Dec 14 17:19:55 2013
@@ -24,13 +24,13 @@ public class TestHomePage{
}
{code}
-The central class in a Wicket testing is org.apache.wicket.util.tester.WicketTester. This utility class provides a set of methods to render a component, click links, check if page contains a given component or a feedback message, and so on.
+The central class in a Wicket testing is @org.apache.wicket.util.tester.WicketTester@. This utility class provides a set of methods to render a component, click links, check if page contains a given component or a feedback message, and so on.
-The basic test case shipped with TestHomePage illustrates how WicketTester is typically instantiated (inside method setUp()). In order to test our components, WicketTester needs to use an instance of WebApplication. Usually, we will use our application class as WebApplication, but we can also decide to build WicketTester invoking its no-argument constructor and letting it automatically build a mock web application (an instance of class org.apache.wicket.mock. MockApplication).
+The basic test case shipped with @TestHomePage@ illustrates how @WicketTester@ is typically instantiated (inside method @setUp()@). In order to test our components, WicketTester needs to use an instance of @WebApplication@. Usually, we will use our application class as @WebApplication@, but we can also decide to build WicketTester invoking its no-argument constructor and letting it automatically build a mock web application (an instance of class @org.apache.wicket.mock.MockApplication@).
-The code from TestHomePage introduces two basic methods to test our pages. The first is method startPage that renders a new instance of the given page class and sets it as current rendered page for WicketTester. The second method is assertRenderedPage which checks if the current rendered page is an instance of the given class. In this way if TestHomePage succeeds we are sure that page HomePage has been rendered without any problem. The last rendered page can be retrieved with method getLastRenderedPage.
+The code from @TestHomePage@ introduces two basic methods to test our pages. The first is method @startPage@ that renders a new instance of the given page class and sets it as current rendered page for WicketTester. The second method is assertRenderedPage which checks if the current rendered page is an instance of the given class. In this way if TestHomePage succeeds we are sure that page HomePage has been rendered without any problem. The last rendered page can be retrieved with method @getLastRenderedPage@.
-That's only a taste of what WicketTester can do. In the next paragraphs we will see how it can be used to test every element that composes a Wicket page (links, models, behaviors, etc...).
+That's only a taste of what @WicketTester@ can do. In the next paragraphs we will see how it can be used to test every element that composes a Wicket page (links, models, behaviors, etc...).
h3. Testing links
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_3.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_3.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_3.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter20/chapter20_3.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-If we need to test component markup at a more fine-grained level, we can use class TagTester from package org.apache.wicket.util.tester.
+If we need to test component markup at a more fine-grained level, we can use class @TagTester@ from package @org.apache.wicket.util.tester@.
This test class allows to check if the generated markup contains one or more tags having a given attribute with a given value. TagTester can not be directly instantiated but it comes with three factory methods that return one or more TagTester matching the searching criteria. In the following test case (from project TagTesterExample) we retrieve the first tag of the home page (a <span> tag) having attribute class equal to myClass:
@@ -44,7 +44,7 @@ public void homePageMarkupTest()
The name of the tag found by TagTester can be retrieved with its method getName. Method createTagsByAttribute returns all the tags that have the given value on the class attribute. In the code above we have used this method to test that our markup contains two tags having attribute class equal to myClass.
-Another utility class that comes in handy when we want to test components markup is ComponentRenderer in package org.apache.wicket.core.util.string. The purpose of this class is to render a page or a component in isolation with its static methods renderComponent and renderPage. Both methods return the generated markup as CharSequence:
+Another utility class that comes in handy when we want to test components markup is ComponentRenderer in package @org.apache.wicket.core.util.string@. The purpose of this class is to render a page or a component in isolation with its static methods renderComponent and renderPage. Both methods return the generated markup as CharSequence:
{code}
@Test
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter21/chapter21_2.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter21/chapter21_2.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter21/chapter21_2.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter21/chapter21_2.gdoc Sat Dec 14 17:19:55 2013
@@ -58,7 +58,7 @@ java.lang.IllegalStateException: No WebA
<init>(WicketTester.java:308)
{code}
-As you can see above, the Exception gets raised during the initialization of the WicketTester instance even before the actual test method gets executed. Even though we have applied rather cool and simple annotation based test configuration already described and passed in perfectly well prepared ApplicationContext instance to the WicketTester instance in the constructor, somewhere down the rabbit hole someone complained that no WebApplicationContext instance could have been found which seems to be required in order to initialize the WicketTester properly.
+As you can see above, the Exception gets raised during the initialization of the @WicketTester@ instance even before the actual test method gets executed. Even though we have applied rather cool and simple annotation based test configuration already described and passed in perfectly well prepared ApplicationContext instance to the WicketTester instance in the constructor, somewhere down the rabbit hole someone complained that no WebApplicationContext instance could have been found which seems to be required in order to initialize the WicketTester properly.
!description-of-illegalstate.jpg!
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter6/chapter6_4.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter6/chapter6_4.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter6/chapter6_4.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter6/chapter6_4.gdoc Sat Dec 14 17:19:55 2013
@@ -49,7 +49,7 @@ Please note that in the example above we
{warning}
If we forget to call superclass version of methods @onInitialize()@ or @onBeforeRender()@, Wicket will throw an @IllegalStateException@ with the following message:
-@java.lang.IllegalStateException: org.apache.wicket.Component has not been properly initialized. Something in the hierarchy of <page class name> has not called super.onInitialize()/onBeforeRender() in the override of onInitialize()/ onBeforeRender() method@
+@java.lang.IllegalStateException: @org.apache.wicket.Component@ has not been properly initialized. Something in the hierarchy of <page class name> has not called super.onInitialize()/onBeforeRender() in the override of onInitialize()/ onBeforeRender() method@
{warning}
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter7/chapter7_2.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter7/chapter7_2.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter7/chapter7_2.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter7/chapter7_2.gdoc Sat Dec 14 17:19:55 2013
@@ -54,7 +54,7 @@ As we have stated at the beginning of th
h3. Using a specific page version with PageReference
-To retrieve a specific page version in our code we can use class org.apache.wicket.PageReference by providing its constructor with the corresponding page id:
+To retrieve a specific page version in our code we can use class @org.apache.wicket.PageReference@ by providing its constructor with the corresponding page id:
{code}
//load page version with page id = 3
@@ -71,7 +71,7 @@ If for any reason we need to switch off
h3. Pluggable serialization
-Starting from version 1.5 it is possible to choose which implementation of Java serialization will be used by Wicket to store page versions. Wicket serializes pages using an implementation of interface org.apache.wicket.serialize.ISerializer. The default implementation is org.apache.wicket.serialize.java.JavaSerializer and it uses the standard Java serialization mechanism based on classes ObjectOutputStream and ObjectInputStream. However on Internet we can find other interesting serialization libraries like Kryo1 which performs faster then the standard implementation.The serializer in use can be customized with the setSerializer(ISerializer) method defined by setting interface org.apache.wicket.settings.IFrameworkSettings.
+Starting from version 1.5 it is possible to choose which implementation of Java serialization will be used by Wicket to store page versions. Wicket serializes pages using an implementation of interface @org.apache.wicket.serialize.ISerializer@. The default implementation is @org.apache.wicket.serialize.java.JavaSerializer@ and it uses the standard Java serialization mechanism based on classes ObjectOutputStream and ObjectInputStream. However on Internet we can find other interesting serialization libraries like Kryo1 which performs faster then the standard implementation.The serializer in use can be customized with the setSerializer(ISerializer) method defined by setting interface @org.apache.wicket.settings.IFrameworkSettings@.
We can access this interface inside the method init of the class Application using the getFrameworkSettings() method :
@@ -94,7 +94,7 @@ The following picture is an overview of
!wicket-cache.png!
-The session-scoped cache is faster then the other memory levels but it contains only the pages used to serve the last request. Wicket allows us to set the maximum amount of memory allowed for the application-scoped cache and for the page store file. Both parameters can be configured via setting interface org.apache.wicket.settings.IStoreSettings.
+The session-scoped cache is faster then the other memory levels but it contains only the pages used to serve the last request. Wicket allows us to set the maximum amount of memory allowed for the application-scoped cache and for the page store file. Both parameters can be configured via setting interface @org.apache.wicket.settings.IStoreSettings@.
This interface provides the setMaxSizePerSession(Bytes bytes) method to set the size for page store file. The Bytes parameter is the maximum size allowed for this file:
@@ -107,7 +107,7 @@ public void init()
}
{code}
-Class org.apache.wicket.util.lang.Bytes is an utility class provided by Wicket to express size in bytes (for further details refer to the JavaDoc).
+Class @org.apache.wicket.util.lang.Bytes@ is an utility class provided by Wicket to express size in bytes (for further details refer to the JavaDoc).
For the second level cache we can use the setInmemoryCacheSize(int inmemoryCacheSize) method. The integer parameter is the maximum number of page instances that will be saved into application-scoped cache:
{code}
@@ -125,7 +125,7 @@ Page instances are not kept in the user
!page-expired.png!
-This error page can be customized with the setPageExpiredErrorPage method of the org.apache.wicket.settings.IApplicationSettings interface:
+This error page can be customized with the setPageExpiredErrorPage method of the @org.apache.wicket.settings.IApplicationSettings@ interface:
{code}
@Override
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter7/chapter7_3.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter7/chapter7_3.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter7/chapter7_3.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter7/chapter7_3.gdoc Sat Dec 14 17:19:55 2013
@@ -26,7 +26,7 @@ protected void onInitialize() {
}
{code}
-Alternatively, we could use the StatelessComponent utility annotation along with the StatelessChecker class (they are both in package org.apache.wicket.devutils. stateless). StatelessChecker will throw an IllegalArgumentException if a component annotated with StatelessComponent doesn't respect the requirements for being stateless. To use StatelessComponent annotation we must first add the StatelessChecker to our application as a component render listener:
+Alternatively, we could use the @StatelessComponent@ utility annotation along with the @StatelessChecker@ class (they are both in package @org.apache.wicket.devutils.stateless@). @StatelessChecker@ will throw an @IllegalArgumentException@ if a component annotated with @StatelessComponent@ doesn't respect the requirements for being stateless. To use @StatelessComponent@ annotation we must first add the @StatelessChecker@ to our application as a component render listener:
{code}
@Override
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_2.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_2.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_2.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_2.gdoc Sat Dec 14 17:19:55 2013
@@ -1,5 +1,5 @@
-The Request and Response classes are located in package org.apache.wicket.request and they provide an abstraction of the concrete request and response used by our web application.
+The @Request@ and @Response@ classes are located in package @org.apache.wicket.request@ and they provide an abstraction of the concrete request and response used by our web application.
-Both classes are declared as abstract but if our application class inherits from WebApplication it will use their sub classes ServletWebRequest and ServletWebResponse, both of them located inside the package org.apache.wicket.protocol.http.servlet.ServletWebRequest and ServletWebResponse wrap respectively a HttpServletRequest and a HttpServletResponse object. If we need to access to these low-level objects we can call Request's method getContainerRequest() and Response's method getContainer Response().
\ No newline at end of file
+Both classes are declared as abstract but if our application class inherits from @WebApplication@ it will use their sub classes @ServletWebRequest@ and @ServletWebResponse@, both of them located inside the package @org.apache.wicket.protocol.http.servlet.ServletWebRequest@ and @ServletWebResponse@ wrap respectively a @HttpServletRequest@ and a @HttpServletResponse@ object. If we need to access to these low-level objects we can call @Request@'s method @getContainerRequest()@ and @Response@'s method @getContainerResponse()@.
\ No newline at end of file
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_3.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_3.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_3.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_3.gdoc Sat Dec 14 17:19:55 2013
@@ -1,16 +1,16 @@
-Class org.apache.wicket.request.cycle.RequestCycle is the entity in charge of serving a web request. Our application class creates a new RequestCycle on every request with its method createRequestCycle(request, response).
+Class @org.apache.wicket.request.cycle.RequestCycle@ is the entity in charge of serving a web request. Our application class creates a new @RequestCycle@ on every request with its method @createRequestCycle(request, response)@.
-Method createRequestCycle is declared as final, so we can't override it to return a custom subclass of RequestCycle. Instead, we must build a request cycle provider implementing interface org.apache.wicket.IRequestCycleProvider, and then we must tell our application class to use it via the setRequestCycleProvider method.
+Method @createRequestCycle@ is declared as final, so we can't override it to return a custom subclass of @RequestCycle@. Instead, we must build a request cycle provider implementing interface @org.apache.wicket.IRequestCycleProvider@, and then we must tell our application class to use it via the @setRequestCycleProvider@ method.
-The current running request cycle can be retrieved at any time by calling its static method RequestCycle.get(). Strictly speaking this method returns the request cycle associated with the current (or local) thread, which is the thread that is serving the current request. A similar get() method is also implemented in classes org.apache.wicket.Application (as we have seen in paragraph 2.2.2) and org.apache.wicket.Session in order to get the application and the session in use by the current thread.
+The current running request cycle can be retrieved at any time by calling its static method @RequestCycle.get()@. Strictly speaking this method returns the request cycle associated with the current (or local) thread, which is the thread that is serving the current request. A similar @get()@ method is also implemented in classes @org.apache.wicket.Application@ (as we have seen in paragraph 2.2.2) and @org.apache.wicket.Session@ in order to get the application and the session in use by the current thread.
{note}
-The implementation of the get method takes advantage of the standard class java.lang.ThreadLocal. See its JavaDoc for an introduction to local-thread variables.
+The implementation of the get method takes advantage of the standard class @java.lang.ThreadLocal@. See its JavaDoc for an introduction to local-thread variables.
{note}
-Class org.apache.wicket.Component provides the getRequestCycle() method which is a convenience method that internally invokes RequestCycle.get():
+Class @org.apache.wicket.Component@ provides the @getRequestCycle()@ method which is a convenience method that internally invokes @RequestCycle.get()@:
{code}
public final RequestCycle getRequestCycle() {
@@ -24,11 +24,11 @@ h3. RequestCycle and request processing
This paragraph will provide just the basic informations about what happens behind the scenes of request processing. When you work with Wicket it's unlikely to have a need for customizing this process, so we won't cover this topic in detail.
{note}
-In order to process a request, RequestCycle delegates the task to another entity which implements interface org.apache.wicket.request.IRequestHandler. There are different implementations of this interface, each suited for a particular type of requested resource (a page to render, an AJAX request, an URL to an external page, etc.).
+In order to process a request, @RequestCycle@ delegates the task to another entity which implements interface @org.apache.wicket.request.IRequestHandler@. There are different implementations of this interface, each suited for a particular type of requested resource (a page to render, an AJAX request, an URL to an external page, etc.).
-To resolve the right handler for a given HTTP request, the RequestCycle uses a set of objects implementing the org.apache.wicket.request.IRequestMapper interface. The mapping interface defines the getCompatibilityScore(Request request) method which returns a score indicating how compatible the request mapper is for the current request. RequestCycle will choose the mapper with the highest score and it will call its mapRequest(Request request) method to get the proper handler for the given request. Once RequestCycle has resolved a request handler, it invokes its method respond(IRequestCycle requestCycle) to start request processing.
+To resolve the right handler for a given HTTP request, the @RequestCycle@ uses a set of objects implementing the @org.apache.wicket.request.IRequestMapper@ interface. The mapping interface defines the @getCompatibilityScore(Request request)@ method which returns a score indicating how compatible the request mapper is for the current request. @RequestCycle@ will choose the mapper with the highest score and it will call its @mapRequest(Request request)@ method to get the proper handler for the given request. Once @RequestCycle@ has resolved a request handler, it invokes its method @respond(IRequestCycle requestCycle)@ to start request processing.
-The following sequence diagram recaps how a request handler is resolved by the RequestCycle:
+The following sequence diagram recaps how a request handler is resolved by the @RequestCycle@:
!request-cycle-handler.png!
@@ -38,15 +38,15 @@ h3. Generating URL with the urlFor and m
The RequestCycle is also responsible for generating the URL value (as CharSequence) for the following entities:
-* a page class, via the urlFor(Class<C> pageClass, PageParameters parameters) method
-* an IRequestHandler via the urlFor(IRequestHandler handler) method
-* a ResourceReference via the urlFor(ResourceReference reference, PageParameters params) method (resource entities will be introduced in chapter 13).
+* a page class, via the @urlFor(Class<C> pageClass, PageParameters parameters)@ method
+* an IRequestHandler via the @urlFor(IRequestHandler handler)@ method
+* a ResourceReference via the @urlFor(ResourceReference reference, PageParameters params)@ method (resource entities will be introduced in chapter 13).
-The overloaded urlFor method from above also has a corresponding version that returns an instance of org.apache.wicket.request.Url instead of a CharSequence. This version has the prefix 'map' in its name (i.e. it has mapUrlFor as full name).
+The overloaded @urlFor@ method from above also has a corresponding version that returns an instance of @org.apache.wicket.request.Url@ instead of a @CharSequence@. This version has the prefix 'map' in its name (i.e. it has @mapUrlFor@ as full name).
h3. Method setResponsePage
-The RequestCycle class contains the implementation of the setResponsePage method we use to redirect a user to a specific page (see paragraph 2.4). The namesake method of class org.apache.wicket.Component is just a convenience method that internally invokes the actual implementation on current request cycle:
+The @RequestCycle@ class contains the implementation of the @setResponsePage@ method we use to redirect a user to a specific page (see paragraph 2.4). The namesake method of class @org.apache.wicket.Component@ is just a convenience method that internally invokes the actual implementation on current request cycle:
{code}
public final void setResponsePage(final Page page) {
@@ -63,7 +63,7 @@ The RequestCycle comes with some hook me
Methods onBeforeRequest and onEndRequest can be used if we need to execute custom actions before and after business code is executed, such as opening a Hibernate/JPA session and closing it when code has terminated.
-A more flexible way to interact with the request processing is to use the listener interface org.apache.wicket.request.cycle.IRequestCycleListener. In addition to the three methods already seen for RequestCycle, this interface offers further hooks into request processing:
+A more flexible way to interact with the request processing is to use the listener interface @org.apache.wicket.request.cycle.IRequestCycleListener@. In addition to the three methods already seen for RequestCycle, this interface offers further hooks into request processing:
* *onBeginRequest(RequestCycle cycle):* (see the description above)
* *onEndRequest(RequestCycle cycle):* (see the description above)
* *onDetach(RequestCycle cycle):* (see the description above)
@@ -74,7 +74,7 @@ A more flexible way to interact with the
* *onExceptionRequestHandlerResolved(RequestCycle rc, IRequestHandler rh, Exception ex):* called when an IRequestHandler has been resolved and will be used to handle an exception.
* *onUrlMapped(RequestCycle cycle, IRequestHandler handler, Url url):* called when an URL has been generated for an IRequestHandler object.
-To use the request cycle listeners we must add them to our application which in turn will pass them to the new RequestCycle's instances created with createRequestCycle method:
+To use the request cycle listeners we must add them to our application which in turn will pass them to the new @RequestCycle@'s instances created with @createRequestCycle@ method:
{code}
@Override
@@ -88,5 +88,5 @@ public void init() {
}
{code}
-The getRequestCycleListeners method returns an instance of class org.apache.wicket.request.cycle.RequestCycleListenerCollection. This class is a sort of typed collection for IRequestCycleListener and it also implements the "Composite pattern":http://en.wikipedia.org/wiki/Composite_pattern .
+The @getRequestCycleListeners@ method returns an instance of class @org.apache.wicket.request.cycle.RequestCycleListenerCollection@. This class is a sort of typed collection for @IRequestCycleListener@ and it also implements the "Composite pattern":http://en.wikipedia.org/wiki/Composite_pattern .
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_4.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_4.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_4.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_4.gdoc Sat Dec 14 17:19:55 2013
@@ -1,14 +1,14 @@
-In Wicket we use class org.apache.wicket.Session to handle session-relative informations such as client informations, session attributes, session-level cache (seen in paragraph 6.2.4), etc...
+In Wicket we use class @org.apache.wicket.Session@ to handle session-relative informations such as client informations, session attributes, session-level cache (seen in paragraph 6.2.4), etc...
-In addition, we know from paragraph 6.1 that Wicket creates a user session to store versions of stateful pages. Similarly to what happens with RequestCycle, the new Session's instances are generated by the Application class with the newSession(Request request, Response response) method. This method is not declared as final, hence it can be overridden if we need to use a custom implementation of the Session class.
+In addition, we know from paragraph 6.1 that Wicket creates a user session to store versions of stateful pages. Similarly to what happens with RequestCycle, the new Session's instances are generated by the @Application@ class with the @newSession(Request request, Response response)@ method. This method is not declared as final, hence it can be overridden if we need to use a custom implementation of the Session class.
-By default if our custom application class is a subclass of WebApplication, method newSession will return an instance of class org.apache.wicket.protocol.http.WebSession. As we have mentioned talking about RequestCycle, also class Session provides a static get() method which returns the session associated to the current thread.
+By default if our custom application class is a subclass of WebApplication, method newSession will return an instance of class @org.apache.wicket.protocol.http.WebSession@. As we have mentioned talking about @RequestCycle@, also class Session provides a static @get()@ method which returns the session associated to the current thread.
h3. Session and listeners
-Similar to the RequestCycle, class org.apache.wicket.Session also offers support for listener entities. With Session these entities must implement the callback interface org.apache.wicket.ISessionListener which exposes only the onCreated(Session session) method. As you might guess from its name, this method is called when a new session is created. Session listeners must be added to our application using a typed collection, just like we have done before with request cycle listeners:
+Similar to the @RequestCycle@, class @org.apache.wicket.Session@ also offers support for listener entities. With Session these entities must implement the callback interface @org.apache.wicket.ISessionListener@ which exposes only the @onCreated(Session session)@ method. As you might guess from its name, this method is called when a new session is created. Session listeners must be added to our application using a typed collection, just like we have done before with request cycle listeners:
{code}
@Override
@@ -116,9 +116,9 @@ JavaServer Pages Specification1 defines
Although Wicket doesn't implement the JSP Specification (it is rather an alternative to it), it offers a feature called metadata which resembles scoped variables but is much more powerful. Metadata is quite similar to a Java Map in that it stores pairs of key-value objects where the key must be unique. In Wicket each of the following classes has its own metadata store: RequestCycle, Session, Application and Component.
-The key used for metadata is an instance of class org.apache.wicket.MetaDataKey<T>. To put an arbitrary object into metadata we must use the setMetaData method which takes two parameters as input: the key used to store the value and the value itself. If we are using metadata with classes Session or Component, data object must be serializable because Wicket serializes both session and component instances. This constraint is not applied to metadata of classes Application and RequestCycle which can contain a generic object. In any case, the type of data object must be compatible with the type parameter T specified by the key.
+The key used for metadata is an instance of class @org.apache.wicket.MetaDataKey<T>@. To put an arbitrary object into metadata we must use the setMetaData method which takes two parameters as input: the key used to store the value and the value itself. If we are using metadata with classes Session or Component, data object must be serializable because Wicket serializes both session and component instances. This constraint is not applied to metadata of classes Application and RequestCycle which can contain a generic object. In any case, the type of data object must be compatible with the type parameter T specified by the key.
-To retrieve a previously inserted object we must use the getMetaData(MetaDataKey<T> key) method. In the following example we set a java.sql.Connection object in the application's metadata so it can be used by any page of the application:
+To retrieve a previously inserted object we must use the @getMetaData(MetaDataKey<T> key)@ method. In the following example we set a @java.sql.Connection@ object in the application's metadata so it can be used by any page of the application:
Application class code:
{code}
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_1.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_1.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_1.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_1.gdoc Sat Dec 14 17:19:55 2013
@@ -2,7 +2,7 @@
A common practice in web development is to pass data to a page using query string parameters (like ?paramName1=paramValu1¶mName2=paramValue2...). Wicket offers a more flexible and object oriented way to do this with models (we will see them in the next chapter). However, even if we are using Wicket, we still need to use query string parameters to exchange data with other Internet-based services. Consider for example a classic confirmation page which is linked inside an email to let users confirm important actions like password changing or the subscription to a mailing list. This kind of page usually expects to receive a query string parameter containing the id of the action to confirm.
-Query string parameters can also be referred to as named parameters. In Wicket they are handled with class org.apache.wicket.request.mapper.parameter.PageParameters. Since named parameters are basically name-value pairs, PageParameters works in much the same way as Java Map providing two methods to create/modify a parameter (add(String name, Object value) and set(String name, Object value)), one method to remove an existing parameter (remove(String name)) and one to retrieve the value of a given parameter (get(String name)) . Here is a snippet to illustrate the usage of PageParameters:
+Query string parameters can also be referred to as named parameters. In Wicket they are handled with class @org.apache.wicket.request.mapper.parameter.PageParameters@. Since named parameters are basically name-value pairs, PageParameters works in much the same way as Java Map providing two methods to create/modify a parameter (add(String name, Object value) and set(String name, Object value)), one method to remove an existing parameter (remove(String name)) and one to retrieve the value of a given parameter (get(String name)) . Here is a snippet to illustrate the usage of PageParameters:
{code}
PageParameters pageParameters = new PageParameters();
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_2.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_2.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_2.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_2.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-A link to a bookmarkable page can be built with the link component org.apache.wicket.markup.html.link.BookmarkablePageLink:
+A link to a bookmarkable page can be built with the link component @org.apache.wicket.markup.html.link.BookmarkablePageLink@:
{code}
BookmarkablePageLink bpl=new BookmarkablePageLink(PageWithParameters.class, pageParameters);
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_4.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_4.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_4.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_4.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-Since Wicket uses plain HTML markup files as templates, we can place an anchor to an external page directly inside the markup file. When we need to dynamically generate external anchors, we can use link component org.apache.wicket.markup.html.link.ExternalLink. In order to build an external link we must specify the value of the href attribute using a model or a plain string. In the next snippet, given an instance of Person, we generate a Google search query for its full name:
+Since Wicket uses plain HTML markup files as templates, we can place an anchor to an external page directly inside the markup file. When we need to dynamically generate external anchors, we can use link component @org.apache.wicket.markup.html.link.ExternalLink@. In order to build an external link we must specify the value of the href attribute using a model or a plain string. In the next snippet, given an instance of Person, we generate a Google search query for its full name:
Html:
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_5.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_5.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_5.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_5.gdoc Sat Dec 14 17:19:55 2013
@@ -1,6 +1,6 @@
-Component Link has a stateful nature, hence it cannot be used with stateless pages. To use links with these kinds of pages Wicket provides the convenience org.apache.wicket.markup.html. link.StatelessLink component which is basically a subtype of Link with the stateless hint set to true.
+Component Link has a stateful nature, hence it cannot be used with stateless pages. To use links with these kinds of pages Wicket provides the convenience @org.apache.wicket.markup.html.link.StatelessLink@ component which is basically a subtype of Link with the stateless hint set to true.
Please keep in mind that Wicket generates a new instance of a stateless page also to serve stateless links, so the code inside the onClick() method can not depend on instance variables. To illustrate this potential issue let's consider the following code (from the project StatelessPage) where the value of the variable index is used inside onclick():
Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_6.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_6.gdoc?rev=1550944&r1=1550943&r2=1550944&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_6.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter9/chapter9_6.gdoc Sat Dec 14 17:19:55 2013
@@ -23,7 +23,7 @@ The path provided to mountPage will be u
RequestCycle.get().urlFor(MountedPage.class);
{code}
-Under the hood the mountPage method mounts an instance of the request mapper org.apache.wicket.request.mapper.MountedMapper configured for the given path:
+Under the hood the mountPage method mounts an instance of the request mapper @org.apache.wicket.request.mapper.MountedMapper@ configured for the given path:
{code}
public final <T extends Page> void mountPage(final String path,final Class<T> pageClass) {
@@ -103,18 +103,18 @@ StatefulPackageMount is one of the pages
<Application path>/mountPackage/StatefulPackageMount?1
{code}
-Similarly to what is done by the mountPage method, the implementation of the mountPackage method mounts an instance of org.apache.wicket.request.mapper.PackageMapper to the given path.
+Similarly to what is done by the mountPage method, the implementation of the mountPackage method mounts an instance of @org.apache.wicket.request.mapper.PackageMapper@ to the given path.
h3. Providing custom mapper context to request mappers
-Interface org.apache.wicket.request.mapper.IMapperContext is used by request mappers to create new page instances and to retrieve static URL segments used to build and parse page URLs. Here is the list of these segments:
+Interface @org.apache.wicket.request.mapper.IMapperContext@ is used by request mappers to create new page instances and to retrieve static URL segments used to build and parse page URLs. Here is the list of these segments:
* Namespace: it's the first URL segment of non-mounted pages. By default its value is wicket.
* Identifier for non-bookmarkable URLs: it's the segment that identifies non bookmarkable pages. By default its value is page.
* Identifier for bookmarkable URLs: it's the segment that identifies bookmarkable pages. By default its value is bookmarkable (as we have seen before in paragraph 8.1.1).
* Identifier for resources: it's the segment that identifies Wicket resources. Its default value is resources. The topic of resource management will be covered in chapter 13.
-IMapperContext provides a getter method for any segment listed above. By default Wicket uses class org.apache.wicket.DefaultMapperContext as mapper context.
+IMapperContext provides a getter method for any segment listed above. By default Wicket uses class @org.apache.wicket.DefaultMapperContext@ as mapper context.
Project CustomMapperContext is an example of customization of mapper context where we use index as identifier for non-bookmarkable pages and staticURL as identifier for bookmarkable pages. In this project, instead of implementing our mapper context from scratch, we used DefaultMapperContext as base class overriding just the two methods we need to achieve the desired result (getBookmarkableIdentifier() and getPageIdentifier()). The final implementation is the following:
@@ -144,11 +144,11 @@ protected IMapperContext newMapperContex
h3. Controlling how page parameters are encoded with IPageParametersEncoder
-Some request mappers (like MountedMapper and PackageMapper) can delegate page parameters encoding/decoding to interface org.apache.wicket.request.mapper.parameter.IPage ParametersEncoder. This entity exposes two methods: encodePageParameters() and decodePageParameters(): the first one is invoked to encode page parameters into an URL while the second one extracts parameters from the URL.
+Some request mappers (like MountedMapper and PackageMapper) can delegate page parameters encoding/decoding to interface @org.apache.wicket.request.mapper.parameter.IPage ParametersEncoder@. This entity exposes two methods: encodePageParameters() and decodePageParameters(): the first one is invoked to encode page parameters into an URL while the second one extracts parameters from the URL.
Wicket comes with a built-in implementation of this interface which encodes named page parameters as URL segments using the following patter: /paramName1/paramValue1/paramName2/param Value2...
-This built-in encoder is org.apache.wicket.request.mapper.parameter.UrlPathPage ParametersEncoder class. In the PageParametersEncoderExample project we have manually mounted a MountedMapper that takes as input also an UrlPathPageParametersEncoder:
+This built-in encoder is @org.apache.wicket.request.mapper.parameter.UrlPathPageParametersEncoder@ class. In the @PageParametersEncoderExample@ project we have manually mounted a @MountedMapper@ that takes as input also an @UrlPathPageParametersEncoder@:
{code}
@Override