Ok, Stefan points to much more fundamental flaws... Thanks Stefan for the clarification
--- Tim Robertson <[EMAIL PROTECTED]> wrote: > That sounds interesting for 2.0... > > Rememeber that I am new to Portlets, but I think: > The major downside that I can picture, is that the > Portlets become aware that they are working on > shared > data - thus they are no longer living in their own > little world. Using my simple example, the Cities > portlet will need to check a session variable on > each > view request to check if it's data (the country) has > changed. This could quickly get out of control, as > there may be another event that it needs to check > on, > and another as the system grows - thus a change to > one > little portlet, may result in code changes necessary > all over the place. > > I wonder if Spring offer anything out the box for > this? Perhaps some fAOP interceptors that let you > fire update events and then the wiring of the > interaction is extracted from the portlet > implementation - anyone seen this? I suspect it to > not be too hard to acheive. > > Tim > > > > --- Bruno Farache <[EMAIL PROTECTED]> wrote: > > > Stefan, I've read that Portlet 2.0 will cover > > portlet events, do you have > > any idea how is it going to work? > > What are the disadvantages of using session to > > accomplish portlet > > communication? > > > > On 9/23/06, Stefan Zoerner <[EMAIL PROTECTED]> > > wrote: > > > > > > Hi Tim! > > > > > > Unfortunately, the Portlet 1.0 specification > does > > not include events or > > > messages between two portlets. Some vendors > offer > > proprietary solutions > > > here. > > > > > > If the portlets are within the same portlet > > application, you have the > > > option to share information between them via the > > portlet session. The > > > latter has two scopes, one of them (application > > scope) is per user and > > > portlet application. > > > > > > It is possible to add/update something in the > > session with this scope > > > during the processAction of the first portlet, > and > > read/react with the > > > second portlet within the render phase. > > > > > > This proceeding has several disadvantages, but > in > > your case, it may > > > work, and it is standard compliant (i.e. your > > portlets will run and > > > interact on all specification conformant portal > > servers). > > > > > > I hope this helps, > > > Stefan > > > > > > > > > > > > > > > > > > ___________________________________________________________ > > All new Yahoo! Mail "The new Interface is stunning > in its simplicity and ease of use." - PC Magazine > http://uk.docs.yahoo.com/nowyoucan.html > ___________________________________________________________ The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
