Best regards,
Taty

I am portal developer and especially interested in the JSR286 IPC (Inter Portlet Communications). I feel I have achieved some nice composite applications with reusable portlets by creating strategies on top of the events publishing & processing framework that JSR286 brings. And that is where the problem with JSR286 IPC resides. The specification defines a nice framework for distributing information about events, but this information lacks any kind of structure. So portal architects need to come up with a proprietary messaging payload standard dealing with the structure of this information. I think this was done intensionally by the JSR286 group with the hope that a de-facto standard would arise from one of the major Java portal vendors, though this has been slow coming. Without such a standard (or possibly a set of standards) it is difficult to assemble composite applications out of portlets developed in isolation from each other, which is crucial for mashups. I am hopeful there will be a follow on specification which deals with this. Possibly by leveraging semantic web standards like OWL and RDF.

The other challenge for portals is having the UI update in a useful way when IPC takes place between portlets. Currently there is a strong reliance on a full page refresh rather than partial browser DOM replacement using a form of AJAX. I feel JSR286 is partially to blame for this because IPC events distribution is always followed by a full page render phase. Maybe a better approach would be to introduce another phase where individual portlets are given the opportunity to signal that their view state has changed between the events and render phase. This idea still doesn’t feel quite right to me because portlets might run client side JavaScript that manipulates the browser DOM, which the portal server would be unaware of. This of course is less of a problem for gadgets because the view state is entirely orchestrated by the browser.

I have also data unlimitted, but connecting quickly without any speed nor opening. always
system error.. have forced to buy BSNL broadband serice which is very good working.

view have deciding to close all realtionship with reliance if they continue to fail serviec and collecting money without any use of serivces. Reliance Web World Centre are an Eyewash
and also threaten like “Gundas”.\

Reliance is the worst company I had experience with in terms of handling Customers and their genuine complaints. I never recommends Reliance Connections to any of my known ones.

Is there way to enable JavaScript / HTML in Body where you can put your own code a part from already built CMS Template. so If I want to create more tabs, gallery etc…in page. can I do all these things there in Fat wire Version 7…

Any updates on this? I am eager to see your views in the uncivilised corporates who call themselves “knowledge industry”.

my advice is be always ready to settle if you are NOT WRONG,
if you have a grievance of say 5000, it would rather set down to 3000
and from that 3k paying to lawyer and and recovery agent leaves almost too short amount for them. and that is the reason many times matter is just dissolved into time…
stretch you fight every time they demand you with your own reason and chances do increase of getting the matter dissolved..

But i have my own principles, i have a strong belief that if you saved any money by any kind of cheating and in unethical way.. nature recovers almost double in it’s own way !!

i had several issues with idea where i fight with them on each and every point of the TRAI rules they have bypassed.. they left the matter. but still i paid the amount that i felt was at me really.