Hi Matt,
You should be able to increase the logging level in the log4j properties
file probably in lib folder.
I sometimes get this type of problem if I've turned javascript error
checking off in webtest and then there is an error which means the
javascript that clicks that link is not loaded and so doesn't run. Have you
turned jscript error checking off?
cheers,
John
On 8/28/07, mraible <[EMAIL PROTECTED]> wrote:
>
>
> Is it possible to crank up logging to see why clicking the link is
> failing?
> Like I said, I haven't changed any code and it worked with the previous
> release.
>
> Thanks,
>
> Matt
>
>
> mraible wrote:
> >
> > I'm trying to upgrade from R_1454 to R_1600. With 1454, I had a JSF
> > dataTable that used a commandLink to edit a record. This command link
> > would submit a JavaScript form. For some reason, this is no longer
> working
> > with R_1600. There's no error or anything, it just never makes it to my
> > edit page. Any ideas?
> >
> > The content of the generated HTML hasn't changed.
> >
> > Thanks,
> >
> > Matt
> >
>
> --
> View this message in context:
> http://www.nabble.com/Upgrading-from-R_1454-to-R_1600-tf4319687.html#a12354180
> Sent from the WebTest mailing list archive at Nabble.com.
>
> _______________________________________________
> WebTest mailing list
> [email protected]
> http://lists.canoo.com/mailman/listinfo/webtest
>
