[Building Sakai] Wicket, Portlets and JSR-168

[Matthew Jones]

Yea, it looks like portlets *were* supported in 1.4 but were removed in 1.5
because nobody was actively maintaining it. (
https://issues.apache.org/jira/browse/WICKET-2976)

The ticket for 1.5 is open with no activity in over a year there or the
repository though.

https://issues.apache.org/jira/browse/WICKET-4019

And old comment on https://issues.apache.org/jira/browse/WICKET-1620 was
that
"we will not be providing portlet support until we have an active committer
that wants to maintain it"

So I wouldn't be betting on this short term, but seems like we could keep
projects back on 1.4 until/if this is ever resolved? Only 2 projects in
core are currently wicket (profile2/sitestats) and both of them are on
1.4.x.



On Sun, Dec 15, 2013 at 8:33 AM, Charles Severance <csev at umich.edu> wrote:

> Just a crazy idea - it seems as though the Wicket community is dabbling
> with JSR-168 support:
>
>
> http://apache-wicket.1842946.n4.nabble.com/Wicket-6-x-and-Portlet-Support-td4654098.html
>
> I am wondering if we could in one fell swoop eliminate the iframes of all
> the wicket apps.  It would also make it so we could build a completely
> frameless portal as the wicket applications were the last group of apps
> that resisted our efforts to inline in the PDA portal.
>
> Just thinking out loud
>
> /Chuck
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131215/3ed188e1/attachment.html