-
Notifications
You must be signed in to change notification settings - Fork 189
Release Updates
nkef edited this page Nov 7, 2014
·
4 revisions
- Mobile-Sensors-Management development and integration into the platform.
- Security module development (CAS) and integration into the platform.
- Schema Editor & LD4S redesign development and integration into the platform for handling sensor types .
- Updated OpenIoT ontology
- Updated sensor type structure and converted it from string to URL
- Added “feature of interest” support to LSM-Light and X-GSN so that a User will be able to bind third party data with the sensor.
- Added ability at X-GSN to support RDF format sensor metadata at configuration time.
- All of the modules running within JBoss (except the security module) adopted a “global properties” file that resides at the JBoss instance to ease configuration and deployment of the platform.
- Hardcoded properties and various properties used within every project in various modules are now set in the global properties file.
- Updated the ui.core module so as to define the ui plug-ins at the global properties file.
- Sensor type support in LSM-Light.
- New LSM-client integration, that supports sensor types in several modules like X-GSN, Scheduler and SD&UM.
- LSM-Light with security support provided as a service from DERI premises currently for testing purposes.
- Support of LSM-Light to the cloud (tested in Amazon cloud).
- Added Maven support to all OpenIoT modules.
- Added Maven parent project support for centralized control of the building/install process. This solves issue #5.
- Packaging of the complete OpenIoT platform (for use and development) to an Oracle Virtual Box for distribution.
- XGSN publish to LSM reads from lsm-config instead of sensor metadata file. This solves issue #49.
- SecurityIntegration: security management web-app uses hard-coded security server url. This solves issue #74.
- Bug loading the filed names XGSN can't push data. This solves issue #78.
- LSM-XGSN: can't push data (requirement for sensor type update identification in LSM-Client). This solves issue #80.
footer