Hi Julien,
I have just found that there is
org.gatein.mop.api.workspace.Navigation.getAttributes() on the MOP layer
which could be used to store the requested navigation node properties.
Can somebody see a reason, why this is not a good idea?
Naturally, I'd have to find a way how to prevent a clash with keys we
use internaly (e.g. MappedAttributes). Some simple prefix for the keys
passed from the gatein api could solve that, I guess.
Thanks,
Peter
On 2014-01-16 18:13, Peter Palaga wrote:
Hi *,
I am starting to look at the customer request to provide a way to define
navigation nodes pointing to external URLs. They can accomplish this in
Portal 4.3 using page properties, storing there not only the URL but
also if the link should open in a new window, etc. This data is then
used in a custom navigation portlet.
There is no way known to me how this could be achieved using the present
navigation API. The following wiki page offers a space to discuss the
solution. Please comment!
https://community.jboss.org/wiki/CustomNavigatonNodeProperties
Best,
Peter
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev