WebSphere related

upcoming Intelij Idea (Demetra) release

It seems Idea will have a lot of features I wanted a long time ago.

posted by s-chro @ 1:02 AM 0 comments

Portlet communication

Ok, I have a few portlets(IBM or JSR168) on WebSphere Portal Server (5.0 or 5.1) and want to talk to each other. How can I develop messaging between all of them? I don't need a big infrastructure, just send a string, or better, a small objects from one portlet to another. Of course, I am too lazy to produce a complicated solution. Here is variants:

1. If I use only JSR 168 - I can put an object into javax.portlet.PortletSession
session.setAttribute("attribute", "attr value", PortletSession.APPLICATION_SCOPE);
The portlets must be packaged in the same WAR.
2. I can use click-to-action and wiring. It does not feet to all situation, but looks funny. This technology is restricted by IBM portlets.For enabling C2A I should put custom c2a tag on JSP page. Also I need to provide some libraries,WSDL and so on.
3. I know that session id for authorized user is just the same on all WebSphere applications.I create persistance cache and provide access to it from any point in portal. It may be a PortletService, SessionBean. The main idea is to get an access to hashtable where keys are session id:
InititalContext ctx = new IntitalContext();
ctx.lookup(...)...;
hashmap.put(getRequestedSessionId(),"my session persistance object");


Here is some articles :
Caching data in JSR 168 portlets with WebSphere Portal V5.1
Portlet-to-portlet communication between JSR 168 portlets on public pages
Sharing information between IBM portlets and JSR 168 portlets with WebSphere Portal V5.1

posted by s-chro @ 10:51 PM 0 comments