thank you jelmer
but none of these methods worked for me
i read
http://www.liferay.com/community/wiki/-/wiki/Main/Using+Class+Loader+Proxy+classes+to+share+plugins+services
http://www.liferay.com/community/forums/-/message_boards/message/5968217
its all the same but also no one talk about the exception it throws
in my case
1ERROR [jsp:154] com.liferay.portal.kernel.bean.BeanLocatorException: BeanLocator has not been set
2at com.liferay.portal.kernel.bean.PortletBeanLocatorUtil.locate(PortletBeanLocatorUtil.java:40)
I tried this methods that Peter mentioned about
1. Placing the portlet-service.jar in the app server's global class path and not in the plugin's web-inf/lib
2. Restarting the app server
and this
1. Copying the portlet-service.jar to both plugin's web-inf/lib directories
2. Redeploying both portlets
and the same exception
I also tried to regenerate the same services in the two portlets and deploy it
and also the same exception !!
i don't know where the problem is?
as i can call any liferay portlet service from anywhere
and the portlet-service placed in the server global path
(as i did to my custom-portlet-service.jar)
any other idea will be appreciated
Bitte melden Sie sich an, um diesen Inhalt als unangebracht zu kennzeichnen.