[
https://issues.apache.org/jira/browse/SLING-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-5914.
-------------------------------------
Fix Version/s: (was: Sling Provisioning Model 1.8.6)
Resolution: Won't Fix
The OSGi configuration resource format is the way to go, therefore resolving
this as won't fix
> Provisioning model does not correctly handle floating-point configuration
> values
> --------------------------------------------------------------------------------
>
> Key: SLING-5914
> URL: https://issues.apache.org/jira/browse/SLING-5914
> Project: Sling
> Issue Type: Bug
> Components: Tooling
> Reporter: Robert Munteanu
> Priority: Major
>
> The provisioning model specifies that floating-point values are encoded in
> the following format:
> - {{D"1.0"}} for doubles
> - {{F"1.0"}} for floats
> However, the ConfigAdmin has a different idea about how these values should
> be stored:
> {code:java}
> case TOKEN_SIMPLE_FLOAT:
> case TOKEN_PRIMITIVE_FLOAT:
> int fBits = Integer.parseInt( readQuoted( pr ) );
> return new Float( Float.intBitsToFloat( fBits ) );
> case TOKEN_SIMPLE_DOUBLE:
> case TOKEN_PRIMITIVE_DOUBLE:
> long dBits = Long.parseLong( readQuoted( pr ) );
> return new Double( Double.longBitsToDouble( dBits ) );
> {code}
> I assume that this is done to preserve precision when reading/writing values.
> The provisioning model should be updated to mediate between the user-supplied
> values and the configuration admin format.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
