[JIRA] (JENKINS-57807) Stapler JS proxy not correctly created for classes implementing StaplerProxy

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner created an issue

Jenkins / JENKINS-57807 Stapler JS proxy not correctly created for classes implementing StaplerProxy Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-05-31 22:22 Priority: Minor Reporter: Ulli Hafner If a method of a Stapler model object *S* is annotated with @JavaScriptMethod then code to access this method using an Ajax call is automatically generated. If the model object implement StaplerProxy and thus delegates all UI logic to a new object *P* of a different class then the invocation of the @JavaScriptMethod (that is now part of the class *P) does not work anymore. In order to get this working again, one needs to add an additional empty method In the class **S* that is also marked with @JavaScriptMethod. See [ChangeLog of warnings plugin 5.1.0](https://github.com/jenkinsci/warnings-ng-plugin/compare/warnings-ng-5.0.0...warnings-ng-5.1.0) for details. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-57807 Stapler JS proxy not correctly created for classes implementing StaplerProxy

Change By: Ulli Hafner If a method of a Stapler model object * * S* * is annotated with {{@JavaScriptMethod}} then code to access this method using an Ajax call is automatically generated. If the model object implement {{StaplerProxy}} and thus delegates all UI logic to a new object * * P* * of a different class then the invocation of the {{@JavaScriptMethod}} (that is now part of the class * * P* * ) does not work anymore. In order to get this working again, one needs to add an additional empty method In the class * * S* * that is also marked with {{@JavaScriptMethod}}.

See [ChangeLog of warnings plugin 5.1.0](https://github.com/jenkinsci/warnings-ng-plugin/compare/warnings-ng-5.0.0...warnings-ng-5.1.0) for details.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-57807 Stapler JS proxy not correctly created for classes implementing StaplerProxy Change By: Ulli Hafner

If a method of a Stapler model object *S* is annotated with {{@JavaScriptMethod}} then code to access this method using an Ajax call is automatically generated. If the model object implement {{StaplerProxy}} and thus delegates all UI logic to a new object *P* of a different class then the invocation of the {{@JavaScriptMethod}} (that is now part of the class *P*) does not work anymore. In order to get this working again, one needs to add an additional empty method with the same name in the class *S* that is also marked with {{@JavaScriptMethod}}. See [ChangeLog of warnings plugin 5.1.0 ]( | https://github.com/jenkinsci/warnings-ng-plugin/compare/warnings-ng-5.0.0...warnings-ng-5.1.0 ) ] for details.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-57807 Stapler JS proxy not correctly created for classes implementing StaplerProxy Change By: Ulli Hafner

If a method of a Stapler model object *S* is annotated with {{@JavaScriptMethod}} then code to access this method using an Ajax call is automatically generated. If the model object implement {{StaplerProxy}} and thus delegates all UI logic to a new object *P* of a different class then the invocation of the {{@JavaScriptMethod}} (that is now part of the class *P*) does not work anymore. In order to get this working again, one needs to add an additional empty method In with the same name in the class *S* that is also marked with {{@JavaScriptMethod}}. See [ChangeLog of warnings plugin 5.1.0](https://github.com/jenkinsci/warnings-ng-plugin/compare/warnings-ng-5.0.0...warnings-ng-5.1.0) for details.

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck updated an issue

Jenkins / JENKINS-57807 Stapler JS proxy not correctly created for classes implementing StaplerProxy

Change By: Daniel Beck Labels: stapler

Add Comment