Recent change (not yet released) #166 changed sunIdentityRepository / idRepoService.xml schema by adding the resourceName attribute to the top-level Schema element. However there is no upgrade step that is capable of updating the schema when its attributes change. This means that the existing installation won't have new schema and the IdRepo service won't be exposed via REST under the expected path.
There is an upgrade step SchemaXmlAttributeUpgradeStep which was intended to update all service definitions when upgrading to 14.0.0 release. However, we released a full release that did not contain all resource names changes.
There are two possible approaches to fixing this issue:
simply change the constant SchemaXmlAttributeUpgradeStep#AM_14 to newer version (forcing the step to be performed again)
update SchemaXmlAttributeUpgradeStep to actually be able to detect schema attribute changes regardless of the version constant (i.e. remove the early exit condition based on the AM version)
pavelhoral
commented
9 months ago
Recent change (not yet released) #166 changed
sunIdentityRepository/idRepoService.xmlschema by adding theresourceNameattribute to the top-levelSchemaelement. However there is no upgrade step that is capable of updating the schema when its attributes change. This means that the existing installation won't have new schema and the IdRepo service won't be exposed via REST under the expected path.There is an upgrade step
SchemaXmlAttributeUpgradeStepwhich was intended to update all service definitions when upgrading to 14.0.0 release. However, we released a full release that did not contain all resource names changes.There are two possible approaches to fixing this issue:
SchemaXmlAttributeUpgradeStep#AM_14to newer version (forcing the step to be performed again)SchemaXmlAttributeUpgradeStepto actually be able to detect schema attribute changes regardless of the version constant (i.e. remove the early exit condition based on the AM version)