You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2008/02/01 21:33:08 UTC
[jira] Created: (SLING-219) Use native representations for boolean
and numbers in JSON export
Use native representations for boolean and numbers in JSON export
-----------------------------------------------------------------
Key: SLING-219
URL: https://issues.apache.org/jira/browse/SLING-219
Project: Sling
Issue Type: Improvement
Components: JSON
Reporter: Tobias Bocanegra
the current JSON export uses just the getString() representation for all
property types. if would be good if the property type can be preserved.
although it's not possible for all property types, at least for 'boolean',
'long' and 'double' the JSON equivalent should be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-219) Use native representations for boolean
and numbers in JSON export
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Bocanegra closed SLING-219.
----------------------------------
perfect.
> Use native representations for boolean and numbers in JSON export
> -----------------------------------------------------------------
>
> Key: SLING-219
> URL: https://issues.apache.org/jira/browse/SLING-219
> Project: Sling
> Issue Type: Improvement
> Components: JSON
> Reporter: Tobias Bocanegra
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
> Attachments: JsonItemWriter-r61526.patch
>
>
> the current JSON export uses just the getString() representation for all
> property types. if would be good if the property type can be preserved.
> although it's not possible for all property types, at least for 'boolean',
> 'long' and 'double' the JSON equivalent should be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-219) Use native representations for boolean
and numbers in JSON export
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-219.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Applied patch slightly modified in Rev. 618408.
Modifications:
- Use switch instead of Ifs
- Use shared DateFormat instance (synchronized of course)
Please close, if this fixes your issue. Thanks.
> Use native representations for boolean and numbers in JSON export
> -----------------------------------------------------------------
>
> Key: SLING-219
> URL: https://issues.apache.org/jira/browse/SLING-219
> Project: Sling
> Issue Type: Improvement
> Components: JSON
> Reporter: Tobias Bocanegra
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
> Attachments: JsonItemWriter-r61526.patch
>
>
> the current JSON export uses just the getString() representation for all
> property types. if would be good if the property type can be preserved.
> although it's not possible for all property types, at least for 'boolean',
> 'long' and 'double' the JSON equivalent should be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-219) Use native representations for boolean
and numbers in JSON export
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Bocanegra updated SLING-219:
-----------------------------------
Attachment: JsonItemWriter-r61526.patch
patch implements the suggested changes.
> Use native representations for boolean and numbers in JSON export
> -----------------------------------------------------------------
>
> Key: SLING-219
> URL: https://issues.apache.org/jira/browse/SLING-219
> Project: Sling
> Issue Type: Improvement
> Components: JSON
> Reporter: Tobias Bocanegra
> Attachments: JsonItemWriter-r61526.patch
>
>
> the current JSON export uses just the getString() representation for all
> property types. if would be good if the property type can be preserved.
> although it's not possible for all property types, at least for 'boolean',
> 'long' and 'double' the JSON equivalent should be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-219) Use native representations for boolean
and numbers in JSON export
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned SLING-219:
---------------------------------------
Assignee: Felix Meschberger
> Use native representations for boolean and numbers in JSON export
> -----------------------------------------------------------------
>
> Key: SLING-219
> URL: https://issues.apache.org/jira/browse/SLING-219
> Project: Sling
> Issue Type: Improvement
> Components: JSON
> Reporter: Tobias Bocanegra
> Assignee: Felix Meschberger
> Attachments: JsonItemWriter-r61526.patch
>
>
> the current JSON export uses just the getString() representation for all
> property types. if would be good if the property type can be preserved.
> although it's not possible for all property types, at least for 'boolean',
> 'long' and 'double' the JSON equivalent should be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.