Ate Douma wrote:
Thijs Vonk wrote:
I've started on implementing the portlet 2.0 specifications. I've
opened https://issues.apache.org/jira/browse/WICKET-1620 to apply
patches to when I get something useful.
But I have some questions before I can go any further.
First of all, do we drop portlet 1.0 in favor of portlet 2.0? I
suppose we do because we need java 5 to support 2.0 but portlet 1.0
doesn't support java 5.
Portlet 1.0 doesn't require Java 5, that's not the same.
I don't want to drop support for portlet 1.0 yet, certainly not until
Jetspeed 2 provides portlet 2.0 support :)
My proposal is adding a new WicketPortlet2 class (or something, I
don't like the name but haven't come up with something better yet).
This class should set a clear marker (like a new request or portlet
context attribute or something) to indicate to the other supportive
classes within Wicket which environment the current request is dealing
with, and use the native Portlet API 2.0 methods if in context of the
current request.
Yeah ok, I'm not sure if we'll introduce a lot of if-statements/casting
if we do it this way.
I was thinking that, because Wicket 1.3 is quite stable, people could
use Wicket 1.3 if they use a portlet 1.0 only portal. And because Wicket
1.5 won't be out for a while, portlet 2.0 might finally be released and
maybe Jetspeed/other portals could be heading in that direction as well.
(I have no insight in the JS-2 time frame)
However, I'll look into the WicketPortlet2 option as well.
What I'm not sure about is the ServletContextProvider. (from apache
portal bridges) I can't really determine if I can drop this as well.
For now I've left it in and it seems to work (on Liferay) but I could
be doing some hybrid crossover now :)
That one isn't needed anymore either for portlet 2.0. The
PortletRequestDispatcher now supports all request types.
Ok, I'll need to look at those chapters again :)
It would be great if you could attach a patch file of your changes to
the new JIRA issue for example.
I'd rather not :) The work I've done isn't really publish worthy, as it
is more of a search for me to try and find my way around all the changes
and inner works of both the portlet specs and how they are implemented
in Wicket. (Writing a portlet and getting Wicket to behave like a
portlet are quite different things :))
But now that I have some direction I might get something out in the next
couple of weeks (If I can find a portal that'll support my changes :P)
BTW: I won't be able to do much on this issue this week as I have to
go to Dublin for a client.
Same here, I've got a deadline on Friday and probably a lot of cleaning
up in the week(s) after so this is not high on the priority list.
Ate
Thijs
