two or three weeks a go I had a look on the current source for the
portlet integration. They are currently stored at the wicket stuff
project. This source do not compile with the wicket 1.3 release (this
was two or three week ago). I play around with the source and get some
examples of the "normal" examples work in the liferay portal. I stop
working, because I had difficults to show images in the portlet. I had a
look at the sources to understand what the problem is. During looking at
the source I see some tricky (tricky from the viewing point of a portlet
container -- correctly from the point of a servlet container) points in
the wicket 1.3 sources. This points must be solved to get wicket running
in a portlet container (e.g. a portlet container has no HttpRequest, a
portlet container has no path and so on, typecast from WebRequest to
HttpWebRequest or getting the path of the application, which is not
available in a portlet container). Up to now I had now time to write
down the points which will be difficult to solve and currently the
source of 1.3 will be code freezed so this stuff could only be solved in
future releases.
The architecture of wicket looks like that the protocol over which
wicket will be use should be "plugable". Is this right?
It should be yeah. Around Wicket 1.0 we introduced a couple of extra
abstractions to facilite portlets. I'm pretty sure we've had basic
portlet support up for some time, so it should be possible to fold
this in for 1.3 again. The main issue now is that we need enough
people with enough energy to work on it and this time finish the job.
Eelco
