There is a lonh mail thread on that topic. Recurring multiple times is the only way to resolve entries that may point to entries that to be resolved/filtered again. Additionally your summary of behaviour is not correct: in case where during a filter cycle no change was detected the loop stops immedeately. The loop only runs to the maximum in case 2 filters change a value with the same key so the other filter is changing it back in a way it is targeting the first filter again in the next run. Definitivly an edge case, but to be aware of to prevent endless looping. All this fuctionality works fine and is also tested.
Cheers Anatole Romain Manni-Bucau <[email protected]> schrieb am Do., 5. Feb. 2015 um 18:03: > that's what we discussed no? > > > Romain Manni-Bucau > @rmannibucau > http://www.tomitribe.com > http://rmannibucau.wordpress.com > https://github.com/rmannibucau > > > 2015-02-05 17:58 GMT+01:00 Oliver B. Fischer <[email protected]>: > > Hi, > > > > while writing tests I stumpled over our PropertyFilter and it > application to > > the properties provided by the property sources. > > > > I expected that each property will be overhanded once to each filter. > But in > > our application each property is overhanded to all filters again and > again. > > This stops only if the property is unchanged after applying all filters > or > > it max passed 10 times to all filters. > > > > WDYT? > > > > Bye, > > > > Oliver > > > > -- > > N Oliver B. Fischer > > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > > P +49 30 44793251 > > M +49 178 7903538 > > E [email protected] > > S oliver.b.fischer > > J [email protected] > > X http://xing.to/obf > > >
