vlsi commented on issue #5895:
URL: https://github.com/apache/jmeter/issues/5895#issuecomment-1542499601
Here's an exception:
```
Caused by: java.lang.UnsupportedOperationException: Implement
getGUIComponentMetadata() in class org.apache.jmeter.config.gui.ArgumentsPanel
at
org.apache.jmeter.gui.JMeterGUIComponent.getLabelResource(JMeterGUIComponent.java:122)
at
org.apache.jmeter.gui.AbstractJMeterGuiComponent.getStaticLabel(AbstractJMeterGuiComponent.java:370)
at
org.apache.jmeter.gui.AbstractJMeterGuiComponent.initGui(AbstractJMeterGuiComponent.java:243)
at
org.apache.jmeter.gui.AbstractJMeterGuiComponent.init(AbstractJMeterGuiComponent.java:248)
at
org.apache.jmeter.gui.AbstractJMeterGuiComponent.<init>(AbstractJMeterGuiComponent.java:95)
at
org.apache.jmeter.config.gui.AbstractConfigGui.<init>(AbstractConfigGui.java:33)
at
org.apache.jmeter.config.gui.ArgumentsPanel.<init>(ArgumentsPanel.java:262)
at
org.apache.jmeter.config.gui.ArgumentsPanel.<init>(ArgumentsPanel.java:210)
at
org.apache.jmeter.config.gui.ArgumentsPanel.<init>(ArgumentsPanel.java:156)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
```
In other words, a "new-style" component `ArgumentsPanel` fails to
instantiate since its superclass accesses `getStaticLabel` right in the
superclass constructor.
Of course, we can't remove `getStaticLabel` method, and the superclasses
might indeed call `getStaticLabel`.
So the way out seems to be adding another constructor that will receive
`JMeterGUIComponentMetadata` parameter.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
