On Tue, 16 Sep 2003, Mete Kural wrote:

> Date: Tue, 16 Sep 2003 11:14:03 +0100
> From: Mete Kural <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>,
>      [EMAIL PROTECTED]
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: Where is Struts 2 going?
>
> Great! I read the whiteboard. Do you know when the development for the
> portlet related aspects of Struts 2.0 may begin. I know that there are
> some Jetspeed developers who are interested in contributing to a project
> that aims to turn Struts into a portlet framework. I think that adding
> more committers to Struts that are coming from a portal/portlet
> background would be of great benefit to the development of Struts 2.0.
> Unfortunately, I am under-skilled for that, but I can refer some
> individuals to you who have the skills from the Jetspeed project, if you
> wish.
>

One approach to dealing with it has (in fact) already begun -- in the
"contrib/struts-chain" subdirectory in the CVS sources is the beginnings
of a refactoring of the standard RequestProcessor based on the
"commons-chain" package in the Commons Sandbox.  If this actually works,
two really good things might be able to happen:

* It'll work for both servlets and portlets (you can see how the
  command implementations are being abstracted so that the chain
  will just do the right thing for each environment).

* It is likely to be backwards compatible with Struts 1.1 as well,
  possibly with some restrictions yet to be discovered.

The best way to get involved would be to check out CVS sources for both
jakarta-struts and jakarta-commons-sandbox, become familiar with the code
referenced above, and start making suggestions and improvements.  A really
good starting point would be portlet-specific implementations of all the
commands that currently have only servlet-specific implementations.

> Regards,
> Mete

Craig

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to