Hello, I would use the PortletSession approach - it will result in portlets that are more portable (and probably, simpler, easier to maintain, less prone to changes in the underlying inter-portlet-communication API's - which are going to be brand new, etc.).
Another design aspect for you to consider is this - Having portlet 1 depend on portlet 2 via inter-portlet communication API's can easily result in portlet implementations that break if one or more of the 'communicating' portlets is not available (or throws an exception). Cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3903537#3903537 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3903537 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
