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).
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
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
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 appl
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 portle
5 matches
Mail list logo
