Grouper Developers Forum

[Tom Zeller <>]

I had pinged Chris off-list but I am bringing this on-list in case
other folks can help me reason my way through this.


I am wondering how good of an idea it is to stash a spring bean
definition (is it a singleton ? a prototype ? I do not remember) as a
static variable.


To implement a grouper change log consumer, the ChangeLogConsumerBase
class should be extended. So,

 public class LdappcngChangeLogConsumer extends ChangeLogConsumerBase {

  private static PSP psp;

  public LdappcngChangeLogConsumer() {
  }

The no-arg constructor is required, and the consumer class is
instantiated every time the changelog processes entries. Obviously, I
will want to keep a persistent copy of the ldappcng provisioning
service provider (PSP.java) as a static (I guess ?) variable to avoid
delays. I assume the loader runs in a separate jvm.

The PSP extends (shibboleth) BaseReloadableService, and is configured
via spring from the hard-coded configuration file
"ldappc-services.xml", which specifies the locations of other
(shibboleth) services, such as the attribute resolver. So we will be
relying on the classpath.

The spring bean definition parser for PSP.java extends
AbstractSingleBeanDefinitionParser, and I remember from reading about
spring that there were singleton and prototype bean definitions - I am
not sure if I need to do something in particular to store the PSP
safely as a static variable for use by the ldappcng changelog
consumer.

Clues ?

TomZ