Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

OM2M/Roadmap

< OM2M
Revision as of 07:46, 1 March 2015 by Benalaya.sensinov.com (Talk | contribs) (Created page with "This page describes the current plan for the upcoming features of the Eclipse OM2M project. Please note that this plan is a moving target - depending on priorities and communi...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page describes the current plan for the upcoming features of the Eclipse OM2M project. Please note that this plan is a moving target - depending on priorities and community contribution and commitments, the plan can change any time, so do not take it for granted, but see it as a guidance of direction.

Release 1.0.0

The first release of OM2M is planned for March 2015. It includes the following features:

  • Replace the XSD resource validation with a native code to provide flexibility.
  • Replace the OASIS OBIX library with a native code based on the JAXB library.
  • Provide a persistence solution layer based on EclipseLink JPA library to support various database solutions.
  • Replace the DB4O database with the H2 database which provide better performance.
  • Introduce persistence parameters to the "config.ini" file to simplify the JPA configuration.
  • Improve the OM2M performance by optimizing database access.
  • Modularize the smarthome.cfg file (bug 434003)
  • Introduction of a configuration meta-data description service (bug 433993)
  • Introduction of the "Thing Concept" as a new way to implement bindings by providing thing and configuration meta-data (bug 433994)

See all details in the official 0.7.0 release plan

Release 0.8.0

Following features are planned for the upcoming 0.8.0 release (planned for March 2015):

  • REST-API for administration of items and things (bug 423546)
  • Updated set of types and items (bug 423550)
  • Provide a server-push mechanism for events (item status updates and other UI-relevant events) (bug 423552)

See a list of all already implemented features and fixed bugs.

Back to the top