- This topic has 31 replies, 20 voices, and was last updated 15 years, 8 months ago by
.
-
Posts
-
Guys I’m going to broach Portlets for 6.1 with management. I know at one point the product manager was asking about demand and I let him know it was “fairly high”, so it’s atleast on his mind.
I’m just about to start using Liferay. Most of my team is using Netbeans, which apparently has pretty good support. Should I be switching over too? Or will MyEclipse make it easy for hot deployment?
Thanks
Milind,
We haven’t announced direct tooling for Liferay at this time. Certainly MyEclipse hotsync deployment would be available to you, but I would suggest evaluating both tools (maybe 1 week each) and see which one you are more productive with.Boy, that was quick!
As impressive as Netbeans has been the past few releases, I still use Eclipse for core Java. But for java EE and Matisse has leapfrogged Eclipse (IMO – don’t want to start a flame war here). I used to use MyEclipse 5 years ago when I was doing EE and I loved the hot deploy. Is there any links on how to use MyEclipse for deployment of portlets?
Milind,
JSR-168 overview is here:
http://www.myeclipseide.com/documentation/quickstarts/portlet_overview/and our specific support for the WebSphere portlet stack is here:
http://www.myeclipseide.com/documentation/quickstarts/blueedition/wps6_tutorial/It certainly helped!
I’ll document the steps I followed for others in the same boat
1. Install Liferay following the instructions on setting auto deploy directory etc. 2. Install MyEclipse 3. Create the portlet as documented in http://www.myeclipseide.com/documentation/quickstarts/portlet_overview/ 4. Create a Tomcat configuration pointing to the Liferay installation This can be done from Eclipse Preferences dialog or from the "Servers" view Tomcat Home Directory : E:\Dev\liferay-portal-tomcat-6.0-5.1.2 JDK VM args : -Xms128m -Xmx512m -Dfile.encoding=UTF8 -Duser.timezone=GMT -XX:MaxPermSize=128m -Djava.security.auth.login.config=E:/Dev/liferay-portal-tomcat-6.0-5.1.2/conf/jaas.config 5. Export the project as a war file to the liferay auto deploy directory. Exporting it to the webapps directory does not work. It explodes the war file, but does not register the portlet. I'm new to portlets and Liferay, and there may be some way around this. Deploying it to the auto deploy directory, registers the portlet and explodes the war file in the webapps directory. 6. Start Liferay (Tomcat) server from the "Servers" view in Eclipse. 7. Open the browser, point to the http://localhost:8080/. Log in and add the portlet from the "Undefined" list. 8. From the Servers view, select "Add Deployment..." from the popup menu Deploy as "Expanded Archive" to the webapps folder. For some reason, I couldn't get it to deploy as a packaged archive. (so have to export the project as a war file in Step #5 above) 9. Change the code of the portlet and refresh the browser. You will see the changed code. You can set break points in the code and the debugger will stop in your code.Still have the following problems that I need to work through.
1. There were times when adding/removing deployment would remove the portlet registration and I had to do remove the webapp if it existed and repeat steps 5 and 8 again. 2. Changes in Java code are hot deployed, but strangely changes in the jsp file are not reflected until I stop and restart liferay.It would be nice if MyEclipse could reduce all these steps by deploying
the portlet so it would get registered. And also add some liferay specific
files like “liferay-display.xml” etc. But all in all, not too bad.Milind,
That is absolutely in line with our thinking moving forward and refining the portlet support. We need to ease the development as much as possible. Thank you for the feedback and details for others.
