Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-jmeter Wiki" for change notification.
The following page has been changed by JMeterAdmin: http://wiki.apache.org/jakarta-jmeter/FutureReleases ------------------------------------------------------------------------------ * XPath Extractor - add user-declared namespaces * Rework HTTP GUI to make it easier to use and extend * JDBC IN/OUT/INOUT parameters - * File->Revert command, to easily reload existing file. This is implemented, but not committed to svn (Alf Hogemark) - * File->Open recent files command, bugzilla 31336 * Add HTTP methods dropdown to "SOAP/XML-RPC sampler", bugzilla 42637 * Remove unnecessary code duplication in "SOAP/XML-RPC sampler", rather use code inherited from HTTPSampler2. This is almost done, not committed to svn (Alf Hogemark) * Add unit tests for SOAP/XML-RPC sampler @@ -82, +80 @@ * Make a "HTTP Proxy Manager", where the user can specify what proxy settings to use * Then use would not have to edit jmeter.properties file or command line arguments to use a proxy * We could get rid of the "HTTP Proxy" settings in the "Webservice(SOAP) sampler" + * Could perhaps just extend HTTP Defaults for this? + * N.B. HTTP (Java) relies on system properties to define proxy items, so it is impossible to have more than one setting. * Make new, nice?, icons for the GUI elements which currently do not have a unique icon. For example the post and preprocessors. * Would make it a lot easier to see what is what in the tree * Make menu options more context sensitive, so they are only enabled when they make sense @@ -118, +118 @@ * Or perhaps SL4J - http://www.slf4j.org/ * What are the risks with continuing to use Avalon, if Avalon is not maintained anymore ? * Remark: Http``Components project is considering migrating Http``Client 4.0 branch off Commons Logging to another logging framework as Commons Logging currently appears unmaintained and the prospects of its further development remain unclear. [Does it need any development? sebb] It may be worthwhile to ensure both projects use the same logging framework / compatible logging frameworks. [Agreed: sebb] - * Move development to the "trunk" of the Subversion repository * Upgrade to httpclient4 ? httpclient4 is still only in Alpha. Should / could we have one sampler class using httpclient3 and one httpclient4 ? * Remove some code in HTTPSampler, which is there fore workaround for httpclient3.0 bug, which has been fixed in httpclient3.1 * Reorganise documentation @@ -179, +178 @@ * Add SVN revision number to version? - or at least to Manifests. * Consider migration to Maven2 as a build tool for JMeter. This should help simply dependency management and facilitate the use of JMeter for automatic load testing / integration into tools like [http://maven.apache.org/continuum/ Continuum] * Maven 1 was tried a couple of years ago, and seemed incompatible with the JMeter directory layout and multiple jars; hopefully Maven 2 is more flexible. + * If Controller - allow functions and variables as alternative to Javascript = Release strategy = @@ -192, +192 @@ This will be the next release. + The following have been implemented: + + * File->Revert command, to easily reload existing file. + * File->Open recent files command, bugzilla 31336 + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
