aboutsummaryrefslogtreecommitdiff
path: root/src/org/traccar/notification/EventForwarder.java
AgeCommit message (Collapse)Author
2018-03-20Add user objects to Event forward payloadAbyss777
2018-02-09Remove unnecessary checksAbyss777
2018-01-26Clean up unused importsAnton Tananaev
2018-01-26Clean up unnecessary codeAnton Tananaev
2017-11-23Minor refactoringSrk
2017-11-22Minor refactoringSrk
2017-11-20Refactoring: parameters only for one mode of eventForwarderSrk
2017-11-20Minor refactoringSrk
2017-11-20Minor refactoringSrk
2017-11-19- Global jsonPrettyPrinting optionSrk
- Minor refactoring - Config option name changed from "event.forward.prettyPrintedPayload" to "config.mapper.prettyPrintedJson"
2017-11-13removing NotificationFormatter from EventForwarderShinryuken
2017-11-08Default payload format as json, plaintext available as optionShinryuken
2017-11-07User defaults when no User is available - EventForwarder refactoringShinryuken
2017-11-06Using templates for event forwarded messagesShinryuken
2017-11-04Adding support for additional parameters on post body request (pushover support)Shinryuken
Hi, i implemented a new modality when sending event messages inside EventForwarder, now you can send requests as a "form-urlencoded", this means that the actual payload will be sent as a form parameter (the parameter name is configurable), this strategy will let you to add another parameters inside the form body message too. You can add new custom form params almost on the same way as the custom headers are inserted (event.forward.header), the only difference is that you will use the equals "=" char instead of ":" as key/value separator. You can enable this mode using the option: "event.forward.payloadAsParamMode", when using this mode you can use the other 2 configuration elements, "event.forward.paramMode.payloadParamName" if you want to change the form name param of the payload (default is "payload") and "event.forward.paramMode.additionalParams" to specify additional key/value form params. I added an option to prettyPrint the payload messages too, you can enable it using "event.forward.prettyPrintedPayload", i decided to add this option only for the EventForwarder behaviour. This is an example (using all the new params) that lets you integrate traccar server with the pushover platform. <entry key='status.timeout'>60</entry> <entry key='event.statusHandler'>true</entry> <entry key="event.forward.enable">true</entry> <entry key='event.forward.url'>https://api.pushover.net/1/messages.json</entry> <entry key='event.forward.prettyPrintedPayload'>true</entry> <entry key='event.forward.payloadAsParamMode'>true</entry> <entry key='event.forward.paramMode.payloadParamName'>message</entry> <entry key='event.forward.paramMode.additionalParams'> token=YOUR_TOKEN_ID user=YOUR_USER_ID </entry> I tested the new options and they work pretty well. Tried to make the change as clean as possible and avoiding code duplications. This mode does not change or affects the actual behabiour of the module. Let me know what do you think.
2017-07-26- Implement base manager classes as genericsAbyss777
- Remame getDeviceById and getDeviceByUniqueId functions
2017-07-19Refactored four managersAbyss777
2017-04-14Add bytecode version checkAnton Tananaev
2017-04-14Update Java librariesAnton Tananaev
2017-02-06Event forward header small improvementAbyss777
2016-12-19Remove own JSON converterAnton Tananaev
2016-11-02Update copyright notice emailsAnton Tananaev
2016-10-03Changed Content-Type for easy access to data from PHP and othersAbyss777
2016-08-30Add missing copyright headerAnton Tananaev
2016-07-13Renamed to EventForwarder and moved to ContextAbyss777
2016-07-13Renamed to EventForwarder and moved to ContextAbyss777