From 2af72ba9636bec70046394c41744f89ce4572e35 Mon Sep 17 00:00:00 2001 From: Ilia Motornyi Date: Thu, 3 Dec 2015 14:59:05 +0000 Subject: Revert "Merge branch 'documentation'" This reverts commit f6874bde3d945c8b2d1b5c17ab50e2d0f1f8ff00. Change-Id: I67ee1c30ba3e3bcc3c43a1dd2e73a822791514bf --- documentation/gwt/gwt-server-side.asciidoc | 38 ------------------------------ 1 file changed, 38 deletions(-) delete mode 100644 documentation/gwt/gwt-server-side.asciidoc (limited to 'documentation/gwt/gwt-server-side.asciidoc') diff --git a/documentation/gwt/gwt-server-side.asciidoc b/documentation/gwt/gwt-server-side.asciidoc deleted file mode 100644 index 1139b78a39..0000000000 --- a/documentation/gwt/gwt-server-side.asciidoc +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Creating a Server-Side Component -order: 3 -layout: page ---- - -[[gwt.server-side]] -= Creating a Server-Side Component - -Typical server-side Vaadin applications use server-side components that are -rendered on the client-side using their counterpart widgets. A server-side -component must manage state synchronization between the widget on the -client-side, in addition to any server-side logic. - -[[gwt.server-side.basic]] -== Basic Server-Side Component - -The component state is usually managed by a __shared state__, described later in -<>. - - ----- -public class MyComponent extends AbstractComponent { - public MyComponent() { - getState().setText("This is MyComponent"); - } - - @Override - protected MyComponentState getState() { - return (MyComponentState) super.getState(); - } -} ----- - - - - -- cgit v1.2.3