[OWASP-WEBSCARAB] Re: Bug in latest build
lists at dawes.za.net
Mon Mar 7 13:44:14 EST 2005
Jesse Burns wrote:
> Hey Rogan,
> So I have developed some scripts in bean shell, and I have found that
> proguard is removing methods that are part of the model (like
> Message.getHeaderNames()) but not used by the application. The lack of
> these methods is confusing (to see that they are gone I had to
> disassemble the jar file, and in custom - non-proguard builds they work
> fine). You may wish to tone down the use of proguard for model objects,
> or other things bean scripters may wish to call. Personally I don't see
> why the size reduction is important - but I am not paying the bandwidth
> charges for downloads.
thanks for the bug report.
In fact, I was just using ProGuard to identify unused classes, because
it reads from a large number of library jars.
But I will change the proguard configuration to not remove methods of
classes that are used.
What kind of scripts are you writing? Do you need any more functionality
in WebScarab itself to support them?
For what it is worth, you can also call the ManualEditFrame
editRequest(Request) and editResponse(Request, Response) methods from
your script, if you want to. They should be thread safe, and block and
*ALL* messages to discard at dawes.za.net will be dropped, and added
to my blacklist. Please respond to "lists AT dawes DOT za DOT net"
More information about the Owasp-webscarab