blocks|key|1709226|text|客户端应用程序只不过是浏览器下载和执行的一个JavaScript应用程序。这个JavaScript应用程序是用Java编写的，由内置到IDE使用的瓦丁库中的Google工具包(GWT)编译器编译到JavaScript中。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1709227|此应用程序可能与在服务器上运行的Java应用程序交互，也可能不与之交互。如果没有，那么它就是一个客户端应用程序。如果是这样的话，它就是服务器端应用程序.|1709228|希望能帮上忙。|1709229|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/JavaScript|1|http://en.wikipedia.org/wiki/Java_(programming_language)|2|http://en.wikipedia.org/wiki/Integrated_development_environment|3|http://en.wikipedia.org/wiki/Vaadin|4|http://en.wikipedia.org/wiki/Google_Web_Toolkit^0|M|A|0|1J|4|1|1V|3|2|21|2|3|26|E|4|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]|$A|11|B|12|1|13]|$A|14|B|15|1|16]|$A|17|B|18|1|19]|$A|1A|B|1B|1|1C]]|C|$]]|$1|D|3|E|5|6|7|1D|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1E|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]|T|$5|K|L|M|C|$N|U]]|V|$5|K|L|M|C|$N|W]]]]

<p>The client-side application is nothing but a <a href="http://en.wikipedia.org/wiki/JavaScript" rel="nofollow">JavaScript</a> application that the browser downloads &amp; executes. This JavaScript application is written in <a href="http://en.wikipedia.org/wiki/Java_(programming_language)" rel="nofollow">Java</a> and compiled to JavaScript by the <a href="http://en.wikipedia.org/wiki/Google_Web_Toolkit" rel="nofollow">Google Web Toolkit (GWT)</a> compiler that is built into the <a href="http://en.wikipedia.org/wiki/Vaadin" rel="nofollow">Vaadin</a> libraries used by your <a href="http://en.wikipedia.org/wiki/Integrated_development_environment" rel="nofollow">IDE</a>.</p>

<p>This application may or may not interact with a Java application that is running on the server. If it does not, then its a Client-side application. If it does, its a Server-side application.</p>

<p>I hope it helps.</p>


