Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
Question about IPC and future roadmap
Hi,
I'm trying to develop some fairly complex application on Liferay (actually, it's an attempt to port an existing apps), but I'm getting a roadblock to solve inter-portlet communication problems.
In our app, we have fairly complex communication between modules (and blocks on the web pages). We tried to make them into portlets, and distribute the development work load to a team of 10 developers. We want to design such that each portlet can have a fairly "standard" interface for communicating with each other. Each developer can package his/her portlet as a war package and deploy on Liferay, and we can create the application by putting the related portlets into an application page, and have the portlets communicate with each other.
In prototyping, we found that IPC in Liferay (or the solutions suggested here) is very limited, and complicated to manage. And I found that it's hard to take advantage of the cool UI provided by Liferay. Unless we want to package all portlets in a gigantic war package, it's almost impossible to do.
Just want to ask, what's the future road map for IPC in Liferay? Any plan to make it "more useable"?
I'm trying to develop some fairly complex application on Liferay (actually, it's an attempt to port an existing apps), but I'm getting a roadblock to solve inter-portlet communication problems.
In our app, we have fairly complex communication between modules (and blocks on the web pages). We tried to make them into portlets, and distribute the development work load to a team of 10 developers. We want to design such that each portlet can have a fairly "standard" interface for communicating with each other. Each developer can package his/her portlet as a war package and deploy on Liferay, and we can create the application by putting the related portlets into an application page, and have the portlets communicate with each other.
In prototyping, we found that IPC in Liferay (or the solutions suggested here) is very limited, and complicated to manage. And I found that it's hard to take advantage of the cool UI provided by Liferay. Unless we want to package all portlets in a gigantic war package, it's almost impossible to do.
Just want to ask, what's the future road map for IPC in Liferay? Any plan to make it "more useable"?
IPC is one of the biggest disadvantages of the portlet 1.0 specs. Take a look at the portlet 2.0 specs at the jcr 286. It seems that portlet 2.0 will be implemented in liferay 5
Inter-portlet communication
You can do it this way or wait for our Portlet 2.0 Spec implementation in Liferay 5.0.
You can do it this way or wait for our Portlet 2.0 Spec implementation in Liferay 5.0.
10527, 18 Jaren geleden aangepast.
Liferay Legend
Berichten: 1197
Aanmelddatum: 8-2-05
Recente berichten
> Just want to ask, what's the future road map for IPC in Liferay? Any plan to make it "more useable"?
Perhaps a good reference read would be the Portlet 2.0.
http://jcp.org/en/jsr/detail?id=286
Portlet 2.0 is the future of IPC in Liferay. In particular, the Portlet
Event interface:
PLT.15.2 Portlet Events
Portlet events are intended to allow portlets to react to actions or
state changes not
directly related to an interaction of the user with the portlet.
Events could be either portal
or portlet container generated or the result of a user interaction
with other portlets. The
portlet event model is a loosely coupled, brokered, model that allows
creating portlets as
stand-alone portlets that can be wired together with other portlets at
runtime. Portlet
programmers should therefore not make any specific assumptions about
the environment
of portlets they are running together with. The means of wiring
different portlets together
is portal implementation specific.
Look the JSR-286 support in coming versions of Liferay. Sorry for not
being more specific than that... but it should be fairly soon...
Perhaps a good reference read would be the Portlet 2.0.
http://jcp.org/en/jsr/detail?id=286
Portlet 2.0 is the future of IPC in Liferay. In particular, the Portlet
Event interface:
PLT.15.2 Portlet Events
Portlet events are intended to allow portlets to react to actions or
state changes not
directly related to an interaction of the user with the portlet.
Events could be either portal
or portlet container generated or the result of a user interaction
with other portlets. The
portlet event model is a loosely coupled, brokered, model that allows
creating portlets as
stand-alone portlets that can be wired together with other portlets at
runtime. Portlet
programmers should therefore not make any specific assumptions about
the environment
of portlets they are running together with. The means of wiring
different portlets together
is portal implementation specific.
Look the JSR-286 support in coming versions of Liferay. Sorry for not
being more specific than that... but it should be fairly soon...
Thanks all for the reply, I'm aware that JSR-168 does not specify any IPC specs. And looking around, most portals have very weird IPC mechanism, including Websphere and Weblogic. It's all too inflexible. Waiting for Portlet 2.0 is not solving current problems though 
Reading a lot recently, and looking a way to put an easy fix to Liferay. And last night, I found this site IDSignet, a company in Shanghai. Looking carefully, I found that their portal is derived from Liferay (from the URL), but it seems that they have done a lot of changes. One of the most interesting things is the IPC mechanism, I have to say, it's exactly what I have in mind. You can take a look at the white papers here describing how their IPC works. The really interesting part is that you can reconfigure IPC between portlets at will, I can think of many ways to recombine my applications and re-create my page flow.
The other thing they seem to have done is the performance of the system. I have to say that opening a page on IDSignet's web site is faster than opening a page of Liferay on my Dell 2950
Looking to get in touch with them to see if I can try it out.
Disclaimer: I have no relation with the company, I'm just looking for a nice IPC solution to my problem.
Reading a lot recently, and looking a way to put an easy fix to Liferay. And last night, I found this site IDSignet, a company in Shanghai. Looking carefully, I found that their portal is derived from Liferay (from the URL), but it seems that they have done a lot of changes. One of the most interesting things is the IPC mechanism, I have to say, it's exactly what I have in mind. You can take a look at the white papers here describing how their IPC works. The really interesting part is that you can reconfigure IPC between portlets at will, I can think of many ways to recombine my applications and re-create my page flow.
The other thing they seem to have done is the performance of the system. I have to say that opening a page on IDSignet's web site is faster than opening a page of Liferay on my Dell 2950
Looking to get in touch with them to see if I can try it out.
Disclaimer: I have no relation with the company, I'm just looking for a nice IPC solution to my problem.
Interesting.
Maybe this is nice to read to:
http://mus.purplecloud.net/portlets/index.php
It seems to be a 168 compliant way of portlet communication.
Maybe this is nice to read to:
http://mus.purplecloud.net/portlets/index.php
It seems to be a 168 compliant way of portlet communication.
Joe Momo:
... Looking carefully, I found that their portal is derived from Liferay (from the URL), but it seems that they have done a lot of changes. One of the most interesting things is the IPC mechanism, ...
Someone with a sharp eye
Probably not supposed to do shameless plug here, we provide custom development, system integration, and consulting for Liferay portal as well. And if anyone needs to know more about IPC, please contact us. You can also request for free developer version too
5679760, 15 Jaren geleden aangepast.
Regular Member
Berichten: 103
Aanmelddatum: 27-8-10
Recente berichten
Joe Momo:
I found this site IDSignet, a company in Shanghai. Looking carefully, I found that their portal is derived from Liferay (from the URL), but it seems that they have done a lot of changes. One of the most interesting things is the IPC mechanism, I have to say, it's exactly what I have in mind. You can take a look at the white papers here describing how their IPC works. The really interesting part is that you can reconfigure IPC between portlets at will, I can think of many ways to recombine my applications and re-create my page flow.
These links don't appear to work anymore. I'm also having a very difficult time finding information about ID-Portal using Google. Has this portal vanished from the face of the earth?
I'm very interested in reading the white papers on the portal's IPC framework in particular as I'm in the process of building a similar framework to run on top of Liferay.