Message Boards

Facelet redeploy in LR 7+ like in LR 6.2

Martin Vaněk, modified 3 Years ago.

Facelet redeploy in LR 7+ like in LR 6.2

New Member Posts: 11 Join Date: 3/12/16 Recent Posts
Hello ,

I am trying to gather information for migrating to LR 7+. 

I develop portlets with Liferay Faces and Primefaces on 6.2. Whenever I change .xhtml file, the change is instantly reflected on started server (Eclipse with Liferay IDE plugin does this automatically). However from what I have read this is not possible due necessity to convert WAR file into WAB (since LR only support OSGi modules). Is there a way to achieve this functionality for developing? It makes working with facelets so much easier.
I have read the forums, stack overflow, help articles. Tried gradle workspace, maven workspace both with Eclipse and Intellj, nothing seems to work. Liferay Blade task watch is not available for Liferay faces projects, nor does blade deploy -w work for me. 

From what I have gathered this is simply not possible, is there any way to speed up the development process without the need to build the whole war for e.g. a typo change? I know only about Eclipse automatically doing the maven package for building the war whenever change happenes but I would like to avoid doing that. 

Thanks for your work, looking forward to your response.
thumbnail
Neil Griffin, modified 3 Years ago.

RE: Facelet redeploy in LR 7+ like in LR 6.2

Liferay Legend Posts: 2655 Join Date: 7/27/05 Recent Posts
Hi Martin,
There is a brand new Gradle task called `deployFast` in Liferay Workspace. It is not yet implemented for Maven.  You can find a how-to video at Mastering Liferay.

Please give it a try and let me know if it works for your JSF portlet.

Thanks,
Neil
Martin Vaněk, modified 3 Years ago.

RE: Facelet redeploy in LR 7+ like in LR 6.2

New Member Posts: 11 Join Date: 3/12/16 Recent Posts
Hello back Neil,

Thanks for the quick response.
I have looked up the deployFast task, watched the video (thanks for the resource tip), but the deployFast task is not available for war projects, which Liferay Faces and JSF requires. So sadly, it cant be used. I think it is has the same limitation as the watch task.
thumbnail
Neil Griffin, modified 3 Years ago.

RE: Facelet redeploy in LR 7+ like in LR 6.2

Liferay Legend Posts: 2655 Join Date: 7/27/05 Recent Posts
Hi Martin,
May I ask where you got the information that deployFast does not work with war projects? Was that in the video?
I have not tried it yet myself, but it is my best understanding that it does indeed work with war projects.
Thanks,
Neil
Martin Vaněk, modified 3 Years ago.

RE: Facelet redeploy in LR 7+ like in LR 6.2

New Member Posts: 11 Join Date: 3/12/16 Recent Posts
Hello again,

I tried it myself in Gradle workspace on latest version of Liferay Gradle Workspace.

Replying a bit later because I tried different combinations like putting the JSF project under the module folder but that does not work. Normally it has to be in wars folder as far as I know, that didnt work as well. Intellj doesn't show me deployFast option for .war project but shows the option for module project. From that I assumed it doesn't work with wars just as watch doesn't work it wars (same behavior, it cant be called). Tried calling it from command line too but without a success, the task doesnt exist for war projects.
thumbnail
Neil Griffin, modified 3 Years ago.

RE: Facelet redeploy in LR 7+ like in LR 6.2

Liferay Legend Posts: 2655 Join Date: 7/27/05 Recent Posts
Hi Martin,
Apologies -- it was my understanding that deployFast already supported war projects. I contacted the tooling team within Liferay and learned that support for war projects is on the roadmap.
Kind Regards,
Neil
Tristian Abshire, modified 3 Years ago.

RE: Facelet redeploy in LR 7+ like in LR 6.2

New Member Post: 1 Join Date: 10/23/20 Recent Posts
Elements of the resource identifier in brackets ([]) are optional, indicating that only a resource-name, which is usually a file name, is a required element. For example, the most common way to specify a style sheet, image, or script is to use the library and name attributes, as in the following tag from the example:  <!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}-->MyBPCreditcard login

<h:outputstylesheet library="css" name="default.css" /> [url=https://www.mybpcreditcard.review/] [/url]<!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}-
</code></pre>-->