blocks|key|692673|text|其他答案并不是精确或彻底的。所以我会在这个问题上加上我自己的看法。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|692674|客户端|692675|Vaadin的主要观点是，作为一个程序员，我们认为这类似于构建桌面应用程序。我们并不真正担心应用程序的客户端和服务器端，我们从打开窗口(+用户界面实例)、表单(布局)和字段&按钮(组件)的角度来考虑。|style|BOLD|692676|纯Java|692677|我们使用纯Java编写所有这些UI、布局和组件对象。底层的瓦丁框架利用Google工具包(GWT)将您的Java代码的用户界面部分转换为JavaScript。该JavaScript代码在运行时透明地传递到web浏览器。因此，JavaScript用于在屏幕上绘制一个按钮和字段，并用于检测用户何时单击该按钮或该字段中的类型。|692678|应用程序生活在服务器上|692679|同时，在服务器端您的业务逻辑仍然是纯Java的。用户单击一个按钮会导致您的一些Java代码在服务器上执行。与字段中的键入相同；类型化文本将自动转发到服务器上的Java代码。从我们这个Java+Vaadin应用程序开发人员的角度来看，整个应用程序似乎都运行在纯Java中。Vaadin框架会自动处理以下内容的来回通信：|692680|⇆/客户端Java/服务器端。|blockquote|692681|所以，用Vaadin做一个网络应用完全不像做一个web应用程序。在大多数情况下，Vaadin开发人员不需要关注HTTP、HTML、CSS、DOM、JavaScript/ECMAScript、Servlet/JSP等等。所有这些网络技术实际上都在使用Vaadin应用程序，但是Vaadin以透明、几乎神奇的方式为我们解决了所有这些问题。我们只使用纯Java编写，以便在Vaadin中构建非常好的“桌面”-style应用程序。|692682|您的所有业务逻辑、Java业务对象、SQL和数据库连接等都只存在于服务器上。web浏览器只包含足够的数据和JavaScript，以显示当前预期的用户界面。我认为这是旧X窗口系统的现代转世。(忽略最后一条评论，你还太年轻，记不起MTV播放音乐视频的时间。)|692683|在web浏览器上，我们只执行JavaScript。我们的用户不需要在他们的计算机上安装Java。不涉及Java小程序。|692684|Vaadin不是“又一个Web应用框架”|692685|这听起来很难相信，也可能很难理解。这是因为Vaadin的架构非常不同。Vaadin肯定不是“又一个HTML模板的web应用框架”。Vaadin的方法几乎是独一无二的；我所知道的唯一一个类似架构的web应用程序开发框架是Xojo+Web版。|692686|在学习Vaadin时忽略“客户端”谈话|692687|Vaadin团队一直致力于允许Vaadin应用程序脱机工作，而不是连接到Java服务器。但这是尖端的研发工作，而不是Vaadin的主要目的或用例。当你读到“客户端Vaadin”时，可能就是在这种背景下。|692688|另一个可能引发您的问题的上下文是“Vaadin”中的客户端应用程序章节。基本上，这是关于Vaadin的最新版本，增加了对高级开发人员的支持，这些开发人员希望在客户端的web浏览器上更好地控制JavaScript中发生的事情。但我认为，最初吸引人们关注Vaadin的主要目的是分散注意力:不关心客户端浏览器上的JavaScript。所以我建议在学习Vaadin的时候跳过这一章。|692689|或者上下文可能指使用GWT在web浏览器上呈现基于JavaScript的用户界面表示。在学习Vaadin时，您可以忽略这个上下文，因为它只适用于将您自己的用户界面小部件构建为附加的到Vaadin的内置小部件库存。|692690|Vaadin+API+doc中列出的许多类都是在学习Vaadin时应该忽略的与GWT相关的客户端类。对于许多工具来说，浏览API文档是学习的好方法。但对Vaadin来说不是这样。在日常工作中，我们只使用了一小部分列出的类.我建议把重点放在瓦丁书、演示站点、教程、论坛和StackOverflow上。|692691|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/25869727/642706|1|https://vaadin.com/api/com/vaadin/ui/UI.html|2|https://vaadin.com/api/com/vaadin/ui/Layout.html|3|https://vaadin.com/api/com/vaadin/ui/Component.html|4|http://en.wikipedia.org/wiki/Vaadin|5|http://en.wikipedia.org/wiki/Google_Web_Toolkit|6|http://en.wikipedia.org/wiki/X_Window_System|7|http://www.xojo.com/|8|https://vaadin.com/book/-/page/clientsideapp.html|9|https://vaadin.com/directory|10|https://vaadin.com/api/|11|https://vaadin.com/book|12|https://vaadin.com/demo|13|https://vaadin.com/tutorial|14|https://vaadin.com/forum^0|0|4|0|0|0|12|1Q|1X|4|1|28|2|2|2I|2|3|0|0|5|0|0|4H|T|2|4|Z|E|5|0|0|B|0|0|4E|0|0|F|0|0|5V|0|0|3J|2B|5|6|0|0|1N|0|0|K|0|0|3B|31|9|7|0|0|J|0|0|2T|0|0|58|Q|7|8|0|0|2Y|2F|3|9|0|0|45|0|E|A|3B|3|B|3F|4|C|3K|2|D|3N|2|E|0^^$0|@$1|2|3|4|5|6|7|2E|8|@]|9|@$A|2F|B|2G|1|2H]]|C|$]]|$1|D|3|E|5|6|7|2I|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|2J|8|@$A|2K|B|2L|H|I]]|9|@$A|2M|B|2N|1|2O]|$A|2P|B|2Q|1|2R]|$A|2S|B|2T|1|2U]]|C|$]]|$1|J|3|K|5|6|7|2V|8|@$A|2W|B|2X|H|I]]|9|@]|C|$]]|$1|L|3|M|5|6|7|2Y|8|@$A|2Z|B|30|H|I]]|9|@$A|31|B|32|1|33]|$A|34|B|35|1|36]]|C|$]]|$1|N|3|O|5|6|7|37|8|@$A|38|B|39|H|I]]|9|@]|C|$]]|$1|P|3|Q|5|6|7|3A|8|@$A|3B|B|3C|H|I]]|9|@]|C|$]]|$1|R|3|S|5|T|7|3D|8|@$A|3E|B|3F|H|I]]|9|@]|C|$]]|$1|U|3|V|5|6|7|3G|8|@$A|3H|B|3I|H|I]]|9|@]|C|$]]|$1|W|3|X|5|6|7|3J|8|@$A|3K|B|3L|H|I]]|9|@$A|3M|B|3N|1|3O]]|C|$]]|$1|Y|3|Z|5|6|7|3P|8|@$A|3Q|B|3R|H|I]]|9|@]|C|$]]|$1|10|3|11|5|6|7|3S|8|@$A|3T|B|3U|H|I]]|9|@]|C|$]]|$1|12|3|13|5|6|7|3V|8|@$A|3W|B|3X|H|I]]|9|@$A|3Y|B|3Z|1|40]]|C|$]]|$1|14|3|15|5|6|7|41|8|@$A|42|B|43|H|I]]|9|@]|C|$]]|$1|16|3|17|5|6|7|44|8|@$A|45|B|46|H|I]]|9|@]|C|$]]|$1|18|3|19|5|6|7|47|8|@$A|48|B|49|H|I]]|9|@$A|4A|B|4B|1|4C]]|C|$]]|$1|1A|3|1B|5|6|7|4D|8|@$A|4E|B|4F|H|I]]|9|@$A|4G|B|4H|1|4I]]|C|$]]|$1|1C|3|1D|5|6|7|4J|8|@$A|4K|B|4L|H|I]]|9|@$A|4M|B|4N|1|4O]|$A|4P|B|4Q|1|4R]|$A|4S|B|4T|1|4U]|$A|4V|B|4W|1|4X]|$A|4Y|B|4Z|1|50]]|C|$]]|$1|1E|3|-4|5|6|7|51|8|@]|9|@]|C|$]]]|1F|$1G|$5|1H|1I|1J|C|$1K|1L]]|1M|$5|1H|1I|1J|C|$1K|1N]]|1O|$5|1H|1I|1J|C|$1K|1P]]|1Q|$5|1H|1I|1J|C|$1K|1R]]|1S|$5|1H|1I|1J|C|$1K|1T]]|1U|$5|1H|1I|1J|C|$1K|1V]]|1W|$5|1H|1I|1J|C|$1K|1X]]|1Y|$5|1H|1I|1J|C|$1K|1Z]]|20|$5|1H|1I|1J|C|$1K|21]]|22|$5|1H|1I|1J|C|$1K|23]]|24|$5|1H|1I|1J|C|$1K|25]]|26|$5|1H|1I|1J|C|$1K|27]]|28|$5|1H|1I|1J|C|$1K|29]]|2A|$5|1H|1I|1J|C|$1K|2B]]|2C|$5|1H|1I|1J|C|$1K|2D]]]]

