[
https://issues.apache.org/jira/browse/WICKET-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated WICKET-655:
-----------------------------
Affects Version/s: (was: 1.3.0-beta2)
1.3.0-beta3
Switching to a new 1.3.0-beta3-portlet-support branch and provide a much
improved implementation which now covers most standard use-cases I think.
> New Wicket Portlet support: Encode Wicket urls through RenderContext to allow
> a PortletRenderContext to replace them by PortletURLs
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-655
> URL: https://issues.apache.org/jira/browse/WICKET-655
> Project: Wicket
> Issue Type: Sub-task
> Components: wicket-portlet
> Affects Versions: 1.3.0-beta3
> Reporter: Ate Douma
> Assignee: Ate Douma
>
> Wicket already nicely encapsulated encoding the final Wicket urls with
> IRequestCodingStrategy.
> I'm not sure if urls are created through other means but so far didn't find
> any :)
> Of course, there are already two separate implementations of
> IRequestCodingStrategy, WebRequestCodingStrategy and
> CryptedWebRequestCodingStrategy, so in the end both these implementations
> will have to be adapted to allow for portlet-support.
> Right now, I've limited myself to adapting the WebRequestCodingStrategy only,
> CryptedWebRequestCodingStrategy can be done once all is working sound and
> solid.
> The WebRequestCodingStrategy changes are not yet 100% complete and I probably
> need help from others to do so.
> With my initial changes, I already get most of the wicket-examples working
> just fine in Jetspeed-2, and I'd like it to be tested and reviewed by others
> before diving deeper into this.
> Note: the initial changes I'll commit still are non-intrusive and don't
> depend on a portlet context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
