a4j:keepAlive and modal panels

[kevcpu411]

I really need help. I am trying to implement modal panels in a master-detail scenario with datagrids. A user can either edit a record or add a new record. Adding a new record should result in a modal panel opening up with empty components, where as an edit scenario should result in all of the components being populated with the information from the record currently being edited. I am using keepAlive because I need certain aspects of the bean accessible between different ajax requests. For some reason, it does not appear to be keeping the bean alive when I use ajaxOnly. What constitutes an "ajax request"? My links and buttons are all a4j. Am I missing something. I basically want the bean to go away when the modal panel is closed and to be accessible as long as the modal panel is open.

[pbaker01]

Did you read this thread?

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=144191

Keep alive works fine for me... with ajax

PB

[kevcpu411]

Thanks for the link. My problem seems to be that the bean goes away. For example, if I click a a4j:commandLink to fire an actionListener that adds a new row to a datagrid. I would expect to be able to click a different link to save the new row after editable information has been entered. This is not the case here. For some reason, it instantiates the bean all over again, calls the constructor, etc. If I am using an a4j:commandLink for adding a new record and another to perform the save I would think this would constitute two different ajax requests. Is my logic for this flawed somewhere?

[kevcpu411]

"kevcpu411" wrote:
Thanks for the link. My problem seems to be that the bean goes away. For example, if I click a a4j:commandLink to fire an actionListener that adds a new row to a datagrid. I would expect to be able to click a different link to save the new row after editable information has been entered. This is not the case here. For some reason, it instantiates the bean all over again, calls the constructor, etc. If I am using an a4j:commandLink for adding a new record and another to perform the save I would think this would constitute two different ajax requests. Is my logic for this flawed somewhere?

Also, I need some insight in what constitutes an ajax request from a jsf/richfaces perspective? Is it merely clicking on a button or link that is a4j:commandButton or a4j:commandLink or is there more to this relationship?

[ilya_shaikovsky]

please paste your code snippets.

[kevcpu411]

There is a lot of code and I will work on condensing it foy you but in the meantime, coould someone answer my previous question about what jsf views as an "ajax request" ad where this differs from a standard request. This is in terms of actions such as button click and link clicks.

[nbelaevski]

Hi,

Please take a look at this: http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/docs/devguide/en/html/ArchitectureOverview.html#introToBasics