In any case, if you don't want to wait for me, the attached Java classes to this issue are an exact replica of the entities we use - you can try and set up a reproducible test case. Basically:

• Create any of the concrete entities (i.e., CsvDataSourceResource or DataBaseSourceResource) with dummy data and persist it
• Commit the transaction
• Exit the transactional state if any associated with the thread - e.g., persist to some durable database instance and exit the test once entity committed
• Examine the tables and make sure the JOIN-ed tables are correctly populated

FYI - any 5.2.x version above 5.2.12 fails for me - in order to be on the same page, when I tested it again and got the results I described in my last comment regarding the sequence I used 5.2.17 ===> i.e., 5.2.12 works fine, 5.2.17 fails as described in this issue consistently.