In that case, I don't want it to throw a ClassCastException because the ApplicationContext was not a ConfigurableApplicationContext.  I just want it to behave like before, which is... the PDX Disk Store bean definition must appear "first" in the application context configuration file, before any persistent Async Event Queues or Regions.  Ordering the bean definitions properly causes this problem to be solved to.

Adding this PdxDiskStoreAwareBeanFactoryPostProcessor is meant solely for convenience so that the user does not have to think about or concern themselves with properly ordering GemFire bean definitions when the ApplicationContext is configurable, which as you say, will probably always be the case.

The only reason why I check for an explicit ConfigurableApplicationContext is because that is the interface with the addBeanFactoryPostProcessor method.