<div dir="ltr"><div>Hello,</div><div><br></div><div>while evaluating the PicketLink IDM for our "storage" requirements (see older emails), I started writing a Java EE version of the "Push/connectivity" server:</div>
<div>AeroGear PushEE -> <a href="https://github.com/matzew/pushee">https://github.com/matzew/pushee</a></div><div><br></div><div>(Dont' worry to much about the name :) ) </div><div><br></div><div>Compared to the vert.x version it's using a more complete/richer API (real classes, instead of a large JsonObject). Also it has slightly more of an internal abstraction</div>
<div>(abstract entity base class, DAO access for all the entities, services accessing the DAOs, RESTendpoints simply accessing the services).</div><div><br></div><div>Oh, also, the "iOS" variant is now supporting a _real_ upload of the certificate (stored as Lob)</div>
<div><br></div><div>## Cloud</div><div><br></div><div>I tested the WAR file, on my private OpenShift Account (with the JBoss 7.1.x config there), afterwards I tested the messaging:</div><div>I could send message to my iPhone and to my Android device - so the Openshift cloud does NOT permit connecting to Apple's APNs (and Google)</div>
<div><br></div><div>Storage:</div><div>* All "beans" are JPA entities</div><div>* No IDM integration, due to the IRC suggestion to simply model the beans as entities</div><div>==> However, since the Database for the push is a _standalone_ thing, and there is no real user (just an optional "client identifier"), this means I could move the "beans" and store the in IDM</div>
<div><br></div><div style>Regarding IDM, please review also older threads regarding this, on the ML</div><div><br></div><div>Thoughts?</div><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div>