I'll work on that tonight and tomorrow. peter
On 9/3/05, sebb <[EMAIL PROTECTED]> wrote: > > All the 2.0.3 classes now load in JMeter 2.1 including the JDBC configs: > I extended the "update.properties" processing. This now allows for > some ConfigTestElements which need to change into different classes > depending on the associated GUI class. Not as difficult as I thought. > > Though of course the code creates separate JDBC config elements for > the Pool and DB configs when ideally they should be combined. > > I've also created screenshots for all the test elements. > > The Access Log Sampler documentation is a bit out of date - the > parsers and filter need to be described - Peter, would you be able to > update this? > > Also the JUnit sampler needs some documentation and a screenshot - please! > > The nightly build has been updated. > > S. > On 02/09/05, sebb <[EMAIL PROTECTED]> wrote: > > IIRC the old sampler had a lot of information in it that is now in the > > config elements, so that would need to be included as well. > > > > Cut and paste between two test elements in the same JMeter instance > > would be pretty tedious, given the number of different fields that > > there are. > > > > It would be easier to open two JMeter instances. > > > > S. > > On 02/09/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > > What if we put the DbConfigGui and PoolConfig classes back in, but > made > > > them "deprecated" and always disabled. That way, people could at least > > > load them and copy/paste their info from it to the new element. And do > > > something to prevent these element from showing up in dropdowns - some > > > sort of isDeprecated method or something like that. > > > > > > I think that might be easier than trying to do something smarter > > > automatically. > > > > > > -Mike > > > > > > On Fri, 2005-09-02 at 15:15 +0100, sebb wrote: > > > > I'm assuming we need to fix the JDBC test plan bug: > > > > > > > > http://issues.apache.org/bugzilla/show_bug.cgi?id=36449 > > > > > > > > for 2.1.1. > > > > > > > > I've made some progress on this, but the upgrade.properties changes > > > > aren't yet complete - indeed I'm not sure that it can handle the > > > > merging of two JDBC config elements. Might need to handle JDBC > > > > specially... > > > > > > > > Anything else vital? > > > > > > > > S. > > > > On 02/09/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > > > > Once we get a patched release of 2.1 out, I want to merge the > include > > > > > controller to the 2.1 branch so that people can use it without > jdk1.5. > > > > > > > > > > peter > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
