Ensure that methods of the schema xtk:session and xtk:persist are loaded when doing a getSchema
Related Issue
When loadiing xtk:session it is possible that the schema is already in the browser cache, because browser storage is persistent). Therefore the schema was loaded from cache of the browser to the memory and the methods of the schema were not loaded in memory.
In same case the cache does not content anymore the methods of xtk:persist because cache values have expired.
But entitycache still contents the schema xtk;persist
So when calling a implemented method in xtk:persist (like Duplicate) from a schema (like xtk;workflow) not loaded yet, it fails:
{
"name": "CampaignException",
"message": "400 - Error 16384: SDK-000009 Unknown method 'Duplicate' of schema 'xtk:workflow'. Method 'Duplicate' of schema 'xtk:workflow' not found",
"statusCode": 400,
"errorCode": "SDK-000009",
"faultCode": 16384,
"faultString": "Unknown method 'Duplicate' of schema 'xtk:workflow'",
"detail": "Method 'Duplicate' of schema 'xtk:workflow' not found"
}
Motivation and Context
Bug fix
How Has This Been Tested?
added unit tests
tested in web ui context
Screenshots (if appropriate):
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Description
Ensure that methods of the schema xtk:session and xtk:persist are loaded when doing a getSchema
Related Issue
When loadiing xtk:session it is possible that the schema is already in the browser cache, because browser storage is persistent). Therefore the schema was loaded from cache of the browser to the memory and the methods of the schema were not loaded in memory.
In same case the cache does not content anymore the methods of xtk:persist because cache values have expired. But entitycache still contents the schema xtk;persist So when calling a implemented method in xtk:persist (like Duplicate) from a schema (like xtk;workflow) not loaded yet, it fails:
Motivation and Context
Bug fix
How Has This Been Tested?
added unit tests tested in web ui context
Screenshots (if appropriate):
Types of changes
Checklist: