user491078 wrote:Thanks for the reply, I have further question on this JSF can get confused between content of two different windows, I have a scenario below
Additionally the suggestion by feature edge is somewhat dangerous. The loop back script is central to window tracking. Without it, JSF can get confused between content of two different windows. Generally the property they add to the request is added by Trinidad when it KNOWS it has a correct window and a previously established window id, and it's never done in a request that's likely to be repeated using ctrl-n on the browser. Furthermore, since that param serves one specific purpose, the implementation of it is not guaranteed so it's likely to break I'm the future.
As was suggested in the future-edge thread, instead of hacking together a solution or taking advantage of an implementation detail, perhaps you could suggest an enhancement to support this officially.