Marco Rosetti Il y a 9 années Noce idea! A quick look at the code, in particular the parte relative to message bus and cache would ve very interesting Veuillez vous identifier pour voter. Répondre en tant que ... Annuler
Marcus Hjortzén Il y a 9 années 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! Veuillez vous identifier pour voter. Répondre en tant que ... Annuler Marco Rosetti Marcus Hjortzén Il y a 9 années Thanks Marcus! Veuillez vous identifier pour voter. Répondre en tant que ... Annuler
Marco Rosetti Marcus Hjortzén Il y a 9 années Thanks Marcus! Veuillez vous identifier pour voter. Répondre en tant que ... Annuler
Bijan Vakili Il y a 9 années 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. Veuillez vous identifier pour voter. Répondre en tant que ... Annuler Marcus Hjortzén Bijan Vakili Il y a 9 années 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). Veuillez vous identifier pour voter. Répondre en tant que ... Annuler Bijan Vakili Marcus Hjortzén Il y a 9 années 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") Veuillez vous identifier pour voter. Répondre en tant que ... Annuler Ben Broome Marcus Hjortzén Il y a 6 années Hi Marcus, this sounds just like what we're looking for. Would you be happy to share the code?Thanks Veuillez vous identifier pour voter. Répondre en tant que ... Annuler
Marcus Hjortzén Bijan Vakili Il y a 9 années 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). Veuillez vous identifier pour voter. Répondre en tant que ... Annuler Bijan Vakili Marcus Hjortzén Il y a 9 années 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") Veuillez vous identifier pour voter. Répondre en tant que ... Annuler Ben Broome Marcus Hjortzén Il y a 6 années Hi Marcus, this sounds just like what we're looking for. Would you be happy to share the code?Thanks Veuillez vous identifier pour voter. Répondre en tant que ... Annuler
Bijan Vakili Marcus Hjortzén Il y a 9 années 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") Veuillez vous identifier pour voter. Répondre en tant que ... Annuler
Ben Broome Marcus Hjortzén Il y a 6 années Hi Marcus, this sounds just like what we're looking for. Would you be happy to share the code?Thanks Veuillez vous identifier pour voter. Répondre en tant que ... Annuler