search

gemire / daofusion

Automatically exported from code.google.com/p/daofusion
0 stars 1 forks source link

Property path refactoring #8

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
NestedPropertyCriterion and its subclasses currently support dot-separated
property path as a String only (in the end, the user has to concatenate
path elements on his own). Furthermore, it is not possible to specify
custom join types for individual path element junctions (single join type
for entire property path).

We propose refactoring based on object representation of association path
and its elements, which leads to the target property. A special class
(AssociationPathRegister) will replace the old "subCriteriaMap" in
NestedPropertyCriteria.

Original issue reported on code.google.com by michal.j...@gmail.com on 1 Jun 2009 at 10:58

GoogleCodeExporter commented 9 years ago 
http://codereview.appspot.com/67132

Original comment by michal.j...@gmail.com on 1 Jun 2009 at 11:19

GoogleCodeExporter commented 9 years ago 
We have refactored DAO Fusion projects according to proposed changes. Old-style
constructors working with propertyPath/associationJoinType combination are now 
marked
as @Deprecated.

This is the first big API change since 1.1.x.

Original comment by Vojtech....@gmail.com on 1 Jun 2009 at 2:09

GoogleCodeExporter commented 9 years ago 
Changes committed into the trunk.

Original comment by Vojtech....@gmail.com on 2 Jun 2009 at 11:11