It is true that inter portlet communication is not supported in the JSR168 spec, but there are ways to exchange data between portlets in a less proprietary manner. The easiest way is to use the shared session scope which is available to all portlets in the same portlet application (same war file). So if you have portlets that need to communicate, put them in the same application (which they probably should anyway, since they obviously have some relation). Without having tried it, you might also be able to build something on top of a distributed caching/JMS/database system.
The Portlet 2.0 (JSR 286) specification includes support for inter portlet communication. The main advantage using Struts 2 (or any web framework that support portlets) is that you get a framework on top of the portlet API. I am not aware of any framework support for the IBM Portlet API (besides a custom struts framework that really wasn't any good the last time I tried it), so it would be like programming servlets in a web application. But still, if you know that inter portlet communication will be important for your application, and none of the proposed solutions are good enough for you to use, I guess you don't have a choice but lock yourself to a vendor. Nils-H On 10/24/07, Guillaume Bilodeau <[EMAIL PROTECTED]> wrote: > > Ok thanks, that's good to know. > > There is a strong recommendation coming from a colleague to use the IBM > Portlet API on WebSphere Portal, particularly because of its support for > inter-portlet communication - from what I'm told, this isn't supported by > the standard JSR-168 API. I'm not too keen on using proprietary extensions, > unless it does provide a significant advantage. Would Struts2 provide the > necessary mechanism to accomplish this communication? What are the > advantages of using Struts2 on top of the standard portlet API or the IBM > API? > > Thanks again, > GB > > > Nils-Helge Garli wrote: > > > > The portlet support in the next 2.0.x and 2.1.x has been improved a > > lot. You can browse the changelogs and remaining issues in the issue > > tracker. It does not include Ajax support, but you can add that > > yourself. I know of several projects that are using it in production > > already. > > > > Nils-H > > > > On 10/23/07, Guillaume Bilodeau <[EMAIL PROTECTED]> wrote: > >> > >> We will soon start a portal project and we're evaluating the technologies > >> available to us. Is Struts2 support for portlets ready for primetime, or > >> should we use something else until it's stabilized? > >> > >> Cheers, > >> GB > >> > >> > >> Nils-Helge Garli wrote: > >> > > >> > Hi! > >> > > >> > If you're thinking of the struts2-portlet application, you need to > >> > install it into a portlet container to test it. However, ajax is not > >> > yet built into the portlet framework. > >> > > >> > Nils-H > >> > > >> > On 10/18/07, Giovanni Azua <[EMAIL PROTECTED]> wrote: > >> >> hi all, > >> >> > >> >> I managed to see the examples in the portlet webapp demo (there is no > >> >> index page) but I didn't see any portlet anywhere ... so I am curious > >> as > >> >> if to there is at all an AJAX portlet control delivered with Struts 2? > >> >> > >> >> Lack of portlets in S2 and AJAxification of displaytag would be the > >> two > >> >> main reasons for me to use ajaxtags in addition to S2. > >> >> Any alternatives to ajaxtags? > >> >> > >> >> regards, > >> >> Giovanni > >> >> > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> >> For additional commands, e-mail: [EMAIL PROTECTED] > >> >> > >> >> > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > For additional commands, e-mail: [EMAIL PROTECTED] > >> > > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/about-Struts-2.0.9-portlet-example-...-tf4646784.html#a13356144 > >> Sent from the Struts - User mailing list archive at Nabble.com. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/about-Struts-2.0.9-portlet-example-...-tf4646784.html#a13394151 > Sent from the Struts - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
