In my views I have a method
public void doSave(final StaplerRequest request, final
StaplerResponse response) {
which is called when pressing save
<f:form method="post" action="save" name="Save">
[...]
<f:entry title="">
<input type="submit" name="Submit'" value="${%Save}"
class="submit-button" />
</f:entry>
What is the Stapler URL trace?
Ulli
On 05/21/2012 11:54 AM, jrusnack wrote:
> Yes, I will resort to moving those option to Edit View, but if it`s
> possible, I would like to have some minimum amount of interactive
> selection right under graph.
>
> And yes, do method in ReportPluginPortlet class is not called, and
> that is what I would like to achieve.
>
> On May 21, 11:45 am, Ullrich Hafner <[email protected]> wrote:
>> I see. Wouldn't it be better if all Jenkins portlets behave in the same
>> way, i.e. only in edit view there are configurable (and so the edit part
>> will take space from the actual graph)?
>>
>> What I don't understand is why you don't delegate to your code from the
>> portlet? Is the do method not called?
>>
>> Ulli
>>
>> On 05/21/2012 11:29 AM, jrusnack wrote:
>>
>>
>>
>>
>>
>>
>>
>>> My plugin generates trend graph with test results and I use textboxes
>>> and drowdown lists to configure this graph. Configuration options
>>> include: how many builds to include in report (or which), which
>>> configurations should be included, even groovy expression for
>>> filtering matrix configurations that should contribute results to
>>> trend graph. All these are right below graph (all part of portlet), so
>>> user can choose what he wants to see interactively. Problem is
>>> submitting these to my plugin, not dashboardView. Obviously, by moving
>>> these options to Edit View, I loose interactivity I want to achieve.
>>> On May 21, 11:16 am, Ullrich Hafner <[email protected]> wrote:
>>>> I'm not sure if I understand your use case - maybe you need to
>>>> elaborate: the dashboard portlets already provide an extensible UI for
>>>> the configuration. What extra buttons and views do you want to show?
>>>> Ulli
>>>> On 05/21/2012 10:19 AM, jrusnack wrote:
>>>>> Hi,
>>>>> I am working on plugin that will show some trends and statistics and I
>>>>> also want ability to add it to dasboard (DashboardView plugin). Also,
>>>>> I need buttons and forms that will control what statistics and trend
>>>>> graphs are displayed. I am able to extend dashboardView plugin, but I
>>>>> cannot submit form with data from within DashboardView portlet to my
>>>>> plugin (stapler sends request to dashboardView plugin, which replies
>>>>> Error: no name specified.). So, my question is, how can I send data
>>>>> from jelly included in one plugin (dashboard) to class of other plugin
>>>>> (mine) ? Thank you in advance.
>>>>> public class ReportPluginPortlet extends DashboardPortlet{
>>>>> ...
>>>>> public void doConfigSubmit(StaplerRequest req, StaplerResponse
>>>>> rsp) throws ServletException,
>>>>> IOException, InterruptedException {
>>>>> ....
>>>>> }
>>>>> ....
>>>>> }
>>>>> portlet.jelly:
>>>>> <f:form method="post" action="configSubmit" name="reportplugin">
>>>>> ...
