Re: [Webwork-devel] JSR 162: Portlet API

[Rickard <ri...@mi...>]

Philipp Meier wrote:

>>>Portlets rely on the portlet container infrastructure accessible via the 
>>>Portlet API for functions like access to user profile information for 
>>>the current user,
>>
>>WebWork Action *Aware interfaces.
>>
> 
> Nope, the aware interfaces won't give you a persistent storage of the
> users profile. 


What I meant was that the *Aware interface design allows you to plug 
these in easily. Although I'm not sure that's the best way to do that 
really.

>>>participation in the portal window 
>>>and action event model, access to web client information, 
>>>
>>WebWork Action *Aware interfaces.
> 
> Rickard, I think you got this one wrong. I'm not sure but I think by
> accessing the "window object" the spec will give you a way to "roll-up",
> close and rearrange the portlets on the page (like my.netscape.com
> does). The event model will supplement this, I suppose by providing
> listeners for these "window"-events.


Ok, I see, yes that is different.


>>>and a standard way of storing and retrieving 
>>>per-user/per-instance data persistently.
>>>
>>SessionAware.setSession().
>>
> 
> Persistently! See above.


Depends on your implementation of session ;-)


> Rickard, I don't see much benefits in this JSR either, but webwork
> alone won't do the job. 


I agree, it won't. But to a large extent it does.

> Correct me if I'm wrong, it was you who did some
> portlet developing a xpedio IIRC. 


I developed portal stuff using WebWork, yes.

> I really love webwork and I don't like
> this JSR but webwork is not the golden hammer.

I agree.

/Rickard

-- 
Rickard Öberg