ConfigUploadAction has two ActionChildren, ConfigDateDetails and ConfigDateFileAction. Both use actionId as a primary key. This should work for ConfigDateDetails (test will indicate that problem), but it will not work for ConfigDateFileAction because ConfigUploadAction contains a set of them, meaning multiple ConfigDateFileActions with the same primary key. There needs to be a test for creating, committing, and looking up a ConfigUploadAction.
Correct, three ActionChildren, ConfigChannelAssociation. This third one also has no mapping file.
Tested whether ConfigUploadActions could be created, committed, and looked up. Added a composite key to ConfigDateFileAction. Found that the equals method of ConfigChannelAssociation wouldn't allow the lookup of more than one ConfigChannelAssociation and fixed that. ConfigChannelAssociations mapping is achieved through a composite key in Action.hbm.xml.