: Regarding Configuration Types
Scott,
Those two issues are actually different things. The first one is to do with the
defaulting of configuration, the second is to do with how File Install
interprets property values with trailing spaces.
As for why you don’t get the default - your configuration
Scott,
Those two issues are actually different things. The first one is to do with the
defaulting of configuration, the second is to do with how File Install
interprets property values with trailing spaces.
As for why you don’t get the default - your configuration explicitly contains a
If trimming was performed by default on tproperties, wouldn't that place a
little extra performance overhead into OSGi vs developers just making sure
there isn't trailing whitespace if they don't want it? It wouldn't be
much, but it adds up...
Ryan
On Thu, Feb 22, 2018 at 12:52 PM Leschke,
I have a configuration type that has a fragment in it as shown below.
@ProviderType
@ObjectClassDefinition(name = "Provider Configuration")
public @interface MetricProviderConfig
{
String schedule() default "0";
}
If the associated property in a .cfg file exists but has no value, as in:
