Hi team and community,
Thijs Vonk, Antony Stubbs and myself have been working over the past few months
on upgrading and improving the Wicket Portlet.
Primary goal for that was upgrading to the now available Portlet API 2.0 so to make it more easy to get Wicket working on other portals
besides Apache Jetspeed-2.
The initial JIRA issue where we started out was https://issues.apache.org/jira/browse/WICKET-1620 and especially Antony added a lot of new
features like Portlet Events handling.
Those *new* features will require some real changes to Wicket core, and for
that reason I changed WICKET-1620 to target Wicket 1.5.
However, upgrading *only* the current Wicket Portlet to use and support Portlet
API 2.0 does *not* require any real changes to Wicket core.
Therefore, I created https://issues.apache.org/jira/browse/WICKET-2058 which
only deals with this part of the upgrade.
I and Thijs have been testing the patches for that issue and we have already been able to verify it to be fully working on Apache Pluto,
Apache Jetspeed-2, SUN Open Portal container and (latest) Liferay Portal.
For JBoss Portal (2.70) an Exo Portal Container (2.0.5) there are still a few (JBoss) or Exo (serious) problems, but AFAIK those really are
because of an incorrect or limited JSR-286 implementation by those portals.
I plan to commit WICKET-2058 (WICKET-2058-patch2.txt, attached to the issue) tomorrow to get it in before the 1.4-RC2 release, unless
somebody raises objections.
Please note again: there are no real changes to Wicket core, and all changes
are contained within code used for portlet support only.
Furthermore, I've removed the dependency on Apache Portals Bridges common
(1.0.4) as that is no longer needed anymore either.
Regards,
Ate
