Forums

Home » Liferay IDE » English

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Dennis Nes
HotDeploy for Vaadin Portlets
October 4, 2011 11:31 AM
Answer

Dennis Nes

Rank: Junior Member

Posts: 55

Join Date: September 23, 2009

Recent Posts

Hi,

I successfully managed to set up Vaadin and depoly a Vaddin portlet to LR. However for deploying I have to go to this procedure (all manually): Save my Java file, export to WAR and copy to the deploy dircectory, remove the portlet and redeploy it from the menu.

Is there a possibility to hot depoly it, so after saving the code the steps above are done automatically?

Thanks in advance!

My config:
LR IDE 1.4
LR 6.0
Vaadin 6.7
David H Nebinger
RE: HotDeploy for Vaadin Portlets
October 5, 2011 12:47 PM
Answer

David H Nebinger

Rank: Liferay Legend

Posts: 7851

Join Date: September 1, 2006

Recent Posts

Hot deploy will work, but you have to remember that your vaadin app is actually (mostly) running in the browser via javascript and backed by entities stored in the portlet session.

After hot deploy, log out and then back into Liferay (the logout will destroy current portlet session objects) and should resolve your issues.
Gregory Amerson
RE: HotDeploy for Vaadin Portlets
October 7, 2011 6:19 PM
Answer

Gregory Amerson

LIFERAY STAFF

Rank: Liferay Master

Posts: 953

Join Date: February 16, 2010

Recent Posts

Can you post a sample project where you don't see hotdeploy (and redeploy) not working correctly? And I can try to reproduce and see if there is something specifically that can be done to improve this in IDE.
Fei Yan
RE: HotDeploy for Vaadin Portlets
December 23, 2011 9:26 AM
Answer

Fei Yan

Rank: New Member

Posts: 1

Join Date: December 22, 2011

Recent Posts

I am trying to develop Vaadin portlet in Liferay IDE. My question is: How to do Hot Deploy anyway? Should I use ant-deploy or the regular eclipse "Server" view.

If I do both, will that be a conflict? (deploy twice)

When I use ant-deploy, I got the following exception
Buildfile: E:\liferay-plugins-sdk-6.1.0-ce-rc1-20111219113511317\portlets\VaadinLiferay-portlet\build.xml
compile:
merge:
Copying 1 file to E:\liferay-plugins-sdk-6.1.0-ce-rc1-20111219113511317\portlets\VaadinLiferay-portlet\docroot\WEB-INF\lib
Copying 5 files to E:\liferay-plugins-sdk-6.1.0-ce-rc1-20111219113511317\portlets\VaadinLiferay-portlet\docroot\WEB-INF\lib
compile-java:
merge:
war:
build-css:
java.lang.NoClassDefFoundError: com/liferay/portal/tools/SassToCssBuilder
Caused by: java.lang.ClassNotFoundException: com.liferay.portal.tools.SassToCssBuilder
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Could not find the main class: com.liferay.portal.tools.SassToCssBuilder. Program will exit.
Exception in thread "main"
Java Result: 1
compile:
merge:
compile-java:
merge:
build-common-plugin.war:
Deleting: E:\liferay-plugins-sdk-6.1.0-ce-rc1-20111219113511317\dist\VaadinLiferay-portlet-6.1.0.1.war
clean-portal-dependencies:
Building zip: E:\liferay-plugins-sdk-6.1.0-ce-rc1-20111219113511317\dist\VaadinLiferay-portlet-6.1.0.1.war
deploy:
Copying 1 file to E:\liferay-portal-6.1.0-ce-b4\deploy
BUILD SUCCESSFUL
Total time: 13 seconds
David H Nebinger
RE: HotDeploy for Vaadin Portlets
December 23, 2011 10:04 AM
Answer

David H Nebinger

Rank: Liferay Legend

Posts: 7851

Join Date: September 1, 2006

Recent Posts

We do all of our vaadin portlets in the SDK. If you do also, just invoke ant on your build script and the war file will eventually get dropped into your local deploy directory.

To hot deploy on a different system, drop the war file from the sdk/dist directory into the deploy directory on the other system and Liferay will pick it up and deploy it (unless you're in web logic land where I understand they had hot deployment issues, but those might have been resolved by now).