You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sis.apache.org by "Martin Desruisseaux (JIRA)" <ji...@apache.org> on 2013/07/31 16:01:49 UTC
[jira] [Resolved] (SIS-115) Ability to set NilReason on Boolean,
Integer, Double and String objects
[ https://issues.apache.org/jira/browse/SIS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Desruisseaux resolved SIS-115.
-------------------------------------
Resolution: Fixed
> Ability to set NilReason on Boolean, Integer, Double and String objects
> -----------------------------------------------------------------------
>
> Key: SIS-115
> URL: https://issues.apache.org/jira/browse/SIS-115
> Project: Spatial Information Systems
> Issue Type: Improvement
> Components: Utilities
> Affects Versions: 0.3
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Fix For: 0.4
>
>
> In SIS 0.3, {{NilReason}} are stored by implementations of the {{org.apache.sis.xml.NilObject}} interface. However we can not implement this interface for {{Boolean}}, {{Integer}}, {{Double}}, {{String}} and other JDK classes that are {{final}}.
> The proposed workaround is to provide an internal {{PrimitiveTypeProperties}} class which will assign {{NilReason}} to a specific instance of {{Boolean}} or other JDK classes, using an {{IdentityHashMap}}. Inconvenient is that testing {{if (object instanceof NilObject)}} is no longer sufficient - we now need to use the {{NilReason.forObject(Object)}} method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira