1. News & Announcements

RE: Vaadin Add-ons Now Available With Maven

2010-08-31T05:09:54Z

Hi Adriaan,

and thanks for the feedback. Typically the source code is included inside the add-on jar file. Actually this is even a requirement for any add-ons with client-side code because of the required GWT widget set compilation.

- Teemu

RE: Vaadin Add-ons Now Available With Maven

2010-08-30T21:01:08Z

Great feature, speeds up the development process yet a bit more!

Unfortunately however, source code for some (all) addons seems to be missing from the maven repository. Is this being worked on?

Vaadin 6.4.3 available

2010-08-30T15:24:27Z

Vaadin 6.4.3 is a maintenance release in the 6.4 series. It includes a number of important bug fixes. See the list of closed issues in Vaadin Trac for a detailed change log. For other release information, see the Release Notes.

Get the installation package from the download site at http://vaadin.com/download. If you are using the Vaadin Plugin for Eclipse, upgrade the Vaadin version from the project preferences.

Problem fixes and enhancements planned for upcoming releases can be found from the Vaadin Roadmap in Vaadin Trac.

As always, when upgrading from an earlier version, you should recompile any custom widget sets and refresh your project in Eclipse. See the General Upgrade Notes for more details on upgrading.

Vaadin Add-ons Now Available With Maven

2010-08-27T13:45:08Z

Today we rolled out a new version of the Vaadin Directory. This update is mostly about fulfilling a common feature request we have heard from the community, downloading add-ons via Maven repository. We have setup our own Maven repository for Vaadin Add-ons and already deployed existing add-ons there with the exception of some add-ons that wouldn't make sense to use via Maven (tools etc). All future add-ons (and new versions of existing add-ons) will automatically be also available via the Maven repository.

How to use this new feature? It's simple, in the Directory we now have a Maven POM button right under the download button for each add-on that is available via Maven. By clicking this button you will be shown all the needed information (<repository> and <dependency>) for you to copy-paste into the pom.xml file of your Maven project. More defailed instructions here.

We would be happy to hear any feedback from you about this new feature. There might still be some rough edges and together we can smooth them out. Please post your comments, bug reports, ideas or any other feedback into this forum thread or use the feedback link on the Directory menu.

Who is using Vaadin?

2010-08-17T13:37:24Z

The reference list of Vaadin projects is finally out! Check it out here: http://vaadin.com/who-is-using-vaadin.

This is just the first batch of projects we got confirmation on, and there are still a ton of projects that are we are waiting for a permission to add to the list, so stay tuned. There are also several very large users and projects that we will not get permission to publish.

If you want your project to be included in the list we are more than happy to add them! We are thinking for the possibility for anyone to add and manage their project on the list, but for the time being send the required data to me at henri.muurimaa@vaadin.com and I'll make sure it gets added to the site.

For a project we need the following pieces of information:

Name
Description (A short >500 characters showcase for the product. Mentioning Vaadin is optional.)
Creator/supplier (w/logo)
Customer(s) (w/logos)
Industry
Country
Screenshots (optional)
External links (optional)

Vaadin 6.4.2 available

2010-08-13T12:48:05Z

Vaadin 6.4.2 is a maintenance release in the 6.4 series. It includes a number of important bug fixes. See the list of closed issues in Vaadin Trac for a detailed change log. For other release information, see the Release Notes.

Get the installation package from the download site at http://vaadin.com/download. If you are using the Vaadin Plugin for Eclipse, upgrade the Vaadin version from the project preferences.

Problem fixes and enhancements planned for upcoming releases can be found from the Vaadin Roadmap in Vaadin Trac.

As always, when upgrading from an earlier version, you should recompile any custom widget sets and refresh your project in Eclipse. See the General Upgrade Notes for more details on upgrading.

Vaadin 6.4.1 available

2010-07-23T13:10:28Z

Vaadin 6.4.1 is a maintenance release in the 6.4 series. It includes a number of important bug fixes. See the list of closed issues in Vaadin Trac for a detailed change log. For other release information, see the Release Notes.

Get the installation package from the download site at http://vaadin.com/download. If you are using the Vaadin Plugin for Eclipse, upgrade the Vaadin version from the project preferences.

Problem fixes and enhancements planned for upcoming releases can be found from the Vaadin Roadmap in Vaadin Trac.

As always, when upgrading from an earlier version, you should recompile any custom widget sets and refresh your project in Eclipse. See the General Upgrade Notes for more details on upgrading.

Vaadin 6.4.0 for Maven users

2010-07-09T12:25:35Z

There are now updated versions (1.3.0) of the Vaadin Maven archetypes that by default refer to Vaadin 6.4.0 and the latest versions of some Maven plugins.

