Although this is really a problem with the Selenium RC jar, I thought I'd post it here as well since there is some discussion on this sight about later releases of Tellurium not using Selenium but a Tellurium specific proxy server instead.
Here is the problem: I wrote a Tellurium test to be run from within Grails during grails 'integration' test phase. During integration testing Grails first starts its own embedded Jetty server. However with the Selenium RC jar in the class path, this fails because the Selenium jar embeds a subset of an older version of the Jetty class library in its own jar. If the selenium jar precedes the jetty jar in the class path, Grails can't start its own server. If the jetty jar precedes the selenium jar, the selenium server start fails. Grails 1.1.1 ships with the Jetty 6.1.14 jars My current work around for this was to modify Tellurium source. Instead of launching the Selenium embedded server in the same JVM, I do a Runtime.exec to lauch the server as an external process. This seems to work intermittently, I think I may be having some timing problems in that the Telluruium client needs to wait some unknown number of seconds until the Selenium server is up and listening on port 4444. Just thought I'd share this info. -- You received this message because you are subscribed to the Google Groups "tellurium-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tellurium-users?hl=.
