Hi everyone,

I have solved the problem.

Just to be sure that we are on the same page here my requirements:

1) Having all my business services in one "component"
2) Having many portlets using those services out of that "component"

The trick is to build that "component" as an portlet under the context "builder". All generated services generated by service builder will refer to that "builder" context.

Than you have to generate the "api" jar and put that jar in the lib folder of each portlet using those services. (or in tomcat lib/ext folder)

That's it!

I know this is a quite poor description - so if you like I could send the eclipse project so that you can transform the solution to either back to plugin sdk or any other IDE.

I have adopted plugin sdk so that it fits well into eclipse dynamic projects and multi service support. I'm planning to extend this to be fully integrated into eclipse as an eclipse plugin.

Anyone interested?

All the best

Andreas
xaxii.com

Hi Dennis,

the problem is that I changed the plugin sdk ant scripts quite a bit to get the things run as smooth as possible in eclipse.

So let me switch back to a pure sdk how-to:

1) create a portlet called "builder". Note: the name "builder" is essential !! This portlet will cover all persistent services you intend to create.
2) create your service xml in the WEB-INF folder of the builder portlet
3) run the build-service target. This will create all classes needed for persistent services.
4) run the war (or the deploy) target and deploy the war to your container
5) check the log for any exception - also check whether the database was created. It will be automatically created by deploying the war.

6) now create a jar file from the "service" folder of the builder portlet.
7) put that jar file in the WEB-INF/lib folder of your portlet which will use the persistent services
8) create a war file of your portlet and deploy it to your container.

Now when your portlet is accessing the persistent services, the xxLocalServiceUtil class in the service api jar will search for the portlet with the name "builder" and retrieve the corresponding beans from the spring application context in the builder portlet. Thats how your portlet can access the persistent service implementation.

If you still get the "BeanLocator has not been set" message means that you didn't deploy a portlet under the "builder" context!

The limitation of the current plugin sdk implementation is that you only can create one service in the builder portlet. To overcome that limitation you need to change folder structure and ant scripts of the plugin sdk. But that might be the next step ... :-)

Hope this helps

Andreas
Xaxii.com

Beanlocator has not been set is a common error in service builder in liferay.Can someone in liferay tell us how to do this once and for all please

Thanks in advance.

Hello All
i think i solved this problem !
When i use MyPortletUtil i have same problem as you but i look inside of generated jar file and i found that there is another class called MyPortletLocalServiceUtil.
Instead of MyPortletUtil try to use MyPortletLocalServiceUtil , i think it can help you.

Thanks
S.M.H.Jamali