If your project has been created with an older version and has a widgetset, it contains an "entry-point" row:

1 ...
2 
7 <entry-point class="com.vaadin.terminal.gwt.client.DefaultWidgetSet" />
8
9 <inherits name="com.vaadin.terminal.gwt.DefaultWidgetSet" />
10 ....

You should remove the entry point row in the widgetset (along with the comment that precedes it) and make sure you are using version 1.3-SNAPSHOT of gwt-maven-plugin.

Also, when upgrading Vaadin in a Maven project, make sure you also update the GWT version in your pom.xml - for Vaadin 6.4.0, use GWT 2.0.3.

Vaadin 6.4.0 available

2010-07-08T12:37:54Z

Vaadin 6.4 is finally out, after nearly three months of work. Get the installation package from the download site at http://vaadin.com/download. If you are using the Vaadin Plugin for Eclipse, upgrade the Vaadin version from the project preferences.

The release includes a number of important new features. To see what's new, please check out the Demo Site and especially the Sampler, which highlights the new features.

The biggest enhancements include improved keyboard navigation in Table, Tree, DateField, Slider and many other components (Sampler for Table, Tree and DateField). Both Table and Tree support multi-selection with Ctrl and Shift keys for selecting ranges of items (Table and Tree). In addition, Table now supports a footer row and click listeners on the header and footer (Sampler), as well as column resize listeners. See the Release Notes for a detailed list of new features as well as bug fixes.

As always, when upgrading from an earlier version, you should recompile any custom widget sets and refresh your project in Eclipse. See the General Upgrade Notes for more details on upgrading.

Vaadin 6.4 will now enter maintenance mode and we will be releasing maintenance releases about every two weeks, as necessary. Plans for upcoming releases can be found from the Vaadin Roadmap in the Vaadin Trac.

Vaadin 6.4.0 prerelease 1 available

2010-06-24T12:57:43Z

Vaadin 6.4 is approaching. Meanwhile, the prerelease version includes most of the new features, such as enhanced keyboard navigation and Table footers. We are stabilizing the new features, possibly adding some more, and fixing some bugs. Also API changes to the new features are possible before the final release - please make your comments now.

Vaadin 6.4.0 will be a significant update release for Vaadin 6, with of number of features as well as bug fixes. See the Release Notes for a full list of enhancements and a detailed change log.

Get the installation package from the download site at http://vaadin.com/releases?version=prerelease/6.4/6.4.0/6.4.0.pre1. If you are using the Vaadin Plugin for Eclipse, upgrade the Vaadin version from the project preferences.

There is some preliminary documentation about the new features in:

Demos - check out especially the Sampler for new features (the new samples are marked)
API Documentation
Book of Vaadin for Vaadin 6.4.0

Remaining problem fixes and enhancements planned for the 6.4.0 release can be found from the Vaadin 6.4.0 milestone in Vaadin Roadmap.

As always, when upgrading from an earlier version, you should recompile any custom widget sets and refresh your project in Eclipse. Notice that Vaadin 6.2 uses GWT 2.0 (included in the installation package). See the General Upgrade Notes for more details on upgrading.

Also check out the TreeTable add-on. The long-awaited component was originally scheduled for Vaadin 6.4, but was left as a separate component until it matures. It may be incorporated into the core library in some later release.

RE: Vaadin Grails Plugin

2010-06-20T12:17:53Z

HI

I have the same behaviour. It's normal, cause to enable single class reloading in grails (like controllers or services) you need to write special artifact handling plugins.
As for me, this restart is very fast, so it doesn't harm development a lot

Another issue in grails: when you are using services in vaadin app. you need to restart application (?restartApplication) after service change (cause grails reloads changed service, but it can't update working vaadin apps)

In summury I can say that I feel very comfortable with vaadin in grails

RE: Vaadin Grails Plugin

2010-06-19T13:20:06Z

HI,

I tried this plugin. I have a simple objective that I can be productive by writing my Vaadin code in groovy hence avoiding any restarts/redeploys. In theory I would like to have only the changed class reloaded. Just like how JVM hotswap works. But what I observed is that any changes to files in src/groovy trigger a complete container restart which is not the desired result. I would love it it works like Jrebel (zeroturnaround.com) which replaces only the changed artifacts. My groovy scripts are places in src/groovy. Am I doing anything wrong?
Thanks.

Vaadin 6.3.4 available

2010-06-15T14:56:06Z

Vaadin 6.3.4 is a maintenance release in the 6.3 series. It includes a number of important bug fixes. See the list of closed issues in Vaadin Trac for a detailed change log. For other release information, see the Release Notes.

Get the installation package from the download site at http://vaadin.com/download. If you are using the Vaadin Plugin for Eclipse, upgrade the Vaadin version from the project preferences.

Problem fixes and enhancements planned for upcoming releases can be found from the Vaadin Roadmap in Vaadin Trac.

As always, when upgrading from an earlier version, you should recompile any custom widget sets and refresh your project in Eclipse. If you are upgrading from earlier than 6.3.0, notice that Vaadin 6.3 uses GWT 2.0 (included in the installation package). See the General Upgrade Notes for more details on upgrading.

RE: Testers needed for Portlet 2.0 support

2010-06-15T12:39:18Z

Okay last message ;)

Problem solved!
The following advice could facilitate also the life for different testers.

The portlet.xml is in the documentation well explained, only the example for web.xml is short.
The block <servlet> must be deleted! The servlet-name in <servlet-mapping> must be equal to portlet name from portlet.xml.

RE: Testers needed for Portlet 2.0 support

2010-06-09T09:57:12Z

Martin Biastoch:

I've read the article, but I probably overlooked this part.
Now I have a Portlet without exeception, but also without contents. Are there also changes with Portlet 2.0? Ich set the height to 400px.

Maybe it would be better to move this discussion to one of the other forum categories, out of "News & Announcements".

Try to see e.g. with Firebug if the contents are there, but with zero size, or not. It might be that some other layout level has size settings that make it shrink to zero size.

RE: Testers needed for Portlet 2.0 support

2010-06-09T09:17:34Z

Henri thanks,
I've read the article, but I probably overlooked this part.
Now I have a Portlet without exeception, but also without contents. Are there also changes with Portlet 2.0? Ich set the height to 400px.

Greeting Martin

RE: Testers needed for Portlet 2.0 support

2010-06-09T08:54:19Z

Martin Biastoch:

when i change the application class in portlet.xml from com.vaadin.terminal.gwt.server.ApplicationPortlet to com.vaadin.terminal.gwt.server.ApplicationPortlet2 and implement PortletListener in main Application class, i get an Exception

1
22010-06-09 06:54:38,296 INFO [STDOUT] ERROR - javax.portlet.PortletException: Failed to load application class: servletname
3javax.portlet.PortletException: Failed to load application class: servletname
4 at com.vaadin.terminal.gwt.server.ApplicationPortlet2.init(ApplicationPortlet2.java:48)
5 at com.liferay.portlet.InvokerPortletImpl.init(InvokerPortletImpl.java:250)
6 at com.liferay.portlet.PortletInstanceFactoryImpl.init(PortletInstanceFactoryImpl.java:245)
7 ...

Without Portlet 2.0 it works.

Just a guess: With portlet 1.0, the application parameter refers to web.xml, whereas with portlet 2.0, it should point to the application class. Did you update the application parameter value as well when you updated the portlet class?

See the book.

RE: Testers needed for Portlet 2.0 support

2010-06-09T07:06:41Z

Hello Petter,

when i change the application class in portlet.xml from com.vaadin.terminal.gwt.server.ApplicationPortlet to com.vaadin.terminal.gwt.server.ApplicationPortlet2 and implement PortletListener in main Application class, i get an Exception

Without Portlet 2.0 it works.

Any experience?

RE: Testers needed for Portlet 2.0 support

2010-06-08T14:46:40Z

Hello Petter,

I'm working on a new Portlet with Portlet 2.0. I use Liferay 5.2.3 on JBoss.
I would like to use the Events from Portlet 2,0. I will tell you about working or problems.

Greeting Martin

RE: Vaadin Grails Plugin

2010-06-04T00:40:37Z

Hi All,

Based on Daniel's work, I've released a new (version 1.1) Grails Vaadin plugin. It now supports:

Latest stable Vaadin version (6.3.3 at this time)
Paths to your Vaadin UI other than the context root (e.g. http://www.somehost.com/myapp/vaadinUI)
Per-environment configuration (Vaadin's 'production mode' = true for Grails production environment only. Can be overridden for any environment). Custom environments are also supported (e.g. 'beta', 'uat', etc)

A *huge* benefit to Grails 1.3 users is that because Grails 1.3 supports Groovy 1.7, which can use nested and anonymous inner classes, you can program all of your Vaadin UI in Groovy with natural Rich UI paradigms. For example, button listener registration and nested logic:

1// Remove a contact from a list:
2def removalCount = 0
3contactRemovalButton = new Button("-", new Button.ClickListener() {
4 void buttonClick(ClickEvent event) {
5    contactList.removeItem(contactList.value)
6    //reference a non-final attribute inside an anonymous inner class!
7    removalCount++;
8 }
9})

To install in your grails app:

> grails install-plugin vaadin

Happy coding!

Les Hazlewood
http://www.katasoft.com