Age | Commit message (Collapse) | Author | |
---|---|---|---|
2019-02-23 | Refactor configuration | Anton Tananaev | |
2019-02-20 | Support headers for forwarding | Anton Tananaev | |
2018-09-29 | Re-implement mail notificator | Anton Tananaev | |
2018-09-23 | Implement push notifications | Anton Tananaev | |
2018-09-15 | Provide error messages | Anton Tananaev | |
2018-09-14 | Log using slf4j and java logging | Anton Tananaev | |
2018-08-17 | Add constructor to MessageException class | Marcos Dallagnelo | |
2018-07-27 | Move notificators to appropriate package and rename. | Abyss777 | |
2018-06-27 | - Rename NotificationException to MessageException | Abyss777 | |
- Simplify Notificator instantiation - Make sms configuration more clear - Move some defaults in code - Some cleanup | |||
2018-06-26 | Rename MailMessage to FullMessage | Abyss777 | |
2018-06-26 | Rename transports to notificators | Abyss777 | |
2018-06-26 | Cleanup and some adjustments | Abyss777 | |
2018-06-26 | Merge remote-tracking branch 'ivanfmartinez/notifications' | Abyss777 | |
# Conflicts: # src/org/traccar/Context.java | |||
2018-06-02 | Remove async HTTP client dependency | Anton Tananaev | |
2018-06-01 | option to instantiate a new SMSNotifier using a different SMSManager | Ivan Martinez | |
2018-06-01 | update api to support notificators | Ivan Martinez | |
2018-06-01 | move NotificatorManager instance to Context | Ivan Martinez | |
2018-06-01 | make compatible with java 7 | Ivan Martinez | |
2018-06-01 | added warning when using the null notificator | Ivan Martinez | |
2018-06-01 | generic template names | Ivan Martinez | |
2018-04-11 | Add support of multiple Maintenances | Abyss777 | |
2018-04-09 | configuration support for notificators | Ivan Martinez | |
2018-04-01 | generalization for notifications processing | Ivan Martinez | |
2018-04-01 | generalization for notifications processing | Ivan Martinez | |
2018-03-20 | Add user objects to Event forward payload | Abyss777 | |
2018-02-09 | Remove unnecessary checks | Abyss777 | |
2018-01-26 | Clean up unused imports | Anton Tananaev | |
2018-01-26 | Clean up unnecessary code | Anton Tananaev | |
2017-12-15 | Put mail properties as string | Abyss777 | |
2017-12-15 | Handle boolean parameters in mail related attributes | Abyss777 | |
2017-11-23 | Minor refactoring | Srk | |
2017-11-22 | Minor refactoring | Srk | |
2017-11-22 | Changing form method | Srk | |
2017-11-20 | Refactoring: parameters only for one mode of eventForwarder | Srk | |
2017-11-20 | Minor refactoring | Srk | |
2017-11-20 | Minor refactoring | Srk | |
2017-11-19 | - Global jsonPrettyPrinting option | Srk | |
- Minor refactoring - Config option name changed from "event.forward.prettyPrintedPayload" to "config.mapper.prettyPrintedJson" | |||
2017-11-18 | Rollback getting defaults without having an user instance | Srk | |
2017-11-18 | Rollback number as primitive type | Srk | |
2017-11-18 | Removing notification templates references | Srk | |
2017-11-13 | removing NotificationFormatter from EventForwarder | Shinryuken | |
2017-11-08 | Default payload format as json, plaintext available as option | Shinryuken | |
2017-11-07 | User defaults when no User is available - EventForwarder refactoring | Shinryuken | |
2017-11-06 | Minor refactoring changes | Shinryuken | |
2017-11-06 | Using templates for event forwarded messages | Shinryuken | |
2017-11-04 | Adding 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-09-28 | Make user SMTP config more priority | Abyss777 | |
2017-09-07 | Optimize values parsing | Abyss777 | |
2017-09-07 | Handle correct and incorrect attribute types | Abyss777 | |
2017-09-06 | Move units to attributes and add volume units | Abyss777 | |