On Tue, 25 Feb 2003, Mete Kural wrote:

> Date: Tue, 25 Feb 2003 09:31:36 -0800 (PST)
> From: Mete Kural <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: Struts Users Mailing List <[EMAIL PROTECTED]>
> Subject: Re: Struts and Portlets
>
> --- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote:
> > I'm definitely interested in making it possible to
> > reuse Struts-based
> > webapp things (actions, form beans, pages, business
> > logic) in a portlet.
> > That's going to take some refactoring and
> > abstraction of the fundamental
> > APIs -- but it's definitely going to be worth doing.
>
> Craig, what would be the scope of implementing the
> Portlet API in Struts? Would it encompass implementing
> some features of a portal server? Do you think it is
> practical to provide a portal server platform within
> Struts?
>

The result of JSR 168 is going to be an API contract between a portal
server and a portlet -- much like the Servlet API contract between a
servlet container and a Servlet.  As such, I think the best role for
Struts is to answer the "how do you program a portlet" rather than "how do
I build a portal server".

The analogy in the servlet space is that there's no need for Struts to
implement the servlet API, since lots of containers (including Tomcat) do
that for you.  Instead, I want to make it possible to write Struts-based
portlets that can run on *anyone's* portal server that supports JSR-168.
That doesn't mean we have to write the portal server itself -- it means we
need to implement the portlet API analog of what ActionServlet does for
servlet requests.

Now, another interesting question is "can I build a portal server based on
Struts that can then incorporate JSR-168 portlets?"  The thinking is that
you could use Tiles and other Struts based features to manage the
aggregation that portal servers do.  There are certainly people in the
world who have done this sort of thing already (Liferay, BasicPortal,
etc.) for non-JSR-168 portlet APIs, so it's clearly feasible, and it's a
pretty good idea.  But, from my perspective, this sort of thing is
actually a Struts-based application, rather than part of the framework
itself.

> Thanks,
> Mete

Craig

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

Reply via email to