Please rename this issues to
Fail to run Selenium RC scripts on grid

Added screenshot of Grid page for 2.15.0 which selenium is looking for: [Selenium2-10+RC_Error.jpg]

Broken backward compatibility of Selenium 2 with selenium 1?

Comparison of selenium-server versions 2.9.0 and 2.15.0 shows that 
selenium-server had lost listening on /selenium-server/driver path of the grid2. 

See attached screenshot with different 2.15.0 and 2.9.0 grid sessions [Selenium2-9vs15_Comparison]

Note: Actually, this feature have been lost since version selenium-server 2.10.0.

Possible solution: adding a simple redirect from "/selenium-server/driver" to "/wd/hub"
in selenium server probably may resolve the issue...

All active development is focused on Selenium 2.0 (the WebDriver APIs).  Updating issue
priority accordingly.

I realize a fix for this issue isn't forthcoming in the 2.16.0 timeframe, but should
I expect a fix soon after that?  2.17.0 perhaps?  Basically, I just want to know if
I should go another way (2.9.0 and earlier) if this is going to be a low priority indefinitely.

While WebDriver is a priority, we need to keep the RC's working imo.  The fact that
the RC's haven't worked since 2.9 is pretty scary.  The longer this waits the farther
reaching the implications may be.  I look forward to when this is fixed and i can upgrade
our company's grid from 2.9.

Has this issue been resolved in the 2.17 release from the 16th ?

No, 2.17 also has this issue. Are there any plans to fix this? This means that you cannot
use the Selenium grid with Selenium 1 clients!

This is still an issue in 2.19.  Any comments from the developers?  Did it work in 2.9?
 We are setting up a new grid deployment with significant amounts of time invested
with selenium 1 scripts. Are the significant differences between server 2.9 and 2.19?

You may try to use the latest server (2.19 now) and RC version 2.9: it works in my environment,
shows correct identification for that RC client as "SeleniumRemoteProxy".

(I am just a user of this system, not a developer :)

I noticed that the API changed which may be the issue I'm facing.  Haven't tested yet
though.  In 2.9, when configuring an RC node you give it the role RC, but looks like
the docs now specify role node.  It states its backwards compatible, but it doesn't
seem to work for "rc" only "wd".

To make Selenium 1 work with Selenium 2 Grid, 
I use:
Hub: one of the latest version for Hub (2.15.0);
RC: version 2.9.0 with "-role rc", to make Selenium grid understand that it has SeleniumRemoteControl.
Command line example:

Java -jar selenium-server-standalone-2.9.0.jar -role rc -nodeTimeout 180  -hubHost
grid -hubPort 4444 -hub http://grid:4444/grid/register  -host rchost -port 5588 -browser
"browserName=*firefox,maxInstances=5,platform=WINDOWS"  -firefoxProfileTemplate "C:\sem\ff\ff4selenium"
-browser "browserName=*iehta,maxInstances=3,platform=WINDOWS"

The grid console shows SeleniumRemoteProxy at 
Address: http://grid:4444/grid/console

Grid Hub 2.15.0
---------------------------------------
SeleniumRemoteProxy
listening on http://rchost:5588
test session time out after 300 sec.
Supports up to 5 concurrent tests from: 
(f)(f)(f)(f)(f)(ie)(ie)(ie)
---------------------------------------

Test scripts are written on python, and the use and code is as described for Selenium
1.

But, unfortunately, this version of Selenium, 2.9.0, does not work with Firefox over
version 7 and Internet Explorer having version over 8: fails to test IE9, FF8, FF9...

So we had to start porting all our Selemiun1 (Python) based test code to Selenium 2
WebDriver (Java) to be able to test FF9 and IE9. And this is really time consuming
task as there is no WebDriver-Backed Selenium-RC for Python yet. Actually, all the
work was started from the scratch...

I wound up converting all of my existing tests to use WebDriver, which was very time
consuming.  What's somewhat maddening is that it would probably take a lot less time
to just fix this bug.  At least where I work, when you break core functionality, you
fix it before moving on to something else instead of lowering the priority and sticking
your head in the sand.  

Hello, guys! A have some surprise for you! See https://github.com/dirzhov/Python-WebDriver-Backed-Selenium-RC
You can join the development!

Hi all, to get the Grid Node work with Selenium RC (ie. so that it responds to /selenium-server/driver
instead of /wd/hub), ensure that the node is launched with a browser argument that
includes 'seleniumProtocol=Selenium', eg.

Java -jar selenium-server-standalone-2.15.0.jar -role rc -hubHost localhost -browser
 browserName=*firefox,version=12,platform=MAC,seleniumProtocol=Selenium

I've tested this in Selenium 2.25.0, but not sure if this applies to older versions
or not...

I can't get Grid working with RC. All requests to /selenium-server/driver return:

HTTP ERROR: 500

Problem accessing /selenium-server/driver/. Reason:

    java.lang.NullPointerException


HUB START:
 java -jar selenium-server-standalone-2.28.0.jar -role hub

NODE START:
java -jar selenium-server-standalone-2.28.0.jar -role node -hub http://127.0.0.1:4444/grid/register



So does Selenium support running RC under grid? I have 1000+ RC tests to support, so
"porting to webdriver" is not a viable solution at this point.

# To install the Python client library:
# pip install -U selenium

When I execute this sample pyhton code,I get the following error 
"SyntaxError: multiple statements found while compiling a single statement" How do
I resolve this..

# Import the Selenium 2 namespace (aka "webdriver")
from selenium import webdriver




# Google Chrome
driver = webdriver.Chrome()

# Firefox
driver = webdriver.Firefox()

# ------------------------------
# The actual test scenario: Test the codepad.org code execution service.

# Go to codepad.org
driver.get('http://codepad.org')

# Select the Python language option
python_link = driver.find_elements_by_xpath("//input[@name='lang' and @value='Python']")[0]
python_link.click()

# Enter some text!
text_area = driver.find_element_by_id('textarea')
text_area.send_keys("print 'Hello,' + ' World!'")

# Submit the form!
submit_button = driver.find_element_by_name('submit')
submit_button.click()

# Make this an actual test. Isn't Python beautiful?
assert "Hello, World!" in driver.get_page_source()

# Close the browser!
driver.quit()

This issue should be fixed by revision 8301806b3af6 and the fix is available in version
2.30+

If the issue is still actual please ask to reopen.

The issue is still actual in version 2.33

and 2.44