RE: [Springframework-developer] Portlet and JSFs

[Faizan H. <fa...@ru...>]

Please see my comments at the bottom


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
William G. Thompson, Jr.
Sent: Friday, April 09, 2004 7:35 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Portlet and JSFs

Ben Alex wrote:
> Hi Bill
>=20
>=20
>>Rutgers is very interested in Spring support for the Portlet=20
>>API in the form of a PortletDispatcher as it were.  We run=20
>>the uPortal[1] platform and the latest release embeds Pluto. =20
>>We are just now embarking on dev cycle for new porlets that=20
>>takes us thru september, if possible these new portlets would=20
>>live behind a Spring PortletDispatcher.
>>
>>We have had some preliminary dicussions with Alef about what=20
>>it might look like, and should be in a better positition to=20
>>try out some ideas/code in a few weeks.
>=20
>=20
> I took a look at uPortal but wondered how hard it would be to get =
Spring
MVC
> capabilities living within a portlet window. Have you actually done
anything
> like this as yet, or are your Spring applications essentially
"traditional"
> (dedicated JSP/VM etc)?
>=20

So far all of our Spring apps are "traditional"; leveraging the full=20
compliment of the Spring stack (WebMVC, DAO, JDBC Abstraction,=20
ApplicationContext, declaritive transaction management, AOP, etc.) and=20
living in a dedicated Servlet context.

We have used Spring DAO/JDBC support for a few simple Channels=20
(Portlets), but that is the extent of it.

We are extremely pleased with the Spring development model and would=20
like to bring our portal project in line.

I don't think it should be too hard to bring SerlvetDispatcher behavior=20
to the Portlet API.  The big difference is that Portlets participated in =

a two step call (ActionRequest/Response and RenderRequest/Response) and=20
also have additional lifecycle events, PortletMode (View, Edit,=20
Help,...) and WindowMode (min, max, normal, etc.) that impact behavior=20
of the service.

later.
Bill

Since we got into this discussion, I would like to add few more =
differences
between Portlets and Serverlets.
- Portlets generate fragments, whereas servlets generate complete =
documents.
- Unlike servlets portlets are not bound directly to a URL.

According to my understanding there are few things that portlets have =
but
servlets don't

- Portlets are able to perform portlet rewriting, so as to create links =
that
are independent of the portal server implementation
- portlets has two different session scopes in which to store object:
application wide and portlet private.
-Portlets has access to user profile information that is definitely far
beyond the basic user and role information provided in the servlet
specifications.

Similarly there are few things that servlets can do but portlets can not =
do
that. For example

-Portlets can not alter the HTTP headers or set response encoding.
-Portlets can not access the URL that the client used to initiate the
request on the portal.

Later.

Faizan


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer