Package com.atlassian.jira

Interface InitializingComponent

All Known Implementing Classes:
AbstractFieldLayoutManager, AbstractSchemeManager, ArchivedStatistics, CachedFieldConfigSchemePersister, CachedGenericConfigManager, CachedOptionSetManager, CachedOptionsManager, CacheInvalidationTriggerIpdJob, CachingCustomFieldManager, CachingDraftWorkflowStore, CachingExternalGadgetStore, CachingFavouritesStore, CachingFieldConfigContextPersister, CachingFieldScreenStore, CachingI18nFactory, CachingJiraHomeTemplateContentLoaderImpl, CachingLabelStore, CachingOfBizPropertyEntryStore, CachingPluginIndexConfigurationManager, CachingPortalPageStore, CachingPortletConfigurationStore, CachingProjectComponentStore, CachingProjectKeyStore, CachingProjectManager, CachingProjectRoleAndActorStore, CachingSearchRequestStore, CachingSharePermissionStore, CachingTaggingAvatarStore, CachingTerminologyEntryDao, CachingUserHistoryStore, CachingVersionStore, CachingWorkflowDescriptorStore, ClusterWatchdogService, ComponentCachingOfBizPropertyEntryStore, CustomFieldContextHandlerImpl, DefaultApplicationRoleManager, DefaultAppMonitoringMetricsService, DefaultCachingApplicationPropertiesManager, DefaultColumnLayoutManager, DefaultConstantsManager, DefaultDBRTransportManager, DefaultDurationFormatterProvider, DefaultEventTypeManager, DefaultFeatureManager, DefaultFieldLayoutManager, DefaultFieldManager, DefaultFieldScreenSchemeManager, DefaultGlobalPermissionManager, DefaultInstanceFeatureManager, DefaultInstrumentationLogger, DefaultIssueLinkManager, DefaultIssueLinkTypeManager, DefaultIssueTypeScreenSchemeManager, DefaultMoveSubTaskOperationManager, DefaultNodeReindexService, DefaultNotificationSchemeManager, DefaultPermissionSchemeAttributeManager, DefaultPermissionSchemeManager, DefaultProjectPropertiesManager, DefaultReindexMessageManager, DefaultSearchHandlerManager, DefaultSecureUserTokenManager, DefaultServiceManager, DefaultTemplateValidationConfigProvider, DefaultTemporaryWebAttachmentManager, DefaultUserPropertyManager, DefaultWorkflowSchemeManager, EagerLoadingOfBizCustomFieldPersister, EagerWorkflowSchemeManager, EmailCachingVelocityEngineFactory, EventReplicationManager, FieldConfigPersisterImpl, FieldConfigSchemePersisterImpl, GadgetSpecsCacheService, IncomingMailServerConnectionIpdJob, IndexingFeaturesImpl, IntegrityCheckManagerImpl, IssueSecurityLevelManagerImpl, IssueSecuritySchemeManagerImpl, IssuesIndexSchemaManager, IssueTypeSchemeHandlerImpl, JiraCacheResetter, JiraDelegatingDirectoryInstanceLoader, JiraFailedPluginTracker, JiraLicenseManagerImpl, JiraPluginPersistentStateStore, JiraWebResourceIntegration, MauEventServiceImpl, OfBizApplicationDao, OfBizDirectoryDao, OfBizGroupDao, OfBizInternalMembershipDao, OfBizMessageHandlerService, OfBizSearchRequestStore, OsgiServiceTrackerCacheImpl, PeriodicIndexWriterCommitScheduler, PluginsAwareUserFormatTypeConfiguration, PluginTransactionListener, PluginUpgradeListener, PropertySetBackedUserFormatTypeConfiguration, RoleTypeMappingZduSafeCache, SecondaryJiraHome, SharedHomeLatencyIpdJob, SingleEntityCachingOfBizPropertyEntryStore, SuperBatchInvalidator, TaskManagerImpl, UiSettingsStateManagerImpl, UserKeyStoreImpl, WebSudoIPAllowListManager, WorkflowBasedPermissionSchemeManager, ZDUAwareNodeReindexService
public interface InitializingComponent
Similar to InitializingBean in Spring but afterInstantiation is called only after the container and ApplicationContext is fully populated. This is useful when you need to access other beans in the container using ComponentAccessor Especially useful when you need to initialize cache or access any db values during component initialization Due to our legacy and hacks, these actions require access to other beans via ComponentAccessor and fail if accessed during bean creation atm of writing. Use InitializingBean when you need to perform initialization right after the bean creation, without accessing ComponentAccessor.
Since:
v6.0.2

  • Method Summary

    Modifier and Type
    Method
    Description
    void
    afterInstantiation()
    Called after all the beans are constructed and the ApplicationContext is fully populated.

  • Method Details

    • afterInstantiation

      void afterInstantiation() throws Exception
      Called after all the beans are constructed and the ApplicationContext is fully populated. Order of execution is order of bean creation, driven by InitializingComponentProcessor.
      Throws:
      Exception