Wes Wannemacher wrote:
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.
Any reason you'd avoid it beyond the double-call bug?
I've generally just used prepare when I needed the params|prepare|params
sandwich. Hadn't really occurred to me to use it more generally.
You're right, it's another way to go that would avoid the bug. And it
doesn't require monkeying with custom interceptors or hackish
workarounds in the action. Good suggestion. I'll go do that now. :-)
- Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
