DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30428>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30428 RequestProcessor should bind form beans after population, not before ------- Additional Comments From [EMAIL PROTECTED] 2004-08-03 00:37 ------- Adding an *additional* bind of the form bean would not cause backwards compatibility problems -- switching the order of calls in RequestProcessor.process would. However, it sounds like the additional bind would cause undesireable overhead on WebLogic, because it would try to persist the form bean twice. You should also investigate whether there is a configuration option to tell WebLogic to wait until the end of the request and then persist anything that has been rebound ... I'd be scared to death to rely on every possible bit of my application code remembering to rebind the session attribute after every change. Indeed, for session-scoped business objects that don't know anything about web tier APIs, it would be impossible for them to do so, because you'd never be sending a reference to the HttpSession along to one of the method calls. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
