[
https://issues.apache.org/jira/browse/WICKET-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651573#action_12651573
]
Ate Douma commented on WICKET-1620:
-----------------------------------
I agree the discussion needs to be about the design of the solution, but for
that I definitely need to take a look at the proposed implementation too.
For me it was to cumbersome to try to see the core Wicket changes (besides the
obvious portlet specific ones) between all the javadoc changes.
And I also like to see the example event portlet actually working in Pluto too!
I got it running (by *not* doing a mvn clean but just take the Eclipse compiled
sources) and fixing PLUTO-517, but then got event payload loading errors
instead :(
Anyway, as I said I'll try to look into both the code and the design questions
next week in the evening hours and get back to you as soon as I've got a better
overview.
> 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
> 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.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.
