Release Name: 3.2.3


Take into account the following functional change, which may impact your application. Up to now (i.e. 0.8.1), you are using the following procedure to create and use entities:

* registerContext: creates a new entity
* updateContext UPDATE: set initial attribute values for the entity
* queryContext, new updateContext UPDATE, subscriptions, etc.

Given that now NGSI9 and NGS10 will be decoupled, the procedure with 0.9.0 is simpler:

* updateContext APPEND: creates a new entity and setinitial attribute values 
* queryContext, new updateContext UPDATE, subscriptions, etc.

Apart of that, the upgrade shouldn’t impact your application.

Please have a look to the new manual at the following URL for details:


Changes since last version (0.8.1 to 0.9.0):

- Complete JSON support for NGSI9/10 standard operations
- Decoupled NGSI9 and NGSI10 functionality
- Complete convenience operations support (XML payload in/out), except the ones related to attribute domains
- Much improved alignment with FI-WARE NGSI XSD in XML payloads
- Support for metadata ID attribute in queryContext, updateContext and equivalent convenience operations
- FIX avoid sending empty notifications with ONTIMEINTERVAL (issue #47)
- Tracelevels changes and cleanup
- Trace for incomplete payload and unsupported HTTP headers moved from warning log to tracelevel log
- ADD trace for output payload (under LmtRestReply tracelevel)
- Proper "User-Agent" and "Accept" headers in notifications sent
- FIX no Content-Type HTTP header for responses without payload
- FIX using HTTP 400 instead of 500 for payload parsing errors
- FIX proper payload per URL operation (issue #old72)
- FIX buffer overflow problems in logging subsystem
Privacy policy       Cookies policy
Powered By FusionForge