GitHub user max3163 opened a pull request:
https://github.com/apache/jmeter/pull/241
Support variable for all JMS messages (bytes, object, ...) and sources
(file, folder)
Source code is based on Java 8 and unit tests has been added. Message
format processing has been moved to a dedicated package, same for cache support.
An encoding field has been added to UI. It is by default filled with two
special values (<RAW>, <DEFAULT> and [standard
charsets](https://docs.oracle.com/javase/8/docs/api/index.html?java/nio/charset/StandardCharsets.html)).
<RAW> acts exactly as current version. No variable support and load files
with default system charset. <DEFAULT> mode applies default system one, except
for XML which relies on XML prolog. In other cases, the specified encoding is
use whatever it is valid or not.
Cache system use a single field in PublisherSampler, so explicit type of
cached content is not known. It may be improved (replaced ?) by using Guava
instead. Cached content isn't consistent for a message type (bytes, object,
...) but also depends if raw mode is used or not. For all non-raw mode, text is
always cached to permit variable processing for each sampler execution.
Two new components were added to JMeter test API:
* ResourceLocator: enables to locate a resource file and give a NIO Path or
String one. Relying on pure URL causes problem with path containing some
special characters such as space (%20). It solves an existing problem on
current code base.
* JMeterContextServiceHelper: it consits in a [JUnit
rule](https://github.com/junit-team/junit4/wiki/Rules) implementation to manage
thread-bound singletons of JMeterContext. See TextMessageRendererTest for an
example usage.
Special notes: in order to check encoding management, test resources
encoding must be preserved. By default, all files are in UTF-8 ; except for:
cp1252.txt, object_cp1252.txt, object_prolog_cp1252.xml,
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/max3163/jmeter POW-322
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jmeter/pull/241.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #241
----
commit 36dd9f7ec959c69e06b7bf52f2ddb5866d822797
Author: Bruno Demion <milam...@apache.org>
Date: 2016-11-16T18:45:11Z
Tag for pre-release
git-svn-id: https://svn.apache.org/repos/asf/jmeter/tags/v3_1_RC4@1770033
13f79535-47bb-0310-9956-ffa450edef68
commit 0b5b61f85c494dedd43ac1648bec96c92a6af33e
Author: Bruno Demion <milam...@apache.org>
Date: 2016-11-19T22:49:23Z
Vote succeeded, create the 3.1 tag
git-svn-id: https://svn.apache.org/repos/asf/jmeter/tags/v3_1@1770529
13f79535-47bb-0310-9956-ffa450edef68
commit b2062f8defb5607b64d998c972f158a4d03e31c5
Author: Logan Mauzaize (T524467) <lomauza...@airfrance.fr>
Date: 2016-12-19T17:17:03Z
POW-322 Adds encoding selection for JMS publishing
commit d77b5dc0ddfe4aab797fdad71937795248475e20
Author: Logan Mauzaize (T524467) <lomauza...@airfrance.fr>
Date: 2016-12-21T10:50:39Z
POW-322 Adds variable support for file source with JMS publishing
commit 4322511111b83dee637a28bf36880b5ba1c09e12
Author: Logan Mauzaize (T524467) <lomauza...@airfrance.fr>
Date: 2016-12-21T16:36:29Z
POW-322 Upgrades java version
commit 9a5a88d1af806726d01c78980e515f69246ccdad
Author: Logan Mauzaize (T524467) <lomauza...@airfrance.fr>
Date: 2016-12-22T08:22:52Z
POW-322 Fixes resource lookup
commit 5c006fe9209b25b39cb10eed66b222d63e61b047
Author: Logan Mauzaize (T524467) <lomauza...@airfrance.fr>
Date: 2016-12-22T08:46:38Z
POW-322 Uses HTTPS for checkstyle location
commit 610fc24e4d33fdf92235b936a611190bd8a648c0
Author: Logan Mauzaize (T524467) <lomauza...@airfrance.fr>
Date: 2016-12-22T08:50:32Z
POW-322 Fixes checkstyle errors
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
