Struts Portlet - inter Portlet communication

Hi
How to make inter Portlet communication in Struts portlets?
Thanks
Subin

A quick google search brought back this:
http://download.oracle.com/docs/cd/B15904_01/portal.1012/b14134/pdg_java.htm

Similar Messages

Turning application into portlet: inter-portlet comunications

Hi there,
I am turning my application into a portlet. I need to add some navigation parameters to the portlet to communicate with the page on which it resides and with other portlets on that page.
Selecting Create navigation parameters for events during the creation of Create Portlet Entry I can create navigation parameters for any events exposed by the page.
I didn't get how to add these events to the page. How can I achieve that?
I am working with Jdev 11g.
Thanks,
Al

Try posting the question on the WebCenter forum.
Basic reading here: http://download.oracle.com/docs/cd/E12839_01/webcenter.1111/e10148/jpsdg_pages.htm#CHDJABHD

Inter portlet Communication - Events and Parameters

Hi,
I just tried a sample inter portlet communication using events and parameters.
I used the below code to enable inter portlet communication between two struts portlet.
UrlUtils.constructLink etc
The above works fine. Instead of link, I would like to use a form button to fire the event.
Is there any way of using button to fire the event.
Another thing I noticed is that when the event is fired the page gets refreshed.
How to enable inter portlet communication without the portal page refreshing.
Many Thanks in advance!!!!!!!!
-Chid

Hi Natu,
To start: read the documentation: http://download.oracle.com/docs/cd/B32110_01/webcenter.1013/b31074/jpsdg_java_adv.htm#CHDHDCGI
Then, you need to make sure the portlets can operate independently. That means: the locations portlet should be able to run without the incidents portlet.
What you should try to achieve is create a locations jspx that uses a page parameter with the incident number as input. The page can then be populated based on that id.
The key thing here is: input portlet variables are available as page parameters.
Then, you need to add some functionality to the incidents portlet to submit the selected incident number to the outside world. You can do this using some backing bean code. Example:
    public void transmitEvent(ActionEvent actionEvent) {
        FacesContext facesContext = FacesContext.getCurrentInstance();
        ExternalContext externalContext = facesContext.getExternalContext();
        Object response = externalContext.getResponse();
        if (response instanceof javax.portlet.ActionResponse) {
            ActionResponse actionResponse = (ActionResponse)response;
            // setting the portlet OUT parameter
            String outResult = "my output";
            actionResponse.setRenderParameter("outParam", outResult);
       } else {
            // not in portlet environment
    }Hope this brings you further.
Jeroen van Veldhuizen

Inter portlet communication in SP4

Can any one tell me in step by step process with sample code to do inter portlet communication in SP4
Here i have 2 portlets
Portlet A and portlet B
Portlet A has 2 hyperlinks link1 and link2
When i click link1 or link2 in portlet A, i am passing a parameter,depends on the paramater i have to display some details in portlet B
Thanks
maria
[email protected]
Message was edited by marianair at Feb 10, 2005 2:27 AM

hi,
implement both portlets as page flow portlets. For both the links in portlet A, implement an action that generates an event and fires thisone. Then let the pageflow in portlet A show whatever content is appropriate, eg. the same as before the link.
Portlet B cathces this event and in the connected pageflow action does whatever it needs to do and redirects to the appripriate JSP.
Just remeber that you probably needs to use a custom event here.
For details on IPC and events, see doc:
http://e-docs.bea.com/workshop/docs81/doc/en/portal/howdoi/howInterPortletComm_wkshp.html
As an alternative you can use the SP3 mechanism, I find thisone somewhat more cumbersome and messy.
http://e-docs.bea.com/workshop/docs81/doc/en/portal/howdoi/howInterPortletComm.html
Feel free to post follow-ups if you get stuck.
- Anders M.

Event interface for inter-portlet communication

In which jar file can I find the com.bea.netuix.events.Event interface?
I wish to offer some support for inter-portlet communication while running inside a 8.1sp4 weblogic portal server.
Firstly, there is almost no documentation for working with Custom/Generic Events and definitely none for working with "Invoke a java portlet method"
Found out by decompiling the code that you can do the following:
add methodName(HttpServletRequest, HttpServletResponse, Event) to you backing file, or
add methodName(ActionRequest, ActionResponse, Event) to your java portlet
In both cases, I need find the jar file containing the "Event" interface. Have found most of the other classes in netuix_servlet.jar
Would also appreciate any further info on when the above methods actually get called with respect to the "processAction" and "processRender" methods for jsr168 portlets...

Found the answer after a pretty manual search - its located inside:
BEA_HOME/weblogic81/portal/lib/netuix/system/netuix_system.jar
All other interfaces being inside the WEB-INF/lib/netuix_servlet.jar, this one class from this package has been packed into a jar at the system classpath level!!
Had to manually look at the classpath in startWeblogic.cmd and then open up every jar file, follow dependent jar files via the manifest.mf etc...

Inter Portlet communication without using workshop

Hi
Does any one have any luck trying to do inter portlet communication without using weblogic workshop IDE?

Hi Curt,
WLP's eventing system is designed such that portlet's don't have to care
whether the source/destination is local or remote. If you have a portlet
that fires/consumes events, when you create a proxy portlet on a
consumer, the portlet on the producer will be able to fire and receive
events without any changes to it. In this scenario, the proxy portlets
work with the WLP's event runtime to collect and dispatch events on
behalf of portlets on the producer. Going forward, WSRP 2.0 and
JSR168-next's eventing models will be mapped to the same WLP event runtime.
Subbu
Curt Smith wrote:
Thanks Subbu for your enlightenment here and in this group!!
You mentioned my next quest, WSRP'ifying my portlet & IPC system.
Can you suggest an WSRP example anywhere on the net or in bea?
I guessing that suitability of IPC is also a function of whether the portlets are the remote portlets or the local portlets.
Might a non-Bea IPC choice be usable within the local portlets, which are WSRP clients to stand alone remote portlets?
I can imagine now that you mention it that the remote WRSP producer portlets can't use just any IPC facility and the events be pushed inband to the consumer portal...
tnx curt

Inter portlet communication using a float portlet

Hi,
I am trying to achieve inter portlet communication between a jsp portlet and a pageflow portlet.
The jsp portlet will open up as a pop up window or as a float portlet.
I am using BEA Weblogic 8.1 SP5.
Has any body tried this IPC when the jsp portlet is a float portlet?
If there is any documentation available for the same?
Thanks,
Shreesh

Hi,
Thanks for the reply.
In the search.jsp I am adding an action associated with a form bean, and passing the search string to the form, which will pass the request to the action method. This is the code snippet:
* @jpf:action
* @jpf:forward name="success" path="search.jsp"
protected Forward searchcriteria(SearchcriteriaForm form)
String searchString = form.getString();
try {
URL url = new URL("http://localhost/demo_search.asp");
HttpURLConnection http = (HttpURLConnection) url.openConnection();
http.setRequestMethod("POST");
PrintStream out=new PrintStream(http.getOutputStream());
out.println("searchParam=searchstring");
out.flush();
out.close();
BufferedReader reader=new BufferedReader(new InputStreamReader(http.getInputStream()));
reader.readLine();
String patternStr = "pattern";
Pattern pattern = Pattern.compile(patternStr);
Matcher matcher = pattern.matcher("<a href");
// Retrieve all lines that match pattern
String line = null;
while ((line = reader.readLine()) != null)
out.println("***"+line+"***");
matcher.reset(line);
if (matcher.find()) {
// line matches the pattern
} catch(Exception e)
e.printStackTrace();
return new Forward("success");
* FormData get and set methods may be overwritten by the Form Bean editor.
public static class SearchcriteriaForm extends FormData
private String string;
public void setString(String string)
this.string = string;
public String getString()
return this.string;
The question is what should be the return forward for the search coz, the result should be displayed in a seperate portlet. Also, how do I capture only the result in the result.jsp.
I would appreciate if you help me,
Thanks in Advance,
Sailatha

How to perform inter-portlet communication in alui6.1.

I want to perform perform inter-portlet communication in alui6.1. I don't have any clue to how to do it.
Can anyone help me.

Frankly, I did it using jQuery. When you have just two portlests on page, you can hardcode object id of second portlet in a code (not so nice, but very fast to see results). Otherwise you can use portlet settings to stay more environment independent.
In brief, in first portlet via ajax I request for data, using css selector jQuery, paste content to div in second portlet.

How we develop inter-portlet communication in plumtree portal using IDK

1)How we will develop inter-portlet communication in plumtree portal using IDK .
is it possiable using Master Detail Pattern? or any other alternate way.
Regards
Dheeraj Sai

This can be done by developing Adaptive Portlets:
http://edocs.bea.com/alui/devdoc/docs60/Portlets/Adaptive_Portlets/PlumtreeDevDoc_Integration_Portlets_Adaptive_Intro.htm

Inter-Portlet Communication Best Practices

Here's the situation:
There are 2 Portlets on a page; a Search Portlet and a List Portlet. When a user selects search criteria in the Search Portlet and presses the Submit button the items displayed in the List Portlet must be updated to reflect the search criteria that was entered.
My approach to implementing this:
When the user presses the Submit button the Search Portlet code will take the information entered by the user and create a searchObj. This searchObj will be attached to the Http Session object. When the Search Portlet is rendered again in the browser it will recognize (via a hidden HTML attribute) that it needs to inform the List Portlet that there is new search criteria. The browser will then generate a Portal Event that will cause the List Portlet to refresh its list based on the searchObj it finds attached to the Http Session object.
Question 1:
Assuming this is a reasonable approach how do I get the Search Portlet to generate an event based on a HTML hidden field at the time the Portlet is rendered?
Question 2:
Is there a better way to implement this type of functionality? Essentially the problem is that one Portlet needs to process some data and once it's done it needs to notify other Portlets. What are the best practices for this type of situation?
Any suggestions are welcome.

Hi,
As per the JSR 168 Specification, we follow PortletSession with APPLICATION_SCOPE for implementing IPC ( inter portlet communication ).
Here are the steps for IPC:-
1. When you press submit from search portlet then fetch the search string value into the processAction method of the search portlet.
2. Put the search string value in the portlet session with APPLICATION_SCOPE.
3. When you press submit of search portlet, doView() method of both the portlets
( Search and List ) will be called.
4. in the doView() method of List portlet retrieve the search string from the portlet session and call the business logic based on the search criteria.
5. Put the search result into bean or as per your framework design.
6. Iterate the bean value on to your List portlet rendering jsp.
Note:-Here it is assumed that both the portlets are in the same ear/war.
The coming JSR 286 specification, allows a portlet to send and receive events and perform state changes or send further events as result of processing an event.
In JSR 286, we would be having one more request and reponse called EventRequest and EventResponse.
Comments and suggestions are welcome for IPC.
Thanks
<Neeraj Sidhaye/>
Try_Catch_Finally AT YAHOO DOT COM
http://ExtremePortal.blog.co.uk

Inter Portlet Communication for JSR 168 Portlets

Hi,
I want to invoke one JSR168 Portlet from another and also pass parameters between the two.I did the same using Events for Oracle Portlets.
I would like to know how to do the same when I build JSR 168 Portlets.
Also Pls let me know where I can get documentation which describes all the possible options that I can try out on JSR168 Portlets
Regards
Yash

Hello Yash,
The current version of the specifications does not support Parameter and Events that allow you to create portlet 2 portlet communication using OracleAS Portal framework.
If the reusability of the parameter is not a major requirement of your application you can simply use URL parameters and this will authorize you implement that.
Regards
Tugdual Grall

Remote Inter Portlet Communication for JSR 168

Hi All,
We are stuck in a big problem using JSR 168 as remote portlets. We will be relieved if someone can suggest few ideas on this. I will provide the scenario which we are trying now.
We have two portlets namely portlet A and portlet B which are Java(JSR 168) type portlets. These two portlets are offered as remote and they reside in the producer application. We have consumed these two portlets in our consumer application.
The portlet A is triggering an event and portlet B is listening to the event triggered by portlet A. Currently we are trying to implement this functionality using Ajax. We tried to use customEventUrl tag in our jsp belonging to portlet A and we finally figured out that customEventUrl will not work in Remote portlets. We are not sure as how to pass the information from remote portlet A to remote portlet B. Please let us know your thoughts about this as whether the implementation is really possible when using Remote portlets.
IMPORTANT NOTE: The event handling and the configuration code that we have made in the above scenario is working perfectly for non-remote java portlets. The problem is occurring only when we consume them in the consumer application.
Thanks
Vijay

Hello Ashwin,
What version of WebLogic Portal are you using? And is this the same for both the consumer and producer?
If you are using WLP 10.3.2 I would highly recommend using JSR286 portlets (the next version of the Java Portlet (JSR168) specification) and the JSR286-standard eventing. The JSR286 eventing model is actually much cleaner and easier to understand than the WLP-proprietary support for events in JSR168 portlets.
However, if you are using a version of WLP prior to 10.3.2 and can't upgrade, JSR168-style events are your only choice. I can give you examples, but they all look very similar to the examples in the online documentation.
When events work between portlets locally, but not over WSRP, the usual problems are:
- There is one or more of "onlyIfDisplayed", "sourceDefinitionLabels" or "sourceInstanceLabels" attributes declared on the handle*Event element in the .portlet file. These attributes restrict when the portlet should receive an event, and they usually don't work the way you think when running over WSRP. It is best to not use these attributes for portlets which are going to be used over WSRP.
- A payload is being sent with the event which is not actually serializable. If serialization of the event payload (which is required for versions of WLP prior to 10.3.2 for WSRP) fails, the event will not be delivered to the portlet.
- The producer may be configured to not accept events. Check your producer's WEB-INF/wsrp-producer-config.xml file; the "service-config" element should either not have an "offer-extensions" attribute, or this attribute's value should be "true".
- The events may be getting sent during a portlet lifecycle other than processAction or handleEvent. There is no way for WSRP to handle events which have been sent during preRender or render, so it simply doesn't work.
- In the case of JSR168 portlets, if you have a backing file on the portlet (in addition to the portlet implementation as well), that may not work in some circumstances over WSRP. It is best to have the event handlers be in the portlet implementation class and avoid the use of backing files for JSR168 portlets.
If none of those things help you, my suggestion would be to post a sample .portlet file for one of the portlets that is supposed to be receiving the event, as well as the method signature in that portlet's implementation class that is supposed to be receiving the event, and the code which is sending the event that is supposed to be received.
Kevin

JSR 168 best practice for saving inter-portlet state

The portlet specification doesn't yet cover inter-portlet communication. Until
it does, what is the best practice for saveing state so that multiple portlets
can use the same data?

The portlet session is layered on top of the HTTP session except for
attribute scoping. So, all portlets in a webapp share the same
HTTP/portlet session for a given client.
All APPLICATION_SCOPEd portlet session attributes are automatically
available to other portlets. With PORTLET_SCOPEd attributes, portlet
containers namespace attribute names, so it would be hard to get
attributes by name (but still possible).
Subbu
Chris Jennings said the following on 10/14/2003 09:17 AM:
If I set an attribute in a PortletSession, though, it isn't visible form another
PortletSession... right? Please tell me that's wrong ;-) If that's right, how
can I have portlet B get to something set by portlet A?
Subbu Allamaraju <[email protected]> wrote:
Chris,
For sharing transient state, the only possible mechanism in V1.0 is to
use sessions.
Subbu

Inter-portlet (JSR286) in liferay portal

i had created two portlets using ADF and i can consume them in WebCenter Portal apps. Nothing has to do in the portal side as webcenter auto-wire the portlets. The question is how i can consume the portlets in liferay? is there any step required in the liferay portal site to 'wire' the portlets so that they can communicate with each other? or just like drag and drop in webcenter? I developed the portlets using the guide here: http://yonaweb.be/inter_portlet_communication_jsr_286_and_webcenter_11g_ps3

Wiring portlets together in liferay not dependend on the portlet. Because your portlets are standard based, liferay doesn't care if they are ADF portlets, JSP portlets or portlets build with other technology.
Information on how to do this in liferay should be found in the documentation of liferay: http://www.liferay.com/community/wiki/-/wiki/Main/Inter-portlet+communication
Just a question... Did you had any issues with consuming the portlets in liferay. I have tried it in the past and had lots of issues with libraries and so on. Especially because ADF uses a lot of javascript and I had a hard time configuring it properly with liferay...

Need an example of Portlet to Portlet Communication

We need a very simple example of Portlet to Portlet communication in Plumtree 5.01. We need to understand the concept of passing a variable from one Portlet to another.
A good example would be clicking on a link in one Portlet and displaying a parameter from that first Portlet in the other Portlet.
Thanks in advance for your help.
Todd Bocik

There are several ways to do this. The way that I like best is using a User Setting.
1) Pick a name for your setting.
2) Enter the name of the setting in the web service configuration for the two (or more) web services that want to share the setting. Any portlet that needs to "see" the setting must have it specified its web service configuration.
3) When a user clicks on a link in one of your portlets, set the setting: IPortletResponse.SetSettingValue(SettingType.User, "settingName", "settingValue")
4) In another portlet, get the setting and display it: IPortetRequest.GetSettingValue(SettingType.User, "settingName")
The nice thing about doing it this way is that even if your portlets are set to be cached "forever," they will change whenever you change the user setting (assuming you followed step 2).
Hope this helps,
Chris Bucchere
[email protected]
Bucchere Development Group
http://www.bucchere.com| 415.516.3941

Struts Portlet - inter Portlet communication

Similar Messages

Maybe you are looking for