From: Joe L. <jml...@gm...> - 2010-04-27 23:30:31
|
Well, I think that is perfectly fine as long as the dev is aware of that :). I've been using the API doc references to ERDefaultNormalizer as well as Travis' fine WOWODC session to date. Because of its simplicity to the dev (can be said as well for ERAttachment), I must say that the WOWODC session has been one of my most referenced to date. On Tue, Apr 27, 2010 at 4:22 PM, Mike Schrag <ms...@po...> wrote: >>> oh .. right because taggable entities aren't cached. yeah, it's a hole in the api. it should ... maybe ... cache the taggableeneity ... or you register those higher up. >> >> I did register them in the app constructor and then assigned the >> normalizer, but it was ignored. >> >> I then used the convenience methods to get a taggable Entity within a >> page, and that appears to be the only place one can set the normalizer >> with any affect. > my point is that every time you ask for a taggable entity, i think it's a new instance. so it's not something special about the page or the app constructor, it's that it's thrown away every time you get an instance. > > ms > |