You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Lars Trieloff (JIRA)" <ji...@apache.org> on 2007/10/24 11:15:51 UTC

[jira] Created: (SLING-80) Sling does not map same-name request-parameters to multi-value properties

Sling does not map same-name request-parameters to multi-value properties
-------------------------------------------------------------------------

                 Key: SLING-80
                 URL: https://issues.apache.org/jira/browse/SLING-80
             Project: Sling
          Issue Type: Improvement
            Reporter: Lars Trieloff


When issuing a POST to the DefaultSlingServlet with same-name request-parameters, only one value will be considered. I propose matching these parameters to multi-value properties instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (SLING-80) Sling does not map same-name request-parameters to multi-value properties

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537254 ] 

Bertrand Delacretaz commented on SLING-80:
------------------------------------------

Makes sense - patch applied in revision 587829, thanks!

> Sling does not map same-name request-parameters to multi-value properties
> -------------------------------------------------------------------------
>
>                 Key: SLING-80
>                 URL: https://issues.apache.org/jira/browse/SLING-80
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Lars Trieloff
>         Attachments: sling-80.patch
>
>
> When issuing a POST to the DefaultSlingServlet with same-name request-parameters, only one value will be considered. I propose matching these parameters to multi-value properties instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SLING-80) Sling does not map same-name request-parameters to multi-value properties

Posted by "Lars Trieloff (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Trieloff updated SLING-80:
-------------------------------

    Attachment: sling-80.patch

this patch adds basic support for multi-value properties.

> Sling does not map same-name request-parameters to multi-value properties
> -------------------------------------------------------------------------
>
>                 Key: SLING-80
>                 URL: https://issues.apache.org/jira/browse/SLING-80
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Lars Trieloff
>         Attachments: sling-80.patch
>
>
> When issuing a POST to the DefaultSlingServlet with same-name request-parameters, only one value will be considered. I propose matching these parameters to multi-value properties instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (SLING-80) Sling does not map same-name request-parameters to multi-value properties

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz closed SLING-80.
------------------------------------

    Resolution: Fixed

> Sling does not map same-name request-parameters to multi-value properties
> -------------------------------------------------------------------------
>
>                 Key: SLING-80
>                 URL: https://issues.apache.org/jira/browse/SLING-80
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Lars Trieloff
>         Attachments: sling-80.patch
>
>
> When issuing a POST to the DefaultSlingServlet with same-name request-parameters, only one value will be considered. I propose matching these parameters to multi-value properties instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.