Excuse me, i mistyped my sample.
I'm agree with you. I use
MyLocalServiceUtil service class in the Vaadin portlet (was already like that before I split in two plugins).
Now, my trouble is just that, before the separation, I was using
ObjectImpl class as parameter for
MyLocalServiceUtil methods. And now this class is no longer available (because not known in
service.jar).
example, in some vaadin side code :
ObjectLocalServiceUtil.updateObject(object) where object has been instancied from
ObjectImpl, that is a result of the service building for a final database item objectTable.
The way I'm going to solve this is to replace this client service call by a new one :
ObjectLocalServiceUtil.updateObject(arg1, arg2, arg3...) providing the service with all the necesssary datas to build an Object
and so, in
ObjectLocalServiceUtilImpl I declare a new method :
1
2updateObject (arg1, arg2.....)
3{
4 Object object = objectPersistence.create(counterLocalService.increment(Object.class.getName()));
5 object.setArg1(arg1);
6 object.setArg2(arg2);
7 ...
8 objectPersistence.update(object)
9}
and after regenerate all the stuff with service builder (Interfaces, service.jar...).
I'm just disappointed that I can't use the ObjectImpl classes. I'm forced to declare some POJOs in my vaadin portlet to transport my datas that are very similar to the ones generated by SBuilder.
But after looking Liferay sources, that's the way Liferay is made itself.... so it seems to be the correct way ...
...unless you have an alternative, giving the ability to reuse the Model stack generated by ServiceBuilder from client Portlet?
Anyway, thanks a lot David for your help.
Christophe
Bitte melden Sie sich an, um diesen Inhalt als unangebracht zu kennzeichnen.