Eclipse Community Forums: Eclipse SmartHome » Thing.configuration.properties vs Thing.properties

Help

Home

Home » Archived » Eclipse SmartHome » Thing.configuration.properties vs Thing.properties

Show: Today's Messages :: Show Polls :: Message Navigator

Thing.configuration.properties vs Thing.properties [message #1699162]

Mon, 22 June 2015 08:56

Karel Goderis

Messages: 198
Registered: March 2014

Senior Member

Hi,

I have a binding in the making where I use a DiscoveryResultBuilder.withProperties()

When inspecting the created Thing afterwards, I notice that the Properties are added to the Configuration.Properties set, and not the Properties set.

That is IMO not very logical, and rather confusing (e.g. why 2 different Properties set at 2 different locations?)

Karel

Report message to a moderator

Re: Thing.configuration.properties vs Thing.properties [message #1699166 is a reply to message #1699162]

Mon, 22 June 2015 09:23

Marcel Verpaalen

Messages: 59
Registered: September 2014

Member

Fully agree, this is very confusing.
See also https://www.eclipse.org/forums/index.php?t=msg&th=1066328&goto=1694593

Report message to a moderator

Re: Thing.configuration.properties vs Thing.properties [message #1699684 is a reply to message #1699166]

Thu, 25 June 2015 19:27

Dennis Nobel

Messages: 166
Registered: September 2014

Senior Member

I also agree. Discovery API was designed before the thing properties existed. But now having the properties, maybe it should be called withConfiguration.

We have to see if want to change the API, because this will break more or less all bindings.

Report message to a moderator