Marco Rosetti 9 Years Ago Noce idea! A quick look at the code, in particular the parte relative to message bus and cache would ve very interesting Please sign in to reply. Reply as... Cancel
Marcus Hjortzén 9 Years Ago Marco, I updated the post with a screenshot of the messagebus/caching! All images are scaled down, if blurry open the image URL in a new tab! Please sign in to reply. Reply as... Cancel Marco Rosetti Marcus Hjortzén 9 Years Ago Thanks Marcus! Please sign in to reply. Reply as... Cancel
Bijan Vakili 9 Years Ago This is a great idea and well done.Usually I use portlet config; it's name is Liferay portlet 86 ( https://t.seebgroup.com/portlet-86 ). The advantage being you get scoping: for each portlet you can scope the config: Company Wide, Unique Per Layout, Owned By Grouphttps://t.seebgroup.com/preferences-company-wideAnd can specify the action here:https://t.seebgroup.com/configuration-action-classThen it would show through the portlet config.Disadvantage is it's decentralized. Please sign in to reply. Reply as... Cancel Marcus Hjortzén Bijan Vakili 9 Years Ago Another disadvantage is that you would have to implement a lot of code in each new portlet. Also, not all code have a UI (we have a lot of scheduled tasks and filters that depend upon feature toggling). Please sign in to reply. Reply as... Cancel Bijan Vakili Marcus Hjortzén 9 Years Ago Well, I don't know if I'd say it's a lot; this is since you can specify:<configuration-action-class>com.liferay.portal.kernel.portlet.DefaultConfigurationAction</configuration-action-class>See */html/wiki_display/{init,configuration}.jsp for example; LR actually did most of work; retrieving is simple as well here:portletPreferences.getValue("prop", "defaultValue") Please sign in to reply. Reply as... Cancel Ben Broome Marcus Hjortzén 6 Years Ago Hi Marcus, this sounds just like what we're looking for. Would you be happy to share the code?Thanks Please sign in to reply. Reply as... Cancel
Marcus Hjortzén Bijan Vakili 9 Years Ago Another disadvantage is that you would have to implement a lot of code in each new portlet. Also, not all code have a UI (we have a lot of scheduled tasks and filters that depend upon feature toggling). Please sign in to reply. Reply as... Cancel Bijan Vakili Marcus Hjortzén 9 Years Ago Well, I don't know if I'd say it's a lot; this is since you can specify:<configuration-action-class>com.liferay.portal.kernel.portlet.DefaultConfigurationAction</configuration-action-class>See */html/wiki_display/{init,configuration}.jsp for example; LR actually did most of work; retrieving is simple as well here:portletPreferences.getValue("prop", "defaultValue") Please sign in to reply. Reply as... Cancel Ben Broome Marcus Hjortzén 6 Years Ago Hi Marcus, this sounds just like what we're looking for. Would you be happy to share the code?Thanks Please sign in to reply. Reply as... Cancel
Bijan Vakili Marcus Hjortzén 9 Years Ago Well, I don't know if I'd say it's a lot; this is since you can specify:<configuration-action-class>com.liferay.portal.kernel.portlet.DefaultConfigurationAction</configuration-action-class>See */html/wiki_display/{init,configuration}.jsp for example; LR actually did most of work; retrieving is simple as well here:portletPreferences.getValue("prop", "defaultValue") Please sign in to reply. Reply as... Cancel
Ben Broome Marcus Hjortzén 6 Years Ago Hi Marcus, this sounds just like what we're looking for. Would you be happy to share the code?Thanks Please sign in to reply. Reply as... Cancel