hi konstantin,
IMHO portlets are going to get more and more important. if you look
at the new portlets 2.0 spec you will see AJAX defined to reload portlet
content, an event mechanism to notify one or more portlets, a new inter
portlet communication protocol, central session handling aso. With this
spec (still in public review) it will be possible to write portals that behave
like "web 2.0" sites but in fact are composed of different web apps.
Portlets serve as THE integration API to combine different web applications
into a single one. A scenario may be in a big company that already uses 2
(or several) web applications to cover their processes (written in different frameworks). They may conclude that the processes could by better
supported if the users had parts of both applications configured into one
workbench to see dependencies and impacts immediatly. Thats where
portlets 2.0 comes into play :)
so i think an integration of Tapestry 5 with portlet 2.0 is necessary.... )
g,
kris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IMHO portlets are going to get more and more important. if you look
at the new portlets 2.0 spec you will see AJAX defined to reload portlet
content, an event mechanism to notify one or more portlets, a new inter
portlet communication protocol, central session handling aso. With this
spec (still in public review) it will be possible to write portals that behave
like "web 2.0" sites but in fact are composed of different web apps.
Portlets serve as THE integration API to combine different web applications
into a single one. A scenario may be in a big company that already uses 2
(or several) web applications to cover their processes (written in different frameworks). They may conclude that the processes could by better
supported if the users had parts of both applications configured into one
workbench to see dependencies and impacts immediatly. Thats where
portlets 2.0 comes into play :)
so i think an integration of Tapestry 5 with portlet 2.0 is necessary.... )
g,
kris
An: Tapestry users <users@tapestry.apache.org>
Von: Konstantin Ignatyev <[EMAIL PROTECTED]>
Datum: 29.12.2006 10:15PM
Thema: Re: JSR-168/268 support and Tapestry 5.0
does it make sense at all to support portals? Does
people still use and develop portals?
I mean that with the AJAX proliferation it looks like
"Clientlets" make much more sense than Portlets and
therefore Portals in a sense of JSR-168 are headed to
oblivion.
What is the peoples' experience and opinion?
--- Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> That should be "action" requests and "render"
> requests.
>
> The fact that servlet Tapestry 5 differentiates
> between the two will make it
> easier, or at least make it more consistent, for
> portlet Tapestry 5.
>
> On 12/29/06, Jan Vissers <[EMAIL PROTECTED]>
> wrote:
> >
>
Konstantin Ignatyev
PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000
Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
