[
https://issues.apache.org/jira/browse/WICKET-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834495#action_12834495
]
Igor Vaynberg commented on WICKET-1620:
---------------------------------------
wicket 1.5 (trunk) may not come with portlet support.
the goal for 1.5 was to rewrite the url/request handling because it was very
fragile. we are almost done with the code and will probably have 1.5 milestone
1 soon. however, since we do not have any active committers who also work with
the portlet api none of that code is in 1.5 and the old code from 1.4 was not
portable because the api is completely changed
. it would be great to get feedback from Ate and other portlet developers about
the current code in 1.5 and how pluggable it is with respect to the
requirements of the portlet api.
if we do not find someone who is willing to devote the time to build the
portlet support into the new code it may not come with it.
> Portlet 2.0 support
> -------------------
>
> Key: WICKET-1620
> URL: https://issues.apache.org/jira/browse/WICKET-1620
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Thijs Vonk
> Assignee: Ate Douma
> Fix For: 1.5-M1
>
> Attachments: myWicketPortal20Patch-example-project.patch,
> myWicketPortal20Patch-v2.patch,
> myWicketPortal20Patch-v3-example-project.patch,
> myWicketPortal20Patch-v3.patch, portlet2-0.patch, portlet2-0.patch,
> WICKET-1620-portlet2.0-tight.patch, WICKET-1620-portlet2.0.patch
>
>
> Upgrade wicket to fully support portlet 2.0 (jsr 286;
> http://jcp.org/en/jsr/detail?id=286).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
