Field Detail

• protected ApplicationContext applicationContext

• protected final boolean earlyPluginRegistrationRan

• protected final GrailsPluginManager pluginManager

Property Detail

• static final boolean RELOADING_ENABLED

• final GrailsApplicationClass applicationClass

• final java.lang.Class[] classes

• final GrailsApplication grailsApplication

• final GrailsApplicationLifeCycle lifeCycle

• boolean loadExternalBeans

• boolean reloadingEnabled

Constructor Detail

• GrailsApplicationPostProcessor(GrailsApplicationLifeCycle lifeCycle, ApplicationContext applicationContext, PluginDiscovery pluginDiscovery, java.lang.Class[] classes)

Method Detail

• protected void customizeGrailsApplication(GrailsApplication grailsApplication)

• protected final void initializeGrailsApplication(ApplicationContext applicationContext)

• protected void loadApplicationConfig()

  Registers conversion service converters and creates the PropertySourcesConfig that backs grailsApplication.config.

  Plugin configurations are loaded early by GrailsEnvironmentPostProcessor and are already present in the environment's property sources by the time this method runs. This method simply creates the PropertySourcesConfig from whatever property sources exist in the environment.

• @java.lang.Override
  void onApplicationEvent(ApplicationContextEvent event)

• protected void performGrailsInitializationSequence()

• @java.lang.Override
  void postProcessBeanDefinitionRegistry(BeanDefinitionRegistry registry)

• @java.lang.Override
  void postProcessBeanFactory(ConfigurableListableBeanFactory beanFactory)

• protected static void registerAnnotationConfigProcessorsForGeneratedArtifacts(BeanDefinitionRegistry registry)

  Restores the processors that read the injection annotations, when running on artifacts generated ahead of time.

  Generating those artifacts normally makes these unnecessary: the generator reads the annotations itself and writes the field and method access into the code it emits, which is why a controller or a tag library arrives fully injected without them. It can only do that for a bean whose implementation it can see, and a bean contributed as an interface built by a supplier hides it -- the link generator is declared as LinkGenerator and built by a closure, so the @Autowired field on the implementation is generated for by nobody. Nothing fails at start-up; the first page that follows a link does.

  Only the two that inject are restored. Registering the whole set would bring back the processor that reads configuration classes, and reading them again in a context whose configuration has already been generated makes a second definition for beans the generated code has already contributed.

  They are registered under the names Spring uses itself, so a context that already has them keeps what it has, and a context running without generated artifacts is untouched.

• @java.lang.Override
  void setApplicationContext(ApplicationContext applicationContext)