For broadcast we only allow a string of one version:
https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-...
This version string is broadcasted to the 'broadcast' channel, so there is
no sense to provide a map, with different channel and other versions.
Perhaps we should make that more clear on the message spec
On Thu, Jul 25, 2013 at 1:17 AM, Corinne Krych <corinnekrych(a)gmail.com>wrote:
Yep
initially created
https://issues.jboss.org/browse/AGIOS-49
bu I guess it's in the wrong category
On Jul 24, 2013, at 6:10 PM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
Do we have jiras for that?
-
abstractj
On Jul 24, 2013, 7:37 PM, Corinne Krych wrote:
Hello all,
Doing some testing on AeroDoc iOS client demo, I noticed that AeroDoc
fails to broadcast when lead has been accepted. Stack trace is:
org.jboss.aerogear.connectivity.rest.sender.PushNotificationSenderEndpoint.broadcast(java.util.Map,javax.servlet.http.HttpServletRequest):
javax.ejb.EJBException: java.lang.ClassCastException:
java.util.LinkedHashMap cannot be cast to java.lang.String
The root of the error is the String cast here:
https://github.com/aerogear/aerogear-unified-push-server/blob/master/src/...
whereas in AeroDoc backend we feed a Map:
https://github.com/aerogear/aerogear-push-quickstart-backend/blob/master/...
Which one is wrong?
Not sure the cast into string is wright.
I've open an iOS JIRA at first thinking this was a client issue
https://issues.jboss.org/browse/AGIOS-49#comment-12792805
++
Corinne
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf