Version 3.7.0
From RifidiWiki
Changes in 3.7
LLRP
- Check rospec response is not error before entering processing state
- Handle add ro spec errors either through logging error and or resending rospec via checking error being returned learned in honeywell cwr project
- Stop showing illegalstateexception in the console in LLRPReaderSession
Monitoring
- Push notifications of server keep alive via MQTT. with ability to enable/disable and config standard mqtt parameters/topic..similar payload to ping I think and server IP/port as messages may go to centralized MQTT topic in cloud and needs to be a way to identify which Rifidi instance it came from - Payload "127.0.0.1</> LLRP_1</>Processing</>epochdate/time</></> - and each event type would have its own end point config/ip/port/qos/topic" - not sure if json format of xml makes more sense here
Rest
- Reset session - delete session, create session, reexcute previous running commands, restart session(if already in processing state)
- LLRP Encoding - validate session state in processing and provide necessary response
- Start/Stop/Install/Uninstall Bundle - allow for install via url http://stackoverflow.com/questions/36017774/how-can-i-execute-osgi-command-in-code http://stackoverflow.com/questions/18825030/can-osgi-install-deploy-bundles-hosted-on-a-url
- Restart Rifidi Edge server
- OSGI SS operations or more generically expose OSGI command line operations - http://stackoverflow.com/questions/36017774/how-can-i-execute-osgi-command-in-code
- Stop Rifidi server command
Adapters
- Added REST interface to the Generic adapter Generic_User_Guide#Rest_Interface
Framework
- Java 64 bit support
- Migrate JVM Arguments where applicable such as things not required during server startup like llrp encoding (Dorg.rifidi.llrp.encode) leveraging Rifidi apps properties framework
- Modify dbapp to use postgresql by defau