Community
Participate
Working Groups
Created attachment 99696 [details] Null table and column messages When a OneToMany is defined as a simple List with no content type, e.g. public class Publisher { @OneToMany private List titles; ... Dali produces error messages like (see screenshot): Column "null" cannot be resolved Join table "null" cannot be resolved These messages do not help the developer resolve the problem and guide them to suppling the missing target entity information. It would be better, when the join table name is to be derived and validated against the schema that, if the join table cannot be determined due to a missing target entity, Dali provide a message along the lines of: Target Entity for Publisher.titles not defined - join table cannot be determined "null" anywhere in a message indicates that we are not providing useful diagnostics to the developer.
Created attachment 99697 [details] From my notes--this results from an unmapped List attribute
This improvement will fit nicely with our focus on improved validation our next release.
Fixed in 2.1 M2
The fix for this has been revised in bug 257629. You can see an explanation of the new validation messages in that bug. Shaun, if you have a chance, could you test this out? We will release it later today if you want to use a build. Otherwise I will check it into cvs soon.