> I think ExtendedType already provides that, so just making sure it isn't > overlooked.
Did you mean “DON’T think .. “? ExtendedType is completely free of the mapping context: http://cayenne.apache.org/docs/3.1/api/org/apache/cayenne/access/types/ExtendedType.html I already started committing some code. Looks like I found a better place for reads that has all the metadata and does not require changing ExtendedType - RowReader. So I created RowReaderFactory that should allow to intercept read data one row at a time. Haven’t looked at writes yet. Andrus On Mar 12, 2014, at 11:06 PM, Michael Gentry <[email protected]> wrote: > In addition to the attribute being read/written, I think it would (or > could) also be helpful to know which entity, too. I think ExtendedType > already provides that, so just making sure it isn't overlooked. > > mrg > > > > On Wed, Mar 12, 2014 at 3:13 AM, Andrus Adamchik > <[email protected]>wrote: > >> A heads up. I am looking to extend ExtendedType API to be a little more >> context-aware (know which attribute is being read/written). My motivation >> is quite interesting on its own - I need to implement generic data >> encryption extensions that would encrypt/decrypt certain columns on the >> fly. And I feel like ExtendedType is a place that is low-level enough to >> make the encryption transparent to the rest of the stack. Very excited >> about this project :) >> >> A.