<p>The <a href="https://stackoverflow.com/a/25869727/642706">other answer</a> is not exactly accurate or thorough. So I'll add my own take on the subject.</p>

<h1>Client-Side, Schmlient-Side</h1>

<p>The main point of Vaadin is that as a programmer we think in terms similar to building a desktop app. <strong>We do not really worry about client-side versus server-side of the app.</strong> We think in terms of a window being open (a <a href="https://vaadin.com/api/com/vaadin/ui/UI.html" rel="nofollow noreferrer">UI</a> instance), with forms (<a href="https://vaadin.com/api/com/vaadin/ui/Layout.html" rel="nofollow noreferrer">Layouts</a>) and fields &amp; buttons (<a href="https://vaadin.com/api/com/vaadin/ui/Component.html" rel="nofollow noreferrer">Components</a>).</p>

<h1>Pure Java</h1>

<p>We write all those UI, Layout, and Component objects using pure Java. The underlying <a href="http://en.wikipedia.org/wiki/Vaadin" rel="nofollow noreferrer">Vaadin</a> framework leverages the <a href="http://en.wikipedia.org/wiki/Google_Web_Toolkit" rel="nofollow noreferrer">Google Web Toolkit (GWT)</a> to convert the user-interface portions of your Java code into JavaScript. That JavaScript code is transparently delivered to the web browser at runtime. So JavaScript is used to draw a button and field on the screen and used to detect when the user clicks that button or types in that field. </p>

<h1>App Lives On The Server</h1>

<p>Meanwhile, your business logic remains in pure Java on the server side. The fact that the user clicked a button causes some of your Java code to execute on the server. Same with typing in the field; the typed text is automatically forwarded to your Java code on the server. From the perspective of us, the Java Vaadin app developer, the entire app seems to be running in pure Java. The Vaadin framework automatically handles this back-and-forth communication of:</p>

