All Downloads are FREE. Search and download functionalities are using the official Maven repository.

adin-client.7.1.0.source-code.release-notes.html Maven / Gradle / Ivy

Go to download

Vaadin is a web application framework for Rich Internet Applications (RIA). Vaadin enables easy development and maintenance of fast and secure rich web applications with a stunning look and feel and a wide browser support. It features a server-side architecture with the majority of the logic running on the server. Ajax technology is used at the browser-side to ensure a rich and interactive user experience.

There is a newer version: 8.27.1
Show newest version




Vaadin Framework 7.1.0







    
    

    

Version 7.1.0 built on 2013-06-26.

Release Notes for Vaadin Framework 7.1.0

Overview of Vaadin 7.1.0 Release

Vaadin 7.1.0 is a feature release that includes a number of enhancements as well as important bug fixes, as listed in the change log below. You can also view the list of the closed issues at the Vaadin developer's site.

Enhancements in Vaadin 7.1

The 7.1 includes many major and minor enhancements. Below is a list of the most notable changes:

  • Server push (Use the @Push annotation to enable push for a UI)
  • Server polling using UI.setPollInterval()
  • Enhanced debug window
  • Internet Explorer 10 support including pointer events
  • Sass compiler improvements: arithmetics, @content
  • Dynamic CSS injection
  • Support for SCSS/CSS files in all add-ons (Use Vaadin-Stylesheet in the manifest)
  • Calendar is included in the core framework
  • ProgressBar provides progress indication without polling (separated from ProgressIndicator)
  • Tooltip and loading indicator delays configurable on server side
  • The range of a DateField can be limited
  • Window has maximize/restore controls
  • UI and VaadinSession provide access() to access the UI and session while holding the needed lock
  • A new @VaadinServletConfiguration annotation for configuring servlet parameters
  • WAI-ARIA support for form fields, Button, and Tree
  • The behavior of Property.toString() can be toggled using the legacyPropertyToString init parameter
  • Default alignment can be set for layout components
  • FieldGroup supports SQL date fields and date field creation
  • Converter.convertToModel/convertFromModel now gets an additional parameter describing the target type
  • The browser page can be reloaded programmatically using Page.reload()
  • The VaadinServlet/VaadinPortlet and VaadinService classes have been refactored
  • Several locking related fixes
  • Client compiler dependencies are packaged as a separate jar
  • DefaultWidgetSet is even more optimized (using compiler parameter -XenableClosureCompiler)
  • Java assert statements have been added to critical code sections. Start JVM with -ea to use.
  • StateChangeEvent.isInitialState() indicates if event is the first for a connector
  • ClientConnector.isAttached() indicates if connector is attached
  • Container.Filterable now contains a getContainerFilters() method
  • TableQuery now supports schemas and catalogs

Tools have been updated for Vaadin @vaadin-minor@ with the following changes:

  • Maven
    • Theme compilation support using vaadin:update-theme and vaadin:compile-theme
  • Eclipse
    • Theme compilation support using the provided button
    • New projects are by default generated using Servlet 3.0 API
    • Additional GWT compiler parameters can be specified

For enchancements introduced in Vaadin 7, see the Release Notes for Vaadin 7.0.0.

