Liferay IDE 1.2 New and Noteworthy
Previous New and Noteworthy pages #
New features in 1.2 #
Portlet UI Frameworks #
Liferay IDE now has support for 3 different portlet UI frameworks.
- Liferay MVC (default framework for 6.0 SDK)
- JSF - based on JSF 2.0 and portletfaces bridge (requires Liferay 6.1)
- Vaadin - based on Vaadin framework (requires Liferay 6.1)
In the new Liferay Project wizard, on the 2nd page, you are now given the option for selecting a portlet framework.
JSF Portlet Wizard #
To create JSF portlets, first create a new Liferay project, select portlet for plugin type and click Next to go to the portlet UI framework select page and select JSF framework and click Finish
Once you have a JSF portlet project you can create new JSF portlets with the new JSF Portlet wizard.
The New JSF Portlet wizard will create a JSF portlet based on the PortletBridge project and will generate facelet XHTML files for the view.
XHTML files are generated in JSF wizard.
Vaadin Portlet Wizard #
To create Vaadin portlets, first create a new Liferay project, select portlet for plugin type and click Next to go to the portlet UI framework select page and select Vaadin framework and click Finish
Once you have a vaadin portlet project you can create new Vaadin portlets with the New vaadin Portlet wizard
The New Vaadin portlet wizard instead of creating a portlet class, it creates a new Vaadin Application class and wires up the Vaadin portlet in portlet.xml to render the application in Liferay.
Improved features in 1.2 #
Improved Ext plugin deployment #
Ext plugin deployment has been reworked in the 1.2 release. It is now fully supported in the IDE for all use-cases, deploy (publish), undeploy (clean), and re-deploy (uses direct-deploy ant task)
- Multiple deploys (redeployment) now works as expected from IDE, note that auto-matic publishing for Ext plugins is not enabled. It requires manually invoking a publish for Ext plugins. Other projects (portlets, hooks) are still automatically published.
- Undeploying of Ext plugins is now supported through the Clean App Server action
- Clean app server action is invokved as a context menu action from Ext plugin project
- Requires extra runtime configuration for specifying the zip bundle
- Multiple Ext plugins are not supported on one server
Custom server settings #
The Liferay Tomcat server has additional settings that can be customized for the developer's use.
- User timezone can be set
- Server memory arguments can be set
- IF user has external properties they would like to set (added to -Dexternal.properties) they can be specified
Other improvements #
- SDK build.<username>.properties can now be optionally updated during SDK commands to match the Liferay IDE configuration (app.server properties)
- Liferay Hook wizard can now add hooks to both Hook and Portlet projects
- Service builder tasks are not performed in external JRE with more memory available
- Multiple or custom service.xml files are now supported
