• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Portel to portel communication

 
Mrudula Jana
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
can portels communicate between each other. if yes how
how do u authenticate a user and direct him to a perticular prtel or porlet depending on his access rights
 
Jessica Sant
Sheriff
Posts: 4313
Android IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Inter Portlet Communication is not covered by the JSR-168 spec, so the only way you can accomplish this is if your particular vendor designed and implemented it.

I know JBoss Portal is working on this, I don't which other vendors are.

Here's this --> JBoss Portal discusses Inter Portlet Communication.

Looks like Advanced Interportlet Commmuncation will be part of the 2.2 release.
 
leevisa asinveel
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In Websphere Portal 5.0 PORTLET messaging is available in 2 flavours

1. Message Broadcast 2. Portlet to Portlet Messaging

thanks
 
K Riaz
Ranch Hand
Posts: 375
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jessica Sant:
Inter Portlet Communication is not covered by the JSR-168 spec,


Actually, it is, although it is not done so explicitly. It can be done by setting session variables with the APPLICATION_SCOPE flag, which makes data available to other portlets in the same portal. By default, all session variables are set with a PORTLET_SCOPE flag, so by writing something like session.setAttribute("key", "value") means that you can access "value" only within the portlet of which it is defined in. But if you add write session.setAttribute("key", "value", APPLICATION_SCOPE), you can retrieve it from another portlet, which is useful for passing data between portlets.
 
Stefan Zoerner
Author
Ranch Hand
Posts: 121
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please note that this form of inter-portlet communication (session attributes) is only possible for portlets within the same portlet application (= webapp). You can't overcome app boundaries and share information with arbitrary portlets within your portal like that.

Another restriction is the life cycle: You may only set an attribute within a processAction method in one portlet and get it within render phase of others (because sequence of render calls is undefined).

Greetings, Stefan
 
pooja jain
greenhorn
Ranch Hand
Posts: 213
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Stefan Zoerner:
Please note that this form of inter-portlet communication (session attributes) is only possible for portlets within the same portlet application (= webapp). You can't overcome app boundaries and share information with arbitrary portlets within your portal like that.


Greetings, Stefan


if they are in different war (application) then use a common database or xml etc to communicate.


Another restriction is the life cycle: You may only set an attribute within a processAction method in one portlet and get it within render phase of others (because sequence of render calls is undefined).


what do you mean by this? :roll:
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic