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 22:13:12 UTC

svn commit: r1550971 [14/15] - in /wicket/common/site/trunk/_site/guide: ./ gapi/ gapi/DefaultPackage/ gapi/spring/ guide/ guide/pages/ guide/src/docs/guide/chapter14/ guide/src/docs/guide/chapter15/ guide/src/docs/guide/chapter16/ guide/src/docs/guide...

Modified: wicket/common/site/trunk/_site/guide/guide/single.pdf
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/single.pdf?rev=1550971&r1=1550970&r2=1550971&view=diff
==============================================================================
Binary files - no diff available.

Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_3.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_3.gdoc?rev=1550971&r1=1550970&r2=1550971&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_3.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_3.gdoc Sat Dec 14 21:13:09 2013
@@ -43,11 +43,11 @@ public class CustomPanel extends Panel {
 
 Wicket will take care of generating a valid URL for file calendar.jpg. URLs for package resources have the following structure:
 
-@<path to application root>/wicket/resource/<fully qualified classname>/<resource file name> -<ver-<id>>[.<file extension>]@
+@<path to application root>/wicket/resource/<fully qualified classname>/<resource file name>-<ver-<id>>(.file extension)@
 
 In our example the URL for our picture file calendar.jpg is the following:
 
-@./wicket/resource/org.wicketTutorial.CustomPanel/ calendar-ver-1297887542000.jpg@
+@./wicket/resource/org.wicketTutorial.CustomPanel/calendar-ver-1297887542000.jpg@
 
 The first part of the URL is the relative path to the application root. In our example our page is already at the application's root so we have only a single-dotted segment. The next two segments, wicket and resource, are respectively the namespace and the identifier for resources seen in paragraph 8.6.4. 
 

Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_5.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_5.gdoc?rev=1550971&r1=1550970&r2=1550971&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_5.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_5.gdoc Sat Dec 14 21:13:09 2013
@@ -1,6 +1,6 @@
 
 
-Class ResourceReference allows to specify the resources it depends on overriding method @getDependencies()@. The method returns an iterator over the set of @HeaderItems@ that must be rendered before the resource referenced by ResourceReference can be used. This can be really helpful when our resources are JavaScript or CSS libraries that in turn depend on other libraries.
+Class @ResourceReference@ allows to specify the resources it depends on overriding method @getDependencies()@. The method returns an iterator over the set of @HeaderItems@ that must be rendered before the resource referenced by @ResourceReference@ can be used. This can be really helpful when our resources are JavaScript or CSS libraries that in turn depend on other libraries.
 
 For example we can use this method to ensure that a custom reference to JQueryUI library will find JQuery already loaded in the page: 
 

Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_7.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_7.gdoc?rev=1550971&r1=1550970&r2=1550971&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_7.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_7.gdoc Sat Dec 14 21:13:09 2013
@@ -17,7 +17,7 @@ public void init() {
 }
 {code}
 
-With the configuration above (taken from project CustomResourceMounting) every request to /foo/bar will be served by the custom resource built in the previous paragraph. 
+With the configuration above (taken from project @CustomResourceMounting@) every request to /foo/bar will be served by the custom resource built in the previous paragraph. 
 
 Parameter placeholders are supported as well:
 

Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_8.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_8.gdoc?rev=1550971&r1=1550970&r2=1550971&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_8.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter14/chapter14_8.gdoc Sat Dec 14 21:13:09 2013
@@ -1,6 +1,6 @@
 
 
-Resources can be added to a global registry in order to share them at application-level. Shared resources are identified by an application-scoped key and they can be easily retrieved at a later time using reference class SharedResourceReference. The global registry can be accessed with Application's method getSharedResources. In the following excerpt of code (taken again from project CustomResourceMounting) we register an instance of our custom RSS feeds producer as application-shared resource:
+Resources can be added to a global registry in order to share them at application-level. Shared resources are identified by an application-scoped key and they can be easily retrieved at a later time using reference class @SharedResourceReference@. The global registry can be accessed with @Application@'s method @getSharedResources@. In the following excerpt of code (taken again from project @CustomResourceMounting@) we register an instance of our custom RSS feeds producer as application-shared resource:
 
 {code}
   //init application's method
@@ -12,7 +12,7 @@ Resources can be added to a global regis
   }
 {code}
 
-Now to use an application-shared resource we can simply retrieve it using class SharedResourceReference and providing the key previously used to register the resource:
+Now to use an application-shared resource we can simply retrieve it using class @SharedResourceReference@ and providing the key previously used to register the resource:
 
 {code}
 add(new ResourceLink("globalRssLink", new SharedResourceReference("globalRSSProducer")));
@@ -22,12 +22,12 @@ The URL generated for application shared
 
 @./wicket/resource/org.apache.wicket.Application/globalRSSProducer@
 
-The last segment of the URL is the key of the resource while the previous segment contains the scope of the resource. For application-scoped resources the scope is always the fully qualified name of class Application. This should not be surprising since global resources are visible at application level (i.e. the scope is the application).
+The last segment of the URL is the key of the resource while the previous segment contains the scope of the resource. For application-scoped resources the scope is always the fully qualified name of class @Application@. This should not be surprising since global resources are visible at application level (i.e. the scope is the application).
 
 {note}
 Package resources are also application-shared resources but they don't need to be explicitly registered.
 {note}
 
 {note}
-Remember that we can get the URL of a resource reference using method @urlFor(ResourceReference resourceRef, PageParameters params )@ available with both class RequestCycle and class Component.
+Remember that we can get the URL of a resource reference using method @urlFor(ResourceReference resourceRef, PageParameters params )@ available with both class @RequestCycle@ and class @Component@.
 {note}
\ No newline at end of file

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=1550971&r1=1550970&r2=1550971&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 21:13:09 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
@@ -13,13 +13,13 @@ Wicket loads application's resources del
   }
 {code}
 
-The default locator used by Wicket is class ResourceStreamLocator which in turn tries to load a requested resource using a set of implementations of interface IResourceFinder. This interface defines method find(Class class, String pathname) which tries to resolve a resource corresponding to the given class and path.
+The default locator used by Wicket is class @ResourceStreamLocator@ which in turn tries to load a requested resource using a set of implementations of interface @IResourceFinder@. This interface defines method @find(Class class, String pathname)@ which tries to resolve a resource corresponding to the given class and path.
 
-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. 
+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:
+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:
 
 !package-structure-custom-folder.png!
 

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -79,15 +79,15 @@ public <Date> IConverter<Date> getConver
 
 The first thing to do inside onInitialize is to ensure that our component will have a markup id for its related text field. This is done invoking setOutputMarkupId(true). 
 
