Route nesting is possible and often desirable as it helps to:
Factor common parameters in a common rule.
Perform more efficient matching as the match of the common rule is done once for all the sub routes.
<route path="/foo">
<route-param qname="gtn:handler">
<value>portal</value>
</route-param>
<route path="/bar">
<route-param qname="gtn:path">
<value>bar</value>
</route-param>
</route>
<route path="/juu">
<route-param qname="gtn:path">
<value>juu</value>
</route-param>
</route>
</route>
The request path "/foo/bar" is mapped to the (gtn:handler=portal,gtn:path=bar) map.
The request path "/foo/juu" is mapped to the (gtn:handler=portal,gtn:path=juu) map.
The request path "/foo" is not mapped as non leaf routes do not perform matches.