Problem with Descriptor.newInstance / StaplerRequest

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem with Descriptor.newInstance / StaplerRequest

Martin Ficker
Hello,

I've got a Problem and will be happy about every Response.
I'm trying to write a Plugin that allows to configure multiple Projects at one time.
The Idea is to first select a descriptor, after this a Page like the following is displayed:

Project A
    [ ] Poll SCM
        Schedule 0,10,20,30,40,50 * * * *
       
Project B
    [ ] Poll SCM
        Schedule 1,11,21,31,51,51 * * * *

Project C
...
[Submit Button]


I wanted to divide the submission with "Structured From Submission" and call the Descriptors newInstance for each Project:

public synchronized void doConfigSubmit(StaplerRequest req, StaplerResponse rsp) throws IOException, ServletException {
JSONObject json = StructuredForm.get(req);.
for (AbstractProject project : projects) {          
            JSONObject o = json.getJSONObject(project.getName());
            Descriptor d =  descriptor.newInstance(req, o);
            <Assign the new Instance to the Project>          
        }
...

But unfortunately not all Descriptors make use of the JSONObject.
Example: newInstance in  the DescriptorImpl of SCMTrigger looks like:
 
  return new SCMTrigger(req.getParameter("scmpoll_spec"));       

This mean the implementation relies on the Request Parameter rather than the JSONObject. But
"req.getParameter("scmpoll_spec")" will always return the first Paraneter ("0,10,20,.." in my Example). The configuration
of Project B will use the wrong Parameter.

Are their any Ideas how to workaround this Problem?
Is there for example a possibility to filter StaplerRequest to only contain those entries corresponding to a given JSONObject?

Best Regards,

Martin
Reply | Threaded
Open this post in threaded view
|

Re: Problem with Descriptor.newInstance / StaplerRequest

Kohsuke Kawaguchi
Administrator

If you are really willing to do it, you can certainly filter
StaplerRequest object and have it only return a subset of parameters.

But I think the best way is really just to fix those plugins.

You can at least detect if a particular Descriptor is using the
deprecated version of the newInstance method or the correct one, so your
plugin could refuse to let people configure the broken ones.

I just committed a fix for SCMTrigger.newInstance in 1.223.

Martin Ficker wrote:

> Hello,
>
> I've got a Problem and will be happy about every Response.
> I'm trying to write a Plugin that allows to configure multiple Projects at
> one time.
> The Idea is to first select a descriptor, after this a Page like the
> following is displayed:
>
> Project A
>     [ ] Poll SCM
>         Schedule 0,10,20,30,40,50 * * * *
>
> Project B
>     [ ] Poll SCM
>         Schedule 1,11,21,31,51,51 * * * *
>
> Project C
> ..
> [Submit Button]
>
>
> I wanted to divide the submission with "Structured From Submission" and call
> the Descriptors newInstance for each Project:
>
> public synchronized void doConfigSubmit(StaplerRequest req, StaplerResponse
> rsp) throws IOException, ServletException {
> JSONObject json = StructuredForm.get(req);.
> for (AbstractProject project : projects) {
>             JSONObject o = json.getJSONObject(project.getName());
>             Descriptor d =  descriptor.newInstance(req, o);
>             <Assign the new Instance to the Project>
>         }
> ..
>
> But unfortunately not all Descriptors make use of the JSONObject.
> Example: newInstance in  the DescriptorImpl of SCMTrigger looks like:
>
>   return new SCMTrigger(req.getParameter("scmpoll_spec"));
>
> This mean the implementation relies on the Request Parameter rather than the
> JSONObject. But
> "req.getParameter("scmpoll_spec")" will always return the first Paraneter
> ("0,10,20,.." in my Example). The configuration
> of Project B will use the wrong Parameter.
>
> Are their any Ideas how to workaround this Problem?
> Is there for example a possibility to filter StaplerRequest to only contain
> those entries corresponding to a given JSONObject?
>
> Best Regards,
>
> Martin
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Problem with Descriptor.newInstance / StaplerRequest

Martin Ficker
Thanks.I will try to use only Desriptors using the correct version of
newIntance. But since this does still take a Request Parameter the
Descriptor could still
make assumptions about it that don't hold in my "Batchconfiguration"
environment. Maybe I'll just white list those Descriptors I've looked at.

Kohsuke Kawaguchi schrieb:

>
> If you are really willing to do it, you can certainly filter
> StaplerRequest object and have it only return a subset of parameters.
>
> But I think the best way is really just to fix those plugins.
>
> You can at least detect if a particular Descriptor is using the
> deprecated version of the newInstance method or the correct one, so
> your plugin could refuse to let people configure the broken ones.
>
> I just committed a fix for SCMTrigger.newInstance in 1.223.
>
> Martin Ficker wrote:
>> Hello,
>>
>> I've got a Problem and will be happy about every Response.
>> I'm trying to write a Plugin that allows to configure multiple
>> Projects at
>> one time.
>> The Idea is to first select a descriptor, after this a Page like the
>> following is displayed:
>>
>> Project A
>>     [ ] Poll SCM
>>         Schedule 0,10,20,30,40,50 * * * *
>>
>> Project B
>>     [ ] Poll SCM
>>         Schedule 1,11,21,31,51,51 * * * *
>>
>> Project C
>> ..
>> [Submit Button]
>>
>>
>> I wanted to divide the submission with "Structured From Submission"
>> and call
>> the Descriptors newInstance for each Project:
>>
>> public synchronized void doConfigSubmit(StaplerRequest req,
>> StaplerResponse
>> rsp) throws IOException, ServletException {
>> JSONObject json = StructuredForm.get(req);.
>> for (AbstractProject project : projects) {
>>             JSONObject o = json.getJSONObject(project.getName());
>>             Descriptor d =  descriptor.newInstance(req, o);
>>             <Assign the new Instance to the Project>
>>         }
>> ..
>>
>> But unfortunately not all Descriptors make use of the JSONObject.
>> Example: newInstance in  the DescriptorImpl of SCMTrigger looks like:
>>
>>   return new SCMTrigger(req.getParameter("scmpoll_spec"));
>>
>> This mean the implementation relies on the Request Parameter rather
>> than the
>> JSONObject. But
>> "req.getParameter("scmpoll_spec")" will always return the first
>> Paraneter
>> ("0,10,20,.." in my Example). The configuration
>> of Project B will use the wrong Parameter.
>>
>> Are their any Ideas how to workaround this Problem?
>> Is there for example a possibility to filter StaplerRequest to only
>> contain
>> those entries corresponding to a given JSONObject?
>>
>> Best Regards,
>>
>> Martin
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Descriptor.newInstance / StaplerRequest

Martin Ficker
In reply to this post by Kohsuke Kawaguchi
I committed the same changes for JavadocArchiver and TimerTrigger.

Kohsuke Kawaguchi schrieb:

>
> If you are really willing to do it, you can certainly filter
> StaplerRequest object and have it only return a subset of parameters.
>
> But I think the best way is really just to fix those plugins.
>
> You can at least detect if a particular Descriptor is using the
> deprecated version of the newInstance method or the correct one, so
> your plugin could refuse to let people configure the broken ones.
>
> I just committed a fix for SCMTrigger.newInstance in 1.223.
>
> Martin Ficker wrote:
>> Hello,
>>
>> I've got a Problem and will be happy about every Response.
>> I'm trying to write a Plugin that allows to configure multiple
>> Projects at
>> one time.
>> The Idea is to first select a descriptor, after this a Page like the
>> following is displayed:
>>
>> Project A
>>     [ ] Poll SCM
>>         Schedule 0,10,20,30,40,50 * * * *
>>
>> Project B
>>     [ ] Poll SCM
>>         Schedule 1,11,21,31,51,51 * * * *
>>
>> Project C
>> ..
>> [Submit Button]
>>
>>
>> I wanted to divide the submission with "Structured From Submission"
>> and call
>> the Descriptors newInstance for each Project:
>>
>> public synchronized void doConfigSubmit(StaplerRequest req,
>> StaplerResponse
>> rsp) throws IOException, ServletException {
>> JSONObject json = StructuredForm.get(req);.
>> for (AbstractProject project : projects) {
>>             JSONObject o = json.getJSONObject(project.getName());
>>             Descriptor d =  descriptor.newInstance(req, o);
>>             <Assign the new Instance to the Project>
>>         }
>> ..
>>
>> But unfortunately not all Descriptors make use of the JSONObject.
>> Example: newInstance in  the DescriptorImpl of SCMTrigger looks like:
>>
>>   return new SCMTrigger(req.getParameter("scmpoll_spec"));
>>
>> This mean the implementation relies on the Request Parameter rather
>> than the
>> JSONObject. But
>> "req.getParameter("scmpoll_spec")" will always return the first
>> Paraneter
>> ("0,10,20,.." in my Example). The configuration
>> of Project B will use the wrong Parameter.
>>
>> Are their any Ideas how to workaround this Problem?
>> Is there for example a possibility to filter StaplerRequest to only
>> contain
>> those entries corresponding to a given JSONObject?
>>
>> Best Regards,
>>
>> Martin
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Descriptor.newInstance / StaplerRequest

Erik Ramfelt
You dont happen to have a list of what other plugins that are using
the old newInstance() method?

//Erik

On Thu, Jun 12, 2008 at 3:28 PM, M. Ficker <[hidden email]> wrote:

> I committed the same changes for JavadocArchiver and TimerTrigger.
>
> Kohsuke Kawaguchi schrieb:
>>
>> If you are really willing to do it, you can certainly filter
>> StaplerRequest object and have it only return a subset of parameters.
>>
>> But I think the best way is really just to fix those plugins.
>>
>> You can at least detect if a particular Descriptor is using the deprecated
>> version of the newInstance method or the correct one, so your plugin could
>> refuse to let people configure the broken ones.
>>
>> I just committed a fix for SCMTrigger.newInstance in 1.223.
>>
>> Martin Ficker wrote:
>>>
>>> Hello,
>>>
>>> I've got a Problem and will be happy about every Response.
>>> I'm trying to write a Plugin that allows to configure multiple Projects
>>> at
>>> one time.
>>> The Idea is to first select a descriptor, after this a Page like the
>>> following is displayed:
>>>
>>> Project A
>>>    [ ] Poll SCM
>>>        Schedule 0,10,20,30,40,50 * * * *
>>>
>>> Project B
>>>    [ ] Poll SCM
>>>        Schedule 1,11,21,31,51,51 * * * *
>>>
>>> Project C
>>> ..
>>> [Submit Button]
>>>
>>>
>>> I wanted to divide the submission with "Structured From Submission" and
>>> call
>>> the Descriptors newInstance for each Project:
>>>
>>> public synchronized void doConfigSubmit(StaplerRequest req,
>>> StaplerResponse
>>> rsp) throws IOException, ServletException {
>>> JSONObject json = StructuredForm.get(req);.
>>> for (AbstractProject project : projects) {
>>>            JSONObject o = json.getJSONObject(project.getName());
>>>            Descriptor d =  descriptor.newInstance(req, o);
>>>            <Assign the new Instance to the Project>
>>>        }
>>> ..
>>>
>>> But unfortunately not all Descriptors make use of the JSONObject.
>>> Example: newInstance in  the DescriptorImpl of SCMTrigger looks like:
>>>
>>>  return new SCMTrigger(req.getParameter("scmpoll_spec"));
>>>
>>> This mean the implementation relies on the Request Parameter rather than
>>> the
>>> JSONObject. But
>>> "req.getParameter("scmpoll_spec")" will always return the first Paraneter
>>> ("0,10,20,.." in my Example). The configuration
>>> of Project B will use the wrong Parameter.
>>>
>>> Are their any Ideas how to workaround this Problem?
>>> Is there for example a possibility to filter StaplerRequest to only
>>> contain
>>> those entries corresponding to a given JSONObject?
>>>
>>> Best Regards,
>>>
>>> Martin
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Descriptor.newInstance / StaplerRequest

Martin Ficker
No. I don't have such a list. I'll go to the Builders, Publisher and
Triggers in the Hudson core and fix them if necessary.

Martin

Erik Ramfelt schrieb:

> You dont happen to have a list of what other plugins that are using
> the old newInstance() method?
>
> //Erik
>
> On Thu, Jun 12, 2008 at 3:28 PM, M. Ficker <[hidden email]> wrote:
>  
>> I committed the same changes for JavadocArchiver and TimerTrigger.
>>
>> Kohsuke Kawaguchi schrieb:
>>    
>>> If you are really willing to do it, you can certainly filter
>>> StaplerRequest object and have it only return a subset of parameters.
>>>
>>> But I think the best way is really just to fix those plugins.
>>>
>>> You can at least detect if a particular Descriptor is using the deprecated
>>> version of the newInstance method or the correct one, so your plugin could
>>> refuse to let people configure the broken ones.
>>>
>>> I just committed a fix for SCMTrigger.newInstance in 1.223.
>>>
>>> Martin Ficker wrote:
>>>      
>>>> Hello,
>>>>
>>>> I've got a Problem and will be happy about every Response.
>>>> I'm trying to write a Plugin that allows to configure multiple Projects
>>>> at
>>>> one time.
>>>> The Idea is to first select a descriptor, after this a Page like the
>>>> following is displayed:
>>>>
>>>> Project A
>>>>    [ ] Poll SCM
>>>>        Schedule 0,10,20,30,40,50 * * * *
>>>>
>>>> Project B
>>>>    [ ] Poll SCM
>>>>        Schedule 1,11,21,31,51,51 * * * *
>>>>
>>>> Project C
>>>> ..
>>>> [Submit Button]
>>>>
>>>>
>>>> I wanted to divide the submission with "Structured From Submission" and
>>>> call
>>>> the Descriptors newInstance for each Project:
>>>>
>>>> public synchronized void doConfigSubmit(StaplerRequest req,
>>>> StaplerResponse
>>>> rsp) throws IOException, ServletException {
>>>> JSONObject json = StructuredForm.get(req);.
>>>> for (AbstractProject project : projects) {
>>>>            JSONObject o = json.getJSONObject(project.getName());
>>>>            Descriptor d =  descriptor.newInstance(req, o);
>>>>            <Assign the new Instance to the Project>
>>>>        }
>>>> ..
>>>>
>>>> But unfortunately not all Descriptors make use of the JSONObject.
>>>> Example: newInstance in  the DescriptorImpl of SCMTrigger looks like:
>>>>
>>>>  return new SCMTrigger(req.getParameter("scmpoll_spec"));
>>>>
>>>> This mean the implementation relies on the Request Parameter rather than
>>>> the
>>>> JSONObject. But
>>>> "req.getParameter("scmpoll_spec")" will always return the first Paraneter
>>>> ("0,10,20,.." in my Example). The configuration
>>>> of Project B will use the wrong Parameter.
>>>>
>>>> Are their any Ideas how to workaround this Problem?
>>>> Is there for example a possibility to filter StaplerRequest to only
>>>> contain
>>>> those entries corresponding to a given JSONObject?
>>>>
>>>> Best Regards,
>>>>
>>>> Martin
>>>>
>>>>        
>>>      
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>    
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>  


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Problem with Descriptor.newInstance / StaplerRequest

Erik Ramfelt
Attached is a list of classes implementing the deprecated method. (I
think I got them all, but some may be missed)
Plugins author please have a look to see if you made the list. :)

//Erik


On Thu, Jun 12, 2008 at 9:52 PM, M. Ficker <[hidden email]> wrote:

> No. I don't have such a list. I'll go to the Builders, Publisher and
> Triggers in the Hudson core and fix them if necessary.
>
> Martin
>
> Erik Ramfelt schrieb:
>>
>> You dont happen to have a list of what other plugins that are using
>> the old newInstance() method?
>>
>> //Erik
>>
>> On Thu, Jun 12, 2008 at 3:28 PM, M. Ficker <[hidden email]>
>> wrote:
>>
>>>
>>> I committed the same changes for JavadocArchiver and TimerTrigger.
>>>
>>> Kohsuke Kawaguchi schrieb:
>>>
>>>>
>>>> If you are really willing to do it, you can certainly filter
>>>> StaplerRequest object and have it only return a subset of parameters.
>>>>
>>>> But I think the best way is really just to fix those plugins.
>>>>
>>>> You can at least detect if a particular Descriptor is using the
>>>> deprecated
>>>> version of the newInstance method or the correct one, so your plugin
>>>> could
>>>> refuse to let people configure the broken ones.
>>>>
>>>> I just committed a fix for SCMTrigger.newInstance in 1.223.
>>>>
>>>> Martin Ficker wrote:
>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> I've got a Problem and will be happy about every Response.
>>>>> I'm trying to write a Plugin that allows to configure multiple Projects
>>>>> at
>>>>> one time.
>>>>> The Idea is to first select a descriptor, after this a Page like the
>>>>> following is displayed:
>>>>>
>>>>> Project A
>>>>>   [ ] Poll SCM
>>>>>       Schedule 0,10,20,30,40,50 * * * *
>>>>>
>>>>> Project B
>>>>>   [ ] Poll SCM
>>>>>       Schedule 1,11,21,31,51,51 * * * *
>>>>>
>>>>> Project C
>>>>> ..
>>>>> [Submit Button]
>>>>>
>>>>>
>>>>> I wanted to divide the submission with "Structured From Submission" and
>>>>> call
>>>>> the Descriptors newInstance for each Project:
>>>>>
>>>>> public synchronized void doConfigSubmit(StaplerRequest req,
>>>>> StaplerResponse
>>>>> rsp) throws IOException, ServletException {
>>>>> JSONObject json = StructuredForm.get(req);.
>>>>> for (AbstractProject project : projects) {
>>>>>           JSONObject o = json.getJSONObject(project.getName());
>>>>>           Descriptor d =  descriptor.newInstance(req, o);
>>>>>           <Assign the new Instance to the Project>
>>>>>       }
>>>>> ..
>>>>>
>>>>> But unfortunately not all Descriptors make use of the JSONObject.
>>>>> Example: newInstance in  the DescriptorImpl of SCMTrigger looks like:
>>>>>
>>>>>  return new SCMTrigger(req.getParameter("scmpoll_spec"));
>>>>>
>>>>> This mean the implementation relies on the Request Parameter rather
>>>>> than
>>>>> the
>>>>> JSONObject. But
>>>>> "req.getParameter("scmpoll_spec")" will always return the first
>>>>> Paraneter
>>>>> ("0,10,20,.." in my Example). The configuration
>>>>> of Project B will use the wrong Parameter.
>>>>>
>>>>> Are their any Ideas how to workaround this Problem?
>>>>> Is there for example a possibility to filter StaplerRequest to only
>>>>> contain
>>>>> those entries corresponding to a given JSONObject?
>>>>>
>>>>> Best Regards,
>>>>>
>>>>> Martin
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

newInstance-deprecated.txt (21K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Problem with Descriptor.newInstance / StaplerRequest

Kohsuke Kawaguchi
Administrator
Erik Ramfelt wrote:
> Attached is a list of classes implementing the deprecated method. (I
> think I got them all, but some may be missed)
> Plugins author please have a look to see if you made the list. :)

I fixed some in the core.

I don't think people would mind Martin making this kind changes
throughout the plugins.

> //Erik
>
>
> On Thu, Jun 12, 2008 at 9:52 PM, M. Ficker <[hidden email]> wrote:
>> No. I don't have such a list. I'll go to the Builders, Publisher and
>> Triggers in the Hudson core and fix them if necessary.
>>
>> Martin
>>
>> Erik Ramfelt schrieb:
>>>
>>> You dont happen to have a list of what other plugins that are using
>>> the old newInstance() method?
>>>
>>> //Erik
>>>
>>> On Thu, Jun 12, 2008 at 3:28 PM, M. Ficker <[hidden email]>
>>> wrote:
>>>
>>>>
>>>> I committed the same changes for JavadocArchiver and TimerTrigger.
>>>>
>>>> Kohsuke Kawaguchi schrieb:
>>>>
>>>>>
>>>>> If you are really willing to do it, you can certainly filter
>>>>> StaplerRequest object and have it only return a subset of parameters.
>>>>>
>>>>> But I think the best way is really just to fix those plugins.
>>>>>
>>>>> You can at least detect if a particular Descriptor is using the
>>>>> deprecated
>>>>> version of the newInstance method or the correct one, so your plugin
>>>>> could
>>>>> refuse to let people configure the broken ones.
>>>>>
>>>>> I just committed a fix for SCMTrigger.newInstance in 1.223.
>>>>>
>>>>> Martin Ficker wrote:
>>>>>
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I've got a Problem and will be happy about every Response.
>>>>>> I'm trying to write a Plugin that allows to configure multiple Projects
>>>>>> at
>>>>>> one time.
>>>>>> The Idea is to first select a descriptor, after this a Page like the
>>>>>> following is displayed:
>>>>>>
>>>>>> Project A
>>>>>>   [ ] Poll SCM
>>>>>>       Schedule 0,10,20,30,40,50 * * * *
>>>>>>
>>>>>> Project B
>>>>>>   [ ] Poll SCM
>>>>>>       Schedule 1,11,21,31,51,51 * * * *
>>>>>>
>>>>>> Project C
>>>>>> ..
>>>>>> [Submit Button]
>>>>>>
>>>>>>
>>>>>> I wanted to divide the submission with "Structured From Submission" and
>>>>>> call
>>>>>> the Descriptors newInstance for each Project:
>>>>>>
>>>>>> public synchronized void doConfigSubmit(StaplerRequest req,
>>>>>> StaplerResponse
>>>>>> rsp) throws IOException, ServletException {
>>>>>> JSONObject json = StructuredForm.get(req);.
>>>>>> for (AbstractProject project : projects) {
>>>>>>           JSONObject o = json.getJSONObject(project.getName());
>>>>>>           Descriptor d =  descriptor.newInstance(req, o);
>>>>>>           <Assign the new Instance to the Project>
>>>>>>       }
>>>>>> ..
>>>>>>
>>>>>> But unfortunately not all Descriptors make use of the JSONObject.
>>>>>> Example: newInstance in  the DescriptorImpl of SCMTrigger looks like:
>>>>>>
>>>>>>  return new SCMTrigger(req.getParameter("scmpoll_spec"));
>>>>>>
>>>>>> This mean the implementation relies on the Request Parameter rather
>>>>>> than
>>>>>> the
>>>>>> JSONObject. But
>>>>>> "req.getParameter("scmpoll_spec")" will always return the first
>>>>>> Paraneter
>>>>>> ("0,10,20,.." in my Example). The configuration
>>>>>> of Project B will use the wrong Parameter.
>>>>>>
>>>>>> Are their any Ideas how to workaround this Problem?
>>>>>> Is there for example a possibility to filter StaplerRequest to only
>>>>>> contain
>>>>>> those entries corresponding to a given JSONObject?
>>>>>>
>>>>>> Best Regards,
>>>>>>
>>>>>> Martin
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment