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 2025/02/07 10:20:52 UTC

(wicket) branch master updated: Removed reference to pre-10.x versions

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

adelbene pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/wicket.git


The following commit(s) were added to refs/heads/master by this push:
     new 040e772e84 Removed reference to pre-10.x versions
040e772e84 is described below

commit 040e772e84381d56d02961207486a584f5f04717
Author: Andrea Del Bene <ad...@apache.org>
AuthorDate: Fri Feb 7 11:20:42 2025 +0100

    Removed reference to pre-10.x versions
---
 wicket-user-guide/src/main/asciidoc/advanced/advanced_3.adoc          | 2 +-
 wicket-user-guide/src/main/asciidoc/ajax/ajax_5.adoc                  | 2 +-
 wicket-user-guide/src/main/asciidoc/ajax/ajax_7.adoc                  | 2 +-
 .../src/main/asciidoc/componentLifecycle/componentLifecycle_5.adoc    | 2 +-
 .../src/main/asciidoc/jsintegration/jsintegration_2.adoc              | 2 +-
 wicket-user-guide/src/main/asciidoc/layout/layout_2.adoc              | 2 +-
 wicket-user-guide/src/main/asciidoc/resources/resources_4.adoc        | 4 ++--
 wicket-user-guide/src/main/asciidoc/resources/resources_9.adoc        | 2 +-
 .../src/main/asciidoc/versioningCaching/versioningCaching_2.adoc      | 4 ++--
 9 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/wicket-user-guide/src/main/asciidoc/advanced/advanced_3.adoc b/wicket-user-guide/src/main/asciidoc/advanced/advanced_3.adoc
index f651665e77..cec0b54a1a 100644
--- a/wicket-user-guide/src/main/asciidoc/advanced/advanced_3.adoc
+++ b/wicket-user-guide/src/main/asciidoc/advanced/advanced_3.adoc
@@ -1,5 +1,5 @@
 
-Starting from version 1.5 Wicket offers an event-based infrastructure for inter-component communication. The infrastructure is based on two simple interfaces (both in package _org.apache.wicket.event_) : _IEventSource_ and _IEventSink_.
+Wicket offers an event-based infrastructure for inter-component communication. The infrastructure is based on two simple interfaces (both in package _org.apache.wicket.event_) : _IEventSource_ and _IEventSink_.
 
 The first interface must be implemented by those entities that want to broadcast en event while the second interface must be implemented by those entities that want to receive a broadcast event.
 
diff --git a/wicket-user-guide/src/main/asciidoc/ajax/ajax_5.adoc b/wicket-user-guide/src/main/asciidoc/ajax/ajax_5.adoc
index a2de03f0dd..e73bc49e8c 100644
--- a/wicket-user-guide/src/main/asciidoc/ajax/ajax_5.adoc
+++ b/wicket-user-guide/src/main/asciidoc/ajax/ajax_5.adoc
@@ -1,7 +1,7 @@
 
 
 
-Starting from version 6.0 Wicket has introduced two entities which allow us to control how an AJAX request is generated on client side and to specify the custom JavaScript code we want to execute during request handling. These entities are class _AjaxRequestAttributes_ and interface _IAjaxCallListener_, both placed in package _org.apache.wicket.ajax.attributes_.
+Wicket has two entities which allow us to control how an AJAX request is generated on client side and to specify the custom JavaScript code we want to execute during request handling. These entities are class _AjaxRequestAttributes_ and interface _IAjaxCallListener_, both placed in package _org.apache.wicket.ajax.attributes_.
 
 AjaxRequestAttributes exposes the attributes used to generate the JavaScript call invoked on client side to start an AJAX request. Each attribute will be passed as a  http://en.wikipedia.org/wiki/JSON[JSON] parameter to the JavaScript function _Wicket.Ajax.ajax_ which is responsible for sending the concrete AJAX request. Every JSON parameter is identified by a short name. Here is a partial list of the available parameters:
 
diff --git a/wicket-user-guide/src/main/asciidoc/ajax/ajax_7.adoc b/wicket-user-guide/src/main/asciidoc/ajax/ajax_7.adoc
index 2f9feac9cb..01b8cf2d8e 100644
--- a/wicket-user-guide/src/main/asciidoc/ajax/ajax_7.adoc
+++ b/wicket-user-guide/src/main/asciidoc/ajax/ajax_7.adoc
@@ -1,6 +1,6 @@
 
 Wicket makes working with AJAX easy and pleasant with its component-oriented abstraction. However as side effect, AJAX components and behaviors make their hosting page stateful. This can be quite annoying if we are working on a page that must be stateless (for example a login page).
