Storing also QualitativeValues in BrokerPolicy.
Fixed a typo in CAS Silver profile.
Made the SAP_HANA BP and SD valid according to the revised validation
mechanism.
Switched to SAP_HANA files for validation.
acquireMemoryForData() is called only once when PCC is created. All
other calls have been eliminated, except those in helper methods (at the
bottom of the file) which are used ad-hoc by external users (e.g. the
Message Broker topic subscibers).
BP is available now in memory so the workaround for "startClassIndex ==
4" is not needed any more.
The completeness check mechanism has been updated in order to follow the
revised validation mechanism.
The compliance check mechanism now checks QualitativeValues also.
Removed references to SD in completeness/compliance check methods since
those will be used for BP validation also.
Encapsulated completeness/compliance methods inside
validateSDForCompletenessCompliance(). This is used by all external
users.
This method checks if already loaded BP had SLP info in it, in order to
perform minimal checks on SD.
Actual algorithm runs in private method runCompletenessCompliance().
Added helper method bpHasSLPInConnection() that returns whether BP had
SLP info in it.
If a BP under validation has SLP info in it, it is checked for
completeness/compliance also.
SDEvaluationListener and WSO2GREGEvaluator conformed to the new PCC API
using method validateSDForCompletenessCompliance().