Thanks for the insight Dan, I was starting to wonder if that is what was happing. The sample looks like it should solve my problem.
-Eric Dan Ellentuck wrote: > Hi Eric, > > The default IEntityGroup implementation, > o.j.p.groups.EntityGroupImpl, caches its member keys. As a > result, once an EntityGroupImpl leaks out of an > externally-managed service, it is vulnerable to becoming out > of sync with its store. I think the easiest approach is to > extend EntityGroupImpl to delegate member queries > (contains(), getMemberEntities() and getMemberGroups()) to > the local group service and have your group store > instantiate instances of this class. I'm attaching an > example of this approach. > > Dan > > Eric Dalquist wrote: > >> I'm writing a JDBC based group store to go against a set of tables with >> group information maintained by another group. I have everything working >> but can't figure out some of the caching issues. Data will be added and >> removed from the tables by an external process. The service is >> configured as externally managed and has caching disabled. Even so I get >> failures (null pointers) in groups manager if groups or members are >> removed from the DB and groups/members that are added don't show up >> until the portal is restarted. >> >> Any help configuring this would be much appreciated. >> >> -Eric >> > > >
smime.p7s
Description: S/MIME Cryptographic Signature