-Next, JQueryDateField tries to retrieve the date format and the ISO language code that must be used as initialization parameters. This is done using class ResourceModel which searches for a given resource in the available bundles. If no value is found for date format or for ISO language code, default values will be used ('mm/dd/yy' and 'en-GB'). 
+Next, JQueryDateField tries to retrieve the date format and the ISO language code that must be used as initialization parameters. This is done using class @ResourceModel@ which searches for a given resource in the available bundles. If no value is found for date format or for ISO language code, default values will be used ('mm/dd/yy' and 'en-GB'). 
 
-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).
+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
 
-The rest of the code of our custom component is inside method renderHeader, which is responsible for adding to page header the bundled JQuery library, the three files from JQuery UI distribution, the custom file JQDatePicker.js and the invocation of function initJQDatepicker:
+The rest of the code of our custom component is inside method @renderHeader@, which is responsible for adding to page header the bundled JQuery library, the three files from JQuery UI distribution, the custom file JQDatePicker.js and the invocation of function @initJQDatepicker@:
 
 {code}
 @Override
@@ -122,9 +122,9 @@ public void renderHead(IHeaderResponse r
 
 If component is disabled the calendar icon must be hidden and no datepicker must be displayed. That's why renderHeader is skipped if component is not enabled.
 
-To get a reference to the bundled JQuery library we used the JavaScript setting interface IJavaScriptLibrarySettings and its method getJQueryReference.
+To get a reference to the bundled JQuery library we used the JavaScript setting interface @IJavaScriptLibrarySettings@ and its method @getJQueryReference@.
 
-In the last part of renderHeader we build the string to invoke function initJQDatepicker using the values obtained inside onInitialize. Unfortunately the date format used by JQuery UI is different from the one adopted in Java so we have to convert it before building the JavaScript code. This init script is rendered into header section using a OnLoadHeaderItem to ensure that it will be executed after all the other scripts have been loaded.
+In the last part of renderHeader we build the string to invoke function initJQDatepicker using the values obtained inside onInitialize. Unfortunately the date format used by JQuery UI is different from the one adopted in Java so we have to convert it before building the JavaScript code. This init script is rendered into header section using a @OnLoadHeaderItem@ to ensure that it will be executed after all the other scripts have been loaded.
 
 {note}
 If we add more than one instance of our custom component to a single page, static resources are rendered to the header section just once. Wicket automatically checks if a static resource is already referenced by a page and if so, it will not render it again.

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -1,10 +1,10 @@
 
 
-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).
+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)@.
 
-Here is a partial list of methods defined inside class Behavior along with a brief description of what they do:
+Here is a partial list of methods defined inside class @Behavior@ along with a brief description of what they do:
 
 * *beforeRender(Component component)*: called when a component is about to be rendered. 
 * *afterRender(Component component)*: called after a component has been rendered. 
@@ -38,8 +38,8 @@ public class RedAsteriskBehavior extends
 }
 {code}
 
-Since method beforeRender is called before the coupled component is rendered, we can use it to prepend custom markup to component tag. This can be done writing our markup directly to the current  Response object, as we did in the example above.
+Since method @beforeRender@ is called before the coupled component is rendered, we can use it to prepend custom markup to component tag. This can be done writing our markup directly to the current  Response object, as we did in the example above.
 
-Please note that we could achieve the same result overriding component method onBeforeRender. However using a behavior we can easily reuse our custom code with any other kind of component without modifying its source code. As general best practice we should always consider to implement a new functionality using a behavior if it can be shared among different kinds of component.
+Please note that we could achieve the same result overriding component method @onBeforeRender@. However using a behavior we can easily reuse our custom code with any other kind of component without modifying its source code. As general best practice we should always consider to implement a new functionality using a behavior if it can be shared among different kinds of component.
 
 Behaviors play also a strategic role in the built-in AJAX support provided by Wicket, as we will see in the next chapter. 

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -27,13 +27,13 @@ public interface IMyListener extends IRe
 }
 {code}
 
-By default RequestListenerInterface will respond rendering the current page after the callback method has been executed (if we have a non-AJAX request). To change this behavior we can use setter method setRenderPageAfterInvocation(boolean).
+By default @RequestListenerInterface@ will respond rendering the current page after the callback method has been executed (if we have a non-AJAX request). To change this behavior we can use setter method @setRenderPageAfterInvocation(boolean)@.
 
-Now that our callback interface is complete we can generate a callback URL with Component's method urlFor(RequestListenerInterface, PageParameters) or with method urlFor (Behavior, RequestListenerInterface, PageParameters) if we are using a callback interface with a behavior (see the following example).
+Now that our callback interface is complete we can generate a callback URL with @Component@'s method @urlFor(RequestListenerInterface, PageParameters)@ or with method @urlFor (Behavior, RequestListenerInterface, PageParameters)@ if we are using a callback interface with a behavior (see the following example).
 
-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). 
+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 @wantOnSelectionChangedNotifications@). 
 
-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
@@ -46,9 +46,9 @@ public void onRequest() {	
 }
 {code}
 
-When invoked via URL, the behavior expects to find a request parameter (choiceId) containing the id of the selected choice. This value is used to obtain the corresponding choice object that must be used to set the model of the component that the behavior is bound to (boundComponent). Method convertChoiceIdToChoice is in charge of retrieving the choice object given its id and it has been copied from class AbstractSingleSelectChoice.
+When invoked via URL, the behavior expects to find a request parameter (choiceId) containing the id of the selected choice. This value is used to obtain the corresponding choice object that must be used to set the model of the component that the behavior is bound to (boundComponent). Method @convertChoiceIdToChoice@ is in charge of retrieving the choice object given its id and it has been copied from class @AbstractSingleSelectChoice@.
 
-Another interesting part of OnChangeSingleChoiceBehavior is its method onComponentTag where some JavaScript “magic” is used to move user's browser to the callback URL when event “change” occurs on bound component:
+Another interesting part of @OnChangeSingleChoiceBehavior@ is its method @onComponentTag@ where some JavaScript “magic” is used to move user's browser to the callback URL when event “change” occurs on bound component:
 
 {code}
 @Override
@@ -71,9 +71,9 @@ public void onComponentTag(Component com
 }
 {code}
 
-The goal of onComponentTag is to build an onchange handler that forces user's browser to move to the callback URL (modifing standard property window.location.href). Please note that we have appended the expected parameter (choiceId) to the URL retrieving its value with a JQuery selector suited for the current type of component (a drop-down menu or a radio group). Since we are using JQuery in our JavaScript code, the behavior comes also with method renderHead that adds the bundled JQuery library to the current page.
+The goal of @onComponentTag@ is to build an onchange handler that forces user's browser to move to the callback URL (modifing standard property window.location.href). Please note that we have appended the expected parameter (choiceId) to the URL retrieving its value with a JQuery selector suited for the current type of component (a drop-down menu or a radio group). Since we are using JQuery in our JavaScript code, the behavior comes also with method @renderHead@ that adds the bundled JQuery library to the current page.
 
