summaryrefslogtreecommitdiffstats
path: root/documentation/components/components-customcomponent.asciidoc
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/components/components-customcomponent.asciidoc')
-rw-r--r--documentation/components/components-customcomponent.asciidoc2
1 files changed, 0 insertions, 2 deletions
diff --git a/documentation/components/components-customcomponent.asciidoc b/documentation/components/components-customcomponent.asciidoc
index cf898ebf17..96024d0ace 100644
--- a/documentation/components/components-customcomponent.asciidoc
+++ b/documentation/components/components-customcomponent.asciidoc
@@ -22,8 +22,6 @@ The benefit of wrapping a layout composite is mainly encapsulation - hiding the
implementation details of the composition. Otherwise, a user of the composite
could rely on implementation details, which would create an unwanted dependency.
-IMPORTANT: The [classname]#Composite# component is currently being developed and only available in the Framework 8.1 prerelease versions, starting from 8.1.0.alpha6.
-
To create a composite, you need to inherit [classname]#Composite# or
[classname]#CustomComponent# and set the __composition root__ component in the
constructor. The composition root is typically a layout component that contains