<div dir="ltr">Ah ok, The Push Server is hidden behind a ESB, hum ... interesting :) <div>Can't your "Leatons" REST Service proxy the register request to the push server ?</div><div><br></div><div>Or maybe just let Leaton accept the register request made by the aerogear plugin and store the json payload, later a service can submit that to the UnifiedPush Server. You can find the definition of this endpoint here : <a href="https://aerogear.org/docs/specs/aerogear-unifiedpush-rest-1.0.x/registry/device/index.html">https://aerogear.org/docs/specs/aerogear-unifiedpush-rest-1.0.x/registry/device/index.html</a> </div><div><br></div><div>And I still don't see why you mention the AeroGear Java Sender API, do you mean this <a href="https://github.com/aerogear/aerogear-unifiedpush-java-client">https://github.com/aerogear/aerogear-unifiedpush-java-client</a> ? This unrelated to the registration and used to send push notification.</div><div> </div><div>Hope that helps.</div><div><br></div><div>Seb</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 2, 2015 at 9:27 PM, delalis <span dir="ltr"><<a href="mailto:delalis@gmail.com" target="_blank">delalis@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks Sebastien!<br>
<br>
heres what I sent to my team to give you a better idea of how we had it set<br>
up to use javascript to register with GCM and then Java to insert into the<br>
Aerogear database:<br>
<br>
<br>
- We recently switched from using the “classic phonegap push plugin” to the<br>
“Aerogear phonegap push plugin” because background Android pushes weren’t<br>
coming through, or the payload was different than the classic push plugin<br>
expected, still not sure about that. Either way, it was recommended by<br>
Aerogear devs to switch to the Aerogear push plugin.<br>
<br>
- Our Aerogear server is hidden behind the ESB.<br>
<br>
- The device originally called the Drupal Rest service Leaton created to<br>
register devices<br>
<br>
- We can no longer do that because the Aerogear push plugin requires you to<br>
specify the Aerogear server in a config variable so it can talk DIRECTLY to<br>
the Aerogear service to register the devices. But since it is behind the<br>
ESB, we can not specify this server from the clients perspective.<br>
<br>
- So I thought maybe we can just call the rest service to register the<br>
devices like we used to, and forego the Aerogear’s “register()” function all<br>
together. However, this wont work because calling the “register()” function<br>
is how the client creates a handler to handle the push notifications … i.e.<br>
register(onNotificationGCM)<br>
<br>
- Since the classic push plugin didn’t require an Aerogear server URL, we<br>
were able to use it to register the device with Apple/GCM, and then in the<br>
success method we called Leatons REST service to insert it into a database<br>
on the ESB, and eventually it would make it into Aerogear using a JAVA<br>
service (Aerogears Java Sender API) running on the ESB.<br>
<br>
- But the new Aerogear push plugin’s register() method seems to want to<br>
register the device with Apple/GCM AND with the Aerogear server all in one<br>
step. But since the Aerogear server (ESB) is not accessible to the public,<br>
we are POOCHED.<br>
<br>
I’m going to try to call the register() function without specifying the<br>
aerogear server, but I expect it to fail since the Aerogear push plugin API<br>
says it is required….<br>
<br>
What to do…what to do….<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11735.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notifications-not-working-tp11716p11735.html</a><br>
<div class="HOEnZb"><div class="h5">Sent from the aerogear-dev mailing list archive at Nabble.com.<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></blockquote></div><br></div>