Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: rename portlet war file
Hi,
i deploy my portlets as a bunch of war files. portet1.war,portlet2.war, portlet3.war etc.
If I mergerthese wars and create a single war portlet.war. Will it impact my private pages?
i intend to keep the settings in liferay-portlet.xml, portlet.xml and web.xml.
Any suggestions how i should be doing this?
i deploy my portlets as a bunch of war files. portet1.war,portlet2.war, portlet3.war etc.
If I mergerthese wars and create a single war portlet.war. Will it impact my private pages?
i intend to keep the settings in liferay-portlet.xml, portlet.xml and web.xml.
Any suggestions how i should be doing this?
Rohit Venkat:
Hi,
i deploy my portlets as a bunch of war files. portet1.war,portlet2.war, portlet3.war etc.
If I mergerthese wars and create a single war portlet.war. Will it impact my private pages?
i intend to keep the settings in liferay-portlet.xml, portlet.xml and web.xml.
Any suggestions how i should be doing this?
I use liferay 6.0.6 CE
Lokhande Vishnudas D., modified 12 Years ago.
Regular Member
Posts: 152
Join Date: 5/27/13
Recent Posts
If I mergerthese wars and create a single war portlet.war. Will it impact my private pages?
how are you going to merge that wars?
Hi Rohit,
There are times Liferay uses the Fully Qualified Portlet ID (FQPI) to uniquely identify a portlet. Merging the portlets into a single war file would change the FQPI so there could definitely be an impact on pages where these portlets have been deployed. If this would impact a lot of pages you could programmatically update the layouts but if it's a small number of pages or if you're using page templates you could update the references manually.
Also, the web app context is used if you are producing any remote services in these portlet applications, so changing the name could have an impact on any remote clients that rely on these services.
There are times Liferay uses the Fully Qualified Portlet ID (FQPI) to uniquely identify a portlet. Merging the portlets into a single war file would change the FQPI so there could definitely be an impact on pages where these portlets have been deployed. If this would impact a lot of pages you could programmatically update the layouts but if it's a small number of pages or if you're using page templates you could update the references manually.
Also, the web app context is used if you are producing any remote services in these portlet applications, so changing the name could have an impact on any remote clients that rely on these services.