Vaadin portlet creation should include ajaxable=false to liferay-portlet.xml
Description
is duplicated by
Activity
Show:

Cynthia Wilburn March 12, 2012 at 2:18 PM
Reopening to add 6.1.1 CE GA2. Close as Fixed.

Michael Saechang February 16, 2012 at 3:09 PM
Committed on:
6.1.x Plugins GIT ID: 55aff1a0ec0d95fe3d217cb91e93f8117e7654d0.
6.2.x Plugins GIT ID: 55aff1a0ec0d95fe3d217cb91e93f8117e7654d0.

Gregory Amerson January 26, 2012 at 6:03 AM

Gregory Amerson January 24, 2012 at 4:44 PM
Thanks for this report, we will get this fixed in time for next SDK release for 6.1 (either EE or GA2).
Fixed
Details
Assignee
Gregory AmersonGregory AmersonReporter
Henri SaraHenri SaraBranch Version/s
6.1.xBackported to Branch
CommittedComponents
Fix versions
Affects versions
Priority
Medium
Details
Details
Assignee

Reporter

Branch Version/s
6.1.x
Backported to Branch
Committed
Components
Fix versions
Affects versions
Priority
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Zendesk Support

Linked Tickets
Created January 24, 2012 at 5:32 AM
Updated June 24, 2023 at 3:54 PM
Resolved March 12, 2012 at 2:37 PM
When the ajaxable setting is true (default), loading of Vaadin 6 applications can result in the portlet body contents being removed when adding the first such portlet on a page. A page reload is required to make it visible.
This seems to be caused by the GWT bootstrapper using document.write (see http://dev.vaadin.com/ticket/6977), and adding "ajaxable=false" to liferay-portlet.xml solves the problem. Therefore, the template used by Liferay IDE should contain that setting.