For those of you reading along at home, the solution I found to this problem
was to add
<j:set var="descriptor" value="${it.descriptor}"/>
into the jelly file where the form is declared, as suggested in a response to a
similar query in this group.
Sorry for the distraction!
Ninian
On Sunday, June 15, 2014 5:40 PM, 'Ninian Harvey' via Jenkins Developers
<[email protected]> wrote:
Just to ask this question a different way, to see if it provokes any interest,
we’re trying to follow the Jelly form controls page
(https://wiki.jenkins-ci.org/display/JENKINS/Jelly+form+controls)
in the section
"Select (drop-down menu) with model filled values"
which says that we need to implement a method doFillXXXItems() in the
descriptor of your Describable instance.
Now, the claim action extends
TestAction(https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/junit/TestAction.java),
and we want to put the user drop down in the summary.jelly shown on the detail
of a build.
Trying to follow the model I can see elsewhere I created a class which was a
TestAction that implemented Describable, and also had its own descriptor, as
per the below DescribableTestAction code snippet
This all seemed to fit the model so far as I can see, but the doFillAssignee()
method is not called, and indeed the drop down list contains no entries. So I
must be missing something about how this all is wired together. Does anyone
have any hints on what we really need to do?
thanks
Ninian
DescribableTestAction snippet:
public abstract class DescribableTestAction extendsTestAction implements
Describable<DescribableTestAction> {
public static final DescriptorImpl DESCRIPTOR = new DescriptorImpl();
public Descriptor<DescribableTestAction> getDescriptor() {
return DESCRIPTOR;
}
@Extension
public static final class DescriptorImpl
extendsDescriptor<DescribableTestAction> {
@Override
public String getDisplayName() { return "Assignee"; }
public ListBoxModel doFillAssigneeItems() {
ListBoxModel items = new ListBoxModel();
for (User u : User.getAll()) {
items.add(u.getDisplayName(), u.getId());
}
return items;
}
}
}
On Tuesday, June 3, 2014 10:23 PM, Marc Carter <[email protected]> wrote:
This isn't actually about the user list aspect. The issue here is how does one
define a Descriptor (which has that nice autofillXXX pattern we can implement
with code similar to Ioannis') for the ClaimBuildAction. It doesn't seem to fit
the usual pattern and I can't guess my way into it.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
