> There should be no need for extra code to make non-GUI mode work; however, > it is important that the GUI-only code does not perform any work other > than > updating the display from the properties and vice-versa.
Seb - In my case, the LoadPropertiesElementGui does *not* have a LoadPropertiesElement counterpart in the /config subdirectory above /config/gui/. Instead LoadPropertiesElementGui reads properties and sets JMeter variables using Arguments in /config/. Is it the case that when JMeter runs with the -n option, the classes under the /gui subdirectory do not get executed? This is now just curiosity. My efforts took too much time, so I've started using __P as you recommended. :-] Works fine. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] > -----Original Message----- > From: BAZLEY, Sebastian [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 6 January 2004 11:48 PM > To: 'JMeter Developers List' > Subject: RE: Problems with argument persistance in a JMX > > I've not used the enhancement. > > [We use the __P() and __property() functions which work fine in non-GUI > mode. These seem to do everything we need.] > > == > > I have seen the problem with test plans that appear to "change" - this is > a > known bug (http://issues.apache.org/bugzilla/show_bug.cgi?id=25441) > > == > > There should be no need for extra code to make non-GUI mode work; however, > it is important that the GUI-only code does not perform any work other > than > updating the display from the properties and vice-versa. > > There are normally two Java files for each test element; one to handle the > GUI, and another to do the common stuff. > > S. > -----Original Message----- > From: Sonam Chauhan [mailto:[EMAIL PROTECTED] > Sent: 06 January 2004 03:27 > To: '[EMAIL PROTECTED]' > Subject: Problems with argument persistance in a JMX > > > Hello - I recently coded a small enhancement to JMeter - a "Load > Properties > Element" ( see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25815 ) > > I noticed this in JMXs that used this element: > - when run from the GUI, the element works fine and loads runtime > properties > > - when run from the command line, the element does *NOT* load runtime > properties > > Note, my enhancement is essentially one file: > LoadPropertiesElementGui.java > located in the *gui* directory: > /src/core/org/apache/jmeter/config/gui > It uses Arguments following a hint Jordi had given. > > Do there need be separate Java classes for running in *non*-GUI mode? > > As I said before, When I run a test with this element the JMeter GUI, this > element works fine. But when I clicked 'exit', JMeter asks if I "want to > save changes" (even though I just ran the test without modification). > > I normally choose no. If I choose clicked "yes", JMeter saves the loaded- > up > properties in the JMX. E.g.: > -------------------------------------- > <node> > <testelement class="org.apache.jmeter.config.Arguments"> > ... > <collection class="java.util.ArrayList" ...> > ... > <testelement class="org.apache.jmeter.config.Argument" > name="MYPROPERTY"> > <property xml:space="preserve" ...>=</property> > <property xml:space="preserve" ...>5</property> > ------------------------------------------------------ > It then uses *these* saved properties, no matter what properties are > passed > in at runtime. > > With regards, > Sonam Chauhan > -- > Corporate Express Australia Ltd. > Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
