Done.

Ran through this test.  The test is misleading as the reason why it's getting and expecting a 405 is because a GET is being performed on the path "/" and this path has no GET method access allowed in the wadl.  I added "/" to the WADL and this passes with a 200.  Moved this test up to the scenario above which asserts it does get through as expected and the extra ? is properly encoded.