Scenario 1: The domain spec file does not exist
An item has its domain entity attribute set to a nonexisting domain entity. This generates an error message in the default.log log file.
If the domain spec file is missing it will generate an error
message in the default.log file. The following
error message is an example of the type of message you would receive
if the domain spec file did not exist.
2013-04-30 23:18:03,238 [jsp_8: getDomainEntityIdForContainer.wpc]
ERROR com.ibm.ccd.content.common.MultiDomainEntityUtils -
CWPCM0606E:There is an error when processing the domain entity spec file:
C:\projects_rtc\aruba\ccd_src\etc/default/domains/multi_domain_entities_en_US.xml.,
Exception:C:\projects_rtc\aruba\ccd_src\etc\default\domains\
multi_domain_entities_en_US.xml (The system cannot find the file specified.)
java.io.FileNotFoundException: C:\projects_rtc\aruba\ccd_src\etc\default\
domains\multi_domain_entities_en_US.xml (The system cannot find the file specified.)