[
https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585638#action_12585638
]
Felix Meschberger commented on SLING-355:
-----------------------------------------
> what was the resolution on this? why is this issue closed now?
Because it was fixed as initially described.
> as for numbers, i agree that an empty string can be ignored or even force a
> removal of the property.
> however i would try to set the value anyways and if it fails try to remove it.
This is the problem we are facing: It creates inconsistent behaviour depending
on the property type. IMHO this is not acceptable
> Empty Request Parameters should be handled as not present
> ---------------------------------------------------------
>
> Key: SLING-355
> URL: https://issues.apache.org/jira/browse/SLING-355
> Project: Sling
> Issue Type: Bug
> Components: ujax
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: 2.0.0
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> When the sling post servlet tries to set a property which value is empty, it
> fails to set the property value if the proper type is not a string as it for
> example tries to convert the empty string into a long - which fails.
> Therefore the servlet should treat empty values as not existing ones and
> rather remove the property.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
