I see there are numerous messages on the list when people attempt to use 
scriptstep and receive noclassdef issues with the bsf javascript engine.

 

We don’t use the bat file to bootstrap things and I would actually think it is 
best practice not to.   This way when you plug webtest into something like 
cruisecontrol you are actually running the exact scenario as you would during 
normal testing…    It looks like the bat file just calls ant and dumps in the 
webtest/lib as bootstrap jars. anyways…..

 

I hit the noclassdef error and immediately just dumped the bsf, js, and commons 
logging jar into my ant_home/lib.   This effectively bootstraps.   The 
unfortunate side effect is that it also breaks my code generation during my 
build due to the use of different versions of those dependencies.

 

I guess my only other option now is to bootstrap my webtest build (e.g.   call 
ant with a default target which calls ant again and bootstraps the lib).  This 
is really ugly and I’d like avoid it.

 

A nice solution would be if the scriptstep would take a classpath as a 
subattribute.  That classpath could then include the necessary scripting 
engines……

 

Is there any other way around this?   I looked through my webtest.xml, but do 
not know enough about webtest to understand how the scriptstep populates its 
execution classpath.

 

 

 

Ruel Loehr

Configuration Management

 

Pointserve, Inc.

110 Wild Basin Road

Suite 300

Austin, Texas 78746

O: 512.617.5314

F: 512.617.0466

 


No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.503 / Virus Database: 269.16.10/1159 - Release Date: 11/29/2007 
11:10 AM
 

Reply via email to