RemoteServlet spelling error on getWindowHandle

[GoogleCodeExporter]

trunk/remote/server/src/java/org/openqa/selenium/remote/server/DriverServlet.jav
a

Lines 112, and 114, exists a spelling mistake which causes
getWindowHandle/getWindowHandles() to fail when using the RemoteDriver.

sessioId should be sessionId:

    getMapper.bind("/session/:sessioId/:context/window_handle",
GetCurrentWindowHandle.class)
        .on(ResultType.SUCCESS, new JsonResult(":response"));
    getMapper.bind("/session/:sessioId/:context/window_handles",
GetAllWindowHandles.class)
        .on(ResultType.SUCCESS, new JsonResult(":response"));

becomes:

    getMapper.bind("/session/:sessionId/:context/window_handle",
GetCurrentWindowHandle.class)
        .on(ResultType.SUCCESS, new JsonResult(":response"));
    getMapper.bind("/session/:sessionId/:context/window_handles",
GetAllWindowHandles.class)
        .on(ResultType.SUCCESS, new JsonResult(":response"));

What steps will reproduce the problem?
1. Create a RemoteDriver test
2. Call driver.getWindowHandle() on the test and watch it throw an exception

What is the expected output? What do you see instead?

Handle name is expected, instead an exception occurs.

What version of the product are you using? On what operating system?

r685, on OS X, Windows XP, and Linux Fedora 10. 

The problem also exists in trunk.

Original issue reported on code.google.com by smith.no...@gmail.com on 11 Feb 2009 at 12:50

[GoogleCodeExporter]

Also occurs in: HttpCommandExecutor.java

    nameToUrl.put("getCurrentWindowHandle", new
CommandInfo("/session/:sessioId/:context/window_handle", HttpVerb.GET));
    nameToUrl.put("getWindowHandles", new
CommandInfo("/session/:sessioId/:context/window_handles", HttpVerb.GET));

Original comment by smith.no...@gmail.com on 11 Feb 2009 at 12:54

[GoogleCodeExporter]

Sorry, wrong project. Please delete.

Original comment by smith.no...@gmail.com on 11 Feb 2009 at 5:58

[GoogleCodeExporter]

Hi, i dont know where you want to report this, but here you are absolutely 
wrong.

This is a components for Microsoft .Net based on a component which was written 
for
Ruby. So there is no java involved at all. 

Original comment by lanwin...@gmail.com on 11 Feb 2009 at 5:58

• Changed state: Invalid