On Monday 20 January 2014 at 10:46, Peter Palaga wrote:
Hi Julien, inline...On 2014-01-20 10:33, Julien Viet wrote:Hi Peter,can you describe the attributes you would like to store in this map ?Sure. Cite from* Both keys and values of the new node Properties would allow strings only* The API would guarantee the uniqueness of the keys per node* The API would not guarantee anything about store/iteration order ofthe properties* GUI for editing the properties not a priority* Authorization: same as for other Navigation Node attributes - who canedit those, can edit also the new properties.-- PeterJulien VietOn Friday 17 January 2014 at 13:58, Peter Palaga wrote:Hi Julien,I have just found that there isorg.gatein.mop.api.workspace.Navigation.getAttributes() on the MOP layerwhich 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 weuse internaly (e.g. MappedAttributes). Some simple prefix for the keyspassed from the gatein api could solve that, I guess.Thanks,PeterOn 2014-01-16 18:13, Peter Palaga wrote:Hi *,I am starting to look at the customer request to provide a way to definenavigation nodes pointing to external URLs. They can accomplish this inPortal 4.3 using page properties, storing there not only the URL butalso if the link should open in a new window, etc. This data is thenused in a custom navigation portlet.There is no way known to me how this could be achieved using the presentnavigation API. The following wiki page offers a space to discuss thesolution. Please comment!Best,Peter_______________________________________________gatein-dev mailing listgatein-dev@lists.jboss.org <mailto:gatein-dev@lists.jboss.org>