[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3704?page=c... ] Antoine Herzog commented on HHH-3704: ------------------------------------- Oups.... I have found the proper way to do this. use an alias for direct access to the related entity. order clause is on : commonInfo_shipFlag.name (commonInfo_shipFlag is the alias). and it works... idem for the filter : use the alias in the criteria for the where clause. ******************* May be this is a way to solve the problem for the MappedSuperclasses I don't know, but it may work... that would explain why the HQL works, but not the Criteria ******************* parsing and decoding of : a.b.c.d for the properties would be a nice feature. using some alias is a bit more complex (must remind the alias to build the filter clause... not easy for query automatic generation). is this possible ? there is a problem to decode several level of entities/properties ? ******************* sorry for the unproper comments on this Jira. Antoine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3704?page=c... ] Antoine Herzog commented on HHH-3704: ------------------------------------- Sorry, I don't know. I don't know why the query builder can do it with alias, but is not able to retrieve the path by introspection of the entities. It seems that it can do it for one step only. but cannot iterate on it. I guess that there is a reason not to have done so. In the engine of Hibernate. may be because Hibernate needs something more to identify the tree of entities (the full path), than just introspection. that would explain why it needs to have an alias of it. but have no real idea if this can be done, by modifying the code (with your special add-on) or by asking it to the project for a next release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3704?page=c... ] Vikash Madhow commented on HHH-3704: ------------------------------------ As a workaround, I've written the following method which automatically create the aliases when ordering by a property which references other entities. It works for property paths of any length, i.e., if you are ordering by a.b.c where b and c are entities, the method will create the alias for join a -> b and for b->c: /** Orders a criteria */ protected Criteria order(Criteria query, Order... order) { try { for (Order ord: order) { // get order property and whether ascending or descending String property = ord.toString(); int pos = property.lastIndexOf(' '); boolean asc = property.substring(pos + 1).trim().equalsIgnoreCase("asc"); property = property.substring(0, pos).trim(); // if property references other entities, create joins. // lastJoinPoint refers to the position in the property path // where the last join was performed. Class currentClass = entityClass; Criteria subCriteria = query; StringBuilder currentPath = new StringBuilder(); String[] paths = property.split("\\."); int lastJoinPoint = 0; for (int i = 0; i < paths.length - 1; i++) { if (currentPath.length() != 0) currentPath.append('.'); currentPath.append(paths[i]); // Create a join for the current property path if it // references an entity class property = currentPath.toString(); Class<?> type = FieldNavigator.getField(property, currentClass).getType(); if (type.isAnnotationPresent(Entity.class)) { subCriteria = subCriteria.createCriteria(property); currentPath.delete(0, currentPath.length()); currentClass = type; lastJoinPoint = i + 1; } } // order subCriteria by path elements starting from last join point currentPath.delete(0, currentPath.length()); for (int i = lastJoinPoint; i < paths.length; i++) { if (currentPath.length() != 0) currentPath.append('.'); currentPath.append(paths[i]); } property = currentPath.toString(); subCriteria.addOrder(asc ? Order.asc(property) : Order.desc(property)); } return query; } catch(Exception e) { throw new RuntimeException( "Could not apply order " + Arrays.toString(order) + " to query '" + query + "' over " + entityClass, e); } } --- The method FieldNavigator.getField simply returns the field corresponding to the property path supplied. If anyone requires the source, I'll post it. Simply call this method to order your criteria query instead of Criteria.addOrder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3704?page=c... ] Kaspar Fischer commented on HHH-3704: ------------------------------------- Thanks, Vikash, for your quick response and sharing of your code. Unfortunately, I realize that I am in a slightly different situation. I don't have property paths to entities but to components. Something like this: @Entity class A { @Embedded B b; } @Embeddable class B { String s; } and I want to list the rows in A sorted by "b.s". With aliases you can, it seems, not handle this case. - Or am I making a mistake at some stage? (P.S. "Java Persistence with Hibernate" 2007 says: "Finally, note that at the time of writing only joining of associated entities or collections that contain references to entities (one-to-many and many-to-many) is supported in Hibernate with the Criteria API. The following example tries to join a collection of components: [...] Hibernate fails with an exception [...]") -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3704?page=c... ] Kaspar Fischer commented on HHH-3704: ------------------------------------- Vikash, first of all, thanks a lot for taking the time to help me. Very much appreciated. You are right, it works as you say. I made a mistake in my property path and now it works. You saved me lots of time, so thanks again. Kaspar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira