Reg : issues with upgrading service builder portlet

RE: Reg : issues with upgrading service builder portlet

2018-12-04T10:02:27Z

Hi Abhishek,

Please, provide more information about what you did: " I have also run the upgrade process changing the servletcontext name in the release_ table"

Thanks.

RE: Reg : issues with upgrading service builder portlet

2018-12-04T09:49:01Z

I am too facing the same problem...the service is not getting registered though it is showing active status. I have also run the upgrade process changing the servletcontext name in the release_ table ..Please help ...any help would be appreciated.

RE: Reg : issues with upgrading service builder portlet

2018-01-31T06:20:51Z

Hi Alberto,
Unfortunately we landed into another issue.

Now the service is not getting registered. Though its deployed & in active state.

When we use XXXLocalServiceUtil.getXXXX() , this throwing null internally getService() method used inside.
When we try to use @Reference , the portlet is coming not up in Add application like shown in link https://web.liferay.com/community/forums/-/message_boards/message/103346926 .

There are some work arounds provided for gradle , but we are using maven in our case , so we are not able to use them.

Kindly provide us few pointers which can help us to resolve the service not registered issue .

regards,
Ramchand

RE: Reg : issues with upgrading service builder portlet

2018-01-30T11:11:06Z

Thanks a lot. This helped us a lot.

regards,
Ramchand

RE: Reg : issues with upgrading service builder portlet

2018-01-30T09:56:29Z

Verify that the javax.portlet.name is the same than in 6.2. This is an example about where that name is defined:
https://github.com/achaparro/liferay-portal/blob/master/modules/apps/chat/chat-web/src/main/java/com/liferay/chat/web/portlet/ChatPortlet.java#L49

If you have another name, you have two options:
- Use the previous one used in 6.2
- Do an upgrade process to switch to the new name in all tables. Like this:
https://github.com/achaparro/liferay-portal/blob/master/modules/apps/chat/chat-web/src/main/java/com/liferay/chat/web/upgrade/ChatWebUpgrade.java

I hope it helps.

RE: Reg : issues with upgrading service builder portlet

2018-01-30T09:36:15Z

Hi Alberto,
No we did not change id of the portlet. We did not use any id attribute in 6.2 as well.
It appears 6.2 has created portlets in page with following conventions since this shown as header in side.

<<PORTLETNAME>>_WAR_<<WARNAME>> .

Any pointers on resolving the issue would be great ?

Note : We have successfully resolved service table creation issue now. Thanks for the help on this.

regards,
Ramchand.

RE: Reg : issues with upgrading service builder portlet

2018-01-30T09:06:42Z

Hi Ramchand,

It seems that the portal does not recognize the new portlet. Have you changed the id of the portlet? If so, you should create an upgrade process to modify of all records from old id to the new id.

Let me know if it works.

Regards.

RE: Reg : issues with upgrading service builder portlet

2018-01-30T04:21:10Z

Hi Alberto,
Thanks a lot . Will check this out.

"This portlet has been undeployed. Please redeploy it or remove it from the page. " Will the above link resolve this issue as well?

regards,
Ramchand.

RE: Reg : issues with upgrading service builder portlet

2018-01-29T15:12:23Z

Hi Ramchand,

Please the following thread to solve your issue:
https://web.liferay.com/es/community/forums/-/message_boards/view_message/99729329

Regards.

Reg : issues with upgrading service builder portlet

2018-01-29T09:14:06Z

Hi Folks,
We had used service builder portlets in 6.2 .
For the DXP upgrade , we have made them into OSGI complaint modules ( api , service , web) & tested this in a standalone instance of the Liferay DXP bundle it works fine.
Now as the the next step , we upgraded the DB of 6.2 instance to DXP using code upgrade tool , after we DB upgrade we deployed OSGI equivalent jar of this portlet & we found below issues.

1) In old pages where this portlet was deployed we got messages "This portlet has been undeployed. Please redeploy it or remove it from the page. "

--> Kindly let us know how to ensure new OSGI complaint portlets automatically come up here .

2) We tried manually configuring the portlet from Add Application , screen & find it is throwing the error , NPE in getService() service

. The service module is started in lb console , but we still get this error. When we scrolled in logs , we found below lines when the service module was getting deployed

Caused by: org.postgresql.util.PSQLException: ERROR: relation "XXXXXXX" already exists

Kindly let us know how to over come these issues.

regards,
Ramchand G