From 99d6de546c74f0eed230ea8253dda6b85109d2e7 Mon Sep 17 00:00:00 2001 From: Markus Koivisto Date: Fri, 22 Jan 2016 14:55:18 +0200 Subject: Add documentation to master branch Change-Id: I2504bb10f1ae73ec0cbc08b7ba5a88925caa1674 --- documentation/gwt/gwt-server-side.asciidoc | 38 ++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create 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 new file mode 100644 index 0000000000..1139b78a39 --- /dev/null +++ b/documentation/gwt/gwt-server-side.asciidoc @@ -0,0 +1,38 @@ +--- +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