summaryrefslogtreecommitdiffstats
path: root/documentation/gwt/gwt-server-side.asciidoc
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/gwt/gwt-server-side.asciidoc')
-rw-r--r--documentation/gwt/gwt-server-side.asciidoc38
1 files changed, 0 insertions, 38 deletions
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
-<<dummy/../../../framework/gwt/gwt-shared-state#gwt.shared-state,"Shared
-State">>.
-
-
-----
-public class MyComponent extends AbstractComponent {
- public MyComponent() {
- getState().setText("This is MyComponent");
- }
-
- @Override
- protected MyComponentState getState() {
- return (MyComponentState) super.getState();
- }
-}
-----
-
-
-
-