It looks like navigationalstate is modified after IPC call with request params so it's a non-starter for us. Will not use IPC for our purposes
I can't reproduce your case
I've tried with 2 simple portlet A --> dispatch event. B --> written in Juzu, and consumes that event (using @Consumes). After process event, it re-render the portlet, and the action urls still works as expected (Gatein 3.5.0.Final , Juzu 0.6.0-beta16)
Can you attach your sample portlet to reproduce this problem ?
Our design calls for setting a json response from the server as a payload in an IPC event. It appears that the payload is very large and the navigationalstate that results from calling the action becamed very large and we have observed the url is actually cut off!