Skip to main content

Notice: This Wiki is now read only and edits are no longer 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 08:02, 1 March 2015 by Unnamed Poltroon (Talk)

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 31 March 2015. It includes the following features:

  • Implementation of the SmartM2M standard. For more information see SmartM2M standard
  • 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 the resource structure and database access.
  • Provide a long-polling mechanism for NAT traversing based on the resource "CommunicationChannel".
  • Provide the HTTP binding based on Jetty and APACHE HTTP client libraries.
  • Provide the CoAP binding based on the Californium library.

Release 2.0.0

The second release of OM2M is planned for 30 September 2015. It includes the following features:

  • Implementation of oneM2M standard. For more information see oneM2M standard.
  • Provide

Back to the top