<blockquote>
  <p>[ JavaScript/client-side ⇆ Java/server-side ].</p>
</blockquote>

<p>So, doing a web app with Vaadin is not like doing a web app at all. For the most part, the Vaadin developer need not concern herself with HTTP, HTML, CSS, DOM, JavaScript/ECMAScript, Servlet/JSP, and such. All of those web technologies are indeed in play with a Vaadin app, but Vaadin handles all that for us transparently, almost magically. We write only in pure Java to build very nice "desktop"-style apps in Vaadin.</p>

<p>All your business logic, Java business objects, SQL and database connections, and such live only on the server. The web browser contains only enough data and JavaScript to show the currently intended user interface. I think of this as modern reincarnation of the old <a href="http://en.wikipedia.org/wiki/X_Window_System" rel="nofollow noreferrer">X Window System</a>. (Ignore that last comment is you are too young to remember when MTV played music videos.)</p>

<p>On the web browser, we execute only JavaScript. Our users need not install Java on their computer. No Java Applet involved.</p>

<h1>Vaadin Is <em>Not</em> "Yet Another Web App Framework"</h1>

<p>This may sound hard-to-believe or difficult to grasp. That is because the architecture of Vaadin is brilliantly different. Vaadin is certainly <em>not</em> "yet another HTML-templating web app framework". Vaadin is nearly unique in its approach; the only similarly architected web-app development framework I know of is <a href="http://www.xojo.com/" rel="nofollow noreferrer">Xojo Web Edition</a>.</p>

<h1>Ignore "client-side" Talk When Learning Vaadin</h1>

<p>The Vaadin team has been working on allowing a Vaadin app to work offline, not connected to the Java server. But this is bleeding-edge R&amp;D work, and not the main purpose or use case of Vaadin. When you read of "client-side Vaadin" it may be in that context. </p>

<p>Another context that may have prompted your Question is the <a href="https://vaadin.com/book/-/page/clientsideapp.html" rel="nofollow noreferrer">Client-Side Applications</a> chapter of the Book of Vaadin. Basically this about the newest versions of Vaadin adding support for advanced developers that want to take more control of what is happening in JavaScript on the client’s web browser. But I consider that a distraction from the main purpose that attracts people to Vaadin in the first place: <em>Not</em> caring about JavaScript on the client’s web browser. So I suggest skipping that chapter when learning Vaadin.</p>

<p>Or the context may refer to the use of GWT to render the JavaScript-based representation of your user-interface on the web browser. You can ignore this context when learning Vaadin as it only applies if building your own user-interface widgets to be <a href="https://vaadin.com/directory" rel="nofollow noreferrer">an add-on</a> to Vaadin’s built-in stock of widgets.</p>

<p>Many many of the classes listed in the <a href="https://vaadin.com/api/" rel="nofollow noreferrer">Vaadin API doc</a> are these GWT-related client-side classes that you should ignore while learning Vaadin. For many tools, browsing the API doc is a good way to learn. But for Vaadin, not the case. In day-to-day work, we use only a tiny fraction of the classes listed. I suggest instead focusing on the <a href="https://vaadin.com/book" rel="nofollow noreferrer">Book of Vaadin</a>, the <a href="https://vaadin.com/demo" rel="nofollow noreferrer">Demo site</a>, the <a href="https://vaadin.com/tutorial" rel="nofollow noreferrer">Tutorial</a>, the <a href="https://vaadin.com/forum" rel="nofollow noreferrer">Forums</a>, and StackOverflow.</p>


<p>I'm new to vaadin framework and was going through the Vaadin Book but was not to able understand the flow of client side Vaadin application. Would be very thankful if anyone explains the working of the Vaadin Client side application. As vaadin offers two development models i.e. Client side and Server Side.</p>


Vaadin Client Side Application Understanding

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我对vaadin框架很陌生，正在阅读Vaadin，但无法理解客户端Vaadin应用程序的流程。如果有人解释Vaadin客户端应用程序的工作，那将是非常感谢的。vaadin提供了两种开发模式，即客户端和服务器端。

问Vaadin客户端应用程序理解
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Vaadin客户端应用程序理解EN