Ah, I found the reason of this problem reported in my last reply. It
was true in the property "runInternally" (in embedded server in the
file TelluriumConfig.groovy). If I started selenium server manually, I
have to switched the property to false. So I did that and got
successful results without some exceptions. I have tested Tellurium
0.5.0 for Selenium 1.0 Beta 2 and Groovy 1.5.7.

What should you do, if you want to that the selenium server starts
automatically?

Greetz

Thomas

On Feb 6, 9:36 am, Thomas Roßberg <[email protected]> wrote:
> Hello,
>
> the passage "widget" didn't exist in my TelluriumConfig.groovy file.
> Because this passage wasn't mentioned in the project site. Should I
> post this passage into this file? I'm trying to do this, now.
>
> Greetz,
>
> Thomas
>
> On Feb 5, 7:17 pm, [email protected] wrote:
>
> > rossiweb,
>
> > Seems it complains about this following method,
>
> > org.tellurium.widget.WidgetConfigurator.configWidgetModule()
>
> > Please show us your TelluriumConfig.groovy file, especially for this
> > following section
>
> >     widget{
> >         module{
> >             //define your widget modules here, for example Dojo or
> > ExtJs
> > //            included="dojo, extjs"
> >             included=""
> >         }
> >     }
>
> > Also, we did not test Tellurium 0.5.0 for Selenium 1.0 Beta 2 and
> > Groovy 1.5.7. Please
> > use Selenium 0.9.2 and Groovy 1.5.6 for Tellurium 0.5.0 instead.
>
> > Our trunk code is upgraded to use Selenium 1.0 Beta 2 and Groovy 1.6
> > RC2.
>
> > Haroon, please try to re-produce this problem in his environment.
>
> > Thanks,
>
> > Jian

--~--~---------~--~----~------------~-------~--~----~
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=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to