Does Improved State-Saving Behavior in jsf 1.2 remove some restriction ...

Question

It was not possible (or not easy, note recommended) to manage more that one application form displayed in a browser without putting some confusion in the page data control binding.
Browsers offer tab management, JavaX offer cut and paste, so user's put pressure to have many duplicated application form in their browser each synchronized with their own data control (and to cut and paste data from one to the another but it is not the question here).
Does jsp 1.2 and the change in state-saving help to solve current problem ?
Does Oracle plan to change something in adf framework to solve this issue ?

Answer 1

To be more specific (if anyone here knows ASP.NET): The UserControl has something called Page, that component has Header and Body, if I add something to the Header (like Link for one) then it'll appear in the head section of my page.
I need the component to add one JavaScript file that will contain my client-side logic (it's not trivial nor short so it needs to be externalized).
Apart from that it's not doable for me to do all the rendering for myself because the controls I'm using have to be from RichFaces (architect's decision - not mine). So all I can do is either manually glue things together in the xhtml template directly and add the necessary JS to the template (again: manually), or create a compound component that will be composed of the two components that already do what I need them to do and add the necessary additional JS file automatically when the component is added to the page.
However what I wanted to do is to create a component that will reuse the functionality of one of the RF components and add an input field in front of it that'll hold String and not Date (like the cumbersome RF component does).
Can you help?
Edited by: padcom on Jun 7, 2010 12:15 PM