All: My app is backended by an Oracle database in which each entity is keyed by an artificial key. I'm using JRF as the persistence framework. I populate my formbeans from JRF data beans using BeanUtils.describe() and BeanUtils.populate(), and the commit function reverses this flow, populating JRF data beans from my formbeans.
In the early stages of development, I displayed the artificial keys on my JSPs with <html:text> tags, because I wanted to see the key values; however, when my app reaches production, I don't want the user to see the artificial keys, or in fact even know that there is such a thing. However, when I changed the tags on my JSPs to <html:hidden>, the artificial key fields seemed no longer to be populated by BeanUtils. I think I may have seen something about BeanUtils methods not operating on hidden fields back when BeanUtils was a Struts package, but I got caught in the transfer of BeanUtils to the Commons project. I did check the current BeanUtils documentation, but of course since BeanUtils is now a Commons component rather than Struts, there's no mention of any relationship to Struts tags. I searched this mailing list's archives and could not find anything on this topic. The behavior I'm seeing seems aberrant, since it seems to me that BeanUtils utilizes only the relationship between the formbean and the data bean, and has no knowledge of Struts tags. So, my question is twofold: Do BeanUtils methods operate on hidden fields? If not, how do I manage transfer of a field that I want hidden on the JSP? -- hiding an artificial key seems like a routine thing to do, and I apologize for raising the question here, but I've done at least some homework and can't find anything definitive. Charles McClain Phone: 603.659.2046 email: [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
