[fredf]

yes there is no way as we don't have storage for persisting long term the changes.

it would work if you don't persist the changes.

Ok, maybe have had a little too high expectations (no offence) on the DnD functionality. My aim is to persist the positions of the dragged windows on the server made on any portal page.

I see in the DynaAjaxServlet that there is some code that is commented out that persists the values (fromRegion, toRegion, windowId etc) sent from the sendData() function in the dyna.js javascript code. Will this be used in the future?

[fredf]

After some analyzing it turns out that the positions of the dragged windows are stored persistently into portal database after all. It is not the DynaAjaxServlet that is requested upon DnD from the client. It is an AjaxCommandFactory that is set up and the PortalServlet is recieving the request. Ok. So basically what I need to do is enable the DynaRenderSet not only for the dashboard context but for any page visited. I have debugged the portal "theme module" for a while now but I am having trouble finding where it is decided if dynarenderer or divrenderer should be used for rendering the regions and thereby add the aftersought tag in the resulting html.

Which object and when is it set which dynarenderer will be used?
Is it as early as in the line (RegionTagHandler.java)

JSPRendererContext renderContext = (JSPRendererContext)request.getAttribute(LayoutConstants.ATTR_RENDERCONTEXT);

Roy Russo or Martin Holzner, can you give me some input on this?
(maybe this thread should be moved to the development forum?)

thanks.

[julien1]

try this :

modify the jboss-portal.sar/conf/data/default-object.xml, in the portal you want to be DnDable, add the following :

 <property>
 <name>theme.dyna.dnd_enabled</name>
 <value>true</value>
 </property>

[fredf]

Nothing happens. I tried it both in the portal deployment tag but also in the dashboard context tag with value false to see if that affected the dashboard but that did not change anything either. Also I tried it on my custom-object.xml in my deployed warfile but that I guess should definitly not work if I have understood you right. Maybe the dnd is not configurable but set entirely based on the request of either dashboard context or ordinary portal pages?

I found the LayoutDispatcher instance interesting. It looks like that it is involved in setting whether dynaregionrenderer is used or not. In the line

PageRendererContext page = (PageRendererContext)request.getAttribute(LayoutConstants.ATTR_PAGE);

from where does the request get its LayoutConstants.ATTR_PAGE value?
I see that the ApplicationHttpRequest contains the string "/dashboard" in pathInfo. Maybe the value of LayoutConstants.ATTR_PAGE is set depending on the pathInfo?