[
https://issues.apache.org/jira/browse/WICKET-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504799
]
Ate Douma commented on WICKET-650:
----------------------------------
Abstracting Header response writing is handled by WICKET-651
> 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.
