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: Porletresources (DXP 7.1)
Hi,
portletmigration from DXP 7.0 to DXP 7.1 looks great so far (working with ext 5.0.4, impl 4.1.3, portal 3.0.4, util 3.2.0 a.t.m.)
My tiny problem is that I cannot see text from portlet properties, we're writing xhtml like
I made no changes regarding location or processing of properties and it worked in 7.0.
Are you aware of any changes regarding portlet properties from 7.0 to 7.1 in bridge or liferay code?
Regards,
gun
portletmigration from DXP 7.0 to DXP 7.1 looks great so far (working with ext 5.0.4, impl 4.1.3, portal 3.0.4, util 3.2.0 a.t.m.)
My tiny problem is that I cannot see text from portlet properties, we're writing xhtml like
value="#{i18n['foo.label']}"
and I see "foo.label" instead of the properties value.I made no changes regarding location or processing of properties and it worked in 7.0.
Are you aware of any changes regarding portlet properties from 7.0 to 7.1 in bridge or liferay code?
Regards,
gun
Kyle Joseph Stiemann, modified 6 Years ago.
Liferay Master
Posts: 760
Join Date: 1/14/13
Recent Posts
Hi Gunnar,
Could you please provide the smallest, simplest portlet that reproduces your issue? The best way to do that is to generate a portlet from our archetypes and add the required code to reproduce the issue.
- Kyle
Could you please provide the smallest, simplest portlet that reproduces your issue? The best way to do that is to generate a portlet from our archetypes and add the required code to reproduce the issue.
- Kyle
Gunnar Brinkmann, modified 6 Years ago.
RE: Porletresources (DXP 7.1)
(Answer)
Junior Member
Posts: 54
Join Date: 12/2/11
Recent Posts
Hi Kyle,
difficult because of complex Maven-Architecture and not much time.
But it looks like I've found it:
I had to add
Dependency versions I used for portlet migration from 7.0 to 7.1:
com.liferay.portal.kernel 3.61.0, com.liferay.util.java 3.0.23, com.liferay.portal.language.extender 3.0.13, com.liferay.faces.portal 3.0.4, com.liferay.faces.bridge.impl 4.1.3, com.liferay.faces.util 3.2.0, com.liferay.faces.bridge.ext 5.0.4, com.liferay.faces.alloy 3.0.2, com.liferay.portal.configuration.metatype.api 1.1.8, com.liferay.portal.configuration.metatype.definitions.annotations 3.0.4, com.liferay.portal.configuration.metatype.definitions.equinox 3.0.0, primefaces 7.0.4 and javax.servlet-api 3.1.0.
Note: Portet dependencies might not have been up-to-date in 7.0 (not always the newest versions)
Regards,
gun
difficult because of complex Maven-Architecture and not much time.
But it looks like I've found it:
I had to add
<message-bundle>content.Language</message-bundle>
to the faces-config.xml, which has not been necessary in 7.0 (same portlet on a 7.0-System shows the label value from Language properties.Dependency versions I used for portlet migration from 7.0 to 7.1:
com.liferay.portal.kernel 3.61.0, com.liferay.util.java 3.0.23, com.liferay.portal.language.extender 3.0.13, com.liferay.faces.portal 3.0.4, com.liferay.faces.bridge.impl 4.1.3, com.liferay.faces.util 3.2.0, com.liferay.faces.bridge.ext 5.0.4, com.liferay.faces.alloy 3.0.2, com.liferay.portal.configuration.metatype.api 1.1.8, com.liferay.portal.configuration.metatype.definitions.annotations 3.0.4, com.liferay.portal.configuration.metatype.definitions.equinox 3.0.0, primefaces 7.0.4 and javax.servlet-api 3.1.0.
Note: Portet dependencies might not have been up-to-date in 7.0 (not always the newest versions)
Regards,
gun
Thanks for posting your solution Gunnar.
You're welcome, but its peanuts compared to all your guru-work and -documentation I've seen over the years.
Thank YOU :-)
Thank YOU :-)
It's my pleasure Gunnar. Thanks for the kind words.

Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™