Fix server startup created time null issue #6340
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
In server startup, through the X509 we are persisting few resources to the configuration manager. But after activating only the created time is set.
This PR fixes that.
This pull request includes a minor but important change to the
ConfigurationManagerComponent
class. The change involves moving the registration of theConfigurationManager
service to ensure it occurs after setting theuseCreatedTime
flag.components/configuration-mgt/org.wso2.carbon.identity.configuration.mgt.core/src/main/java/org/wso2/carbon/identity/configuration/mgt/core/internal/ConfigurationManagerComponent.java
: Moved thebundleContext.registerService
call to occur after setting theuseCreatedTime
flag to ensure proper initialization order.