Tribune

Home » Liferay IDE » English

Vista Combinata Vista Piatta Vista ad Albero
Discussioni [ Precedente | Successivo ]
toggle
Dennis Nes
HotDeploy for Vaadin Portlets
4 ottobre 2011 11.31
Risposta

Dennis Nes

Punteggio: Junior Member

Messaggi: 55

Data di Iscrizione: 23 settembre 2009

Messaggi recenti

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
5 ottobre 2011 12.47
Risposta

David H Nebinger

Punteggio: Liferay Legend

Messaggi: 4496

Data di Iscrizione: 1 settembre 2006

Messaggi recenti

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
7 ottobre 2011 18.19
Risposta

Gregory Amerson

LIFERAY STAFF

Punteggio: Liferay Master

Messaggi: 775

Data di Iscrizione: 16 febbraio 2010

Messaggi recenti

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
23 dicembre 2011 9.26
Risposta

Fei Yan

Punteggio: New Member

Messaggi: 1

Data di Iscrizione: 22 dicembre 2011

Messaggi recenti

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
23 dicembre 2011 10.04
Risposta

David H Nebinger

Punteggio: Liferay Legend

Messaggi: 4496

Data di Iscrizione: 1 settembre 2006

Messaggi recenti

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).