aboutsummaryrefslogtreecommitdiff
path: root/src/org/traccar/notification
AgeCommit message (Collapse)Author
2018-07-27Move notificators to appropriate package and rename.Abyss777
2018-06-27- Rename NotificationException to MessageExceptionAbyss777
- Simplify Notificator instantiation - Make sms configuration more clear - Move some defaults in code - Some cleanup
2018-06-26Rename MailMessage to FullMessageAbyss777
2018-06-26Rename transports to notificatorsAbyss777
2018-06-26Cleanup and some adjustmentsAbyss777
2018-06-26Merge remote-tracking branch 'ivanfmartinez/notifications'Abyss777
# Conflicts: # src/org/traccar/Context.java
2018-06-02Remove async HTTP client dependencyAnton Tananaev
2018-06-01option to instantiate a new SMSNotifier using a different SMSManagerIvan Martinez
2018-06-01update api to support notificatorsIvan Martinez
2018-06-01move NotificatorManager instance to ContextIvan Martinez
2018-06-01make compatible with java 7Ivan Martinez
2018-06-01added warning when using the null notificatorIvan Martinez
2018-06-01generic template namesIvan Martinez
2018-04-11Add support of multiple MaintenancesAbyss777
2018-04-09configuration support for notificatorsIvan Martinez
2018-04-01generalization for notifications processingIvan Martinez
2018-04-01generalization for notifications processingIvan Martinez
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-12-15Put mail properties as stringAbyss777
2017-12-15Handle boolean parameters in mail related attributesAbyss777
2017-11-23Minor refactoringSrk
2017-11-22Minor refactoringSrk
2017-11-22Changing form methodSrk
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-18Rollback getting defaults without having an user instanceSrk
2017-11-18Rollback number as primitive typeSrk
2017-11-18Removing notification templates referencesSrk
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-06Minor refactoring changesShinryuken
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-09-28Make user SMTP config more priorityAbyss777
2017-09-07Optimize values parsingAbyss777
2017-09-07Handle correct and incorrect attribute typesAbyss777
2017-09-06Move units to attributes and add volume unitsAbyss777
2017-08-07Remove "auth" parameter as not necessaryAbyss777
2017-07-26- Implement base manager classes as genericsAbyss777
- Remame getDeviceById and getDeviceByUniqueId functions
2017-07-20Rename Identifiable and Extensible to BaseModel and ExtendedModelAbyss777
2017-07-19Refactored four managersAbyss777
2017-07-13- Save both driver name and driver unique id in trip reportAbyss777
- Map user and driver objects to notification templates - Add driverUnauthorized templates
2017-04-29Save more statistics infoAnton Tananaev
2017-04-20Add a Date: header in notification emailsRenaud Allard