Limitations

  • It is currently not possible to specify font-size as em or %, or layout component sizes with em (#10634)
  • Push is currently not supported in portals (See #11493)
  • HTTP session can not be invalidated while using push (#11721)
  • Cookies are not available while using push (#11808)
  • Not all proxies are compatible with websockets. If you are using push with an incompatible proxy you might have to force the transport mode to streaming. Some proxies have problems with streaming also - you need to ensure that the proxy does not buffer responses for HTTP streaming to work.

ChangeLog

This release includes the following closed issues:

  • #4513: Varargs could be utilized more in Vaadin API
  • #5615: Allow logging of debug messages on client side
  • #6207: PopupDateField always uses English names for day of week
  • #7997: Remove customized Smartsprites library
  • #8759: Performance Improvement for setting and removing styles
  • #9823: vaadin-all-7*.zip contains portal-service-6.0.2.jar
  • #9851: Package rebased or modified client-compiler dependencies as vaadin-client-compiler-deps
  • #9913: ProgressIndicator does not work properly with primary stylenames
  • #9934: Enable using images with @StyleSheet
  • #9959: Update smartsprites to avoid google-collections dependency
  • #10055: Page.addBrowserWindowResizeListener is not working
  • #10217: Merge #10189 fix to v7 branches
  • #10291: Support sass themes in Maven
  • #10477: Add StateChangeEvent.isInitialState to indicate if it is the first state change or an update
  • #10795: vaadin:clean does not remove the unit cache directory
  • #10875: Smartsprites should not depend on junit
  • #11026: TabSheet adds extra child nodes to the DOM
  • #11048: Drag & drop not ported to Calendar 2.0.0
  • #11158: Converter JavaDoc mentions PRESENTER and MODEL in the wrong order
  • #11168: Provide isIOS and isAndroid in WebBrowser class
  • #11224: SQLContainer and java.sql.Date fields
  • #11275: Javascript files not transferred properly: "Resource interpreted as Document but transferred with MIME type application/javascript"
  • #11279: Support for REM units
  • #11289: GWT RPC leak in IE9
  • #11378: The locale system is broken
  • #11442: Warning: widgetset version 7.x does not seem to match theme version
  • #11476: Focus after selection from context menu
  • #11485: Fix/unify server push error handling
  • #11509: Restoring a sub window should restore it to its previous position, not server position
  • #11510: Window looks broken when made too small
  • #11533: Missing vaadin-client-compiler makes it difficult to use ConnectorBundleLoaderFactory
  • #11536: Push breaks analyzeLayouts (and more)
  • #11621: Use release profile to enable compiling application archetype directly after checkout
  • #11642: Push using streaming is not reliable using Opera
  • #11667: Styles.add(Resource) adds the same resource multiple times
  • #11673: Improve error message if push js has not been loaded
  • #11688: UItest war cannot be deployed on JBoss 5/6
  • #11691: com.vaadin.push OSGi
  • #11692: Communication error: (SyntaxError) : Unexpected token ILLEGAL
  • #11708: Scoll position incorrect in Table with validator in immediate mode
  • #11722: Navigator creates instances of all views while finding the view with the longest name
  • #11726: Update migration guide with 7.1 related changes
  • #11734: Maximize button position is wrong in Runo dialog style
  • #11737: A window which has been maximized can't be restore through server side API
  • #11741: RichTextArea race condition.
  • #11752: ClickingWhilePopupOpen fails
  • #11759: Long delay before streaming channel is opened
  • #11764: Use the same UI template in Maven as in Eclipse
  • #11765: Remove slf4j dependency
  • #11769: Changelog contains triples quotation marks
  • #11771: vaadin-archetype-application should create and use a theme
  • #11773: Vaadin Maven plugin should not add vaadin-client-compiler on theme update classpath
  • #11777: Bean property "parent" has inconsistent getter/setter property types in AbstractComponent.java
  • #11779: Portlet detection code causes LinkageError
  • #11782: Sass theme compilation does not work if path contains spaces
  • #11785: Form field and layout Aria corrections
  • #11796: LayoutTesterApplication broken due to tests being run in different order
  • #11799: Tooltip/ErrorMessage output for assistive devices
  • #11805: AriaHelper.setVisibleForAssistiveDevicesOnly not working for arbitrary elements
  • #11807: Upgrade to Atmosphere 1.0.13 to fix memory leak with Tomcat native comet
  • #11809: Reload in browser leads to NPE in AtmospherePushConnection
  • #11831: Server connection does not recover when push is enabled
  • #11842: Client-to-server message splitting should count bytes, not characters
  • #11850: Initial rendering is always delayed by 300ms
  • #11861: Update to Atmosphere 1.0.13
  • #11863: Explicitly defined converters should not be overridden if they can possibly handle the conversion
  • #11865: Show tooltip on focus for DataField for AT
  • #11866: Add ARIA presentation role to FormLayout
  • #11867: Client-side push config should be customizable on the server side
  • #11869: Allow to close a context menu with ESC key
  • #11870: Document that server push does not work with an Apache/mod_jk load balancer
  • #11872: Remove workarounds for broken Timer.cancel in IE
  • #11873: vaadin-shared depends on vaadin-server after #10055
  • #11879: Update JDT dependency
  • #11890: Disable Atmosphere 1.0.13 update check
  • #11891: Log levels should be styled
  • #11895: Converter convert methods should get the requested target type as an additional parameter
  • #11897: Make access() enqueue the runnable if the session is locked
  • #11898: Initialization of PushRequestHandler fails - HTTP 503
  • #11900: Cleanup number converters
  • #11901: Remove UI.runSafely and VaadinSession.runSafely
  • #11909: SASS compiler does not support nested imports
  • #11914: Update CurrentInstance API and documentation to move focus away from ThreadLocal
  • #11922: Verify that streaming reconnect works
  • #11923: Provide push opportunity for updating ProgressIndicator on the client.
  • #11925: Split ProgressIndicator widget into ProgressBar and deprecate ProgressIndicator
  • #11928: Add ComponentConnector.isAttached()
  • #11934: Streaming does not work on iPhone/iPad
  • #11937: Resize for debug window does not work as expected
  • #11940: DateField range limitation does not update styles on subsequent modifications after first call
  • #11950: Add profiler section to the debug window
  • #11954: Vaadin still compiles a IE6/IE7 permutation
  • #11955: SSE transport does not work
  • #11956: Define XML formatting standard for the project and reformat existing files
  • #11960: Make it possible to show errors from the converter to the user
  • #11961: Throw exception if service has not ben initialized
  • #11963: Excessive logging from toString() in JUnit tests
  • #11964: Move VaadinSession.runPendingAccessTasks to VaadinService
  • #11965: Move ApplicationConnection.setOverlayContainerLabel to VOverlay
  • #11966: Add transport to @Push
  • #11968: Chrome/firefox only: opening mailto results in orange spinner when streaming enabled
  • #11970: Add @VaadinServletConfiguration
  • #11980: script error in vaadinpush.js shown in ie
  • #11985: Maven update and compile theme should be bound to appropriate phases in archetype
  • #11991: Document that push only works with VaadinServlet in 7.1
  • #11993: Release notes for 7.1.0
  • #11996: Allow using element resize listeners from javascript connectors
  • #12001: Server-side push connection is not closed when using streaming
  • #12005: Button caption should not be selectable (merge)
  • #12011: Components get wrong size in GridLayout after clearing ComponentError
  • #12014: Upload keeps polling forever if upload finishes quickly and push is enabled
  • #12015: 7.1.0 beta Debug console crash on IE9
  • #12017: Changing the push mode sometimes expires the session
  • #12019: Add an info section to the debug window
  • #12024: Widget archetype should not use artifactId as a Java field
  • #12031: Print warning if in production mode and theme compilation is required
  • #12033: Use .vaadin in the version of our atmosphere package
  • #12039: @WebServlet without @VaadinServletConfiguration or UI parameter should try to use enclosing UI
  • #12040: TeamCity no longer reports all failing tests
  • #12050: Entering pipe in a textbox and submitting returns a json error
  • #12053: Update widgetset template (Vaadin)
  • #12054: Update widgetset template (Maven archetypes)
  • #12056: Portlet action requests cause ClassCastException
  • #12058: DebugWindow small but critical fixes
  • #12062: Combobox Field caption does not get enabled when in a FormLayout
  • #12069: Upgrade to Smartsprites 0.2.10
  • #12073: Push in IE only recovers from the first disconnection
  • #12075: Test using Glassfish 4 and add support for it
  • #12077: Required indicator not shown for TextField (when placed in GridLayout)
  • #12080: Add support for pointer events in IE 10
  • #12081: Maven vaadin:clean should be bound to clean phase in application archetype
  • #12094: Set pushmode/transport via GET parameter in AbstractTestUI
  • #12097: NPE in runPendingAccessTasks
  • #12101: Push for Android 4.1.2 don't work
  • #12128: Loading indicator not shown while loading an application

The full list of the closed issues can also be found at dev.vaadin.com .

Vaadin Installation

Vaadin is a Java framework for building modern web applications that look great, perform well and make you and your users happy. Vaadin is available under the Apache License, Version 2.0 (see the license.html in the Vaadin ZIP or JAR package).

The easiest ways to install Vaadin are:

  • If using Maven, define it as a dependency or use any of the available archetypes (only vaadin-application is available for Vaadin 7 at the time of this release) to create a new project
  • If using Eclipse, use the Vaadin Plugin for Eclipse, which automatically downloads the Vaadin libraries. To use this prerelease version, the plugin should be installed from the experimental update site (http://vaadin.com/eclipse/experimental).

It is also available as a ZIP package downloadable from Vaadin Download page.

Package Contents

Inside the ZIP installation package you will find:

  • Separate server-side (vaadin-server) and client-side (vaadin-client, vaadin-client-compiler) development libraries
  • Precompiled widget set (vaadin-client-compiled) for server-side development
  • Shared library (vaadin-shared) for both server- and client-side libraries
  • Built-in themes (vaadin-themes) and the theme compiler (vaadin-theme-compiler)
  • Dependency libraries provided under the lib/ folder

See the README.TXT in the installation package for detailed information about the package contents. Book of Vaadin (for Vaadin 7) gives more detailed instructions.

For server-side development, copy the vaadin-server , vaadin-client-compiled , vaadin-shared , vaadin-theme-compiler , and vaadin-themes from the main folder and the dependencies from the lib folder to the WEB-INF/lib folder of your Vaadin project. (The vaadin-client-compiled is necessary if you do not wish to compile the widget set by your own, which you need to do if you use almost any add-on components.)

For pure client-side development, you only need the vaadin-client and vaadin-client-compiler JARs, which should be put to a non-deployed project library folder, such as lib . You also need them if you compile the widget set for any reason, such as using Vaadin add-ons, or create new server-side components integrated with client-side widgets.

Migrating from Vaadin 6

All Vaadin 6 applications need some changes when migrating to Vaadin 7. The most obvious changes are in the application/window API and require extending either UI or UI.LegacyApplication instead of Application. A detailed list of migration changes are given in the Vaadin 7 Migration Guide.

Any custom client-side widgets need to be ported to use the new client-server communication API, or the Vaadin 6 compatibility API.

Vaadin 6 add-ons (ones that contain widgets) do not work in Vaadin 7 - please check the add-ons in Vaadin Directory for Vaadin 7 support.

Vaadin 7.1.0 Dependencies

When using Maven, Ivy, Gradle, or other dependency management system, all Vaadin dependencies are downloaded automatically. This is also the case when using the Vaadin Plugin for Eclipse.

The Vaadin ZIP installation package includes the dependencies in the lib subfolder. These need to be copied to the WEB-INF/lib folder of the web application that uses Vaadin.

The dependencies are listed in the Licensing description. Some are explicit dependencies packaged and distributed as separate JARs, while some are included inside other libraries.

Bean Validation

If you use the bean validation feature in Vaadin 7, you need a Bean Validation API implementation. You need to install the implementation JAR in the WEB-INF/lib directory of the web application that uses validation.

Upgrading to Vaadin 7.1

Upgrading the Eclipse Plugin

Vaadin 7 requires that you use a compatible version of the Vaadin Plugin for Eclipse. The stable version of the plugin is available from the http://vaadin.com/eclipse update site. Please see the section about updating the plugin in the Book of Vaadin and the installation instructions at the download site for more details.

You can also use the experimental Vaadin Plugin for Eclipse. Its update site is http://vaadin.com/eclipse/experimental .

General Upgrading Instructions

When upgrading from an earlier Vaadin version, you must:

  • Recompile your classes using the new Vaadin version. Binary compatibility is only guaranteed for maintenance releases of Vaadin.
  • Recompile any add-ons you have created using the new Vaadin
  • Unless using the precompiled widget set, recompile your widget set using the new Vaadin version

Remember also to refresh the project in your IDE to ensure that the new version of everything is in use.

By using the " ?debug " URL parameter, you can verify that the version of the servlet, the theme, and the widget set all match.

Eclipse users should always check if there is a new version of the Eclipse Plug-in available. The Eclipse Plug-in can be used to update the Vaadin version in the project (Project properties » Vaadin).

Maven users should update the Vaadin dependency version in the pom.xml unless it is defined as LATEST . You must also ensure that the GWT dependency uses the correct version and recompile your project and your widget set.

Liferay and other portal users must install the Vaadin libraries in ROOT/WEB-INF/lib/ in the portal (and remove a possibly obsolete older vaadin.jar). Additionally, the contents of the vaadin-client-compiled and vaadin-themes must be extracted to the ROOT/html/VAADIN directory in the Liferay installation. If your portal uses custom widgets, install the latest version of Vaadin Control Panel for Liferay for easy widget set compilation - when it is available - the add-on is not compatible with Vaadin 7.1.0 at the time of this Vaadin release.

Notes and Limitations for Google App Engine

The following instructions and limitations apply when you run a Vaadin application under the Google App Engine.

  • Applications must use GAEVaadinServlet instead of VaadinServlet in web.xml .

  • Session support must be enabled in appengine-web.xml :

        <sessions-enabled>true</sessions-enabled>
  • Avoid using the session for storage, usual App Engine limitations apply (no synchronization, that is, unreliable).

  • Vaadin uses memcache for mutex, the key is of the form _vmutex<sessionid> .

  • The Vaadin VaadinSession class is serialized separately into memcache and datastore; the memcache key is _vac<sessionid> and the datastore entity kind is _vac with identifiers of the type _vac<sessionid> .

  • DO NOT update application state when serving an ConnectorResource (such as ClassResource.getStream()).

  • The application remains locked during uploads - a progress bar is not possible

For other known problems, see open tickets at developer site dev.vaadin.com.

Supported Technologies

Vaadin 7 is compatible with Java 6 and newer. Vaadin 7 is especially supported on the following operating systems:

  • Windows
  • Linux
  • Mac OS X

Vaadin 7 requires Java Servlet API 2.4 but also supports later versions and should work with any Java application server that conforms to the standard. The following application servers are supported:

  • Apache Tomcat 5-7
  • Apache TomEE 1
  • Oracle WebLogic Server 10.3-12
  • IBM WebSphere Application Server 7-8
  • JBoss Application Server 4-7
  • Jetty 5-9
  • Glassfish 2-4

Vaadin 7 supports the JSR-286 Portlet specification and all portals that implement the specification should work. The following portals are supported:

  • Liferay Portal 5.2-6
  • GateIn Portal 3
  • eXo Platform 3

Vaadin also supports Google App Engine.

Vaadin supports the following desktop browsers:

  • Mozilla Firefox 18-21
  • Mozilla Firefox 17 ESR
  • Internet Explorer 8-10
  • Safari 6
  • Opera 12
  • Google Chrome 23-27

Additionally, Vaadin supports the built-in browsers in the following mobile operating systems:

  • iOS 5-6
  • Android 2.3-4

Vaadin SQL Container supports the following databases:

  • HSQLDB
  • MySQL
  • MSSQL
  • Oracle
  • PostgreSQL

Vaadin on the Web





© 2015 - 2024 Weber Informatics LLC | Privacy Policy