What is happening is when you submit the form by selecting save, your request scoped stuff which was displayed to the browser on your edit isn't going to survive unless you have a way of carrying it across. On input fields in your jsp it gets carried across, if you want to bring other stuff that isn't displayed or put in hidden input fields, you need to either store it to the http session and get it back out in the target backing bean or use x:savestate from the myfaces library.
Ron ----- Original Message ---- From: contact1981 <[EMAIL PROTECTED]> To: users@appfuse.dev.java.net Sent: Thursday, December 21, 2006 12:53:01 PM Subject: [appfuse-user] JSF Backing bean's application-specific class type attributes get nulled I am using Appfuse with JSF. I generated DAOs, xhtml pages, Managers and much more using Appfuse. I have a backing bean for a form webpage. Using sample-data.xml, I load up pre-existing data. Therefore, there will be a backing bean containing pre-existing data for that particular form webpage. Most of the attributes of the backing bean are primitive data types(i.e int, boolean) or java class types(i.e Integer, String). However, I also have attributes that are application-specific class types. These objects of application-specific class types do not need to be shown on the screen. They are just associated with the backing bean as attributes. I stepped through the code using MyEclipse Debugger, and loading up the webpage worked out fine. In other words, all the fill-in boxes had the correct pre-existing data. I also noticed that the backing bean’s application-specific objects contain the correct information. When I clicked on the save button, I decided to continue tracing through the code. As I stepped through the code, I noticed that at some point all the attributes of the backing bean are reset to null, and again refreshed with the latest values in the fill-in boxes of the webpage. All attributes of primitive data types and java class types are restored with legitimate data. However, any attributes of application-specific class types remain as null. In other words, somewhere between edit and save, I lose all objects of application-specific class types. Moreover, I don’t even see why appfuse nulls out all the attributes of the backing bean in the first place. How can I prevent losing all the attributes that are of application-specific class types? View this message in context: JSF Backing bean's application-specific class type attributes get nulled Sent from the AppFuse - User mailing list archive at Nabble.com.
