Yes I can envision some useful transforms which wrapper/unwrapper data formats without doing copies.
That raises the question of how to turn off PBVInterceptor dynamically. I guess I hadn't given this enough thought before, since actually I'd like to be able to do the same from the binding impl... I'd like to, dynamically at invocation time, be able to turn off the PBVInterceptor. It seems like we could use a setter on the chain itself to do this. Then we still have the question of how to turn off the copy or not for particular data transforms. I agree turning it off is a good default, but it seems like it should be a possible for a particular transform to, even dynamically, decide that, as far as it knows anyway, the PBVInterceptor copy may still be needed. What do you think? Scott On Feb 19, 2008 10:32 PM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > Raymond Feng wrote: > > That was my intention to return true as the DTInterceptor will make sure > > the data passing is safe. > > > > Is that always a correct assumption? I thought that it could depend on > the nature of the transformation. Some transforms would copy or protect > the data, some wouldn't... > > -- > Jean-Sebastien > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
