[
https://issues.apache.org/jira/browse/WICKET-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated WICKET-650:
-----------------------------
Description:
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 RequestContext class which default
implementation (for standard web application purposes) really doesn't do
anything.
was:
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.
Affects Version/s: 1.3.0-beta3
Summary: New Wicket Portlet support: use a RequestContext for
abstracted url generation, writing header response and namespacing (was: New
Wicket Portlet support: use a RenderContext for abstracted url generation,
writing header response and namespacing)
Switching to a new 1.3.0-beta3-portlet-support branch.
In the process of moving to this new branch, renamed RenderContext to
RequestContext as it better reflects its purpose, so I also update this issue
summary accordingly.
> New Wicket Portlet support: use a RequestContext 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, 1.3.0-beta3
> 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 RequestContext 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.
