* Update clientsideapp-entrypoint.asciidoc Adding missing ```[source, java]```

5 years ago · febddda057
--- a/documentation/clientsideapp/clientsideapp-entrypoint.asciidoc
+++ b/documentation/clientsideapp/clientsideapp-entrypoint.asciidoc
 Consider the following application:
 [source, java]
 ----
 package com.example.myapp.client;
 Module Descriptor">>. The descriptor is an XML file with suffix
 [filename]#.gwt.xml#.
 [source, xml]
 ----
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE module PUBLIC
--- a/documentation/clientsideapp/clientsideapp-loading.asciidoc
+++ b/documentation/clientsideapp/clientsideapp-loading.asciidoc
 page__ by including it with a [literal]#++<script>++# tag, for example as
 follows:
 [source, html] 
 ----
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
--- a/documentation/clientsideapp/clientsideapp-overview.asciidoc
+++ b/documentation/clientsideapp/clientsideapp-overview.asciidoc
 Consider the following client-side application:
 [source, java]
 ----
 public class HelloWorld implements EntryPoint {
    @Override
--- a/documentation/clientsidewidgets/clientsidewidgets-grid.asciidoc
+++ b/documentation/clientsidewidgets/clientsidewidgets-grid.asciidoc
 For example, [classname]#TextRenderer# is implemented simply as follows:
 [source, java] 
 ----
 public class TextRenderer implements Renderer<String> {
    @Override
 [classname]#ClickableRenderer# with the data type accepted by the renderer. The
 data type also must be given for the superclass constructor.
 [source, java] 
 ----
 public class TextRenderer extends AbstractRenderer<String> {
    public TextRenderer() {
 The client-side and server-side renderer need to be connected with a connector
 extending from [classname]#AbstractRendererConnector#.
 [source, java] 
 ----
@Connect(com.vaadin.ui.renderer.TextRenderer.class)
 public class TextRendererConnector
--- a/documentation/clientsidewidgets/clientsidewidgets-vaadin.asciidoc
+++ b/documentation/clientsidewidgets/clientsidewidgets-vaadin.asciidoc
 foremost intended for integration with the server-side components, but some may
 prove useful for client-side applications as well.
 [source, java] 
 ----
 public class MyEntryPoint implements EntryPoint {
    @Override
--- a/documentation/gwt/gwt-connector.asciidoc
+++ b/documentation/gwt/gwt-connector.asciidoc
 from user interaction and changes received from the server. A connector also has
 a number of routine infrastructure methods which need to be implemented.
 [source,java]
 ----
@Connect(MyComponent.class)
 public class MyComponentConnector
--- a/documentation/gwt/gwt-extension.asciidoc
+++ b/documentation/gwt/gwt-extension.asciidoc
 For example, let us have a trivial example with an extension that takes no
 special parameters, and illustrates the three alternative APIs:
 [source,java]
 ----
 public class CapsLockWarning extends AbstractExtension {
    // You could pass it in the constructor
 The extension could then be added to a component as follows:
 [source,java]
 ----
 PasswordField password = new PasswordField("Give it");
 listens for changes in Caps Lock state and displays a floating warning element
 over the extended component if the Caps Lock is on.
 [source,java]
 ----
@Connect(CapsLockWarning.class)
 public class CapsLockWarningConnector
--- a/documentation/gwt/gwt-rpc.asciidoc
+++ b/documentation/gwt/gwt-rpc.asciidoc
 For example:
 [source,java]
 ----
 public interface MyComponentServerRpc extends ServerRpc {
    public void clicked(String buttonName);
 [methodname]#RpcProxy.create()#. This is usually done transparently by using [methodname]#getRpcProxy()#. After that, you can make calls through the
 server RPC interface that you defined, for example as follows:
 [source,java]
 ----
@Connect(MyComponent.class)
 public class MyComponentConnector
 interface. The call and its parameters are serialized and passed to the server
 in an RPC request transparently.
 [source,java]
 ----
 public class MyComponent extends AbstractComponent {
    private MyComponentServerRpc rpc =
--- a/documentation/gwt/gwt-server-side.asciidoc
+++ b/documentation/gwt/gwt-server-side.asciidoc
 <<dummy/../../../framework/gwt/gwt-shared-state#gwt.shared-state,"Shared
 State">>.
 [source, java]
 ----
 public class MyComponent extends AbstractComponent {
    public MyComponent() {
--- a/documentation/gwt/gwt-shared-state.asciidoc
+++ b/documentation/gwt/gwt-shared-state.asciidoc
 [classname]#AbstractComponentState#. The member variables should normally be
 declared as public.
 [source, java]
 ----
 public class MyComponentState extends AbstractComponentState {
    public String text;
 For example, you could have the following definitions in the
 [filename]#.gwt.xml# descriptor:
 [source, xml]
 ----
    <source path="client" />
    <source path="shared" />
 implementation with one that returns the shared state object cast to the proper
 type, as follows:
 [source, java]
 ----
@Override
 public MyComponentState getState() {
 You can then use the [methodname]#getState()# to access the shared state object
 with the proper type.
 [source, java]
 ----
 public MyComponent() {
    getState().setText("This is the initial state");
 The access should be read-only. It is required that you override the base
 implementation with one that returns the proper shared state type, as follows:
 [source, java]
 ----
@Override
 public MyComponentState getState() {
 method in the connector is called. You should always call the superclass
 method before anything else to handle changes to common component properties.
 [source, java]
 ----
@Override
 public void onStateChanged(StateChangeEvent stateChangeEvent) {
 We can replace the [methodname]#onStateChange()# method in the earlier connector
 example with the following:
 [source, java]
 ----
@OnStateChange("text")
 void updateText() {
 property of the same name and type, by calling the respective setter for the
 property in the widget.
 [source, java]
 ----
 public class MyComponentState extends AbstractComponentState {
    @DelegateToWidget
 If you want to delegate a shared state property to a widget property of another
 name, you can give the property name as a string parameter for the annotation.
 [source, java]
 ----
 public class MyComponentState extends AbstractComponentState {
    @DelegateToWidget("description")
 widgets. References to components can be made by referring to their connectors
 (all server-side components implement the [interfacename]#Connector# interface).
 [source, java]
 ----
 public class MyComponentState extends AbstractComponentState {
    public Connector otherComponent;
 You could then access the component on the server-side as follows:
 [source, java]
 ----
 public class MyComponent {
    public void MyComponent(Component otherComponent) {
 Let us begin with the server-side API:
 [source, java]
 ----
 public class MyComponent extends AbstractComponent {
    ...
 On the client-side, you can then get the URL of the resource with
 [methodname]#getResourceUrl()#.
 [source, java]
 ----
@Override
 public void onStateChanged(StateChangeEvent stateChangeEvent) {
 The widget could then use the URL, for example, as follows:
 [source, java]
 ----
 public class MyWidget extends Label {
    ...
--- a/documentation/gwt/gwt-styling.asciidoc
+++ b/documentation/gwt/gwt-styling.asciidoc
 For example, you could style a composite widget with an overall style and with
 separate styles for the sub-widgets as follows:
 [source, java]
 ----
 public class MyPickerWidget extends ComplexPanel {
    public static final String CLASSNAME = "mypicker";