You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by Peter Lin <wo...@gmail.com> on 2005/09/02 15:46:17 UTC
another merge from HEAD to 2.1 branch
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
Re: another merge from HEAD to 2.1 branch
Posted by Peter Lin <wo...@gmail.com>.
I'll work on that tonight and tomorrow.
peter
On 9/3/05, sebb <se...@gmail.com> 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 <se...@gmail.com> 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 <ms...@apache.org> 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 <wo...@gmail.com> 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: jmeter-dev-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
Re: another merge from HEAD to 2.1 branch
Posted by sebb <se...@gmail.com>.
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 <se...@gmail.com> 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 <ms...@apache.org> 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 <wo...@gmail.com> 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: jmeter-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: another merge from HEAD to 2.1 branch
Posted by sebb <se...@gmail.com>.
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 <ms...@apache.org> 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 <wo...@gmail.com> 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: jmeter-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: another merge from HEAD to 2.1 branch
Posted by Michael Stover <ms...@apache.org>.
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 <wo...@gmail.com> 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: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: another merge from HEAD to 2.1 branch
Posted by Peter Lin <wo...@gmail.com>.
no, that hasn't been fixed. it requires enhancements to the converters to
save the data to CSV format.
peter
On 9/2/05, sebb <se...@gmail.com> wrote:
>
> I've just remembered - there was a problem with saving Monitor data as
> CSV - did that get fixed?
>
> S.
> On 02/09/05, Peter Lin <wo...@gmail.com> wrote:
> > nothing else comes to mind.
> >
> > peter
> >
> >
> > On 9/2/05, sebb <se...@gmail.com> 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 <wo...@gmail.com> 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: jmeter-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
Re: another merge from HEAD to 2.1 branch
Posted by sebb <se...@gmail.com>.
I've just remembered - there was a problem with saving Monitor data as
CSV - did that get fixed?
S.
On 02/09/05, Peter Lin <wo...@gmail.com> wrote:
> nothing else comes to mind.
>
> peter
>
>
> On 9/2/05, sebb <se...@gmail.com> 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 <wo...@gmail.com> 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: jmeter-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: another merge from HEAD to 2.1 branch
Posted by Peter Lin <wo...@gmail.com>.
nothing else comes to mind.
peter
On 9/2/05, sebb <se...@gmail.com> 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 <wo...@gmail.com> 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: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
Re: another merge from HEAD to 2.1 branch
Posted by sebb <se...@gmail.com>.
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 <wo...@gmail.com> 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: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org