Ate,

You know you have my support :)  I am drooling over using wicket to replace
Jetspeed 2's existing Velocity-based layout-portlets and decoration api.

Regards,
-Scott (also a Jetspeed committer ;)

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:wicket-user-
> [EMAIL PROTECTED] On Behalf Of Ate Douma
> Sent: Saturday, August 20, 2005 11:57 PM
> To: [email protected]
> Cc: [email protected]
> Subject: [Wicket-user] JSR-168 Portlet support development started
> 
> All,
> 
> I finally got some time this week to start with the JSR-168 Portlet
> support and I
> committed my first set of changes for that to the 1_2 branch.
> 
> Beware: this is still very much a work in progress (not "process" as I
> accidentally
> wrote in some commit messages :-).
> 
> As you already can tell from my changes, this will require some big
> structural
> changes because currently Wicket is still very deeply entangled with the
> Servlet api.
> To be able to use Wicket in a Portlet context, *all* of that needs to be
> abstracted
> away to a generalized interface.
> And, although I will do my best to keep as much of the current public api
> intact,
> important changes will be required.
> 
> This is a "major operation" which will take easily several weeks or more,
> and although
> I'm very dedicated to get this working ASAP, I can only work on this in my
> own free time.
> Furthermore, although I have a rough idea what will be needed, it
> certainly will take
> some time before the whole picture becomes clear. So don't expect this to
> be finished
> or even stabilized overnight.
> 
> Next week, I'll try to provide a global overview of the things I think are
> needed.
> 
> I think it also might be interesting to know why I'm working on the JSR-
> 168 support.
> I'm a core developer of the Apache Jetspeed 2 Enterprise Portal:
>    http://portal.apache.org/jetspeed-2.
> And, I'm also the creator of the Struts Portlet Bridge which allows you to
> use Struts
> for JSR-168 Portlet Development.
> 
> Since I created the Struts Bridge, other Portlet bridges were developed
> too (not only by me)
> and recently the Apache Portals Project Management Committee decided to
> create a new
> (and Jetspeed independent) home for these bridges:
>    http://portals.apache.org/bridges.
> 
> And then came Wicket :-)
> 
> We of the Jetspeed-2 team have become very interested in Wicket as
> possible portlet
> development framework. So, a few months ago, I got in touch with Eelco and
> after some
> discussions I agreed on joining the Wicket team and help providing native
> portlet support.
> I also like to mention that others from the Jetspeed-2 team have promised
> to provide support.
> 
> So, everyone interested in Wicket Portlets: please help out with
> discussing, coding and
> testing this baby.
> 
> Regards,
> 
> Ate Douma
> 
> Oh, and I'm also Dutch ;-)
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to