New message format

fixing AGPUSH-1044
ah, ok - that's reasonable, to name that payload (instead of message)

On Thu, Oct 23, 2014 at 1:38 PM, Sebastien Blanc <notifications@github.com>
wrote:

> In
> jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java:
>
> > -     *     "message":
> > -     *     {
> > -     *       "key":"value",
> > -     *       "key2":"other value",
> > -     *       "alert":"HELLO!",
> > -     *       "action-category":"some value",
> > -     *       "sound":"default",
> > -     *       "badge":2,
> > -     *       "content-available" : true
> > +     *     "message": {
> > +     *      "alert": "HELLO!",
> > +     *      "action-category": "some value",
> > +     *      "sound": "default",
> > +     *      "badge": 2,
> > +     *      "content-available": true,
> > +     *      "data": {
>
> hum, was confused by
> https://github.com/edewit/aerogear-unifiedpush-server/blob/new-message-format/push/src/main/java/org/jboss/aerogear/unifiedpush/message/UnifiedPushMessage.java#L40
> where payload is an attribute of the message
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/411/files#r19271742>
> .
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf