How to retain the portlet Id of a spring mvc based portlet during upgrade?How to retain the portlet Id of a spring mvc based portlet during upgrade?https://uat.liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=1216224832026-10-15T12:00:23Z2026-10-15T12:00:23ZRE: RE: How to retain the portlet Id of a spring mvc based portlet during upgrade?Olaf Kockhttps://uat.liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1216231582023-01-02T09:25:16Z2023-01-02T09:25:15Z<p>This <em>must</em> be something that Liferay is doing all the time.
I'm assuming that there's some reusable Upgrade-routine code that you
can pass in the old and the new portlet-id. Technically that does the
database change that you're looking to avoid, but as you don't have to
do the work yourself, this might not be too bad (and you'll be in a
somewhat standardized environment of generated portlet IDs)</p>Olaf Kock2023-01-02T09:25:15ZRE: RE: How to retain the portlet Id of a spring mvc based portlet during upgrade?Rajesh Chaurasiahttps://uat.liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1216226742022-12-30T13:21:07Z2022-12-30T13:16:51Z<p>Hi Olaf</p>
<p>Thanks for your reply.</p>
<p>Since the portlets were bundled into another spring mvc portlet ,
they had the container portlet mentioned in its portlet id for ex <em>
<strong>knowledgecookiesnavigation_WAR_knowledgecookiesportlet
</strong>is a <strong>knowledegcookies-navigation
portlet </strong></em>being contained under the main <strong>knowledgecookies-portlet.</strong></p>
<p>I did use the portlet id that was there in the liferay-portlet.xml
for the portlet ie<em> <strong>knowledgecookies-navigation
</strong></em>but the<em>
<strong> knowledgecookiesnavigation_WAR_knowledgecookiesportlet </strong></em>
as portlet wasn't generated in the process so this portlet didnt find
placed on page on successful deployment.I had to forcibly add it to
the page via add application but this thing I want to avoid.Since I am
working on upgrading the code from 7.1 to 74 and wanted to maintain
the portlet id references that database on 7.1 was having so that I
dont have to alter the database tables like portlet table , layout
table etc.</p>Rajesh Chaurasia2022-12-30T13:16:51ZRE: How to retain the portlet Id of a spring mvc based portlet during upgrade?Olaf Kockhttps://uat.liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1216226332022-12-30T12:20:10Z2022-12-30T12:20:09Z<p>Have you tried using the old portlet id explicitly? What happens?
What's the behavior? Is there some decoration going on that the portal
does to those portlet ids? (I never look at them, thus I can't tell
from the top of my head)</p>
<p>Please describe what you observe, what you expect, and what you've tried</p>Olaf Kock2022-12-30T12:20:09ZHow to retain the portlet Id of a spring mvc based portlet during upgrade?Rajesh Chaurasiahttps://uat.liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1216224822022-12-30T03:36:51Z2022-12-30T03:36:50Z<p>Hi All,</p>
<p>We had a portlet which was spring mvc based porltet , it was having
21 spring mvc based portlets bundled into one mammoth war style portlet.</p>
<p>We upgraded them to 7.4 from 7.1 and kept some of them as spring mvc
based portlet as some of them were using lot of spring web / mvc based
features so we kept them as it is to avoid doing lot of testing or
migrating them to Liferay MVC.We want that the portlet id to be the
same as earlier.But in Spring MVC portlet we have to define the
portlet id in xml config files like liferay-portlet.xml,portlet.xml,liferay-display.xml.</p>
<p>
<strong>Old portlet id :</strong></p>
<p>
<em>knowledgecookiesnavigation_WAR_knowledgecookiesportlet</em></p>Rajesh Chaurasia2022-12-30T03:36:50Z