Created attachment 33586 [details] screen Currently you can add a file in the file upload panel AND set a raw body post. The file upload panel (HTTPFileArgsPanel) is now a new tab Benefits Better screen space usage Add some validation to prevent incoherent configuration The file upload tab will be hidden by default.
PR https://github.com/apache/jmeter/pull/140 Please amend the new label if needed.
Date: Fri Feb 26 20:12:33 2016 New Revision: 1732554 URL: http://svn.apache.org/viewvc?rev=1732554&view=rev Log: Bug 59060 - HTTP Request GUI : Move File Upload to a new Tab to have more space for parameters and prevent incoherent configuration Contributed by Benoit Wiart #resolve #140 https://github.com/apache/jmeter/pull/140 Bugzilla Id: 59060 Modified: jmeter/trunk/src/core/org/apache/jmeter/resources/messages.properties jmeter/trunk/src/core/org/apache/jmeter/resources/messages_fr.properties jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/config/gui/MultipartUrlConfigGui.java jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/config/gui/UrlConfigGui.java jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/control/gui/HttpTestSampleGui.java jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/gui/HTTPFileArgsPanel.java jmeter/trunk/xdocs/changes.xml
The patch deprecated several items; however they are still used internally by non-deprecated code, and indirectly by non-deprecated code in other JMeter classes. So it's not possible to remove the deprecated items. Either the items are not supposed to be deprecated, or the code that uses them needs to be fixed to use whatever is intended to replace the deprecated code.
(In reply to Sebb from comment #3) > The patch deprecated several items; however they are still used internally > by non-deprecated code, and indirectly by non-deprecated code in other > JMeter classes. which one ?
(In reply to benoit.wiart from comment #4) > (In reply to Sebb from comment #3) > > The patch deprecated several items; however they are still used internally > > by non-deprecated code, and indirectly by non-deprecated code in other > > JMeter classes. > > which one ? This is easily found by an IDE, e.g. using Eclipse: Select a deprecated item, e.g. tableLabel Open Call Hierarchy This shows that the item is used by init() HTTPFileArgsPanel() UrlConfigGui.getParameterPanel() None of these are deprecated and all are in use. Similarly for the other deprecated items.
> This is easily found by an IDE, e.g. using Eclipse: thanx for the tip. I was using a punched card to develop jmeter. > Select a deprecated item, e.g. tableLabel > Open Call Hierarchy > This shows that the item is used by > init() > HTTPFileArgsPanel() > UrlConfigGui.getParameterPanel() You should not blindly rely on your IDE to do this kind of analysis. In your example it's perfectly possible to remove tableLabel without any impact on UrlConfigGui.getParameterPanel(). As tableLabel defaults to null and when it's null the component is not created see init(). tableLabel is not null only when used with the deprecated constructor. the deprecated constructor is only used by the deprecated MultipartUrlConfigGui Some of the methods/ fields were deprecated and not removed to let third party plugins provider adapt to the change.
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/3853