[jira] Commented: (WICKET-650) New Wicket Portlet support: use a RenderContext for abstracted url generation, writing header response and namespacing

["Ate Douma (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504782 ] 

Ate Douma commented on WICKET-650:
----------------------------------

As multiple portlets can live on one page, tag id's really need to be unique for each portlet to allow proper usage of Ajax and other dhtml features.

The Portlet API provides the String RenderResponse.getNamespace() method for this, which returns a unique id for the current portlet (Window).

The new RenderContext interface adds both a getNamespace() and a encodeMarkupId(String id) method which should be used for the final markupId generated and returned by Component.getMarkupId().

> New Wicket Portlet support: use a RenderContext for abstracted url generation,  writing header response and namespacing
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-650
>                 URL: https://issues.apache.org/jira/browse/WICKET-650
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket-portlet
>    Affects Versions: 1.3.0-beta2
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>
> To support rendering in a Portlet container, wicket needs to abstract the (final) url, markupId generation and writing the IHeaderResponse.
> I'm going to provide a new base RenderContext class which default implementation (for standard web application purposes) really doesn't do anything.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.