Null handling in TextPool might result in license texts never be retrieved
Closed this issue · 1 comments
ohecker commented
The current TextPool implementation distinguishes between a null value being explicitely stored (resulting in a NULL_KEY as key) and nothing being stored (which is represented by a null key). The code currently checks if license texts are already retrieved/filled. This is done by checking if the pool key for the text is set (is not null). If the text was previously explicitely set to null (resulting in a NULL_KEY to be stored), no further retrieval will be attempted.
To avoid these problems in using the TextPool no differentation should be done between "nothing being stored" and "null being stored".