Community
Participate
Working Groups
If some nodes are absent in CC xml file, application fails (e.g. each RepositoryConfiguration node must have one RepositoryConnectionParameters child). The xsd definition of CC does not specify that some nodes are required, however application is not designed to handle such cases. In general, if a node does not exist, null is returned by the getter method. However, it is not checked later whether the returned value is null. It seems that either xsd definition or container handling needs to be changed. Incorrect CC data can occur now as the functionality of CC modification is added to UI.
A workaround was implemented. It prevents from defining incorrect CC from UI. Additional xsd were created that are used only for validation purposes. If CC/PCC is modified in UI, the validation xsds are used to check if all required fields are present. The difference between the original and the validation xsds is that the later contain different minValues for some elements. If validation fails, modifications are not applied. No changes to generated code nor original xsds are required. The application will still fail if, for some reason (e.g. manual file modifications on server side), CC xml data is incorrect.
Closing all outstanding RESOLVED and VERIFIED items.
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.
Project is archived.
