[kevcpu411]

Do you have any alternative scenarios? I see trouble in my future if I use serializable with my bean.

Also, how does the keepAlive affect the lifecycle. Is it the equivalent of a session bean or does it have a shorter cycle? The reason why I ask ... As a user selects records to edit I need a new data pull to occur each time to retrieve the currently selected record. Also, I have wizards that may utilize several beans and I might have problems with the keepAlive in this situation. I did this to keep the beans lightweight. Say I have a wizard that spans 7 different pages, it seemed resource intensive if I housed all of this in one bean as opposed to a separate bean for each wizard scenario. Can you think of a way that i can utilize the approach you discussed in the confines I outlined here? You mentioned there were other ways besides the easiest. What do you think would be the second easiest, third, etc.? :-)