-Method getCallbackUrl() is used to generate the callback URL for our custom behavior and it has been copied from built-in class AbstractAjaxBehavior: 
+Method @getCallbackUrl()@ is used to generate the callback URL for our custom behavior and it has been copied from built-in class @AbstractAjaxBehavior@: 
 
 {code}
 public CharSequence getCallbackUrl(){
@@ -90,14 +90,14 @@ public CharSequence getCallbackUrl(){
 }
 {code}
 
-Static field IBehaviorListener.INTERFACE is the implementation of RequestListenerInterface defined inside callback interface IBehaviorListener.
+Static field @IBehaviorListener.INTERFACE@ is the implementation of @RequestListenerInterface@ defined inside callback interface @IBehaviorListener@.
 
-The home page of project CallbackURLExample contains a DropDownChoice and a RadioChoice which use our custom behavior. There are also two labels to display the content of the models of the two components:
+The home page of project @CallbackURLExample@ contains a @DropDownChoice@ and a @RadioChoice@ which use our custom behavior. There are also two labels to display the content of the models of the two components:
 
 !CallbackURLExample-screenshot.png!
 
 {note}
-Implementing interface IBehaviorListener makes a behavior stateful because its callback URL is specific for a given instance of component.
+Implementing interface @IBehaviorListener@ makes a behavior stateful because its callback URL is specific for a given instance of component.
 {note}
 
 
@@ -107,11 +107,11 @@ Starting from version 1.5 Wicket offers 
 
 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.
 
-The following entities already implement both these two interfaces (i.e. they can be either sender or receiver): Component, Session, RequestCycle and Application.
-IEventSource exposes a single method named send which takes in input three parameters:
+The following entities already implement both these two interfaces (i.e. they can be either sender or receiver): @Component@, @Session@, @RequestCycle@ and @Application@.
+@IEventSource@ exposes a single method named send which takes in input three parameters:
 
-* *sink*: an implementation of IEventSink that will be the receiver of the event. 
-* *broadcast*: a Broadcast enum which defines the broadcast method used to dispatch the event to the sink and to other entities such as sink children, sink containers, session object, application object and the current request cycle. It has four possible values:
+* *sink*: an implementation of @IEventSink@ that will be the receiver of the event. 
+* *broadcast*: a @Broadcast@ enum which defines the broadcast method used to dispatch the event to the sink and to other entities such as sink children, sink containers, session object, application object and the current request cycle. It has four possible values:
 {table}
 *Value* | *Description*
 BREADTH | The event is sent first to the specified sink and then to all its children components following a breadth-first order.
@@ -121,9 +121,9 @@ EXACT | The event is sent only to the sp
 {table}
 * *payload*: a generic object representing the data sent with the event.
 
-Each broadcast mode has its own traversal order for Session, RequestCycle and Application. See JavaDoc of class Broadcast for further details about this order.
+Each broadcast mode has its own traversal order for @Session@, @RequestCycle@ and @Application@. See JavaDoc of class @Broadcast@ for further details about this order.
 
-Interface IEventSink exposes callback method onEvent(IEvent<?> event) which is triggered when a sink receives an event. The interface IEvent represents the received event and provides getter methods to retrieve the event broadcast type, the source of the event and its payload. Typically the received event is used checking the type of its payload object:
+Interface @IEventSink@ exposes callback method @onEvent(IEvent<?> event)@ which is triggered when a sink receives an event. The interface @IEvent@ represents the received event and provides getter methods to retrieve the event broadcast type, the source of the event and its payload. Typically the received event is used checking the type of its payload object:
 
 {code}
 @Override
@@ -137,6 +137,6 @@ public void onEvent(IEvent event) {
 }
 {code}
 
-Project InterComponetsEventsExample provides a concrete example of sending an event to a component (named 'container in the middle') using all the available broadcast methods:
+Project @InterComponetsEventsExample@ provides a concrete example of sending an event to a component (named 'container in the middle') using all the available broadcast methods:
 
 !InterComponentsEventsExample-screenshot.png!

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -8,7 +8,7 @@ During application's bootstrap Wicket se
 initializer=org.wicketTutorial.MyInitializer
 {code}
 
-The fully qualified class name corresponds to the initializer that must be executed. Interface IInitializer defines method init(Application) which should contain our initialization code, and method destroy(Application) which is invoked when application is terminated:
+The fully qualified class name corresponds to the initializer that must be executed. Interface @IInitializer@ defines method init(Application) which should contain our initialization code, and method @destroy(Application)@ which is invoked when application is terminated:
 
 {code}
 public class MyInitializer implements IInitializer{

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -22,6 +22,6 @@ As we can see in the picture above, ever
 
 With these two operations we can force Wicket to clear the internal caches used to load components markup and resource bundles. This can be particularly useful if we have our application running in DEPLOYMENT mode and we want to publish minor fixes for markup or bundle files (like spelling or typo corrections) without restarting the entire application. Without cleaning these two caches Wicket would continue to use cached values ignoring any change made to markup or bundle files.
 
-Some of the exposed properties are editable, hence we can tune their values while the application is running. For example if we look at the properties of ApplicationSettings we can set the maximum size allowed for an upload modifying the attribute DefaultMaximumUploadSize:
+Some of the exposed properties are editable, hence we can tune their values while the application is running. For example if we look at the properties of @ApplicationSettings@ we can set the maximum size allowed for an upload modifying the attribute DefaultMaximumUploadSize:
 
 !JMX-console4.png!
\ No newline at end of file

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=1550971&r1=1550970&r2=1550971&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 21:13:09 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: 
 
@@ -27,9 +27,9 @@ Class StringResourceStream is a resource
 
 h3. Avoiding markup caching
 
-As we have seen in the previous paragraph, Wicket uses an internal cache for components markup. This can be a problem if our component dynamical generates its markup when it is rendered because once the markup has been cached, Wicket will always use the cached version for the specific component. To overwrite this default caching policy, a component can implement interface IMarkupCacheKeyProvider. 
+As we have seen in the previous paragraph, Wicket uses an internal cache for components markup. This can be a problem if our component dynamical generates its markup when it is rendered because once the markup has been cached, Wicket will always use the cached version for the specific component. To overwrite this default caching policy, a component can implement interface @IMarkupCacheKeyProvider@. 
 
-This interface defines method getCacheKey(MarkupContainer, Class<?>) which returns a string value representing the key used by Wicket to retrieve the markup of the component from the cache. If this value is null the markup will not be cached, allowing the component to display the last generated markup each time it is rendered:
+This interface defines method @getCacheKey(MarkupContainer, Class<?>)@ which returns a string value representing the key used by Wicket to retrieve the markup of the component from the cache. If this value is null the markup will not be cached, allowing the component to display the last generated markup each time it is rendered:
 
 {code}
 public class NoCacheMarkupPanel extends Panel implements IMarkupCacheKeyProvider {

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -15,7 +15,7 @@ new AjaxLink("ajaxLink"){
 };
 {code}
 
-Using AjaxRequestTarget we can specify the content that must be sent back to the client as response to the current AJAX request. The most commonly used method of this interface is probably add(Component... components). With this method we tell Wicket to render again the specified components and refresh their markup via AJAX:
+Using AjaxRequestTarget we can specify the content that must be sent back to the client as response to the current AJAX request. The most commonly used method of this interface is probably @add(Component... components)@. With this method we tell Wicket to render again the specified components and refresh their markup via AJAX:
 
 {code}
 new AjaxLink("ajaxLink"){
@@ -28,7 +28,7 @@ new AjaxLink("ajaxLink"){
 };
 {code}
 
-Components can be refreshed via Ajax only if they have rendered a markup id for their related tag. As a consequence, we must remember to set a valid id value on every component we want to add to AjaxRequestTarget. This can be done using one of the two methods seen in paragraph 4.3:
+Components can be refreshed via Ajax only if they have rendered a markup id for their related tag. As a consequence, we must remember to set a valid id value on every component we want to add to @AjaxRequestTarget@. This can be done using one of the two methods seen in paragraph 4.3:
 
 {code}
 final Label label = new Label("labelComponent", "Initial value.");

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -8,17 +8,17 @@ This paragraph provides an overview of w
 
 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. 
+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@.
 
 h3. Fallback components
 
-Building an entire site using AJAX can be risky as some clients may not support this technology. In order to provide an usable version of our site also to these clients, we can use components AjaxFallbackLink and AjaxFallbackButton which are able to automatically degrade to a standard link or to a standard button if client doesn't support AJAX.
+Building an entire site using AJAX can be risky as some clients may not support this technology. In order to provide an usable version of our site also to these clients, we can use components @AjaxFallbackLink@ and @AjaxFallbackButton@ which are able to automatically degrade to a standard link or to a standard button if client doesn't support AJAX.
 
 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
 
@@ -35,7 +35,7 @@ Base component AjaxEditableLabel exposes
 * *onError(AjaxRequestTarget target)*: called when the new inserted input has failed validation.
 * *onCancel(AjaxRequestTarget target)*: called when user has exited from editing mode pressing escape key. The default implementation brings back the label to its initial state hiding the editor component.  
 
-Wicket module wicket-examples contains page class EditableLabelPage.java which shows all these three components together. You can see this page in action at "http://www.wicket-library.com/wicket-examples-6.0.x/ajax/editable-label":http://www.wicket-library.com/wicket-examples-6.0.x/ajax/editable-label :
+Wicket module wicket-examples contains page class @EditableLabelPage.java@ which shows all these three components together. You can see this page in action at "http://www.wicket-library.com/wicket-examples-6.0.x/ajax/editable-label":http://www.wicket-library.com/wicket-examples-6.0.x/ajax/editable-label :
 
 !edit-label-example-screenshot.png!
 
@@ -49,11 +49,11 @@ When using AutoCompleteTextField we are 
 
 !autocomplete-example-screenshot.png!
 
-Suggestions are rendered using a render which implements interface IAutoCompleteRenderer. The default implementation simply calls toString() on each suggestion object. If we need to work with a custom render we can specify it via component constructor.
+Suggestions are rendered using a render which implements interface @IAutoCompleteRenderer@. The default implementation simply calls toString() on each suggestion object. If we need to work with a custom render we can specify it via component constructor.
 
-AutoCompleteTextField supports a wide range of settings that are passed to its constructor with class AutoCompleteSettings.
+AutoCompleteTextField supports a wide range of settings that are passed to its constructor with class @AutoCompleteSettings@.
 
-One of the most interesting parameter we can specify for AutoCompleteTextField is the throttle delay which is the amount of time (in milliseconds) that must elapse between a change of input value and the transmission of a new Ajax request to display suggestions. This parameter can be set with method setThrottleDelay(int):
+One of the most interesting parameter we can specify for @AutoCompleteTextField@ is the throttle delay which is the amount of time (in milliseconds) that must elapse between a change of input value and the transmission of a new Ajax request to display suggestions. This parameter can be set with method @setThrottleDelay(int)@:
 
 {code}
 AutoCompleteSettings settings = new AutoCompleteSettings();
@@ -69,7 +69,7 @@ AutoCompleteTextField field = new AutoCo
 };
 {code}
 
-Wicket module wicket-examples contains page class AutoCompletePagePage.java which shows an example of autocomplete text field. The running example is available at "http://www.wicket-library.com/wicket-examples-6.0.x/ajax/autocomplete":http://www.wicket-library.com/wicket-examples-6.0.x/ajax/autocomplete .
+Wicket module wicket-examples contains page class @AutoCompletePagePage.java@ which shows an example of autocomplete text field. The running example is available at "http://www.wicket-library.com/wicket-examples-6.0.x/ajax/autocomplete":http://www.wicket-library.com/wicket-examples-6.0.x/ajax/autocomplete .
 
 h3. Modal window
 
@@ -79,9 +79,9 @@ Class @org.apache.wicket.extensions.ajax
 
 The content of a modal window can be either another component or a page. In the first case the id of the  component used as content must be retrieved with method getContentId(). 
 
-If instead we want to use a page as window content, we must implement the inner interface ModalWindow.PageCreator and pass it to method setPageCreator. The page used as content will be embedded in a <iframe> tag.
+If instead we want to use a page as window content, we must implement the inner interface @ModalWindow.PageCreator@ and pass it to method @setPageCreator@. The page used as content will be embedded in a <iframe> tag.
 
-To display a modal window we must call its method show(AjaxRequestTarget target). This is  usually done inside the AJAX callback method of another component (like an AjaxLink). The following markup and code are taken from project BasicModalWindowExample and illustrate a basic usage of a modal window:
+To display a modal window we must call its method @show(AjaxRequestTarget target)@. This is  usually done inside the AJAX callback method of another component (like an @AjaxLink@). The following markup and code are taken from project @BasicModalWindowExample@ and illustrate a basic usage of a modal window:
 
 *HTML:*
 {code:html}
@@ -112,7 +112,7 @@ public HomePage(final PageParameters par
 }
 {code}
 
-Just like any other component also ModalWindow must be added to a markup tag, like we did in our example using a <div> tag. Wicket will automatically hide this tag in the final markup appending the style value display:none. 
+Just like any other component also @ModalWindow@ must be added to a markup tag, like we did in our example using a <div> tag. Wicket will automatically hide this tag in the final markup appending the style value display:none. 
 The component provides different setter methods to customize the appearance of the window:
 
 * *setTitle(String)*: specifies the title of the window
@@ -123,13 +123,13 @@ The component provides different setter 
 * *setCssClassName(String)*: specifies the CSS class used for the window. 
 * *setAutoSize(boolean)*: when this flag is set to true the window will automatically adjust its size to fit content width and height. By default it is false.
 
-The modal window can be closed from code using its method close(AjaxRequestTarget target). The currently opened window can be closed also with the following JavaScript instruction:
+The modal window can be closed from code using its method @close(AjaxRequestTarget target)@. The currently opened window can be closed also with the following JavaScript instruction:
 
 {code}
 Wicket.Window.get().close();
 {code}
 
-ModalWindow gives the opportunity to perform custom actions when window is closing. Inner interface ModalWindow.WindowClosedCallback can be implemented and passed to window's method setWindowClosedCallback to specify the callback that must be executed after window has been closed:
+@ModalWindow@ gives the opportunity to perform custom actions when window is closing. Inner interface @ModalWindow.WindowClosedCallback@ can be implemented and passed to window's method @setWindowClosedCallback@ to specify the callback that must be executed after window has been closed:
 
 {code}
 modalWindow.setWindowClosedCallback(new ModalWindow.WindowClosedCallback() {
@@ -149,15 +149,15 @@ Class @org.apache.wicket.extensions.mark
 
 Because of their highly interactive nature, tree repeaters are implemented as AJAX components,  meaning that they are updated via AJAX when we expand or collapse their nodes. 
 
-The basic implementation of a tree repeater shipped with Wicket is component NestedTree. In order to use a tree repeater we must provide an implementation of interface ITreeProvider which is in charge of returning the nodes that compose the tree.  
+The basic implementation of a tree repeater shipped with Wicket is component @NestedTree@. In order to use a tree repeater we must provide an implementation of interface @ITreeProvider@ which is in charge of returning the nodes that compose the tree.  
 
-Wicket comes with a built-in implementation of ITreeProvider called TreeModelProvider that works with the same tree model and nodes used by Swing component javax.swing.JTree. These Swing entities should be familiar to you if you have previously worked with the old tree repeaters (components Tree and TreeTable) that have been deprecated with Wicket 6 and that are strongly dependent on Swing-based model and nodes. TreeModelProvider can be used to migrate your code to the new tree repeaters. 
+Wicket comes with a built-in implementation of ITreeProvider called TreeModelProvider that works with the same tree model and nodes used by Swing component @javax.swing.JTree@. These Swing entities should be familiar to you if you have previously worked with the old tree repeaters (components @Tree@ and @TreeTable@) that have been deprecated with Wicket 6 and that are strongly dependent on Swing-based model and nodes. @TreeModelProvider@ can be used to migrate your code to the new tree repeaters. 
 
-In the next example (project CheckBoxAjaxTree) we will build a tree that displays some of the main cities of three European countries: Italy, Germany and France. The cities are sub-nodes of a main node representing the relative county. The nodes of the final tree will be also selectable with a checkbox control. The whole tree will have the classic look & feel of Windows XP. This is how our tree will look like:
+In the next example (project @CheckBoxAjaxTree@) we will build a tree that displays some of the main cities of three European countries: Italy, Germany and France. The cities are sub-nodes of a main node representing the relative county. The nodes of the final tree will be also selectable with a checkbox control. The whole tree will have the classic look & feel of Windows XP. This is how our tree will look like:
 
 !AJAX-tree-repeater.png!
 
-We will start to explore the code of this example from the home page. The first portion of code we will see is where we build the nodes and the TreeModelProvider for the three. As tree node we will use Swing class javax.swing.tree.DefaultMutableTreeNode:
+We will start to explore the code of this example from the home page. The first portion of code we will see is where we build the nodes and the @TreeModelProvider@ for the three. As tree node we will use Swing class @javax.swing.tree.DefaultMutableTreeNode@:
 
 {code}
 public class HomePage extends WebPage {
@@ -180,7 +180,7 @@ public class HomePage extends WebPage {
      //To be continued...
 {code}
 
-Nodes have been built using simple strings as data objects and invoking custom utility method addNodes which converts string parameters into children nodes for a given parent node. Once we have our tree of DefaultMutableTreeNodes we can build the Swing tree model (DefaultTreeModel) that will be the backing object for a TreeModelProvider. This provider wraps each node in a model invoking its abstract method model. In our example we have used a simple Model as wrapper model.
+Nodes have been built using simple strings as data objects and invoking custom utility method addNodes which converts string parameters into children nodes for a given parent node. Once we have our tree of @DefaultMutableTreeNodes@ we can build the Swing tree model (@DefaultTreeModel@) that will be the backing object for a @TreeModelProvider@. This provider wraps each node in a model invoking its abstract method model. In our example we have used a simple @Model@ as wrapper model.
 
 Scrolling down the code we can see how the tree component is instantiated and configured before being added to the home page:
 
@@ -206,7 +206,7 @@ Scrolling down the code we can see how t
 }
 {code}
 
-To use tree repeaters we must implement their abstract method newContentComponent which is called internally by base class AbstractTree when a new node must be built. As content component we have used built-in class CheckedFolder which combines a Folder component with a CheckBox form control. 
+To use tree repeaters we must implement their abstract method @newContentComponent@ which is called internally by base class @AbstractTree@ when a new node must be built. As content component we have used built-in class @CheckedFolder@ which combines a @Folder@ component with a @CheckBox@ form control. 
 
 The final step before adding the tree to its page is to apply a theme to it. Wicket comes with two behaviors, WindowsTheme and HumanTheme, which correspond to the classic Windows XP theme and to the Human theme from Ubuntu.
 
@@ -217,11 +217,11 @@ Another nice feature we would like to im
 * When a node is checked also all its children nodes (if any) must be checked. We must also ensure that all the ancestors of the checked node (root included) are checked, otherwise we would get an inconsistent selection.
 * When a node is unchecked also all its children nodes (if any) must be unchecked and we must also ensure that ancestors get unchecked if they have no more checked children.
 
-The first goal (keeping track of checked node) can be accomplished building a custom version of CheckedFolder that uses a shared Java Set to store checked node and to verify if its node has been  checked. This kind of solution requires a custom model for checkbox component in order to reflect its checked status when its container node is rendered. This model must implement typed interface IModel<Boolean> and must be returned by CheckedFolder's method newCheckBoxModel.
+The first goal (keeping track of checked node) can be accomplished building a custom version of @CheckedFolder@ that uses a shared Java Set to store checked node and to verify if its node has been  checked. This kind of solution requires a custom model for checkbox component in order to reflect its checked status when its container node is rendered. This model must implement typed interface @IModel<Boolean>@ and must be returned by @CheckedFolder@'s method @newCheckBoxModel@.
 
-For the second goal (auto select/unselect children and ancestor nodes) we can use CheckedFolder's callback method onUpdate(AjaxRequestTarget) that is invoked after a checkbox is clicked and its value has been updated. Overriding this method we can handle user click adding/removing nodes to/from the Java Set.
+For the second goal (auto select/unselect children and ancestor nodes) we can use @CheckedFolder@'s callback method onUpdate(AjaxRequestTarget) that is invoked after a checkbox is clicked and its value has been updated. Overriding this method we can handle user click adding/removing nodes to/from the Java Set.
 
-Following this implementation plan we can start coding our custom CheckedFolder (named AutocheckedFolder): 
+Following this implementation plan we can start coding our custom @CheckedFolder@ (named @AutocheckedFolder@): 
 
 {code}
 public class AutocheckedFolder<T> extends CheckedFolder<T> {
@@ -274,15 +274,15 @@ public class AutocheckedFolder<T> extend
 
 The constructor of this new component takes in input a further parameter which is the set containing checked nodes. 
 
-Class CheckModel is the custom model we have implemented for checkbox control. As base class for this model we have used AbstractCheckBoxModel which is provided to implement custom models for checkbox controls. 
+Class CheckModel is the custom model we have implemented for checkbox control. As base class for this model we have used @AbstractCheckBoxModel@ which is provided to implement custom models for checkbox controls. 
 
-Methods addRemoveSubNodes and addRemoveAncestorNodes are called to automatically add/remove children and ancestor nodes to/from the current Set. Their implementation is mainly focused on the navigation of tree nodes and it heavily depends on the internal implementation of the tree, so we won't dwell on their code.
+Methods @addRemoveSubNodes@ and @addRemoveAncestorNodes@ are called to automatically add/remove children and ancestor nodes to/from the current Set. Their implementation is mainly focused on the navigation of tree nodes and it heavily depends on the internal implementation of the tree, so we won't dwell on their code.
 
 Now we are just one step away from completing our tree as we still have to find a way to update the checked status of both children and ancestors nodes on client side. Although we could easily accomplish this task by simply refreshing the whole tree via AJAX, we would like to find a better and more performant solution for this task. 
 
 When we modify the checked status of a node we don't expand/collapse any node of the three so we can simply update the desired checkboxes rather than updating the entire tree component. This alternative approach could lead to a more responsive interface and to a strong reduction of bandwidth consumption. 
 
-With the help of JQuery we can code a couple of JavaScript functions that can be used to check/ uncheck all the children and ancestors of a given node. Then, we can append these functions to the current AjaxRequest at the end of method onUpdate:
+With the help of JQuery we can code a couple of JavaScript functions that can be used to check/ uncheck all the children and ancestors of a given node. Then, we can append these functions to the current @AjaxRequest@ at the end of method onUpdate:
 
 {code}
    @Override
@@ -319,7 +319,7 @@ public void renderHead(IHeaderResponse r
 
 h3. Working with hidden components
 
-When a component is not visible its markup and the related id attribute are not rendered in the final page, hence it can not be updated via AJAX. To overcome this problem we must use Component's method setOutputMarkupPlaceholderTag(true) which has the effect of rendering a hidden <span> tag containing the markup id of the hidden component: 
+When a component is not visible its markup and the related id attribute are not rendered in the final page, hence it can not be updated via AJAX. To overcome this problem we must use Component's method @setOutputMarkupPlaceholderTag(true)@ which has the effect of rendering a hidden <span> tag containing the markup id of the hidden component: 
 
 {code}
 final Label label = new Label("labelComponent", "Initial value.");
@@ -339,4 +339,4 @@ new AjaxLink("ajaxLink"){
 };
 {code}
 
-Please note that in the code above we didn't invoked method setOutputMarkupId(true) as setOutputMarkupPlaceholderTag already does it internally.
+Please note that in the code above we didn't invoked method @setOutputMarkupId(true)@ as @setOutputMarkupPlaceholderTag@ already does it internally.

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -4,9 +4,9 @@ In addition to specific components, Wick
 
 h3. AjaxEventBehavior
 
-AjaxEventBehavior allows to handle a JavaScript event (like click, change, etc...) on server side via AJAX. Its constructor takes in input the name of the event that must be handled. Every time this event is fired for a given component on client side, the callback method onEvent(AjaxRequestTarget target) is executed. onEvent is abstract, hence we must implement it to tell AjaxEventBehavior what to do when the specified event occurs.
+AjaxEventBehavior allows to handle a JavaScript event (like click, change, etc...) on server side via AJAX. Its constructor takes in input the name of the event that must be handled. Every time this event is fired for a given component on client side, the callback method @onEvent(AjaxRequestTarget target)@ is executed. onEvent is abstract, hence we must implement it to tell @AjaxEventBehavior@ what to do when the specified event occurs.
 
-In project AjaxEventBehaviorExample we used this behavior to build a “clickable” Label component that counts the number of clicks. Here is the code from the home page of the project:
+In project @AjaxEventBehaviorExample@ we used this behavior to build a “clickable” Label component that counts the number of clicks. Here is the code from the home page of the project:
 
 *HTML:*
 {code:html}
@@ -60,9 +60,9 @@ class ClickCounterLabel extends Label{
 }
 {code}
 
-In the code above we have declared a custom label class named ClickCounterLabel that exposes a public integer field called clickCounter. Then, in the home page we have attached a AjaxEventBehavior to our custom label to increment clickCounter every time it receives a click event.
+In the code above we have declared a custom label class named @ClickCounterLabel@ that exposes a public integer field called clickCounter. Then, in the home page we have attached a @AjaxEventBehavior@ to our custom label to increment clickCounter every time it receives a click event.
 
-The number of clicks is displayed with another standard label named clickCounter.
+The number of clicks is displayed with another standard label named @clickCounter@.
 
 h3. AjaxFormSubmitBehavior
 
@@ -81,7 +81,7 @@ h3. AjaxFormComponentUpdatingBehavior
 
 This behavior updates the model of the form component it is attached to when a given event occurs. The standard form submitting process is skipped and the behavior validates only its form component. 
 
-The behavior doesn't work with radio buttons and checkboxes. For these kinds of components we must use AjaxFormChoiceComponentUpdatingBehavior:
+The behavior doesn't work with radio buttons and checkboxes. For these kinds of components we must use @AjaxFormChoiceComponentUpdatingBehavior@:
 
 {code}
 Form form = new Form("form");		
@@ -98,7 +98,7 @@ add(form.add(textField));
 
 h3. AbstractAjaxTimerBehavior
 
-AbstractAjaxTimerBehavior executes callback method onTimer(AjaxRequestTarget target) at a specified interval. The behavior can be stopped and restarted at a later time with methods stop(AjaxRequestTarget target) and restart(AjaxRequestTarget target):
+@AbstractAjaxTimerBehavior@ executes callback method @onTimer(AjaxRequestTarget target)@ at a specified interval. The behavior can be stopped and restarted at a later time with methods @stop(AjaxRequestTarget target)@ and @restart(AjaxRequestTarget target)@:
 
 {code}
 Label dynamicLabel = new Label("dynamicLabel");

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -2,11 +2,11 @@
 
 One of the things we must take care of when we use AJAX is to notify user when an AJAX request is already in progress. This is usually done displaying an animated picture as activity indicator while the AJAX request is running. 
 
-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.
+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@). 
 
-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:
+@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:
 
 {code}
 //1-Implement interface IAjaxIndicatorAware
@@ -28,4 +28,4 @@ public class MyComponent extends Compone
 }
 {code}
 
-If we need to change the default picture used as activity indicator, we can override method getIndicatorUrl() of AjaxIndicatorAppender and return the URL to the desired picture.
\ No newline at end of file
+If we need to change the default picture used as activity indicator, we can override method @getIndicatorUrl()@ of @AjaxIndicatorAppender@ and return the URL to the desired picture.
\ No newline at end of file

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -22,20 +22,20 @@ bh, pre, bsh, ah, sh, fh, coh | This is 
 A full list of the available request parameters as well as more details on the related JavaScript code can be found at "https://cwiki.apache.org/confluence/ display/WICKET/Wicket+Ajax":https://cwiki.apache.org/confluence/ display/WICKET/Wicket+Ajax .
 {note}
 
-Parameters 'u' (callback URL) and 'c' (the id of the component) are generated by the AJAX behavior that will serve the AJAX call and they are not accessible through AjaxRequestAttributes.
+Parameters 'u' (callback URL) and 'c' (the id of the component) are generated by the AJAX behavior that will serve the AJAX call and they are not accessible through @AjaxRequestAttributes@.
 
-Here is the final AJAX function generate for the behavior used in example project AjaxEventBehavior Example:
+Here is the final AJAX function generate for the behavior used in example project @AjaxEventBehavior@ Example:
 
 {code}
 Wicket.Ajax.ajax({"u":"./?0-1.IBehaviorListener.0-clickCounterLabel", "e":"click",               
                   "c":"clickCounterLabel1"});
 {code}
 
-Even if most of the times we will let Wicket generate request attributes for us, both AJAX components and behaviors give us the chance to modify them overriding their method updateAjaxAttributes (AjaxRequestAttributes attributes). 
+Even if most of the times we will let Wicket generate request attributes for us, both AJAX components and behaviors give us the chance to modify them overriding their method @updateAjaxAttributes (AjaxRequestAttributes attributes)@. 
 
-One of the attribute we may need to modify is the list of IAjaxCallListeners returned by method getAjaxCallListeners(). 
+One of the attribute we may need to modify is the list of @IAjaxCallListeners@ returned by method @getAjaxCallListeners()@. 
 
-IAjaxCallListener defines a set of methods which return the JavaScript code (as a CharSequence) that must be executed on client side when the AJAX request handling reaches a given stage:
+@IAjaxCallListener@ defines a set of methods which return the JavaScript code (as a @CharSequence@) that must be executed on client side when the AJAX request handling reaches a given stage:
 
 * *getBeforeHandler(Component)*: returns the JavaScript code that will be executed before any other handlers returned by IAjaxCallListener. The code is executed in a scope where it can use variable attrs, which is an array containing the JSON parameters passed to Wicket.Ajax.ajax. 
 * *getPrecondition(Component)*: returns the JavaScript code that will be used as precondition for the AJAX call. If the script returns false then neither the Ajax call nor the other handlers will be executed. The code is executed in a scope where it can use variable attrs, which is the same variable seen for getBeforeHandler. 
@@ -51,4 +51,4 @@ IAjaxCallListener defines a set of metho
 * *getFailureHandler(Component)*: returns the JavaScript code that will be executed if the AJAX call has returned with a failure. The code is executed in a scope where it can use variable attrs, which is the same variable seen for getBeforeHandler. 
 * *getCompleteHandler(Component)*: returns the JavaScript that will be invoked after success or failure handler has been executed. The code is executed in a scope where it can use variables attrs, jqXHR and textStatus which are the same variables seen for getSuccessHandler. 
 
-In the next paragraph we will see an example of custom IAjaxCallListener designed to disable a component during AJAX request processing.
+In the next paragraph we will see an example of custom @IAjaxCallListener@ designed to disable a component during AJAX request processing.

Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_6.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_6.gdoc?rev=1550971&r1=1550970&r2=1550971&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_6.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter17/chapter17_6.gdoc Sat Dec 14 21:13:09 2013
@@ -1,6 +1,6 @@
 
 
-Displaying an activity indicator is a nice way to notify user that an AJAX request is already running, but sometimes is not enough. In some situations we may need to completely disable a component during AJAX request processing, for example when we want to avoid that impatient users submit a form multiple times. In this paragraph we will see how to accomplish this goal building a custom and reusable IAjaxCallListener. The code used in this example is from project CustomAjaxListenerExample.
+Displaying an activity indicator is a nice way to notify user that an AJAX request is already running, but sometimes is not enough. In some situations we may need to completely disable a component during AJAX request processing, for example when we want to avoid that impatient users submit a form multiple times. In this paragraph we will see how to accomplish this goal building a custom and reusable @IAjaxCallListener@. The code used in this example is from project @CustomAjaxListenerExample@.
 
 h3. What we want for our listener
 
@@ -14,13 +14,13 @@ The final result will look like this:
 
 h3. How to implement the listener
 
-The listener will implement methods getBeforeHandler and getAfterHandler: the first will return the code needed to place an overlay <div> on the desired component while the second must remove this overlay when the AJAX call has completed.
+The listener will implement methods @getBeforeHandler@ and @getAfterHandler@: the first will return the code needed to place an overlay <div> on the desired component while the second must remove this overlay when the AJAX call has completed.
 
 To move and resize the overlay area we will use another module from "JQueryUI library":http://jqueryui.com/position/ that allows us to position DOM elements on our page relative to another element.
 
 So our listener will depend on four static resources: the JQuery library, the position module of JQuery UI, the custom code used to move the overlay <div> and the picture used as activity indicator. Except for the activity indicator, all these resources must be added to page header section in order to be used. 
 
-Ajax call listeners can contribute to header section by simply implementing interface IComponentAwareHeaderContributor. Wicket provides adapter class AjaxCallListener that implements both IAjaxCallListener and IComponentAwareHeaderContributor. We will use this class as base class for our listener.
+Ajax call listeners can contribute to header section by simply implementing interface @IComponentAwareHeaderContributor@. Wicket provides adapter class @AjaxCallListener@ that implements both @IAjaxCallListener@ and @IComponentAwareHeaderContributor@. We will use this class as base class for our listener.
 
 h3. JavaScript code
 
@@ -119,9 +119,9 @@ public class DisableComponentListener ex
 }
 {code}
 
-As you can see in the code above we have created a function (getIndicatorUrl) to retrieve the URL of the indicator picture. This was done in order to make the picture customizable by overriding this method.
+As you can see in the code above we have created a function (@getIndicatorUrl@) to retrieve the URL of the indicator picture. This was done in order to make the picture customizable by overriding this method.
 
-Once we have our listener in place, we can finally use it in our example overwriting method updateAjaxAttributes of the AJAX button that submits the form:
+Once we have our listener in place, we can finally use it in our example overwriting method @updateAjaxAttributes@ of the AJAX button that submits the form:
 
 {code}
 //...
@@ -139,7 +139,7 @@ h3. Global listeners
 
 So far we have seen how to use an AJAX call listener to track the AJAX activity of a single component. In addition to these kinds of listeners, Wicket provides also global listeners which are triggered for any AJAX request sent from a page. 
 
-Global AJAX call events are handled with JavaScript. We can register a callback function for a specific event of the AJAX call lifecycle with function Wicket.Event.subscribe('<eventName>', <callback Function>). The first parameter of this function is the name of the event we want to handle. The possible names are:
+Global AJAX call events are handled with JavaScript. We can register a callback function for a specific event of the AJAX call lifecycle with function @Wicket.Event.subscribe('<eventName>', <callback Function>)@. The first parameter of this function is the name of the event we want to handle. The possible names are:
 
 * '/ajax/call/before': called before any other event handler.
 * '/ajax/call/beforeSend': called just before the AJAX call.
@@ -147,10 +147,10 @@ Global AJAX call events are handled with
 * '/ajax/call/success': called if the AJAX call has successfully returned.
 * '/ajax/call/failure': called if the AJAX call has returned with a failure.
 * '/ajax/call/complete': called when the AJAX call has completed.
-* '/dom/node/removing': called when a component is about to be removed via AJAX. This  happens when component markup is updated via AJAX (i.e. the component itself or one of its containers has been added to AjaxRequestTarget) 
-* '/dom/node/added': called when a component has been added via AJAX. Just like '/dom/node/removing', this event is triggered when a component is added to AjaxRequest Target.
+* '/dom/node/removing': called when a component is about to be removed via AJAX. This  happens when component markup is updated via AJAX (i.e. the component itself or one of its containers has been added to @AjaxRequestTarget@) 
+* '/dom/node/added': called when a component has been added via AJAX. Just like '/dom/node/removing', this event is triggered when a component is added to @AjaxRequestTarget@.
 
-The callback function takes in input the following parameters:  attrs, jqXHR, textStatus, jqEvent and errorThrown. The first three parameters are the same seen before with IAjaxCallListener while jqEvent is an event internally fired by Wicket. The last parameter errorThrown indicates if an error has occurred during the AJAX call. 
+The callback function takes in input the following parameters:  attrs, jqXHR, textStatus, jqEvent and errorThrown. The first three parameters are the same seen before with @IAjaxCallListener@ while jqEvent is an event internally fired by Wicket. The last parameter errorThrown indicates if an error has occurred during the AJAX call. 
 
 To see a basic example of use of a global AJAX call listener, let's go back to our custom datepicker created in chapter 14. When we built it we didn't think about a possible use of the component with AJAX.  When a complex component like our datepicker is refreshed via AJAX, the following two side effects can occur: 
 
@@ -159,7 +159,7 @@ To see a basic example of use of a globa
 
 To solve the second unwanted side effect we can register a global AJAX call listener that completely removes the datepicker functionality from our component before it is removed due to an AJAX refresh (which fires event '/dom/node/removing'). 
 
-Project CustomDatepickerAjax contains a new version of our datepicker which adds to its JavaScript file JQDatePicker.js the code needed to register a callback function that gets rid of the JQuery datepicker before the component is removed from the DOM:
+Project @CustomDatepickerAjax@ contains a new version of our datepicker which adds to its JavaScript file JQDatePicker.js the code needed to register a callback function that gets rid of the JQuery datepicker before the component is removed from the DOM:
 
 {code}
 Wicket.Event.subscribe('/dom/node/removing', 

Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_1.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_1.gdoc?rev=1550971&r1=1550970&r2=1550971&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_1.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter18/chapter18_1.gdoc Sat Dec 14 21:13:09 2013
@@ -1,10 +1,10 @@
 
 
-WicketStuff provides a module called wicketstuff-javaee-inject that contains component instantiation listener JavaEEComponentInjector. If we register this listener in our application we can use standard EJB annotations to inject dependencies into our Wicket components.
+WicketStuff provides a module called wicketstuff-javaee-inject that contains component instantiation listener @JavaEEComponentInjector@. If we register this listener in our application we can use standard EJB annotations to inject dependencies into our Wicket components.
 
-To register a component instantiation listener in Wicket we must use Application's method getComponentInstantiationListeners which returns a typed collection of IComponent InstantiationListeners. 
+To register a component instantiation listener in Wicket we must use @Application@'s method @getComponentInstantiationListeners@ which returns a typed collection of @IComponentInstantiationListeners@. 
 
-The following initialization code is taken from project EjbInjectionExample: 
+The following initialization code is taken from project @EjbInjectionExample@: 
 
 {code}
 public class WicketApplication extends WebApplication
@@ -29,7 +29,7 @@ public class EnterpriseMessage {
 }
 {code}
 
-Please note that we have used annotation @ManagedBean to decorate our object. Now to inject it into the home page we must add a field of type EnterpriseMessage and annotate it with annotation @EJB:
+Please note that we have used annotation ManagedBean to decorate our object. Now to inject it into the home page we must add a field of type EnterpriseMessage and annotate it with annotation @EJB:
 
 {code}
 public class HomePage extends WebPage {

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=1550971&r1=1550970&r2=1550971&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 21:13:09 2013
@@ -2,7 +2,7 @@
 
 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:
+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:
 
 {code}
 public class WicketApplication extends WebApplication
@@ -24,9 +24,9 @@ public class WicketApplication extends W
 }
 {code}
 
-As we can see in the code above, the constructor of SpringComponentInjector takes in input also an instance of Spring context.
+As we can see in the code above, the constructor of @SpringComponentInjector@ takes in input also an instance of Spring context.
 
-The injected object is the same used in the previous project EjbInjectionExample, it differs only for the greeting message:
+The injected object is the same used in the previous project @EjbInjectionExample@, it differs only for the greeting message:
 
 {code}
 @ManagedBean
@@ -51,7 +51,7 @@ public class HomePage extends WebPage {
 }
 {code}
 
-By default @SpringBean searches into Spring context for a bean having the same type of the annotated field. If we want we can specify also the name of the bean to use as injected object and we can declare if the dependency is required or not. By default dependencies are required and if they can not be resolved to a compatible bean, Wicket will throw an IllegalStateException:
+By default @SpringBean searches into Spring context for a bean having the same type of the annotated field. If we want we can specify also the name of the bean to use as injected object and we can declare if the dependency is required or not. By default dependencies are required and if they can not be resolved to a compatible bean, Wicket will throw an @IllegalStateException@:
 
 {code}
   //set the dependency as not required, i.e the field can be left null