hi rudy, (there was always the intention to find a more flexible solution. therefore referencing strategies are an internal concept and we just have to support the same syntax and behaviour. furthermore, i suggest that we also think about a typesafe alternative.)
concerning the mentioned constellation: i think there was a reason. however, we should have a look at it. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/3/30 Rudy De Busscher <[email protected]> > @ExtVal implementers > > Started to implement a prototype for the ReferenceResolver feature for the > next release of ExtVal. > > I studied LocalCompareStrategy, LocalPropertyChainCompareStrategy and > ELCompareStrategy to understand the current functionality and to unsure > backwards compatibility of the new code. > > I found out that LocalPropertyChainCompareStrategy doesn't call the > functionality in the CrossValidationHelper for the NON model case. The > other 2 strategies do. > It seems that the code is identical, except that the > LocalPropertyChainCompareStrategy doesn't use the outcome of > compareStrategy.useTargetComponentToDisplayErrorMsg method but always use > the target component to display the validation message. > > Was there a specific reason for this? Can I just call the code in > CrossValidationHelper for all strategies in the new system? > > Thx > regards > > Rudy >