-Starting from version 7.4.0 Wicket has made quite easy forcing existing AJAX components to be stateless. All we have to do is to override component's method _getStatelessHint_ returning true:
+Wicket makes quite easy forcing existing AJAX components to be stateless. All we have to do is to override component's method _getStatelessHint_ returning true:
 
 [source,java]
 ----
diff --git a/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_5.adoc b/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_5.adoc
index c08351b103..5700a4cfbe 100644
--- a/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_5.adoc
+++ b/wicket-user-guide/src/main/asciidoc/componentLifecycle/componentLifecycle_5.adoc
@@ -3,6 +3,6 @@
 
 This stage is entered when a component is removed from its container hierarchy. The only hook method for this phase is _onRemove()_. If our component still holds some resources needed during rendering phase, we can override this method to release them.
 
-Once a component has been removed we are free to add it again to the same container or to a different one. Starting from version 6.18.0 Wicket added a further hook method called _onReAdd()_ which is triggered every time a previously removed component is re-added to a container.
+Once a component has been removed we are free to add it again to the same container or to a different one. Wicket offers a further hook method called _onReAdd()_ which is triggered every time a previously removed component is re-added to a container.
 Please note that while _onInitialize()_ is called only the very first time a component is added, _onReAdd()_ is called every time it is re-added after having been removed.
 
diff --git a/wicket-user-guide/src/main/asciidoc/jsintegration/jsintegration_2.adoc b/wicket-user-guide/src/main/asciidoc/jsintegration/jsintegration_2.adoc
index 2b0053d0cb..b931052951 100644
--- a/wicket-user-guide/src/main/asciidoc/jsintegration/jsintegration_2.adoc
+++ b/wicket-user-guide/src/main/asciidoc/jsintegration/jsintegration_2.adoc
@@ -3,7 +3,7 @@
 
 Our new component will extend the built-in text field _org.apache.wicket.extensions.markup.html.form.DateTextField_ which already uses a java.util.Date as model object and already performs conversion and validation for input values. Since the component must be self-contained, we must ensure that the JavaScript libraries it relies on (JQuery and JQuery UI) will be always available.
 
-Starting from version 6.0 Wicket has adopted JQuery as backing JavaScript library so we can use the  version bundled with Wicket for our custom datepicker.
+Wicket adopted JQuery as backing JavaScript library so we can use the version bundled with Wicket for our custom datepicker.
 
 To make JQuery UI available we should instead go to its official site, download the required artifacts and use them as package resources of our component.
 
diff --git a/wicket-user-guide/src/main/asciidoc/layout/layout_2.adoc b/wicket-user-guide/src/main/asciidoc/layout/layout_2.adoc
index 3c631c6921..723a6b986b 100644
--- a/wicket-user-guide/src/main/asciidoc/layout/layout_2.adoc
+++ b/wicket-user-guide/src/main/asciidoc/layout/layout_2.adoc
@@ -42,7 +42,7 @@ Label name = (Label)get("innerContainer:name");
 ----
 
 * replace a specific child component with a new component having the same id (with method _replace_).
-* iterate thought children components. This can be done in the old way (pre-Wicket 8) using method _iterator_ or using visitor pattern with method _visitChildren_. Starting from Wicket 8 the same task can be accomplished using the _stream_ object returned by methods _stream_ (which contains only the direct children) and _streamChildren_ (which contains all children).
+* iterate thought children components. This can be done in the old way (pre-Wicket 8) using method _iterator_ or using visitor pattern with method _visitChildren_. The same task can be accomplished using Java Streams and Lambdas with methods _stream_ (which returns a stream containing only the direct children) and _streamChildren_ (which returns a stream containing all children).
 
 Both _Panel_ and _WebPage_ have their own associated markup file which is used to render the corresponding component. If such file is not provided, Wicket will apply markup inheritance looking for a markup file through their ancestor classes. When a panel is attached to a container, the content of its markup file is inserted into its related tag.
 
diff --git a/wicket-user-guide/src/main/asciidoc/resources/resources_4.adoc b/wicket-user-guide/src/main/asciidoc/resources/resources_4.adoc
index 3e5693c150..d4a1124310 100644
--- a/wicket-user-guide/src/main/asciidoc/resources/resources_4.adoc
+++ b/wicket-user-guide/src/main/asciidoc/resources/resources_4.adoc
@@ -12,8 +12,8 @@ Header entries are instances of abstract class _org.apache.wicket.markup.head.He
 * *OnLoadHeaderItem:* the JavaScript code added with this class is executed after the whole page is loaded, external files included. The factory method is _forScript(CharSequence javaScript)_.
 * *PriorityHeaderItem:* it wraps another header item and ensures that it will have the priority over the other items during rendering phase.
 * *StringHeaderItem:* with this class we can add an arbitrary text to the header section. Factory method is _forString(CharSequence string)_.
-* *MetaDataHeaderItem:* starting from version 6.17.0, Wicket provides this class to handle meta information such as <meta> tags or http://en.wikipedia.org/wiki/Canonical_link_element[canonical link element]
-* *HtmlImportHeaderItem:* introduced in Wicket 6.19.0, provides a HTML5 functionality to include other wicket pages (other html files) into the current generated. Factory methods provided by this class are _forImportLinkTag_ which takes the page class or the url of the page / html to be included.
+* *MetaDataHeaderItem:* Wicket provides this class to handle meta information such as <meta> tags or http://en.wikipedia.org/wiki/Canonical_link_element[canonical link element]
+* *HtmlImportHeaderItem:* provides a HTML5 functionality to include other wicket pages (other html files) into the current generated. Factory methods provided by this class are _forImportLinkTag_ which takes the page class or the url of the page / html to be included.
 
 
 In the following example our custom component loads a CSS file as a package resource (placed in the same package) and it adds it to header section. 
diff --git a/wicket-user-guide/src/main/asciidoc/resources/resources_9.adoc b/wicket-user-guide/src/main/asciidoc/resources/resources_9.adoc
index ce2c65b1a4..2eee0d1096 100644
--- a/wicket-user-guide/src/main/asciidoc/resources/resources_9.adoc
+++ b/wicket-user-guide/src/main/asciidoc/resources/resources_9.adoc
@@ -1,5 +1,5 @@
 
-Starting from version 6.15.0 we can specify where header contributors must be rendered inside <head> tag using the placeholder tag _<wicket:header-items/>_: 
+We can also specify where header contributors must be rendered inside <head> tag using the placeholder tag _<wicket:header-items/>_: 
 
 [source,html]
 ----
diff --git a/wicket-user-guide/src/main/asciidoc/versioningCaching/versioningCaching_2.adoc b/wicket-user-guide/src/main/asciidoc/versioningCaching/versioningCaching_2.adoc
index e118ce4da4..eb11460212 100644
--- a/wicket-user-guide/src/main/asciidoc/versioningCaching/versioningCaching_2.adoc
+++ b/wicket-user-guide/src/main/asciidoc/versioningCaching/versioningCaching_2.adoc
@@ -71,9 +71,9 @@ If for any reason we need to switch off versioning for a given page, we can call
 
 === Pluggable serialization
 
-Starting from version 1.5 it is possible to choose which implementation of Java serialization will be used by Wicket to store page versions. Wicket serializes pages using an implementation of interface _org.apache.wicket.serialize.ISerializer_. The default implementation is _org.apache.wicket.serialize.java.JavaSerializer_ and it uses the standard Java serialization mechanism based on classes _ObjectOutputStream_ and _ObjectInputStream_. However on internet we can find other interesting  [...]
+Wicket serializes pages using an implementation of interface _org.apache.wicket.serialize.ISerializer_. The default implementation is _org.apache.wicket.serialize.java.JavaSerializer_ and it uses the standard Java serialization mechanism based on classes _ObjectOutputStream_ and _ObjectInputStream_. However on internet we can find other interesting serialization libraries like https://github.com/EsotericSoftware/kryo[Kryo].
 
-We can access this class inside the method _init_ of the class _Application_ using the _getFrameworkSettings()_ method :
+We can set a custom serializer inside _init_ method accessing Wicket settings with _getFrameworkSettings()_:
 
 [source,java]
 ----