Xinsheng Robert Chen 12 Years Ago It sounds very interesting. I will give it a try. Thank you! Please sign in to reply. Reply as... Cancel
Jan Gregor 12 Years Ago After some testing I must say, this is amazing! I am going to test it a bit deeper to see, whether it is usable for production and stable with different enviroments. If yes, then it is a huge move forward especially for portal development! Please sign in to reply. Reply as... Cancel
Jay Patel 12 Years Ago This is good...thnx for Sharing...Can we achieve the same for extension environment, apart from using reloadable=true? Please sign in to reply. Reply as... Cancel Neil Griffin Jay Patel 12 Years Ago Since Liferay lives in a web application context (for example, webapps/ROOT under Tomcat), then JRebel should work just fine for EXT plugins. You would just need to add a rebel.xml file to the web application context in which Liferay is deployed. Please sign in to reply. Reply as... Cancel
Neil Griffin Jay Patel 12 Years Ago Since Liferay lives in a web application context (for example, webapps/ROOT under Tomcat), then JRebel should work just fine for EXT plugins. You would just need to add a rebel.xml file to the web application context in which Liferay is deployed. Please sign in to reply. Reply as... Cancel
(You) 12 Years Ago [...] If you look for official info in our documentation about JRebel supporting Liferay, you will not find it yet; we are working towards getting this more formalized in future JRebel releases. However,... [...] Read More Please sign in to reply. Reply as... Cancel
Petros Giakouvakis 12 Years Ago Hi Neil, I tested JRebel myself just using the JRebel documentation offered during installation (which is really excellent I must say) and got Liferay working with JRebel and making use of the MVCPortlet as the base. Both the presenation jsp as well as the java classes are now instantly reloaded on the save of the content, but changing configuration files such as liferay-portlet.xml and portlet.xml still require a restart. Is this the same with you?Regardless of this: JRebel seems to really speed up the development cycle that is sure. So thanks for this very inspiring post! Please sign in to reply. Reply as... Cancel Jan Gregor Petros Giakouvakis 12 Years Ago Hi Petros,I thinks this is ok, since these deployment descriptors are checked by each deployment of a plugin and thus the plugin must be re-deployed in order to see changes in mentioned descriptors. Anyways it would be nice to have a plugin for Liferay to enable hot-swap of these descriptor. I am not sure whether it will be possible on the Liferay part. Please sign in to reply. Reply as... Cancel Neil Griffin Jan Gregor 12 Years Ago @Petros: Jan is right -- it would be really nice to have portlet.xml and other descriptors get reloaded as well, but it is something I think we can live with. Perhaps this is something the folks at zeroturnaround.com could investigate as a feature. Please sign in to reply. Reply as... Cancel
Jan Gregor Petros Giakouvakis 12 Years Ago Hi Petros,I thinks this is ok, since these deployment descriptors are checked by each deployment of a plugin and thus the plugin must be re-deployed in order to see changes in mentioned descriptors. Anyways it would be nice to have a plugin for Liferay to enable hot-swap of these descriptor. I am not sure whether it will be possible on the Liferay part. Please sign in to reply. Reply as... Cancel Neil Griffin Jan Gregor 12 Years Ago @Petros: Jan is right -- it would be really nice to have portlet.xml and other descriptors get reloaded as well, but it is something I think we can live with. Perhaps this is something the folks at zeroturnaround.com could investigate as a feature. Please sign in to reply. Reply as... Cancel
Neil Griffin Jan Gregor 12 Years Ago @Petros: Jan is right -- it would be really nice to have portlet.xml and other descriptors get reloaded as well, but it is something I think we can live with. Perhaps this is something the folks at zeroturnaround.com could investigate as a feature. Please sign in to reply. Reply as... Cancel
Sampsa Sohlman 12 Years Ago Actually, we have used this for years Please sign in to reply. Reply as... Cancel Neil Griffin Sampsa Sohlman 12 Years Ago @Sampsa: Great to hear. JRebel must be the world's best kept secret! Please sign in to reply. Reply as... Cancel Petros Giakouvakis Neil Griffin 12 Years Ago @Jan and Neil: thank you for the info. I can definitely live with this, as these changes don't occur al that often after all. I just wasn't sure if I might have made some JRebel configuration error. I am definitely recommending JRebel from now on as is. :-) Please sign in to reply. Reply as... Cancel
Neil Griffin Sampsa Sohlman 12 Years Ago @Sampsa: Great to hear. JRebel must be the world's best kept secret! Please sign in to reply. Reply as... Cancel Petros Giakouvakis Neil Griffin 12 Years Ago @Jan and Neil: thank you for the info. I can definitely live with this, as these changes don't occur al that often after all. I just wasn't sure if I might have made some JRebel configuration error. I am definitely recommending JRebel from now on as is. :-) Please sign in to reply. Reply as... Cancel
Petros Giakouvakis Neil Griffin 12 Years Ago @Jan and Neil: thank you for the info. I can definitely live with this, as these changes don't occur al that often after all. I just wasn't sure if I might have made some JRebel configuration error. I am definitely recommending JRebel from now on as is. :-) Please sign in to reply. Reply as... Cancel
Daniel Tomsu 12 Years Ago Hi Neil, thanks for the great post. I do have a slight problem though and was wondering if anyone else is in the same situation:I do have the application running in the debug perspective of eclipse and starting with the registered server there, not with the bin/startup script. I disabled the automatic publishing, as it is recommended by the jRebel Feature.The class changes are working just fine, but any jsp changes don't get deployed. Any help on that. Thanks a lot. Please sign in to reply. Reply as... Cancel Neil Griffin Daniel Tomsu 12 Years Ago Hi Daniel. Thanks for the kind words. I normally do all my work with Facelets and so I haven't tried JSP. You might want to try the JRebel forums regarding that. Please sign in to reply. Reply as... Cancel
Neil Griffin Daniel Tomsu 12 Years Ago Hi Daniel. Thanks for the kind words. I normally do all my work with Facelets and so I haven't tried JSP. You might want to try the JRebel forums regarding that. Please sign in to reply. Reply as... Cancel
(You) 11 Years Ago [...] If you look for official info in our documentation about JRebel supporting Liferay, you will not find it yet; we are working towards getting this more formalized in future JRebel releases. However,... [...] Read More Please sign in to reply. Reply as... Cancel
Mathieu Hicauber 11 Years Ago Hi,Just downloaded jrebel eclipse plugin.I also use Liferay IDE plugin for Eclipse.Everything goes smooth during jrebel plugin installation. Then I add my liferay server to jrebel managed servers through the JRebl perspective. The java agent seems to ben installed , as I can see the following log lines :============================================================JRebel: Starting logging to file: C:\Documents and Settings\utilisateur\.jrebel\jrebel.log[2012-07-02 08:20:28] [2012-07-02 08:20:28] #############################################################[2012-07-02 08:20:28] [2012-07-02 08:20:28] JRebel 5.0.0 (201206080930)[2012-07-02 08:20:28] (c) Copyright ZeroTurnaround OU, Estonia, Tartu.........#############################################################Next step, I add the jrebel nature to one of my portlet projects. The rebel.xml file is created,, with the classpath configuration pointing to the WEB-INF/classes of the project in the plugin SDK.But when I alter my portlet class, nothing happen in the portal : the class is compiled by the IDE in ${pluginSDK}/portlets/myproject/docroot/WEB-INF/classes, but never deployed to my app server.Am I missing something here ? Please sign in to reply. Reply as... Cancel Neil Griffin Mathieu Hicauber 11 Years Ago I would recommend that you do the following:1. Right click on your portlet project, and left click on Properties2. Click on Java Build Path3. Click on the Source tab4. Make sure that the "Default output folder" text field has the same value as the <classpath> <dir> entry in rebel.xml Please sign in to reply. Reply as... Cancel
Neil Griffin Mathieu Hicauber 11 Years Ago I would recommend that you do the following:1. Right click on your portlet project, and left click on Properties2. Click on Java Build Path3. Click on the Source tab4. Make sure that the "Default output folder" text field has the same value as the <classpath> <dir> entry in rebel.xml Please sign in to reply. Reply as... Cancel
Mathieu Hicauber 10 Years Ago - Edited THat was some one and a half year a ago, but I'll give it another try :-)Thanks for the tip. Please sign in to reply. Reply as... Cancel