Documentation, provide example of static @{...} Query String values

[dlmiles]

Documentation Enchancement.

In the section covering href/src/URL rewriting there is no example showing some common requirements:

The section should cover more examples of possible uses that a developer might come across.

Some of these points may not be simple documentation fixes but need features adding, however the documentation should show or indicate how it is possible or the fact it is not possible for each requirement.

• Static parameters, @{/dir/file.foo(name1='value1',name2='value2')} this is non-obvious to the new user, the name is not quoted but the value needs to be. I think including one example of such would make it more clear to a new user.
• Name only, no value ? Is this allowed @{/dir/file.foo(name1,name2) ? or documentation covering how to achieve it. Again a single example showing it as possible.
• Multiple parameters with the same name ? Is this allowed @{/dir/file.foo(name1='value1',name1='value2') or documentation covering how to achieve it.
• Dynamic parameters names ? is this possible at all to put an expression on the left hand side? Using an expression on the left hand side like @{/dir/file.foo(${foobar.foo}='fixedString').
• Optional parameter (single name/value pair), maybe this could be a special Java type/interface that when used is as the result of an expression has getName() getValue() isOmit(). 'Optional' means that the name/value may or may not exist in the final output. Some kind of expression is needed to decide to emit or omit.
• Optional parameters (multiple name/value pairs). Same as the above but with ability to return multiple name/value pairs from a single expression. Maybe an Array or Collection or the special Java type/interface returned from an expression.