Datacage: Added <dc:filter> element. This allows cleaner way to narrow the datasets. Example: <dc:context> <dc:statement> SELECT DISTINCT name AS hws_name, official AS hws_official, kind_id AS hws_kind FROM hws_lines WHERE river_id = ${river_id} </dc:statement> <dc:if test="dc:has-result()"> <lines> <dc:macro name="hws-lines"> <dc:elements> <hws factory="hwsfactory" name="{$hws_name}"/> </dc:elements> </dc:macro> <dc:filter expr="$hws_official=1"> <dc:if test="dc:has-result()"> <official> <dc:filter expr="$hws_kind=1"> <dc:if test="dc:has-result()"> <Durchlass><dc:call-macro name="hws-lines"></Durchlass> </dc:if> </dc:filter> <dc:filter expr="$hws_kind=2"> <dc:if test="dc:has-result()"> <Damm><dc:call-macro name="hws-lines"></Damm> </dc:if> </dc:filter> <dc:filter expr="$hws_kind=3"> <dc:if test="dc:has-result()"> <Graben><dc:call-macro name="hws-lines"></Graben> </dc:if> </dc:filter> </official> </dc:if> </dc:filter> </lines> </dc:if> </dc:context>

syntax: regexp
flys-artifacts/target      # maven output
flys-artifacts/\.classpath # eclipse
flys-artifacts/\.project   # eclipse
flys-artifacts/\.settings  # eclipse
flys-artifacts/test-output # eclipse junit/testng plugin output
flys-backend/target      # maven output
flys-backend/\.classpath # eclipse
flys-backend/\.project   # eclipse
flys-backend/\.settings  # eclipse
flys-backend/test-output # eclipse junit/testng plugin output
flys-client/target      # maven output
flys-client/\.classpath # eclipse
flys-client/\.project   # eclipse
flys-client/\.settings  # eclipse
flys-client/test-output # eclipse junit/testng plugin output
flys-aft/target      # maven output
flys-aft/\.classpath # eclipse
flys-aft/\.project   # eclipse
flys-aft/\.settings  # eclipse
flys-aft/test-output # eclipse junit/testng plugin output
flys-client/src/main/webapp/OpenLayers-2.11
\.swp
\.swo