This is an automated email from the ASF dual-hosted git repository.

mgrigorov pushed a commit to branch wicket-9.x
in repository https://gitbox.apache.org/repos/asf/wicket.git


The following commit(s) were added to refs/heads/wicket-9.x by this push:
     new f0cdafd  Fix index of a list item
f0cdafd is described below

commit f0cdafda68bb953889671440af762dbca5f629a3
Author: Martin Tzvetanov Grigorov <[email protected]>
AuthorDate: Tue May 4 17:33:46 2021 +0300

    Fix index of a list item
    
    (cherry picked from commit ae7a254f112bd07bebf09a7ab2c8725dd4af0d64)
---
 .../src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc
 
b/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc
index a2c778a..45df71c 100644
--- 
a/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc
+++ 
b/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_1.adoc
@@ -6,7 +6,7 @@ During its life a Wicket component goes through the following 
stages:
 1. *Initialization:* a component is instantiated and initialized by Wicket.
 2. *Rendering:* components are prepared for rendering and generate markup. If 
a component contains children (i.e. is a subclass of _MarkupContainer_) their 
rendering result is included in the resulting markup.
 3. *Removed:* this stage is triggered when a component is explicitly removed 
from its component hierarchy, i.e. when its parent invokes _remove(component)_ 
on it. This stage is facultative and is never triggered for pages.
-3. *Detached:* after request processing has ended all components are notified 
to detach any state that is no longer needed. 
+4. *Detached:* after request processing has ended all components are notified 
to detach any state that is no longer needed.
 
 The following picture shows the state diagram of component lifecycle:
 

Reply via email to