struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Jouravlev <jmi...@gmail.com>
Subject Re: Struts Dialogs (was HTTP method for action-mappings)
Date Tue, 05 Jul 2005 21:56:52 GMT
I want to add a little to my previous email. Let's look at Portlet spec.

"A portlet fragment can be aggregated with other fragments to form a
complete document. The content of a portlet is normally aggregated
with the content of other portlets to form the portal page."

Yup, can do that.

"The lifecycle of a portlet is managed by the portlet container."

The lifecycle of JSP control, which can be developed with Struts
Dialogs, is managed by whatever framework a control is based on, or by
the control itself.

"Web clients interact with portlets via a request/response paradigm
implemented by the portal."

In case of JSP components, web clients interact with controls via a
request/response paradigm implemented by a control.

"Normally, users interact with content produced by portlets, for
example by following links or submitting forms, resulting in portlet
actions being received by the portal, which are forwarded by it to the
portlets targeted by the user's interactions." ... "A portlet
container receives requests from the portal to execute requests on the
portlets hosted by it."

JSP controls receive request directly, not through a portal or portal
container or master page or whatever. Master page does not have to
interact with JSP controls, and controls do not have to interact with
master page. In simple cases, they do not even know about each other.

"Portlets are not directly bound to a URL" -- JSP components are
directly bound to a URL.
"Web clients interact with portlets through a portal system" -- Web
clients interact with JSP components directly
"Portlets have a more refined request handling, action requests and
render requests" -- Whatever that means, but JSP components have very
refined request handling, based on two-phase request processing.
"Portlets have predefined portlet modes and window states that
indicate the function the portlet is performing and the amount of real
state in the portal page" -- JSP components has three modes:
initialization, input and rendering. Additional modes can be defined
per component.
"Portlets can exist many times in a portal page" -- This is what my
stuff cannot do, because each type of Struts form bean has only one
instance per session.
"Portlets have access to user profile information" -- JSP controls
have no notion of user profile. But this API can be designed ;)
Portlets have URL rewriting functions for creating hyperlinks within
their content, which allow portal server agnostic creation of links
and actions in page fragments" -- With JSP controls, master page does
not care about the links a control has.
"Portlets can store transient data in the portlet session in two
different scopes: the application-wide scope and the portlet private
scope" -- Yeah, why not. Just create a key specific to a JSP control.
"A portlet container provides persistent storage for portlet
preferences." -- Don't have that, I admit. But then again, one can get
only that much from API consisting of single <jsp:include>.

Michael.

--
Dialogs for Struts
http://struts.sourceforge.net/strutsdialogs

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message