In the past, the solution was to do the "work" using the prepareable interface then just returning the reference to your model. I could be remembering incorrectly, but I would avoid doing any work in a getter.
-Wes On 12/6/07, Gary Affonso <[EMAIL PROTECTED]> wrote: > Dave Newton wrote: > > That depends on what happens in your getModel() call... if it doesn't matter > > that it's called twice then there aren't any issues. > > Let me add that the code for the ModelDrivenInterceptor is near-trivial. > It would be easy to copy-and-paste it into a custom interceptor, fix > the bug (also trivial) and then use that custom interceptor until the > bug-fix was released (and installed). > > I'm still considering doing that instead of the action workaround. I > don't use any of the built-in interceptor stacks which means I define a > custom stack anyway. It's just as easy to point to a fixed version of > ModelDriven than the sort-of-broken built-in one. > > Still figuring which way I want to go. > > - Gary > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Wesley Wannemacher President, Head Engineer/Consultant WanTii, Inc. http://www.wantii.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
