From 2f71bce092badfc225d200e197ea217341d6ae8f Mon Sep 17 00:00:00 2001 From: elmot Date: Wed, 6 Apr 2016 10:50:23 +0300 Subject: [PATCH] Documentation for container switch limitations (#18323) Change-Id: Ib8ce5d82fe2c270296bf9196fec103edc1534d46 --- documentation/datamodel/datamodel-container.asciidoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/documentation/datamodel/datamodel-container.asciidoc b/documentation/datamodel/datamodel-container.asciidoc index c68e4bec4e..5e610cd671 100644 --- a/documentation/datamodel/datamodel-container.asciidoc +++ b/documentation/datamodel/datamodel-container.asciidoc @@ -87,7 +87,10 @@ Creation of the container depends on its type. For some containers, such as the (columns) as was done above, while some others determine them otherwise. The definition of a property with [methodname]#addContainerProperty()# requires a unique property ID, type, and a default value. You can also give -[parameter]#null#. +[parameter]#null#. If the container of a component is replaced and the new container +contains a different set of columns, such as a property with the same ID but a +different data type, the component should be reinitialized. For a table or grid, +it means redefining their columns. Vaadin has a several built-in in-memory container implementations, such as [classname]#IndexedContainer# and [classname]#BeanItemContainer#, which are easy -- 2.39.5