Bugzilla – Full Text Bug Listing
| Summary: | PK ordering on 1-m does not appear in virtual orm.xml mapping | ||
|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Karen Butzke <karenfbutzke> |
| Component: | General | Assignee: | Neil Hauge <neil.hauge> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | neil.hauge |
| Version: | 2.3 | ||
| Target Milestone: | 3.0 M5 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Can no longer reproduce this. Was likely fixed as a result of Brian's M5 refactoring that changed how virtuals are handled. |
Given the following example looks at the employees virtual mapping in the JPA Details view of the orm.xml. Notice that Ordering 'None' radio button is selected instead of 'Primary key' @Entity public class EmployeeHistory { @OneToMany @OrderBy private Collection<Employee> employees; } <entity class="model.EmployeeHistory"> </entity>