Vaadin

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Vaadin
Vaadin-logo
Developer(s) Vaadin Ltd.
Stable release 6.7.4 / January 10, 2012; 17 days ago (2012-01-10)
Platform Java
Type Web Application Framework
License Apache License 2.0
Website http://vaadin.com/

Vaadin is an open source Web application framework for rich Internet applications. In contrast to JavaScript libraries and browser-plugin based solutions, it features a server-side architecture, which means that the majority of the logic runs on the servers. Ajax technology is used at the browser-side to ensure a rich and interactive user experience. On client-side Vaadin is built on top of and can be extended with Google Web Toolkit.

Contents

[edit] Features

One of the most prominent features of Vaadin Framework is the ability to use Java (using a Java EE platform) as the programming language, while creating content for the Web. The framework incorporates event-driven programming and widgets, which enables a programming model that is closer to GUI software development, than traditional Web development with HTML and JavaScript.

Vaadin Framework utilizes Google Web Toolkit for rendering the resulting Web page. While Google Web Toolkit operates only on client-side (i.e. a browser's JavaScript engine) – which could lead to trust issues – Vaadin adds server-side validation to all actions. This means that if the client data is tampered with, the server notices this and doesn't allow it.

Vaadin Framework's default component set can be extended with custom GWT widgets and themed with CSS.

From application developers point of view, Vaadin is just one JAR-file that can be included in any kind of Java Web project developed with standard Java tools. In addition, there are Eclipse and Netbeans plugins for easing the development of Vaadin applications as well as direct support of (and distribution through) Maven.

Vaadin applications can be deployed as Java Servlets to any Java server, including Google App Engine. Applications can also be deployed as Portlets to any Java portal, with deeper integration to Liferay Portal.

[edit] History

Development was first started as an adapter on top of the Millstone 3 open source Web framework released in year 2002. It introduced an Ajax based client communication and rendering engine. During 2006 this concept was then developed separately as a commercial product. As a consequence for this, a large part of Vaadin's server-side API is still compatible with Millstone's Swing-like APIs.

In early 2007 the product name was changed to IT Mill Toolkit and version 4 was released. It used a proprietary JavaScript Ajax-implementation for the client-side rendering, which made it rather complicated to implement new widgets. By the end of year 2007 the proprietary client-side implementation was abandoned and GWT was integrated on top of the server-side components. At the same time the product license was changed to open source Apache License 2.0. The first production ready release of IT Mill Toolkit 5 was made on March 4, 2009 after over one year beta period.

On September 11, 2008, it was publicly announced[1][2] that Michael Widenius, the main author of the original version of MySQL, invested in IT Mill, the developer of Vaadin. The size of the investment is undisclosed.

On May 20, 2009, IT Mill Toolkit changed its name to Vaadin Framework to attract more community. The name originates from the Finnish word for doe, more precisely put, a female reindeer. It can also be translated from Finnish as "I insist". In addition to name change, a pre-release of version 6 along with a community web-site was launched. Later, IT Mill Ltd, the company behind the open source Vaadin Framework, changed its name to Vaadin Ltd.

On March 30, 2010, Vaadin Directory was opened. Directory added a channel for easily distributing, for free or commercially, add-on components to the core Vaadin Framework. On launch date there were 95 add-ons already available for download.

On Feb 25, 2011, Vaadin Pro Account - a commercial support model was launched.

[edit] Competitors

Historically, Vaadin has been compared[by whom?] to Echo, ICEfaces and ZK - frameworks that use a similar server-side programming model. The server-side APIs are quite similar, providing both events and GUI components, but the client-side (i.e. web-browser) interaction differs in that Vaadin uses Java-programmed GWT widgets (ICEFaces uses JSF, ZK uses jQuery, and Echo has its own implementation). As of 2011 the most frequently compared frameworks include Adobe Flex, Google Web Toolkit, Apache Wicket and RichFaces.

For C++, the Wt toolkit offers similar capabilities.

[edit] See also

[edit] External links

[edit] References

Personal tools
Namespaces
Variants
Actions
Navigation
Interaction
Toolbox
Print/export
Languages