svn commit: r1534370 - in /wicket/common/site/trunk/_site/guide/guide/src/docs/guide: chapter13/chapter13_3.gdoc chapter8/chapter8_3.gdoc chapter8/chapter8_4.gdoc

[ad...@apache.org]

Author: adelbene
Date: Mon Oct 21 21:00:28 2013
New Revision: 1534370

URL: http://svn.apache.org/r1534370
Log:
Fixed list elements to make them bold.

Modified:
    wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter13/chapter13_3.gdoc
    wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_3.gdoc
    wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter8/chapter8_4.gdoc

Modified: wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter13/chapter13_3.gdoc
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter13/chapter13_3.gdoc?rev=1534370&r1=1534369&r2=1534370&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter13/chapter13_3.gdoc (original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/chapter13/chapter13_3.gdoc Mon Oct 21 21:00:28 2013
@@ -80,11 +80,11 @@ h3. Extending the default lookup algorit
 
 Wicket implements the default lookup algorithm using the strategy pattern1. The concrete strategies are abstracted with the interface org.apache.wicket.resource.loader.IStringResource Loader. By default Wicket uses the following implementations of IStringResourceLoader (sorted by execution order):
 
-# ComponentStringResourceLoader: implements most of the default algorithm. It searches for a given resource across bundles from the container hierarchy, from class hierarchy and from the given component.
-# PackageStringResourceLoader: searches into package bundles.
-# ClassStringResourceLoader: searches into bundles of a given class. By default the target class is the application class.
-# ValidatorStringResourceLoader: searches for resources into validator's bundles. A list of validators is provided by the form component that failed validation.
-# InitializerStringResourceLoader: this resource allows internationalization to interact with the initialization mechanism of the framework that will be illustrated in paragraph 15.4.
+# *ComponentStringResourceLoader:* implements most of the default algorithm. It searches for a given resource across bundles from the container hierarchy, from class hierarchy and from the given component.
+# *PackageStringResourceLoader:* searches into package bundles.
+# *ClassStringResourceLoader:* searches into bundles of a given class. By default the target class is the application class.
+# *ValidatorStringResourceLoader:* searches for resources into validator's bundles. A list of validators is provided by the form component that failed validation.
+# *InitializerStringResourceLoader:* this resource allows internationalization to interact with the initialization mechanism of the framework that will be illustrated in paragraph 15.4.
 
 Developer can customize lookup algorithm removing default resource loaders or adding custom implementations to the list of the resource loaders in use. This task can be accomplished using method getStringResourceLoaders of setting interface org.apache.wicket.settings. IResourceSettings:
 

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=1534370&r1=1534369&r2=1534370&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 Mon Oct 21 21:00:28 2013
@@ -57,22 +57,22 @@ public final void setResponsePage(final 
 h3. RequestCycle's hook methods and listeners
 
 The RequestCycle comes with some hook methods which can be overridden to perform custom actions when request handling reaches a specific stage. These methods are:
-* onBeginRequest(): called when the RequestCycle is about to start handling the request. 
-* onEndRequest(): called when the RequestCycle has finished to handle the request
-* onDetach(): called after the request handling has completed and the RequestCycle is about to be detached from its thread. The default implementation of this method invokes detach() on the current session (the Session class will be shortly discussed in paragraph 7.4).
+* *onBeginRequest():* called when the RequestCycle is about to start handling the request. 
+* *onEndRequest():* called when the RequestCycle has finished to handle the request
+* *onDetach():* called after the request handling has completed and the RequestCycle is about to be detached from its thread. The default implementation of this method invokes detach() on the current session (the Session class will be shortly discussed in paragraph 7.4).
 
 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:
-* onBeginRequest(RequestCycle cycle): (see the description above)
-* onEndRequest(RequestCycle cycle): (see the description above)
-* onDetach(RequestCycle cycle): (see the description above)
-* onRequestHandlerResolved(RequestCycle cycle, IRequestHandler handler): called when an IRequestHandler has been resolved.
-* onRequestHandlerScheduled(RequestCycle cycle, IRequestHandler handler): called when an IRequestHandler has been scheduled for execution.
-* onRequestHandlerExecuted(RequestCycle cycle, IRequestHandler handler): called when an IRequestHandler has been executed.
-* onException(RequestCycle cycle, Exception ex): called when an exception has been thrown during request processing.
-* 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.
+* *onBeginRequest(RequestCycle cycle):* (see the description above)
+* *onEndRequest(RequestCycle cycle):* (see the description above)
+* *onDetach(RequestCycle cycle):* (see the description above)
+* *onRequestHandlerResolved(RequestCycle cycle, IRequestHandler handler):* called when an IRequestHandler has been resolved.
+* *onRequestHandlerScheduled(RequestCycle cycle, IRequestHandler handler):* called when an IRequestHandler has been scheduled for execution.
+* *onRequestHandlerExecuted(RequestCycle cycle, IRequestHandler handler):* called when an IRequestHandler has been executed.
+* *onException(RequestCycle cycle, Exception ex):* called when an exception has been thrown during request processing.
+* *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:
 

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=1534370&r1=1534369&r2=1534370&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 Mon Oct 21 21:00:28 2013
@@ -28,9 +28,9 @@ h3. Handling session attributes
 
 The Session class handles session attributes in much the same way as the standard interface javax.servlet.http.HttpSession. The following methods are provided to create, read and remove session attributes:
 
-* setAttribute(String name, Serializable value): creates an attribute identified by the given name. If the session already contains an attribute with the same name, the new value will replace the existing one. The value must be a serializable object.
-* getAttribute(String name): returns the value of the attribute identified by the given name, or null if the name does not correspond to any attribute.
-* removeAttribute(String name): removes the attribute identified by the given name.
+* *setAttribute(String name, Serializable value):* creates an attribute identified by the given name. If the session already contains an attribute with the same name, the new value will replace the existing one. The value must be a serializable object.
+* *getAttribute(String name):* returns the value of the attribute identified by the given name, or null if the name does not correspond to any attribute.
+* *removeAttribute(String name):* removes the attribute identified by the given name.
 
 By default class WebSession will use the underlying http session to store attributes. Wicket will automatically add a prefix to the name of the attributes. This prefix is returned by the WebApplication's method getSessionAttributePrefix().
 
@@ -109,10 +109,10 @@ h3. Storing arbitrary objects with metad
 
 JavaServer Pages Specification1 defines 4 scopes in which a page can create and access a variable. These scopes are:
 
-* request: variables declared in this scope can be seen only by pages processing the same request. The lifespan of these variables is (at most) equal to the one of the related request. They are discarded when the full response has been generated or when the request is forwarded somewhere else.
-* page: variables declared in this scope can be seen only by the page that has created them. 
-* session: variables in session scope can be created and accessed by every page used in the same session where they are defined.
-* application: this is the widest scope. Variables declared in this scope can be used by any page of a given web application.
+* *request:* variables declared in this scope can be seen only by pages processing the same request. The lifespan of these variables is (at most) equal to the one of the related request. They are discarded when the full response has been generated or when the request is forwarded somewhere else.
+* *page:* variables declared in this scope can be seen only by the page that has created them. 
+* *session:* variables in session scope can be created and accessed by every page used in the same session where they are defined.
+* *application:* this is the widest scope. Variables declared in this scope can be used by any page of a given web application.
 
 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.