IPC sample project ala JSR 286

[samuel.michelot]

Hello !

I am looking for a sample project for the InterPortlet Communication.
I read this article :
http://java.sun.com/developer/technicalArticles/J2EE/sdk_portletcontainer2/#Sample_Application:Events
And the events looks simple.

But after, I checked out the HelloWorldIPC project sample, but I am a little confused. I though that the JSR 286 had simplified portlet communication, and portlets was independant of the portlet container.
But in this sample project, there is a need of an .SAR, with a Listener mbean. Looks very specific to JBoss Portal, no ?

Is the HelloWorldIPC project sample is the way to go to implement IPC compliant with JSR 286 ?

Thanks,

Samuel

[samuel.michelot]

Ok, so it's look like IPC was the JBoss way to communicate before JSR 286.
Cf. : http://docs.jboss.org/jbportal/v2.2/reference-guide/en/html/ipc.html

I tried to deploy the SUN Sample Application of portlet event (JSR 286) from
http://java.sun.com/developer/technicalArticles/J2EE/sdk_portletcontainer2/#Sample_Application:Events
But it doesn't work on JBoss

Is there a sample project for JBoss ?

[theute]

Look at the shopping cart and catalog portlets. You can even play with them here:
http://portal.demo.jboss.com/portal/default/Samples

That said the Sun examples should work if they follow the spec (Which i guess they do).

[samuel.michelot]

Thanks for your answer Thomas !

The shopping cart and catalog portlets looks great for my needs, but I can't find them here :
http://www.jboss.org/portletswap/portlet_main.html
Where can I download the source code ?


The sun examples are recognized by JBoss Portal, but when I display them, I have this Exception:

11:55:32,743 ERROR [[jsp]] "Servlet.service()" pour la servlet jsp a lancé une exception
org.apache.jasper.JasperException: L'uri absolue: http://java.sun.com/portlet ne peut être résolu dans le fichier web.xml ou dans les fichiers jar déployés avec cette application
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)

It's maybe nothing, but I prefere to start with the shopping cart, once I'll get the source code.

[theute]

You can find the code for those examples here:
https://svn.jboss.org/repos/portal/modules/portlet/tags/JBP_PORTLET_2_0_5/samples/src/main/java/org/jboss/portal/portlet/samples/shoppingcart/

Not sure about the other error, the TLD should have been included. What version of JBoss Portal are you running ?

[samuel.michelot]

Thanks for the link !

I am running Portal 2.7.2 (the last one).

[claprun]

The wiki is your friend (at least, when it's not broken as it seems the link to the FAQ is currently broken):
http://www.jboss.org/community/docs/DOC-13228

[samuel.michelot]

Thanks everybody for your help.
I manage to create two little portlets communicating ;-)
The next step is to migrate a seam/richfaces application in several portlets view.

[antoine_h]

hi,
you have interesting things about IPC there :
http://mus.purplecloud.net/portlets/thesis/ipc.php
the Michelle Osmond site provides nice explaination (both IPC by events and by messages), and provides an implementation for IPC by message.
which is the one I use, to have multiple portlets share some info (the menu and the operations portlets, etc...).
hope it helps,

[theute]

Antoine,

is there still value added by this approach vs the JSR-286 approach ?

[saarkotti]

hi samuel,

can you please send me the source of portlet IPC without seam.

thanks

[antoine_h]

Hello,

Thomas Heute wrote:

Antoine,

is there still value added by this approach vs the JSR-286 approach ?

sorry, long time after,... I've just seen that there was this question...

It is less value added than before JSR-286... of course.

but still interesting, for the nice explanation of the principles.

and for an implementation based on messaging, which have it's advantages in some specific use cases.

the main draw back is to make portlets that are not full compliant with the JSR.

one use case that can requiere some real messaging is when the message must be received by the portlet.

the JSR states it limit like this (page 109) :

"Portlet events are not a replacement for reliable messaging (see other JavaEE APIs, like
Java Message Service, JMS, for providing reliable messaging). Portlet events are not
guaranteed to be delivered and thus the portlet should always work in a meaningful
manner even if some or all events are not being delivered."

so... it is better if it can be done with the JSR way... but in case of unavoidable need of messaging... this approach is a nice architecture and code base.