If you are using NetBeans 7.1 or 7.1.1, you can now use Portal Pack plugins in your IDE. Because of a library mismatch the previous Portal Pack 3.0.5 binary was not working with NetBeans 7.1. Finally I have compiled Portal Pack sources with latest NetBeans 7.1/7.1.1.
Tags: netbeans, NetBeans 7.1, NetBeans 7.1.1, portal pack 3.0.5, Portlets, Portlets plugin
Tags: liferay, netbeans, NetBeans 7, portal pack, portal pack 3.0.5, portlet development
Portal Pack 3.0.5 Beta for NetBeans IDE 7 is now available for download.
- Compatible with NetBeans IDE 7.x
- Works with maven based web project
- Works with Liferays maven projects
- Service builder plug-in is compatible with Liferay 6.0.4 and later
I have released this as beta to address any major regressions before the main release. You can submit issues here.
Tags: netbeans, portal pack, portal pack 3.0.4, portalpack, service builder, servicebuilder
I got few comments in my previous blog that the Service Builder functionality is broken in Portal Pack 3.0.4 & Liferay 6.0.5. After a little investigation, I found that there are few changes in the new liferay release in service builder part. I will fix that issue in the next release.
It is a regression and due to lack of QA resources, we could not test it.
Meanwhile, I would really like to know from the users that what are the features you are using most in Portal Pack ? And any area where you want improvement ? These information are really critical for the next release, as I don’t have much bandwidth to develop and test everything😦 . So based on your feedback I can priorities the areas and will make sure those would be tested properly in future releases.
Also based on your feedback, if there are more users using service builder plugin in Portal Pack, I will try to do a better integration for service builder plugin in Portal Pack.
Also if you have any new suggestions or if you would like to contribute to this project in any way like QA or development, please let me know.
There is a workaround or alternative which is little tricky.
– Please download the servicebuilder.jar from http://portalpack.netbeans.org/servicebuilder.jar
– Go to your ~userhome/.netbeans/6.9/ directory
– Remove the existing servicebuilder directory
-Unjar the downloaded jar inside ~userhome/.netbeans/6.9 directory
-Now try to generate the service without restarting NetBeans. It should work.
But if you restart your NetBeans, the servicebuilder directory will be overwritten with the default files. So you need to follow the above steps again.
Tags: liferay, netbeans, portal pack, portal pack 3.0.4, portalpack, portlet container, portlet development, portlet plugin
I am pleased to announce that a new version Portal Pack 3.0.4 is now available for download. There was a long gap between Portal Pack 3.0.3 and 3.0.4 release because of various reasons. But this new version is aimed to be compatible with NetBeans 6.9, Liferay 6 and also latest version of Portlet Container.
So here are some key features
- Support For Liferay 6
- Compatible with NetBeans 6.5 to NetBeans 6.9
- Latest Portlet Container Support on both GlassFish V2 & V3
Many thanks to Deepak for helping me for this release.
If you want to contribute any new feature or doc, you can leave a message here in this blog or send a mail to portalpack at contrib.netbeans.org
FYI, This project is no longer sponsored by Sun/Oracle.
After leaving from Sun, now here you can find me blogging about technology and myself. I have imported some of my old blog posts here. But you can still access my old blog posts at http://blogs.sun.com/satya (Hope Oracle will keep it live…) and my liferay’s blogs at http://www.liferay.com/web/satyaranjan/blog
As you know Portal Pack 3.0.1 provides a nice service builder editor where you can add/remove services and also generate service classes from NetBeans IDE. These services can be deployed on Liferay/Web Space server. To know more about how the services can be generated using Portal Pack, check this blog.
If all your portlets are deployed on the same liferay instance, then they can consume those services through normal java calls. But what about exposing a service as remote service, so that it can be consumed by remote clients. But currently the service builder plug-in in Portal Pack doesn’t generate SOAP, JSON classes which are required to expose a remote service as SOAP and JSON and hence can not be consumed by remote clients.
So if you are using service builder plugin in NetBeans, here are some steps provided by Ilya Zverev in this forum post to generate soap/http/json classes for the services in your service.xml . I am just doing the copy paste of those steps here in this blog
- Create service using ServiceBuilder.
- Create new package apart from your portlet and create an interface there with all service methods.
- Use Apache Axis’ Java2WSDL and WSDL2Java to create all soap classes and deploy.wsdd .(You can also manually call the build-wsdd target)
- Find YourServiceSoapBindingImpl.java and write implementations for all methods to call corresponding YourServiceUtil methods, generated by ServiceBuilder.
- Build this package and put it into tomcat/webapps/ROOT/WEB-INF/lib folder;
- Take <service> tag from generated deploy.wsdd file and copy-paste it into tomcat/webapps/tunnel-web/WEB-INF/server-config.wsdd near other services.
- Copy the jar generated with ServiceBuilder into tomcat/common/lib/ext
- Stop, then start tomcat, deploy your portlet.
- Check http://localhost:8080/tunnel-web/axis for your service. It should be there.
Thanks to Ilya Zverev for these steps.
Meanwhile we are trying to automate these steps in Portal Pack Service Builder and hope you won’t need to follow all these manual steps in next update release of Portal Pack.
There is an issue with JSF Portlet (Woodstock portlet) with page navigation created by Portal Pack 3.x and running on Liferay or Web Space Server. So if you have page navigation inside jsf portlet, then no component in the portlet is shown when try to navigate to the a second page.But if you reload the page, the portlet is shown properly. This behaviour is there only with Firefox, but it works fine with IE.
So the detail steps to reproduce this issue are
1)Create a JSF portlet app using portal pack that uses page naviagation (say from page1 to page2)
2)Deploy the portlet app
3)Click on some botton in page1 to naviagate to page
Issue:Page2 of the JSF portlet is not rendered untill a referesh.Issue not seen in IE..
So now the good news is, there’s a workaround
From the jsf jsp page remove webuiAll="true" attribute from <webuijsf:themeLinks……/> tag. Everything works perfectly in Firefox & IE after removing this attribute.