From edewit at redhat.com Wed Apr 1 05:08:53 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 1 Apr 2015 11:08:53 +0200 Subject: [aerogear-dev] status Message-ID: Hi, Right now we have a ping endpoint, but we need a health check as well. what we could check in this health check are the state of the database, send a ping to the push networks. And then send a response accordingly 'critical' if the database is not up, 'warn' if one of the networks is not responding and 'ok' if everything is fine. I've created a issue for it https://issues.jboss.org/browse/AGPUSH-1347 WDYT? -- Cheers, Erik Jan From matzew at apache.org Wed Apr 1 07:36:09 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 1 Apr 2015 13:36:09 +0200 Subject: [aerogear-dev] status In-Reply-To: References: Message-ID: sounds good! IMO the endpoint should be protected by Keycloak, so it is only accessible for registered UPS users On Wed, Apr 1, 2015 at 11:08 AM, Erik Jan de Wit wrote: > Hi, > > Right now we have a ping endpoint, but we need a health check as well. > what we could check in this health check are the state of the > database, send a ping to the push networks. And then send a response > accordingly 'critical' if the database is not up, 'warn' if one of the > networks is not responding and 'ok' if everything is fine. I've > created a issue for it https://issues.jboss.org/browse/AGPUSH-1347 > > WDYT? > > -- > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150401/51d40ebc/attachment.html From idel.pivnitskiy at gmail.com Wed Apr 1 08:24:26 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Wed, 1 Apr 2015 15:24:26 +0300 Subject: [aerogear-dev] GSoC project for WebPush Server In-Reply-To: References: Message-ID: I'm ready to update my proposal! Here is what I want to add: https://www.dropbox.com/s/y51denpp3b4ojar/Idel.Pivnitskiy.WebPush.pdf Please, leave comments if you have suggestions of how improve it. Also, please, enable edit mode for my proposal on Melange: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/idel/5689792285114368 Best regards, Idel Pivnitskiy -- E-mail: Idel.Pivnitskiy at gmail.com GitHub: @idelpivnitskiy 2015-03-31 16:20 GMT+03:00 Sebastien Blanc : > +1 > > On Tue, Mar 31, 2015 at 3:20 PM, Matthias Wessendorf > wrote: > >> That's a good point. I thought I added it :-) But yeah, keeping our own >> server to stay up-to-date with this emerging spec is good for all of us :-) >> >> On Tue, Mar 31, 2015 at 3:15 PM, Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> wrote: >> >>> If vert.x server has a low priority and may take a long time I can >>> remove it from my proposal and add another task: >>> "Update WebPush Server to use a new WebPush Protocol spec". Because >>> current spec will expire during this summer (June 15, 2015). >>> http://tools.ietf.org/html/draft-thomson-webpush-http2-02 >>> >>> Best regards, >>> Idel Pivnitskiy >>> -- >>> E-mail: Idel.Pivnitskiy at gmail.com >>> GitHub: @idelpivnitskiy >>> >>> 2015-03-31 15:54 GMT+03:00 Matthias Wessendorf : >>> >>>> >>>> >>>> On Tue, Mar 31, 2015 at 2:48 PM, Sebastien Blanc >>>> wrote: >>>> >>>>> >>>>> >>>>> On Tue, Mar 31, 2015 at 12:48 PM, Matthias Wessendorf < >>>>> matzew at apache.org> wrote: >>>>> >>>>>> Hi Idel, >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Mar 31, 2015 at 12:14 PM, Idel Pivnitskiy < >>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>> >>>>>>> Thanks to all! >>>>>>> >>>>>>> Sounds interesting! I've read source code of UPS and SimplePush and >>>>>>> it won't be a problem for me to add support for WebPush >>>>>>> >>>>>> >>>>>> sweet >>>>>> >>>>>> and update aerogear-unifiedpush-java-client to support it too. >>>>>>> >>>>>> >>>>>> that one does likely does not need any update. It sends the payload >>>>>> to UPS, and UPS delivers to all supported Push Networks (e.g APNs or a >>>>>> WebPush enabled server) >>>>>> >>>>>> >>>>>> >>>>>>> Also I can write something like aerogear-simplepush-java-client for >>>>>>> WebPush and some vert.x module. >>>>>>> Do I understand this part of the job? >>>>>>> >>>>>> That's right. Get a client codec for WebPush in place, stick that >>>>>> into a client like the above for simplepush. Leverage that client in a >>>>>> vert.x 3 module >>>>>> >>>>> For vert.x, what I had in mind was more an implementation of the >>>>> server (like Dan did for SimplePush) but that makes it maybe a bit too much >>>>> ... >>>>> >>>> >>>> if time allows that - ok, but I don't see too much value of creating a >>>> server that directly is competing with our own server.... >>>> >>>> >>>>> >>>>>> >>>>>>> >>>>>>> But I'm not familiar with IoT devices. Where I can find how to >>>>>>> deploy test applications and test them? Could you, please, clarify this >>>>>>> idea? >>>>>>> >>>>>> >>>>>> Some highlevel ideas: >>>>>> >>>>>> https://matthiaswessendorf.wordpress.com/2015/03/25/push-notifications-and-the-internet-of-things/ >>>>>> >>>>>> Checkout Sebi's cool videos. IMO if something runs on a Pi, Ardino or >>>>>> a Lego Robot :-) we are talking. hehe >>>>>> >>>>>> >>>>>>> >>>>>>> Best regards, >>>>>>> Idel Pivnitskiy >>>>>>> -- >>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>> GitHub: @idelpivnitskiy >>>>>>> >>>>>>> 2015-03-30 17:03 GMT+03:00 Matthias Wessendorf : >>>>>>> >>>>>>>> +1 >>>>>>>> >>>>>>>> all of these items could be all done in one GSOC project. Perhaps, >>>>>>>> to have something more "fancy", the project aims to offer "WebPush support >>>>>>>> for mobile cloud services on IoT devices". >>>>>>>> Needed deliverables: >>>>>>>> * UPS support for WebPush >>>>>>>> * Java client of the WebPush wireprotocol, that can be wrapped in >>>>>>>> the mentioned vert.x module >>>>>>>> * demo app of showing the WebPush standard on IoT devices, with >>>>>>>> mobile cloud services (like UPS) >>>>>>>> >>>>>>>> IMO this would make a nice project. It even may be also the case >>>>>>>> that some "WebPush codec" code could be contributed back to Netty project, >>>>>>>> if needed. >>>>>>>> >>>>>>>> -Matthias >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Monday, March 30, 2015, Sebastien Blanc >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> I see 2 or 3 differents topics that could be articulated around >>>>>>>>> WebPush : >>>>>>>>> >>>>>>>>> - Add WebPush support to the UnifiedPush Server >>>>>>>>> - Create a lightweight Java WebPush Client (think of embedded >>>>>>>>> device) >>>>>>>>> - Create a vert.x mod that implements the WebPush protocol. >>>>>>>>> >>>>>>>>> Sebi >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Mar 30, 2015 at 3:06 PM, Idel Pivnitskiy < >>>>>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>> I participated in GSoC 2014 with Twitter and worked on Netty last >>>>>>>>>> year. Unfortunately, this year Google does not accept Twitter as a >>>>>>>>>> mentoring organization. So I'm trying to find a new organization and a new >>>>>>>>>> project for this summer. >>>>>>>>>> >>>>>>>>>> I know that time for student applications is over, but I have one >>>>>>>>>> opened proposal for JBoss Community. I found WebPush Server at the last day >>>>>>>>>> of student applications' deadline. I'm really interested in it and I want >>>>>>>>>> to change my proposal and work on WebPush Server! >>>>>>>>>> >>>>>>>>>> WebPush Server is a new project which should have many tasks and >>>>>>>>>> plan to use new features of Netty 5 (HTTP/2) and Java 8. All of these are >>>>>>>>>> very interesting for me. Also I have 2 years experience of server-side >>>>>>>>>> development of other services (mobile API, administrative panels, etc.) on >>>>>>>>>> Jetty, WildFly and JBoss AS7. So I will be able to work on any part of >>>>>>>>>> WebPush Server and not only on server-netty subproject. >>>>>>>>>> >>>>>>>>>> I began to get acquainted with the WebPush Server code >>>>>>>>>> base, WebPush Protocol and Push API last weekend. Also I I've >>>>>>>>>> used AeroGear UnifiedPush Server in one of my projects on my work. And it's >>>>>>>>>> perfect! AeroGear is easy to configure and push notifications. Thanks to >>>>>>>>>> all for this work! >>>>>>>>>> >>>>>>>>>> Could you, please, help me to find a project idea for my new >>>>>>>>>> proposal for WebPush Server? >>>>>>>>>> >>>>>>>>>> Best regards, >>>>>>>>>> Idel Pivnitskiy >>>>>>>>>> -- >>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>> Resume: >>>>>>>>>> https://www.dropbox.com/s/q99epi9jyygvaxf/Idel.Pivnitskiy.resume.pdf >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150401/619112a7/attachment-0001.html From matzew at apache.org Wed Apr 1 09:31:25 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 1 Apr 2015 15:31:25 +0200 Subject: [aerogear-dev] GSoC project for WebPush Server In-Reply-To: References: Message-ID: Hi Idel, it is editable :-) On Wed, Apr 1, 2015 at 2:24 PM, Idel Pivnitskiy wrote: > I'm ready to update my proposal! Here is what I want to add: > https://www.dropbox.com/s/y51denpp3b4ojar/Idel.Pivnitskiy.WebPush.pdf > > Please, leave comments if you have suggestions of how improve it. > Also, please, enable edit mode for my proposal on Melange: > > https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/idel/5689792285114368 > > Best regards, > Idel Pivnitskiy > -- > E-mail: Idel.Pivnitskiy at gmail.com > GitHub: @idelpivnitskiy > > 2015-03-31 16:20 GMT+03:00 Sebastien Blanc : > >> +1 >> >> On Tue, Mar 31, 2015 at 3:20 PM, Matthias Wessendorf >> wrote: >> >>> That's a good point. I thought I added it :-) But yeah, keeping our own >>> server to stay up-to-date with this emerging spec is good for all of us :-) >>> >>> On Tue, Mar 31, 2015 at 3:15 PM, Idel Pivnitskiy < >>> idel.pivnitskiy at gmail.com> wrote: >>> >>>> If vert.x server has a low priority and may take a long time I can >>>> remove it from my proposal and add another task: >>>> "Update WebPush Server to use a new WebPush Protocol spec". Because >>>> current spec will expire during this summer (June 15, 2015). >>>> http://tools.ietf.org/html/draft-thomson-webpush-http2-02 >>>> >>>> Best regards, >>>> Idel Pivnitskiy >>>> -- >>>> E-mail: Idel.Pivnitskiy at gmail.com >>>> GitHub: @idelpivnitskiy >>>> >>>> 2015-03-31 15:54 GMT+03:00 Matthias Wessendorf : >>>> >>>>> >>>>> >>>>> On Tue, Mar 31, 2015 at 2:48 PM, Sebastien Blanc >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Tue, Mar 31, 2015 at 12:48 PM, Matthias Wessendorf < >>>>>> matzew at apache.org> wrote: >>>>>> >>>>>>> Hi Idel, >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Mar 31, 2015 at 12:14 PM, Idel Pivnitskiy < >>>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>>> >>>>>>>> Thanks to all! >>>>>>>> >>>>>>>> Sounds interesting! I've read source code of UPS and SimplePush and >>>>>>>> it won't be a problem for me to add support for WebPush >>>>>>>> >>>>>>> >>>>>>> sweet >>>>>>> >>>>>>> and update aerogear-unifiedpush-java-client to support it too. >>>>>>>> >>>>>>> >>>>>>> that one does likely does not need any update. It sends the payload >>>>>>> to UPS, and UPS delivers to all supported Push Networks (e.g APNs or a >>>>>>> WebPush enabled server) >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Also I can write something like aerogear-simplepush-java-client for >>>>>>>> WebPush and some vert.x module. >>>>>>>> Do I understand this part of the job? >>>>>>>> >>>>>>> That's right. Get a client codec for WebPush in place, stick that >>>>>>> into a client like the above for simplepush. Leverage that client in a >>>>>>> vert.x 3 module >>>>>>> >>>>>> For vert.x, what I had in mind was more an implementation of the >>>>>> server (like Dan did for SimplePush) but that makes it maybe a bit too much >>>>>> ... >>>>>> >>>>> >>>>> if time allows that - ok, but I don't see too much value of creating a >>>>> server that directly is competing with our own server.... >>>>> >>>>> >>>>>> >>>>>>> >>>>>>>> >>>>>>>> But I'm not familiar with IoT devices. Where I can find how to >>>>>>>> deploy test applications and test them? Could you, please, clarify this >>>>>>>> idea? >>>>>>>> >>>>>>> >>>>>>> Some highlevel ideas: >>>>>>> >>>>>>> https://matthiaswessendorf.wordpress.com/2015/03/25/push-notifications-and-the-internet-of-things/ >>>>>>> >>>>>>> Checkout Sebi's cool videos. IMO if something runs on a Pi, Ardino >>>>>>> or a Lego Robot :-) we are talking. hehe >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Best regards, >>>>>>>> Idel Pivnitskiy >>>>>>>> -- >>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>> GitHub: @idelpivnitskiy >>>>>>>> >>>>>>>> 2015-03-30 17:03 GMT+03:00 Matthias Wessendorf : >>>>>>>> >>>>>>>>> +1 >>>>>>>>> >>>>>>>>> all of these items could be all done in one GSOC project. Perhaps, >>>>>>>>> to have something more "fancy", the project aims to offer "WebPush support >>>>>>>>> for mobile cloud services on IoT devices". >>>>>>>>> Needed deliverables: >>>>>>>>> * UPS support for WebPush >>>>>>>>> * Java client of the WebPush wireprotocol, that can be wrapped in >>>>>>>>> the mentioned vert.x module >>>>>>>>> * demo app of showing the WebPush standard on IoT devices, with >>>>>>>>> mobile cloud services (like UPS) >>>>>>>>> >>>>>>>>> IMO this would make a nice project. It even may be also the case >>>>>>>>> that some "WebPush codec" code could be contributed back to Netty project, >>>>>>>>> if needed. >>>>>>>>> >>>>>>>>> -Matthias >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Monday, March 30, 2015, Sebastien Blanc >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> I see 2 or 3 differents topics that could be articulated around >>>>>>>>>> WebPush : >>>>>>>>>> >>>>>>>>>> - Add WebPush support to the UnifiedPush Server >>>>>>>>>> - Create a lightweight Java WebPush Client (think of embedded >>>>>>>>>> device) >>>>>>>>>> - Create a vert.x mod that implements the WebPush protocol. >>>>>>>>>> >>>>>>>>>> Sebi >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Mar 30, 2015 at 3:06 PM, Idel Pivnitskiy < >>>>>>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi all, >>>>>>>>>>> >>>>>>>>>>> I participated in GSoC 2014 with Twitter and worked on Netty >>>>>>>>>>> last year. Unfortunately, this year Google does not accept Twitter as a >>>>>>>>>>> mentoring organization. So I'm trying to find a new organization and a new >>>>>>>>>>> project for this summer. >>>>>>>>>>> >>>>>>>>>>> I know that time for student applications is over, but I have >>>>>>>>>>> one opened proposal for JBoss Community. I found WebPush Server at the last >>>>>>>>>>> day of student applications' deadline. I'm really interested in it and I >>>>>>>>>>> want to change my proposal and work on WebPush Server! >>>>>>>>>>> >>>>>>>>>>> WebPush Server is a new project which should have many tasks >>>>>>>>>>> and plan to use new features of Netty 5 (HTTP/2) and Java 8. All of these >>>>>>>>>>> are very interesting for me. Also I have 2 years experience of server-side >>>>>>>>>>> development of other services (mobile API, administrative panels, etc.) on >>>>>>>>>>> Jetty, WildFly and JBoss AS7. So I will be able to work on any part of >>>>>>>>>>> WebPush Server and not only on server-netty subproject. >>>>>>>>>>> >>>>>>>>>>> I began to get acquainted with the WebPush Server code >>>>>>>>>>> base, WebPush Protocol and Push API last weekend. Also I I've >>>>>>>>>>> used AeroGear UnifiedPush Server in one of my projects on my work. And it's >>>>>>>>>>> perfect! AeroGear is easy to configure and push notifications. Thanks to >>>>>>>>>>> all for this work! >>>>>>>>>>> >>>>>>>>>>> Could you, please, help me to find a project idea for my new >>>>>>>>>>> proposal for WebPush Server? >>>>>>>>>>> >>>>>>>>>>> Best regards, >>>>>>>>>>> Idel Pivnitskiy >>>>>>>>>>> -- >>>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>>> Resume: >>>>>>>>>>> https://www.dropbox.com/s/q99epi9jyygvaxf/Idel.Pivnitskiy.resume.pdf >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150401/bc2118ec/attachment-0001.html From scm.blanc at gmail.com Wed Apr 1 09:39:41 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 1 Apr 2015 15:39:41 +0200 Subject: [aerogear-dev] GSoC project for WebPush Server In-Reply-To: References: Message-ID: Hi Idel ! Very nice ! I have jsut one suggestion about the title which is very long IMO, maybe just "WebPush support for mobile cloud services" , in the content, you mention IoT , so it's okay. what do you think ? Seb On Wed, Apr 1, 2015 at 3:31 PM, Matthias Wessendorf wrote: > Hi Idel, > > it is editable :-) > > On Wed, Apr 1, 2015 at 2:24 PM, Idel Pivnitskiy > wrote: > >> I'm ready to update my proposal! Here is what I want to add: >> https://www.dropbox.com/s/y51denpp3b4ojar/Idel.Pivnitskiy.WebPush.pdf >> >> Please, leave comments if you have suggestions of how improve it. >> Also, please, enable edit mode for my proposal on Melange: >> >> https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/idel/5689792285114368 >> >> Best regards, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> GitHub: @idelpivnitskiy >> >> 2015-03-31 16:20 GMT+03:00 Sebastien Blanc : >> >>> +1 >>> >>> On Tue, Mar 31, 2015 at 3:20 PM, Matthias Wessendorf >>> wrote: >>> >>>> That's a good point. I thought I added it :-) But yeah, keeping our own >>>> server to stay up-to-date with this emerging spec is good for all of us :-) >>>> >>>> On Tue, Mar 31, 2015 at 3:15 PM, Idel Pivnitskiy < >>>> idel.pivnitskiy at gmail.com> wrote: >>>> >>>>> If vert.x server has a low priority and may take a long time I can >>>>> remove it from my proposal and add another task: >>>>> "Update WebPush Server to use a new WebPush Protocol spec". Because >>>>> current spec will expire during this summer (June 15, 2015). >>>>> http://tools.ietf.org/html/draft-thomson-webpush-http2-02 >>>>> >>>>> Best regards, >>>>> Idel Pivnitskiy >>>>> -- >>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>> GitHub: @idelpivnitskiy >>>>> >>>>> 2015-03-31 15:54 GMT+03:00 Matthias Wessendorf : >>>>> >>>>>> >>>>>> >>>>>> On Tue, Mar 31, 2015 at 2:48 PM, Sebastien Blanc >>>>> > wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Mar 31, 2015 at 12:48 PM, Matthias Wessendorf < >>>>>>> matzew at apache.org> wrote: >>>>>>> >>>>>>>> Hi Idel, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Mar 31, 2015 at 12:14 PM, Idel Pivnitskiy < >>>>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>>>> >>>>>>>>> Thanks to all! >>>>>>>>> >>>>>>>>> Sounds interesting! I've read source code of UPS and SimplePush >>>>>>>>> and it won't be a problem for me to add support for WebPush >>>>>>>>> >>>>>>>> >>>>>>>> sweet >>>>>>>> >>>>>>>> and update aerogear-unifiedpush-java-client to support it too. >>>>>>>>> >>>>>>>> >>>>>>>> that one does likely does not need any update. It sends the payload >>>>>>>> to UPS, and UPS delivers to all supported Push Networks (e.g APNs or a >>>>>>>> WebPush enabled server) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Also I can write something like aerogear-simplepush-java-client >>>>>>>>> for WebPush and some vert.x module. >>>>>>>>> Do I understand this part of the job? >>>>>>>>> >>>>>>>> That's right. Get a client codec for WebPush in place, stick that >>>>>>>> into a client like the above for simplepush. Leverage that client in a >>>>>>>> vert.x 3 module >>>>>>>> >>>>>>> For vert.x, what I had in mind was more an implementation of the >>>>>>> server (like Dan did for SimplePush) but that makes it maybe a bit too much >>>>>>> ... >>>>>>> >>>>>> >>>>>> if time allows that - ok, but I don't see too much value of creating >>>>>> a server that directly is competing with our own server.... >>>>>> >>>>>> >>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> But I'm not familiar with IoT devices. Where I can find how to >>>>>>>>> deploy test applications and test them? Could you, please, clarify this >>>>>>>>> idea? >>>>>>>>> >>>>>>>> >>>>>>>> Some highlevel ideas: >>>>>>>> >>>>>>>> https://matthiaswessendorf.wordpress.com/2015/03/25/push-notifications-and-the-internet-of-things/ >>>>>>>> >>>>>>>> Checkout Sebi's cool videos. IMO if something runs on a Pi, Ardino >>>>>>>> or a Lego Robot :-) we are talking. hehe >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> Idel Pivnitskiy >>>>>>>>> -- >>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>> >>>>>>>>> 2015-03-30 17:03 GMT+03:00 Matthias Wessendorf >>>>>>>>> : >>>>>>>>> >>>>>>>>>> +1 >>>>>>>>>> >>>>>>>>>> all of these items could be all done in one GSOC project. >>>>>>>>>> Perhaps, to have something more "fancy", the project aims to offer "WebPush >>>>>>>>>> support for mobile cloud services on IoT devices". >>>>>>>>>> Needed deliverables: >>>>>>>>>> * UPS support for WebPush >>>>>>>>>> * Java client of the WebPush wireprotocol, that can be wrapped in >>>>>>>>>> the mentioned vert.x module >>>>>>>>>> * demo app of showing the WebPush standard on IoT devices, with >>>>>>>>>> mobile cloud services (like UPS) >>>>>>>>>> >>>>>>>>>> IMO this would make a nice project. It even may be also the case >>>>>>>>>> that some "WebPush codec" code could be contributed back to Netty project, >>>>>>>>>> if needed. >>>>>>>>>> >>>>>>>>>> -Matthias >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Monday, March 30, 2015, Sebastien Blanc >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> I see 2 or 3 differents topics that could be articulated around >>>>>>>>>>> WebPush : >>>>>>>>>>> >>>>>>>>>>> - Add WebPush support to the UnifiedPush Server >>>>>>>>>>> - Create a lightweight Java WebPush Client (think of embedded >>>>>>>>>>> device) >>>>>>>>>>> - Create a vert.x mod that implements the WebPush protocol. >>>>>>>>>>> >>>>>>>>>>> Sebi >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Mar 30, 2015 at 3:06 PM, Idel Pivnitskiy < >>>>>>>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi all, >>>>>>>>>>>> >>>>>>>>>>>> I participated in GSoC 2014 with Twitter and worked on Netty >>>>>>>>>>>> last year. Unfortunately, this year Google does not accept Twitter as a >>>>>>>>>>>> mentoring organization. So I'm trying to find a new organization and a new >>>>>>>>>>>> project for this summer. >>>>>>>>>>>> >>>>>>>>>>>> I know that time for student applications is over, but I have >>>>>>>>>>>> one opened proposal for JBoss Community. I found WebPush Server at the last >>>>>>>>>>>> day of student applications' deadline. I'm really interested in it and I >>>>>>>>>>>> want to change my proposal and work on WebPush Server! >>>>>>>>>>>> >>>>>>>>>>>> WebPush Server is a new project which should have many tasks >>>>>>>>>>>> and plan to use new features of Netty 5 (HTTP/2) and Java 8. All of these >>>>>>>>>>>> are very interesting for me. Also I have 2 years experience of server-side >>>>>>>>>>>> development of other services (mobile API, administrative panels, etc.) on >>>>>>>>>>>> Jetty, WildFly and JBoss AS7. So I will be able to work on any part of >>>>>>>>>>>> WebPush Server and not only on server-netty subproject. >>>>>>>>>>>> >>>>>>>>>>>> I began to get acquainted with the WebPush Server code >>>>>>>>>>>> base, WebPush Protocol and Push API last weekend. Also I I've >>>>>>>>>>>> used AeroGear UnifiedPush Server in one of my projects on my work. And it's >>>>>>>>>>>> perfect! AeroGear is easy to configure and push notifications. Thanks to >>>>>>>>>>>> all for this work! >>>>>>>>>>>> >>>>>>>>>>>> Could you, please, help me to find a project idea for my new >>>>>>>>>>>> proposal for WebPush Server? >>>>>>>>>>>> >>>>>>>>>>>> Best regards, >>>>>>>>>>>> Idel Pivnitskiy >>>>>>>>>>>> -- >>>>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>>>> Resume: >>>>>>>>>>>> https://www.dropbox.com/s/q99epi9jyygvaxf/Idel.Pivnitskiy.resume.pdf >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at 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 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150401/cba9f0eb/attachment-0001.html From idel.pivnitskiy at gmail.com Wed Apr 1 09:45:28 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Wed, 1 Apr 2015 16:45:28 +0300 Subject: [aerogear-dev] GSoC project for WebPush Server In-Reply-To: References: Message-ID: Sure! The shorter title is better :) Any suggestions about expected results or project timeline? Or may be I should add some additional descriptions about my plans? Best, Idel -- E-mail: Idel.Pivnitskiy at gmail.com GitHub: @idelpivnitskiy 2015-04-01 16:39 GMT+03:00 Sebastien Blanc : > Hi Idel ! > Very nice ! > I have jsut one suggestion about the title which is very long IMO, maybe > just "WebPush support for mobile cloud services" , in the content, you > mention IoT , so it's okay. > what do you think ? > Seb > > > On Wed, Apr 1, 2015 at 3:31 PM, Matthias Wessendorf > wrote: > >> Hi Idel, >> >> it is editable :-) >> >> On Wed, Apr 1, 2015 at 2:24 PM, Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> wrote: >> >>> I'm ready to update my proposal! Here is what I want to add: >>> https://www.dropbox.com/s/y51denpp3b4ojar/Idel.Pivnitskiy.WebPush.pdf >>> >>> Please, leave comments if you have suggestions of how improve it. >>> Also, please, enable edit mode for my proposal on Melange: >>> >>> https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/idel/5689792285114368 >>> >>> Best regards, >>> Idel Pivnitskiy >>> -- >>> E-mail: Idel.Pivnitskiy at gmail.com >>> GitHub: @idelpivnitskiy >>> >>> 2015-03-31 16:20 GMT+03:00 Sebastien Blanc : >>> >>>> +1 >>>> >>>> On Tue, Mar 31, 2015 at 3:20 PM, Matthias Wessendorf >>> > wrote: >>>> >>>>> That's a good point. I thought I added it :-) But yeah, keeping our >>>>> own server to stay up-to-date with this emerging spec is good for all of us >>>>> :-) >>>>> >>>>> On Tue, Mar 31, 2015 at 3:15 PM, Idel Pivnitskiy < >>>>> idel.pivnitskiy at gmail.com> wrote: >>>>> >>>>>> If vert.x server has a low priority and may take a long time I can >>>>>> remove it from my proposal and add another task: >>>>>> "Update WebPush Server to use a new WebPush Protocol spec". Because >>>>>> current spec will expire during this summer (June 15, 2015). >>>>>> http://tools.ietf.org/html/draft-thomson-webpush-http2-02 >>>>>> >>>>>> Best regards, >>>>>> Idel Pivnitskiy >>>>>> -- >>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>> GitHub: @idelpivnitskiy >>>>>> >>>>>> 2015-03-31 15:54 GMT+03:00 Matthias Wessendorf : >>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Mar 31, 2015 at 2:48 PM, Sebastien Blanc < >>>>>>> scm.blanc at gmail.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Mar 31, 2015 at 12:48 PM, Matthias Wessendorf < >>>>>>>> matzew at apache.org> wrote: >>>>>>>> >>>>>>>>> Hi Idel, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Tue, Mar 31, 2015 at 12:14 PM, Idel Pivnitskiy < >>>>>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Thanks to all! >>>>>>>>>> >>>>>>>>>> Sounds interesting! I've read source code of UPS and SimplePush >>>>>>>>>> and it won't be a problem for me to add support for WebPush >>>>>>>>>> >>>>>>>>> >>>>>>>>> sweet >>>>>>>>> >>>>>>>>> and update aerogear-unifiedpush-java-client to support it too. >>>>>>>>>> >>>>>>>>> >>>>>>>>> that one does likely does not need any update. It sends the >>>>>>>>> payload to UPS, and UPS delivers to all supported Push Networks (e.g APNs >>>>>>>>> or a WebPush enabled server) >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> Also I can write something like aerogear-simplepush-java-client >>>>>>>>>> for WebPush and some vert.x module. >>>>>>>>>> Do I understand this part of the job? >>>>>>>>>> >>>>>>>>> That's right. Get a client codec for WebPush in place, stick that >>>>>>>>> into a client like the above for simplepush. Leverage that client in a >>>>>>>>> vert.x 3 module >>>>>>>>> >>>>>>>> For vert.x, what I had in mind was more an implementation of the >>>>>>>> server (like Dan did for SimplePush) but that makes it maybe a bit too much >>>>>>>> ... >>>>>>>> >>>>>>> >>>>>>> if time allows that - ok, but I don't see too much value of creating >>>>>>> a server that directly is competing with our own server.... >>>>>>> >>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> But I'm not familiar with IoT devices. Where I can find how to >>>>>>>>>> deploy test applications and test them? Could you, please, clarify this >>>>>>>>>> idea? >>>>>>>>>> >>>>>>>>> >>>>>>>>> Some highlevel ideas: >>>>>>>>> >>>>>>>>> https://matthiaswessendorf.wordpress.com/2015/03/25/push-notifications-and-the-internet-of-things/ >>>>>>>>> >>>>>>>>> Checkout Sebi's cool videos. IMO if something runs on a Pi, Ardino >>>>>>>>> or a Lego Robot :-) we are talking. hehe >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Best regards, >>>>>>>>>> Idel Pivnitskiy >>>>>>>>>> -- >>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>> >>>>>>>>>> 2015-03-30 17:03 GMT+03:00 Matthias Wessendorf >>>>>>>>> >: >>>>>>>>>> >>>>>>>>>>> +1 >>>>>>>>>>> >>>>>>>>>>> all of these items could be all done in one GSOC project. >>>>>>>>>>> Perhaps, to have something more "fancy", the project aims to offer "WebPush >>>>>>>>>>> support for mobile cloud services on IoT devices". >>>>>>>>>>> Needed deliverables: >>>>>>>>>>> * UPS support for WebPush >>>>>>>>>>> * Java client of the WebPush wireprotocol, that can be wrapped >>>>>>>>>>> in the mentioned vert.x module >>>>>>>>>>> * demo app of showing the WebPush standard on IoT devices, with >>>>>>>>>>> mobile cloud services (like UPS) >>>>>>>>>>> >>>>>>>>>>> IMO this would make a nice project. It even may be also the case >>>>>>>>>>> that some "WebPush codec" code could be contributed back to Netty project, >>>>>>>>>>> if needed. >>>>>>>>>>> >>>>>>>>>>> -Matthias >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Monday, March 30, 2015, Sebastien Blanc >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> I see 2 or 3 differents topics that could be articulated around >>>>>>>>>>>> WebPush : >>>>>>>>>>>> >>>>>>>>>>>> - Add WebPush support to the UnifiedPush Server >>>>>>>>>>>> - Create a lightweight Java WebPush Client (think of embedded >>>>>>>>>>>> device) >>>>>>>>>>>> - Create a vert.x mod that implements the WebPush protocol. >>>>>>>>>>>> >>>>>>>>>>>> Sebi >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Mar 30, 2015 at 3:06 PM, Idel Pivnitskiy < >>>>>>>>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi all, >>>>>>>>>>>>> >>>>>>>>>>>>> I participated in GSoC 2014 with Twitter and worked on Netty >>>>>>>>>>>>> last year. Unfortunately, this year Google does not accept Twitter as a >>>>>>>>>>>>> mentoring organization. So I'm trying to find a new organization and a new >>>>>>>>>>>>> project for this summer. >>>>>>>>>>>>> >>>>>>>>>>>>> I know that time for student applications is over, but I have >>>>>>>>>>>>> one opened proposal for JBoss Community. I found WebPush Server at the last >>>>>>>>>>>>> day of student applications' deadline. I'm really interested in it and I >>>>>>>>>>>>> want to change my proposal and work on WebPush Server! >>>>>>>>>>>>> >>>>>>>>>>>>> WebPush Server is a new project which should have many tasks >>>>>>>>>>>>> and plan to use new features of Netty 5 (HTTP/2) and Java 8. All of these >>>>>>>>>>>>> are very interesting for me. Also I have 2 years experience of server-side >>>>>>>>>>>>> development of other services (mobile API, administrative panels, etc.) on >>>>>>>>>>>>> Jetty, WildFly and JBoss AS7. So I will be able to work on any part of >>>>>>>>>>>>> WebPush Server and not only on server-netty subproject. >>>>>>>>>>>>> >>>>>>>>>>>>> I began to get acquainted with the WebPush Server code >>>>>>>>>>>>> base, WebPush Protocol and Push API last weekend. Also I I've >>>>>>>>>>>>> used AeroGear UnifiedPush Server in one of my projects on my work. And it's >>>>>>>>>>>>> perfect! AeroGear is easy to configure and push notifications. Thanks to >>>>>>>>>>>>> all for this work! >>>>>>>>>>>>> >>>>>>>>>>>>> Could you, please, help me to find a project idea for my new >>>>>>>>>>>>> proposal for WebPush Server? >>>>>>>>>>>>> >>>>>>>>>>>>> Best regards, >>>>>>>>>>>>> Idel Pivnitskiy >>>>>>>>>>>>> -- >>>>>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>>>>> Resume: >>>>>>>>>>>>> https://www.dropbox.com/s/q99epi9jyygvaxf/Idel.Pivnitskiy.resume.pdf >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at 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 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150401/0324ceca/attachment-0001.html From dpassos at redhat.com Wed Apr 1 10:18:21 2015 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 1 Apr 2015 11:18:21 -0300 Subject: [aerogear-dev] Automatic quickstart ftesting solution In-Reply-To: References: Message-ID: That is really awesome. Is possible create and use an emulator instead of a real device. -- Passos On Wed, Mar 25, 2015 at 12:37 PM, Stefan Miklosovic wrote: > Hi, > > I think few days ago there was some information from Karel Piwko that we > developed fully automatic functional tests when it comes to Cordova > quickstarts (1) (hello world and shoot and share) > > We think that it could be useful for developers as well. This tests the > whole life cycle of the push from creation of UPS cartridge through > building of the example to the functional test in a fully automatic manner > from zero setup to push notification receive at mobile device you have > connected to your notebook and it could be useful for developers in order > to not execute it manually every time and set it up all over again. > > By what I mean "fully automatic" is the following scenario: > > 1) Automatic creation of UPS cartridge on OpenShift right from our test, > patched with this extension * (2), (3) > 2) Because of the deployed extension to UPS in 1), we can login via REST > and we do not need to change passwords so we can create application with > some variant directly from our test script (4) > 3) After this is done, quickstart example is downloaded from GH, Android > SDK is installed locally at your PC, quickstart is filled with application > and google credentials automatically and after that it is built > 4) APK built in 3) is then used in functional test by Arquillian Droidium > (5) which deploys that APK to physical device and in that test, we send > push notification request to UPS > 5) Once push notification comes to UPS, it sends it to GCM which in turn > sends it to physical device and Droidium test asserts that the message > really came and appeared on the mobile device. > > It takes about 10 minutes, you have to have Android device attached to > your PC since test will communicate with it. Time could be massively > decreased when you do not expect new OS UPS instance to be created every > time. > > You execute it like this in > https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests > repository > > ./gradlew test -Pprofile=helloWorldCordovaQuickstart \ > -PgoogleProjectNumber= \ > -PgoogleKey= \ > -PopenShiftUsername= > -PopenShiftPassword= \ > -PopenShiftCartridge= > https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push > \ > -PopenShiftAppDirectory=aerogear-push > > Similar process is executed with Shoot & Share demo where we send image to > Facebook. All triggered by one shell command from integration tests and > after that the above magic happens. > > I case you want to use it and you struggle with it, feel free to ask me > for guidance. > > * unified-test-extension adds custom functionality to UPS cartridge, it > adds fancy performance test endpoints where you can feed UPS instance with > custom number of generated installations / categories / variants and so on. > More to it, it can put proxy behind sender API so push notifications goes > nowhere in the end but it seems like they were indeed sent from UPS point > of view. This is particularly handy in test environment where you really do > not want to send anything to APNS or GCM. > > (1) https://github.com/jboss-mobile/unified-push-helloworld > (2) > https://github.com/aerogear/aerogear-testing-tools/tree/master/unifiedpush-test-extension > (3) > https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/build.gradle#L354-L356 > (4) > https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/build.gradle#L472-L543 > (5) > https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/quickstartTests/aerogear-push-helloworld-cordova/src/test/java/org/jboss/aerogear/push/helloworld/cordova/test/AerogearPushHelloworldCordovaTestCase.java#L65-L85 > > -- > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: smikloso at redhat.com > irc: smikloso > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150401/7090c5e9/attachment.html From bruno at abstractj.org Thu Apr 2 08:55:46 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 2 Apr 2015 09:55:46 -0300 Subject: [aerogear-dev] [UPS] issues with UPS 1.1 on OpenShift (manual deploy) In-Reply-To: References: Message-ID: Good morning guys, I'm investigating the problem since yesterday. The problem at first glance is related with the upgrade on OpenShift to Java 8. Java 8 sends TLSv1.2 ClientHello and Java 7 TLSv1 and if the server somehow does not support version 1.2, it should be able to negotiate down to 1.1 or 1.0. I'm still investigating the root cause, but the immediate fix is to run KC and UPS on JDK 1.7 only. Meanwhile I will be investigating the issue. On Tue, Mar 31, 2015 at 11:10 AM, Matthias Wessendorf wrote: > that is on a totally different KC version > > On Tue, Mar 31, 2015 at 4:03 PM, Sebastien Blanc > wrote: > >> Maybe, >> But it may also be that I'm missing something stupid :) and I have to >> configure something extra since openshift is https and I always test >> locally ... But yeah for 1.0.x I did not have to do anything. >> >> >> On Tue, Mar 31, 2015 at 3:52 PM, Matthias Wessendorf >> wrote: >> >>> anything wrong w/ the keycloak adapter, or was there a fix for a 1.1.1? >>> >>> On Tue, Mar 31, 2015 at 3:50 PM, Sebastien Blanc >>> wrote: >>> >>>> Hi ! >>>> I was trying (and so was Lukas) to deploy UPS 1.1 (master branch) to an >>>> openshift gear (Wildfly 8.2 cartridge). After tweaking a bit the >>>> datasources to get it deployed, when trying to access /ag-push , I'm get an >>>> 500 internal server error. >>>> >>>> The wildfly logs show me the following : >>>> >>>> 2015-03-31 09:40:47,240 ERROR [io.undertow.request] (default task-8) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Unable to resolve realm public key remotely >>>> at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>> at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>> at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>> at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>> at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) [keycloak-undertow-adapter-1.1.0.Final.jar:1.1.0.Final] >>>> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Final.jar:1.1.0.Final] >>>> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:247) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:166) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Final.jar:1.1.0.Final] >>>> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:759) [undertow-core-1.1.0.Final.jar:1.1.0.Final] >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] >>>> Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated >>>> at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:431) [jsse.jar:1.8.0_31] >>>> at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128) [httpclient-4.2.1.jar:4.2.1] >>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:572) [httpclient-4.2.1.jar:4.2.1] >>>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) [httpclient-4.2.1.jar:4.2.1] >>>> >>>> >>>> So "peer not authenticated" seems pretty obvious for the reason it fails. >>>> The question is what do we need to do for this ? Anyone an idea ? >>>> >>>> Thx, >>>> Sebi >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- "The measure of a man is what he does with power" - Plato - @abstractj - Volenti Nihil Difficile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150402/67357a67/attachment-0001.html From scm.blanc at gmail.com Thu Apr 2 09:06:43 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 2 Apr 2015 15:06:43 +0200 Subject: [aerogear-dev] [UPS] issues with UPS 1.1 on OpenShift (manual deploy) In-Reply-To: References: Message-ID: Thx for the headup ! When did this upgrade happened ? Shouldn't we have the problem also with UPS 1.0.x series on OpenShift ? On Thu, Apr 2, 2015 at 2:55 PM, Bruno Oliveira wrote: > Good morning guys, I'm investigating the problem since yesterday. The > problem at first glance is related with the upgrade on OpenShift to Java 8. > > Java 8 sends TLSv1.2 ClientHello and Java 7 TLSv1 and if the server > somehow does not support version 1.2, it should be able to negotiate down > to 1.1 or 1.0. > > I'm still investigating the root cause, but the immediate fix is to run KC > and UPS on JDK 1.7 only. Meanwhile I will be investigating the issue. > > On Tue, Mar 31, 2015 at 11:10 AM, Matthias Wessendorf > wrote: > >> that is on a totally different KC version >> >> On Tue, Mar 31, 2015 at 4:03 PM, Sebastien Blanc >> wrote: >> >>> Maybe, >>> But it may also be that I'm missing something stupid :) and I have to >>> configure something extra since openshift is https and I always test >>> locally ... But yeah for 1.0.x I did not have to do anything. >>> >>> >>> On Tue, Mar 31, 2015 at 3:52 PM, Matthias Wessendorf >>> wrote: >>> >>>> anything wrong w/ the keycloak adapter, or was there a fix for a 1.1.1? >>>> >>>> On Tue, Mar 31, 2015 at 3:50 PM, Sebastien Blanc >>>> wrote: >>>> >>>>> Hi ! >>>>> I was trying (and so was Lukas) to deploy UPS 1.1 (master branch) to >>>>> an openshift gear (Wildfly 8.2 cartridge). After tweaking a bit the >>>>> datasources to get it deployed, when trying to access /ag-push , I'm get an >>>>> 500 internal server error. >>>>> >>>>> The wildfly logs show me the following : >>>>> >>>>> 2015-03-31 09:40:47,240 ERROR [io.undertow.request] (default task-8) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Unable to resolve realm public key remotely >>>>> at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>>> at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>>> at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>>> at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>>> at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) [keycloak-undertow-adapter-1.1.0.Final.jar:1.1.0.Final] >>>>> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Final.jar:1.1.0.Final] >>>>> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>>> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:247) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>>> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>>> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:166) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>>> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Final.jar:1.1.0.Final] >>>>> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:759) [undertow-core-1.1.0.Final.jar:1.1.0.Final] >>>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] >>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] >>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] >>>>> Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated >>>>> at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:431) [jsse.jar:1.8.0_31] >>>>> at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128) [httpclient-4.2.1.jar:4.2.1] >>>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:572) [httpclient-4.2.1.jar:4.2.1] >>>>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) [httpclient-4.2.1.jar:4.2.1] >>>>> >>>>> >>>>> So "peer not authenticated" seems pretty obvious for the reason it fails. >>>>> The question is what do we need to do for this ? Anyone an idea ? >>>>> >>>>> Thx, >>>>> Sebi >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > > -- > "The measure of a man is what he does with power" - Plato > - > @abstractj > - > Volenti Nihil Difficile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150402/2bfb0e6c/attachment.html From bruno at abstractj.org Thu Apr 2 10:23:49 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 2 Apr 2015 11:23:49 -0300 Subject: [aerogear-dev] [UPS] issues with UPS 1.1 on OpenShift (manual deploy) In-Reply-To: References: Message-ID: I would like to do a little fix in my e-mail, to avoid any misunderstanding. WildFly cartridge targets OpenJDK 1.8, not the whole OpenShift. I realized my poor explanation, after I got some questions. Sorry about that. On Thu, Apr 2, 2015 at 10:06 AM, Sebastien Blanc wrote: > Thx for the headup ! > When did this upgrade happened ? > Shouldn't we have the problem also with UPS 1.0.x series on OpenShift ? > > On Thu, Apr 2, 2015 at 2:55 PM, Bruno Oliveira > wrote: > >> Good morning guys, I'm investigating the problem since yesterday. The >> problem at first glance is related with the upgrade on OpenShift to Java 8. >> >> Java 8 sends TLSv1.2 ClientHello and Java 7 TLSv1 and if the server >> somehow does not support version 1.2, it should be able to negotiate down >> to 1.1 or 1.0. >> >> I'm still investigating the root cause, but the immediate fix is to run >> KC and UPS on JDK 1.7 only. Meanwhile I will be investigating the issue. >> >> On Tue, Mar 31, 2015 at 11:10 AM, Matthias Wessendorf >> wrote: >> >>> that is on a totally different KC version >>> >>> On Tue, Mar 31, 2015 at 4:03 PM, Sebastien Blanc >>> wrote: >>> >>>> Maybe, >>>> But it may also be that I'm missing something stupid :) and I have to >>>> configure something extra since openshift is https and I always test >>>> locally ... But yeah for 1.0.x I did not have to do anything. >>>> >>>> >>>> On Tue, Mar 31, 2015 at 3:52 PM, Matthias Wessendorf >>> > wrote: >>>> >>>>> anything wrong w/ the keycloak adapter, or was there a fix for a >>>>> 1.1.1? >>>>> >>>>> On Tue, Mar 31, 2015 at 3:50 PM, Sebastien Blanc >>>>> wrote: >>>>> >>>>>> Hi ! >>>>>> I was trying (and so was Lukas) to deploy UPS 1.1 (master branch) to >>>>>> an openshift gear (Wildfly 8.2 cartridge). After tweaking a bit the >>>>>> datasources to get it deployed, when trying to access /ag-push , I'm get an >>>>>> 500 internal server error. >>>>>> >>>>>> The wildfly logs show me the following : >>>>>> >>>>>> 2015-03-31 09:40:47,240 ERROR [io.undertow.request] (default task-8) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Unable to resolve realm public key remotely >>>>>> at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>>>> at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>>>> at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>>>> at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] >>>>>> at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) [keycloak-undertow-adapter-1.1.0.Final.jar:1.1.0.Final] >>>>>> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Final.jar:1.1.0.Final] >>>>>> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>>>> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:247) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>>>> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>>>> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:166) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] >>>>>> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Final.jar:1.1.0.Final] >>>>>> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:759) [undertow-core-1.1.0.Final.jar:1.1.0.Final] >>>>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] >>>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] >>>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] >>>>>> Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated >>>>>> at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:431) [jsse.jar:1.8.0_31] >>>>>> at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128) [httpclient-4.2.1.jar:4.2.1] >>>>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:572) [httpclient-4.2.1.jar:4.2.1] >>>>>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) [httpclient-4.2.1.jar:4.2.1] >>>>>> >>>>>> >>>>>> So "peer not authenticated" seems pretty obvious for the reason it fails. >>>>>> The question is what do we need to do for this ? Anyone an idea ? >>>>>> >>>>>> Thx, >>>>>> Sebi >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> >> -- >> "The measure of a man is what he does with power" - Plato >> - >> @abstractj >> - >> Volenti Nihil Difficile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- "The measure of a man is what he does with power" - Plato - @abstractj - Volenti Nihil Difficile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150402/e4561a2b/attachment-0001.html From smikloso at redhat.com Fri Apr 3 03:48:13 2015 From: smikloso at redhat.com (Stefan Miklosovic) Date: Fri, 3 Apr 2015 09:48:13 +0200 Subject: [aerogear-dev] Automatic quickstart ftesting solution In-Reply-To: References: Message-ID: Hi Daniel, yes you can test it with emulator, meaning you create AVD and provide avdName to arquillian.xml, in this automatic scenario it is little bit more complicated because you need to add there avdName parameter exactly here (1). Notice that arquillian.xml file is empty regarding of property values, they are filled by test script dynamically here (2). Then you have to be sure your Android SDK is installed in a such way you have Android AVD of Google API. To not mess with bundled Android SDK in the test (3) script, you can point test to your local Android SDK installation where, I guess, everything is already downloaded. You just need to provide paths to it here (4) I abandoned emulator testing because I have some problems to automate it and I was not able to get push message on it. Maybe I just did something wrong. It seems you have to have Google API based emulator. This is not very important issue for me right now, core interest was given to physical device when it comes to push notification receiving. (1) https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/quickstartTests/aerogear-push-helloworld-cordova/src/test/resources/arquillian.xml#L4 (2) https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/build.gradle#L1004-L1008 (3) https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/build.gradle#L627-L633 (4) https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/build.gradle#L1010-L1016 On Wed, Apr 1, 2015 at 4:18 PM, Daniel Passos wrote: > That is really awesome. Is possible create and use an emulator instead of a > real device. > > -- Passos > > On Wed, Mar 25, 2015 at 12:37 PM, Stefan Miklosovic > wrote: >> >> Hi, >> >> I think few days ago there was some information from Karel Piwko that we >> developed fully automatic functional tests when it comes to Cordova >> quickstarts (1) (hello world and shoot and share) >> >> We think that it could be useful for developers as well. This tests the >> whole life cycle of the push from creation of UPS cartridge through building >> of the example to the functional test in a fully automatic manner from zero >> setup to push notification receive at mobile device you have connected to >> your notebook and it could be useful for developers in order to not execute >> it manually every time and set it up all over again. >> >> By what I mean "fully automatic" is the following scenario: >> >> 1) Automatic creation of UPS cartridge on OpenShift right from our test, >> patched with this extension * (2), (3) >> 2) Because of the deployed extension to UPS in 1), we can login via REST >> and we do not need to change passwords so we can create application with >> some variant directly from our test script (4) >> 3) After this is done, quickstart example is downloaded from GH, Android >> SDK is installed locally at your PC, quickstart is filled with application >> and google credentials automatically and after that it is built >> 4) APK built in 3) is then used in functional test by Arquillian Droidium >> (5) which deploys that APK to physical device and in that test, we send push >> notification request to UPS >> 5) Once push notification comes to UPS, it sends it to GCM which in turn >> sends it to physical device and Droidium test asserts that the message >> really came and appeared on the mobile device. >> >> It takes about 10 minutes, you have to have Android device attached to >> your PC since test will communicate with it. Time could be massively >> decreased when you do not expect new OS UPS instance to be created every >> time. >> >> You execute it like this in >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests >> repository >> >> ./gradlew test -Pprofile=helloWorldCordovaQuickstart \ >> -PgoogleProjectNumber= \ >> -PgoogleKey= \ >> -PopenShiftUsername= >> -PopenShiftPassword= \ >> >> -PopenShiftCartridge=https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >> \ >> -PopenShiftAppDirectory=aerogear-push >> >> Similar process is executed with Shoot & Share demo where we send image to >> Facebook. All triggered by one shell command from integration tests and >> after that the above magic happens. >> >> I case you want to use it and you struggle with it, feel free to ask me >> for guidance. >> >> * unified-test-extension adds custom functionality to UPS cartridge, it >> adds fancy performance test endpoints where you can feed UPS instance with >> custom number of generated installations / categories / variants and so on. >> More to it, it can put proxy behind sender API so push notifications goes >> nowhere in the end but it seems like they were indeed sent from UPS point of >> view. This is particularly handy in test environment where you really do not >> want to send anything to APNS or GCM. >> >> (1) https://github.com/jboss-mobile/unified-push-helloworld >> (2) >> https://github.com/aerogear/aerogear-testing-tools/tree/master/unifiedpush-test-extension >> (3) >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/build.gradle#L354-L356 >> (4) >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/build.gradle#L472-L543 >> (5) >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/quickstartTests/aerogear-push-helloworld-cordova/src/test/java/org/jboss/aerogear/push/helloworld/cordova/test/AerogearPushHelloworldCordovaTestCase.java#L65-L85 >> >> -- >> Stefan Miklosovic >> Red Hat Brno - JBoss Mobile Platform >> >> e-mail: smikloso at redhat.com >> irc: smikloso >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Stefan Miklosovic Red Hat Brno - JBoss Mobile Platform e-mail: smikloso at redhat.com irc: smikloso From lukas.fryc at gmail.com Fri Apr 3 04:34:34 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Fri, 3 Apr 2015 10:34:34 +0200 Subject: [aerogear-dev] UPS using JMS update Message-ID: Hi guys, so as outlined in previous thread [1], I have prototyped a JMS batching approach for push message delivery. We've discussed the approach with Matthias, Mirek Novak and Ondrej Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents describes a concept that we have came with: Diagram: https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing Text Doc: https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing Implementation-wise, I've so far prototyped the messaging part (split SenderService functionality to two subsequent queues with MDBs as shown on diagram), but that's just a start, since we must configure it appropriately for efficiency (queue configuration and batch sizes) and verify that configuration works as expected, the prototype lives on a branch (unpolished, to be squashed later): https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching Off course, you can play with it already. :-) Apart from the new requirement of using Java EE full profile (JMS), the prototype leverages implementation-specific configurations and APIs: - org.hibernate.Query for token streaming / batch fetching - HornetQ configurations of queue size, blocking behavior and message de-duplication That pretty much binds us to WildFly/EAP - we can tweak it to run on any compliant app server, but without specific configurations it won't work properly. Once configured and functionally tested (that can even wait for Beta2 I guess), we can cooperate with Mobile QE on testing (Stefan, Adam), their test suite contains mocks of APNS/GCM against which we can load test. Cheers! ~ Lukas [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/120a1db9/attachment.html From smikloso at redhat.com Fri Apr 3 05:06:58 2015 From: smikloso at redhat.com (Stefan Miklosovic) Date: Fri, 3 Apr 2015 11:06:58 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? Message-ID: Hello, Is there any interest to describe REST API for UPS in a Swagger? (1),(2) I can imagine it would be pretty handy for folks, it is just one yaml file to write really. It could be somehow linked in UPS web page, swagger is just pure html + js without any dependencies at all. (1) http://swagger.io/ (2) http://petstore.swagger.io/#!/pet/deletePet -- Stefan Miklosovic Red Hat Brno - JBoss Mobile Platform e-mail: smikloso at redhat.com irc: smikloso From tkriz at redhat.com Fri Apr 3 05:33:47 2015 From: tkriz at redhat.com (Tadeas Kriz) Date: Fri, 3 Apr 2015 11:33:47 +0200 Subject: [aerogear-dev] Automatic quickstart ftesting solution In-Reply-To: References: Message-ID: On Wed, Mar 25, 2015 at 4:53 PM, Luk?? Fry? wrote: > This sounds great, Stefan, > > questions: > 1. what about automate this as a commit-triggered CI build on AeroGear > CloudBees jenkins? > 2. are we able to automate more platforms such as iOS? > Yes but not on iOS simulator so it won't be possible to do this on remote Jenkins. iOS unfortunately supports push notifications only on real devices. > > It would be huge time-saver if this build could actually test that UPS > pushes successfully to Android (and potentially iOS) and report that as a > comment to each Pull Request. No matter how long it would take, half an > hour is my ideal here considering the use case ;-) > > ~ Lukas > > > st 25. 3. 2015 v 16:37 odes?latel Stefan Miklosovic > napsal: > >> Hi, >> >> I think few days ago there was some information from Karel Piwko that we >> developed fully automatic functional tests when it comes to Cordova >> quickstarts (1) (hello world and shoot and share) >> >> We think that it could be useful for developers as well. This tests the >> whole life cycle of the push from creation of UPS cartridge through >> building of the example to the functional test in a fully automatic manner >> from zero setup to push notification receive at mobile device you have >> connected to your notebook and it could be useful for developers in order >> to not execute it manually every time and set it up all over again. >> >> By what I mean "fully automatic" is the following scenario: >> >> 1) Automatic creation of UPS cartridge on OpenShift right from our test, >> patched with this extension * (2), (3) >> 2) Because of the deployed extension to UPS in 1), we can login via REST >> and we do not need to change passwords so we can create application with >> some variant directly from our test script (4) >> 3) After this is done, quickstart example is downloaded from GH, Android >> SDK is installed locally at your PC, quickstart is filled with application >> and google credentials automatically and after that it is built >> 4) APK built in 3) is then used in functional test by Arquillian Droidium >> (5) which deploys that APK to physical device and in that test, we send >> push notification request to UPS >> 5) Once push notification comes to UPS, it sends it to GCM which in turn >> sends it to physical device and Droidium test asserts that the message >> really came and appeared on the mobile device. >> >> It takes about 10 minutes, you have to have Android device attached to >> your PC since test will communicate with it. Time could be massively >> decreased when you do not expect new OS UPS instance to be created every >> time. >> >> You execute it like this in >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests >> repository >> >> ./gradlew test -Pprofile=helloWorldCordovaQuickstart \ >> -PgoogleProjectNumber= \ >> -PgoogleKey= \ >> -PopenShiftUsername= >> -PopenShiftPassword= \ >> -PopenShiftCartridge= >> https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push >> \ >> -PopenShiftAppDirectory=aerogear-push >> >> Similar process is executed with Shoot & Share demo where we send image >> to Facebook. All triggered by one shell command from integration tests and >> after that the above magic happens. >> >> I case you want to use it and you struggle with it, feel free to ask me >> for guidance. >> >> * unified-test-extension adds custom functionality to UPS cartridge, it >> adds fancy performance test endpoints where you can feed UPS instance with >> custom number of generated installations / categories / variants and so on. >> More to it, it can put proxy behind sender API so push notifications goes >> nowhere in the end but it seems like they were indeed sent from UPS point >> of view. This is particularly handy in test environment where you really do >> not want to send anything to APNS or GCM. >> >> (1) https://github.com/jboss-mobile/unified-push-helloworld >> (2) >> https://github.com/aerogear/aerogear-testing-tools/tree/master/unifiedpush-test-extension >> (3) >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/build.gradle#L354-L356 >> (4) >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/build.gradle#L472-L543 >> (5) >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/quickstartTests/aerogear-push-helloworld-cordova/src/test/java/org/jboss/aerogear/push/helloworld/cordova/test/AerogearPushHelloworldCordovaTestCase.java#L65-L85 >> >> -- >> Stefan Miklosovic >> Red Hat Brno - JBoss Mobile Platform >> >> e-mail: smikloso at redhat.com >> irc: smikloso >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Tadeas Kriz -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/6a29875d/attachment-0001.html From kpiwko at redhat.com Fri Apr 3 07:04:09 2015 From: kpiwko at redhat.com (Karel Piwko) Date: Fri, 3 Apr 2015 13:04:09 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: Message-ID: I really like the idea! On Fri, Apr 3, 2015 at 11:06 AM, Stefan Miklosovic wrote: > Hello, > > Is there any interest to describe REST API for UPS in a Swagger? (1),(2) > > I can imagine it would be pretty handy for folks, it is just one yaml > file to write really. > > It could be somehow linked in UPS web page, swagger is just pure html > + js without any dependencies at all. > > (1) http://swagger.io/ > (2) http://petstore.swagger.io/#!/pet/deletePet > > -- > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: smikloso at redhat.com > irc: smikloso > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/bd1fb3f2/attachment.html From matzew at apache.org Fri Apr 3 07:10:15 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 3 Apr 2015 13:10:15 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: Message-ID: that is very cool! Also this helps to retire the jaxrs doclet, that is not working w/ jdk8 On Friday, April 3, 2015, Karel Piwko wrote: > I really like the idea! > > On Fri, Apr 3, 2015 at 11:06 AM, Stefan Miklosovic > wrote: > >> Hello, >> >> Is there any interest to describe REST API for UPS in a Swagger? (1),(2) >> >> I can imagine it would be pretty handy for folks, it is just one yaml >> file to write really. >> >> It could be somehow linked in UPS web page, swagger is just pure html >> + js without any dependencies at all. >> >> (1) http://swagger.io/ >> (2) http://petstore.swagger.io/#!/pet/deletePet >> >> -- >> Stefan Miklosovic >> Red Hat Brno - JBoss Mobile Platform >> >> e-mail: smikloso at redhat.com >> >> irc: smikloso >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/b1b3919c/attachment.html From scm.blanc at gmail.com Fri Apr 3 07:12:13 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 3 Apr 2015 13:12:13 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: Message-ID: +1 feels free to PR this On Fri, Apr 3, 2015 at 1:10 PM, Matthias Wessendorf wrote: > that is very cool! > > Also this helps to retire the jaxrs doclet, that is not working w/ jdk8 > > > On Friday, April 3, 2015, Karel Piwko wrote: > >> I really like the idea! >> >> On Fri, Apr 3, 2015 at 11:06 AM, Stefan Miklosovic >> wrote: >> >>> Hello, >>> >>> Is there any interest to describe REST API for UPS in a Swagger? (1),(2) >>> >>> I can imagine it would be pretty handy for folks, it is just one yaml >>> file to write really. >>> >>> It could be somehow linked in UPS web page, swagger is just pure html >>> + js without any dependencies at all. >>> >>> (1) http://swagger.io/ >>> (2) http://petstore.swagger.io/#!/pet/deletePet >>> >>> -- >>> Stefan Miklosovic >>> Red Hat Brno - JBoss Mobile Platform >>> >>> e-mail: smikloso at redhat.com >>> irc: smikloso >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/695b276f/attachment.html From scm.blanc at gmail.com Fri Apr 3 07:25:11 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 3 Apr 2015 13:25:11 +0200 Subject: [aerogear-dev] UPS using JMS update In-Reply-To: References: Message-ID: That all sounds very good :) Thanks for the headupate, I will soon give it a try. On Fri, Apr 3, 2015 at 10:34 AM, Luk?? Fry? wrote: > Hi guys, > > so as outlined in previous thread [1], I have prototyped a JMS batching > approach for push message delivery. > > > > > We've discussed the approach with Matthias, Mirek Novak and Ondrej > Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents > describes a concept that we have came with: > > Diagram: > https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing > > Text Doc: > https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing > > > > > > > Implementation-wise, I've so far prototyped the messaging part (split > SenderService functionality to two subsequent queues with MDBs as shown on > diagram), > > but that's just a start, since we must configure it appropriately for > efficiency (queue configuration and batch sizes) and verify that > configuration works as expected, > > the prototype lives on a branch (unpolished, to be squashed later): > https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching > > Off course, you can play with it already. :-) > > > > > > Apart from the new requirement of using Java EE full profile (JMS), the > prototype leverages implementation-specific configurations and APIs: > > - org.hibernate.Query for token streaming / batch fetching > - HornetQ configurations of queue size, blocking behavior and message > de-duplication > > That pretty much binds us to WildFly/EAP - we can tweak it to run on any > compliant app server, but without specific configurations it won't work > properly. > > > > Once configured and functionally tested (that can even wait for Beta2 I > guess), > > we can cooperate with Mobile QE on testing (Stefan, Adam), their test > suite contains mocks of APNS/GCM against which we can load test. > > > > Cheers! > > ~ Lukas > > > [1] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/652d572d/attachment.html From matzew at apache.org Fri Apr 3 07:50:39 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 3 Apr 2015 13:50:39 +0200 Subject: [aerogear-dev] UPS using JMS update In-Reply-To: References: Message-ID: Cool stuff I am totally fine having this tied ti wf/eap wondering: at some point, should we offer a dist as (only) subststem for wf/eap? On Friday, April 3, 2015, Sebastien Blanc wrote: > That all sounds very good :) > Thanks for the headupate, I will soon give it a try. > > On Fri, Apr 3, 2015 at 10:34 AM, Luk?? Fry? > wrote: > >> Hi guys, >> >> so as outlined in previous thread [1], I have prototyped a JMS batching >> approach for push message delivery. >> >> >> >> >> We've discussed the approach with Matthias, Mirek Novak and Ondrej >> Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents >> describes a concept that we have came with: >> >> Diagram: >> https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing >> >> Text Doc: >> https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing >> >> >> >> >> >> >> Implementation-wise, I've so far prototyped the messaging part (split >> SenderService functionality to two subsequent queues with MDBs as shown on >> diagram), >> >> but that's just a start, since we must configure it appropriately for >> efficiency (queue configuration and batch sizes) and verify that >> configuration works as expected, >> >> the prototype lives on a branch (unpolished, to be squashed later): >> https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching >> >> Off course, you can play with it already. :-) >> >> >> >> >> >> Apart from the new requirement of using Java EE full profile (JMS), the >> prototype leverages implementation-specific configurations and APIs: >> >> - org.hibernate.Query for token streaming / batch fetching >> - HornetQ configurations of queue size, blocking behavior and message >> de-duplication >> >> That pretty much binds us to WildFly/EAP - we can tweak it to run on any >> compliant app server, but without specific configurations it won't work >> properly. >> >> >> >> Once configured and functionally tested (that can even wait for Beta2 I >> guess), >> >> we can cooperate with Mobile QE on testing (Stefan, Adam), their test >> suite contains mocks of APNS/GCM against which we can load test. >> >> >> >> Cheers! >> >> ~ Lukas >> >> >> [1] >> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/0e5292f9/attachment-0001.html From scm.blanc at gmail.com Fri Apr 3 07:54:09 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 3 Apr 2015 13:54:09 +0200 Subject: [aerogear-dev] UPS using JMS update In-Reply-To: References: Message-ID: On Fri, Apr 3, 2015 at 1:50 PM, Matthias Wessendorf wrote: > Cool stuff > > I am totally fine having this tied ti wf/eap > > wondering: at some point, should we offer a dist as (only) subststem for > wf/eap? > +1, I was exactly thinking the same, since we are tied to wf/eap, subsystem makes a lot of sense IMO > > > On Friday, April 3, 2015, Sebastien Blanc wrote: > >> That all sounds very good :) >> Thanks for the headupate, I will soon give it a try. >> >> On Fri, Apr 3, 2015 at 10:34 AM, Luk?? Fry? wrote: >> >>> Hi guys, >>> >>> so as outlined in previous thread [1], I have prototyped a JMS batching >>> approach for push message delivery. >>> >>> >>> >>> >>> We've discussed the approach with Matthias, Mirek Novak and Ondrej >>> Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents >>> describes a concept that we have came with: >>> >>> Diagram: >>> https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing >>> >>> Text Doc: >>> https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing >>> >>> >>> >>> >>> >>> >>> Implementation-wise, I've so far prototyped the messaging part (split >>> SenderService functionality to two subsequent queues with MDBs as shown on >>> diagram), >>> >>> but that's just a start, since we must configure it appropriately for >>> efficiency (queue configuration and batch sizes) and verify that >>> configuration works as expected, >>> >>> the prototype lives on a branch (unpolished, to be squashed later): >>> https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching >>> >>> Off course, you can play with it already. :-) >>> >>> >>> >>> >>> >>> Apart from the new requirement of using Java EE full profile (JMS), the >>> prototype leverages implementation-specific configurations and APIs: >>> >>> - org.hibernate.Query for token streaming / batch fetching >>> - HornetQ configurations of queue size, blocking behavior and >>> message de-duplication >>> >>> That pretty much binds us to WildFly/EAP - we can tweak it to run on any >>> compliant app server, but without specific configurations it won't work >>> properly. >>> >>> >>> >>> Once configured and functionally tested (that can even wait for Beta2 I >>> guess), >>> >>> we can cooperate with Mobile QE on testing (Stefan, Adam), their test >>> suite contains mocks of APNS/GCM against which we can load test. >>> >>> >>> >>> Cheers! >>> >>> ~ Lukas >>> >>> >>> [1] >>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/ce2758c7/attachment.html From dpassos at redhat.com Fri Apr 3 08:18:42 2015 From: dpassos at redhat.com (Daniel Passos) Date: Fri, 3 Apr 2015 09:18:42 -0300 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: Message-ID: +9001 On Fri, Apr 3, 2015 at 8:12 AM, Sebastien Blanc wrote: > +1 > feels free to PR this > > On Fri, Apr 3, 2015 at 1:10 PM, Matthias Wessendorf > wrote: > >> that is very cool! >> >> Also this helps to retire the jaxrs doclet, that is not working w/ jdk8 >> >> >> On Friday, April 3, 2015, Karel Piwko wrote: >> >>> I really like the idea! >>> >>> On Fri, Apr 3, 2015 at 11:06 AM, Stefan Miklosovic >>> wrote: >>> >>>> Hello, >>>> >>>> Is there any interest to describe REST API for UPS in a Swagger? (1),(2) >>>> >>>> I can imagine it would be pretty handy for folks, it is just one yaml >>>> file to write really. >>>> >>>> It could be somehow linked in UPS web page, swagger is just pure html >>>> + js without any dependencies at all. >>>> >>>> (1) http://swagger.io/ >>>> (2) http://petstore.swagger.io/#!/pet/deletePet >>>> >>>> -- >>>> Stefan Miklosovic >>>> Red Hat Brno - JBoss Mobile Platform >>>> >>>> e-mail: smikloso at redhat.com >>>> irc: smikloso >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/89607206/attachment.html From banddk1 at gmail.com Fri Apr 3 09:16:31 2015 From: banddk1 at gmail.com (=?UTF-8?B?0JTQtdC90LjRgSDQmtCw0YDQv9C10L3QutC+?=) Date: Fri, 3 Apr 2015 16:16:31 +0300 Subject: [aerogear-dev] GSoC - AeroDoc overhaul? In-Reply-To: References: Message-ID: Hi everyone, I am a GSoC applicant and I am interested in development of "AeroDoc 2.0". It seems to me that this project fits my skills and interests. Denis. 2015-03-26 10:53 GMT+03:00 Matthias Wessendorf : > Hi, > > for GSoC, I thought about a possible "AeroDoc 2.0" > > * remove picket link based auth with keycloak > * usage of OAuth2 auth for the iOS and Android version > * port iOS app to Swift > * Windows support > > One related tought: perhaps we change the name, and modify the use-case - > to not be "doctor" specific? > > -Matthias > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/5bae0fec/attachment.html From smikloso at redhat.com Fri Apr 3 10:07:45 2015 From: smikloso at redhat.com (Stefan Miklosovic) Date: Fri, 3 Apr 2015 16:07:45 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: Message-ID: Do we need just that yaml or we want to integrate it directly into the source code with this? (1) By doing this you can just point your browser to some url and it is generated dynamically. Or I just write that yaml, the disadvantage is that you have to update it every time some REST API changes to reflect it however I hesitate to touch sources, they should not know about this. (1) https://github.com/swagger-api/swagger-core/wiki/Java-JAXRS-Quickstart On Fri, Apr 3, 2015 at 2:18 PM, Daniel Passos wrote: > +9001 > > On Fri, Apr 3, 2015 at 8:12 AM, Sebastien Blanc wrote: >> >> +1 >> feels free to PR this >> >> On Fri, Apr 3, 2015 at 1:10 PM, Matthias Wessendorf >> wrote: >>> >>> that is very cool! >>> >>> Also this helps to retire the jaxrs doclet, that is not working w/ jdk8 >>> >>> >>> On Friday, April 3, 2015, Karel Piwko wrote: >>>> >>>> I really like the idea! >>>> >>>> On Fri, Apr 3, 2015 at 11:06 AM, Stefan Miklosovic >>>> wrote: >>>>> >>>>> Hello, >>>>> >>>>> Is there any interest to describe REST API for UPS in a Swagger? >>>>> (1),(2) >>>>> >>>>> I can imagine it would be pretty handy for folks, it is just one yaml >>>>> file to write really. >>>>> >>>>> It could be somehow linked in UPS web page, swagger is just pure html >>>>> + js without any dependencies at all. >>>>> >>>>> (1) http://swagger.io/ >>>>> (2) http://petstore.swagger.io/#!/pet/deletePet >>>>> >>>>> -- >>>>> Stefan Miklosovic >>>>> Red Hat Brno - JBoss Mobile Platform >>>>> >>>>> e-mail: smikloso at redhat.com >>>>> irc: smikloso >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > -- Passos > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Stefan Miklosovic Red Hat Brno - JBoss Mobile Platform e-mail: smikloso at redhat.com irc: smikloso From bsutter at redhat.com Fri Apr 3 10:25:13 2015 From: bsutter at redhat.com (Burr Sutter) Date: Fri, 3 Apr 2015 10:25:13 -0400 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: Message-ID: <128869AC-455E-4DB7-95F5-A015F3617B3C@redhat.com> > On Apr 3, 2015, at 5:06 AM, Stefan Miklosovic wrote: > > Hello, > > Is there any interest to describe REST API for UPS in a Swagger? (1),(2) I love the idea :-) > > I can imagine it would be pretty handy for folks, it is just one yaml > file to write really. > > It could be somehow linked in UPS web page, swagger is just pure html > + js without any dependencies at all. > > (1) http://swagger.io/ > (2) http://petstore.swagger.io/#!/pet/deletePet > > -- > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: smikloso at redhat.com > irc: smikloso > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From corinnekrych at gmail.com Fri Apr 3 11:30:21 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 3 Apr 2015 17:30:21 +0200 Subject: [aerogear-dev] GSoC - AeroDoc overhaul? In-Reply-To: References: Message-ID: Very nice Denis! With this subject you will have the opportunity to leverage your OAuth2 learning on iOS but also Android and Windows. You will also work with UnifiedPush server and Keycloak on server side. I have several blog post for you: http://corinnekrych.blogspot.fr/2014/07/ios8-interactive-notification-available.html http://corinnekrych.blogspot.fr/2014/11/oauth2-for-android-and-ios-with-keycloak.html ++ Corinne On 3 April 2015 at 15:16, ????? ???????? wrote: > Hi everyone, > I am a GSoC applicant and I am interested in development of "AeroDoc 2.0". > It seems to me that this project fits my skills and interests. > > > Denis. > > 2015-03-26 10:53 GMT+03:00 Matthias Wessendorf : > >> Hi, >> >> for GSoC, I thought about a possible "AeroDoc 2.0" >> >> * remove picket link based auth with keycloak >> * usage of OAuth2 auth for the iOS and Android version >> * port iOS app to Swift >> * Windows support >> >> One related tought: perhaps we change the name, and modify the use-case - >> to not be "doctor" specific? >> >> -Matthias >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/a02919ba/attachment.html From scm.blanc at gmail.com Fri Apr 3 11:37:26 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 3 Apr 2015 17:37:26 +0200 Subject: [aerogear-dev] GSoC - AeroDoc overhaul? In-Reply-To: References: Message-ID: Sounds good ! As Corinne said, it touches many parts of the AeroGear project. Sebi On Fri, Apr 3, 2015 at 3:16 PM, ????? ???????? wrote: > Hi everyone, > I am a GSoC applicant and I am interested in development of "AeroDoc 2.0". > It seems to me that this project fits my skills and interests. > > > Denis. > > 2015-03-26 10:53 GMT+03:00 Matthias Wessendorf : > >> Hi, >> >> for GSoC, I thought about a possible "AeroDoc 2.0" >> >> * remove picket link based auth with keycloak >> * usage of OAuth2 auth for the iOS and Android version >> * port iOS app to Swift >> * Windows support >> >> One related tought: perhaps we change the name, and modify the use-case - >> to not be "doctor" specific? >> >> -Matthias >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/a33dd670/attachment.html From avibelli at redhat.com Fri Apr 3 12:53:12 2015 From: avibelli at redhat.com (Andrea Vibelli) Date: Fri, 3 Apr 2015 09:53:12 -0700 (MST) Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: Message-ID: <1428079992224-11356.post@n5.nabble.com> Hi Stefan, we are using it in Project Newcastle with annotations on the endpoints, and it's really handy. So +1 for integration on the source code :) Andrea Stefan Miklosovic wrote > Do we need just that yaml or we want to integrate it directly into the > source code with this? (1) By doing this you can just point your > browser to some url and it is generated dynamically. > > Or I just write that yaml, the disadvantage is that you have to update > it every time some REST API changes to reflect it however I hesitate > to touch sources, they should not know about this. > > (1) https://github.com/swagger-api/swagger-core/wiki/Java-JAXRS-Quickstart > > On Fri, Apr 3, 2015 at 2:18 PM, Daniel Passos < > dpassos@ > > wrote: >> +9001 >> >> On Fri, Apr 3, 2015 at 8:12 AM, Sebastien Blanc < > scm.blanc@ > > wrote: >>> >>> +1 >>> feels free to PR this >>> >>> On Fri, Apr 3, 2015 at 1:10 PM, Matthias Wessendorf < > matzew@ > > >>> wrote: >>>> >>>> that is very cool! >>>> >>>> Also this helps to retire the jaxrs doclet, that is not working w/ jdk8 >>>> >>>> >>>> On Friday, April 3, 2015, Karel Piwko < > kpiwko@ > > wrote: >>>>> >>>>> I really like the idea! >>>>> >>>>> On Fri, Apr 3, 2015 at 11:06 AM, Stefan Miklosovic < > smikloso@ > > >>>>> wrote: >>>>>> >>>>>> Hello, >>>>>> >>>>>> Is there any interest to describe REST API for UPS in a Swagger? >>>>>> (1),(2) >>>>>> >>>>>> I can imagine it would be pretty handy for folks, it is just one yaml >>>>>> file to write really. >>>>>> >>>>>> It could be somehow linked in UPS web page, swagger is just pure html >>>>>> + js without any dependencies at all. >>>>>> >>>>>> (1) http://swagger.io/ >>>>>> (2) http://petstore.swagger.io/#!/pet/deletePet >>>>>> >>>>>> -- >>>>>> Stefan Miklosovic >>>>>> Red Hat Brno - JBoss Mobile Platform >>>>>> >>>>>> e-mail: > smikloso@ >>>>>> irc: smikloso >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> > aerogear-dev at .jboss >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> > aerogear-dev at .jboss >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> > aerogear-dev at .jboss >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> aerogear-dev mailing list >> > aerogear-dev at .jboss >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: > smikloso@ > irc: smikloso > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at .jboss > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-do-we-want-swagger-for-REST-endpoint-documentation-tp11342p11356.html Sent from the aerogear-dev mailing list archive at Nabble.com. From hrupp at redhat.com Fri Apr 3 16:27:34 2015 From: hrupp at redhat.com (Heiko W.Rupp) Date: Fri, 03 Apr 2015 22:27:34 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: <1428079992224-11356.post@n5.nabble.com> References: <1428079992224-11356.post@n5.nabble.com> Message-ID: <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: > we are using it in Project Newcastle with annotations on the > endpoints, and > it's really handy. All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + Swagger annotations. In Hawkular we are basically doing the same, but with a different annotation processor. I personally think the best is really to have the annotations in the source and not trying to update a separate .yml file, as the latter usually is much easier forgotten. From dpassos at redhat.com Fri Apr 3 17:41:28 2015 From: dpassos at redhat.com (Daniel Passos) Date: Fri, 3 Apr 2015 18:41:28 -0300 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: <1428079992224-11356.post@n5.nabble.com> References: <1428079992224-11356.post@n5.nabble.com> Message-ID: +1 for integration on the source code On Fri, Apr 3, 2015 at 1:53 PM, Andrea Vibelli wrote: > Hi Stefan, > we are using it in Project Newcastle with annotations on the endpoints, and > it's really handy. > So +1 for integration on the source code :) > > Andrea > > > > > Stefan Miklosovic wrote > > Do we need just that yaml or we want to integrate it directly into the > > source code with this? (1) By doing this you can just point your > > browser to some url and it is generated dynamically. > > > > Or I just write that yaml, the disadvantage is that you have to update > > it every time some REST API changes to reflect it however I hesitate > > to touch sources, they should not know about this. > > > > (1) > https://github.com/swagger-api/swagger-core/wiki/Java-JAXRS-Quickstart > > > > On Fri, Apr 3, 2015 at 2:18 PM, Daniel Passos < > > > dpassos@ > > > > wrote: > >> +9001 > >> > >> On Fri, Apr 3, 2015 at 8:12 AM, Sebastien Blanc < > > > scm.blanc@ > > > > wrote: > >>> > >>> +1 > >>> feels free to PR this > >>> > >>> On Fri, Apr 3, 2015 at 1:10 PM, Matthias Wessendorf < > > > matzew@ > > > > > >>> wrote: > >>>> > >>>> that is very cool! > >>>> > >>>> Also this helps to retire the jaxrs doclet, that is not working w/ > jdk8 > >>>> > >>>> > >>>> On Friday, April 3, 2015, Karel Piwko < > > > kpiwko@ > > > > wrote: > >>>>> > >>>>> I really like the idea! > >>>>> > >>>>> On Fri, Apr 3, 2015 at 11:06 AM, Stefan Miklosovic < > > > smikloso@ > > > > > >>>>> wrote: > >>>>>> > >>>>>> Hello, > >>>>>> > >>>>>> Is there any interest to describe REST API for UPS in a Swagger? > >>>>>> (1),(2) > >>>>>> > >>>>>> I can imagine it would be pretty handy for folks, it is just one > yaml > >>>>>> file to write really. > >>>>>> > >>>>>> It could be somehow linked in UPS web page, swagger is just pure > html > >>>>>> + js without any dependencies at all. > >>>>>> > >>>>>> (1) http://swagger.io/ > >>>>>> (2) http://petstore.swagger.io/#!/pet/deletePet > >>>>>> > >>>>>> -- > >>>>>> Stefan Miklosovic > >>>>>> Red Hat Brno - JBoss Mobile Platform > >>>>>> > >>>>>> e-mail: > > > smikloso@ > > >>>>>> irc: smikloso > >>>>>> _______________________________________________ > >>>>>> aerogear-dev mailing list > >>>>>> > > > aerogear-dev at .jboss > > >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> Sent from Gmail Mobile > >>>> > >>>> _______________________________________________ > >>>> aerogear-dev mailing list > >>>> > > > aerogear-dev at .jboss > > >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>> > >>> > >>> > >>> _______________________________________________ > >>> aerogear-dev mailing list > >>> > > > aerogear-dev at .jboss > > >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > >> > >> > >> > >> -- > >> -- Passos > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> > > > aerogear-dev at .jboss > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > -- > > Stefan Miklosovic > > Red Hat Brno - JBoss Mobile Platform > > > > e-mail: > > > smikloso@ > > > irc: smikloso > > _______________________________________________ > > aerogear-dev mailing list > > > aerogear-dev at .jboss > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-do-we-want-swagger-for-REST-endpoint-documentation-tp11342p11356.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150403/309ae928/attachment-0001.html From matzew at apache.org Sat Apr 4 02:43:19 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Sat, 4 Apr 2015 08:43:19 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp wrote: > On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: > > > we are using it in Project Newcastle with annotations on the > > endpoints, and > > it's really handy. > > All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + > Swagger annotations. > In Hawkular we are basically doing the same, but with a different > annotation processor. > +1000 we are, atm, doing similar: source https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 result: https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST but the jaxrs doclet does not work w/ JDK8 - something has to change here ;-) So, I am all for using Swagger annotations on the code to generate the HTML docs :-) Greetings, Matthias > > I personally think the best is really to have the annotations in the > source and not trying > to update a separate .yml file, as the latter usually is much easier > forgotten. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150404/e65b9c33/attachment.html From matzew at apache.org Sat Apr 4 02:43:59 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Sat, 4 Apr 2015 08:43:59 +0200 Subject: [aerogear-dev] GSoC - AeroDoc overhaul? In-Reply-To: References: Message-ID: +1 I think it's a cool GSoC project as well :-) On Fri, Apr 3, 2015 at 5:37 PM, Sebastien Blanc wrote: > Sounds good ! > As Corinne said, it touches many parts of the AeroGear project. > Sebi > > On Fri, Apr 3, 2015 at 3:16 PM, ????? ???????? wrote: > >> Hi everyone, >> I am a GSoC applicant and I am interested in development of "AeroDoc 2.0". >> It seems to me that this project fits my skills and interests. >> >> >> Denis. >> >> 2015-03-26 10:53 GMT+03:00 Matthias Wessendorf : >> >>> Hi, >>> >>> for GSoC, I thought about a possible "AeroDoc 2.0" >>> >>> * remove picket link based auth with keycloak >>> * usage of OAuth2 auth for the iOS and Android version >>> * port iOS app to Swift >>> * Windows support >>> >>> One related tought: perhaps we change the name, and modify the use-case >>> - to not be "doctor" specific? >>> >>> -Matthias >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150404/0847e62b/attachment.html From idel.pivnitskiy at gmail.com Sun Apr 5 13:59:59 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Sun, 5 Apr 2015 20:59:59 +0300 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: For JAX-RS I prefer use MireDot as a REST API doc generator http://www.miredot.com/ With MireDot you do not need to use additional annotations, like @Api: @Path("/pet") @Api(value = "/pet", description = "Operations about pets") It will parse your JAX-RS annotation and pure javadoc: /** * Operations about pets */ @Path("/pet") and generate beautiful and user friendly documentation, like this: http://www.miredot.com/exampledocs/ Swagger example: http://petstore.swagger.io/ And MireDot is free for open source projects! Think about this alternative for Swagger. I'm able to prepare Pull Request for UPS next week. 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : > > > On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp wrote: > >> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >> >> > we are using it in Project Newcastle with annotations on the >> > endpoints, and >> > it's really handy. >> >> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + >> Swagger annotations. >> In Hawkular we are basically doing the same, but with a different >> annotation processor. >> > > +1000 > > we are, atm, doing similar: > source > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 > result: > > https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST > > but the jaxrs doclet does not work w/ JDK8 - something has to change here > ;-) > So, I am all for using Swagger annotations on the code to generate the > HTML docs :-) > > Greetings, > Matthias > > >> >> I personally think the best is really to have the annotations in the >> source and not trying >> to update a separate .yml file, as the latter usually is much easier >> forgotten. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Best regards, Idel Pivnitskiy E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150405/353f4165/attachment.html From cvasilak at gmail.com Mon Apr 6 08:42:00 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 6 Apr 2015 15:42:00 +0300 Subject: [aerogear-dev] Team Meeting Message-ID: Hi all, since some of our member's are currently on Easter holiday, we decided to pause our regular meeting for today until tomorrow same time. Agenda is here: http://oksoclap.com/p/aerogear-team-mgt-04.07.2015 Thanks, Christos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150406/659f129c/attachment.html From bruno at abstractj.org Mon Apr 6 13:13:49 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 6 Apr 2015 14:13:49 -0300 Subject: [aerogear-dev] [UPS] issues with UPS 1.1 on OpenShift (manual deploy) In-Reply-To: References: Message-ID: <20150406171349.GA4956@abstractj.org> A little update, if you're willing to deploy UPS on Openshift: https://issues.jboss.org/browse/AGPUSH-1352 On 2015-04-02, Sebastien Blanc wrote: > Thx for the headup ! > When did this upgrade happened ? > Shouldn't we have the problem also with UPS 1.0.x series on OpenShift ? > > On Thu, Apr 2, 2015 at 2:55 PM, Bruno Oliveira wrote: > > > Good morning guys, I'm investigating the problem since yesterday. The > > problem at first glance is related with the upgrade on OpenShift to Java 8. > > > > Java 8 sends TLSv1.2 ClientHello and Java 7 TLSv1 and if the server > > somehow does not support version 1.2, it should be able to negotiate down > > to 1.1 or 1.0. > > > > I'm still investigating the root cause, but the immediate fix is to run KC > > and UPS on JDK 1.7 only. Meanwhile I will be investigating the issue. > > > > On Tue, Mar 31, 2015 at 11:10 AM, Matthias Wessendorf > > wrote: > > > >> that is on a totally different KC version > >> > >> On Tue, Mar 31, 2015 at 4:03 PM, Sebastien Blanc > >> wrote: > >> > >>> Maybe, > >>> But it may also be that I'm missing something stupid :) and I have to > >>> configure something extra since openshift is https and I always test > >>> locally ... But yeah for 1.0.x I did not have to do anything. > >>> > >>> > >>> On Tue, Mar 31, 2015 at 3:52 PM, Matthias Wessendorf > >>> wrote: > >>> > >>>> anything wrong w/ the keycloak adapter, or was there a fix for a 1.1.1? > >>>> > >>>> On Tue, Mar 31, 2015 at 3:50 PM, Sebastien Blanc > >>>> wrote: > >>>> > >>>>> Hi ! > >>>>> I was trying (and so was Lukas) to deploy UPS 1.1 (master branch) to > >>>>> an openshift gear (Wildfly 8.2 cartridge). After tweaking a bit the > >>>>> datasources to get it deployed, when trying to access /ag-push , I'm get an > >>>>> 500 internal server error. > >>>>> > >>>>> The wildfly logs show me the following : > >>>>> > >>>>> 2015-03-31 09:40:47,240 ERROR [io.undertow.request] (default task-8) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Unable to resolve realm public key remotely > >>>>> at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] > >>>>> at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] > >>>>> at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] > >>>>> at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47) [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] > >>>>> at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) [keycloak-undertow-adapter-1.1.0.Final.jar:1.1.0.Final] > >>>>> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Final.jar:1.1.0.Final] > >>>>> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] > >>>>> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:247) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] > >>>>> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] > >>>>> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:166) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] > >>>>> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Final.jar:1.1.0.Final] > >>>>> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:759) [undertow-core-1.1.0.Final.jar:1.1.0.Final] > >>>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] > >>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] > >>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] > >>>>> Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated > >>>>> at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:431) [jsse.jar:1.8.0_31] > >>>>> at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128) [httpclient-4.2.1.jar:4.2.1] > >>>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:572) [httpclient-4.2.1.jar:4.2.1] > >>>>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) [httpclient-4.2.1.jar:4.2.1] > >>>>> > >>>>> > >>>>> So "peer not authenticated" seems pretty obvious for the reason it fails. > >>>>> The question is what do we need to do for this ? Anyone an idea ? > >>>>> > >>>>> Thx, > >>>>> Sebi > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> aerogear-dev mailing list > >>>>> aerogear-dev at 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 > >>>> > >>>> _______________________________________________ > >>>> aerogear-dev mailing list > >>>> aerogear-dev at lists.jboss.org > >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>> > >>> > >>> > >>> _______________________________________________ > >>> aerogear-dev mailing list > >>> aerogear-dev at 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 > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > > > > > > > > -- > > > > -- > > "The measure of a man is what he does with power" - Plato > > - > > @abstractj > > - > > Volenti Nihil Difficile > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj PGP: 0x84DC9914 From jbalunas at redhat.com Mon Apr 6 14:17:44 2015 From: jbalunas at redhat.com (Jay Balunas) Date: Mon, 6 Apr 2015 14:17:44 -0400 Subject: [aerogear-dev] UPS using JMS update In-Reply-To: References: Message-ID: This all sounds really good to me! The priority would be wf/eap imo, with others if very easy, or if community members want to jump in and add their favorite. On Fri, Apr 3, 2015 at 7:54 AM, Sebastien Blanc wrote: > > > On Fri, Apr 3, 2015 at 1:50 PM, Matthias Wessendorf > wrote: > >> Cool stuff >> >> I am totally fine having this tied ti wf/eap >> >> wondering: at some point, should we offer a dist as (only) subststem for >> wf/eap? >> > +1, I was exactly thinking the same, since we are tied to wf/eap, > subsystem makes a lot of sense IMO > > >> >> >> On Friday, April 3, 2015, Sebastien Blanc wrote: >> >>> That all sounds very good :) >>> Thanks for the headupate, I will soon give it a try. >>> >>> On Fri, Apr 3, 2015 at 10:34 AM, Luk?? Fry? >>> wrote: >>> >>>> Hi guys, >>>> >>>> so as outlined in previous thread [1], I have prototyped a JMS batching >>>> approach for push message delivery. >>>> >>>> >>>> >>>> >>>> We've discussed the approach with Matthias, Mirek Novak and Ondrej >>>> Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents >>>> describes a concept that we have came with: >>>> >>>> Diagram: >>>> https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing >>>> >>>> Text Doc: >>>> https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing >>>> >>>> >>>> >>>> >>>> >>>> >>>> Implementation-wise, I've so far prototyped the messaging part (split >>>> SenderService functionality to two subsequent queues with MDBs as shown on >>>> diagram), >>>> >>>> but that's just a start, since we must configure it appropriately for >>>> efficiency (queue configuration and batch sizes) and verify that >>>> configuration works as expected, >>>> >>>> the prototype lives on a branch (unpolished, to be squashed later): >>>> https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching >>>> >>>> Off course, you can play with it already. :-) >>>> >>>> >>>> >>>> >>>> >>>> Apart from the new requirement of using Java EE full profile (JMS), the >>>> prototype leverages implementation-specific configurations and APIs: >>>> >>>> - org.hibernate.Query for token streaming / batch fetching >>>> - HornetQ configurations of queue size, blocking behavior and >>>> message de-duplication >>>> >>>> That pretty much binds us to WildFly/EAP - we can tweak it to run on >>>> any compliant app server, but without specific configurations it won't work >>>> properly. >>>> >>>> >>>> >>>> Once configured and functionally tested (that can even wait for Beta2 I >>>> guess), >>>> >>>> we can cooperate with Mobile QE on testing (Stefan, Adam), their test >>>> suite contains mocks of APNS/GCM against which we can load test. >>>> >>>> >>>> >>>> Cheers! >>>> >>>> ~ Lukas >>>> >>>> >>>> [1] >>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150406/9cdbf832/attachment.html From banddk1 at gmail.com Mon Apr 6 14:42:00 2015 From: banddk1 at gmail.com (=?UTF-8?B?0JTQtdC90LjRgSDQmtCw0YDQv9C10L3QutC+?=) Date: Mon, 6 Apr 2015 21:42:00 +0300 Subject: [aerogear-dev] GSoC - AeroDoc overhaul? In-Reply-To: References: Message-ID: Thank you everybody, I hope I will work on AeroDoc with you. I really excited about this project. Denis 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : > +1 I think it's a cool GSoC project as well :-) > > On Fri, Apr 3, 2015 at 5:37 PM, Sebastien Blanc > wrote: > >> Sounds good ! >> As Corinne said, it touches many parts of the AeroGear project. >> Sebi >> >> On Fri, Apr 3, 2015 at 3:16 PM, ????? ???????? wrote: >> >>> Hi everyone, >>> I am a GSoC applicant and I am interested in development of "AeroDoc >>> 2.0". >>> It seems to me that this project fits my skills and interests. >>> >>> >>> Denis. >>> >>> 2015-03-26 10:53 GMT+03:00 Matthias Wessendorf : >>> >>>> Hi, >>>> >>>> for GSoC, I thought about a possible "AeroDoc 2.0" >>>> >>>> * remove picket link based auth with keycloak >>>> * usage of OAuth2 auth for the iOS and Android version >>>> * port iOS app to Swift >>>> * Windows support >>>> >>>> One related tought: perhaps we change the name, and modify the use-case >>>> - to not be "doctor" specific? >>>> >>>> -Matthias >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150406/ce66a4cc/attachment.html From lukas.fryc at gmail.com Tue Apr 7 03:08:40 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 07 Apr 2015 07:08:40 +0000 Subject: [aerogear-dev] UPS using JMS update In-Reply-To: References: Message-ID: Do I read well that the subsystem would be the ONLY distribution mechanism? Created https://issues.jboss.org/browse/AGPUSH-1354 btw. Feel free to comment there. ~ Lukas p? 3. 4. 2015 v 13:50 odes?latel Matthias Wessendorf napsal: > Cool stuff > > I am totally fine having this tied ti wf/eap > > wondering: at some point, should we offer a dist as (only) subststem for > wf/eap? > > > On Friday, April 3, 2015, Sebastien Blanc wrote: > >> That all sounds very good :) >> Thanks for the headupate, I will soon give it a try. >> >> On Fri, Apr 3, 2015 at 10:34 AM, Luk?? Fry? wrote: >> >>> Hi guys, >>> >>> so as outlined in previous thread [1], I have prototyped a JMS batching >>> approach for push message delivery. >>> >>> >>> >>> >>> We've discussed the approach with Matthias, Mirek Novak and Ondrej >>> Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents >>> describes a concept that we have came with: >>> >>> Diagram: >>> https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing >>> >>> Text Doc: >>> https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing >>> >>> >>> >>> >>> >>> >>> Implementation-wise, I've so far prototyped the messaging part (split >>> SenderService functionality to two subsequent queues with MDBs as shown on >>> diagram), >>> >>> but that's just a start, since we must configure it appropriately for >>> efficiency (queue configuration and batch sizes) and verify that >>> configuration works as expected, >>> >>> the prototype lives on a branch (unpolished, to be squashed later): >>> https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching >>> >>> Off course, you can play with it already. :-) >>> >>> >>> >>> >>> >>> Apart from the new requirement of using Java EE full profile (JMS), the >>> prototype leverages implementation-specific configurations and APIs: >>> >>> - org.hibernate.Query for token streaming / batch fetching >>> - HornetQ configurations of queue size, blocking behavior and >>> message de-duplication >>> >>> That pretty much binds us to WildFly/EAP - we can tweak it to run on any >>> compliant app server, but without specific configurations it won't work >>> properly. >>> >>> >>> >>> Once configured and functionally tested (that can even wait for Beta2 I >>> guess), >>> >>> we can cooperate with Mobile QE on testing (Stefan, Adam), their test >>> suite contains mocks of APNS/GCM against which we can load test. >>> >>> >>> >>> Cheers! >>> >>> ~ Lukas >>> >>> >>> [1] >>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > -- > Sent from Gmail Mobile > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/c4c34ecb/attachment-0001.html From matzew at apache.org Tue Apr 7 03:17:50 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Apr 2015 09:17:50 +0200 Subject: [aerogear-dev] UPS using JMS update In-Reply-To: References: Message-ID: Not sure, I think that was my question though On Tue, Apr 7, 2015 at 9:08 AM, Luk?? Fry? wrote: > Do I read well that the subsystem would be the ONLY distribution mechanism? > > Created https://issues.jboss.org/browse/AGPUSH-1354 btw. Feel free to > comment there. > > ~ Lukas > > p? 3. 4. 2015 v 13:50 odes?latel Matthias Wessendorf > napsal: > > Cool stuff >> >> I am totally fine having this tied ti wf/eap >> >> wondering: at some point, should we offer a dist as (only) subststem for >> wf/eap? >> >> >> On Friday, April 3, 2015, Sebastien Blanc wrote: >> >>> That all sounds very good :) >>> Thanks for the headupate, I will soon give it a try. >>> >>> On Fri, Apr 3, 2015 at 10:34 AM, Luk?? Fry? >>> wrote: >>> >>>> Hi guys, >>>> >>>> so as outlined in previous thread [1], I have prototyped a JMS batching >>>> approach for push message delivery. >>>> >>>> >>>> >>>> >>>> We've discussed the approach with Matthias, Mirek Novak and Ondrej >>>> Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents >>>> describes a concept that we have came with: >>>> >>>> Diagram: >>>> https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing >>>> >>>> Text Doc: >>>> https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing >>>> >>>> >>>> >>>> >>>> >>>> >>>> Implementation-wise, I've so far prototyped the messaging part (split >>>> SenderService functionality to two subsequent queues with MDBs as shown on >>>> diagram), >>>> >>>> but that's just a start, since we must configure it appropriately for >>>> efficiency (queue configuration and batch sizes) and verify that >>>> configuration works as expected, >>>> >>>> the prototype lives on a branch (unpolished, to be squashed later): >>>> https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching >>>> >>>> Off course, you can play with it already. :-) >>>> >>>> >>>> >>>> >>>> >>>> Apart from the new requirement of using Java EE full profile (JMS), the >>>> prototype leverages implementation-specific configurations and APIs: >>>> >>>> - org.hibernate.Query for token streaming / batch fetching >>>> - HornetQ configurations of queue size, blocking behavior and >>>> message de-duplication >>>> >>>> That pretty much binds us to WildFly/EAP - we can tweak it to run on >>>> any compliant app server, but without specific configurations it won't work >>>> properly. >>>> >>>> >>>> >>>> Once configured and functionally tested (that can even wait for Beta2 I >>>> guess), >>>> >>>> we can cooperate with Mobile QE on testing (Stefan, Adam), their test >>>> suite contains mocks of APNS/GCM against which we can load test. >>>> >>>> >>>> >>>> Cheers! >>>> >>>> ~ Lukas >>>> >>>> >>>> [1] >>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> -- >> Sent from Gmail Mobile >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/a07d97f1/attachment.html From ivan.gurtler at ahead-itec.com Tue Apr 7 03:48:47 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Tue, 7 Apr 2015 09:48:47 +0200 Subject: [aerogear-dev] WP raw push message In-Reply-To: References: Message-ID: Hi, I have problem with ... https://aerogear.org/docs/unifiedpush/push-message-format-dev/ ... it return 403 error .. Thanks *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-03-04 16:26 GMT+01:00 Ivan G?rtler : > Thanks ... > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-03-04 16:19 GMT+01:00 Sebastien Blanc : > >> FYI https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/68 >> Feel free to review and test, feedback welcome ! >> >> >> On Tue, Mar 3, 2015 at 2:51 PM, Ivan G?rtler > > wrote: >> >>> Thanks .. thanks .. thanks... :) >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> 2015-03-03 14:46 GMT+01:00 Sebastien Blanc : >>> >>>> It's on my plate for this week : >>>> https://issues.jboss.org/browse/AGPUSH-1262 >>>> But until getting there, you can use the .userData(map) builder method >>>> and set the values manually ( >>>> https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/message/UnifiedMessage.java#L338 >>>> ) >>>> >>>> >>>> >>>> >>>> On Tue, Mar 3, 2015 at 2:39 PM, Ivan G?rtler < >>>> ivan.gurtler at ahead-itec.com> wrote: >>>> >>>>> Thanks :) .... and is there already java library with this >>>>> functionality ? >>>>> >>>>> *Mgr. Ivan G?rtler* >>>>> Mobile software developer >>>>> >>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>> 602 00 Brno (Czech Republic) >>>>> >>>>> www.ahead-itec.com | twitter | >>>>> mobile security solutions >>>>> >>>>> 2015-03-03 14:31 GMT+01:00 Sebastien Blanc : >>>>> >>>>>> Hi ! >>>>>> This is documentated but not yet pushed to our published website. But >>>>>> you can find it here : >>>>>> https://github.com/aerogear/aerogear.org/pull/492/files >>>>>> >>>>>> Seb >>>>>> >>>>>> >>>>>> On Tue, Mar 3, 2015 at 2:26 PM, Ivan G?rtler < >>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> in master branch (in WNSPushNotificationSender.java) it is possible >>>>>>> to send raw notification. But how can it be called from outside server? I >>>>>>> found this... >>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html >>>>>>> ... but without "raw" configuration ... >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> *Mgr. Ivan G?rtler* >>>>>>> Mobile software developer >>>>>>> >>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>> 602 00 Brno (Czech Republic) >>>>>>> >>>>>>> www.ahead-itec.com | twitter | >>>>>>> mobile security solutions >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/1c20dc78/attachment-0001.html From lukas.fryc at gmail.com Tue Apr 7 03:49:55 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 07 Apr 2015 07:49:55 +0000 Subject: [aerogear-dev] UPS as WildFly Subsystem (was: UPS using JMS) In-Reply-To: References: Message-ID: I reached out to Stian in order to fully understand the "Why" behind Keycloak offering a subsystem, and he identified two benefits: * smaller appliance downloads * easier to patch modules than monolithic WAR Can you see anything else? The question is how much relevant are these benefits for us, since we depend much more on Java EE (especially with JMS coming). In case of UPS, we can definitely strip some download Megabytes for (potential) appliance distribution (good for microservices oriented architectures), while still providing installation of subsystem to existing Wildfly EE instances. We can continue shipping WAR just for sake of backwards compatibility in case it will appear to be effortless. However I agree that UPS as WF subsystem is a direction worth to explore! ~ Lukas ?t 7. 4. 2015 v 9:18 odes?latel Matthias Wessendorf napsal: > Not sure, I think that was my question though > > On Tue, Apr 7, 2015 at 9:08 AM, Luk?? Fry? wrote: > >> Do I read well that the subsystem would be the ONLY distribution >> mechanism? >> >> Created https://issues.jboss.org/browse/AGPUSH-1354 btw. Feel free to >> comment there. >> >> ~ Lukas >> >> p? 3. 4. 2015 v 13:50 odes?latel Matthias Wessendorf >> napsal: >> >> Cool stuff >>> >>> I am totally fine having this tied ti wf/eap >>> >>> wondering: at some point, should we offer a dist as (only) subststem for >>> wf/eap? >>> >>> >>> On Friday, April 3, 2015, Sebastien Blanc wrote: >>> >>>> That all sounds very good :) >>>> Thanks for the headupate, I will soon give it a try. >>>> >>>> On Fri, Apr 3, 2015 at 10:34 AM, Luk?? Fry? >>>> wrote: >>>> >>>>> Hi guys, >>>>> >>>>> so as outlined in previous thread [1], I have prototyped a JMS >>>>> batching approach for push message delivery. >>>>> >>>>> >>>>> >>>>> >>>>> We've discussed the approach with Matthias, Mirek Novak and Ondrej >>>>> Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents >>>>> describes a concept that we have came with: >>>>> >>>>> Diagram: >>>>> https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing >>>>> >>>>> Text Doc: >>>>> https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Implementation-wise, I've so far prototyped the messaging part (split >>>>> SenderService functionality to two subsequent queues with MDBs as shown on >>>>> diagram), >>>>> >>>>> but that's just a start, since we must configure it appropriately for >>>>> efficiency (queue configuration and batch sizes) and verify that >>>>> configuration works as expected, >>>>> >>>>> the prototype lives on a branch (unpolished, to be squashed later): >>>>> https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching >>>>> >>>>> Off course, you can play with it already. :-) >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Apart from the new requirement of using Java EE full profile (JMS), >>>>> the prototype leverages implementation-specific configurations and APIs: >>>>> >>>>> - org.hibernate.Query for token streaming / batch fetching >>>>> - HornetQ configurations of queue size, blocking behavior and >>>>> message de-duplication >>>>> >>>>> That pretty much binds us to WildFly/EAP - we can tweak it to run on >>>>> any compliant app server, but without specific configurations it won't work >>>>> properly. >>>>> >>>>> >>>>> >>>>> Once configured and functionally tested (that can even wait for Beta2 >>>>> I guess), >>>>> >>>>> we can cooperate with Mobile QE on testing (Stefan, Adam), their test >>>>> suite contains mocks of APNS/GCM against which we can load test. >>>>> >>>>> >>>>> >>>>> Cheers! >>>>> >>>>> ~ Lukas >>>>> >>>>> >>>>> [1] >>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >>> -- >>> Sent from Gmail Mobile >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/b0be730b/attachment.html From lukas.fryc at gmail.com Tue Apr 7 03:50:56 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 07 Apr 2015 07:50:56 +0000 Subject: [aerogear-dev] [UPS] issues with UPS 1.1 on OpenShift (manual deploy) In-Reply-To: <20150406171349.GA4956@abstractj.org> References: <20150406171349.GA4956@abstractj.org> Message-ID: Thanks for update, Bruno. I will try it and let you know. po 6. 4. 2015 v 19:14 odes?latel Bruno Oliveira napsal: > A little update, if you're willing to deploy UPS on Openshift: > https://issues.jboss.org/browse/AGPUSH-1352 > > On 2015-04-02, Sebastien Blanc wrote: > > Thx for the headup ! > > When did this upgrade happened ? > > Shouldn't we have the problem also with UPS 1.0.x series on OpenShift ? > > > > On Thu, Apr 2, 2015 at 2:55 PM, Bruno Oliveira > wrote: > > > > > Good morning guys, I'm investigating the problem since yesterday. The > > > problem at first glance is related with the upgrade on OpenShift to > Java 8. > > > > > > Java 8 sends TLSv1.2 ClientHello and Java 7 TLSv1 and if the server > > > somehow does not support version 1.2, it should be able to negotiate > down > > > to 1.1 or 1.0. > > > > > > I'm still investigating the root cause, but the immediate fix is to > run KC > > > and UPS on JDK 1.7 only. Meanwhile I will be investigating the issue. > > > > > > On Tue, Mar 31, 2015 at 11:10 AM, Matthias Wessendorf < > matzew at apache.org> > > > wrote: > > > > > >> that is on a totally different KC version > > >> > > >> On Tue, Mar 31, 2015 at 4:03 PM, Sebastien Blanc > > > >> wrote: > > >> > > >>> Maybe, > > >>> But it may also be that I'm missing something stupid :) and I have > to > > >>> configure something extra since openshift is https and I always test > > >>> locally ... But yeah for 1.0.x I did not have to do anything. > > >>> > > >>> > > >>> On Tue, Mar 31, 2015 at 3:52 PM, Matthias Wessendorf < > matzew at apache.org> > > >>> wrote: > > >>> > > >>>> anything wrong w/ the keycloak adapter, or was there a fix for a > 1.1.1? > > >>>> > > >>>> On Tue, Mar 31, 2015 at 3:50 PM, Sebastien Blanc < > scm.blanc at gmail.com> > > >>>> wrote: > > >>>> > > >>>>> Hi ! > > >>>>> I was trying (and so was Lukas) to deploy UPS 1.1 (master branch) > to > > >>>>> an openshift gear (Wildfly 8.2 cartridge). After tweaking a bit the > > >>>>> datasources to get it deployed, when trying to access /ag-push , > I'm get an > > >>>>> 500 internal server error. > > >>>>> > > >>>>> The wildfly logs show me the following : > > >>>>> > > >>>>> 2015-03-31 09:40:47,240 ERROR [io.undertow.request] (default > task-8) UT005023: Exception handling request to /ag-push/index.html: > java.lang.RuntimeException: Unable to resolve realm public key remotely > > >>>>> at org.keycloak.adapters.AdapterDeploymentContext. > resolveRealmKey(AdapterDeploymentContext.java:134) > [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] > > >>>>> at org.keycloak.adapters.AdapterDeploymentContext. > resolveDeployment(AdapterDeploymentContext.java:83) > [keycloak-adapter-core-1.1.0.Final.jar:1.1.0.Final] > > >>>>> at org.keycloak.adapters.PreAuthActionsHandler. > preflightCors(PreAuthActionsHandler.java:71) [keycloak-adapter-core-1.1.0. > Final.jar:1.1.0.Final] > > >>>>> at org.keycloak.adapters.PreAuthActionsHandler. > handleRequest(PreAuthActionsHandler.java:47) [keycloak-adapter-core-1.1.0. > Final.jar:1.1.0.Final] > > >>>>> at org.keycloak.adapters.undertow. > ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) > [keycloak-undertow-adapter-1.1.0.Final.jar:1.1.0.Final] > > >>>>> at io.undertow.server.handlers.PredicateHandler. > handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Final. > jar:1.1.0.Final] > > >>>>> at io.undertow.servlet.handlers.ServletInitialHandler. > handleFirstRequest(ServletInitialHandler.java:261) > [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] > > >>>>> at io.undertow.servlet.handlers.ServletInitialHandler. > dispatchRequest(ServletInitialHandler.java:247) > [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] > > >>>>> at io.undertow.servlet.handlers. > ServletInitialHandler.access$000(ServletInitialHandler.java:76) > [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] > > >>>>> at io.undertow.servlet.handlers.ServletInitialHandler$1. > handleRequest(ServletInitialHandler.java:166) > [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] > > >>>>> at io.undertow.server.Connectors. > executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Final. > jar:1.1.0.Final] > > >>>>> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:759) > [undertow-core-1.1.0.Final.jar:1.1.0.Final] > > >>>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [rt.jar:1.8.0_31] > > >>>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [rt.jar:1.8.0_31] > > >>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] > > >>>>> Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not > authenticated > > >>>>> at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:431) > [jsse.jar:1.8.0_31] > > >>>>> at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128) > [httpclient-4.2.1.jar:4.2.1] > > >>>>> at org.apache.http.conn.ssl.SSLSocketFactory. > connectSocket(SSLSocketFactory.java:572) [httpclient-4.2.1.jar:4.2.1] > > >>>>> at org.apache.http.impl.conn. > DefaultClientConnectionOperator.openConnection( > DefaultClientConnectionOperator.java:180) [httpclient-4.2.1.jar:4.2.1] > > >>>>> > > >>>>> > > >>>>> So "peer not authenticated" seems pretty obvious for the reason it > fails. > > >>>>> The question is what do we need to do for this ? Anyone an idea ? > > >>>>> > > >>>>> Thx, > > >>>>> Sebi > > >>>>> > > >>>>> > > >>>>> _______________________________________________ > > >>>>> aerogear-dev mailing list > > >>>>> aerogear-dev at 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 > > >>>> > > >>>> _______________________________________________ > > >>>> aerogear-dev mailing list > > >>>> aerogear-dev at lists.jboss.org > > >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > >>>> > > >>> > > >>> > > >>> _______________________________________________ > > >>> aerogear-dev mailing list > > >>> aerogear-dev at 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 > > >> > > >> _______________________________________________ > > >> aerogear-dev mailing list > > >> aerogear-dev at lists.jboss.org > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > >> > > > > > > > > > > > > -- > > > > > > -- > > > "The measure of a man is what he does with power" - Plato > > > - > > > @abstractj > > > - > > > Volenti Nihil Difficile > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/98fc0d5b/attachment-0001.html From lukas.fryc at gmail.com Tue Apr 7 03:54:01 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 07 Apr 2015 07:54:01 +0000 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: I agree with Idel that DRY approach in Miredot's case seems more appealing. They offer basic docs generation in Free version, but also Pro version for open-source projects under conditions that Aerogear meets [1]. ~ Lukas [1] http://www.miredot.com/price/ ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy napsal: For JAX-RS I prefer use MireDot as a REST API doc generator > http://www.miredot.com/ > > With MireDot you do not need to use additional annotations, like @Api: > > @Path("/pet") > @Api(value = "/pet", description = "Operations about pets") > > > It will parse your JAX-RS annotation and pure javadoc: > > /** > * Operations about pets > */ > @Path("/pet") > > and generate beautiful and user friendly documentation, like this: > http://www.miredot.com/exampledocs/ > Swagger example: http://petstore.swagger.io/ > > And MireDot is free for open source projects! > > Think about this alternative for Swagger. I'm able to prepare Pull Request > for UPS next week. > > > 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : > >> >> >> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp wrote: >> >>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>> >>> > we are using it in Project Newcastle with annotations on the >>> > endpoints, and >>> > it's really handy. >>> >>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + >>> Swagger annotations. >>> In Hawkular we are basically doing the same, but with a different >>> annotation processor. >>> >> >> +1000 >> >> we are, atm, doing similar: >> source >> https://github.com/aerogear/aerogear-unifiedpush-server/ >> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >> unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >> result: >> https://aerogear.org/docs/specs/aerogear-unifiedpush- >> rest/sender/index.html#POST >> >> but the jaxrs doclet does not work w/ JDK8 - something has to change here >> ;-) >> So, I am all for using Swagger annotations on the code to generate the >> HTML docs :-) >> >> Greetings, >> Matthias >> >> >>> >>> I personally think the best is really to have the annotations in the >>> source and not trying >>> to update a separate .yml file, as the latter usually is much easier >>> forgotten. >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Best regards, > Idel Pivnitskiy > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/df104aa4/attachment.html From lukas.fryc at gmail.com Tue Apr 7 03:58:00 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 07 Apr 2015 07:58:00 +0000 Subject: [aerogear-dev] WP raw push message In-Reply-To: References: Message-ID: Hi Ivan, we are working on the fix: https://github.com/aerogear/aerogear.org/pull/569 ?t 7. 4. 2015 v 9:49 odes?latel Ivan G?rtler napsal: Hi, > I have problem with ... https://aerogear.org/docs/ > unifiedpush/push-message-format-dev/ ... it return 403 error .. > > Thanks > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-03-04 16:26 GMT+01:00 Ivan G?rtler : > >> Thanks ... >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-03-04 16:19 GMT+01:00 Sebastien Blanc : >> >>> FYI https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/68 >>> >>> Feel free to review and test, feedback welcome ! >>> >>> >>> On Tue, Mar 3, 2015 at 2:51 PM, Ivan G?rtler < >>> ivan.gurtler at ahead-itec.com> wrote: >>> >>>> Thanks .. thanks .. thanks... :) >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>>> 2015-03-03 14:46 GMT+01:00 Sebastien Blanc : >>>> >>>>> It's on my plate for this week : https://issues.jboss.org/ >>>>> browse/AGPUSH-1262 >>>>> But until getting there, you can use the .userData(map) builder method >>>>> and set the values manually (https://github.com/aerogear/ >>>>> aerogear-unifiedpush-java-client/blob/master/src/main/ >>>>> java/org/jboss/aerogear/unifiedpush/message/UnifiedMessage.java#L338) >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, Mar 3, 2015 at 2:39 PM, Ivan G?rtler < >>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>> >>>>>> Thanks :) .... and is there already java library with this >>>>>> functionality ? >>>>>> >>>>>> *Mgr. Ivan G?rtler* >>>>>> Mobile software developer >>>>>> >>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>> 602 00 Brno (Czech Republic) >>>>>> >>>>>> www.ahead-itec.com | twitter | >>>>>> mobile security solutions >>>>>> >>>>>> 2015-03-03 14:31 GMT+01:00 Sebastien Blanc : >>>>>> >>>>>>> Hi ! >>>>>>> This is documentated but not yet pushed to our published website. >>>>>>> But you can find it here : https://github.com/aerogear/ >>>>>>> aerogear.org/pull/492/files >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> >>>>>>> On Tue, Mar 3, 2015 at 2:26 PM, Ivan G?rtler < >>>>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> in master branch (in WNSPushNotificationSender.java) it is >>>>>>>> possible to send raw notification. But how can it be called from outside >>>>>>>> server? I found this... https://aerogear.org/docs/ >>>>>>>> specs/aerogear-unifiedpush-rest/sender/index.html ... but without >>>>>>>> "raw" configuration ... >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> *Mgr. Ivan G?rtler* >>>>>>>> Mobile software developer >>>>>>>> >>>>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>>>> 602 00 Brno (Czech Republic) >>>>>>>> >>>>>>>> www.ahead-itec.com | twitter | >>>>>>>> mobile security solutions >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/ab267e46/attachment-0001.html From smikloso at redhat.com Tue Apr 7 04:10:36 2015 From: smikloso at redhat.com (Stefan Miklosovic) Date: Tue, 7 Apr 2015 10:10:36 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: Well, we are on the crossroad guys :) Even such simple task as generating API automatically can be done by different means. I do not mind either approach. If Idel is about to do it, feel free to do so. I do not know Miredot and I would personally stick to something proven and widely used, even it does not cover our need 100% and it is not all shiny and cool. I would personaly do simple Swagger YAML and I would not integrate it to sources directly. Having it separate has another advantage like you can move that YAML here and there plus you can design endpoints and you can share it with other people before you even start to implement it. >From my point of view in work, this is really marginal issue for me right now. I just proposed the idea. Regards On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? wrote: > I agree with Idel that DRY approach in Miredot's case seems more appealing. > > They offer basic docs generation in Free version, but also Pro version for > open-source projects under conditions that Aerogear meets [1]. > > ~ Lukas > > [1] http://www.miredot.com/price/ > > ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy > napsal: > >> For JAX-RS I prefer use MireDot as a REST API doc generator >> http://www.miredot.com/ >> >> With MireDot you do not need to use additional annotations, like @Api: >> >> @Path("/pet") >> @Api(value = "/pet", description = "Operations about pets") >> >> >> It will parse your JAX-RS annotation and pure javadoc: >> >> /** >> * Operations about pets >> */ >> @Path("/pet") >> >> and generate beautiful and user friendly documentation, like this: >> http://www.miredot.com/exampledocs/ >> Swagger example: http://petstore.swagger.io/ >> >> And MireDot is free for open source projects! >> >> Think about this alternative for Swagger. I'm able to prepare Pull Request >> for UPS next week. >> >> >> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : >>> >>> >>> >>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp wrote: >>>> >>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>> >>>> > we are using it in Project Newcastle with annotations on the >>>> > endpoints, and >>>> > it's really handy. >>>> >>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + >>>> Swagger annotations. >>>> In Hawkular we are basically doing the same, but with a different >>>> annotation processor. >>> >>> >>> +1000 >>> >>> we are, atm, doing similar: >>> source >>> >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>> result: >>> >>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST >>> >>> but the jaxrs doclet does not work w/ JDK8 - something has to change here >>> ;-) >>> So, I am all for using Swagger annotations on the code to generate the >>> HTML docs :-) >>> >>> Greetings, >>> Matthias >>> >>>> >>>> >>>> I personally think the best is really to have the annotations in the >>>> source and not trying >>>> to update a separate .yml file, as the latter usually is much easier >>>> forgotten. >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> Best regards, >> Idel Pivnitskiy >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Stefan Miklosovic Red Hat Brno - JBoss Mobile Platform e-mail: smikloso at redhat.com irc: smikloso From matzew at apache.org Tue Apr 7 04:16:04 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Apr 2015 10:16:04 +0200 Subject: [aerogear-dev] UPS as WildFly Subsystem (was: UPS using JMS) In-Reply-To: References: Message-ID: On Tue, Apr 7, 2015 at 9:49 AM, Luk?? Fry? wrote: > I reached out to Stian in order to fully understand the "Why" behind > Keycloak offering a subsystem, and he identified two benefits: > > * smaller appliance downloads > * easier to patch modules than monolithic WAR > > Can you see anything else? > > The question is how much relevant are these benefits for us, since we > depend much more on Java EE (especially with JMS coming). > I think it's worth to evaluate once we got JMS working and integrated. I don't think it has to come now - it was more an open question for future development tasks > > > > In case of UPS, we can definitely strip some download Megabytes for > (potential) appliance distribution (good for microservices oriented > architectures), > > while still providing installation of subsystem to existing Wildfly EE > instances. We can continue shipping WAR just for sake of backwards > compatibility in case it will appear to be effortless. > Perhaps a 2.0.0 can be subsystem only? > > > > However I agree that UPS as WF subsystem is a direction worth to explore! > > ~ Lukas > > > > > > ?t 7. 4. 2015 v 9:18 odes?latel Matthias Wessendorf > napsal: > >> Not sure, I think that was my question though >> >> On Tue, Apr 7, 2015 at 9:08 AM, Luk?? Fry? wrote: >> >>> Do I read well that the subsystem would be the ONLY distribution >>> mechanism? >>> >>> Created https://issues.jboss.org/browse/AGPUSH-1354 btw. Feel free to >>> comment there. >>> >>> ~ Lukas >>> >>> p? 3. 4. 2015 v 13:50 odes?latel Matthias Wessendorf >>> napsal: >>> >>> Cool stuff >>>> >>>> I am totally fine having this tied ti wf/eap >>>> >>>> wondering: at some point, should we offer a dist as (only) subststem >>>> for wf/eap? >>>> >>>> >>>> On Friday, April 3, 2015, Sebastien Blanc wrote: >>>> >>>>> That all sounds very good :) >>>>> Thanks for the headupate, I will soon give it a try. >>>>> >>>>> On Fri, Apr 3, 2015 at 10:34 AM, Luk?? Fry? >>>>> wrote: >>>>> >>>>>> Hi guys, >>>>>> >>>>>> so as outlined in previous thread [1], I have prototyped a JMS >>>>>> batching approach for push message delivery. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> We've discussed the approach with Matthias, Mirek Novak and Ondrej >>>>>> Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents >>>>>> describes a concept that we have came with: >>>>>> >>>>>> Diagram: >>>>>> https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing >>>>>> >>>>>> Text Doc: >>>>>> https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Implementation-wise, I've so far prototyped the messaging part (split >>>>>> SenderService functionality to two subsequent queues with MDBs as shown on >>>>>> diagram), >>>>>> >>>>>> but that's just a start, since we must configure it appropriately for >>>>>> efficiency (queue configuration and batch sizes) and verify that >>>>>> configuration works as expected, >>>>>> >>>>>> the prototype lives on a branch (unpolished, to be squashed later): >>>>>> https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching >>>>>> >>>>>> Off course, you can play with it already. :-) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Apart from the new requirement of using Java EE full profile (JMS), >>>>>> the prototype leverages implementation-specific configurations and APIs: >>>>>> >>>>>> - org.hibernate.Query for token streaming / batch fetching >>>>>> - HornetQ configurations of queue size, blocking behavior and >>>>>> message de-duplication >>>>>> >>>>>> That pretty much binds us to WildFly/EAP - we can tweak it to run on >>>>>> any compliant app server, but without specific configurations it won't work >>>>>> properly. >>>>>> >>>>>> >>>>>> >>>>>> Once configured and functionally tested (that can even wait for Beta2 >>>>>> I guess), >>>>>> >>>>>> we can cooperate with Mobile QE on testing (Stefan, Adam), their test >>>>>> suite contains mocks of APNS/GCM against which we can load test. >>>>>> >>>>>> >>>>>> >>>>>> Cheers! >>>>>> >>>>>> ~ Lukas >>>>>> >>>>>> >>>>>> [1] >>>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/2fefb16e/attachment.html From matzew at apache.org Tue Apr 7 04:29:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Apr 2015 10:29:41 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: having it separate did not work out. We had that in the past. Even today, where the source code comments is used, not every API changes is automatically catched (lack of updates on the documentation/comments). However, since both live together (comments/doc and source), it is IMO less of a hassle to get things updated. On Tue, Apr 7, 2015 at 10:10 AM, Stefan Miklosovic wrote: > Well, > > we are on the crossroad guys :) Even such simple task as generating > API automatically can be done by different means. > > I do not mind either approach. If Idel is about to do it, feel free to > do so. I do not know Miredot and I would personally stick to something > proven and widely used, even it does not cover our need 100% and it is > not all shiny and cool. > > I would personaly do simple Swagger YAML and I would not integrate it > to sources directly. Having it separate has another advantage like you > can move that YAML here and there plus you can design endpoints and > you can share it with other people before you even start to implement > it. > > From my point of view in work, this is really marginal issue for me > right now. I just proposed the idea. > > Regards > > On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? wrote: > > I agree with Idel that DRY approach in Miredot's case seems more > appealing. > > > > They offer basic docs generation in Free version, but also Pro version > for > > open-source projects under conditions that Aerogear meets [1]. > > > > ~ Lukas > > > > [1] http://www.miredot.com/price/ > > > > ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < > idel.pivnitskiy at gmail.com> > > napsal: > > > >> For JAX-RS I prefer use MireDot as a REST API doc generator > >> http://www.miredot.com/ > >> > >> With MireDot you do not need to use additional annotations, like @Api: > >> > >> @Path("/pet") > >> @Api(value = "/pet", description = "Operations about pets") > >> > >> > >> It will parse your JAX-RS annotation and pure javadoc: > >> > >> /** > >> * Operations about pets > >> */ > >> @Path("/pet") > >> > >> and generate beautiful and user friendly documentation, like this: > >> http://www.miredot.com/exampledocs/ > >> Swagger example: http://petstore.swagger.io/ > >> > >> And MireDot is free for open source projects! > >> > >> Think about this alternative for Swagger. I'm able to prepare Pull > Request > >> for UPS next week. > >> > >> > >> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : > >>> > >>> > >>> > >>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp > wrote: > >>>> > >>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: > >>>> > >>>> > we are using it in Project Newcastle with annotations on the > >>>> > endpoints, and > >>>> > it's really handy. > >>>> > >>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + > >>>> Swagger annotations. > >>>> In Hawkular we are basically doing the same, but with a different > >>>> annotation processor. > >>> > >>> > >>> +1000 > >>> > >>> we are, atm, doing similar: > >>> source > >>> > >>> > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 > >>> result: > >>> > >>> > https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST > >>> > >>> but the jaxrs doclet does not work w/ JDK8 - something has to change > here > >>> ;-) > >>> So, I am all for using Swagger annotations on the code to generate the > >>> HTML docs :-) > >>> > >>> Greetings, > >>> Matthias > >>> > >>>> > >>>> > >>>> I personally think the best is really to have the annotations in the > >>>> source and not trying > >>>> to update a separate .yml file, as the latter usually is much easier > >>>> forgotten. > >>>> _______________________________________________ > >>>> aerogear-dev mailing list > >>>> aerogear-dev at 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 > >>> > >>> _______________________________________________ > >>> aerogear-dev mailing list > >>> aerogear-dev at lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > >> > >> > >> > >> -- > >> Best regards, > >> Idel Pivnitskiy > >> E-mail: Idel.Pivnitskiy at gmail.com > >> Twitter: @idelpivnitskiy > >> GitHub: @idelpivnitskiy > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: smikloso at redhat.com > irc: smikloso > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/32810d05/attachment-0001.html From matzew at apache.org Tue Apr 7 05:44:33 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Apr 2015 11:44:33 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: Idel, would you mind to create a branch for us, so we can investigate the MireDot solution? also the build should be working w/ JDK8. ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it does not really use any fancy annotations (e.g. see [2]) - that's why we picked it. Thanks! Matthias [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ [2] https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? wrote: > I agree with Idel that DRY approach in Miredot's case seems more appealing. > > They offer basic docs generation in Free version, but also Pro version for > open-source projects under conditions that Aerogear meets [1]. > > ~ Lukas > > [1] http://www.miredot.com/price/ > > ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < > idel.pivnitskiy at gmail.com> napsal: > > For JAX-RS I prefer use MireDot as a REST API doc generator >> http://www.miredot.com/ >> >> With MireDot you do not need to use additional annotations, like @Api: >> >> @Path("/pet") >> @Api(value = "/pet", description = "Operations about pets") >> >> >> It will parse your JAX-RS annotation and pure javadoc: >> >> /** >> * Operations about pets >> */ >> @Path("/pet") >> >> and generate beautiful and user friendly documentation, like this: >> http://www.miredot.com/exampledocs/ >> Swagger example: http://petstore.swagger.io/ >> >> And MireDot is free for open source projects! >> >> Think about this alternative for Swagger. I'm able to prepare Pull >> Request for UPS next week. >> >> >> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : >> >>> >>> >>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp wrote: >>> >>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>> >>>> > we are using it in Project Newcastle with annotations on the >>>> > endpoints, and >>>> > it's really handy. >>>> >>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + >>>> Swagger annotations. >>>> In Hawkular we are basically doing the same, but with a different >>>> annotation processor. >>>> >>> >>> +1000 >>> >>> we are, atm, doing similar: >>> source >>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>> unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>> result: >>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>> rest/sender/index.html#POST >>> >>> but the jaxrs doclet does not work w/ JDK8 - something has to change >>> here ;-) >>> So, I am all for using Swagger annotations on the code to generate the >>> HTML docs :-) >>> >>> Greetings, >>> Matthias >>> >>> >>>> >>>> I personally think the best is really to have the annotations in the >>>> source and not trying >>>> to update a separate .yml file, as the latter usually is much easier >>>> forgotten. >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Best regards, >> Idel Pivnitskiy >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/1c13d04e/attachment.html From idel.pivnitskiy at gmail.com Tue Apr 7 05:57:06 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 7 Apr 2015 12:57:06 +0300 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: Matthias, Sure, I will work on it. But I think that it would be better if you request a license [1] on your email and forward it to me. It won't be a problem to use a free version, but pro version has a very cool features, like: - Display javadoc comments for the fields of json payloads and enums - JSON field documentation - Type replacement (custom serialisation, JSON types) Please, request a li [1] http://miredot.com/price/ 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : > Idel, > > would you mind to create a branch for us, so we can investigate the > MireDot solution? also the build should be working w/ JDK8. > > ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it does not > really use any fancy annotations (e.g. see [2]) - that's why we picked it. > > Thanks! > Matthias > > [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ > [2] > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 > > On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? wrote: > >> I agree with Idel that DRY approach in Miredot's case seems more >> appealing. >> >> They offer basic docs generation in Free version, but also Pro version >> for open-source projects under conditions that Aerogear meets [1]. >> >> ~ Lukas >> >> [1] http://www.miredot.com/price/ >> >> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> napsal: >> >> For JAX-RS I prefer use MireDot as a REST API doc generator >>> http://www.miredot.com/ >>> >>> With MireDot you do not need to use additional annotations, like @Api: >>> >>> @Path("/pet") >>> @Api(value = "/pet", description = "Operations about pets") >>> >>> >>> It will parse your JAX-RS annotation and pure javadoc: >>> >>> /** >>> * Operations about pets >>> */ >>> @Path("/pet") >>> >>> and generate beautiful and user friendly documentation, like this: >>> http://www.miredot.com/exampledocs/ >>> Swagger example: http://petstore.swagger.io/ >>> >>> And MireDot is free for open source projects! >>> >>> Think about this alternative for Swagger. I'm able to prepare Pull >>> Request for UPS next week. >>> >>> >>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : >>> >>>> >>>> >>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp wrote: >>>> >>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>> >>>>> > we are using it in Project Newcastle with annotations on the >>>>> > endpoints, and >>>>> > it's really handy. >>>>> >>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + >>>>> Swagger annotations. >>>>> In Hawkular we are basically doing the same, but with a different >>>>> annotation processor. >>>>> >>>> >>>> +1000 >>>> >>>> we are, atm, doing similar: >>>> source >>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>> result: >>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>> rest/sender/index.html#POST >>>> >>>> but the jaxrs doclet does not work w/ JDK8 - something has to change >>>> here ;-) >>>> So, I am all for using Swagger annotations on the code to generate the >>>> HTML docs :-) >>>> >>>> Greetings, >>>> Matthias >>>> >>>> >>>>> >>>>> I personally think the best is really to have the annotations in the >>>>> source and not trying >>>>> to update a separate .yml file, as the latter usually is much easier >>>>> forgotten. >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Idel Pivnitskiy >>> E-mail: Idel.Pivnitskiy at gmail.com >>> Twitter: @idelpivnitskiy >>> GitHub: @idelpivnitskiy >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Best regards, Idel Pivnitskiy E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/e84a094d/attachment-0001.html From matzew at apache.org Tue Apr 7 06:48:29 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Apr 2015 12:48:29 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: Swagger allows doc on the source as well, right ? Just wondering. REgarding license, I need to double check on that before... On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy wrote: > Matthias, > > Sure, I will work on it. > But I think that it would be better if you request a license [1] on your > email and forward it to me. > It won't be a problem to use a free version, but pro version has a very > cool features, like: > > - Display javadoc comments for the fields of json payloads and enums > - JSON field documentation > - Type replacement (custom serialisation, JSON types) > > Please, request a li > > [1] http://miredot.com/price/ > > 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : > >> Idel, >> >> would you mind to create a branch for us, so we can investigate the >> MireDot solution? also the build should be working w/ JDK8. >> >> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it does >> not really use any fancy annotations (e.g. see [2]) - that's why we picked >> it. >> >> Thanks! >> Matthias >> >> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >> [2] >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >> >> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? wrote: >> >>> I agree with Idel that DRY approach in Miredot's case seems more >>> appealing. >>> >>> They offer basic docs generation in Free version, but also Pro version >>> for open-source projects under conditions that Aerogear meets [1]. >>> >>> ~ Lukas >>> >>> [1] http://www.miredot.com/price/ >>> >>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>> idel.pivnitskiy at gmail.com> napsal: >>> >>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>> http://www.miredot.com/ >>>> >>>> With MireDot you do not need to use additional annotations, like @Api: >>>> >>>> @Path("/pet") >>>> @Api(value = "/pet", description = "Operations about pets") >>>> >>>> >>>> It will parse your JAX-RS annotation and pure javadoc: >>>> >>>> /** >>>> * Operations about pets >>>> */ >>>> @Path("/pet") >>>> >>>> and generate beautiful and user friendly documentation, like this: >>>> http://www.miredot.com/exampledocs/ >>>> Swagger example: http://petstore.swagger.io/ >>>> >>>> And MireDot is free for open source projects! >>>> >>>> Think about this alternative for Swagger. I'm able to prepare Pull >>>> Request for UPS next week. >>>> >>>> >>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : >>>> >>>>> >>>>> >>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>> wrote: >>>>> >>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>> >>>>>> > we are using it in Project Newcastle with annotations on the >>>>>> > endpoints, and >>>>>> > it's really handy. >>>>>> >>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + >>>>>> Swagger annotations. >>>>>> In Hawkular we are basically doing the same, but with a different >>>>>> annotation processor. >>>>>> >>>>> >>>>> +1000 >>>>> >>>>> we are, atm, doing similar: >>>>> source >>>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>> result: >>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>>> rest/sender/index.html#POST >>>>> >>>>> but the jaxrs doclet does not work w/ JDK8 - something has to change >>>>> here ;-) >>>>> So, I am all for using Swagger annotations on the code to generate the >>>>> HTML docs :-) >>>>> >>>>> Greetings, >>>>> Matthias >>>>> >>>>> >>>>>> >>>>>> I personally think the best is really to have the annotations in the >>>>>> source and not trying >>>>>> to update a separate .yml file, as the latter usually is much easier >>>>>> forgotten. >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Idel Pivnitskiy >>>> E-mail: Idel.Pivnitskiy at gmail.com >>>> Twitter: @idelpivnitskiy >>>> GitHub: @idelpivnitskiy >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Best regards, > Idel Pivnitskiy > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/8bb51bfc/attachment.html From idel.pivnitskiy at gmail.com Tue Apr 7 06:56:51 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 7 Apr 2015 13:56:51 +0300 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: Yes, Swagger can generate doc on the fly, but Swagger use its own annotations instead of parse JAX-RS annotations and javadoc, like MireDot. What about licence: Apache Tika, for example, uses pro version of MireDot https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : > Swagger allows doc on the source as well, right ? Just wondering. > > REgarding license, I need to double check on that before... > > On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < > idel.pivnitskiy at gmail.com> wrote: > >> Matthias, >> >> Sure, I will work on it. >> But I think that it would be better if you request a license [1] on your >> email and forward it to me. >> It won't be a problem to use a free version, but pro version has a very >> cool features, like: >> >> - Display javadoc comments for the fields of json payloads and enums >> - JSON field documentation >> - Type replacement (custom serialisation, JSON types) >> >> Please, request a li >> >> [1] http://miredot.com/price/ >> >> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >> >>> Idel, >>> >>> would you mind to create a branch for us, so we can investigate the >>> MireDot solution? also the build should be working w/ JDK8. >>> >>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it does >>> not really use any fancy annotations (e.g. see [2]) - that's why we picked >>> it. >>> >>> Thanks! >>> Matthias >>> >>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>> [2] >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>> >>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? wrote: >>> >>>> I agree with Idel that DRY approach in Miredot's case seems more >>>> appealing. >>>> >>>> They offer basic docs generation in Free version, but also Pro version >>>> for open-source projects under conditions that Aerogear meets [1]. >>>> >>>> ~ Lukas >>>> >>>> [1] http://www.miredot.com/price/ >>>> >>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>> idel.pivnitskiy at gmail.com> napsal: >>>> >>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>> http://www.miredot.com/ >>>>> >>>>> With MireDot you do not need to use additional annotations, like @Api: >>>>> >>>>> @Path("/pet") >>>>> @Api(value = "/pet", description = "Operations about pets") >>>>> >>>>> >>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>> >>>>> /** >>>>> * Operations about pets >>>>> */ >>>>> @Path("/pet") >>>>> >>>>> and generate beautiful and user friendly documentation, like this: >>>>> http://www.miredot.com/exampledocs/ >>>>> Swagger example: http://petstore.swagger.io/ >>>>> >>>>> And MireDot is free for open source projects! >>>>> >>>>> Think about this alternative for Swagger. I'm able to prepare Pull >>>>> Request for UPS next week. >>>>> >>>>> >>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : >>>>> >>>>>> >>>>>> >>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>> wrote: >>>>>> >>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>> >>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>> > endpoints, and >>>>>>> > it's really handy. >>>>>>> >>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + >>>>>>> Swagger annotations. >>>>>>> In Hawkular we are basically doing the same, but with a different >>>>>>> annotation processor. >>>>>>> >>>>>> >>>>>> +1000 >>>>>> >>>>>> we are, atm, doing similar: >>>>>> source >>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>> result: >>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>>>> rest/sender/index.html#POST >>>>>> >>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to change >>>>>> here ;-) >>>>>> So, I am all for using Swagger annotations on the code to generate >>>>>> the HTML docs :-) >>>>>> >>>>>> Greetings, >>>>>> Matthias >>>>>> >>>>>> >>>>>>> >>>>>>> I personally think the best is really to have the annotations in the >>>>>>> source and not trying >>>>>>> to update a separate .yml file, as the latter usually is much easier >>>>>>> forgotten. >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Idel Pivnitskiy >>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>> Twitter: @idelpivnitskiy >>>>> GitHub: @idelpivnitskiy >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Best regards, >> Idel Pivnitskiy >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/8d4c1253/attachment-0001.html From matzew at apache.org Tue Apr 7 07:11:19 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Apr 2015 13:11:19 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: On Tue, Apr 7, 2015 at 12:56 PM, Idel Pivnitskiy wrote: > Yes, Swagger can generate doc on the fly, but Swagger use its own > annotations instead of parse JAX-RS annotations and javadoc, like MireDot. > Ok, I think I have not a huge concern against custom annotations, especially due to the wide adoption of Swagger. I guess it's just a very tiny JAR, that contains the annotations, right? (+ the build time tool dependency for processing) > What about licence: Apache Tika, for example, uses pro version of MireDot > > > https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 > Thanks for the example, that's helpful > > > 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : > >> Swagger allows doc on the source as well, right ? Just wondering. >> >> REgarding license, I need to double check on that before... >> >> On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> wrote: >> >>> Matthias, >>> >>> Sure, I will work on it. >>> But I think that it would be better if you request a license [1] on your >>> email and forward it to me. >>> It won't be a problem to use a free version, but pro version has a very >>> cool features, like: >>> >>> - Display javadoc comments for the fields of json payloads and enums >>> - JSON field documentation >>> - Type replacement (custom serialisation, JSON types) >>> >>> Please, request a li >>> >>> [1] http://miredot.com/price/ >>> >>> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >>> >>>> Idel, >>>> >>>> would you mind to create a branch for us, so we can investigate the >>>> MireDot solution? also the build should be working w/ JDK8. >>>> >>>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it does >>>> not really use any fancy annotations (e.g. see [2]) - that's why we picked >>>> it. >>>> >>>> Thanks! >>>> Matthias >>>> >>>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>>> [2] >>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>> >>>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? >>>> wrote: >>>> >>>>> I agree with Idel that DRY approach in Miredot's case seems more >>>>> appealing. >>>>> >>>>> They offer basic docs generation in Free version, but also Pro version >>>>> for open-source projects under conditions that Aerogear meets [1]. >>>>> >>>>> ~ Lukas >>>>> >>>>> [1] http://www.miredot.com/price/ >>>>> >>>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>>> idel.pivnitskiy at gmail.com> napsal: >>>>> >>>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>>> http://www.miredot.com/ >>>>>> >>>>>> With MireDot you do not need to use additional annotations, like @Api: >>>>>> >>>>>> @Path("/pet") >>>>>> @Api(value = "/pet", description = "Operations about pets") >>>>>> >>>>>> >>>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>>> >>>>>> /** >>>>>> * Operations about pets >>>>>> */ >>>>>> @Path("/pet") >>>>>> >>>>>> and generate beautiful and user friendly documentation, like this: >>>>>> http://www.miredot.com/exampledocs/ >>>>>> Swagger example: http://petstore.swagger.io/ >>>>>> >>>>>> And MireDot is free for open source projects! >>>>>> >>>>>> Think about this alternative for Swagger. I'm able to prepare Pull >>>>>> Request for UPS next week. >>>>>> >>>>>> >>>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : >>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>>> wrote: >>>>>>> >>>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>>> >>>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>>> > endpoints, and >>>>>>>> > it's really handy. >>>>>>>> >>>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + >>>>>>>> Swagger annotations. >>>>>>>> In Hawkular we are basically doing the same, but with a different >>>>>>>> annotation processor. >>>>>>>> >>>>>>> >>>>>>> +1000 >>>>>>> >>>>>>> we are, atm, doing similar: >>>>>>> source >>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>>>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>>>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>>> result: >>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>>>>> rest/sender/index.html#POST >>>>>>> >>>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to change >>>>>>> here ;-) >>>>>>> So, I am all for using Swagger annotations on the code to generate >>>>>>> the HTML docs :-) >>>>>>> >>>>>>> Greetings, >>>>>>> Matthias >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> I personally think the best is really to have the annotations in the >>>>>>>> source and not trying >>>>>>>> to update a separate .yml file, as the latter usually is much easier >>>>>>>> forgotten. >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> Idel Pivnitskiy >>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>> Twitter: @idelpivnitskiy >>>>>> GitHub: @idelpivnitskiy >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Idel Pivnitskiy >>> E-mail: Idel.Pivnitskiy at gmail.com >>> Twitter: @idelpivnitskiy >>> GitHub: @idelpivnitskiy >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/091bab39/attachment.html From idel.pivnitskiy at gmail.com Tue Apr 7 07:42:18 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 7 Apr 2015 14:42:18 +0300 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: IMO, custom annotations force you to duplicate code and documentation. Take a look at a more detailed example: @POST @Path("/{petId}") @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) @ApiOperation(value = "Updates a pet in the store with form data", consumes = MediaType.APPLICATION_FORM_URLENCODED) @ApiResponses(value = { @ApiResponse(code = 405, message = "Invalid input")}) public Response updatePetWithForm ( @ApiParam(value = "ID of pet that needs to be updated", required = true)@PathParam("petId") String petId, @ApiParam(value = "Updated name of the pet", required = false)@FormParam("name") String name, @ApiParam(value = "Updated status of the pet", required = false)@FormParam("status") String status) { System.out.println(name); System.out.println(status); return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); } It is much more simple with MireDot (also because javadoc could be generated automatically by IDE): /** * Updates a pet in the store with form data. * * @param petId ID of pet that needs to be updated * @param name Updated name of the pet * @param status Updated status of the pet */ @POST @Path("/{petId}") @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) public Response updatePetWithForm (@PathParam("petId") String petId, @FormParam("name") String name, @FormParam("status") String status) { System.out.println(name); System.out.println(status); return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); } Really, I don't know why Swagger is so popular :) 2015-04-07 14:11 GMT+03:00 Matthias Wessendorf : > > > On Tue, Apr 7, 2015 at 12:56 PM, Idel Pivnitskiy < > idel.pivnitskiy at gmail.com> wrote: > >> Yes, Swagger can generate doc on the fly, but Swagger use its own >> annotations instead of parse JAX-RS annotations and javadoc, like MireDot. >> > > Ok, I think I have not a huge concern against custom annotations, > especially due to the wide adoption of Swagger. > I guess it's just a very tiny JAR, that contains the annotations, right? > > (+ the build time tool dependency for processing) > > >> What about licence: Apache Tika, for example, uses pro version of MireDot >> >> >> https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 >> > > Thanks for the example, that's helpful > > >> >> >> 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : >> >>> Swagger allows doc on the source as well, right ? Just wondering. >>> >>> REgarding license, I need to double check on that before... >>> >>> On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < >>> idel.pivnitskiy at gmail.com> wrote: >>> >>>> Matthias, >>>> >>>> Sure, I will work on it. >>>> But I think that it would be better if you request a license [1] on >>>> your email and forward it to me. >>>> It won't be a problem to use a free version, but pro version has a very >>>> cool features, like: >>>> >>>> - Display javadoc comments for the fields of json payloads and enums >>>> - JSON field documentation >>>> - Type replacement (custom serialisation, JSON types) >>>> >>>> Please, request a li >>>> >>>> [1] http://miredot.com/price/ >>>> >>>> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >>>> >>>>> Idel, >>>>> >>>>> would you mind to create a branch for us, so we can investigate the >>>>> MireDot solution? also the build should be working w/ JDK8. >>>>> >>>>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it does >>>>> not really use any fancy annotations (e.g. see [2]) - that's why we picked >>>>> it. >>>>> >>>>> Thanks! >>>>> Matthias >>>>> >>>>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>>>> [2] >>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>> >>>>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? >>>>> wrote: >>>>> >>>>>> I agree with Idel that DRY approach in Miredot's case seems more >>>>>> appealing. >>>>>> >>>>>> They offer basic docs generation in Free version, but also Pro >>>>>> version for open-source projects under conditions that Aerogear meets [1]. >>>>>> >>>>>> ~ Lukas >>>>>> >>>>>> [1] http://www.miredot.com/price/ >>>>>> >>>>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>>>> idel.pivnitskiy at gmail.com> napsal: >>>>>> >>>>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>>>> http://www.miredot.com/ >>>>>>> >>>>>>> With MireDot you do not need to use additional annotations, like >>>>>>> @Api: >>>>>>> >>>>>>> @Path("/pet") >>>>>>> @Api(value = "/pet", description = "Operations about pets") >>>>>>> >>>>>>> >>>>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>>>> >>>>>>> /** >>>>>>> * Operations about pets >>>>>>> */ >>>>>>> @Path("/pet") >>>>>>> >>>>>>> and generate beautiful and user friendly documentation, like this: >>>>>>> http://www.miredot.com/exampledocs/ >>>>>>> Swagger example: http://petstore.swagger.io/ >>>>>>> >>>>>>> And MireDot is free for open source projects! >>>>>>> >>>>>>> Think about this alternative for Swagger. I'm able to prepare Pull >>>>>>> Request for UPS next week. >>>>>>> >>>>>>> >>>>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>>>> wrote: >>>>>>>> >>>>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>>>> >>>>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>>>> > endpoints, and >>>>>>>>> > it's really handy. >>>>>>>>> >>>>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS + >>>>>>>>> Swagger annotations. >>>>>>>>> In Hawkular we are basically doing the same, but with a different >>>>>>>>> annotation processor. >>>>>>>>> >>>>>>>> >>>>>>>> +1000 >>>>>>>> >>>>>>>> we are, atm, doing similar: >>>>>>>> source >>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>>>>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>>>>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint >>>>>>>> .java#L99-L102 >>>>>>>> result: >>>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>>>>>> rest/sender/index.html#POST >>>>>>>> >>>>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to >>>>>>>> change here ;-) >>>>>>>> So, I am all for using Swagger annotations on the code to generate >>>>>>>> the HTML docs :-) >>>>>>>> >>>>>>>> Greetings, >>>>>>>> Matthias >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> I personally think the best is really to have the annotations in >>>>>>>>> the >>>>>>>>> source and not trying >>>>>>>>> to update a separate .yml file, as the latter usually is much >>>>>>>>> easier >>>>>>>>> forgotten. >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at 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 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Idel Pivnitskiy >>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>> Twitter: @idelpivnitskiy >>>>>>> GitHub: @idelpivnitskiy >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Idel Pivnitskiy >>>> E-mail: Idel.Pivnitskiy at gmail.com >>>> Twitter: @idelpivnitskiy >>>> GitHub: @idelpivnitskiy >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/ff1d2db6/attachment-0001.html From matzew at apache.org Tue Apr 7 07:55:40 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Apr 2015 13:55:40 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: On Tue, Apr 7, 2015 at 1:42 PM, Idel Pivnitskiy wrote: > IMO, custom annotations force you to duplicate code and documentation. > Take a look at a more detailed example: > > @POST > @Path("/{petId}") > @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) > @ApiOperation(value = "Updates a pet in the store with form data", > consumes = MediaType.APPLICATION_FORM_URLENCODED) > @ApiResponses(value = { > @ApiResponse(code = 405, message = "Invalid input")}) > public Response updatePetWithForm ( > @ApiParam(value = "ID of pet that needs to be updated", required = true)@PathParam("petId") String petId, > @ApiParam(value = "Updated name of the pet", required = false)@FormParam("name") String name, > @ApiParam(value = "Updated status of the pet", required = false)@FormParam("status") String status) { > System.out.println(name); > System.out.println(status); > return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); > } > > > It is much more simple with MireDot (also because javadoc could be > generated automatically by IDE): > > /** > * Updates a pet in the store with form data. > * > * @param petId ID of pet that needs to be updated > * @param name Updated name of the pet > * @param status Updated status of the pet > */ > @POST > @Path("/{petId}") > @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) > public Response updatePetWithForm (@PathParam("petId") String petId, > @FormParam("name") String name, > @FormParam("status") String status) { > System.out.println(name); > System.out.println(status); > return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); > } > > Really, I don't know why Swagger is so popular :) > That's quite a difference, and less verbose and less of duplication (DRY). So I'd say, let's try Miredot :-) Thanks for the valuable info, Idel! -Matthias > > 2015-04-07 14:11 GMT+03:00 Matthias Wessendorf : > >> >> >> On Tue, Apr 7, 2015 at 12:56 PM, Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> wrote: >> >>> Yes, Swagger can generate doc on the fly, but Swagger use its own >>> annotations instead of parse JAX-RS annotations and javadoc, like MireDot. >>> >> >> Ok, I think I have not a huge concern against custom annotations, >> especially due to the wide adoption of Swagger. >> I guess it's just a very tiny JAR, that contains the annotations, right? >> >> (+ the build time tool dependency for processing) >> >> >>> What about licence: Apache Tika, for example, uses pro version of MireDot >>> >>> >>> https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 >>> >> >> Thanks for the example, that's helpful >> >> >>> >>> >>> 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : >>> >>>> Swagger allows doc on the source as well, right ? Just wondering. >>>> >>>> REgarding license, I need to double check on that before... >>>> >>>> On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < >>>> idel.pivnitskiy at gmail.com> wrote: >>>> >>>>> Matthias, >>>>> >>>>> Sure, I will work on it. >>>>> But I think that it would be better if you request a license [1] on >>>>> your email and forward it to me. >>>>> It won't be a problem to use a free version, but pro version has a >>>>> very cool features, like: >>>>> >>>>> - Display javadoc comments for the fields of json payloads and >>>>> enums >>>>> - JSON field documentation >>>>> - Type replacement (custom serialisation, JSON types) >>>>> >>>>> Please, request a li >>>>> >>>>> [1] http://miredot.com/price/ >>>>> >>>>> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >>>>> >>>>>> Idel, >>>>>> >>>>>> would you mind to create a branch for us, so we can investigate the >>>>>> MireDot solution? also the build should be working w/ JDK8. >>>>>> >>>>>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it >>>>>> does not really use any fancy annotations (e.g. see [2]) - that's why we >>>>>> picked it. >>>>>> >>>>>> Thanks! >>>>>> Matthias >>>>>> >>>>>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>>>>> [2] >>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>> >>>>>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? >>>>>> wrote: >>>>>> >>>>>>> I agree with Idel that DRY approach in Miredot's case seems more >>>>>>> appealing. >>>>>>> >>>>>>> They offer basic docs generation in Free version, but also Pro >>>>>>> version for open-source projects under conditions that Aerogear meets [1]. >>>>>>> >>>>>>> ~ Lukas >>>>>>> >>>>>>> [1] http://www.miredot.com/price/ >>>>>>> >>>>>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>>>>> idel.pivnitskiy at gmail.com> napsal: >>>>>>> >>>>>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>>>>> http://www.miredot.com/ >>>>>>>> >>>>>>>> With MireDot you do not need to use additional annotations, like >>>>>>>> @Api: >>>>>>>> >>>>>>>> @Path("/pet") >>>>>>>> @Api(value = "/pet", description = "Operations about pets") >>>>>>>> >>>>>>>> >>>>>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>>>>> >>>>>>>> /** >>>>>>>> * Operations about pets >>>>>>>> */ >>>>>>>> @Path("/pet") >>>>>>>> >>>>>>>> and generate beautiful and user friendly documentation, like this: >>>>>>>> http://www.miredot.com/exampledocs/ >>>>>>>> Swagger example: http://petstore.swagger.io/ >>>>>>>> >>>>>>>> And MireDot is free for open source projects! >>>>>>>> >>>>>>>> Think about this alternative for Swagger. I'm able to prepare Pull >>>>>>>> Request for UPS next week. >>>>>>>> >>>>>>>> >>>>>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>>>>> >>>>>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>>>>> > endpoints, and >>>>>>>>>> > it's really handy. >>>>>>>>>> >>>>>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from JAX-RS >>>>>>>>>> + >>>>>>>>>> Swagger annotations. >>>>>>>>>> In Hawkular we are basically doing the same, but with a different >>>>>>>>>> annotation processor. >>>>>>>>>> >>>>>>>>> >>>>>>>>> +1000 >>>>>>>>> >>>>>>>>> we are, atm, doing similar: >>>>>>>>> source >>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>>>>>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>>>>>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint >>>>>>>>> .java#L99-L102 >>>>>>>>> result: >>>>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>>>>>>> rest/sender/index.html#POST >>>>>>>>> >>>>>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to >>>>>>>>> change here ;-) >>>>>>>>> So, I am all for using Swagger annotations on the code to generate >>>>>>>>> the HTML docs :-) >>>>>>>>> >>>>>>>>> Greetings, >>>>>>>>> Matthias >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> I personally think the best is really to have the annotations in >>>>>>>>>> the >>>>>>>>>> source and not trying >>>>>>>>>> to update a separate .yml file, as the latter usually is much >>>>>>>>>> easier >>>>>>>>>> forgotten. >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at 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 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Best regards, >>>>>>>> Idel Pivnitskiy >>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>> Twitter: @idelpivnitskiy >>>>>>>> GitHub: @idelpivnitskiy >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Idel Pivnitskiy >>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>> Twitter: @idelpivnitskiy >>>>> GitHub: @idelpivnitskiy >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/622f0cd4/attachment-0001.html From idel.pivnitskiy at gmail.com Tue Apr 7 07:57:13 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 7 Apr 2015 14:57:13 +0300 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: Ok, so I will wait a license key from you. 2015-04-07 14:55 GMT+03:00 Matthias Wessendorf : > > > On Tue, Apr 7, 2015 at 1:42 PM, Idel Pivnitskiy > wrote: > >> IMO, custom annotations force you to duplicate code and documentation. >> Take a look at a more detailed example: >> >> @POST >> @Path("/{petId}") >> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >> @ApiOperation(value = "Updates a pet in the store with form data", >> consumes = MediaType.APPLICATION_FORM_URLENCODED) >> @ApiResponses(value = { >> @ApiResponse(code = 405, message = "Invalid input")}) >> public Response updatePetWithForm ( >> @ApiParam(value = "ID of pet that needs to be updated", required = true)@PathParam("petId") String petId, >> @ApiParam(value = "Updated name of the pet", required = false)@FormParam("name") String name, >> @ApiParam(value = "Updated status of the pet", required = false)@FormParam("status") String status) { >> System.out.println(name); >> System.out.println(status); >> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >> } >> >> >> It is much more simple with MireDot (also because javadoc could be >> generated automatically by IDE): >> >> /** >> * Updates a pet in the store with form data. >> * >> * @param petId ID of pet that needs to be updated >> * @param name Updated name of the pet >> * @param status Updated status of the pet >> */ >> @POST >> @Path("/{petId}") >> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >> public Response updatePetWithForm (@PathParam("petId") String petId, >> @FormParam("name") String name, >> @FormParam("status") String status) { >> System.out.println(name); >> System.out.println(status); >> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >> } >> >> Really, I don't know why Swagger is so popular :) >> > > That's quite a difference, and less verbose and less of duplication (DRY). > So I'd say, let's try Miredot :-) > > Thanks for the valuable info, Idel! > > -Matthias > > >> >> 2015-04-07 14:11 GMT+03:00 Matthias Wessendorf : >> >>> >>> >>> On Tue, Apr 7, 2015 at 12:56 PM, Idel Pivnitskiy < >>> idel.pivnitskiy at gmail.com> wrote: >>> >>>> Yes, Swagger can generate doc on the fly, but Swagger use its own >>>> annotations instead of parse JAX-RS annotations and javadoc, like MireDot. >>>> >>> >>> Ok, I think I have not a huge concern against custom annotations, >>> especially due to the wide adoption of Swagger. >>> I guess it's just a very tiny JAR, that contains the annotations, right? >>> >>> (+ the build time tool dependency for processing) >>> >>> >>>> What about licence: Apache Tika, for example, uses pro version of >>>> MireDot >>>> >>>> >>>> https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 >>>> >>> >>> Thanks for the example, that's helpful >>> >>> >>>> >>>> >>>> 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : >>>> >>>>> Swagger allows doc on the source as well, right ? Just wondering. >>>>> >>>>> REgarding license, I need to double check on that before... >>>>> >>>>> On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < >>>>> idel.pivnitskiy at gmail.com> wrote: >>>>> >>>>>> Matthias, >>>>>> >>>>>> Sure, I will work on it. >>>>>> But I think that it would be better if you request a license [1] on >>>>>> your email and forward it to me. >>>>>> It won't be a problem to use a free version, but pro version has a >>>>>> very cool features, like: >>>>>> >>>>>> - Display javadoc comments for the fields of json payloads and >>>>>> enums >>>>>> - JSON field documentation >>>>>> - Type replacement (custom serialisation, JSON types) >>>>>> >>>>>> Please, request a li >>>>>> >>>>>> [1] http://miredot.com/price/ >>>>>> >>>>>> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >>>>>> >>>>>>> Idel, >>>>>>> >>>>>>> would you mind to create a branch for us, so we can investigate the >>>>>>> MireDot solution? also the build should be working w/ JDK8. >>>>>>> >>>>>>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it >>>>>>> does not really use any fancy annotations (e.g. see [2]) - that's why we >>>>>>> picked it. >>>>>>> >>>>>>> Thanks! >>>>>>> Matthias >>>>>>> >>>>>>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>>>>>> [2] >>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>>> >>>>>>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? >>>>>>> wrote: >>>>>>> >>>>>>>> I agree with Idel that DRY approach in Miredot's case seems more >>>>>>>> appealing. >>>>>>>> >>>>>>>> They offer basic docs generation in Free version, but also Pro >>>>>>>> version for open-source projects under conditions that Aerogear meets [1]. >>>>>>>> >>>>>>>> ~ Lukas >>>>>>>> >>>>>>>> [1] http://www.miredot.com/price/ >>>>>>>> >>>>>>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>>>>>> idel.pivnitskiy at gmail.com> napsal: >>>>>>>> >>>>>>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>>>>>> http://www.miredot.com/ >>>>>>>>> >>>>>>>>> With MireDot you do not need to use additional annotations, like >>>>>>>>> @Api: >>>>>>>>> >>>>>>>>> @Path("/pet") >>>>>>>>> @Api(value = "/pet", description = "Operations about pets") >>>>>>>>> >>>>>>>>> >>>>>>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>>>>>> >>>>>>>>> /** >>>>>>>>> * Operations about pets >>>>>>>>> */ >>>>>>>>> @Path("/pet") >>>>>>>>> >>>>>>>>> and generate beautiful and user friendly documentation, like this: >>>>>>>>> http://www.miredot.com/exampledocs/ >>>>>>>>> Swagger example: http://petstore.swagger.io/ >>>>>>>>> >>>>>>>>> And MireDot is free for open source projects! >>>>>>>>> >>>>>>>>> Think about this alternative for Swagger. I'm able to prepare Pull >>>>>>>>> Request for UPS next week. >>>>>>>>> >>>>>>>>> >>>>>>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf : >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>>>>>> >>>>>>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>>>>>> > endpoints, and >>>>>>>>>>> > it's really handy. >>>>>>>>>>> >>>>>>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from >>>>>>>>>>> JAX-RS + >>>>>>>>>>> Swagger annotations. >>>>>>>>>>> In Hawkular we are basically doing the same, but with a different >>>>>>>>>>> annotation processor. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> +1000 >>>>>>>>>> >>>>>>>>>> we are, atm, doing similar: >>>>>>>>>> source >>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>>>>>>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>>>>>>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint >>>>>>>>>> .java#L99-L102 >>>>>>>>>> result: >>>>>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>>>>>>>> rest/sender/index.html#POST >>>>>>>>>> >>>>>>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to >>>>>>>>>> change here ;-) >>>>>>>>>> So, I am all for using Swagger annotations on the code to >>>>>>>>>> generate the HTML docs :-) >>>>>>>>>> >>>>>>>>>> Greetings, >>>>>>>>>> Matthias >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I personally think the best is really to have the annotations in >>>>>>>>>>> the >>>>>>>>>>> source and not trying >>>>>>>>>>> to update a separate .yml file, as the latter usually is much >>>>>>>>>>> easier >>>>>>>>>>> forgotten. >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at 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 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Best regards, >>>>>>>>> Idel Pivnitskiy >>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>> Twitter: @idelpivnitskiy >>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> Idel Pivnitskiy >>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>> Twitter: @idelpivnitskiy >>>>>> GitHub: @idelpivnitskiy >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Best regards, Idel Pivnitskiy E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/2165c39a/attachment-0001.html From idel.pivnitskiy at gmail.com Tue Apr 7 07:59:40 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 7 Apr 2015 14:59:40 +0300 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: We may try to start with free version (because it will be faster) and request a pro version later. 2015-04-07 14:57 GMT+03:00 Idel Pivnitskiy : > Ok, so I will wait a license key from you. > > 2015-04-07 14:55 GMT+03:00 Matthias Wessendorf : > >> >> >> On Tue, Apr 7, 2015 at 1:42 PM, Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> wrote: >> >>> IMO, custom annotations force you to duplicate code and documentation. >>> Take a look at a more detailed example: >>> >>> @POST >>> @Path("/{petId}") >>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>> @ApiOperation(value = "Updates a pet in the store with form data", >>> consumes = MediaType.APPLICATION_FORM_URLENCODED) >>> @ApiResponses(value = { >>> @ApiResponse(code = 405, message = "Invalid input")}) >>> public Response updatePetWithForm ( >>> @ApiParam(value = "ID of pet that needs to be updated", required = true)@PathParam("petId") String petId, >>> @ApiParam(value = "Updated name of the pet", required = false)@FormParam("name") String name, >>> @ApiParam(value = "Updated status of the pet", required = false)@FormParam("status") String status) { >>> System.out.println(name); >>> System.out.println(status); >>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>> } >>> >>> >>> It is much more simple with MireDot (also because javadoc could be >>> generated automatically by IDE): >>> >>> /** >>> * Updates a pet in the store with form data. >>> * >>> * @param petId ID of pet that needs to be updated >>> * @param name Updated name of the pet >>> * @param status Updated status of the pet >>> */ >>> @POST >>> @Path("/{petId}") >>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>> public Response updatePetWithForm (@PathParam("petId") String petId, >>> @FormParam("name") String name, >>> @FormParam("status") String status) { >>> System.out.println(name); >>> System.out.println(status); >>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>> } >>> >>> Really, I don't know why Swagger is so popular :) >>> >> >> That's quite a difference, and less verbose and less of duplication >> (DRY). So I'd say, let's try Miredot :-) >> >> Thanks for the valuable info, Idel! >> >> -Matthias >> >> >>> >>> 2015-04-07 14:11 GMT+03:00 Matthias Wessendorf : >>> >>>> >>>> >>>> On Tue, Apr 7, 2015 at 12:56 PM, Idel Pivnitskiy < >>>> idel.pivnitskiy at gmail.com> wrote: >>>> >>>>> Yes, Swagger can generate doc on the fly, but Swagger use its own >>>>> annotations instead of parse JAX-RS annotations and javadoc, like MireDot. >>>>> >>>> >>>> Ok, I think I have not a huge concern against custom annotations, >>>> especially due to the wide adoption of Swagger. >>>> I guess it's just a very tiny JAR, that contains the annotations, right? >>>> >>>> (+ the build time tool dependency for processing) >>>> >>>> >>>>> What about licence: Apache Tika, for example, uses pro version of >>>>> MireDot >>>>> >>>>> >>>>> https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 >>>>> >>>> >>>> Thanks for the example, that's helpful >>>> >>>> >>>>> >>>>> >>>>> 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : >>>>> >>>>>> Swagger allows doc on the source as well, right ? Just wondering. >>>>>> >>>>>> REgarding license, I need to double check on that before... >>>>>> >>>>>> On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < >>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>> >>>>>>> Matthias, >>>>>>> >>>>>>> Sure, I will work on it. >>>>>>> But I think that it would be better if you request a license [1] on >>>>>>> your email and forward it to me. >>>>>>> It won't be a problem to use a free version, but pro version has a >>>>>>> very cool features, like: >>>>>>> >>>>>>> - Display javadoc comments for the fields of json payloads and >>>>>>> enums >>>>>>> - JSON field documentation >>>>>>> - Type replacement (custom serialisation, JSON types) >>>>>>> >>>>>>> Please, request a li >>>>>>> >>>>>>> [1] http://miredot.com/price/ >>>>>>> >>>>>>> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >>>>>>> >>>>>>>> Idel, >>>>>>>> >>>>>>>> would you mind to create a branch for us, so we can investigate the >>>>>>>> MireDot solution? also the build should be working w/ JDK8. >>>>>>>> >>>>>>>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it >>>>>>>> does not really use any fancy annotations (e.g. see [2]) - that's why we >>>>>>>> picked it. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> Matthias >>>>>>>> >>>>>>>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>>>>>>> [2] >>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>>>> >>>>>>>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I agree with Idel that DRY approach in Miredot's case seems more >>>>>>>>> appealing. >>>>>>>>> >>>>>>>>> They offer basic docs generation in Free version, but also Pro >>>>>>>>> version for open-source projects under conditions that Aerogear meets [1]. >>>>>>>>> >>>>>>>>> ~ Lukas >>>>>>>>> >>>>>>>>> [1] http://www.miredot.com/price/ >>>>>>>>> >>>>>>>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>>>>>>> idel.pivnitskiy at gmail.com> napsal: >>>>>>>>> >>>>>>>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>>>>>>> http://www.miredot.com/ >>>>>>>>>> >>>>>>>>>> With MireDot you do not need to use additional annotations, like >>>>>>>>>> @Api: >>>>>>>>>> >>>>>>>>>> @Path("/pet") >>>>>>>>>> @Api(value = "/pet", description = "Operations about pets") >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>>>>>>> >>>>>>>>>> /** >>>>>>>>>> * Operations about pets >>>>>>>>>> */ >>>>>>>>>> @Path("/pet") >>>>>>>>>> >>>>>>>>>> and generate beautiful and user friendly documentation, like >>>>>>>>>> this: http://www.miredot.com/exampledocs/ >>>>>>>>>> Swagger example: http://petstore.swagger.io/ >>>>>>>>>> >>>>>>>>>> And MireDot is free for open source projects! >>>>>>>>>> >>>>>>>>>> Think about this alternative for Swagger. I'm able to prepare >>>>>>>>>> Pull Request for UPS next week. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf >>>>>>>>>> : >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>>>>>>> >>>>>>>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>>>>>>> > endpoints, and >>>>>>>>>>>> > it's really handy. >>>>>>>>>>>> >>>>>>>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from >>>>>>>>>>>> JAX-RS + >>>>>>>>>>>> Swagger annotations. >>>>>>>>>>>> In Hawkular we are basically doing the same, but with a >>>>>>>>>>>> different >>>>>>>>>>>> annotation processor. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> +1000 >>>>>>>>>>> >>>>>>>>>>> we are, atm, doing similar: >>>>>>>>>>> source >>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>>>>>>>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>>>>>>>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint >>>>>>>>>>> .java#L99-L102 >>>>>>>>>>> result: >>>>>>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>>>>>>>>> rest/sender/index.html#POST >>>>>>>>>>> >>>>>>>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to >>>>>>>>>>> change here ;-) >>>>>>>>>>> So, I am all for using Swagger annotations on the code to >>>>>>>>>>> generate the HTML docs :-) >>>>>>>>>>> >>>>>>>>>>> Greetings, >>>>>>>>>>> Matthias >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> I personally think the best is really to have the annotations >>>>>>>>>>>> in the >>>>>>>>>>>> source and not trying >>>>>>>>>>>> to update a separate .yml file, as the latter usually is much >>>>>>>>>>>> easier >>>>>>>>>>>> forgotten. >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at 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 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Best regards, >>>>>>>>>> Idel Pivnitskiy >>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>> Twitter: @idelpivnitskiy >>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at 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 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Idel Pivnitskiy >>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>> Twitter: @idelpivnitskiy >>>>>>> GitHub: @idelpivnitskiy >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Best regards, > Idel Pivnitskiy > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > -- Best regards, Idel Pivnitskiy E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/a6ae39dd/attachment-0001.html From matzew at apache.org Tue Apr 7 08:16:30 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Apr 2015 14:16:30 +0200 Subject: [aerogear-dev] do we want swagger for REST endpoint documentation? In-Reply-To: References: <1428079992224-11356.post@n5.nabble.com> <6FC8E75A-DCD9-477B-A674-4EBF733F36FC@redhat.com> Message-ID: sounds like a good plan On Tue, Apr 7, 2015 at 1:59 PM, Idel Pivnitskiy wrote: > We may try to start with free version (because it will be faster) and > request a pro version later. > > > 2015-04-07 14:57 GMT+03:00 Idel Pivnitskiy : > >> Ok, so I will wait a license key from you. >> >> 2015-04-07 14:55 GMT+03:00 Matthias Wessendorf : >> >>> >>> >>> On Tue, Apr 7, 2015 at 1:42 PM, Idel Pivnitskiy < >>> idel.pivnitskiy at gmail.com> wrote: >>> >>>> IMO, custom annotations force you to duplicate code and documentation. >>>> Take a look at a more detailed example: >>>> >>>> @POST >>>> @Path("/{petId}") >>>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>>> @ApiOperation(value = "Updates a pet in the store with form data", >>>> consumes = MediaType.APPLICATION_FORM_URLENCODED) >>>> @ApiResponses(value = { >>>> @ApiResponse(code = 405, message = "Invalid input")}) >>>> public Response updatePetWithForm ( >>>> @ApiParam(value = "ID of pet that needs to be updated", required = true)@PathParam("petId") String petId, >>>> @ApiParam(value = "Updated name of the pet", required = false)@FormParam("name") String name, >>>> @ApiParam(value = "Updated status of the pet", required = false)@FormParam("status") String status) { >>>> System.out.println(name); >>>> System.out.println(status); >>>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>>> } >>>> >>>> >>>> It is much more simple with MireDot (also because javadoc could be >>>> generated automatically by IDE): >>>> >>>> /** >>>> * Updates a pet in the store with form data. >>>> * >>>> * @param petId ID of pet that needs to be updated >>>> * @param name Updated name of the pet >>>> * @param status Updated status of the pet >>>> */ >>>> @POST >>>> @Path("/{petId}") >>>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>>> public Response updatePetWithForm (@PathParam("petId") String petId, >>>> @FormParam("name") String name, >>>> @FormParam("status") String status) { >>>> System.out.println(name); >>>> System.out.println(status); >>>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>>> } >>>> >>>> Really, I don't know why Swagger is so popular :) >>>> >>> >>> That's quite a difference, and less verbose and less of duplication >>> (DRY). So I'd say, let's try Miredot :-) >>> >>> Thanks for the valuable info, Idel! >>> >>> -Matthias >>> >>> >>>> >>>> 2015-04-07 14:11 GMT+03:00 Matthias Wessendorf : >>>> >>>>> >>>>> >>>>> On Tue, Apr 7, 2015 at 12:56 PM, Idel Pivnitskiy < >>>>> idel.pivnitskiy at gmail.com> wrote: >>>>> >>>>>> Yes, Swagger can generate doc on the fly, but Swagger use its own >>>>>> annotations instead of parse JAX-RS annotations and javadoc, like MireDot. >>>>>> >>>>> >>>>> Ok, I think I have not a huge concern against custom annotations, >>>>> especially due to the wide adoption of Swagger. >>>>> I guess it's just a very tiny JAR, that contains the annotations, >>>>> right? >>>>> >>>>> (+ the build time tool dependency for processing) >>>>> >>>>> >>>>>> What about licence: Apache Tika, for example, uses pro version of >>>>>> MireDot >>>>>> >>>>>> >>>>>> https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 >>>>>> >>>>> >>>>> Thanks for the example, that's helpful >>>>> >>>>> >>>>>> >>>>>> >>>>>> 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : >>>>>> >>>>>>> Swagger allows doc on the source as well, right ? Just wondering. >>>>>>> >>>>>>> REgarding license, I need to double check on that before... >>>>>>> >>>>>>> On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < >>>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>>> >>>>>>>> Matthias, >>>>>>>> >>>>>>>> Sure, I will work on it. >>>>>>>> But I think that it would be better if you request a license [1] on >>>>>>>> your email and forward it to me. >>>>>>>> It won't be a problem to use a free version, but pro version has a >>>>>>>> very cool features, like: >>>>>>>> >>>>>>>> - Display javadoc comments for the fields of json payloads and >>>>>>>> enums >>>>>>>> - JSON field documentation >>>>>>>> - Type replacement (custom serialisation, JSON types) >>>>>>>> >>>>>>>> Please, request a li >>>>>>>> >>>>>>>> [1] http://miredot.com/price/ >>>>>>>> >>>>>>>> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >>>>>>>> >>>>>>>>> Idel, >>>>>>>>> >>>>>>>>> would you mind to create a branch for us, so we can investigate >>>>>>>>> the MireDot solution? also the build should be working w/ JDK8. >>>>>>>>> >>>>>>>>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it >>>>>>>>> does not really use any fancy annotations (e.g. see [2]) - that's why we >>>>>>>>> picked it. >>>>>>>>> >>>>>>>>> Thanks! >>>>>>>>> Matthias >>>>>>>>> >>>>>>>>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>>>>>>>> [2] >>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>>>>> >>>>>>>>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I agree with Idel that DRY approach in Miredot's case seems more >>>>>>>>>> appealing. >>>>>>>>>> >>>>>>>>>> They offer basic docs generation in Free version, but also Pro >>>>>>>>>> version for open-source projects under conditions that Aerogear meets [1]. >>>>>>>>>> >>>>>>>>>> ~ Lukas >>>>>>>>>> >>>>>>>>>> [1] http://www.miredot.com/price/ >>>>>>>>>> >>>>>>>>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>>>>>>>> idel.pivnitskiy at gmail.com> napsal: >>>>>>>>>> >>>>>>>>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>>>>>>>> http://www.miredot.com/ >>>>>>>>>>> >>>>>>>>>>> With MireDot you do not need to use additional annotations, like >>>>>>>>>>> @Api: >>>>>>>>>>> >>>>>>>>>>> @Path("/pet") >>>>>>>>>>> @Api(value = "/pet", description = "Operations about pets") >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>>>>>>>> >>>>>>>>>>> /** >>>>>>>>>>> * Operations about pets >>>>>>>>>>> */ >>>>>>>>>>> @Path("/pet") >>>>>>>>>>> >>>>>>>>>>> and generate beautiful and user friendly documentation, like >>>>>>>>>>> this: http://www.miredot.com/exampledocs/ >>>>>>>>>>> Swagger example: http://petstore.swagger.io/ >>>>>>>>>>> >>>>>>>>>>> And MireDot is free for open source projects! >>>>>>>>>>> >>>>>>>>>>> Think about this alternative for Swagger. I'm able to prepare >>>>>>>>>>> Pull Request for UPS next week. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf >>>>>>>>>> >: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>>>>>>> > wrote: >>>>>>>>>>>> >>>>>>>>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>>>>>>>> > endpoints, and >>>>>>>>>>>>> > it's really handy. >>>>>>>>>>>>> >>>>>>>>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from >>>>>>>>>>>>> JAX-RS + >>>>>>>>>>>>> Swagger annotations. >>>>>>>>>>>>> In Hawkular we are basically doing the same, but with a >>>>>>>>>>>>> different >>>>>>>>>>>>> annotation processor. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> +1000 >>>>>>>>>>>> >>>>>>>>>>>> we are, atm, doing similar: >>>>>>>>>>>> source >>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>>>>>>>>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>>>>>>>>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint >>>>>>>>>>>> .java#L99-L102 >>>>>>>>>>>> result: >>>>>>>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>>>>>>>>>> rest/sender/index.html#POST >>>>>>>>>>>> >>>>>>>>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to >>>>>>>>>>>> change here ;-) >>>>>>>>>>>> So, I am all for using Swagger annotations on the code to >>>>>>>>>>>> generate the HTML docs :-) >>>>>>>>>>>> >>>>>>>>>>>> Greetings, >>>>>>>>>>>> Matthias >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> I personally think the best is really to have the annotations >>>>>>>>>>>>> in the >>>>>>>>>>>>> source and not trying >>>>>>>>>>>>> to update a separate .yml file, as the latter usually is much >>>>>>>>>>>>> easier >>>>>>>>>>>>> forgotten. >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at 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 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Best regards, >>>>>>>>>>> Idel Pivnitskiy >>>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>>> Twitter: @idelpivnitskiy >>>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at 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 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Best regards, >>>>>>>> Idel Pivnitskiy >>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>> Twitter: @idelpivnitskiy >>>>>>>> GitHub: @idelpivnitskiy >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Best regards, >> Idel Pivnitskiy >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> > > > > -- > Best regards, > Idel Pivnitskiy > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/465fd358/attachment-0001.html From cvasilak at gmail.com Tue Apr 7 10:05:21 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Tue, 7 Apr 2015 17:05:21 +0300 Subject: [aerogear-dev] Team Meeting In-Reply-To: References: Message-ID: fyi, meeting minutes: Meeting ended Tue Apr 7 14:03:34 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-07-14.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-07-14.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-07-14.00.log.html On Mon, Apr 6, 2015 at 3:42 PM, Christos Vasilakis wrote: > Hi all, > > since some of our member's are currently on Easter holiday, we decided to > pause our regular meeting for today until tomorrow same time. > > Agenda is here: > http://oksoclap.com/p/aerogear-team-mgt-04.07.2015 > > Thanks, > Christos > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/5cbca417/attachment.html From agalante at redhat.com Tue Apr 7 12:28:02 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 7 Apr 2015 13:28:02 -0300 Subject: [aerogear-dev] Quick survey Message-ID: This is off topic: The patternfly team is having a booth at deviation, and apart from the usual shirts and stickers we want to give away a bigger item (or a bunch of them). We came up with a list, can you help us decide: https://www.surveymonkey.com/s/2KVZNQL Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150407/64526356/attachment.html From agalante at redhat.com Wed Apr 8 08:12:32 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 8 Apr 2015 09:12:32 -0300 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: Hi, With the new data we have I've compared sent vs open messages on a chart for each App: https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html (the x axis should be dates) I am wondering if we can generate a ratio that's useful for a marketing person and show a benchmark comparing with other UPS users to know if the users campaign is successful or not. Something like: open/sent or device/open I believe that to show the first and last time a message was open is not very useful. Maybe I am wrong, but, If we want to show an over time chart for each notification we should collect periodical data, for example # of open messages per hour to generate a linear graph that represents a day. What do you think? On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc wrote: > > > Envoy? de mon iPhone > > Le 30 mars 2015 ? 21:31, Daniel Passos a ?crit : > > On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc > wrote: > >> Folks ! >> >> For AGPUSH-969[1] and to kick off the discussions, I started a small POC >> mainly focused on the backend. To sum up quickly : we want to know how many >> installations/users has opened the application after that a Push >> Notification has been touched. >> > > Let me see if I understood. UPS will send a message to the client and when > the message be *read* (instead of delivered), the client will send a > message back to the UPS saying: "The message was read"? > > > Yes , but let me be more specific here : us when the app is in the > background or not running and that the user "tap" the notification > > So, the very first thing that had to be done was to give the Push >> Notification a unique identifier, so that we can track it and do the >> metrics on it. >> > > +1. Not only us (UPS) but also the backend app > > >> For that, I have been using an existing model object that we have , the >> PushMessageInformation[2], and that is currently used to provide >> information for our dashboard. >> This object has now some extra fields, like a appOpenCounter etc ... >> >> The ID of this PushMessageInformation is now passed into the payload of >> the Push Message, just before we send it, this way the client library can >> use this ID to pass extra information to the UPS when a notification is >> touched. >> For this POC, I hijacked the cordova-helloworld, so that it extracts the >> ID from the payload and pass it as header when registering. >> > > The message back (from client to UPS) will be send every time the user > _read_ that? > > Well normally that will only happen once per installation per Push message > > > >> When the UPS receive the request, it looks for the header and if it exist >> it updates the existing PushMessageInformation instance. >> >> Please note, that for this POC, all is happening on Application level and >> not on Variant level but that can be easily changed. It depends on how >> fined grained we want to have these analytics. >> >> I did a small screencast that shows this in action : >> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >> >> The UPS branch containing the changes is here (the 2 latests commits are >> relevant) : >> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >> >> The client app is not really relevant since I really hacked badly the app >> (and the push plugin) ;) , however if interested I may share it. >> >> Now, let's discuss :) >> >> Sebi >> >> [1] https://issues.jboss.org/browse/AGPUSH-969 >> [2] >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > -- Passos > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/4fc22052/attachment.html From lukas.fryc at gmail.com Wed Apr 8 08:37:42 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 08 Apr 2015 12:37:42 +0000 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: Looks good so far, Andres, you are right, we want to show time-aggregated data, not particular events. Idea: My perspective might be very technical rather then marketing, but a pie chart with Push Network split would be interesting to me. st 8. 4. 2015 v 14:12 odes?latel Andres Galante napsal: > Hi, > > With the new data we have I've compared sent vs open messages on a chart > for each App: > https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html > (the x axis should be dates) > > I am wondering if we can generate a ratio that's useful for a marketing > person and show a benchmark comparing with other UPS users to know if the > users campaign is successful or not. Something like: open/sent or > device/open > > I believe that to show the first and last time a message was open is not > very useful. Maybe I am wrong, but, If we want to show an over time chart > for each notification we should collect periodical data, for example # of > open messages per hour to generate a linear graph that represents a day. > > What do you think? > > > On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc > wrote: > >> >> >> Envoy? de mon iPhone >> >> Le 30 mars 2015 ? 21:31, Daniel Passos a ?crit : >> >> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc >> wrote: >> >>> Folks ! >>> >>> For AGPUSH-969[1] and to kick off the discussions, I started a small >>> POC mainly focused on the backend. To sum up quickly : we want to know how >>> many installations/users has opened the application after that a Push >>> Notification has been touched. >>> >> >> Let me see if I understood. UPS will send a message to the client and >> when the message be *read* (instead of delivered), the client will send a >> message back to the UPS saying: "The message was read"? >> >> >> Yes , but let me be more specific here : us when the app is in the >> background or not running and that the user "tap" the notification >> >> So, the very first thing that had to be done was to give the Push >>> Notification a unique identifier, so that we can track it and do the >>> metrics on it. >>> >> >> +1. Not only us (UPS) but also the backend app >> >> >>> For that, I have been using an existing model object that we have , the >>> PushMessageInformation[2], and that is currently used to provide >>> information for our dashboard. >>> This object has now some extra fields, like a appOpenCounter etc ... >>> >>> The ID of this PushMessageInformation is now passed into the payload of >>> the Push Message, just before we send it, this way the client library can >>> use this ID to pass extra information to the UPS when a notification is >>> touched. >>> For this POC, I hijacked the cordova-helloworld, so that it extracts the >>> ID from the payload and pass it as header when registering. >>> >> >> The message back (from client to UPS) will be send every time the user >> _read_ that? >> >> Well normally that will only happen once per installation per Push >> message >> >> >> >>> When the UPS receive the request, it looks for the header and if it >>> exist it updates the existing PushMessageInformation instance. >>> >>> Please note, that for this POC, all is happening on Application level >>> and not on Variant level but that can be easily changed. It depends on how >>> fined grained we want to have these analytics. >>> >>> I did a small screencast that shows this in action : >>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>> >>> The UPS branch containing the changes is here (the 2 latests commits are >>> relevant) : >>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>> >>> The client app is not really relevant since I really hacked badly the >>> app (and the push plugin) ;) , however if interested I may share it. >>> >>> Now, let's discuss :) >>> >>> Sebi >>> >>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>> [2] >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/75c6942e/attachment-0001.html From scm.blanc at gmail.com Wed Apr 8 08:46:21 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 8 Apr 2015 14:46:21 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? wrote: > Looks good so far, Andres, > > you are right, we want to show time-aggregated data, not particular events. > > Idea: > My perspective might be very technical rather then marketing, but a pie > chart with Push Network split would be interesting to me. > +1 (or Donut :) ) > > st 8. 4. 2015 v 14:12 odes?latel Andres Galante > napsal: > > Hi, >> >> With the new data we have I've compared sent vs open messages on a chart >> for each App: >> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >> (the x axis should be dates) >> >> I am wondering if we can generate a ratio that's useful for a marketing >> person and show a benchmark comparing with other UPS users to know if the >> users campaign is successful or not. Something like: open/sent or >> device/open >> >> I believe that to show the first and last time a message was open is not >> very useful. Maybe I am wrong, but, If we want to show an over time chart >> for each notification we should collect periodical data, for example # of >> open messages per hour to generate a linear graph that represents a day. >> >> What do you think? >> >> >> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc >> wrote: >> >>> >>> >>> Envoy? de mon iPhone >>> >>> Le 30 mars 2015 ? 21:31, Daniel Passos a ?crit : >>> >>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc >>> wrote: >>> >>>> Folks ! >>>> >>>> For AGPUSH-969[1] and to kick off the discussions, I started a small >>>> POC mainly focused on the backend. To sum up quickly : we want to know how >>>> many installations/users has opened the application after that a Push >>>> Notification has been touched. >>>> >>> >>> Let me see if I understood. UPS will send a message to the client and >>> when the message be *read* (instead of delivered), the client will send a >>> message back to the UPS saying: "The message was read"? >>> >>> >>> Yes , but let me be more specific here : us when the app is in the >>> background or not running and that the user "tap" the notification >>> >>> So, the very first thing that had to be done was to give the Push >>>> Notification a unique identifier, so that we can track it and do the >>>> metrics on it. >>>> >>> >>> +1. Not only us (UPS) but also the backend app >>> >>> >>>> For that, I have been using an existing model object that we have , the >>>> PushMessageInformation[2], and that is currently used to provide >>>> information for our dashboard. >>>> This object has now some extra fields, like a appOpenCounter etc ... >>>> >>>> The ID of this PushMessageInformation is now passed into the payload of >>>> the Push Message, just before we send it, this way the client library can >>>> use this ID to pass extra information to the UPS when a notification is >>>> touched. >>>> For this POC, I hijacked the cordova-helloworld, so that it extracts >>>> the ID from the payload and pass it as header when registering. >>>> >>> >>> The message back (from client to UPS) will be send every time the user >>> _read_ that? >>> >>> Well normally that will only happen once per installation per Push >>> message >>> >>> >>> >>>> When the UPS receive the request, it looks for the header and if it >>>> exist it updates the existing PushMessageInformation instance. >>>> >>>> Please note, that for this POC, all is happening on Application level >>>> and not on Variant level but that can be easily changed. It depends on how >>>> fined grained we want to have these analytics. >>>> >>>> I did a small screencast that shows this in action : >>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>> >>>> The UPS branch containing the changes is here (the 2 latests commits >>>> are relevant) : >>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>> >>>> The client app is not really relevant since I really hacked badly the >>>> app (and the push plugin) ;) , however if interested I may share it. >>>> >>>> Now, let's discuss :) >>>> >>>> Sebi >>>> >>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>> [2] >>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> -- Passos >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/f9fc41c8/attachment.html From matzew at apache.org Wed Apr 8 08:59:54 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Apr 2015 14:59:54 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: :-) I like that too. But Andres, again, awesome UX ! On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc wrote: > > > On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? wrote: > >> Looks good so far, Andres, >> >> you are right, we want to show time-aggregated data, not particular >> events. >> >> Idea: >> My perspective might be very technical rather then marketing, but a pie >> chart with Push Network split would be interesting to me. >> > +1 (or Donut :) ) > >> >> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >> napsal: >> >> Hi, >>> >>> With the new data we have I've compared sent vs open messages on a chart >>> for each App: >>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>> (the x axis should be dates) >>> >>> I am wondering if we can generate a ratio that's useful for a marketing >>> person and show a benchmark comparing with other UPS users to know if the >>> users campaign is successful or not. Something like: open/sent or >>> device/open >>> >>> I believe that to show the first and last time a message was open is not >>> very useful. Maybe I am wrong, but, If we want to show an over time chart >>> for each notification we should collect periodical data, for example # of >>> open messages per hour to generate a linear graph that represents a day. >>> >>> What do you think? >>> >>> >>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc >>> wrote: >>> >>>> >>>> >>>> Envoy? de mon iPhone >>>> >>>> Le 30 mars 2015 ? 21:31, Daniel Passos a ?crit : >>>> >>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc >>>> wrote: >>>> >>>>> Folks ! >>>>> >>>>> For AGPUSH-969[1] and to kick off the discussions, I started a small >>>>> POC mainly focused on the backend. To sum up quickly : we want to know how >>>>> many installations/users has opened the application after that a Push >>>>> Notification has been touched. >>>>> >>>> >>>> Let me see if I understood. UPS will send a message to the client and >>>> when the message be *read* (instead of delivered), the client will send a >>>> message back to the UPS saying: "The message was read"? >>>> >>>> >>>> Yes , but let me be more specific here : us when the app is in the >>>> background or not running and that the user "tap" the notification >>>> >>>> So, the very first thing that had to be done was to give the Push >>>>> Notification a unique identifier, so that we can track it and do the >>>>> metrics on it. >>>>> >>>> >>>> +1. Not only us (UPS) but also the backend app >>>> >>>> >>>>> For that, I have been using an existing model object that we have , >>>>> the PushMessageInformation[2], and that is currently used to provide >>>>> information for our dashboard. >>>>> This object has now some extra fields, like a appOpenCounter etc ... >>>>> >>>>> The ID of this PushMessageInformation is now passed into the payload >>>>> of the Push Message, just before we send it, this way the client library >>>>> can use this ID to pass extra information to the UPS when a notification is >>>>> touched. >>>>> For this POC, I hijacked the cordova-helloworld, so that it extracts >>>>> the ID from the payload and pass it as header when registering. >>>>> >>>> >>>> The message back (from client to UPS) will be send every time the user >>>> _read_ that? >>>> >>>> Well normally that will only happen once per installation per Push >>>> message >>>> >>>> >>>> >>>>> When the UPS receive the request, it looks for the header and if it >>>>> exist it updates the existing PushMessageInformation instance. >>>>> >>>>> Please note, that for this POC, all is happening on Application level >>>>> and not on Variant level but that can be easily changed. It depends on how >>>>> fined grained we want to have these analytics. >>>>> >>>>> I did a small screencast that shows this in action : >>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>> >>>>> The UPS branch containing the changes is here (the 2 latests commits >>>>> are relevant) : >>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>> >>>>> The client app is not really relevant since I really hacked badly the >>>>> app (and the push plugin) ;) , however if interested I may share it. >>>>> >>>>> Now, let's discuss :) >>>>> >>>>> Sebi >>>>> >>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>> [2] >>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> -- Passos >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/3d4ac476/attachment-0001.html From matzew at apache.org Wed Apr 8 09:32:37 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Apr 2015 15:32:37 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: One thing: I think the numbers on the chart are confusing, and incorrect. It's usually not a ton of messages that are sent. that's more like 5 or 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL the damn app. Therefore the "app opened due to receiving push" numbers are also not 100% correct here. On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf wrote: > :-) I like that too. > > But Andres, again, awesome UX ! > > On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc > wrote: > >> >> >> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? wrote: >> >>> Looks good so far, Andres, >>> >>> you are right, we want to show time-aggregated data, not particular >>> events. >>> >>> Idea: >>> My perspective might be very technical rather then marketing, but a pie >>> chart with Push Network split would be interesting to me. >>> >> +1 (or Donut :) ) >> >>> >>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >>> napsal: >>> >>> Hi, >>>> >>>> With the new data we have I've compared sent vs open messages on a >>>> chart for each App: >>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>> (the x axis should be dates) >>>> >>>> I am wondering if we can generate a ratio that's useful for a marketing >>>> person and show a benchmark comparing with other UPS users to know if the >>>> users campaign is successful or not. Something like: open/sent or >>>> device/open >>>> >>>> I believe that to show the first and last time a message was open is >>>> not very useful. Maybe I am wrong, but, If we want to show an over time >>>> chart for each notification we should collect periodical data, for example >>>> # of open messages per hour to generate a linear graph that represents a >>>> day. >>>> >>>> What do you think? >>>> >>>> >>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc >>>> wrote: >>>> >>>>> >>>>> >>>>> Envoy? de mon iPhone >>>>> >>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a ?crit : >>>>> >>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc >>>> > wrote: >>>>> >>>>>> Folks ! >>>>>> >>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a small >>>>>> POC mainly focused on the backend. To sum up quickly : we want to know how >>>>>> many installations/users has opened the application after that a Push >>>>>> Notification has been touched. >>>>>> >>>>> >>>>> Let me see if I understood. UPS will send a message to the client and >>>>> when the message be *read* (instead of delivered), the client will send a >>>>> message back to the UPS saying: "The message was read"? >>>>> >>>>> >>>>> Yes , but let me be more specific here : us when the app is in the >>>>> background or not running and that the user "tap" the notification >>>>> >>>>> So, the very first thing that had to be done was to give the Push >>>>>> Notification a unique identifier, so that we can track it and do the >>>>>> metrics on it. >>>>>> >>>>> >>>>> +1. Not only us (UPS) but also the backend app >>>>> >>>>> >>>>>> For that, I have been using an existing model object that we have , >>>>>> the PushMessageInformation[2], and that is currently used to provide >>>>>> information for our dashboard. >>>>>> This object has now some extra fields, like a appOpenCounter etc ... >>>>>> >>>>>> The ID of this PushMessageInformation is now passed into the payload >>>>>> of the Push Message, just before we send it, this way the client library >>>>>> can use this ID to pass extra information to the UPS when a notification is >>>>>> touched. >>>>>> For this POC, I hijacked the cordova-helloworld, so that it extracts >>>>>> the ID from the payload and pass it as header when registering. >>>>>> >>>>> >>>>> The message back (from client to UPS) will be send every time the user >>>>> _read_ that? >>>>> >>>>> Well normally that will only happen once per installation per Push >>>>> message >>>>> >>>>> >>>>> >>>>>> When the UPS receive the request, it looks for the header and if it >>>>>> exist it updates the existing PushMessageInformation instance. >>>>>> >>>>>> Please note, that for this POC, all is happening on Application level >>>>>> and not on Variant level but that can be easily changed. It depends on how >>>>>> fined grained we want to have these analytics. >>>>>> >>>>>> I did a small screencast that shows this in action : >>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>> >>>>>> The UPS branch containing the changes is here (the 2 latests commits >>>>>> are relevant) : >>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>> >>>>>> The client app is not really relevant since I really hacked badly the >>>>>> app (and the push plugin) ;) , however if interested I may share it. >>>>>> >>>>>> Now, let's discuss :) >>>>>> >>>>>> Sebi >>>>>> >>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>> [2] >>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> -- Passos >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/d6e50bdb/attachment.html From agalante at redhat.com Wed Apr 8 09:44:57 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 8 Apr 2015 10:44:57 -0300 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: Yes, you are right, it should be something like: 5 message sent 3k delivered 2k open 4k devices. Just change the example. Also the x-axis should be dates. Thanks! On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf wrote: > One thing: I think the numbers on the chart are confusing, and incorrect. > It's usually not a ton of messages that are sent. that's more like 5 or 10 > per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL the > damn app. > Therefore the "app opened due to receiving push" numbers are also not 100% > correct here. > > On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf > wrote: > >> :-) I like that too. >> >> But Andres, again, awesome UX ! >> >> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >> wrote: >> >>> >>> >>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? wrote: >>> >>>> Looks good so far, Andres, >>>> >>>> you are right, we want to show time-aggregated data, not particular >>>> events. >>>> >>>> Idea: >>>> My perspective might be very technical rather then marketing, but a pie >>>> chart with Push Network split would be interesting to me. >>>> >>> +1 (or Donut :) ) >>> >>>> >>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >>>> napsal: >>>> >>>> Hi, >>>>> >>>>> With the new data we have I've compared sent vs open messages on a >>>>> chart for each App: >>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>> (the x axis should be dates) >>>>> >>>>> I am wondering if we can generate a ratio that's useful for a >>>>> marketing person and show a benchmark comparing with other UPS users to >>>>> know if the users campaign is successful or not. Something like: open/sent >>>>> or device/open >>>>> >>>>> I believe that to show the first and last time a message was open is >>>>> not very useful. Maybe I am wrong, but, If we want to show an over time >>>>> chart for each notification we should collect periodical data, for example >>>>> # of open messages per hour to generate a linear graph that represents a >>>>> day. >>>>> >>>>> What do you think? >>>>> >>>>> >>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> Envoy? de mon iPhone >>>>>> >>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a ?crit : >>>>>> >>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>> scm.blanc at gmail.com> wrote: >>>>>> >>>>>>> Folks ! >>>>>>> >>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>> know how many installations/users has opened the application after that a >>>>>>> Push Notification has been touched. >>>>>>> >>>>>> >>>>>> Let me see if I understood. UPS will send a message to the client and >>>>>> when the message be *read* (instead of delivered), the client will send a >>>>>> message back to the UPS saying: "The message was read"? >>>>>> >>>>>> >>>>>> Yes , but let me be more specific here : us when the app is in the >>>>>> background or not running and that the user "tap" the notification >>>>>> >>>>>> So, the very first thing that had to be done was to give the Push >>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>> metrics on it. >>>>>>> >>>>>> >>>>>> +1. Not only us (UPS) but also the backend app >>>>>> >>>>>> >>>>>>> For that, I have been using an existing model object that we have , >>>>>>> the PushMessageInformation[2], and that is currently used to provide >>>>>>> information for our dashboard. >>>>>>> This object has now some extra fields, like a appOpenCounter etc ... >>>>>>> >>>>>>> The ID of this PushMessageInformation is now passed into the payload >>>>>>> of the Push Message, just before we send it, this way the client library >>>>>>> can use this ID to pass extra information to the UPS when a notification is >>>>>>> touched. >>>>>>> For this POC, I hijacked the cordova-helloworld, so that it extracts >>>>>>> the ID from the payload and pass it as header when registering. >>>>>>> >>>>>> >>>>>> The message back (from client to UPS) will be send every time the >>>>>> user _read_ that? >>>>>> >>>>>> Well normally that will only happen once per installation per Push >>>>>> message >>>>>> >>>>>> >>>>>> >>>>>>> When the UPS receive the request, it looks for the header and if it >>>>>>> exist it updates the existing PushMessageInformation instance. >>>>>>> >>>>>>> Please note, that for this POC, all is happening on Application >>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>> on how fined grained we want to have these analytics. >>>>>>> >>>>>>> I did a small screencast that shows this in action : >>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>> >>>>>>> The UPS branch containing the changes is here (the 2 latests commits >>>>>>> are relevant) : >>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>> >>>>>>> The client app is not really relevant since I really hacked badly >>>>>>> the app (and the push plugin) ;) , however if interested I may share it. >>>>>>> >>>>>>> Now, let's discuss :) >>>>>>> >>>>>>> Sebi >>>>>>> >>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>> [2] >>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> -- Passos >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/d94b76b7/attachment-0001.html From matzew at apache.org Wed Apr 8 09:51:30 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Apr 2015 15:51:30 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: Thanks for the changed UI I think we also have the notion to track a specifc push message "Show this by Friday, and get 5% discount". I think what I'd like to see is, on the current UI, you click a specific push message, to get more details: here would be the right spot to see 2k opened due to push On Wed, Apr 8, 2015 at 3:44 PM, Andres Galante wrote: > Yes, you are right, it should be something like: > > 5 message sent > 3k delivered > 2k open > 4k devices. > > Just change the example. Also the x-axis should be dates. > > Thanks! > > > > > On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf > wrote: > >> One thing: I think the numbers on the chart are confusing, and incorrect. >> It's usually not a ton of messages that are sent. that's more like 5 or >> 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL >> the damn app. >> Therefore the "app opened due to receiving push" numbers are also not >> 100% correct here. >> >> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >> wrote: >> >>> :-) I like that too. >>> >>> But Andres, again, awesome UX ! >>> >>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>> wrote: >>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>> wrote: >>>> >>>>> Looks good so far, Andres, >>>>> >>>>> you are right, we want to show time-aggregated data, not particular >>>>> events. >>>>> >>>>> Idea: >>>>> My perspective might be very technical rather then marketing, but a >>>>> pie chart with Push Network split would be interesting to me. >>>>> >>>> +1 (or Donut :) ) >>>> >>>>> >>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >>>>> napsal: >>>>> >>>>> Hi, >>>>>> >>>>>> With the new data we have I've compared sent vs open messages on a >>>>>> chart for each App: >>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>> (the x axis should be dates) >>>>>> >>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>> or device/open >>>>>> >>>>>> I believe that to show the first and last time a message was open is >>>>>> not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>> chart for each notification we should collect periodical data, for example >>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>> day. >>>>>> >>>>>> What do you think? >>>>>> >>>>>> >>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc >>>>> > wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> Envoy? de mon iPhone >>>>>>> >>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>> ?crit : >>>>>>> >>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>> scm.blanc at gmail.com> wrote: >>>>>>> >>>>>>>> Folks ! >>>>>>>> >>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>> know how many installations/users has opened the application after that a >>>>>>>> Push Notification has been touched. >>>>>>>> >>>>>>> >>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>> >>>>>>> >>>>>>> Yes , but let me be more specific here : us when the app is in the >>>>>>> background or not running and that the user "tap" the notification >>>>>>> >>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>> metrics on it. >>>>>>>> >>>>>>> >>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>> >>>>>>> >>>>>>>> For that, I have been using an existing model object that we have , >>>>>>>> the PushMessageInformation[2], and that is currently used to provide >>>>>>>> information for our dashboard. >>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>> ... >>>>>>>> >>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>> notification is touched. >>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>> >>>>>>> >>>>>>> The message back (from client to UPS) will be send every time the >>>>>>> user _read_ that? >>>>>>> >>>>>>> Well normally that will only happen once per installation per Push >>>>>>> message >>>>>>> >>>>>>> >>>>>>> >>>>>>>> When the UPS receive the request, it looks for the header and if it >>>>>>>> exist it updates the existing PushMessageInformation instance. >>>>>>>> >>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>> on how fined grained we want to have these analytics. >>>>>>>> >>>>>>>> I did a small screencast that shows this in action : >>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>> >>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>> commits are relevant) : >>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>> >>>>>>>> The client app is not really relevant since I really hacked badly >>>>>>>> the app (and the push plugin) ;) , however if interested I may share it. >>>>>>>> >>>>>>>> Now, let's discuss :) >>>>>>>> >>>>>>>> Sebi >>>>>>>> >>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>> [2] >>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> -- Passos >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/3f694bd9/attachment.html From agalante at redhat.com Wed Apr 8 09:58:36 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 8 Apr 2015 10:58:36 -0300 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: There will be more stats for each notification. The idea is to have a general view on the App analytics and more detail numbers on each notification. I don't know how "intelligent" they can be. First crawl, then walk, then run. Lets crawl and get the most we can with the numbers we have. We can do some clever stuff with performance ratios, and I trying to figure out which ratio is useful and which isn't. And add the count chart with Push Network split :) On Wed, Apr 8, 2015 at 10:51 AM, Matthias Wessendorf wrote: > Thanks for the changed UI > > I think we also have the notion to track a specifc push message "Show this > by Friday, and get 5% discount". > I think what I'd like to see is, on the current UI, you click a specific > push message, to get more details: here would be the right spot to see 2k > opened due to push > > On Wed, Apr 8, 2015 at 3:44 PM, Andres Galante > wrote: > >> Yes, you are right, it should be something like: >> >> 5 message sent >> 3k delivered >> 2k open >> 4k devices. >> >> Just change the example. Also the x-axis should be dates. >> >> Thanks! >> >> >> >> >> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf >> wrote: >> >>> One thing: I think the numbers on the chart are confusing, and >>> incorrect. >>> It's usually not a ton of messages that are sent. that's more like 5 or >>> 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL >>> the damn app. >>> Therefore the "app opened due to receiving push" numbers are also not >>> 100% correct here. >>> >>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >>> wrote: >>> >>>> :-) I like that too. >>>> >>>> But Andres, again, awesome UX ! >>>> >>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>> wrote: >>>>> >>>>>> Looks good so far, Andres, >>>>>> >>>>>> you are right, we want to show time-aggregated data, not particular >>>>>> events. >>>>>> >>>>>> Idea: >>>>>> My perspective might be very technical rather then marketing, but a >>>>>> pie chart with Push Network split would be interesting to me. >>>>>> >>>>> +1 (or Donut :) ) >>>>> >>>>>> >>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >>>>>> napsal: >>>>>> >>>>>> Hi, >>>>>>> >>>>>>> With the new data we have I've compared sent vs open messages on a >>>>>>> chart for each App: >>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>> (the x axis should be dates) >>>>>>> >>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>> or device/open >>>>>>> >>>>>>> I believe that to show the first and last time a message was open is >>>>>>> not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>> chart for each notification we should collect periodical data, for example >>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>> day. >>>>>>> >>>>>>> What do you think? >>>>>>> >>>>>>> >>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>> scm.blanc at gmail.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Envoy? de mon iPhone >>>>>>>> >>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>> ?crit : >>>>>>>> >>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>> >>>>>>>>> Folks ! >>>>>>>>> >>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>> Push Notification has been touched. >>>>>>>>> >>>>>>>> >>>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>>> >>>>>>>> >>>>>>>> Yes , but let me be more specific here : us when the app is in the >>>>>>>> background or not running and that the user "tap" the notification >>>>>>>> >>>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>>> metrics on it. >>>>>>>>> >>>>>>>> >>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>> >>>>>>>> >>>>>>>>> For that, I have been using an existing model object that we have >>>>>>>>> , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>> information for our dashboard. >>>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>>> ... >>>>>>>>> >>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>> notification is touched. >>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>> >>>>>>>> >>>>>>>> The message back (from client to UPS) will be send every time the >>>>>>>> user _read_ that? >>>>>>>> >>>>>>>> Well normally that will only happen once per installation per Push >>>>>>>> message >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> When the UPS receive the request, it looks for the header and if >>>>>>>>> it exist it updates the existing PushMessageInformation instance. >>>>>>>>> >>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>> >>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>> >>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>> commits are relevant) : >>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>> >>>>>>>>> The client app is not really relevant since I really hacked badly >>>>>>>>> the app (and the push plugin) ;) , however if interested I may share it. >>>>>>>>> >>>>>>>>> Now, let's discuss :) >>>>>>>>> >>>>>>>>> Sebi >>>>>>>>> >>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>> [2] >>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> -- Passos >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/3060a5b4/attachment-0001.html From matzew at apache.org Wed Apr 8 10:14:51 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Apr 2015 16:14:51 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: On Wed, Apr 8, 2015 at 3:58 PM, Andres Galante wrote: > There will be more stats for each notification. The idea is to have a > general view on the App analytics and more detail numbers on each > notification. > > I don't know how "intelligent" they can be. First crawl, then walk, then > run. Lets crawl and get the most we can with the numbers we have. > > We can do some clever stuff with performance ratios, and I trying to > figure out which ratio is useful and which isn't. > the push message has an ID, so we can see which one was opened or not > > And add the count chart with Push Network split :) > that would be a split per variant (since you can not have APNs and GCM on one variant) > > > > On Wed, Apr 8, 2015 at 10:51 AM, Matthias Wessendorf > wrote: > >> Thanks for the changed UI >> >> I think we also have the notion to track a specifc push message "Show >> this by Friday, and get 5% discount". >> I think what I'd like to see is, on the current UI, you click a specific >> push message, to get more details: here would be the right spot to see 2k >> opened due to push >> >> On Wed, Apr 8, 2015 at 3:44 PM, Andres Galante >> wrote: >> >>> Yes, you are right, it should be something like: >>> >>> 5 message sent >>> 3k delivered >>> 2k open >>> 4k devices. >>> >>> Just change the example. Also the x-axis should be dates. >>> >>> Thanks! >>> >>> >>> >>> >>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf >>> wrote: >>> >>>> One thing: I think the numbers on the chart are confusing, and >>>> incorrect. >>>> It's usually not a ton of messages that are sent. that's more like 5 or >>>> 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL >>>> the damn app. >>>> Therefore the "app opened due to receiving push" numbers are also not >>>> 100% correct here. >>>> >>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >>>> wrote: >>>> >>>>> :-) I like that too. >>>>> >>>>> But Andres, again, awesome UX ! >>>>> >>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>> wrote: >>>>>> >>>>>>> Looks good so far, Andres, >>>>>>> >>>>>>> you are right, we want to show time-aggregated data, not particular >>>>>>> events. >>>>>>> >>>>>>> Idea: >>>>>>> My perspective might be very technical rather then marketing, but a >>>>>>> pie chart with Push Network split would be interesting to me. >>>>>>> >>>>>> +1 (or Donut :) ) >>>>>> >>>>>>> >>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >>>>>>> napsal: >>>>>>> >>>>>>> Hi, >>>>>>>> >>>>>>>> With the new data we have I've compared sent vs open messages on a >>>>>>>> chart for each App: >>>>>>>> >>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>> (the x axis should be dates) >>>>>>>> >>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>> or device/open >>>>>>>> >>>>>>>> I believe that to show the first and last time a message was open >>>>>>>> is not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>>> chart for each notification we should collect periodical data, for example >>>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>>> day. >>>>>>>> >>>>>>>> What do you think? >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Envoy? de mon iPhone >>>>>>>>> >>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>> ?crit : >>>>>>>>> >>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Folks ! >>>>>>>>>> >>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>> Push Notification has been touched. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>>>> >>>>>>>>> >>>>>>>>> Yes , but let me be more specific here : us when the app is in the >>>>>>>>> background or not running and that the user "tap" the notification >>>>>>>>> >>>>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>>>> metrics on it. >>>>>>>>>> >>>>>>>>> >>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>> >>>>>>>>> >>>>>>>>>> For that, I have been using an existing model object that we have >>>>>>>>>> , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>> information for our dashboard. >>>>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>>>> ... >>>>>>>>>> >>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>> notification is touched. >>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>> >>>>>>>>> >>>>>>>>> The message back (from client to UPS) will be send every time the >>>>>>>>> user _read_ that? >>>>>>>>> >>>>>>>>> Well normally that will only happen once per installation per Push >>>>>>>>> message >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> When the UPS receive the request, it looks for the header and if >>>>>>>>>> it exist it updates the existing PushMessageInformation instance. >>>>>>>>>> >>>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>>> >>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>> >>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>> commits are relevant) : >>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>> >>>>>>>>>> The client app is not really relevant since I really hacked badly >>>>>>>>>> the app (and the push plugin) ;) , however if interested I may share it. >>>>>>>>>> >>>>>>>>>> Now, let's discuss :) >>>>>>>>>> >>>>>>>>>> Sebi >>>>>>>>>> >>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>> [2] >>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> -- Passos >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/6aec580d/attachment-0001.html From scm.blanc at gmail.com Wed Apr 8 11:24:50 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Wed, 8 Apr 2015 17:24:50 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> Message-ID: <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> I wonder if a bar chart (even maybe stacked bar) would not be more clear to show this data ? Wdyt ? Envoy? de mon iPhone > Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : > > Yes, you are right, it should be something like: > > 5 message sent > 3k delivered > 2k open > 4k devices. > > Just change the example. Also the x-axis should be dates. > > Thanks! > > > > >> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf wrote: >> One thing: I think the numbers on the chart are confusing, and incorrect. >> It's usually not a ton of messages that are sent. that's more like 5 or 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL the damn app. >> Therefore the "app opened due to receiving push" numbers are also not 100% correct here. >> >>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf wrote: >>> :-) I like that too. >>> >>> But Andres, again, awesome UX ! >>> >>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc wrote: >>>> >>>> >>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? wrote: >>>>> Looks good so far, Andres, >>>>> >>>>> you are right, we want to show time-aggregated data, not particular events. >>>>> >>>>> Idea: >>>>> My perspective might be very technical rather then marketing, but a pie chart with Push Network split would be interesting to me. >>>> >>>> +1 (or Donut :) ) >>>>> >>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante napsal: >>>>> >>>>>> Hi, >>>>>> >>>>>> With the new data we have I've compared sent vs open messages on a chart for each App: >>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>> (the x axis should be dates) >>>>>> >>>>>> I am wondering if we can generate a ratio that's useful for a marketing person and show a benchmark comparing with other UPS users to know if the users campaign is successful or not. Something like: open/sent or device/open >>>>>> >>>>>> I believe that to show the first and last time a message was open is not very useful. Maybe I am wrong, but, If we want to show an over time chart for each notification we should collect periodical data, for example # of open messages per hour to generate a linear graph that represents a day. >>>>>> >>>>>> What do you think? >>>>>> >>>>>> >>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc wrote: >>>>>>> >>>>>>> >>>>>>> Envoy? de mon iPhone >>>>>>> >>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a ?crit : >>>>>>>> >>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc wrote: >>>>>>>>> Folks ! >>>>>>>>> >>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a small POC mainly focused on the backend. To sum up quickly : we want to know how many installations/users has opened the application after that a Push Notification has been touched. >>>>>>>> >>>>>>>> Let me see if I understood. UPS will send a message to the client and when the message be *read* (instead of delivered), the client will send a message back to the UPS saying: "The message was read"? >>>>>>> Yes , but let me be more specific here : us when the app is in the background or not running and that the user "tap" the notification >>>>>>>>> So, the very first thing that had to be done was to give the Push Notification a unique identifier, so that we can track it and do the metrics on it. >>>>>>>> >>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>> >>>>>>>>> For that, I have been using an existing model object that we have , the PushMessageInformation[2], and that is currently used to provide information for our dashboard. >>>>>>>>> This object has now some extra fields, like a appOpenCounter etc ... >>>>>>>>> >>>>>>>>> The ID of this PushMessageInformation is now passed into the payload of the Push Message, just before we send it, this way the client library can use this ID to pass extra information to the UPS when a notification is touched. >>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it extracts the ID from the payload and pass it as header when registering. >>>>>>>> >>>>>>>> The message back (from client to UPS) will be send every time the user _read_ that? >>>>>>> Well normally that will only happen once per installation per Push message >>>>>>>> >>>>>>>>> When the UPS receive the request, it looks for the header and if it exist it updates the existing PushMessageInformation instance. >>>>>>>>> >>>>>>>>> Please note, that for this POC, all is happening on Application level and not on Variant level but that can be easily changed. It depends on how fined grained we want to have these analytics. >>>>>>>>> >>>>>>>>> I did a small screencast that shows this in action : https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>> >>>>>>>>> The UPS branch containing the changes is here (the 2 latests commits are relevant) : https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>> >>>>>>>>> The client app is not really relevant since I really hacked badly the app (and the push plugin) ;) , however if interested I may share it. >>>>>>>>> >>>>>>>>> Now, let's discuss :) >>>>>>>>> >>>>>>>>> Sebi >>>>>>>>> >>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>> [2] https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> -- Passos >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/bb0e3efc/attachment.html From agalante at redhat.com Wed Apr 8 11:44:23 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 8 Apr 2015 12:44:23 -0300 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: Good idea! take a look: https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc wrote: > I wonder if a bar chart (even maybe stacked bar) would not be more clear > to show this data ? > Wdyt ? > > Envoy? de mon iPhone > > Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : > > Yes, you are right, it should be something like: > > 5 message sent > 3k delivered > 2k open > 4k devices. > > Just change the example. Also the x-axis should be dates. > > Thanks! > > > > > On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf > wrote: > >> One thing: I think the numbers on the chart are confusing, and incorrect. >> It's usually not a ton of messages that are sent. that's more like 5 or >> 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL >> the damn app. >> Therefore the "app opened due to receiving push" numbers are also not >> 100% correct here. >> >> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >> wrote: >> >>> :-) I like that too. >>> >>> But Andres, again, awesome UX ! >>> >>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>> wrote: >>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>> wrote: >>>> >>>>> Looks good so far, Andres, >>>>> >>>>> you are right, we want to show time-aggregated data, not particular >>>>> events. >>>>> >>>>> Idea: >>>>> My perspective might be very technical rather then marketing, but a >>>>> pie chart with Push Network split would be interesting to me. >>>>> >>>> +1 (or Donut :) ) >>>> >>>>> >>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >>>>> napsal: >>>>> >>>>> Hi, >>>>>> >>>>>> With the new data we have I've compared sent vs open messages on a >>>>>> chart for each App: >>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>> (the x axis should be dates) >>>>>> >>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>> or device/open >>>>>> >>>>>> I believe that to show the first and last time a message was open is >>>>>> not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>> chart for each notification we should collect periodical data, for example >>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>> day. >>>>>> >>>>>> What do you think? >>>>>> >>>>>> >>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc >>>>> > wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> Envoy? de mon iPhone >>>>>>> >>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>> ?crit : >>>>>>> >>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>> scm.blanc at gmail.com> wrote: >>>>>>> >>>>>>>> Folks ! >>>>>>>> >>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>> know how many installations/users has opened the application after that a >>>>>>>> Push Notification has been touched. >>>>>>>> >>>>>>> >>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>> >>>>>>> >>>>>>> Yes , but let me be more specific here : us when the app is in the >>>>>>> background or not running and that the user "tap" the notification >>>>>>> >>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>> metrics on it. >>>>>>>> >>>>>>> >>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>> >>>>>>> >>>>>>>> For that, I have been using an existing model object that we have , >>>>>>>> the PushMessageInformation[2], and that is currently used to provide >>>>>>>> information for our dashboard. >>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>> ... >>>>>>>> >>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>> notification is touched. >>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>> >>>>>>> >>>>>>> The message back (from client to UPS) will be send every time the >>>>>>> user _read_ that? >>>>>>> >>>>>>> Well normally that will only happen once per installation per Push >>>>>>> message >>>>>>> >>>>>>> >>>>>>> >>>>>>>> When the UPS receive the request, it looks for the header and if it >>>>>>>> exist it updates the existing PushMessageInformation instance. >>>>>>>> >>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>> on how fined grained we want to have these analytics. >>>>>>>> >>>>>>>> I did a small screencast that shows this in action : >>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>> >>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>> commits are relevant) : >>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>> >>>>>>>> The client app is not really relevant since I really hacked badly >>>>>>>> the app (and the push plugin) ;) , however if interested I may share it. >>>>>>>> >>>>>>>> Now, let's discuss :) >>>>>>>> >>>>>>>> Sebi >>>>>>>> >>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>> [2] >>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> -- Passos >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/365ec15d/attachment-0001.html From matzew at apache.org Wed Apr 8 11:51:37 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Apr 2015 17:51:37 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: Again, I doubt that there will be 3k of messages per app, a day. That would mean your "ESPN Sports News" app would send you 3k messages - joy, he? I wonder how the charts would look on more realistic data: 500.000 devices 1 push message a day (delivered to all 500k) opened by 250k, same day Now if I sent two messages: Breaking news A, Breaking news B How would I see how many directly opened "Breaking news A" (or the other one)? On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante wrote: > Good idea! take a look: > > https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html > > > > On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc > wrote: > >> I wonder if a bar chart (even maybe stacked bar) would not be more clear >> to show this data ? >> Wdyt ? >> >> Envoy? de mon iPhone >> >> Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : >> >> Yes, you are right, it should be something like: >> >> 5 message sent >> 3k delivered >> 2k open >> 4k devices. >> >> Just change the example. Also the x-axis should be dates. >> >> Thanks! >> >> >> >> >> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf >> wrote: >> >>> One thing: I think the numbers on the chart are confusing, and >>> incorrect. >>> It's usually not a ton of messages that are sent. that's more like 5 or >>> 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL >>> the damn app. >>> Therefore the "app opened due to receiving push" numbers are also not >>> 100% correct here. >>> >>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >>> wrote: >>> >>>> :-) I like that too. >>>> >>>> But Andres, again, awesome UX ! >>>> >>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>> wrote: >>>>> >>>>>> Looks good so far, Andres, >>>>>> >>>>>> you are right, we want to show time-aggregated data, not particular >>>>>> events. >>>>>> >>>>>> Idea: >>>>>> My perspective might be very technical rather then marketing, but a >>>>>> pie chart with Push Network split would be interesting to me. >>>>>> >>>>> +1 (or Donut :) ) >>>>> >>>>>> >>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >>>>>> napsal: >>>>>> >>>>>> Hi, >>>>>>> >>>>>>> With the new data we have I've compared sent vs open messages on a >>>>>>> chart for each App: >>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>> (the x axis should be dates) >>>>>>> >>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>> or device/open >>>>>>> >>>>>>> I believe that to show the first and last time a message was open is >>>>>>> not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>> chart for each notification we should collect periodical data, for example >>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>> day. >>>>>>> >>>>>>> What do you think? >>>>>>> >>>>>>> >>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>> scm.blanc at gmail.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Envoy? de mon iPhone >>>>>>>> >>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>> ?crit : >>>>>>>> >>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>> >>>>>>>>> Folks ! >>>>>>>>> >>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>> Push Notification has been touched. >>>>>>>>> >>>>>>>> >>>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>>> >>>>>>>> >>>>>>>> Yes , but let me be more specific here : us when the app is in the >>>>>>>> background or not running and that the user "tap" the notification >>>>>>>> >>>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>>> metrics on it. >>>>>>>>> >>>>>>>> >>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>> >>>>>>>> >>>>>>>>> For that, I have been using an existing model object that we have >>>>>>>>> , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>> information for our dashboard. >>>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>>> ... >>>>>>>>> >>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>> notification is touched. >>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>> >>>>>>>> >>>>>>>> The message back (from client to UPS) will be send every time the >>>>>>>> user _read_ that? >>>>>>>> >>>>>>>> Well normally that will only happen once per installation per Push >>>>>>>> message >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> When the UPS receive the request, it looks for the header and if >>>>>>>>> it exist it updates the existing PushMessageInformation instance. >>>>>>>>> >>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>> >>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>> >>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>> commits are relevant) : >>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>> >>>>>>>>> The client app is not really relevant since I really hacked badly >>>>>>>>> the app (and the push plugin) ;) , however if interested I may share it. >>>>>>>>> >>>>>>>>> Now, let's discuss :) >>>>>>>>> >>>>>>>>> Sebi >>>>>>>>> >>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>> [2] >>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> -- Passos >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/82568f14/attachment.html From lukas.fryc at gmail.com Wed Apr 8 11:57:29 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 08 Apr 2015 15:57:29 +0000 Subject: [aerogear-dev] UPS using JMS update In-Reply-To: References: Message-ID: Okay, first prototype is reading for testing and review: https://github.com/aerogear/aerogear-unifiedpush-server/pull/522 po 6. 4. 2015 v 20:17 odes?latel Jay Balunas napsal: > This all sounds really good to me! The priority would be wf/eap imo, with > others if very easy, or if community members want to jump in and add their > favorite. > > On Fri, Apr 3, 2015 at 7:54 AM, Sebastien Blanc > wrote: > >> >> >> On Fri, Apr 3, 2015 at 1:50 PM, Matthias Wessendorf >> wrote: >> >>> Cool stuff >>> >>> I am totally fine having this tied ti wf/eap >>> >>> wondering: at some point, should we offer a dist as (only) subststem for >>> wf/eap? >>> >> +1, I was exactly thinking the same, since we are tied to wf/eap, >> subsystem makes a lot of sense IMO >> >> >>> >>> >>> On Friday, April 3, 2015, Sebastien Blanc wrote: >>> >>>> That all sounds very good :) >>>> Thanks for the headupate, I will soon give it a try. >>>> >>>> On Fri, Apr 3, 2015 at 10:34 AM, Luk?? Fry? >>>> wrote: >>>> >>>>> Hi guys, >>>>> >>>>> so as outlined in previous thread [1], I have prototyped a JMS >>>>> batching approach for push message delivery. >>>>> >>>>> >>>>> >>>>> >>>>> We've discussed the approach with Matthias, Mirek Novak and Ondrej >>>>> Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents >>>>> describes a concept that we have came with: >>>>> >>>>> Diagram: >>>>> https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing >>>>> >>>>> Text Doc: >>>>> https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Implementation-wise, I've so far prototyped the messaging part (split >>>>> SenderService functionality to two subsequent queues with MDBs as shown on >>>>> diagram), >>>>> >>>>> but that's just a start, since we must configure it appropriately for >>>>> efficiency (queue configuration and batch sizes) and verify that >>>>> configuration works as expected, >>>>> >>>>> the prototype lives on a branch (unpolished, to be squashed later): >>>>> https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching >>>>> >>>>> Off course, you can play with it already. :-) >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Apart from the new requirement of using Java EE full profile (JMS), >>>>> the prototype leverages implementation-specific configurations and APIs: >>>>> >>>>> - org.hibernate.Query for token streaming / batch fetching >>>>> - HornetQ configurations of queue size, blocking behavior and >>>>> message de-duplication >>>>> >>>>> That pretty much binds us to WildFly/EAP - we can tweak it to run on >>>>> any compliant app server, but without specific configurations it won't work >>>>> properly. >>>>> >>>>> >>>>> >>>>> Once configured and functionally tested (that can even wait for Beta2 >>>>> I guess), >>>>> >>>>> we can cooperate with Mobile QE on testing (Stefan, Adam), their test >>>>> suite contains mocks of APNS/GCM against which we can load test. >>>>> >>>>> >>>>> >>>>> Cheers! >>>>> >>>>> ~ Lukas >>>>> >>>>> >>>>> [1] >>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/5acdb5ef/attachment-0001.html From agalante at redhat.com Wed Apr 8 12:05:17 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 8 Apr 2015 13:05:17 -0300 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: Do we always successful deliver messages to all registered devices? On Wed, Apr 8, 2015 at 12:51 PM, Matthias Wessendorf wrote: > Again, I doubt that there will be 3k of messages per app, a day. > That would mean your "ESPN Sports News" app would send you 3k messages - > joy, he? > > I wonder how the charts would look on more realistic data: > 500.000 devices > 1 push message a day (delivered to all 500k) > opened by 250k, same day > > > Now if I sent two messages: Breaking news A, Breaking news B > How would I see how many directly opened "Breaking news A" (or the other > one)? > > > > On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante > wrote: > >> Good idea! take a look: >> >> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >> >> >> >> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc >> wrote: >> >>> I wonder if a bar chart (even maybe stacked bar) would not be more clear >>> to show this data ? >>> Wdyt ? >>> >>> Envoy? de mon iPhone >>> >>> Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : >>> >>> Yes, you are right, it should be something like: >>> >>> 5 message sent >>> 3k delivered >>> 2k open >>> 4k devices. >>> >>> Just change the example. Also the x-axis should be dates. >>> >>> Thanks! >>> >>> >>> >>> >>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf >>> wrote: >>> >>>> One thing: I think the numbers on the chart are confusing, and >>>> incorrect. >>>> It's usually not a ton of messages that are sent. that's more like 5 or >>>> 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL >>>> the damn app. >>>> Therefore the "app opened due to receiving push" numbers are also not >>>> 100% correct here. >>>> >>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >>>> wrote: >>>> >>>>> :-) I like that too. >>>>> >>>>> But Andres, again, awesome UX ! >>>>> >>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>> wrote: >>>>>> >>>>>>> Looks good so far, Andres, >>>>>>> >>>>>>> you are right, we want to show time-aggregated data, not particular >>>>>>> events. >>>>>>> >>>>>>> Idea: >>>>>>> My perspective might be very technical rather then marketing, but a >>>>>>> pie chart with Push Network split would be interesting to me. >>>>>>> >>>>>> +1 (or Donut :) ) >>>>>> >>>>>>> >>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >>>>>>> napsal: >>>>>>> >>>>>>> Hi, >>>>>>>> >>>>>>>> With the new data we have I've compared sent vs open messages on a >>>>>>>> chart for each App: >>>>>>>> >>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>> (the x axis should be dates) >>>>>>>> >>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>> or device/open >>>>>>>> >>>>>>>> I believe that to show the first and last time a message was open >>>>>>>> is not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>>> chart for each notification we should collect periodical data, for example >>>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>>> day. >>>>>>>> >>>>>>>> What do you think? >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Envoy? de mon iPhone >>>>>>>>> >>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>> ?crit : >>>>>>>>> >>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Folks ! >>>>>>>>>> >>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>> Push Notification has been touched. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>>>> >>>>>>>>> >>>>>>>>> Yes , but let me be more specific here : us when the app is in the >>>>>>>>> background or not running and that the user "tap" the notification >>>>>>>>> >>>>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>>>> metrics on it. >>>>>>>>>> >>>>>>>>> >>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>> >>>>>>>>> >>>>>>>>>> For that, I have been using an existing model object that we have >>>>>>>>>> , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>> information for our dashboard. >>>>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>>>> ... >>>>>>>>>> >>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>> notification is touched. >>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>> >>>>>>>>> >>>>>>>>> The message back (from client to UPS) will be send every time the >>>>>>>>> user _read_ that? >>>>>>>>> >>>>>>>>> Well normally that will only happen once per installation per Push >>>>>>>>> message >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> When the UPS receive the request, it looks for the header and if >>>>>>>>>> it exist it updates the existing PushMessageInformation instance. >>>>>>>>>> >>>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>>> >>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>> >>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>> commits are relevant) : >>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>> >>>>>>>>>> The client app is not really relevant since I really hacked badly >>>>>>>>>> the app (and the push plugin) ;) , however if interested I may share it. >>>>>>>>>> >>>>>>>>>> Now, let's discuss :) >>>>>>>>>> >>>>>>>>>> Sebi >>>>>>>>>> >>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>> [2] >>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> -- Passos >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/11e98079/attachment-0001.html From scm.blanc at gmail.com Wed Apr 8 12:07:36 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Wed, 8 Apr 2015 18:07:36 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: Envoy? de mon iPhone > Le 8 avr. 2015 ? 17:51, Matthias Wessendorf a ?crit : > > Again, I doubt that there will be 3k of messages per app, a day. > That would mean your "ESPN Sports News" app would send you 3k messages - joy, he? No, on the graph here you can see that "message1" has been sent to 2400 devices and has been opened by 1250 users , it's pretty realistic , and for the whole week 6 messages has been sent > > I wonder how the charts would look on more realistic data: > 500.000 devices > 1 push message a day (delivered to all 500k) > opened by 250k, same day > > > Now if I sent two messages: Breaking news A, Breaking news B > How would I see how many directly opened "Breaking news A" (or the other one)? > > > >> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante wrote: >> Good idea! take a look: >> >> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >> >> >> >>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc wrote: >>> I wonder if a bar chart (even maybe stacked bar) would not be more clear to show this data ? >>> Wdyt ? >>> >>> Envoy? de mon iPhone >>> >>>> Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : >>>> >>>> Yes, you are right, it should be something like: >>>> >>>> 5 message sent >>>> 3k delivered >>>> 2k open >>>> 4k devices. >>>> >>>> Just change the example. Also the x-axis should be dates. >>>> >>>> Thanks! >>>> >>>> >>>> >>>> >>>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf wrote: >>>>> One thing: I think the numbers on the chart are confusing, and incorrect. >>>>> It's usually not a ton of messages that are sent. that's more like 5 or 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL the damn app. >>>>> Therefore the "app opened due to receiving push" numbers are also not 100% correct here. >>>>> >>>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf wrote: >>>>>> :-) I like that too. >>>>>> >>>>>> But Andres, again, awesome UX ! >>>>>> >>>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc wrote: >>>>>>> >>>>>>> >>>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? wrote: >>>>>>>> Looks good so far, Andres, >>>>>>>> >>>>>>>> you are right, we want to show time-aggregated data, not particular events. >>>>>>>> >>>>>>>> Idea: >>>>>>>> My perspective might be very technical rather then marketing, but a pie chart with Push Network split would be interesting to me. >>>>>>> >>>>>>> +1 (or Donut :) ) >>>>>>>> >>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante napsal: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> With the new data we have I've compared sent vs open messages on a chart for each App: >>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>> (the x axis should be dates) >>>>>>>>> >>>>>>>>> I am wondering if we can generate a ratio that's useful for a marketing person and show a benchmark comparing with other UPS users to know if the users campaign is successful or not. Something like: open/sent or device/open >>>>>>>>> >>>>>>>>> I believe that to show the first and last time a message was open is not very useful. Maybe I am wrong, but, If we want to show an over time chart for each notification we should collect periodical data, for example # of open messages per hour to generate a linear graph that represents a day. >>>>>>>>> >>>>>>>>> What do you think? >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>> >>>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a ?crit : >>>>>>>>>>> >>>>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc wrote: >>>>>>>>>>>> Folks ! >>>>>>>>>>>> >>>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a small POC mainly focused on the backend. To sum up quickly : we want to know how many installations/users has opened the application after that a Push Notification has been touched. >>>>>>>>>>> >>>>>>>>>>> Let me see if I understood. UPS will send a message to the client and when the message be *read* (instead of delivered), the client will send a message back to the UPS saying: "The message was read"? >>>>>>>>>> Yes , but let me be more specific here : us when the app is in the background or not running and that the user "tap" the notification >>>>>>>>>>>> So, the very first thing that had to be done was to give the Push Notification a unique identifier, so that we can track it and do the metrics on it. >>>>>>>>>>> >>>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>>> >>>>>>>>>>>> For that, I have been using an existing model object that we have , the PushMessageInformation[2], and that is currently used to provide information for our dashboard. >>>>>>>>>>>> This object has now some extra fields, like a appOpenCounter etc ... >>>>>>>>>>>> >>>>>>>>>>>> The ID of this PushMessageInformation is now passed into the payload of the Push Message, just before we send it, this way the client library can use this ID to pass extra information to the UPS when a notification is touched. >>>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>> >>>>>>>>>>> The message back (from client to UPS) will be send every time the user _read_ that? >>>>>>>>>> Well normally that will only happen once per installation per Push message >>>>>>>>>>> >>>>>>>>>>>> When the UPS receive the request, it looks for the header and if it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>>> >>>>>>>>>>>> Please note, that for this POC, all is happening on Application level and not on Variant level but that can be easily changed. It depends on how fined grained we want to have these analytics. >>>>>>>>>>>> >>>>>>>>>>>> I did a small screencast that shows this in action : https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>>> >>>>>>>>>>>> The UPS branch containing the changes is here (the 2 latests commits are relevant) : https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>>> >>>>>>>>>>>> The client app is not really relevant since I really hacked badly the app (and the push plugin) ;) , however if interested I may share it. >>>>>>>>>>>> >>>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>>> >>>>>>>>>>>> Sebi >>>>>>>>>>>> >>>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>>> [2] https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> -- Passos >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/2bba1dc1/attachment-0001.html From scm.blanc at gmail.com Wed Apr 8 12:16:05 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 8 Apr 2015 18:16:05 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: I think that the wording confuses you Matthias and I agree it should be different : [image: Displaying IMG_1727.PNG] Instead of "Delivered Messages" and "Open Message" we should have something else, but I have no idea right now tbh :) On Wed, Apr 8, 2015 at 6:07 PM, S?bastien Blanc wrote: > > > Envoy? de mon iPhone > > Le 8 avr. 2015 ? 17:51, Matthias Wessendorf a ?crit : > > Again, I doubt that there will be 3k of messages per app, a day. > That would mean your "ESPN Sports News" app would send you 3k messages - > joy, he? > > No, on the graph here you can see that "message1" has been sent to 2400 > devices and has been opened by 1250 users , it's pretty realistic , and for > the whole week 6 messages has been sent > > > I wonder how the charts would look on more realistic data: > 500.000 devices > 1 push message a day (delivered to all 500k) > opened by 250k, same day > > > Now if I sent two messages: Breaking news A, Breaking news B > How would I see how many directly opened "Breaking news A" (or the other > one)? > > > > On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante > wrote: > >> Good idea! take a look: >> >> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >> >> >> >> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc >> wrote: >> >>> I wonder if a bar chart (even maybe stacked bar) would not be more clear >>> to show this data ? >>> Wdyt ? >>> >>> Envoy? de mon iPhone >>> >>> Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : >>> >>> Yes, you are right, it should be something like: >>> >>> 5 message sent >>> 3k delivered >>> 2k open >>> 4k devices. >>> >>> Just change the example. Also the x-axis should be dates. >>> >>> Thanks! >>> >>> >>> >>> >>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf >>> wrote: >>> >>>> One thing: I think the numbers on the chart are confusing, and >>>> incorrect. >>>> It's usually not a ton of messages that are sent. that's more like 5 or >>>> 10 per day (speaking of vanilla marketing pushes). If more, I'd UNINSTALL >>>> the damn app. >>>> Therefore the "app opened due to receiving push" numbers are also not >>>> 100% correct here. >>>> >>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >>>> wrote: >>>> >>>>> :-) I like that too. >>>>> >>>>> But Andres, again, awesome UX ! >>>>> >>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>> wrote: >>>>>> >>>>>>> Looks good so far, Andres, >>>>>>> >>>>>>> you are right, we want to show time-aggregated data, not particular >>>>>>> events. >>>>>>> >>>>>>> Idea: >>>>>>> My perspective might be very technical rather then marketing, but a >>>>>>> pie chart with Push Network split would be interesting to me. >>>>>>> >>>>>> +1 (or Donut :) ) >>>>>> >>>>>>> >>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante >>>>>>> napsal: >>>>>>> >>>>>>> Hi, >>>>>>>> >>>>>>>> With the new data we have I've compared sent vs open messages on a >>>>>>>> chart for each App: >>>>>>>> >>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>> (the x axis should be dates) >>>>>>>> >>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>> or device/open >>>>>>>> >>>>>>>> I believe that to show the first and last time a message was open >>>>>>>> is not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>>> chart for each notification we should collect periodical data, for example >>>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>>> day. >>>>>>>> >>>>>>>> What do you think? >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Envoy? de mon iPhone >>>>>>>>> >>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>> ?crit : >>>>>>>>> >>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Folks ! >>>>>>>>>> >>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>> Push Notification has been touched. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>>>> >>>>>>>>> >>>>>>>>> Yes , but let me be more specific here : us when the app is in the >>>>>>>>> background or not running and that the user "tap" the notification >>>>>>>>> >>>>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>>>> metrics on it. >>>>>>>>>> >>>>>>>>> >>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>> >>>>>>>>> >>>>>>>>>> For that, I have been using an existing model object that we have >>>>>>>>>> , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>> information for our dashboard. >>>>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>>>> ... >>>>>>>>>> >>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>> notification is touched. >>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>> >>>>>>>>> >>>>>>>>> The message back (from client to UPS) will be send every time the >>>>>>>>> user _read_ that? >>>>>>>>> >>>>>>>>> Well normally that will only happen once per installation per Push >>>>>>>>> message >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> When the UPS receive the request, it looks for the header and if >>>>>>>>>> it exist it updates the existing PushMessageInformation instance. >>>>>>>>>> >>>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>>> >>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>> >>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>> commits are relevant) : >>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>> >>>>>>>>>> The client app is not really relevant since I really hacked badly >>>>>>>>>> the app (and the push plugin) ;) , however if interested I may share it. >>>>>>>>>> >>>>>>>>>> Now, let's discuss :) >>>>>>>>>> >>>>>>>>>> Sebi >>>>>>>>>> >>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>> [2] >>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> -- Passos >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/5c50240a/attachment-0001.html From agalante at redhat.com Wed Apr 8 12:27:35 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 8 Apr 2015 13:27:35 -0300 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: How about "Push notifications" = for the # of notifications sent "Open notifications" = for the ones that where open. Do we always have the same amount of notifications sent than devices registered? in that case Matthias is right and its useless to have both. On Wed, Apr 8, 2015 at 1:16 PM, Sebastien Blanc wrote: > I think that the wording confuses you Matthias and I agree it should be > different : > > [image: Displaying IMG_1727.PNG] > > Instead of "Delivered Messages" and "Open Message" we should have > something else, but I have no idea right now tbh :) > > On Wed, Apr 8, 2015 at 6:07 PM, S?bastien Blanc > wrote: > >> >> >> Envoy? de mon iPhone >> >> Le 8 avr. 2015 ? 17:51, Matthias Wessendorf a ?crit : >> >> Again, I doubt that there will be 3k of messages per app, a day. >> That would mean your "ESPN Sports News" app would send you 3k messages - >> joy, he? >> >> No, on the graph here you can see that "message1" has been sent to 2400 >> devices and has been opened by 1250 users , it's pretty realistic , and for >> the whole week 6 messages has been sent >> >> >> I wonder how the charts would look on more realistic data: >> 500.000 devices >> 1 push message a day (delivered to all 500k) >> opened by 250k, same day >> >> >> Now if I sent two messages: Breaking news A, Breaking news B >> How would I see how many directly opened "Breaking news A" (or the other >> one)? >> >> >> >> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante >> wrote: >> >>> Good idea! take a look: >>> >>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>> >>> >>> >>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc >>> wrote: >>> >>>> I wonder if a bar chart (even maybe stacked bar) would not be more >>>> clear to show this data ? >>>> Wdyt ? >>>> >>>> Envoy? de mon iPhone >>>> >>>> Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : >>>> >>>> Yes, you are right, it should be something like: >>>> >>>> 5 message sent >>>> 3k delivered >>>> 2k open >>>> 4k devices. >>>> >>>> Just change the example. Also the x-axis should be dates. >>>> >>>> Thanks! >>>> >>>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf >>> > wrote: >>>> >>>>> One thing: I think the numbers on the chart are confusing, and >>>>> incorrect. >>>>> It's usually not a ton of messages that are sent. that's more like 5 >>>>> or 10 per day (speaking of vanilla marketing pushes). If more, I'd >>>>> UNINSTALL the damn app. >>>>> Therefore the "app opened due to receiving push" numbers are also not >>>>> 100% correct here. >>>>> >>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >>>> > wrote: >>>>> >>>>>> :-) I like that too. >>>>>> >>>>>> But Andres, again, awesome UX ! >>>>>> >>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>>> wrote: >>>>>>> >>>>>>>> Looks good so far, Andres, >>>>>>>> >>>>>>>> you are right, we want to show time-aggregated data, not particular >>>>>>>> events. >>>>>>>> >>>>>>>> Idea: >>>>>>>> My perspective might be very technical rather then marketing, but a >>>>>>>> pie chart with Push Network split would be interesting to me. >>>>>>>> >>>>>>> +1 (or Donut :) ) >>>>>>> >>>>>>>> >>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante < >>>>>>>> agalante at redhat.com> napsal: >>>>>>>> >>>>>>>> Hi, >>>>>>>>> >>>>>>>>> With the new data we have I've compared sent vs open messages on a >>>>>>>>> chart for each App: >>>>>>>>> >>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>> (the x axis should be dates) >>>>>>>>> >>>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>>> or device/open >>>>>>>>> >>>>>>>>> I believe that to show the first and last time a message was open >>>>>>>>> is not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>>>> chart for each notification we should collect periodical data, for example >>>>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>>>> day. >>>>>>>>> >>>>>>>>> What do you think? >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>> >>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>>> ?crit : >>>>>>>>>> >>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Folks ! >>>>>>>>>>> >>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>>> Push Notification has been touched. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Yes , but let me be more specific here : us when the app is in >>>>>>>>>> the background or not running and that the user "tap" the notification >>>>>>>>>> >>>>>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>>>>> metrics on it. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> For that, I have been using an existing model object that we >>>>>>>>>>> have , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>>> information for our dashboard. >>>>>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>>>>> ... >>>>>>>>>>> >>>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>>> notification is touched. >>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The message back (from client to UPS) will be send every time the >>>>>>>>>> user _read_ that? >>>>>>>>>> >>>>>>>>>> Well normally that will only happen once per installation per >>>>>>>>>> Push message >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> When the UPS receive the request, it looks for the header and if >>>>>>>>>>> it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>> >>>>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>>>> >>>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>> >>>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>>> commits are relevant) : >>>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>> >>>>>>>>>>> The client app is not really relevant since I really hacked >>>>>>>>>>> badly the app (and the push plugin) ;) , however if interested I may share >>>>>>>>>>> it. >>>>>>>>>>> >>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>> >>>>>>>>>>> Sebi >>>>>>>>>>> >>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>> [2] >>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> -- Passos >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/fc80a64b/attachment-0001.html From scm.blanc at gmail.com Wed Apr 8 12:39:50 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 8 Apr 2015 18:39:50 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: On Wed, Apr 8, 2015 at 6:27 PM, Andres Galante wrote: > How about > > "Push notifications" = for the # of notifications sent > No that is still confusing , something like (still bad wording and too long) : number of devices that received the push notifcation > "Open notifications" = for the ones that where open. > That one is okay > > Do we always have the same amount of notifications sent than devices > registered? in that case Matthias is right and its useless to have both. > no, you can 1000 devices registered for a variant but send only to 15 due to some criteria. But that is a bit out of scope for the analytic around a Push Notification, for the graph numbers let's forget the number of registered devices and only show the number of devices that received the push. (so we can compare just with the number of times the app was opened) > > > > > On Wed, Apr 8, 2015 at 1:16 PM, Sebastien Blanc > wrote: > >> I think that the wording confuses you Matthias and I agree it should be >> different : >> >> [image: Displaying IMG_1727.PNG] >> >> Instead of "Delivered Messages" and "Open Message" we should have >> something else, but I have no idea right now tbh :) >> >> On Wed, Apr 8, 2015 at 6:07 PM, S?bastien Blanc >> wrote: >> >>> >>> >>> Envoy? de mon iPhone >>> >>> Le 8 avr. 2015 ? 17:51, Matthias Wessendorf a >>> ?crit : >>> >>> Again, I doubt that there will be 3k of messages per app, a day. >>> That would mean your "ESPN Sports News" app would send you 3k messages - >>> joy, he? >>> >>> No, on the graph here you can see that "message1" has been sent to 2400 >>> devices and has been opened by 1250 users , it's pretty realistic , and for >>> the whole week 6 messages has been sent >>> >>> >>> I wonder how the charts would look on more realistic data: >>> 500.000 devices >>> 1 push message a day (delivered to all 500k) >>> opened by 250k, same day >>> >>> >>> Now if I sent two messages: Breaking news A, Breaking news B >>> How would I see how many directly opened "Breaking news A" (or the other >>> one)? >>> >>> >>> >>> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante >>> wrote: >>> >>>> Good idea! take a look: >>>> >>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc >>>> wrote: >>>> >>>>> I wonder if a bar chart (even maybe stacked bar) would not be more >>>>> clear to show this data ? >>>>> Wdyt ? >>>>> >>>>> Envoy? de mon iPhone >>>>> >>>>> Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : >>>>> >>>>> Yes, you are right, it should be something like: >>>>> >>>>> 5 message sent >>>>> 3k delivered >>>>> 2k open >>>>> 4k devices. >>>>> >>>>> Just change the example. Also the x-axis should be dates. >>>>> >>>>> Thanks! >>>>> >>>>> >>>>> >>>>> >>>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf < >>>>> matzew at apache.org> wrote: >>>>> >>>>>> One thing: I think the numbers on the chart are confusing, and >>>>>> incorrect. >>>>>> It's usually not a ton of messages that are sent. that's more like 5 >>>>>> or 10 per day (speaking of vanilla marketing pushes). If more, I'd >>>>>> UNINSTALL the damn app. >>>>>> Therefore the "app opened due to receiving push" numbers are also not >>>>>> 100% correct here. >>>>>> >>>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf < >>>>>> matzew at apache.org> wrote: >>>>>> >>>>>>> :-) I like that too. >>>>>>> >>>>>>> But Andres, again, awesome UX ! >>>>>>> >>>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>>>> > wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Looks good so far, Andres, >>>>>>>>> >>>>>>>>> you are right, we want to show time-aggregated data, not >>>>>>>>> particular events. >>>>>>>>> >>>>>>>>> Idea: >>>>>>>>> My perspective might be very technical rather then marketing, but >>>>>>>>> a pie chart with Push Network split would be interesting to me. >>>>>>>>> >>>>>>>> +1 (or Donut :) ) >>>>>>>> >>>>>>>>> >>>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante < >>>>>>>>> agalante at redhat.com> napsal: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> With the new data we have I've compared sent vs open messages on >>>>>>>>>> a chart for each App: >>>>>>>>>> >>>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>>> (the x axis should be dates) >>>>>>>>>> >>>>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>>>> or device/open >>>>>>>>>> >>>>>>>>>> I believe that to show the first and last time a message was open >>>>>>>>>> is not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>>>>> chart for each notification we should collect periodical data, for example >>>>>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>>>>> day. >>>>>>>>>> >>>>>>>>>> What do you think? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>>> >>>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>>>> ?crit : >>>>>>>>>>> >>>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Folks ! >>>>>>>>>>>> >>>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>>>> Push Notification has been touched. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Let me see if I understood. UPS will send a message to the >>>>>>>>>>> client and when the message be *read* (instead of delivered), the client >>>>>>>>>>> will send a message back to the UPS saying: "The message was read"? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Yes , but let me be more specific here : us when the app is in >>>>>>>>>>> the background or not running and that the user "tap" the notification >>>>>>>>>>> >>>>>>>>>>> So, the very first thing that had to be done was to give the >>>>>>>>>>>> Push Notification a unique identifier, so that we can track it and do the >>>>>>>>>>>> metrics on it. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> For that, I have been using an existing model object that we >>>>>>>>>>>> have , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>>>> information for our dashboard. >>>>>>>>>>>> This object has now some extra fields, like a appOpenCounter >>>>>>>>>>>> etc ... >>>>>>>>>>>> >>>>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>>>> notification is touched. >>>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> The message back (from client to UPS) will be send every time >>>>>>>>>>> the user _read_ that? >>>>>>>>>>> >>>>>>>>>>> Well normally that will only happen once per installation per >>>>>>>>>>> Push message >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> When the UPS receive the request, it looks for the header and >>>>>>>>>>>> if it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>>> >>>>>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>>>>> >>>>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>>> >>>>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>>>> commits are relevant) : >>>>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>>> >>>>>>>>>>>> The client app is not really relevant since I really hacked >>>>>>>>>>>> badly the app (and the push plugin) ;) , however if interested I may share >>>>>>>>>>>> it. >>>>>>>>>>>> >>>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>>> >>>>>>>>>>>> Sebi >>>>>>>>>>>> >>>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>>> [2] >>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> -- Passos >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at 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 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/840d90e1/attachment-0001.html From matzew at apache.org Wed Apr 8 12:46:19 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Apr 2015 18:46:19 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: On Wed, Apr 8, 2015 at 6:05 PM, Andres Galante wrote: > Do we always successful deliver messages to all registered devices? > no, it's not even us. we just give the payload to the networks. They all (APNS, GCM, Windows) have no SLA for actual delivery. All what we can say is: delivered "payload" to APNs for distribution to n devices Once they open the app, our server is hit, and we know: n devices did receive it > > On Wed, Apr 8, 2015 at 12:51 PM, Matthias Wessendorf > wrote: > >> Again, I doubt that there will be 3k of messages per app, a day. >> That would mean your "ESPN Sports News" app would send you 3k messages - >> joy, he? >> >> I wonder how the charts would look on more realistic data: >> 500.000 devices >> 1 push message a day (delivered to all 500k) >> opened by 250k, same day >> >> >> Now if I sent two messages: Breaking news A, Breaking news B >> How would I see how many directly opened "Breaking news A" (or the other >> one)? >> >> >> >> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante >> wrote: >> >>> Good idea! take a look: >>> >>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>> >>> >>> >>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc >>> wrote: >>> >>>> I wonder if a bar chart (even maybe stacked bar) would not be more >>>> clear to show this data ? >>>> Wdyt ? >>>> >>>> Envoy? de mon iPhone >>>> >>>> Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : >>>> >>>> Yes, you are right, it should be something like: >>>> >>>> 5 message sent >>>> 3k delivered >>>> 2k open >>>> 4k devices. >>>> >>>> Just change the example. Also the x-axis should be dates. >>>> >>>> Thanks! >>>> >>>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf >>> > wrote: >>>> >>>>> One thing: I think the numbers on the chart are confusing, and >>>>> incorrect. >>>>> It's usually not a ton of messages that are sent. that's more like 5 >>>>> or 10 per day (speaking of vanilla marketing pushes). If more, I'd >>>>> UNINSTALL the damn app. >>>>> Therefore the "app opened due to receiving push" numbers are also not >>>>> 100% correct here. >>>>> >>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >>>> > wrote: >>>>> >>>>>> :-) I like that too. >>>>>> >>>>>> But Andres, again, awesome UX ! >>>>>> >>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>>> wrote: >>>>>>> >>>>>>>> Looks good so far, Andres, >>>>>>>> >>>>>>>> you are right, we want to show time-aggregated data, not particular >>>>>>>> events. >>>>>>>> >>>>>>>> Idea: >>>>>>>> My perspective might be very technical rather then marketing, but a >>>>>>>> pie chart with Push Network split would be interesting to me. >>>>>>>> >>>>>>> +1 (or Donut :) ) >>>>>>> >>>>>>>> >>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante < >>>>>>>> agalante at redhat.com> napsal: >>>>>>>> >>>>>>>> Hi, >>>>>>>>> >>>>>>>>> With the new data we have I've compared sent vs open messages on a >>>>>>>>> chart for each App: >>>>>>>>> >>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>> (the x axis should be dates) >>>>>>>>> >>>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>>> or device/open >>>>>>>>> >>>>>>>>> I believe that to show the first and last time a message was open >>>>>>>>> is not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>>>> chart for each notification we should collect periodical data, for example >>>>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>>>> day. >>>>>>>>> >>>>>>>>> What do you think? >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>> >>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>>> ?crit : >>>>>>>>>> >>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Folks ! >>>>>>>>>>> >>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>>> Push Notification has been touched. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Yes , but let me be more specific here : us when the app is in >>>>>>>>>> the background or not running and that the user "tap" the notification >>>>>>>>>> >>>>>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>>>>> metrics on it. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> For that, I have been using an existing model object that we >>>>>>>>>>> have , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>>> information for our dashboard. >>>>>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>>>>> ... >>>>>>>>>>> >>>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>>> notification is touched. >>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The message back (from client to UPS) will be send every time the >>>>>>>>>> user _read_ that? >>>>>>>>>> >>>>>>>>>> Well normally that will only happen once per installation per >>>>>>>>>> Push message >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> When the UPS receive the request, it looks for the header and if >>>>>>>>>>> it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>> >>>>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>>>> >>>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>> >>>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>>> commits are relevant) : >>>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>> >>>>>>>>>>> The client app is not really relevant since I really hacked >>>>>>>>>>> badly the app (and the push plugin) ;) , however if interested I may share >>>>>>>>>>> it. >>>>>>>>>>> >>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>> >>>>>>>>>>> Sebi >>>>>>>>>>> >>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>> [2] >>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> -- Passos >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/4c2c827b/attachment-0001.html From matzew at apache.org Wed Apr 8 12:56:27 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 8 Apr 2015 18:56:27 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: Ahhh!!!!! yes, that _is_ confusing (at least to me) How about: * Delivered Messages -> that's what we currently display with n installations (aka delivered to PUSH_NETWORK for distribution to xyz installations) * Open Messages -> "App opened, due to push" * registered devices -> that means we keep a history of how many devices were registered at what point in time On Wed, Apr 8, 2015 at 6:16 PM, Sebastien Blanc wrote: > I think that the wording confuses you Matthias and I agree it should be > different : > > [image: Displaying IMG_1727.PNG] > > Instead of "Delivered Messages" and "Open Message" we should have > something else, but I have no idea right now tbh :) > > On Wed, Apr 8, 2015 at 6:07 PM, S?bastien Blanc > wrote: > >> >> >> Envoy? de mon iPhone >> >> Le 8 avr. 2015 ? 17:51, Matthias Wessendorf a ?crit : >> >> Again, I doubt that there will be 3k of messages per app, a day. >> That would mean your "ESPN Sports News" app would send you 3k messages - >> joy, he? >> >> No, on the graph here you can see that "message1" has been sent to 2400 >> devices and has been opened by 1250 users , it's pretty realistic , and for >> the whole week 6 messages has been sent >> >> >> I wonder how the charts would look on more realistic data: >> 500.000 devices >> 1 push message a day (delivered to all 500k) >> opened by 250k, same day >> >> >> Now if I sent two messages: Breaking news A, Breaking news B >> How would I see how many directly opened "Breaking news A" (or the other >> one)? >> >> >> >> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante >> wrote: >> >>> Good idea! take a look: >>> >>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>> >>> >>> >>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc >>> wrote: >>> >>>> I wonder if a bar chart (even maybe stacked bar) would not be more >>>> clear to show this data ? >>>> Wdyt ? >>>> >>>> Envoy? de mon iPhone >>>> >>>> Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : >>>> >>>> Yes, you are right, it should be something like: >>>> >>>> 5 message sent >>>> 3k delivered >>>> 2k open >>>> 4k devices. >>>> >>>> Just change the example. Also the x-axis should be dates. >>>> >>>> Thanks! >>>> >>>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf >>> > wrote: >>>> >>>>> One thing: I think the numbers on the chart are confusing, and >>>>> incorrect. >>>>> It's usually not a ton of messages that are sent. that's more like 5 >>>>> or 10 per day (speaking of vanilla marketing pushes). If more, I'd >>>>> UNINSTALL the damn app. >>>>> Therefore the "app opened due to receiving push" numbers are also not >>>>> 100% correct here. >>>>> >>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf >>>> > wrote: >>>>> >>>>>> :-) I like that too. >>>>>> >>>>>> But Andres, again, awesome UX ! >>>>>> >>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>>> wrote: >>>>>>> >>>>>>>> Looks good so far, Andres, >>>>>>>> >>>>>>>> you are right, we want to show time-aggregated data, not particular >>>>>>>> events. >>>>>>>> >>>>>>>> Idea: >>>>>>>> My perspective might be very technical rather then marketing, but a >>>>>>>> pie chart with Push Network split would be interesting to me. >>>>>>>> >>>>>>> +1 (or Donut :) ) >>>>>>> >>>>>>>> >>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante < >>>>>>>> agalante at redhat.com> napsal: >>>>>>>> >>>>>>>> Hi, >>>>>>>>> >>>>>>>>> With the new data we have I've compared sent vs open messages on a >>>>>>>>> chart for each App: >>>>>>>>> >>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>> (the x axis should be dates) >>>>>>>>> >>>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>>> or device/open >>>>>>>>> >>>>>>>>> I believe that to show the first and last time a message was open >>>>>>>>> is not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>>>> chart for each notification we should collect periodical data, for example >>>>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>>>> day. >>>>>>>>> >>>>>>>>> What do you think? >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>> >>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>>> ?crit : >>>>>>>>>> >>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Folks ! >>>>>>>>>>> >>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>>> Push Notification has been touched. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Let me see if I understood. UPS will send a message to the client >>>>>>>>>> and when the message be *read* (instead of delivered), the client will send >>>>>>>>>> a message back to the UPS saying: "The message was read"? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Yes , but let me be more specific here : us when the app is in >>>>>>>>>> the background or not running and that the user "tap" the notification >>>>>>>>>> >>>>>>>>>> So, the very first thing that had to be done was to give the Push >>>>>>>>>>> Notification a unique identifier, so that we can track it and do the >>>>>>>>>>> metrics on it. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> For that, I have been using an existing model object that we >>>>>>>>>>> have , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>>> information for our dashboard. >>>>>>>>>>> This object has now some extra fields, like a appOpenCounter etc >>>>>>>>>>> ... >>>>>>>>>>> >>>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>>> notification is touched. >>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The message back (from client to UPS) will be send every time the >>>>>>>>>> user _read_ that? >>>>>>>>>> >>>>>>>>>> Well normally that will only happen once per installation per >>>>>>>>>> Push message >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> When the UPS receive the request, it looks for the header and if >>>>>>>>>>> it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>> >>>>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>>>> >>>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>> >>>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>>> commits are relevant) : >>>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>> >>>>>>>>>>> The client app is not really relevant since I really hacked >>>>>>>>>>> badly the app (and the push plugin) ;) , however if interested I may share >>>>>>>>>>> it. >>>>>>>>>>> >>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>> >>>>>>>>>>> Sebi >>>>>>>>>>> >>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>> [2] >>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> -- Passos >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/f6fe5b19/attachment-0001.html From agalante at redhat.com Wed Apr 8 12:57:57 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 8 Apr 2015 13:57:57 -0300 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: Sebi, I just change the demo. I now understand what you mean, and you are right its hard to explain it in a short word. If we want we can ask someone from marketing, they have a hole sub team dedicated to writing. Parse uses "Push Notifications" http://blog.parse.com/2013/03/18/introducing-push-analytics-improved-insight-into-push-campaigns/ Urban Airship uses "Total Pushes sent" http://urbanairship.com/products/mobile-analytics On Wed, Apr 8, 2015 at 1:46 PM, Matthias Wessendorf wrote: > > > On Wed, Apr 8, 2015 at 6:05 PM, Andres Galante > wrote: > >> Do we always successful deliver messages to all registered devices? >> > > no, it's not even us. we just give the payload to the networks. They all > (APNS, GCM, Windows) have no SLA for actual delivery. > > All what we can say is: > delivered "payload" to APNs for distribution to n devices > > Once they open the app, our server is hit, and we know: n devices did > receive it > > >> >> On Wed, Apr 8, 2015 at 12:51 PM, Matthias Wessendorf >> wrote: >> >>> Again, I doubt that there will be 3k of messages per app, a day. >>> That would mean your "ESPN Sports News" app would send you 3k messages - >>> joy, he? >>> >>> I wonder how the charts would look on more realistic data: >>> 500.000 devices >>> 1 push message a day (delivered to all 500k) >>> opened by 250k, same day >>> >>> >>> Now if I sent two messages: Breaking news A, Breaking news B >>> How would I see how many directly opened "Breaking news A" (or the other >>> one)? >>> >>> >>> >>> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante >>> wrote: >>> >>>> Good idea! take a look: >>>> >>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc >>>> wrote: >>>> >>>>> I wonder if a bar chart (even maybe stacked bar) would not be more >>>>> clear to show this data ? >>>>> Wdyt ? >>>>> >>>>> Envoy? de mon iPhone >>>>> >>>>> Le 8 avr. 2015 ? 15:44, Andres Galante a ?crit : >>>>> >>>>> Yes, you are right, it should be something like: >>>>> >>>>> 5 message sent >>>>> 3k delivered >>>>> 2k open >>>>> 4k devices. >>>>> >>>>> Just change the example. Also the x-axis should be dates. >>>>> >>>>> Thanks! >>>>> >>>>> >>>>> >>>>> >>>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf < >>>>> matzew at apache.org> wrote: >>>>> >>>>>> One thing: I think the numbers on the chart are confusing, and >>>>>> incorrect. >>>>>> It's usually not a ton of messages that are sent. that's more like 5 >>>>>> or 10 per day (speaking of vanilla marketing pushes). If more, I'd >>>>>> UNINSTALL the damn app. >>>>>> Therefore the "app opened due to receiving push" numbers are also not >>>>>> 100% correct here. >>>>>> >>>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf < >>>>>> matzew at apache.org> wrote: >>>>>> >>>>>>> :-) I like that too. >>>>>>> >>>>>>> But Andres, again, awesome UX ! >>>>>>> >>>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc >>>>>> > wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Looks good so far, Andres, >>>>>>>>> >>>>>>>>> you are right, we want to show time-aggregated data, not >>>>>>>>> particular events. >>>>>>>>> >>>>>>>>> Idea: >>>>>>>>> My perspective might be very technical rather then marketing, but >>>>>>>>> a pie chart with Push Network split would be interesting to me. >>>>>>>>> >>>>>>>> +1 (or Donut :) ) >>>>>>>> >>>>>>>>> >>>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante < >>>>>>>>> agalante at redhat.com> napsal: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> With the new data we have I've compared sent vs open messages on >>>>>>>>>> a chart for each App: >>>>>>>>>> >>>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>>> (the x axis should be dates) >>>>>>>>>> >>>>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>>>> or device/open >>>>>>>>>> >>>>>>>>>> I believe that to show the first and last time a message was open >>>>>>>>>> is not very useful. Maybe I am wrong, but, If we want to show an over time >>>>>>>>>> chart for each notification we should collect periodical data, for example >>>>>>>>>> # of open messages per hour to generate a linear graph that represents a >>>>>>>>>> day. >>>>>>>>>> >>>>>>>>>> What do you think? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>>> >>>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>>>> ?crit : >>>>>>>>>>> >>>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Folks ! >>>>>>>>>>>> >>>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started a >>>>>>>>>>>> small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>>>> Push Notification has been touched. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Let me see if I understood. UPS will send a message to the >>>>>>>>>>> client and when the message be *read* (instead of delivered), the client >>>>>>>>>>> will send a message back to the UPS saying: "The message was read"? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Yes , but let me be more specific here : us when the app is in >>>>>>>>>>> the background or not running and that the user "tap" the notification >>>>>>>>>>> >>>>>>>>>>> So, the very first thing that had to be done was to give the >>>>>>>>>>>> Push Notification a unique identifier, so that we can track it and do the >>>>>>>>>>>> metrics on it. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> For that, I have been using an existing model object that we >>>>>>>>>>>> have , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>>>> information for our dashboard. >>>>>>>>>>>> This object has now some extra fields, like a appOpenCounter >>>>>>>>>>>> etc ... >>>>>>>>>>>> >>>>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>>>> notification is touched. >>>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> The message back (from client to UPS) will be send every time >>>>>>>>>>> the user _read_ that? >>>>>>>>>>> >>>>>>>>>>> Well normally that will only happen once per installation per >>>>>>>>>>> Push message >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> When the UPS receive the request, it looks for the header and >>>>>>>>>>>> if it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>>> >>>>>>>>>>>> Please note, that for this POC, all is happening on Application >>>>>>>>>>>> level and not on Variant level but that can be easily changed. It depends >>>>>>>>>>>> on how fined grained we want to have these analytics. >>>>>>>>>>>> >>>>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>>> >>>>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>>>> commits are relevant) : >>>>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>>> >>>>>>>>>>>> The client app is not really relevant since I really hacked >>>>>>>>>>>> badly the app (and the push plugin) ;) , however if interested I may share >>>>>>>>>>>> it. >>>>>>>>>>>> >>>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>>> >>>>>>>>>>>> Sebi >>>>>>>>>>>> >>>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>>> [2] >>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> -- Passos >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at 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 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150408/98fe0b04/attachment-0001.html From scm.blanc at gmail.com Thu Apr 9 03:15:31 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 9 Apr 2015 09:15:31 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: On Wed, Apr 8, 2015 at 6:57 PM, Andres Galante wrote: > Sebi, I just change the demo. > I like it more, but I wonder about the stacked bars again, not sure it is the best visually, maybe having the 2 bar side-by-side like here http://c3js.org/samples/chart_bar.html or what I really would like to see but I could not find it in c3 is : the 2 bars superposed a bit like this http://i.stack.imgur.com/0hjX7.png > > I now understand what you mean, and you are right its hard to explain it > in a short word. > Yes , what about "Sent out to devices" ? > If we want we can ask someone from marketing, they have a hole sub team > dedicated to writing. > > Parse uses "Push Notifications" > > http://blog.parse.com/2013/03/18/introducing-push-analytics-improved-insight-into-push-campaigns/ > > Urban Airship uses "Total Pushes sent" > http://urbanairship.com/products/mobile-analytics > > > > On Wed, Apr 8, 2015 at 1:46 PM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Apr 8, 2015 at 6:05 PM, Andres Galante >> wrote: >> >>> Do we always successful deliver messages to all registered devices? >>> >> >> no, it's not even us. we just give the payload to the networks. They all >> (APNS, GCM, Windows) have no SLA for actual delivery. >> >> All what we can say is: >> delivered "payload" to APNs for distribution to n devices >> >> Once they open the app, our server is hit, and we know: n devices did >> receive it >> >> >>> >>> On Wed, Apr 8, 2015 at 12:51 PM, Matthias Wessendorf >>> wrote: >>> >>>> Again, I doubt that there will be 3k of messages per app, a day. >>>> That would mean your "ESPN Sports News" app would send you 3k messages >>>> - joy, he? >>>> >>>> I wonder how the charts would look on more realistic data: >>>> 500.000 devices >>>> 1 push message a day (delivered to all 500k) >>>> opened by 250k, same day >>>> >>>> >>>> Now if I sent two messages: Breaking news A, Breaking news B >>>> How would I see how many directly opened "Breaking news A" (or the >>>> other one)? >>>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante >>>> wrote: >>>> >>>>> Good idea! take a look: >>>>> >>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>> >>>>> >>>>> >>>>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc >>>>> wrote: >>>>> >>>>>> I wonder if a bar chart (even maybe stacked bar) would not be more >>>>>> clear to show this data ? >>>>>> Wdyt ? >>>>>> >>>>>> Envoy? de mon iPhone >>>>>> >>>>>> Le 8 avr. 2015 ? 15:44, Andres Galante a >>>>>> ?crit : >>>>>> >>>>>> Yes, you are right, it should be something like: >>>>>> >>>>>> 5 message sent >>>>>> 3k delivered >>>>>> 2k open >>>>>> 4k devices. >>>>>> >>>>>> Just change the example. Also the x-axis should be dates. >>>>>> >>>>>> Thanks! >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf < >>>>>> matzew at apache.org> wrote: >>>>>> >>>>>>> One thing: I think the numbers on the chart are confusing, and >>>>>>> incorrect. >>>>>>> It's usually not a ton of messages that are sent. that's more like 5 >>>>>>> or 10 per day (speaking of vanilla marketing pushes). If more, I'd >>>>>>> UNINSTALL the damn app. >>>>>>> Therefore the "app opened due to receiving push" numbers are also >>>>>>> not 100% correct here. >>>>>>> >>>>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf < >>>>>>> matzew at apache.org> wrote: >>>>>>> >>>>>>>> :-) I like that too. >>>>>>>> >>>>>>>> But Andres, again, awesome UX ! >>>>>>>> >>>>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc < >>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Looks good so far, Andres, >>>>>>>>>> >>>>>>>>>> you are right, we want to show time-aggregated data, not >>>>>>>>>> particular events. >>>>>>>>>> >>>>>>>>>> Idea: >>>>>>>>>> My perspective might be very technical rather then marketing, but >>>>>>>>>> a pie chart with Push Network split would be interesting to me. >>>>>>>>>> >>>>>>>>> +1 (or Donut :) ) >>>>>>>>> >>>>>>>>>> >>>>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante < >>>>>>>>>> agalante at redhat.com> napsal: >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> With the new data we have I've compared sent vs open messages on >>>>>>>>>>> a chart for each App: >>>>>>>>>>> >>>>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>>>> (the x axis should be dates) >>>>>>>>>>> >>>>>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>>>>> or device/open >>>>>>>>>>> >>>>>>>>>>> I believe that to show the first and last time a message was >>>>>>>>>>> open is not very useful. Maybe I am wrong, but, If we want to show an over >>>>>>>>>>> time chart for each notification we should collect periodical data, for >>>>>>>>>>> example # of open messages per hour to generate a linear graph that >>>>>>>>>>> represents a day. >>>>>>>>>>> >>>>>>>>>>> What do you think? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>>>> >>>>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>>>>> ?crit : >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Folks ! >>>>>>>>>>>>> >>>>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started >>>>>>>>>>>>> a small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>>>>> Push Notification has been touched. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Let me see if I understood. UPS will send a message to the >>>>>>>>>>>> client and when the message be *read* (instead of delivered), the client >>>>>>>>>>>> will send a message back to the UPS saying: "The message was read"? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Yes , but let me be more specific here : us when the app is in >>>>>>>>>>>> the background or not running and that the user "tap" the notification >>>>>>>>>>>> >>>>>>>>>>>> So, the very first thing that had to be done was to give the >>>>>>>>>>>>> Push Notification a unique identifier, so that we can track it and do the >>>>>>>>>>>>> metrics on it. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> For that, I have been using an existing model object that we >>>>>>>>>>>>> have , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>>>>> information for our dashboard. >>>>>>>>>>>>> This object has now some extra fields, like a appOpenCounter >>>>>>>>>>>>> etc ... >>>>>>>>>>>>> >>>>>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>>>>> notification is touched. >>>>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> The message back (from client to UPS) will be send every time >>>>>>>>>>>> the user _read_ that? >>>>>>>>>>>> >>>>>>>>>>>> Well normally that will only happen once per installation per >>>>>>>>>>>> Push message >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> When the UPS receive the request, it looks for the header and >>>>>>>>>>>>> if it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>>>> >>>>>>>>>>>>> Please note, that for this POC, all is happening on >>>>>>>>>>>>> Application level and not on Variant level but that can be easily changed. >>>>>>>>>>>>> It depends on how fined grained we want to have these analytics. >>>>>>>>>>>>> >>>>>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>>>> >>>>>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>>>>> commits are relevant) : >>>>>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>>>> >>>>>>>>>>>>> The client app is not really relevant since I really hacked >>>>>>>>>>>>> badly the app (and the push plugin) ;) , however if interested I may share >>>>>>>>>>>>> it. >>>>>>>>>>>>> >>>>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>>>> >>>>>>>>>>>>> Sebi >>>>>>>>>>>>> >>>>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>>>> [2] >>>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> -- Passos >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Matthias Wessendorf >>>>>>> >>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150409/b8dce682/attachment-0001.html From matzew at apache.org Thu Apr 9 03:27:17 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 9 Apr 2015 09:27:17 +0200 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: since APNs, and GCM can be used for Desktop and browsers, I don't like the word device here. It's more an installation (that's the origin of this name actually) On Thu, Apr 9, 2015 at 9:15 AM, Sebastien Blanc wrote: > > > On Wed, Apr 8, 2015 at 6:57 PM, Andres Galante > wrote: > >> Sebi, I just change the demo. >> > I like it more, but I wonder about the stacked bars again, not sure it is > the best visually, maybe having the 2 bar side-by-side like here > http://c3js.org/samples/chart_bar.html or what I really would like to see > but I could not find it in c3 is : the 2 bars superposed a bit like this > http://i.stack.imgur.com/0hjX7.png > >> >> I now understand what you mean, and you are right its hard to explain it >> in a short word. >> > Yes , what about "Sent out to devices" ? > >> If we want we can ask someone from marketing, they have a hole sub team >> dedicated to writing. >> >> Parse uses "Push Notifications" >> >> http://blog.parse.com/2013/03/18/introducing-push-analytics-improved-insight-into-push-campaigns/ >> >> Urban Airship uses "Total Pushes sent" >> http://urbanairship.com/products/mobile-analytics >> >> >> >> On Wed, Apr 8, 2015 at 1:46 PM, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Wed, Apr 8, 2015 at 6:05 PM, Andres Galante >>> wrote: >>> >>>> Do we always successful deliver messages to all registered devices? >>>> >>> >>> no, it's not even us. we just give the payload to the networks. They all >>> (APNS, GCM, Windows) have no SLA for actual delivery. >>> >>> All what we can say is: >>> delivered "payload" to APNs for distribution to n devices >>> >>> Once they open the app, our server is hit, and we know: n devices did >>> receive it >>> >>> >>>> >>>> On Wed, Apr 8, 2015 at 12:51 PM, Matthias Wessendorf >>> > wrote: >>>> >>>>> Again, I doubt that there will be 3k of messages per app, a day. >>>>> That would mean your "ESPN Sports News" app would send you 3k messages >>>>> - joy, he? >>>>> >>>>> I wonder how the charts would look on more realistic data: >>>>> 500.000 devices >>>>> 1 push message a day (delivered to all 500k) >>>>> opened by 250k, same day >>>>> >>>>> >>>>> Now if I sent two messages: Breaking news A, Breaking news B >>>>> How would I see how many directly opened "Breaking news A" (or the >>>>> other one)? >>>>> >>>>> >>>>> >>>>> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante >>>>> wrote: >>>>> >>>>>> Good idea! take a look: >>>>>> >>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc >>>>> > wrote: >>>>>> >>>>>>> I wonder if a bar chart (even maybe stacked bar) would not be more >>>>>>> clear to show this data ? >>>>>>> Wdyt ? >>>>>>> >>>>>>> Envoy? de mon iPhone >>>>>>> >>>>>>> Le 8 avr. 2015 ? 15:44, Andres Galante a >>>>>>> ?crit : >>>>>>> >>>>>>> Yes, you are right, it should be something like: >>>>>>> >>>>>>> 5 message sent >>>>>>> 3k delivered >>>>>>> 2k open >>>>>>> 4k devices. >>>>>>> >>>>>>> Just change the example. Also the x-axis should be dates. >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf < >>>>>>> matzew at apache.org> wrote: >>>>>>> >>>>>>>> One thing: I think the numbers on the chart are confusing, and >>>>>>>> incorrect. >>>>>>>> It's usually not a ton of messages that are sent. that's more like >>>>>>>> 5 or 10 per day (speaking of vanilla marketing pushes). If more, I'd >>>>>>>> UNINSTALL the damn app. >>>>>>>> Therefore the "app opened due to receiving push" numbers are also >>>>>>>> not 100% correct here. >>>>>>>> >>>>>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf < >>>>>>>> matzew at apache.org> wrote: >>>>>>>> >>>>>>>>> :-) I like that too. >>>>>>>>> >>>>>>>>> But Andres, again, awesome UX ! >>>>>>>>> >>>>>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc < >>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Looks good so far, Andres, >>>>>>>>>>> >>>>>>>>>>> you are right, we want to show time-aggregated data, not >>>>>>>>>>> particular events. >>>>>>>>>>> >>>>>>>>>>> Idea: >>>>>>>>>>> My perspective might be very technical rather then marketing, >>>>>>>>>>> but a pie chart with Push Network split would be interesting to me. >>>>>>>>>>> >>>>>>>>>> +1 (or Donut :) ) >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante < >>>>>>>>>>> agalante at redhat.com> napsal: >>>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> With the new data we have I've compared sent vs open messages >>>>>>>>>>>> on a chart for each App: >>>>>>>>>>>> >>>>>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>>>>> (the x axis should be dates) >>>>>>>>>>>> >>>>>>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>>>>>> or device/open >>>>>>>>>>>> >>>>>>>>>>>> I believe that to show the first and last time a message was >>>>>>>>>>>> open is not very useful. Maybe I am wrong, but, If we want to show an over >>>>>>>>>>>> time chart for each notification we should collect periodical data, for >>>>>>>>>>>> example # of open messages per hour to generate a linear graph that >>>>>>>>>>>> represents a day. >>>>>>>>>>>> >>>>>>>>>>>> What do you think? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>>>>> >>>>>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos a >>>>>>>>>>>>> ?crit : >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Folks ! >>>>>>>>>>>>>> >>>>>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I started >>>>>>>>>>>>>> a small POC mainly focused on the backend. To sum up quickly : we want to >>>>>>>>>>>>>> know how many installations/users has opened the application after that a >>>>>>>>>>>>>> Push Notification has been touched. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Let me see if I understood. UPS will send a message to the >>>>>>>>>>>>> client and when the message be *read* (instead of delivered), the client >>>>>>>>>>>>> will send a message back to the UPS saying: "The message was read"? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Yes , but let me be more specific here : us when the app is in >>>>>>>>>>>>> the background or not running and that the user "tap" the notification >>>>>>>>>>>>> >>>>>>>>>>>>> So, the very first thing that had to be done was to give the >>>>>>>>>>>>>> Push Notification a unique identifier, so that we can track it and do the >>>>>>>>>>>>>> metrics on it. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> For that, I have been using an existing model object that we >>>>>>>>>>>>>> have , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>>>>>> information for our dashboard. >>>>>>>>>>>>>> This object has now some extra fields, like a appOpenCounter >>>>>>>>>>>>>> etc ... >>>>>>>>>>>>>> >>>>>>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>>>>>> notification is touched. >>>>>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> The message back (from client to UPS) will be send every time >>>>>>>>>>>>> the user _read_ that? >>>>>>>>>>>>> >>>>>>>>>>>>> Well normally that will only happen once per installation per >>>>>>>>>>>>> Push message >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> When the UPS receive the request, it looks for the header and >>>>>>>>>>>>>> if it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Please note, that for this POC, all is happening on >>>>>>>>>>>>>> Application level and not on Variant level but that can be easily changed. >>>>>>>>>>>>>> It depends on how fined grained we want to have these analytics. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>>>>> >>>>>>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>>>>>> commits are relevant) : >>>>>>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>>>>> >>>>>>>>>>>>>> The client app is not really relevant since I really hacked >>>>>>>>>>>>>> badly the app (and the push plugin) ;) , however if interested I may share >>>>>>>>>>>>>> it. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>>>>> >>>>>>>>>>>>>> Sebi >>>>>>>>>>>>>> >>>>>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>>>>> [2] >>>>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> -- Passos >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Matthias Wessendorf >>>>>>>> >>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150409/d201aaba/attachment-0001.html From matzew at apache.org Thu Apr 9 03:46:39 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 9 Apr 2015 09:46:39 +0200 Subject: [aerogear-dev] License Key for AeroGear UnifiedPush Server (was: Re: do we want swagger for REST endpoint documentation?) Message-ID: Hi Miredot team, for the AeroGear UnifiedPush Server ([1], [2]), we would like to start using miredot for our jaxrs endpoints ([3]). The Maven groupId is "org.jboss.aerogear.unifiedpush" and the artifactId is "unifiedpush-jaxrs". Currently we are using jaxrs-doclet ([4]), but we are not happy with that. The Server is an OpenSource project with regular releases, and it is licensed under the Apache 2.0 license. For this project we would like to request an opensource license. Thanks, Matthias [1] https://aerogear.org/push/#unifiedpush [2] https://aerogear.org/docs/unifiedpush/ups_userguide/index/ [3] https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/jaxrs [4] https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/overview-index.html On Tue, Apr 7, 2015 at 1:57 PM, Idel Pivnitskiy wrote: > Ok, so I will wait a license key from you. > > 2015-04-07 14:55 GMT+03:00 Matthias Wessendorf : > >> >> >> On Tue, Apr 7, 2015 at 1:42 PM, Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> wrote: >> >>> IMO, custom annotations force you to duplicate code and documentation. >>> Take a look at a more detailed example: >>> >>> @POST >>> @Path("/{petId}") >>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>> @ApiOperation(value = "Updates a pet in the store with form data", >>> consumes = MediaType.APPLICATION_FORM_URLENCODED) >>> @ApiResponses(value = { >>> @ApiResponse(code = 405, message = "Invalid input")}) >>> public Response updatePetWithForm ( >>> @ApiParam(value = "ID of pet that needs to be updated", required = true)@PathParam("petId") String petId, >>> @ApiParam(value = "Updated name of the pet", required = false)@FormParam("name") String name, >>> @ApiParam(value = "Updated status of the pet", required = false)@FormParam("status") String status) { >>> System.out.println(name); >>> System.out.println(status); >>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>> } >>> >>> >>> It is much more simple with MireDot (also because javadoc could be >>> generated automatically by IDE): >>> >>> /** >>> * Updates a pet in the store with form data. >>> * >>> * @param petId ID of pet that needs to be updated >>> * @param name Updated name of the pet >>> * @param status Updated status of the pet >>> */ >>> @POST >>> @Path("/{petId}") >>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>> public Response updatePetWithForm (@PathParam("petId") String petId, >>> @FormParam("name") String name, >>> @FormParam("status") String status) { >>> System.out.println(name); >>> System.out.println(status); >>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>> } >>> >>> Really, I don't know why Swagger is so popular :) >>> >> >> That's quite a difference, and less verbose and less of duplication >> (DRY). So I'd say, let's try Miredot :-) >> >> Thanks for the valuable info, Idel! >> >> -Matthias >> >> >>> >>> 2015-04-07 14:11 GMT+03:00 Matthias Wessendorf : >>> >>>> >>>> >>>> On Tue, Apr 7, 2015 at 12:56 PM, Idel Pivnitskiy < >>>> idel.pivnitskiy at gmail.com> wrote: >>>> >>>>> Yes, Swagger can generate doc on the fly, but Swagger use its own >>>>> annotations instead of parse JAX-RS annotations and javadoc, like MireDot. >>>>> >>>> >>>> Ok, I think I have not a huge concern against custom annotations, >>>> especially due to the wide adoption of Swagger. >>>> I guess it's just a very tiny JAR, that contains the annotations, right? >>>> >>>> (+ the build time tool dependency for processing) >>>> >>>> >>>>> What about licence: Apache Tika, for example, uses pro version of >>>>> MireDot >>>>> >>>>> >>>>> https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 >>>>> >>>> >>>> Thanks for the example, that's helpful >>>> >>>> >>>>> >>>>> >>>>> 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : >>>>> >>>>>> Swagger allows doc on the source as well, right ? Just wondering. >>>>>> >>>>>> REgarding license, I need to double check on that before... >>>>>> >>>>>> On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < >>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>> >>>>>>> Matthias, >>>>>>> >>>>>>> Sure, I will work on it. >>>>>>> But I think that it would be better if you request a license [1] on >>>>>>> your email and forward it to me. >>>>>>> It won't be a problem to use a free version, but pro version has a >>>>>>> very cool features, like: >>>>>>> >>>>>>> - Display javadoc comments for the fields of json payloads and >>>>>>> enums >>>>>>> - JSON field documentation >>>>>>> - Type replacement (custom serialisation, JSON types) >>>>>>> >>>>>>> Please, request a li >>>>>>> >>>>>>> [1] http://miredot.com/price/ >>>>>>> >>>>>>> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >>>>>>> >>>>>>>> Idel, >>>>>>>> >>>>>>>> would you mind to create a branch for us, so we can investigate the >>>>>>>> MireDot solution? also the build should be working w/ JDK8. >>>>>>>> >>>>>>>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it >>>>>>>> does not really use any fancy annotations (e.g. see [2]) - that's why we >>>>>>>> picked it. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> Matthias >>>>>>>> >>>>>>>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>>>>>>> [2] >>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>>>> >>>>>>>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I agree with Idel that DRY approach in Miredot's case seems more >>>>>>>>> appealing. >>>>>>>>> >>>>>>>>> They offer basic docs generation in Free version, but also Pro >>>>>>>>> version for open-source projects under conditions that Aerogear meets [1]. >>>>>>>>> >>>>>>>>> ~ Lukas >>>>>>>>> >>>>>>>>> [1] http://www.miredot.com/price/ >>>>>>>>> >>>>>>>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>>>>>>> idel.pivnitskiy at gmail.com> napsal: >>>>>>>>> >>>>>>>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>>>>>>> http://www.miredot.com/ >>>>>>>>>> >>>>>>>>>> With MireDot you do not need to use additional annotations, like >>>>>>>>>> @Api: >>>>>>>>>> >>>>>>>>>> @Path("/pet") >>>>>>>>>> @Api(value = "/pet", description = "Operations about pets") >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>>>>>>> >>>>>>>>>> /** >>>>>>>>>> * Operations about pets >>>>>>>>>> */ >>>>>>>>>> @Path("/pet") >>>>>>>>>> >>>>>>>>>> and generate beautiful and user friendly documentation, like >>>>>>>>>> this: http://www.miredot.com/exampledocs/ >>>>>>>>>> Swagger example: http://petstore.swagger.io/ >>>>>>>>>> >>>>>>>>>> And MireDot is free for open source projects! >>>>>>>>>> >>>>>>>>>> Think about this alternative for Swagger. I'm able to prepare >>>>>>>>>> Pull Request for UPS next week. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf >>>>>>>>>> : >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>>>>>>> >>>>>>>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>>>>>>> > endpoints, and >>>>>>>>>>>> > it's really handy. >>>>>>>>>>>> >>>>>>>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from >>>>>>>>>>>> JAX-RS + >>>>>>>>>>>> Swagger annotations. >>>>>>>>>>>> In Hawkular we are basically doing the same, but with a >>>>>>>>>>>> different >>>>>>>>>>>> annotation processor. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> +1000 >>>>>>>>>>> >>>>>>>>>>> we are, atm, doing similar: >>>>>>>>>>> source >>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/ >>>>>>>>>>> blob/master/jaxrs/src/main/java/org/jboss/aerogear/ >>>>>>>>>>> unifiedpush/rest/sender/PushNotificationSenderEndpoint >>>>>>>>>>> .java#L99-L102 >>>>>>>>>>> result: >>>>>>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush- >>>>>>>>>>> rest/sender/index.html#POST >>>>>>>>>>> >>>>>>>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to >>>>>>>>>>> change here ;-) >>>>>>>>>>> So, I am all for using Swagger annotations on the code to >>>>>>>>>>> generate the HTML docs :-) >>>>>>>>>>> >>>>>>>>>>> Greetings, >>>>>>>>>>> Matthias >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> I personally think the best is really to have the annotations >>>>>>>>>>>> in the >>>>>>>>>>>> source and not trying >>>>>>>>>>>> to update a separate .yml file, as the latter usually is much >>>>>>>>>>>> easier >>>>>>>>>>>> forgotten. >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at 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 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Best regards, >>>>>>>>>> Idel Pivnitskiy >>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>> Twitter: @idelpivnitskiy >>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at 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 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Idel Pivnitskiy >>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>> Twitter: @idelpivnitskiy >>>>>>> GitHub: @idelpivnitskiy >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Best regards, > Idel Pivnitskiy > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150409/fc388540/attachment-0001.html From matzew at apache.org Thu Apr 9 04:14:18 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 9 Apr 2015 10:14:18 +0200 Subject: [aerogear-dev] Fwd: License Key for AeroGear UnifiedPush Server (was: Re: do we want swagger for REST endpoint documentation?) In-Reply-To: <5526332B.3040309@miredot.com> References: <5526332B.3040309@miredot.com> Message-ID: Hi Yves, thanks a lot! Idel, below is the license key - I saw (looking at your Tika link) it needs to be included on the pom.xml file. Cheers, Matthias ---------- Forwarded message ---------- From: Yves Vandewoude Date: Thu, Apr 9, 2015 at 10:07 AM Subject: Re: License Key for AeroGear UnifiedPush Server (was: Re: [aerogear-dev] do we want swagger for REST endpoint documentation?) To: Matthias Wessendorf Hello Matthias, The licence key for the AeroGear UnifiedPush Server project is: cHJvamVjdHxvcmcuamJvc3MuYWVyb2dlYXIudW5pZmllZHB1c2gudW5pZmllZHB1c2gtamF4cnN8MjAxNy0wNS0wMXx0cnVlfC0xI01Dd0NGQitaa0VVRVlsaU9LQjljR2h5TWNSWm1VMTREQWhRbUlHOXY3MExCR0FoT2FubklFSER2SWl1OVZnPT0= It is valid for two years (until May 1st 2017) for org.jboss.aerogear.unifiedpush / unifiedpush-jaxrs After that, you are free to request a new licence key. We continuously aim to improve our tool, so do not hesitate to contact us if you have any questions or remarks. Support questions are best sent to support at miredot.com, since they are dealt with by a team instead of just me :) Kind regards, Yves Matthias Wessendorf schreef op 9/04/2015 om 9:46: Hi Miredot team, for the AeroGear UnifiedPush Server ([1], [2]), we would like to start using miredot for our jaxrs endpoints ([3]). The Maven groupId is "org.jboss.aerogear.unifiedpush" and the artifactId is "unifiedpush-jaxrs". Currently we are using jaxrs-doclet ([4]), but we are not happy with that. The Server is an OpenSource project with regular releases, and it is licensed under the Apache 2.0 license. For this project we would like to request an opensource license. Thanks, Matthias [1] https://aerogear.org/push/#unifiedpush [2] https://aerogear.org/docs/unifiedpush/ups_userguide/index/ [3] https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/jaxrs [4] https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/overview-index.html On Tue, Apr 7, 2015 at 1:57 PM, Idel Pivnitskiy wrote: > Ok, so I will wait a license key from you. > > 2015-04-07 14:55 GMT+03:00 Matthias Wessendorf : > >> >> >> On Tue, Apr 7, 2015 at 1:42 PM, Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> wrote: >> >>> IMO, custom annotations force you to duplicate code and documentation. >>> Take a look at a more detailed example: >>> >>> @POST >>> @Path("/{petId}") >>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>> @ApiOperation(value = "Updates a pet in the store with form data", >>> consumes = MediaType.APPLICATION_FORM_URLENCODED) >>> @ApiResponses(value = { >>> @ApiResponse(code = 405, message = "Invalid input")}) >>> public Response updatePetWithForm ( >>> @ApiParam(value = "ID of pet that needs to be updated", required = true)@PathParam("petId") String petId, >>> @ApiParam(value = "Updated name of the pet", required = false)@FormParam("name") String name, >>> @ApiParam(value = "Updated status of the pet", required = false)@FormParam("status") String status) { >>> System.out.println(name); >>> System.out.println(status); >>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>> } >>> >>> It is much more simple with MireDot (also because javadoc could be >>> generated automatically by IDE): >>> >>> /** >>> * Updates a pet in the store with form data. >>> * >>> * @param petId ID of pet that needs to be updated >>> * @param name Updated name of the pet >>> * @param status Updated status of the pet >>> */ >>> @POST >>> @Path("/{petId}") >>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>> public Response updatePetWithForm (@PathParam("petId") String petId, >>> @FormParam("name") String name, >>> @FormParam("status") String status) { >>> System.out.println(name); >>> System.out.println(status); >>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>> } >>> >>> Really, I don't know why Swagger is so popular :) >>> >> >> That's quite a difference, and less verbose and less of duplication >> (DRY). So I'd say, let's try Miredot :-) >> >> Thanks for the valuable info, Idel! >> >> -Matthias >> >> >>> >>> 2015-04-07 14:11 GMT+03:00 Matthias Wessendorf : >>> >>>> >>>> >>>> On Tue, Apr 7, 2015 at 12:56 PM, Idel Pivnitskiy < >>>> idel.pivnitskiy at gmail.com> wrote: >>>> >>>>> Yes, Swagger can generate doc on the fly, but Swagger use its own >>>>> annotations instead of parse JAX-RS annotations and javadoc, like MireDot. >>>>> >>>> >>>> Ok, I think I have not a huge concern against custom annotations, >>>> especially due to the wide adoption of Swagger. >>>> I guess it's just a very tiny JAR, that contains the annotations, right? >>>> >>>> (+ the build time tool dependency for processing) >>>> >>>> >>>>> What about licence: Apache Tika, for example, uses pro version of >>>>> MireDot >>>>> >>>>> >>>>> https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 >>>>> >>>> >>>> Thanks for the example, that's helpful >>>> >>>> >>>>> >>>>> >>>>> 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : >>>>> >>>>>> Swagger allows doc on the source as well, right ? Just wondering. >>>>>> >>>>>> REgarding license, I need to double check on that before... >>>>>> >>>>>> On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < >>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>> >>>>>>> Matthias, >>>>>>> >>>>>>> Sure, I will work on it. >>>>>>> But I think that it would be better if you request a license [1] on >>>>>>> your email and forward it to me. >>>>>>> It won't be a problem to use a free version, but pro version has a >>>>>>> very cool features, like: >>>>>>> >>>>>>> - Display javadoc comments for the fields of json payloads and >>>>>>> enums >>>>>>> - JSON field documentation >>>>>>> - Type replacement (custom serialisation, JSON types) >>>>>>> >>>>>>> Please, request a li >>>>>>> >>>>>>> [1] http://miredot.com/price/ >>>>>>> >>>>>>> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >>>>>>> >>>>>>>> Idel, >>>>>>>> >>>>>>>> would you mind to create a branch for us, so we can investigate >>>>>>>> the MireDot solution? also the build should be working w/ JDK8. >>>>>>>> >>>>>>>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but it >>>>>>>> does not really use any fancy annotations (e.g. see [2]) - that's why we >>>>>>>> picked it. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> Matthias >>>>>>>> >>>>>>>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>>>>>>> [2] >>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>>>> >>>>>>>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I agree with Idel that DRY approach in Miredot's case seems more >>>>>>>>> appealing. >>>>>>>>> >>>>>>>>> They offer basic docs generation in Free version, but also Pro >>>>>>>>> version for open-source projects under conditions that Aerogear meets [1]. >>>>>>>>> >>>>>>>>> ~ Lukas >>>>>>>>> >>>>>>>>> [1] http://www.miredot.com/price/ >>>>>>>>> >>>>>>>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>>>>>>> idel.pivnitskiy at gmail.com> napsal: >>>>>>>>> >>>>>>>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>>>>>>> http://www.miredot.com/ >>>>>>>>>> >>>>>>>>>> With MireDot you do not need to use additional annotations, >>>>>>>>>> like @Api: >>>>>>>>>> >>>>>>>>>> @Path("/pet") >>>>>>>>>> @Api(value = "/pet", description = "Operations about pets") >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>>>>>>> >>>>>>>>>> /** >>>>>>>>>> * Operations about pets >>>>>>>>>> */ >>>>>>>>>> @Path("/pet") >>>>>>>>>> >>>>>>>>>> and generate beautiful and user friendly documentation, like >>>>>>>>>> this: http://www.miredot.com/exampledocs/ >>>>>>>>>> Swagger example: http://petstore.swagger.io/ >>>>>>>>>> >>>>>>>>>> And MireDot is free for open source projects! >>>>>>>>>> >>>>>>>>>> Think about this alternative for Swagger. I'm able to prepare >>>>>>>>>> Pull Request for UPS next week. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf >>>>>>>>>> : >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>>>>>>> >>>>>>>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>>>>>>> > endpoints, and >>>>>>>>>>>> > it's really handy. >>>>>>>>>>>> >>>>>>>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from >>>>>>>>>>>> JAX-RS + >>>>>>>>>>>> Swagger annotations. >>>>>>>>>>>> In Hawkular we are basically doing the same, but with a >>>>>>>>>>>> different >>>>>>>>>>>> annotation processor. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> +1000 >>>>>>>>>>> >>>>>>>>>>> we are, atm, doing similar: >>>>>>>>>>> source >>>>>>>>>>> >>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>>>>>>> result: >>>>>>>>>>> >>>>>>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST >>>>>>>>>>> >>>>>>>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to >>>>>>>>>>> change here ;-) >>>>>>>>>>> So, I am all for using Swagger annotations on the code to >>>>>>>>>>> generate the HTML docs :-) >>>>>>>>>>> >>>>>>>>>>> Greetings, >>>>>>>>>>> Matthias >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> I personally think the best is really to have the annotations >>>>>>>>>>>> in the >>>>>>>>>>>> source and not trying >>>>>>>>>>>> to update a separate .yml file, as the latter usually is much >>>>>>>>>>>> easier >>>>>>>>>>>> forgotten. >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at 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 >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Best regards, >>>>>>>>>> Idel Pivnitskiy >>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>> Twitter: @idelpivnitskiy >>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at 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 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best regards, >>>>>>> Idel Pivnitskiy >>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>> Twitter: @idelpivnitskiy >>>>>>> GitHub: @idelpivnitskiy >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Best regards, > Idel Pivnitskiy > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150409/49664a4f/attachment-0001.html From idel.pivnitskiy at gmail.com Thu Apr 9 06:19:58 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Thu, 9 Apr 2015 13:19:58 +0300 Subject: [aerogear-dev] License Key for AeroGear UnifiedPush Server (was: Re: do we want swagger for REST endpoint documentation?) In-Reply-To: References: <5526332B.3040309@miredot.com> Message-ID: Thanks a lot to Yves! Matthias, I will send a PR this week :) Best, Idel 2015-04-09 11:14 GMT+03:00 Matthias Wessendorf : > Hi Yves, > > thanks a lot! > > Idel, below is the license key - I saw (looking at your Tika link) it > needs to be included on the pom.xml file. > > Cheers, > Matthias > > > ---------- Forwarded message ---------- > From: Yves Vandewoude > Date: Thu, Apr 9, 2015 at 10:07 AM > Subject: Re: License Key for AeroGear UnifiedPush Server (was: Re: > [aerogear-dev] do we want swagger for REST endpoint documentation?) > To: Matthias Wessendorf > > > Hello Matthias, > > The licence key for the AeroGear UnifiedPush Server project is: > > > cHJvamVjdHxvcmcuamJvc3MuYWVyb2dlYXIudW5pZmllZHB1c2gudW5pZmllZHB1c2gtamF4cnN8MjAxNy0wNS0wMXx0cnVlfC0xI01Dd0NGQitaa0VVRVlsaU9LQjljR2h5TWNSWm1VMTREQWhRbUlHOXY3MExCR0FoT2FubklFSER2SWl1OVZnPT0= > > It is valid for two years (until May 1st 2017) for > org.jboss.aerogear.unifiedpush / unifiedpush-jaxrs > > After that, you are free to request a new licence key. > > We continuously aim to improve our tool, so do not hesitate to contact us > if you have any questions or remarks. Support questions are best sent to > support at miredot.com, since they are dealt with by a team instead of just > me :) > > Kind regards, > Yves > > Matthias Wessendorf schreef op 9/04/2015 om 9:46: > > Hi Miredot team, > > for the AeroGear UnifiedPush Server ([1], [2]), we would like to start > using miredot for our jaxrs endpoints ([3]). The Maven groupId is > "org.jboss.aerogear.unifiedpush" and the artifactId is "unifiedpush-jaxrs". > > Currently we are using jaxrs-doclet ([4]), but we are not happy with > that. > > The Server is an OpenSource project with regular releases, and it is > licensed under the Apache 2.0 license. > > For this project we would like to request an opensource license. > > Thanks, > Matthias > > [1] https://aerogear.org/push/#unifiedpush > [2] https://aerogear.org/docs/unifiedpush/ups_userguide/index/ > [3] > https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/jaxrs > [4] > https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/overview-index.html > > > > On Tue, Apr 7, 2015 at 1:57 PM, Idel Pivnitskiy > wrote: > >> Ok, so I will wait a license key from you. >> >> 2015-04-07 14:55 GMT+03:00 Matthias Wessendorf : >> >>> >>> >>> On Tue, Apr 7, 2015 at 1:42 PM, Idel Pivnitskiy < >>> idel.pivnitskiy at gmail.com> wrote: >>> >>>> IMO, custom annotations force you to duplicate code and documentation. >>>> Take a look at a more detailed example: >>>> >>>> @POST >>>> @Path("/{petId}") >>>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>>> @ApiOperation(value = "Updates a pet in the store with form data", >>>> consumes = MediaType.APPLICATION_FORM_URLENCODED) >>>> @ApiResponses(value = { >>>> @ApiResponse(code = 405, message = "Invalid input")}) >>>> public Response updatePetWithForm ( >>>> @ApiParam(value = "ID of pet that needs to be updated", required = true)@PathParam("petId") String petId, >>>> @ApiParam(value = "Updated name of the pet", required = false)@FormParam("name") String name, >>>> @ApiParam(value = "Updated status of the pet", required = false)@FormParam("status") String status) { >>>> System.out.println(name); >>>> System.out.println(status); >>>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>>> } >>>> >>>> It is much more simple with MireDot (also because javadoc could be >>>> generated automatically by IDE): >>>> >>>> /** >>>> * Updates a pet in the store with form data. >>>> * >>>> * @param petId ID of pet that needs to be updated >>>> * @param name Updated name of the pet >>>> * @param status Updated status of the pet >>>> */ >>>> @POST >>>> @Path("/{petId}") >>>> @Consumes({MediaType.APPLICATION_FORM_URLENCODED}) >>>> public Response updatePetWithForm (@PathParam("petId") String petId, >>>> @FormParam("name") String name, >>>> @FormParam("status") String status) { >>>> System.out.println(name); >>>> System.out.println(status); >>>> return Response.ok().entity(new com.wordnik.swagger.sample.model.ApiResponse(200, "SUCCESS")).build(); >>>> } >>>> >>>> Really, I don't know why Swagger is so popular :) >>>> >>> >>> That's quite a difference, and less verbose and less of duplication >>> (DRY). So I'd say, let's try Miredot :-) >>> >>> Thanks for the valuable info, Idel! >>> >>> -Matthias >>> >>> >>>> >>>> 2015-04-07 14:11 GMT+03:00 Matthias Wessendorf : >>>> >>>>> >>>>> >>>>> On Tue, Apr 7, 2015 at 12:56 PM, Idel Pivnitskiy < >>>>> idel.pivnitskiy at gmail.com> wrote: >>>>> >>>>>> Yes, Swagger can generate doc on the fly, but Swagger use its own >>>>>> annotations instead of parse JAX-RS annotations and javadoc, like MireDot. >>>>>> >>>>> >>>>> Ok, I think I have not a huge concern against custom annotations, >>>>> especially due to the wide adoption of Swagger. >>>>> I guess it's just a very tiny JAR, that contains the annotations, >>>>> right? >>>>> >>>>> (+ the build time tool dependency for processing) >>>>> >>>>> >>>>>> What about licence: Apache Tika, for example, uses pro version of >>>>>> MireDot >>>>>> >>>>>> >>>>>> https://github.com/apache/tika/blob/5fbc56cca94b9da0a914e82dd466abb139f9e3f4/tika-server/pom.xml#L248-L266 >>>>>> >>>>> >>>>> Thanks for the example, that's helpful >>>>> >>>>> >>>>>> >>>>>> >>>>>> 2015-04-07 13:48 GMT+03:00 Matthias Wessendorf : >>>>>> >>>>>>> Swagger allows doc on the source as well, right ? Just wondering. >>>>>>> >>>>>>> REgarding license, I need to double check on that before... >>>>>>> >>>>>>> On Tue, Apr 7, 2015 at 11:57 AM, Idel Pivnitskiy < >>>>>>> idel.pivnitskiy at gmail.com> wrote: >>>>>>> >>>>>>>> Matthias, >>>>>>>> >>>>>>>> Sure, I will work on it. >>>>>>>> But I think that it would be better if you request a license [1] on >>>>>>>> your email and forward it to me. >>>>>>>> It won't be a problem to use a free version, but pro version has a >>>>>>>> very cool features, like: >>>>>>>> >>>>>>>> - Display javadoc comments for the fields of json payloads and >>>>>>>> enums >>>>>>>> - JSON field documentation >>>>>>>> - Type replacement (custom serialisation, JSON types) >>>>>>>> >>>>>>>> Please, request a li >>>>>>>> >>>>>>>> [1] http://miredot.com/price/ >>>>>>>> >>>>>>>> 2015-04-07 12:44 GMT+03:00 Matthias Wessendorf : >>>>>>>> >>>>>>>>> Idel, >>>>>>>>> >>>>>>>>> would you mind to create a branch for us, so we can investigate >>>>>>>>> the MireDot solution? also the build should be working w/ JDK8. >>>>>>>>> >>>>>>>>> ATM we use jax-doclet ([1]) which does not work w/ JDK 8 - but >>>>>>>>> it does not really use any fancy annotations (e.g. see [2]) - that's why we >>>>>>>>> picked it. >>>>>>>>> >>>>>>>>> Thanks! >>>>>>>>> Matthias >>>>>>>>> >>>>>>>>> [1] http://fromage.github.io/jax-doclets/docs/0.10.0/html/ >>>>>>>>> [2] >>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>>>>> >>>>>>>>> On Tue, Apr 7, 2015 at 9:54 AM, Luk?? Fry? >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I agree with Idel that DRY approach in Miredot's case seems >>>>>>>>>> more appealing. >>>>>>>>>> >>>>>>>>>> They offer basic docs generation in Free version, but also Pro >>>>>>>>>> version for open-source projects under conditions that Aerogear meets [1]. >>>>>>>>>> >>>>>>>>>> ~ Lukas >>>>>>>>>> >>>>>>>>>> [1] http://www.miredot.com/price/ >>>>>>>>>> >>>>>>>>>> ne 5. 4. 2015 v 20:00 odes?latel Idel Pivnitskiy < >>>>>>>>>> idel.pivnitskiy at gmail.com> napsal: >>>>>>>>>> >>>>>>>>>> For JAX-RS I prefer use MireDot as a REST API doc generator >>>>>>>>>>> http://www.miredot.com/ >>>>>>>>>>> >>>>>>>>>>> With MireDot you do not need to use additional annotations, >>>>>>>>>>> like @Api: >>>>>>>>>>> >>>>>>>>>>> @Path("/pet") >>>>>>>>>>> @Api(value = "/pet", description = "Operations about pets") >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> It will parse your JAX-RS annotation and pure javadoc: >>>>>>>>>>> >>>>>>>>>>> /** >>>>>>>>>>> * Operations about pets >>>>>>>>>>> */ >>>>>>>>>>> @Path("/pet") >>>>>>>>>>> >>>>>>>>>>> and generate beautiful and user friendly documentation, like >>>>>>>>>>> this: http://www.miredot.com/exampledocs/ >>>>>>>>>>> Swagger example: http://petstore.swagger.io/ >>>>>>>>>>> >>>>>>>>>>> And MireDot is free for open source projects! >>>>>>>>>>> >>>>>>>>>>> Think about this alternative for Swagger. I'm able to prepare >>>>>>>>>>> Pull Request for UPS next week. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2015-04-04 9:43 GMT+03:00 Matthias Wessendorf >>>>>>>>>> >: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Apr 3, 2015 at 10:27 PM, Heiko W.Rupp >>>>>>>>>>> > wrote: >>>>>>>>>>>> >>>>>>>>>>>>> On 3 Apr 2015, at 18:53, Andrea Vibelli wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> > we are using it in Project Newcastle with annotations on the >>>>>>>>>>>>> > endpoints, and >>>>>>>>>>>>> > it's really handy. >>>>>>>>>>>>> >>>>>>>>>>>>> All the JBoss ON 3.2+ and RHQ REST-docs are generated from >>>>>>>>>>>>> JAX-RS + >>>>>>>>>>>>> Swagger annotations. >>>>>>>>>>>>> In Hawkular we are basically doing the same, but with a >>>>>>>>>>>>> different >>>>>>>>>>>>> annotation processor. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> +1000 >>>>>>>>>>>> >>>>>>>>>>>> we are, atm, doing similar: >>>>>>>>>>>> source >>>>>>>>>>>> >>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L99-L102 >>>>>>>>>>>> result: >>>>>>>>>>>> >>>>>>>>>>>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/sender/index.html#POST >>>>>>>>>>>> >>>>>>>>>>>> but the jaxrs doclet does not work w/ JDK8 - something has to >>>>>>>>>>>> change here ;-) >>>>>>>>>>>> So, I am all for using Swagger annotations on the code to >>>>>>>>>>>> generate the HTML docs :-) >>>>>>>>>>>> >>>>>>>>>>>> Greetings, >>>>>>>>>>>> Matthias >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> I personally think the best is really to have the annotations >>>>>>>>>>>>> in the >>>>>>>>>>>>> source and not trying >>>>>>>>>>>>> to update a separate .yml file, as the latter usually is much >>>>>>>>>>>>> easier >>>>>>>>>>>>> forgotten. >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at 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 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Best regards, >>>>>>>>>>> Idel Pivnitskiy >>>>>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>>>>> Twitter: @idelpivnitskiy >>>>>>>>>>> GitHub: @idelpivnitskiy >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at 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 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Best regards, >>>>>>>> Idel Pivnitskiy >>>>>>>> E-mail: Idel.Pivnitskiy at gmail.com >>>>>>>> Twitter: @idelpivnitskiy >>>>>>>> GitHub: @idelpivnitskiy >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Best regards, >> Idel Pivnitskiy >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Best regards, Idel Pivnitskiy E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150409/9b53203d/attachment-0001.html From lholmqui at redhat.com Thu Apr 9 08:51:21 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 9 Apr 2015 08:51:21 -0400 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: On Thu, Apr 9, 2015 at 3:27 AM, Matthias Wessendorf wrote: > since APNs, and GCM can be used for Desktop and browsers, I don't like the > word device here. It's more an installation (that's the origin of this name > actually) > #Agreed > > On Thu, Apr 9, 2015 at 9:15 AM, Sebastien Blanc > wrote: > >> >> >> On Wed, Apr 8, 2015 at 6:57 PM, Andres Galante >> wrote: >> >>> Sebi, I just change the demo. >>> >> I like it more, but I wonder about the stacked bars again, not sure it is >> the best visually, maybe having the 2 bar side-by-side like here >> http://c3js.org/samples/chart_bar.html or what I really would like to >> see but I could not find it in c3 is : the 2 bars superposed a bit like >> this http://i.stack.imgur.com/0hjX7.png >> >>> >>> I now understand what you mean, and you are right its hard to explain it >>> in a short word. >>> >> Yes , what about "Sent out to devices" ? >> >>> If we want we can ask someone from marketing, they have a hole sub team >>> dedicated to writing. >>> >>> Parse uses "Push Notifications" >>> >>> http://blog.parse.com/2013/03/18/introducing-push-analytics-improved-insight-into-push-campaigns/ >>> >>> Urban Airship uses "Total Pushes sent" >>> http://urbanairship.com/products/mobile-analytics >>> >>> >>> >>> On Wed, Apr 8, 2015 at 1:46 PM, Matthias Wessendorf >>> wrote: >>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 6:05 PM, Andres Galante >>>> wrote: >>>> >>>>> Do we always successful deliver messages to all registered devices? >>>>> >>>> >>>> no, it's not even us. we just give the payload to the networks. They >>>> all (APNS, GCM, Windows) have no SLA for actual delivery. >>>> >>>> All what we can say is: >>>> delivered "payload" to APNs for distribution to n devices >>>> >>>> Once they open the app, our server is hit, and we know: n devices did >>>> receive it >>>> >>>> >>>>> >>>>> On Wed, Apr 8, 2015 at 12:51 PM, Matthias Wessendorf < >>>>> matzew at apache.org> wrote: >>>>> >>>>>> Again, I doubt that there will be 3k of messages per app, a day. >>>>>> That would mean your "ESPN Sports News" app would send you 3k >>>>>> messages - joy, he? >>>>>> >>>>>> I wonder how the charts would look on more realistic data: >>>>>> 500.000 devices >>>>>> 1 push message a day (delivered to all 500k) >>>>>> opened by 250k, same day >>>>>> >>>>>> >>>>>> Now if I sent two messages: Breaking news A, Breaking news B >>>>>> How would I see how many directly opened "Breaking news A" (or the >>>>>> other one)? >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante >>>>>> wrote: >>>>>> >>>>>>> Good idea! take a look: >>>>>>> >>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc < >>>>>>> scm.blanc at gmail.com> wrote: >>>>>>> >>>>>>>> I wonder if a bar chart (even maybe stacked bar) would not be more >>>>>>>> clear to show this data ? >>>>>>>> Wdyt ? >>>>>>>> >>>>>>>> Envoy? de mon iPhone >>>>>>>> >>>>>>>> Le 8 avr. 2015 ? 15:44, Andres Galante a >>>>>>>> ?crit : >>>>>>>> >>>>>>>> Yes, you are right, it should be something like: >>>>>>>> >>>>>>>> 5 message sent >>>>>>>> 3k delivered >>>>>>>> 2k open >>>>>>>> 4k devices. >>>>>>>> >>>>>>>> Just change the example. Also the x-axis should be dates. >>>>>>>> >>>>>>>> Thanks! >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf < >>>>>>>> matzew at apache.org> wrote: >>>>>>>> >>>>>>>>> One thing: I think the numbers on the chart are confusing, and >>>>>>>>> incorrect. >>>>>>>>> It's usually not a ton of messages that are sent. that's more like >>>>>>>>> 5 or 10 per day (speaking of vanilla marketing pushes). If more, I'd >>>>>>>>> UNINSTALL the damn app. >>>>>>>>> Therefore the "app opened due to receiving push" numbers are also >>>>>>>>> not 100% correct here. >>>>>>>>> >>>>>>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf < >>>>>>>>> matzew at apache.org> wrote: >>>>>>>>> >>>>>>>>>> :-) I like that too. >>>>>>>>>> >>>>>>>>>> But Andres, again, awesome UX ! >>>>>>>>>> >>>>>>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc < >>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? >>>>>>>>>> > wrote: >>>>>>>>>>> >>>>>>>>>>>> Looks good so far, Andres, >>>>>>>>>>>> >>>>>>>>>>>> you are right, we want to show time-aggregated data, not >>>>>>>>>>>> particular events. >>>>>>>>>>>> >>>>>>>>>>>> Idea: >>>>>>>>>>>> My perspective might be very technical rather then marketing, >>>>>>>>>>>> but a pie chart with Push Network split would be interesting to me. >>>>>>>>>>>> >>>>>>>>>>> +1 (or Donut :) ) >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante < >>>>>>>>>>>> agalante at redhat.com> napsal: >>>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>>> >>>>>>>>>>>>> With the new data we have I've compared sent vs open messages >>>>>>>>>>>>> on a chart for each App: >>>>>>>>>>>>> >>>>>>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>>>>>> (the x axis should be dates) >>>>>>>>>>>>> >>>>>>>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>>>>>>> or device/open >>>>>>>>>>>>> >>>>>>>>>>>>> I believe that to show the first and last time a message was >>>>>>>>>>>>> open is not very useful. Maybe I am wrong, but, If we want to show an over >>>>>>>>>>>>> time chart for each notification we should collect periodical data, for >>>>>>>>>>>>> example # of open messages per hour to generate a linear graph that >>>>>>>>>>>>> represents a day. >>>>>>>>>>>>> >>>>>>>>>>>>> What do you think? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>>>>>> >>>>>>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos >>>>>>>>>>>>>> a ?crit : >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Folks ! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I >>>>>>>>>>>>>>> started a small POC mainly focused on the backend. To sum up quickly : we >>>>>>>>>>>>>>> want to know how many installations/users has opened the application after >>>>>>>>>>>>>>> that a Push Notification has been touched. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Let me see if I understood. UPS will send a message to the >>>>>>>>>>>>>> client and when the message be *read* (instead of delivered), the client >>>>>>>>>>>>>> will send a message back to the UPS saying: "The message was read"? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Yes , but let me be more specific here : us when the app is >>>>>>>>>>>>>> in the background or not running and that the user "tap" the notification >>>>>>>>>>>>>> >>>>>>>>>>>>>> So, the very first thing that had to be done was to give the >>>>>>>>>>>>>>> Push Notification a unique identifier, so that we can track it and do the >>>>>>>>>>>>>>> metrics on it. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> For that, I have been using an existing model object that we >>>>>>>>>>>>>>> have , the PushMessageInformation[2], and that is currently used to provide >>>>>>>>>>>>>>> information for our dashboard. >>>>>>>>>>>>>>> This object has now some extra fields, like a appOpenCounter >>>>>>>>>>>>>>> etc ... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The ID of this PushMessageInformation is now passed into the >>>>>>>>>>>>>>> payload of the Push Message, just before we send it, this way the client >>>>>>>>>>>>>>> library can use this ID to pass extra information to the UPS when a >>>>>>>>>>>>>>> notification is touched. >>>>>>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> The message back (from client to UPS) will be send every time >>>>>>>>>>>>>> the user _read_ that? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Well normally that will only happen once per installation per >>>>>>>>>>>>>> Push message >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> When the UPS receive the request, it looks for the header >>>>>>>>>>>>>>> and if it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Please note, that for this POC, all is happening on >>>>>>>>>>>>>>> Application level and not on Variant level but that can be easily changed. >>>>>>>>>>>>>>> It depends on how fined grained we want to have these analytics. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The UPS branch containing the changes is here (the 2 latests >>>>>>>>>>>>>>> commits are relevant) : >>>>>>>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The client app is not really relevant since I really hacked >>>>>>>>>>>>>>> badly the app (and the push plugin) ;) , however if interested I may share >>>>>>>>>>>>>>> it. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Sebi >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>>>>>> [2] >>>>>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> -- Passos >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at 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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Matthias Wessendorf >>>>>>>>> >>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at 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 >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150409/5a2a22f4/attachment-0001.html From banddk1 at gmail.com Thu Apr 9 15:01:07 2015 From: banddk1 at gmail.com (=?UTF-8?B?0JTQtdC90LjRgSDQmtCw0YDQv9C10L3QutC+?=) Date: Thu, 9 Apr 2015 22:01:07 +0300 Subject: [aerogear-dev] Aerodoc Message-ID: Hello everyone. I'd like to figure out with Aerodoc and I need help :) I tried to launch AeroDoc, but I have a some problems with deploying backend[1]. I used command mvn clean install jboss-as:deploy , however page localhost:8080/aerodoc is not exist. What should I do to launch it? Denis. [1]: https://github.com/aerogear/aerogear-backend-cookbook/tree/master/aerodoc-backend -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150409/b0df78d9/attachment.html From corinnekrych at gmail.com Thu Apr 9 15:22:06 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 9 Apr 2015 21:22:06 +0200 Subject: [aerogear-dev] Aerodoc In-Reply-To: References: Message-ID: Hi Denis Which jboss are you running? Do you have any erros in the console log? ++ Corinne > On 09 Apr 2015, at 21:01, ????? ???????? wrote: > > Hello everyone. > I'd like to figure out with Aerodoc and I need help :) > I tried to launch AeroDoc, but I have a some problems with deploying backend[1]. I used command mvn clean install jboss-as:deploy > , however page localhost:8080/aerodoc is not exist. What should I do to launch it? > > > Denis. > > [1]: https://github.com/aerogear/aerogear-backend-cookbook/tree/master/aerodoc-backend > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From banddk1 at gmail.com Thu Apr 9 16:18:44 2015 From: banddk1 at gmail.com (=?UTF-8?B?0JTQtdC90LjRgSDQmtCw0YDQv9C10L3QutC+?=) Date: Thu, 9 Apr 2015 23:18:44 +0300 Subject: [aerogear-dev] Aerodoc In-Reply-To: References: Message-ID: My server works on 8787 port not 8080, and I get in console "Debugger failed to attach: handshake failed - received >GET /aerodoc H< - expected >JDWP-Handshake<" It's problem ( Denis. 2015-04-09 22:22 GMT+03:00 Corinne Krych : > Hi Denis > > Which jboss are you running? > Do you have any erros in the console log? > > ++ > Corinne > > > On 09 Apr 2015, at 21:01, ????? ???????? wrote: > > > > Hello everyone. > > I'd like to figure out with Aerodoc and I need help :) > > I tried to launch AeroDoc, but I have a some problems with deploying > backend[1]. I used command mvn clean install jboss-as:deploy > > , however page localhost:8080/aerodoc is not exist. What should I do > to launch it? > > > > > > Denis. > > > > [1]: > https://github.com/aerogear/aerogear-backend-cookbook/tree/master/aerodoc-backend > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150409/424bb597/attachment.html From corinnekrych at gmail.com Fri Apr 10 02:57:25 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 10 Apr 2015 08:57:25 +0200 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! Message-ID: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Hello iOS lovers, Xcode 6.3 is officially out (since 2 days actually). And Travis build seems to be ready. Xcode 6.3 comes with Swift 1.2, so it implies some (minor) compilation changes. I think it?s time to move to this new stable version. I have created the JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS release (end of April). Any questions, toughts? ++ Corinne [1] https://issues.jboss.org/browse/AGIOS-428 From ivan.gurtler at ahead-itec.com Fri Apr 10 04:33:44 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Fri, 10 Apr 2015 10:33:44 +0200 Subject: [aerogear-dev] AG UPS deadlock Message-ID: Hi, we use two AG unified push servers with Oracle DB in cluster, but we have some problem with deadlock (probably caused by clean up by both servers at the same time). We used DB owner PUSHSRVAG and application DB account APUSHSRVAG. (version ... my fork (with small change in dev) ... https://github.com/IvanGurtler/aerogear-unifiedpush-server/tree/MyBranch) Is possible change some settings to prevent deadlock ? or some different solution ? ----------------------------------------------------------------------------------------- *** 2015-04-10 00:00:04.506 *** SESSION ID:(84.48937) 2015-04-10 00:00:04.506 *** CLIENT ID:() 2015-04-10 00:00:04.506 *** SERVICE NAME:(SYS$USERS) 2015-04-10 00:00:04.506 *** MODULE NAME:(JDBC Thin Client) 2015-04-10 00:00:04.506 *** CLIENT DRIVER:(jdbcthin) 2015-04-10 00:00:04.506 *** ACTION NAME:() 2015-04-10 00:00:04.506 *** 2015-04-10 00:00:04.506 DEADLOCK DETECTED ( ORA-00060 ) See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors [Transaction Deadlock] The following deadlock is not an ORACLE error. It is a deadlock due to user error in the design of an application or from issuing incorrect ad-hoc SQL. The following information may aid in determining the deadlock: Deadlock graph: ---------Blocker(s)-------- ---------Waiter(s)--------- Resource Name process session holds waits process session holds waits TM-00013891-00000000-00000000-00000000 142 84 SX SSX 144 162 SX SSX TM-00013891-00000000-00000000-00000000 144 162 SX SSX 142 84 SX SSX Rows waited on: Session 84: no row Session 162: no row ----- Information for the OTHER waiting sessions ----- Session 162: sid: 162 ser: 54036 audsid: 10790094 user: 115/APUSHSRVAG flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/- flags2: (0x40009) -/-/INC pid: 144 O/S info: user: oracle, term: UNKNOWN, ospid: 11534420 image: oracle at s16000ks client details: O/S info: user: jbotp, term: unknown, ospid: 1234 machine: s1.sk.srv.acc.sys program: JDBC Thin Client application name: JDBC Thin Client, hash value=2546894660 current SQL: delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 ----- End of information for the OTHER waiting sessions ----- Information for THIS session: ----- Current SQL Statement for this session (sql_id=bsk109wpq55yg) ----- delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 ----------------------------------------------------------------------------------------- Thanks *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150410/267b31f2/attachment.html From matzew at apache.org Fri Apr 10 05:20:01 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 10 Apr 2015 11:20:01 +0200 Subject: [aerogear-dev] AG UPS deadlock In-Reply-To: References: Message-ID: Oh, that's this guy, triggered at midnight: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/DeleteOldPushMessageInformationScheduler.java It's a singleton, but per node :-/ Can you create a JIRA ticket for that ? On Fri, Apr 10, 2015 at 10:33 AM, Ivan G?rtler wrote: > Hi, we use two AG unified push servers with Oracle DB in cluster, but we > have some problem with deadlock (probably caused by clean up by both > servers at the same time). > We used DB owner PUSHSRVAG and application DB account APUSHSRVAG. > > (version ... my fork (with small change in dev) ... > https://github.com/IvanGurtler/aerogear-unifiedpush-server/tree/MyBranch) > > Is possible change some settings to prevent deadlock ? or some different > solution ? > > > ----------------------------------------------------------------------------------------- > > *** 2015-04-10 00:00:04.506 > *** SESSION ID:(84.48937) 2015-04-10 00:00:04.506 > *** CLIENT ID:() 2015-04-10 00:00:04.506 > *** SERVICE NAME:(SYS$USERS) 2015-04-10 00:00:04.506 > *** MODULE NAME:(JDBC Thin Client) 2015-04-10 00:00:04.506 > *** CLIENT DRIVER:(jdbcthin) 2015-04-10 00:00:04.506 > *** ACTION NAME:() 2015-04-10 00:00:04.506 > > > > *** 2015-04-10 00:00:04.506 > DEADLOCK DETECTED ( ORA-00060 ) > See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors > [Transaction Deadlock] > > The following deadlock is not an ORACLE error. It is a > deadlock due to user error in the design of an application > or from issuing incorrect ad-hoc SQL. The following > information may aid in determining the deadlock: > > Deadlock graph: > > ---------Blocker(s)-------- ---------Waiter(s)--------- > Resource Name process session > holds waits process session holds waits > TM-00013891-00000000-00000000-00000000 142 84 SX SSX > 144 162 SX SSX > TM-00013891-00000000-00000000-00000000 144 162 SX SSX > 142 84 SX SSX > > > Rows waited on: > Session 84: no row > Session 162: no row > > ----- Information for the OTHER waiting sessions ----- > Session 162: > sid: 162 ser: 54036 audsid: 10790094 user: 115/APUSHSRVAG > flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/- > flags2: (0x40009) -/-/INC > pid: 144 O/S info: user: oracle, term: UNKNOWN, ospid: 11534420 > image: oracle at s16000ks > client details: > O/S info: user: jbotp, term: unknown, ospid: 1234 > machine: s1.sk.srv.acc.sys program: JDBC Thin Client > application name: JDBC Thin Client, hash value=2546894660 > current SQL: > delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 > > ----- End of information for the OTHER waiting sessions ----- > > Information for THIS session: > > ----- Current SQL Statement for this session (sql_id=bsk109wpq55yg) ----- > delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 > > > ----------------------------------------------------------------------------------------- > > > > > Thanks > > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150410/97f90e3b/attachment-0001.html From cvasilak at gmail.com Fri Apr 10 05:26:03 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Fri, 10 Apr 2015 12:26:03 +0300 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: On Fri, Apr 10, 2015 at 9:57 AM, Corinne Krych wrote: > Hello iOS lovers, > > Xcode 6.3 is officially out (since 2 days actually). > And Travis build seems to be ready. > > Xcode 6.3 comes with Swift 1.2, so it implies some (minor) compilation > changes. > I think it?s time to move to this new stable version. I have created the > JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS > release (end of April). > +9001 long time to see only one release out and no myriad of betas ;) *http://tinyurl.com/po946bv * > Any questions, toughts? > ++ > Corinne > [1] https://issues.jboss.org/browse/AGIOS-428 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150410/a7152635/attachment.html From matzew at apache.org Fri Apr 10 05:48:20 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 10 Apr 2015 11:48:20 +0200 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: On Fri, Apr 10, 2015 at 8:57 AM, Corinne Krych wrote: > Hello iOS lovers, > > Xcode 6.3 is officially out (since 2 days actually). > And Travis build seems to be ready. > great news! > > Xcode 6.3 comes with Swift 1.2, so it implies some (minor) compilation > changes. > I think it?s time to move to this new stable version. I have created the > JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS > release (end of April). > yes, sounds reasonable to do that > > Any questions, toughts? > ++ > Corinne > [1] https://issues.jboss.org/browse/AGIOS-428 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150410/a31c729b/attachment.html From ivan.gurtler at ahead-itec.com Fri Apr 10 06:32:03 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Fri, 10 Apr 2015 12:32:03 +0200 Subject: [aerogear-dev] AG UPS deadlock In-Reply-To: References: Message-ID: And is it possible in current version to set up time for scheduler not to run at midnight? *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-04-10 11:20 GMT+02:00 Matthias Wessendorf : > Oh, that's this guy, triggered at midnight: > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/DeleteOldPushMessageInformationScheduler.java > > It's a singleton, but per node :-/ > > Can you create a JIRA ticket for that ? > > On Fri, Apr 10, 2015 at 10:33 AM, Ivan G?rtler < > ivan.gurtler at ahead-itec.com> wrote: > >> Hi, we use two AG unified push servers with Oracle DB in cluster, but we >> have some problem with deadlock (probably caused by clean up by both >> servers at the same time). >> We used DB owner PUSHSRVAG and application DB account APUSHSRVAG. >> >> (version ... my fork (with small change in dev) ... >> https://github.com/IvanGurtler/aerogear-unifiedpush-server/tree/MyBranch) >> >> Is possible change some settings to prevent deadlock ? or some different >> solution ? >> >> >> ----------------------------------------------------------------------------------------- >> >> *** 2015-04-10 00:00:04.506 >> *** SESSION ID:(84.48937) 2015-04-10 00:00:04.506 >> *** CLIENT ID:() 2015-04-10 00:00:04.506 >> *** SERVICE NAME:(SYS$USERS) 2015-04-10 00:00:04.506 >> *** MODULE NAME:(JDBC Thin Client) 2015-04-10 00:00:04.506 >> *** CLIENT DRIVER:(jdbcthin) 2015-04-10 00:00:04.506 >> *** ACTION NAME:() 2015-04-10 00:00:04.506 >> >> >> >> *** 2015-04-10 00:00:04.506 >> DEADLOCK DETECTED ( ORA-00060 ) >> See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors >> [Transaction Deadlock] >> >> The following deadlock is not an ORACLE error. It is a >> deadlock due to user error in the design of an application >> or from issuing incorrect ad-hoc SQL. The following >> information may aid in determining the deadlock: >> >> Deadlock graph: >> >> ---------Blocker(s)-------- ---------Waiter(s)--------- >> Resource Name process >> session holds waits process session holds waits >> TM-00013891-00000000-00000000-00000000 142 84 SX SSX >> 144 162 SX SSX >> TM-00013891-00000000-00000000-00000000 144 162 SX SSX >> 142 84 SX SSX >> >> >> Rows waited on: >> Session 84: no row >> Session 162: no row >> >> ----- Information for the OTHER waiting sessions ----- >> Session 162: >> sid: 162 ser: 54036 audsid: 10790094 user: 115/APUSHSRVAG >> flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/- >> flags2: (0x40009) -/-/INC >> pid: 144 O/S info: user: oracle, term: UNKNOWN, ospid: 11534420 >> image: oracle at s16000ks >> client details: >> O/S info: user: jbotp, term: unknown, ospid: 1234 >> machine: s1.sk.srv.acc.sys program: JDBC Thin Client >> application name: JDBC Thin Client, hash value=2546894660 >> current SQL: >> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >> >> ----- End of information for the OTHER waiting sessions ----- >> >> Information for THIS session: >> >> ----- Current SQL Statement for this session (sql_id=bsk109wpq55yg) ----- >> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >> >> >> ----------------------------------------------------------------------------------------- >> >> >> >> >> Thanks >> >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150410/9c340a86/attachment.html From matzew at apache.org Fri Apr 10 07:19:22 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 10 Apr 2015 13:19:22 +0200 Subject: [aerogear-dev] AG UPS deadlock In-Reply-To: References: Message-ID: On Fri, Apr 10, 2015 at 12:32 PM, Ivan G?rtler wrote: > And is it possible in current version to set up time for scheduler not to > run at midnight? > unfortunately not - we discussed that option, but I am overasked if we actually have a JIRA for that :-) But I agree, it should be done, for 1.1.x - for now you would have to tweak your fork :) > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-04-10 11:20 GMT+02:00 Matthias Wessendorf : > >> Oh, that's this guy, triggered at midnight: >> >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/DeleteOldPushMessageInformationScheduler.java >> >> It's a singleton, but per node :-/ >> >> Can you create a JIRA ticket for that ? >> >> On Fri, Apr 10, 2015 at 10:33 AM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> Hi, we use two AG unified push servers with Oracle DB in cluster, but we >>> have some problem with deadlock (probably caused by clean up by both >>> servers at the same time). >>> We used DB owner PUSHSRVAG and application DB account APUSHSRVAG. >>> >>> (version ... my fork (with small change in dev) ... >>> https://github.com/IvanGurtler/aerogear-unifiedpush-server/tree/MyBranch >>> ) >>> >>> Is possible change some settings to prevent deadlock ? or some different >>> solution ? >>> >>> >>> ----------------------------------------------------------------------------------------- >>> >>> *** 2015-04-10 00:00:04.506 >>> *** SESSION ID:(84.48937) 2015-04-10 00:00:04.506 >>> *** CLIENT ID:() 2015-04-10 00:00:04.506 >>> *** SERVICE NAME:(SYS$USERS) 2015-04-10 00:00:04.506 >>> *** MODULE NAME:(JDBC Thin Client) 2015-04-10 00:00:04.506 >>> *** CLIENT DRIVER:(jdbcthin) 2015-04-10 00:00:04.506 >>> *** ACTION NAME:() 2015-04-10 00:00:04.506 >>> >>> >>> >>> *** 2015-04-10 00:00:04.506 >>> DEADLOCK DETECTED ( ORA-00060 ) >>> See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors >>> [Transaction Deadlock] >>> >>> The following deadlock is not an ORACLE error. It is a >>> deadlock due to user error in the design of an application >>> or from issuing incorrect ad-hoc SQL. The following >>> information may aid in determining the deadlock: >>> >>> Deadlock graph: >>> >>> ---------Blocker(s)-------- >>> ---------Waiter(s)--------- >>> Resource Name process >>> session holds waits process session holds waits >>> TM-00013891-00000000-00000000-00000000 142 84 SX SSX >>> 144 162 SX SSX >>> TM-00013891-00000000-00000000-00000000 144 162 SX SSX >>> 142 84 SX SSX >>> >>> >>> Rows waited on: >>> Session 84: no row >>> Session 162: no row >>> >>> ----- Information for the OTHER waiting sessions ----- >>> Session 162: >>> sid: 162 ser: 54036 audsid: 10790094 user: 115/APUSHSRVAG >>> flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/- >>> flags2: (0x40009) -/-/INC >>> pid: 144 O/S info: user: oracle, term: UNKNOWN, ospid: 11534420 >>> image: oracle at s16000ks >>> client details: >>> O/S info: user: jbotp, term: unknown, ospid: 1234 >>> machine: s1.sk.srv.acc.sys program: JDBC Thin Client >>> application name: JDBC Thin Client, hash value=2546894660 >>> current SQL: >>> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >>> >>> ----- End of information for the OTHER waiting sessions ----- >>> >>> Information for THIS session: >>> >>> ----- Current SQL Statement for this session (sql_id=bsk109wpq55yg) ----- >>> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >>> >>> >>> ----------------------------------------------------------------------------------------- >>> >>> >>> >>> >>> Thanks >>> >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150410/de5a30ef/attachment-0001.html From ivan.gurtler at ahead-itec.com Fri Apr 10 07:55:39 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Fri, 10 Apr 2015 13:55:39 +0200 Subject: [aerogear-dev] AG UPS deadlock In-Reply-To: References: Message-ID: OK I create issue ... https://issues.jboss.org/browse/AGPUSH-1362 *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-04-10 13:19 GMT+02:00 Matthias Wessendorf : > > > On Fri, Apr 10, 2015 at 12:32 PM, Ivan G?rtler < > ivan.gurtler at ahead-itec.com> wrote: > >> And is it possible in current version to set up time for scheduler not to >> run at midnight? >> > > unfortunately not - we discussed that option, but I am overasked if we > actually have a JIRA for that :-) > But I agree, it should be done, for 1.1.x - for now you would have to > tweak your fork :) > > >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-04-10 11:20 GMT+02:00 Matthias Wessendorf : >> >>> Oh, that's this guy, triggered at midnight: >>> >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/DeleteOldPushMessageInformationScheduler.java >>> >>> It's a singleton, but per node :-/ >>> >>> Can you create a JIRA ticket for that ? >>> >>> On Fri, Apr 10, 2015 at 10:33 AM, Ivan G?rtler < >>> ivan.gurtler at ahead-itec.com> wrote: >>> >>>> Hi, we use two AG unified push servers with Oracle DB in cluster, but >>>> we have some problem with deadlock (probably caused by clean up by both >>>> servers at the same time). >>>> We used DB owner PUSHSRVAG and application DB account APUSHSRVAG. >>>> >>>> (version ... my fork (with small change in dev) ... >>>> https://github.com/IvanGurtler/aerogear-unifiedpush-server/tree/MyBranch >>>> ) >>>> >>>> Is possible change some settings to prevent deadlock ? or some >>>> different solution ? >>>> >>>> >>>> ----------------------------------------------------------------------------------------- >>>> >>>> *** 2015-04-10 00:00:04.506 >>>> *** SESSION ID:(84.48937) 2015-04-10 00:00:04.506 >>>> *** CLIENT ID:() 2015-04-10 00:00:04.506 >>>> *** SERVICE NAME:(SYS$USERS) 2015-04-10 00:00:04.506 >>>> *** MODULE NAME:(JDBC Thin Client) 2015-04-10 00:00:04.506 >>>> *** CLIENT DRIVER:(jdbcthin) 2015-04-10 00:00:04.506 >>>> *** ACTION NAME:() 2015-04-10 00:00:04.506 >>>> >>>> >>>> >>>> *** 2015-04-10 00:00:04.506 >>>> DEADLOCK DETECTED ( ORA-00060 ) >>>> See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors >>>> [Transaction Deadlock] >>>> >>>> The following deadlock is not an ORACLE error. It is a >>>> deadlock due to user error in the design of an application >>>> or from issuing incorrect ad-hoc SQL. The following >>>> information may aid in determining the deadlock: >>>> >>>> Deadlock graph: >>>> >>>> ---------Blocker(s)-------- >>>> ---------Waiter(s)--------- >>>> Resource Name process >>>> session holds waits process session holds waits >>>> TM-00013891-00000000-00000000-00000000 142 84 SX SSX >>>> 144 162 SX SSX >>>> TM-00013891-00000000-00000000-00000000 144 162 SX SSX >>>> 142 84 SX SSX >>>> >>>> >>>> Rows waited on: >>>> Session 84: no row >>>> Session 162: no row >>>> >>>> ----- Information for the OTHER waiting sessions ----- >>>> Session 162: >>>> sid: 162 ser: 54036 audsid: 10790094 user: 115/APUSHSRVAG >>>> flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/- >>>> flags2: (0x40009) -/-/INC >>>> pid: 144 O/S info: user: oracle, term: UNKNOWN, ospid: 11534420 >>>> image: oracle at s16000ks >>>> client details: >>>> O/S info: user: jbotp, term: unknown, ospid: 1234 >>>> machine: s1.sk.srv.acc.sys program: JDBC Thin Client >>>> application name: JDBC Thin Client, hash value=2546894660 >>>> current SQL: >>>> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >>>> >>>> ----- End of information for the OTHER waiting sessions ----- >>>> >>>> Information for THIS session: >>>> >>>> ----- Current SQL Statement for this session (sql_id=bsk109wpq55yg) >>>> ----- >>>> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >>>> >>>> >>>> ----------------------------------------------------------------------------------------- >>>> >>>> >>>> >>>> >>>> Thanks >>>> >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150410/dc6f50fe/attachment.html From corinnekrych at gmail.com Fri Apr 10 08:17:09 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 10 Apr 2015 14:17:09 +0200 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: On 10 April 2015 at 11:26, Christos Vasilakis wrote: > > > On Fri, Apr 10, 2015 at 9:57 AM, Corinne Krych > wrote: > >> Hello iOS lovers, >> >> Xcode 6.3 is officially out (since 2 days actually). >> And Travis build seems to be ready. >> >> Xcode 6.3 comes with Swift 1.2, so it implies some (minor) compilation >> changes. >> I think it?s time to move to this new stable version. I have created the >> JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS >> release (end of April). >> > > +9001 > > long time to see only one release out and no myriad of betas ;) > *http://tinyurl.com/po946bv * > > Indeed! :) > > > >> Any questions, toughts? >> ++ >> Corinne >> [1] https://issues.jboss.org/browse/AGIOS-428 >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150410/68e8d779/attachment.html From corinnekrych at gmail.com Fri Apr 10 09:41:58 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 10 Apr 2015 15:41:58 +0200 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: Unfortunately Travis is not ready yet [1] I will prepare the PR and test it so we can merge when Travis is ready. ++ Corinne [1] http://blog.travis-ci.com/2015-04-09-this-week-in-travis-ci/ [2] https://travis-ci.org/corinnekrych/aerogear-ios-http-1/builds/57947586 On 10 April 2015 at 14:17, Corinne Krych wrote: > > > On 10 April 2015 at 11:26, Christos Vasilakis wrote: > >> >> >> On Fri, Apr 10, 2015 at 9:57 AM, Corinne Krych >> wrote: >> >>> Hello iOS lovers, >>> >>> Xcode 6.3 is officially out (since 2 days actually). >>> And Travis build seems to be ready. >>> >>> Xcode 6.3 comes with Swift 1.2, so it implies some (minor) compilation >>> changes. >>> I think it?s time to move to this new stable version. I have created the >>> JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS >>> release (end of April). >>> >> >> +9001 >> >> long time to see only one release out and no myriad of betas ;) >> *http://tinyurl.com/po946bv * >> >> > > Indeed! > :) > > >> >> >> >>> Any questions, toughts? >>> ++ >>> Corinne >>> [1] https://issues.jboss.org/browse/AGIOS-428 >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150410/ce53a1e5/attachment-0001.html From cvasilak at gmail.com Sun Apr 12 11:20:41 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Sun, 12 Apr 2015 18:20:41 +0300 Subject: [aerogear-dev] Team Meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-04.13.2015 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150412/15602f34/attachment.html From banddk1 at gmail.com Sun Apr 12 17:14:51 2015 From: banddk1 at gmail.com (=?UTF-8?B?0JTQtdC90LjRgSDQmtCw0YDQv9C10L3QutC+?=) Date: Mon, 13 Apr 2015 00:14:51 +0300 Subject: [aerogear-dev] Aerodoc In-Reply-To: References: Message-ID: If someone interested in this problem, It was because I had jdk1.8. I have just installed 1.7 and It's ok now :) Thanks Corinne. Denis 2015-04-09 23:18 GMT+03:00 ????? ???????? : > My server works on 8787 port not 8080, and I get in console "Debugger > failed to attach: handshake failed - received >GET /aerodoc H< - expected > >JDWP-Handshake<" > It's problem ( > > Denis. > > 2015-04-09 22:22 GMT+03:00 Corinne Krych : > >> Hi Denis >> >> Which jboss are you running? >> Do you have any erros in the console log? >> >> ++ >> Corinne >> >> > On 09 Apr 2015, at 21:01, ????? ???????? wrote: >> > >> > Hello everyone. >> > I'd like to figure out with Aerodoc and I need help :) >> > I tried to launch AeroDoc, but I have a some problems with deploying >> backend[1]. I used command mvn clean install jboss-as:deploy >> > , however page localhost:8080/aerodoc is not exist. What should I do >> to launch it? >> > >> > >> > Denis. >> > >> > [1]: >> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/aerodoc-backend >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150413/4165319f/attachment.html From agalante at redhat.com Mon Apr 13 08:45:09 2015 From: agalante at redhat.com (Andres Galante) Date: Mon, 13 Apr 2015 09:45:09 -0300 Subject: [aerogear-dev] [UPS] Advanced Analytics In-Reply-To: References: <6E6FC50B-A726-4C61-A988-19DD95BF4226@gmail.com> <3CA6630A-833E-4F10-8100-9258E76B7198@gmail.com> Message-ID: Hi! I've done a few changes: http://andresgalante.com/ups-console/app-detail-analytics.html - Added tooltips to make it easier to understand. - Added a ration sent /open the larger that number the more successful is your campaign. - Moved date selector to the top instead of just filtering the chart, does that make sense? Thanks! On Thu, Apr 9, 2015 at 9:51 AM, Luke Holmquist wrote: > > > On Thu, Apr 9, 2015 at 3:27 AM, Matthias Wessendorf > wrote: > >> since APNs, and GCM can be used for Desktop and browsers, I don't like >> the word device here. It's more an installation (that's the origin of this >> name actually) >> > #Agreed > >> >> On Thu, Apr 9, 2015 at 9:15 AM, Sebastien Blanc >> wrote: >> >>> >>> >>> On Wed, Apr 8, 2015 at 6:57 PM, Andres Galante >>> wrote: >>> >>>> Sebi, I just change the demo. >>>> >>> I like it more, but I wonder about the stacked bars again, not sure it >>> is the best visually, maybe having the 2 bar side-by-side like here >>> http://c3js.org/samples/chart_bar.html or what I really would like to >>> see but I could not find it in c3 is : the 2 bars superposed a bit like >>> this http://i.stack.imgur.com/0hjX7.png >>> >>>> >>>> I now understand what you mean, and you are right its hard to explain >>>> it in a short word. >>>> >>> Yes , what about "Sent out to devices" ? >>> >>>> If we want we can ask someone from marketing, they have a hole sub team >>>> dedicated to writing. >>>> >>>> Parse uses "Push Notifications" >>>> >>>> http://blog.parse.com/2013/03/18/introducing-push-analytics-improved-insight-into-push-campaigns/ >>>> >>>> Urban Airship uses "Total Pushes sent" >>>> http://urbanairship.com/products/mobile-analytics >>>> >>>> >>>> >>>> On Wed, Apr 8, 2015 at 1:46 PM, Matthias Wessendorf >>>> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Apr 8, 2015 at 6:05 PM, Andres Galante >>>>> wrote: >>>>> >>>>>> Do we always successful deliver messages to all registered devices? >>>>>> >>>>> >>>>> no, it's not even us. we just give the payload to the networks. They >>>>> all (APNS, GCM, Windows) have no SLA for actual delivery. >>>>> >>>>> All what we can say is: >>>>> delivered "payload" to APNs for distribution to n devices >>>>> >>>>> Once they open the app, our server is hit, and we know: n devices did >>>>> receive it >>>>> >>>>> >>>>>> >>>>>> On Wed, Apr 8, 2015 at 12:51 PM, Matthias Wessendorf < >>>>>> matzew at apache.org> wrote: >>>>>> >>>>>>> Again, I doubt that there will be 3k of messages per app, a day. >>>>>>> That would mean your "ESPN Sports News" app would send you 3k >>>>>>> messages - joy, he? >>>>>>> >>>>>>> I wonder how the charts would look on more realistic data: >>>>>>> 500.000 devices >>>>>>> 1 push message a day (delivered to all 500k) >>>>>>> opened by 250k, same day >>>>>>> >>>>>>> >>>>>>> Now if I sent two messages: Breaking news A, Breaking news B >>>>>>> How would I see how many directly opened "Breaking news A" (or the >>>>>>> other one)? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 8, 2015 at 5:44 PM, Andres Galante >>>>>>> wrote: >>>>>>> >>>>>>>> Good idea! take a look: >>>>>>>> >>>>>>>> >>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Apr 8, 2015 at 12:24 PM, S?bastien Blanc < >>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>> >>>>>>>>> I wonder if a bar chart (even maybe stacked bar) would not be more >>>>>>>>> clear to show this data ? >>>>>>>>> Wdyt ? >>>>>>>>> >>>>>>>>> Envoy? de mon iPhone >>>>>>>>> >>>>>>>>> Le 8 avr. 2015 ? 15:44, Andres Galante a >>>>>>>>> ?crit : >>>>>>>>> >>>>>>>>> Yes, you are right, it should be something like: >>>>>>>>> >>>>>>>>> 5 message sent >>>>>>>>> 3k delivered >>>>>>>>> 2k open >>>>>>>>> 4k devices. >>>>>>>>> >>>>>>>>> Just change the example. Also the x-axis should be dates. >>>>>>>>> >>>>>>>>> Thanks! >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Apr 8, 2015 at 10:32 AM, Matthias Wessendorf < >>>>>>>>> matzew at apache.org> wrote: >>>>>>>>> >>>>>>>>>> One thing: I think the numbers on the chart are confusing, and >>>>>>>>>> incorrect. >>>>>>>>>> It's usually not a ton of messages that are sent. that's more >>>>>>>>>> like 5 or 10 per day (speaking of vanilla marketing pushes). If more, I'd >>>>>>>>>> UNINSTALL the damn app. >>>>>>>>>> Therefore the "app opened due to receiving push" numbers are also >>>>>>>>>> not 100% correct here. >>>>>>>>>> >>>>>>>>>> On Wed, Apr 8, 2015 at 2:59 PM, Matthias Wessendorf < >>>>>>>>>> matzew at apache.org> wrote: >>>>>>>>>> >>>>>>>>>>> :-) I like that too. >>>>>>>>>>> >>>>>>>>>>> But Andres, again, awesome UX ! >>>>>>>>>>> >>>>>>>>>>> On Wed, Apr 8, 2015 at 2:46 PM, Sebastien Blanc < >>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Apr 8, 2015 at 2:37 PM, Luk?? Fry? < >>>>>>>>>>>> lukas.fryc at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Looks good so far, Andres, >>>>>>>>>>>>> >>>>>>>>>>>>> you are right, we want to show time-aggregated data, not >>>>>>>>>>>>> particular events. >>>>>>>>>>>>> >>>>>>>>>>>>> Idea: >>>>>>>>>>>>> My perspective might be very technical rather then marketing, >>>>>>>>>>>>> but a pie chart with Push Network split would be interesting to me. >>>>>>>>>>>>> >>>>>>>>>>>> +1 (or Donut :) ) >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> st 8. 4. 2015 v 14:12 odes?latel Andres Galante < >>>>>>>>>>>>> agalante at redhat.com> napsal: >>>>>>>>>>>>> >>>>>>>>>>>>> Hi, >>>>>>>>>>>>>> >>>>>>>>>>>>>> With the new data we have I've compared sent vs open messages >>>>>>>>>>>>>> on a chart for each App: >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://rawgit.com/andresgalante/UPS/master/app-detail-analytics.html >>>>>>>>>>>>>> (the x axis should be dates) >>>>>>>>>>>>>> >>>>>>>>>>>>>> I am wondering if we can generate a ratio that's useful for a >>>>>>>>>>>>>> marketing person and show a benchmark comparing with other UPS users to >>>>>>>>>>>>>> know if the users campaign is successful or not. Something like: open/sent >>>>>>>>>>>>>> or device/open >>>>>>>>>>>>>> >>>>>>>>>>>>>> I believe that to show the first and last time a message was >>>>>>>>>>>>>> open is not very useful. Maybe I am wrong, but, If we want to show an over >>>>>>>>>>>>>> time chart for each notification we should collect periodical data, for >>>>>>>>>>>>>> example # of open messages per hour to generate a linear graph that >>>>>>>>>>>>>> represents a day. >>>>>>>>>>>>>> >>>>>>>>>>>>>> What do you think? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Mar 30, 2015 at 5:00 PM, S?bastien Blanc < >>>>>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Envoy? de mon iPhone >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Le 30 mars 2015 ? 21:31, Daniel Passos >>>>>>>>>>>>>>> a ?crit : >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Mar 30, 2015 at 12:29 PM, Sebastien Blanc < >>>>>>>>>>>>>>> scm.blanc at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Folks ! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> For AGPUSH-969[1] and to kick off the discussions, I >>>>>>>>>>>>>>>> started a small POC mainly focused on the backend. To sum up quickly : we >>>>>>>>>>>>>>>> want to know how many installations/users has opened the application after >>>>>>>>>>>>>>>> that a Push Notification has been touched. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Let me see if I understood. UPS will send a message to the >>>>>>>>>>>>>>> client and when the message be *read* (instead of delivered), the client >>>>>>>>>>>>>>> will send a message back to the UPS saying: "The message was read"? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Yes , but let me be more specific here : us when the app is >>>>>>>>>>>>>>> in the background or not running and that the user "tap" the notification >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> So, the very first thing that had to be done was to give the >>>>>>>>>>>>>>>> Push Notification a unique identifier, so that we can track it and do the >>>>>>>>>>>>>>>> metrics on it. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> +1. Not only us (UPS) but also the backend app >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> For that, I have been using an existing model object that >>>>>>>>>>>>>>>> we have , the PushMessageInformation[2], and that is currently used to >>>>>>>>>>>>>>>> provide information for our dashboard. >>>>>>>>>>>>>>>> This object has now some extra fields, like a >>>>>>>>>>>>>>>> appOpenCounter etc ... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The ID of this PushMessageInformation is now passed into >>>>>>>>>>>>>>>> the payload of the Push Message, just before we send it, this way the >>>>>>>>>>>>>>>> client library can use this ID to pass extra information to the UPS when a >>>>>>>>>>>>>>>> notification is touched. >>>>>>>>>>>>>>>> For this POC, I hijacked the cordova-helloworld, so that it >>>>>>>>>>>>>>>> extracts the ID from the payload and pass it as header when registering. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The message back (from client to UPS) will be send every >>>>>>>>>>>>>>> time the user _read_ that? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Well normally that will only happen once per installation >>>>>>>>>>>>>>> per Push message >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> When the UPS receive the request, it looks for the header >>>>>>>>>>>>>>>> and if it exist it updates the existing PushMessageInformation instance. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Please note, that for this POC, all is happening on >>>>>>>>>>>>>>>> Application level and not on Variant level but that can be easily changed. >>>>>>>>>>>>>>>> It depends on how fined grained we want to have these analytics. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I did a small screencast that shows this in action : >>>>>>>>>>>>>>>> https://www.youtube.com/watch?v=PseBBJZLz6s&feature=youtu.be >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The UPS branch containing the changes is here (the 2 >>>>>>>>>>>>>>>> latests commits are relevant) : >>>>>>>>>>>>>>>> https://github.com/sebastienblanc/aerogear-unified-push-server/tree/analytics >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The client app is not really relevant since I really hacked >>>>>>>>>>>>>>>> badly the app (and the push plugin) ;) , however if interested I may share >>>>>>>>>>>>>>>> it. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Now, let's discuss :) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Sebi >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> [1] https://issues.jboss.org/browse/AGPUSH-969 >>>>>>>>>>>>>>>> [2] >>>>>>>>>>>>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/PushMessageInformation.java >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> -- Passos >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at 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 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Matthias Wessendorf >>>>>>>>>> >>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150413/85811e73/attachment-0001.html From scott.cumming at digitalbarriers.com Mon Apr 13 08:55:30 2015 From: scott.cumming at digitalbarriers.com (scottyedinb) Date: Mon, 13 Apr 2015 05:55:30 -0700 (MST) Subject: [aerogear-dev] inactive apns device id notifications in aerogear UPS Message-ID: <1428929730859-11431.post@n5.nabble.com> using aerogear unified push (to push via apns), is there a mechanism by which the caller can be notified that the device Id has become inactive? and that it should look to obtain a new device id? -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/inactive-apns-device-id-notifications-in-aerogear-UPS-tp11431.html Sent from the aerogear-dev mailing list archive at Nabble.com. From dpassos at redhat.com Mon Apr 13 10:22:57 2015 From: dpassos at redhat.com (Daniel Passos) Date: Mon, 13 Apr 2015 11:22:57 -0300 Subject: [aerogear-dev] Team Meeting In-Reply-To: References: Message-ID: Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-13-14.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-13-14.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-13-14.00.log.html On Sun, Apr 12, 2015 at 12:20 PM, Christos Vasilakis wrote: > Agenda: > > http://oksoclap.com/p/aerogear-team-mgt-04.13.2015 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150413/ceeb54db/attachment.html From ivan.gurtler at ahead-itec.com Mon Apr 13 10:37:02 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Mon, 13 Apr 2015 16:37:02 +0200 Subject: [aerogear-dev] AG UPS deadlock In-Reply-To: References: Message-ID: Hi, if we want to add some configuration for schedule ... where other Aerogear Push configuration is? *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-04-10 13:55 GMT+02:00 Ivan G?rtler : > OK I create issue ... https://issues.jboss.org/browse/AGPUSH-1362 > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-04-10 13:19 GMT+02:00 Matthias Wessendorf : > >> >> >> On Fri, Apr 10, 2015 at 12:32 PM, Ivan G?rtler < >> ivan.gurtler at ahead-itec.com> wrote: >> >>> And is it possible in current version to set up time for scheduler not >>> to run at midnight? >>> >> >> unfortunately not - we discussed that option, but I am overasked if we >> actually have a JIRA for that :-) >> But I agree, it should be done, for 1.1.x - for now you would have to >> tweak your fork :) >> >> >>> >>> *Mgr. Ivan G?rtler* >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | >>> mobile security solutions >>> >>> 2015-04-10 11:20 GMT+02:00 Matthias Wessendorf : >>> >>>> Oh, that's this guy, triggered at midnight: >>>> >>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/DeleteOldPushMessageInformationScheduler.java >>>> >>>> It's a singleton, but per node :-/ >>>> >>>> Can you create a JIRA ticket for that ? >>>> >>>> On Fri, Apr 10, 2015 at 10:33 AM, Ivan G?rtler < >>>> ivan.gurtler at ahead-itec.com> wrote: >>>> >>>>> Hi, we use two AG unified push servers with Oracle DB in cluster, but >>>>> we have some problem with deadlock (probably caused by clean up by both >>>>> servers at the same time). >>>>> We used DB owner PUSHSRVAG and application DB account APUSHSRVAG. >>>>> >>>>> (version ... my fork (with small change in dev) ... >>>>> https://github.com/IvanGurtler/aerogear-unifiedpush-server/tree/MyBranch >>>>> ) >>>>> >>>>> Is possible change some settings to prevent deadlock ? or some >>>>> different solution ? >>>>> >>>>> >>>>> ----------------------------------------------------------------------------------------- >>>>> >>>>> *** 2015-04-10 00:00:04.506 >>>>> *** SESSION ID:(84.48937) 2015-04-10 00:00:04.506 >>>>> *** CLIENT ID:() 2015-04-10 00:00:04.506 >>>>> *** SERVICE NAME:(SYS$USERS) 2015-04-10 00:00:04.506 >>>>> *** MODULE NAME:(JDBC Thin Client) 2015-04-10 00:00:04.506 >>>>> *** CLIENT DRIVER:(jdbcthin) 2015-04-10 00:00:04.506 >>>>> *** ACTION NAME:() 2015-04-10 00:00:04.506 >>>>> >>>>> >>>>> >>>>> *** 2015-04-10 00:00:04.506 >>>>> DEADLOCK DETECTED ( ORA-00060 ) >>>>> See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors >>>>> [Transaction Deadlock] >>>>> >>>>> The following deadlock is not an ORACLE error. It is a >>>>> deadlock due to user error in the design of an application >>>>> or from issuing incorrect ad-hoc SQL. The following >>>>> information may aid in determining the deadlock: >>>>> >>>>> Deadlock graph: >>>>> >>>>> ---------Blocker(s)-------- >>>>> ---------Waiter(s)--------- >>>>> Resource Name process >>>>> session holds waits process session holds waits >>>>> TM-00013891-00000000-00000000-00000000 142 84 SX SSX >>>>> 144 162 SX SSX >>>>> TM-00013891-00000000-00000000-00000000 144 162 SX SSX >>>>> 142 84 SX SSX >>>>> >>>>> >>>>> Rows waited on: >>>>> Session 84: no row >>>>> Session 162: no row >>>>> >>>>> ----- Information for the OTHER waiting sessions ----- >>>>> Session 162: >>>>> sid: 162 ser: 54036 audsid: 10790094 user: 115/APUSHSRVAG >>>>> flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/- >>>>> flags2: (0x40009) -/-/INC >>>>> pid: 144 O/S info: user: oracle, term: UNKNOWN, ospid: 11534420 >>>>> image: oracle at s16000ks >>>>> client details: >>>>> O/S info: user: jbotp, term: unknown, ospid: 1234 >>>>> machine: s1.sk.srv.acc.sys program: JDBC Thin Client >>>>> application name: JDBC Thin Client, hash value=2546894660 >>>>> current SQL: >>>>> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >>>>> >>>>> ----- End of information for the OTHER waiting sessions ----- >>>>> >>>>> Information for THIS session: >>>>> >>>>> ----- Current SQL Statement for this session (sql_id=bsk109wpq55yg) >>>>> ----- >>>>> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >>>>> >>>>> >>>>> ----------------------------------------------------------------------------------------- >>>>> >>>>> >>>>> >>>>> >>>>> Thanks >>>>> >>>>> >>>>> *Mgr. Ivan G?rtler* >>>>> Mobile software developer >>>>> >>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>> 602 00 Brno (Czech Republic) >>>>> >>>>> www.ahead-itec.com | twitter | >>>>> mobile security solutions >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150413/53b315b9/attachment.html From matzew at apache.org Mon Apr 13 10:46:51 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 13 Apr 2015 16:46:51 +0200 Subject: [aerogear-dev] inactive apns device id notifications in aerogear UPS In-Reply-To: <1428929730859-11431.post@n5.nabble.com> References: <1428929730859-11431.post@n5.nabble.com> Message-ID: There is a feedback service, which returns 'invalid' tokens (e.g. uninstalled app - or users disabled push). after sending, we call that serivce and remove these tokens from our database On Mon, Apr 13, 2015 at 2:55 PM, scottyedinb < scott.cumming at digitalbarriers.com> wrote: > using aerogear unified push (to push via apns), is there a mechanism by > which > the caller can be notified that the device Id has become inactive? and that > it should look to obtain a new device id? > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/inactive-apns-device-id-notifications-in-aerogear-UPS-tp11431.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150413/e4bc2df9/attachment-0001.html From scott.cumming at digitalbarriers.com Mon Apr 13 11:26:31 2015 From: scott.cumming at digitalbarriers.com (scottyedinb) Date: Mon, 13 Apr 2015 08:26:31 -0700 (MST) Subject: [aerogear-dev] inactive apns device id notifications in aerogear UPS In-Reply-To: References: <1428929730859-11431.post@n5.nabble.com> Message-ID: <1428938791747-11435.post@n5.nabble.com> Thanks for your reply... So supposing I've previously registered an iOS device using the "rest/registry/device" api call.. And I'm pushing to that device from my application (via aerogear of course).. but the associated token has been found by aerogear to be inactive and removed from the database.. Should I expect to receive an exception back in my MessageResponseCallback::OnError method? One more wee thing: For test purposes, is it possible to register false device tokens with aerogear, in order to test the above scenario? -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/inactive-apns-device-id-notifications-in-aerogear-UPS-tp11431p11435.html Sent from the aerogear-dev mailing list archive at Nabble.com. From scm.blanc at gmail.com Mon Apr 13 11:38:10 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 13 Apr 2015 17:38:10 +0200 Subject: [aerogear-dev] inactive apns device id notifications in aerogear UPS In-Reply-To: <1428938791747-11435.post@n5.nabble.com> References: <1428929730859-11431.post@n5.nabble.com> <1428938791747-11435.post@n5.nabble.com> Message-ID: On Mon, Apr 13, 2015 at 5:26 PM, scottyedinb < scott.cumming at digitalbarriers.com> wrote: > Thanks for your reply... > > So supposing I've previously registered an iOS device using the > "rest/registry/device" api call.. You mean using directly the API not using the AeoGear ios Push library ? Because the ios lib will automacilly use the new delivered valid token. > And I'm pushing to that device from my > application (via aerogear of course).. but the associated token has been > found by aerogear to be inactive and removed from the database.. Should I > expect to receive an exception back in my MessageResponseCallback::OnError > method? > No we contact the feedback service only when sending Push Notifications and we don't keep track of invalid tokens. > > One more wee thing: For test purposes, is it possible to register false > device tokens with aerogear, in order to test the above scenario? > Yes, as long it respects the format , take a look at https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/validation/DeviceTokenValidator.java#L35 > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/inactive-apns-device-id-notifications-in-aerogear-UPS-tp11431p11435.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150413/2146da6f/attachment.html From matzew at apache.org Mon Apr 13 11:55:43 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 13 Apr 2015 17:55:43 +0200 Subject: [aerogear-dev] inactive apns device id notifications in aerogear UPS In-Reply-To: <1428938791747-11435.post@n5.nabble.com> References: <1428929730859-11431.post@n5.nabble.com> <1428938791747-11435.post@n5.nabble.com> Message-ID: On Mon, Apr 13, 2015 at 5:26 PM, scottyedinb < scott.cumming at digitalbarriers.com> wrote: > Thanks for your reply... > > So supposing I've previously registered an iOS device using the > "rest/registry/device" api call.. And I'm pushing to that device from my > application (via aerogear of course).. but the associated token has been > found by aerogear to be inactive and removed from the database.. Should I > expect to receive an exception back in my MessageResponseCallback::OnError > method? > No, that's not an error - error is really if the crendtials for the application/masterSecret are wrong, the URL to UPS is wrong, etc. you will receive a 200, if you could post your "send push" request to our server. internally the UPS acts as a broker delivering the tokens to Apple. Apple may (or may not) deliver the message straight to your phone > > One more wee thing: For test purposes, is it possible to register false > device tokens with aerogear, in order to test the above scenario? > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/inactive-apns-device-id-notifications-in-aerogear-UPS-tp11431p11435.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150413/e7ab1c7a/attachment.html From matzew at apache.org Tue Apr 14 04:46:43 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Apr 2015 10:46:43 +0200 Subject: [aerogear-dev] AG UPS deadlock In-Reply-To: References: Message-ID: we don't really have configuration needs for stuff like that. However, we do have a system property for APNs/GCM server URI replacements (due to testing), but that's really all On Mon, Apr 13, 2015 at 4:37 PM, Ivan G?rtler wrote: > Hi, > if we want to add some configuration for schedule ... where other Aerogear > Push configuration is? > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-04-10 13:55 GMT+02:00 Ivan G?rtler : > >> OK I create issue ... https://issues.jboss.org/browse/AGPUSH-1362 >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-04-10 13:19 GMT+02:00 Matthias Wessendorf : >> >>> >>> >>> On Fri, Apr 10, 2015 at 12:32 PM, Ivan G?rtler < >>> ivan.gurtler at ahead-itec.com> wrote: >>> >>>> And is it possible in current version to set up time for scheduler not >>>> to run at midnight? >>>> >>> >>> unfortunately not - we discussed that option, but I am overasked if we >>> actually have a JIRA for that :-) >>> But I agree, it should be done, for 1.1.x - for now you would have to >>> tweak your fork :) >>> >>> >>>> >>>> *Mgr. Ivan G?rtler* >>>> Mobile software developer >>>> >>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> 602 00 Brno (Czech Republic) >>>> >>>> www.ahead-itec.com | twitter | >>>> mobile security solutions >>>> >>>> 2015-04-10 11:20 GMT+02:00 Matthias Wessendorf : >>>> >>>>> Oh, that's this guy, triggered at midnight: >>>>> >>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/metrics/DeleteOldPushMessageInformationScheduler.java >>>>> >>>>> It's a singleton, but per node :-/ >>>>> >>>>> Can you create a JIRA ticket for that ? >>>>> >>>>> On Fri, Apr 10, 2015 at 10:33 AM, Ivan G?rtler < >>>>> ivan.gurtler at ahead-itec.com> wrote: >>>>> >>>>>> Hi, we use two AG unified push servers with Oracle DB in cluster, but >>>>>> we have some problem with deadlock (probably caused by clean up by both >>>>>> servers at the same time). >>>>>> We used DB owner PUSHSRVAG and application DB account APUSHSRVAG. >>>>>> >>>>>> (version ... my fork (with small change in dev) ... >>>>>> https://github.com/IvanGurtler/aerogear-unifiedpush-server/tree/MyBranch >>>>>> ) >>>>>> >>>>>> Is possible change some settings to prevent deadlock ? or some >>>>>> different solution ? >>>>>> >>>>>> >>>>>> ----------------------------------------------------------------------------------------- >>>>>> >>>>>> *** 2015-04-10 00:00:04.506 >>>>>> *** SESSION ID:(84.48937) 2015-04-10 00:00:04.506 >>>>>> *** CLIENT ID:() 2015-04-10 00:00:04.506 >>>>>> *** SERVICE NAME:(SYS$USERS) 2015-04-10 00:00:04.506 >>>>>> *** MODULE NAME:(JDBC Thin Client) 2015-04-10 00:00:04.506 >>>>>> *** CLIENT DRIVER:(jdbcthin) 2015-04-10 00:00:04.506 >>>>>> *** ACTION NAME:() 2015-04-10 00:00:04.506 >>>>>> >>>>>> >>>>>> >>>>>> *** 2015-04-10 00:00:04.506 >>>>>> DEADLOCK DETECTED ( ORA-00060 ) >>>>>> See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors >>>>>> [Transaction Deadlock] >>>>>> >>>>>> The following deadlock is not an ORACLE error. It is a >>>>>> deadlock due to user error in the design of an application >>>>>> or from issuing incorrect ad-hoc SQL. The following >>>>>> information may aid in determining the deadlock: >>>>>> >>>>>> Deadlock graph: >>>>>> >>>>>> ---------Blocker(s)-------- >>>>>> ---------Waiter(s)--------- >>>>>> Resource Name process >>>>>> session holds waits process session holds waits >>>>>> TM-00013891-00000000-00000000-00000000 142 84 SX SSX >>>>>> 144 162 SX SSX >>>>>> TM-00013891-00000000-00000000-00000000 144 162 SX SSX >>>>>> 142 84 SX SSX >>>>>> >>>>>> >>>>>> Rows waited on: >>>>>> Session 84: no row >>>>>> Session 162: no row >>>>>> >>>>>> ----- Information for the OTHER waiting sessions ----- >>>>>> Session 162: >>>>>> sid: 162 ser: 54036 audsid: 10790094 user: 115/APUSHSRVAG >>>>>> flags: (0x41) USR/- flags_idl: (0x1) BSY/-/-/-/-/- >>>>>> flags2: (0x40009) -/-/INC >>>>>> pid: 144 O/S info: user: oracle, term: UNKNOWN, ospid: 11534420 >>>>>> image: oracle at s16000ks >>>>>> client details: >>>>>> O/S info: user: jbotp, term: unknown, ospid: 1234 >>>>>> machine: s1.sk.srv.acc.sys program: JDBC Thin Client >>>>>> application name: JDBC Thin Client, hash value=2546894660 >>>>>> current SQL: >>>>>> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >>>>>> >>>>>> ----- End of information for the OTHER waiting sessions ----- >>>>>> >>>>>> Information for THIS session: >>>>>> >>>>>> ----- Current SQL Statement for this session (sql_id=bsk109wpq55yg) >>>>>> ----- >>>>>> delete from PUSHSRVAG.PushMessageInformation where submitDate<:1 >>>>>> >>>>>> >>>>>> ----------------------------------------------------------------------------------------- >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Thanks >>>>>> >>>>>> >>>>>> *Mgr. Ivan G?rtler* >>>>>> Mobile software developer >>>>>> >>>>>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>>>>> 602 00 Brno (Czech Republic) >>>>>> >>>>>> www.ahead-itec.com | twitter | >>>>>> mobile security solutions >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150414/027f6dbd/attachment-0001.html From corinnekrych at gmail.com Tue Apr 14 05:09:53 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 14 Apr 2015 11:09:53 +0200 Subject: [aerogear-dev] iOS roadmap update Message-ID: Hello iOS lovers, Sync 1.0.0-0alpha 1 uses Objective-C third parties libs JSONTools [2] and [2] not 100% following the specs but still doing the job after some hacks around[3] Plan is to build Swift version of the libs is moved out of 2.3 release. I think we should move those thickets to either 2.4 (June release) or 2.5 (September release) to match alpha2 schedule. Thoughts? ++ Corinne [1] https://github.com/s9tpepper/JSONTools [2] https://github.com/samskiter/KiteJSONValidator [3] https://github.com/aerogear/aerogear-ios-sync/blob/master/AeroGearSync-JSONPatch%2FJsonPatchSynchronizer.swift#L91 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150414/267b4d2f/attachment.html From matzew at apache.org Tue Apr 14 05:12:27 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 14 Apr 2015 11:12:27 +0200 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: Corinne, will you update this app as well ? https://github.com/jboss-mobile/unified-push-helloworld/tree/swift/ios-swift On Fri, Apr 10, 2015 at 3:41 PM, Corinne Krych wrote: > Unfortunately Travis is not ready yet [1] > I will prepare the PR and test it so we can merge when Travis is ready. > ++ > Corinne > [1] http://blog.travis-ci.com/2015-04-09-this-week-in-travis-ci/ > [2] https://travis-ci.org/corinnekrych/aerogear-ios-http-1/builds/57947586 > > On 10 April 2015 at 14:17, Corinne Krych wrote: > >> >> >> On 10 April 2015 at 11:26, Christos Vasilakis wrote: >> >>> >>> >>> On Fri, Apr 10, 2015 at 9:57 AM, Corinne Krych >>> wrote: >>> >>>> Hello iOS lovers, >>>> >>>> Xcode 6.3 is officially out (since 2 days actually). >>>> And Travis build seems to be ready. >>>> >>>> Xcode 6.3 comes with Swift 1.2, so it implies some (minor) compilation >>>> changes. >>>> I think it?s time to move to this new stable version. I have created >>>> the JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS >>>> release (end of April). >>>> >>> >>> +9001 >>> >>> long time to see only one release out and no myriad of betas ;) >>> *http://tinyurl.com/po946bv * >>> >>> >> >> Indeed! >> :) >> >> >>> >>> >>> >>>> Any questions, toughts? >>>> ++ >>>> Corinne >>>> [1] https://issues.jboss.org/browse/AGIOS-428 >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150414/04d33d5d/attachment.html From corinnekrych at gmail.com Tue Apr 14 05:16:00 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 14 Apr 2015 11:16:00 +0200 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: Off course I'm doing it atm ++ Corinne On 14 April 2015 at 11:12, Matthias Wessendorf wrote: > Corinne, > > will you update this app as well ? > > https://github.com/jboss-mobile/unified-push-helloworld/tree/swift/ios-swift > > > > On Fri, Apr 10, 2015 at 3:41 PM, Corinne Krych > wrote: > >> Unfortunately Travis is not ready yet [1] >> I will prepare the PR and test it so we can merge when Travis is ready. >> ++ >> Corinne >> [1] http://blog.travis-ci.com/2015-04-09-this-week-in-travis-ci/ >> [2] >> https://travis-ci.org/corinnekrych/aerogear-ios-http-1/builds/57947586 >> >> On 10 April 2015 at 14:17, Corinne Krych wrote: >> >>> >>> >>> On 10 April 2015 at 11:26, Christos Vasilakis >>> wrote: >>> >>>> >>>> >>>> On Fri, Apr 10, 2015 at 9:57 AM, Corinne Krych >>>> wrote: >>>> >>>>> Hello iOS lovers, >>>>> >>>>> Xcode 6.3 is officially out (since 2 days actually). >>>>> And Travis build seems to be ready. >>>>> >>>>> Xcode 6.3 comes with Swift 1.2, so it implies some (minor) compilation >>>>> changes. >>>>> I think it?s time to move to this new stable version. I have created >>>>> the JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS >>>>> release (end of April). >>>>> >>>> >>>> +9001 >>>> >>>> long time to see only one release out and no myriad of betas ;) >>>> *http://tinyurl.com/po946bv * >>>> >>>> >>> >>> Indeed! >>> :) >>> >>> >>>> >>>> >>>> >>>>> Any questions, toughts? >>>>> ++ >>>>> Corinne >>>>> [1] https://issues.jboss.org/browse/AGIOS-428 >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150414/6a22d4fa/attachment.html From matzew at apache.org Wed Apr 15 02:37:25 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 15 Apr 2015 08:37:25 +0200 Subject: [aerogear-dev] UPS: Deleting 1.0.x branch ? Message-ID: Hi, the 1.0.x line is put to bed, and we have a tag for 1.0.3. Since there is no plan to have a 1.0.4, I'd propose deleting this branch. That said, if there is a need for a 1.0.4 (e.g. security issues), we can branch of the 1.0.3 tag, therefore I see no sense in maintaining this branch.. Any thoughts? -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150415/f23f5fb2/attachment.html From cvasilak at gmail.com Wed Apr 15 02:41:21 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Wed, 15 Apr 2015 09:41:21 +0300 Subject: [aerogear-dev] UPS: Deleting 1.0.x branch ? In-Reply-To: References: Message-ID: On Wed, Apr 15, 2015 at 9:37 AM, Matthias Wessendorf wrote: > Hi, > > the 1.0.x line is put to bed, and we have a tag for 1.0.3. > > Since there is no plan to have a 1.0.4, I'd propose deleting this branch. > +1 > > That said, if there is a need for a 1.0.4 (e.g. security issues), we can > branch of the 1.0.3 tag, therefore I see no sense in maintaining this > branch.. > makes sense > > Any thoughts? > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150415/0247b37c/attachment-0001.html From scm.blanc at gmail.com Wed Apr 15 02:47:23 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 15 Apr 2015 08:47:23 +0200 Subject: [aerogear-dev] UPS: Deleting 1.0.x branch ? In-Reply-To: References: Message-ID: +1 On Wed, Apr 15, 2015 at 8:41 AM, Christos Vasilakis wrote: > > > On Wed, Apr 15, 2015 at 9:37 AM, Matthias Wessendorf > wrote: > >> Hi, >> >> the 1.0.x line is put to bed, and we have a tag for 1.0.3. >> >> Since there is no plan to have a 1.0.4, I'd propose deleting this branch. >> > > +1 > > >> >> That said, if there is a need for a 1.0.4 (e.g. security issues), we can >> branch of the 1.0.3 tag, therefore I see no sense in maintaining this >> branch.. >> > > makes sense > > >> >> Any thoughts? >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150415/49e5cf4a/attachment.html From lukas.fryc at gmail.com Wed Apr 15 04:25:38 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 15 Apr 2015 08:25:38 +0000 Subject: [aerogear-dev] UPS: Deleting 1.0.x branch ? In-Reply-To: References: Message-ID: +1 st 15. 4. 2015 v 8:47 odes?latel Sebastien Blanc napsal: > +1 > > On Wed, Apr 15, 2015 at 8:41 AM, Christos Vasilakis > wrote: > >> >> >> On Wed, Apr 15, 2015 at 9:37 AM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> the 1.0.x line is put to bed, and we have a tag for 1.0.3. >>> >>> Since there is no plan to have a 1.0.4, I'd propose deleting this branch. >>> >> >> +1 >> >> >>> >>> That said, if there is a need for a 1.0.4 (e.g. security issues), we can >>> branch of the 1.0.3 tag, therefore I see no sense in maintaining this >>> branch.. >>> >> >> makes sense >> >> >>> >>> Any thoughts? >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150415/40c5a13a/attachment.html From banddk1 at gmail.com Thu Apr 16 08:37:10 2015 From: banddk1 at gmail.com (=?UTF-8?B?0JTQtdC90LjRgSDQmtCw0YDQv9C10L3QutC+?=) Date: Thu, 16 Apr 2015 15:37:10 +0300 Subject: [aerogear-dev] AeroDoc Message-ID: Hi Everyone ! I am going to start porting Aerodoc to Swift. So I'd like to know, what we will do with modifying the use-case - to not be "doctor" specific ? I see two options: 1) We continue to make the application for doctors. I will slightly change UI and port to swift. 2) We will make global changes. To do this, we need to come up with the theme of a new application, and sketch main features of it. P.S I think the app for doctors is ok, and with a new design, it can find a second life. Denis. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150416/894a781d/attachment.html From matzew at apache.org Thu Apr 16 08:45:43 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 16 Apr 2015 14:45:43 +0200 Subject: [aerogear-dev] AeroDoc In-Reply-To: References: Message-ID: On Thu, Apr 16, 2015 at 2:37 PM, ????? ???????? wrote: > Hi Everyone ! > I am going to start porting Aerodoc to Swift. So I'd like to know, what we > will do with modifying the use-case - to not be "doctor" specific ? > I see two options: > 1) We continue to make the application for doctors. I will slightly change > UI and port to swift. > +1 that makes sense for first run > > 2) We will make global changes. To do this, we need to come up with the > theme of a new application, and sketch main features of it. > > P.S I think the app for doctors is ok, and with a new design, it can find > a second life. > > > Denis. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150416/ea28e373/attachment.html From qmx at qmx.me Wed Apr 15 05:36:01 2015 From: qmx at qmx.me (Douglas Campos) Date: Wed, 15 Apr 2015 06:36:01 -0300 Subject: [aerogear-dev] UPS: Deleting 1.0.x branch ? In-Reply-To: References: Message-ID: +1 On Apr 15, 2015 3:38 AM, "Matthias Wessendorf" wrote: > Hi, > > the 1.0.x line is put to bed, and we have a tag for 1.0.3. > > Since there is no plan to have a 1.0.4, I'd propose deleting this branch. > > That said, if there is a need for a 1.0.4 (e.g. security issues), we can > branch of the 1.0.3 tag, therefore I see no sense in maintaining this > branch.. > > Any thoughts? > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150415/3b3327cf/attachment.html From cvasilak at gmail.com Mon Apr 20 02:30:58 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 20 Apr 2015 09:30:58 +0300 Subject: [aerogear-dev] Team Meeting Message-ID: agenda: http://oksoclap.com/p/aerogear-team-mgt-04.20.2015 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150420/c61dc596/attachment.html From corinnekrych at gmail.com Mon Apr 20 07:54:45 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 20 Apr 2015 13:54:45 +0200 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: Hello All, Let me give you an update on Swift 1.2: all Swift repos has been updated (PR sent and under review). See [1] The only missing part is the lack of Travis support for Xcode 6.3. Although initial announcement from April 9th says: good news will happen "next week" (ie: last week), we still don't have xcode63 support. iOS and OSX community is eagerly asking for it [2] but no clear answer so far :( Given the iOS 2.3 planned release end of this week, I'd propose to merge this PRs without travis support. And keep an eyes on Travis Xcode63 support. Thoughts? ++ Corinne [1] https://issues.jboss.org/browse/AGIOS-428 [2] https://twitter.com/rob_rix/status/589774192813432832 On 14 April 2015 at 11:16, Corinne Krych wrote: > Off course > I'm doing it atm > ++ > Corinne > > On 14 April 2015 at 11:12, Matthias Wessendorf wrote: > >> Corinne, >> >> will you update this app as well ? >> >> https://github.com/jboss-mobile/unified-push-helloworld/tree/swift/ios-swift >> >> >> >> On Fri, Apr 10, 2015 at 3:41 PM, Corinne Krych >> wrote: >> >>> Unfortunately Travis is not ready yet [1] >>> I will prepare the PR and test it so we can merge when Travis is ready. >>> ++ >>> Corinne >>> [1] http://blog.travis-ci.com/2015-04-09-this-week-in-travis-ci/ >>> [2] >>> https://travis-ci.org/corinnekrych/aerogear-ios-http-1/builds/57947586 >>> >>> On 10 April 2015 at 14:17, Corinne Krych wrote: >>> >>>> >>>> >>>> On 10 April 2015 at 11:26, Christos Vasilakis >>>> wrote: >>>> >>>>> >>>>> >>>>> On Fri, Apr 10, 2015 at 9:57 AM, Corinne Krych >>>> > wrote: >>>>> >>>>>> Hello iOS lovers, >>>>>> >>>>>> Xcode 6.3 is officially out (since 2 days actually). >>>>>> And Travis build seems to be ready. >>>>>> >>>>>> Xcode 6.3 comes with Swift 1.2, so it implies some (minor) >>>>>> compilation changes. >>>>>> I think it?s time to move to this new stable version. I have created >>>>>> the JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS >>>>>> release (end of April). >>>>>> >>>>> >>>>> +9001 >>>>> >>>>> long time to see only one release out and no myriad of betas ;) >>>>> *http://tinyurl.com/po946bv * >>>>> >>>>> >>>> >>>> Indeed! >>>> :) >>>> >>>> >>>>> >>>>> >>>>> >>>>>> Any questions, toughts? >>>>>> ++ >>>>>> Corinne >>>>>> [1] https://issues.jboss.org/browse/AGIOS-428 >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150420/ccbc35da/attachment-0001.html From lholmqui at redhat.com Mon Apr 20 08:15:36 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Mon, 20 Apr 2015 08:15:36 -0400 Subject: [aerogear-dev] UPS: Deleting 1.0.x branch ? In-Reply-To: References: Message-ID: do it On Wed, Apr 15, 2015 at 5:36 AM, Douglas Campos wrote: > +1 > On Apr 15, 2015 3:38 AM, "Matthias Wessendorf" wrote: > >> Hi, >> >> the 1.0.x line is put to bed, and we have a tag for 1.0.3. >> >> Since there is no plan to have a 1.0.4, I'd propose deleting this branch. >> >> That said, if there is a need for a 1.0.4 (e.g. security issues), we can >> branch of the 1.0.3 tag, therefore I see no sense in maintaining this >> branch.. >> >> Any thoughts? >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150420/b73608a4/attachment.html From cvasilak at gmail.com Mon Apr 20 08:31:17 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 20 Apr 2015 15:31:17 +0300 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: On Mon, Apr 20, 2015 at 2:54 PM, Corinne Krych wrote: > Hello All, > > Let me give you an update on Swift 1.2: all Swift repos has been updated > (PR sent and under review). See [1] > > The only missing part is the lack of Travis support for Xcode 6.3. > > Although initial announcement from April 9th says: good news will happen > "next week" (ie: last week), we still don't have xcode63 support. iOS and > OSX community is eagerly asking for it [2] but no clear answer so far :( > > Given the iOS 2.3 planned release end of this week, I'd propose to merge > this PRs without travis support. And keep an eyes on Travis Xcode63 support. > > Thoughts? > > +1 let's not block cause of delay's of Travis and release the bits - Christos > ++ > Corinne > > [1] https://issues.jboss.org/browse/AGIOS-428 > [2] https://twitter.com/rob_rix/status/589774192813432832 > > On 14 April 2015 at 11:16, Corinne Krych wrote: > >> Off course >> I'm doing it atm >> ++ >> Corinne >> >> On 14 April 2015 at 11:12, Matthias Wessendorf wrote: >> >>> Corinne, >>> >>> will you update this app as well ? >>> >>> https://github.com/jboss-mobile/unified-push-helloworld/tree/swift/ios-swift >>> >>> >>> >>> On Fri, Apr 10, 2015 at 3:41 PM, Corinne Krych >>> wrote: >>> >>>> Unfortunately Travis is not ready yet [1] >>>> I will prepare the PR and test it so we can merge when Travis is ready. >>>> ++ >>>> Corinne >>>> [1] http://blog.travis-ci.com/2015-04-09-this-week-in-travis-ci/ >>>> [2] >>>> https://travis-ci.org/corinnekrych/aerogear-ios-http-1/builds/57947586 >>>> >>>> On 10 April 2015 at 14:17, Corinne Krych >>>> wrote: >>>> >>>>> >>>>> >>>>> On 10 April 2015 at 11:26, Christos Vasilakis >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Fri, Apr 10, 2015 at 9:57 AM, Corinne Krych < >>>>>> corinnekrych at gmail.com> wrote: >>>>>> >>>>>>> Hello iOS lovers, >>>>>>> >>>>>>> Xcode 6.3 is officially out (since 2 days actually). >>>>>>> And Travis build seems to be ready. >>>>>>> >>>>>>> Xcode 6.3 comes with Swift 1.2, so it implies some (minor) >>>>>>> compilation changes. >>>>>>> I think it?s time to move to this new stable version. I have created >>>>>>> the JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS >>>>>>> release (end of April). >>>>>>> >>>>>> >>>>>> +9001 >>>>>> >>>>>> long time to see only one release out and no myriad of betas ;) >>>>>> *http://tinyurl.com/po946bv * >>>>>> >>>>>> >>>>> >>>>> Indeed! >>>>> :) >>>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>>> Any questions, toughts? >>>>>>> ++ >>>>>>> Corinne >>>>>>> [1] https://issues.jboss.org/browse/AGIOS-428 >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150420/b3ef6caa/attachment.html From cvasilak at gmail.com Mon Apr 20 10:17:30 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 20 Apr 2015 17:17:30 +0300 Subject: [aerogear-dev] Team Meeting In-Reply-To: References: Message-ID: fyi, meeting minutes: Meeting ended Mon Apr 20 14:15:45 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-20-14.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-20-14.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-20-14.00.log.html On Mon, Apr 20, 2015 at 9:30 AM, Christos Vasilakis wrote: > agenda: > > http://oksoclap.com/p/aerogear-team-mgt-04.20.2015 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150420/a81fdd02/attachment.html From scm.blanc at gmail.com Mon Apr 20 15:03:37 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 21 Apr 2015 00:33:37 +0530 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: +1 We are way more cooler than travis ;) On Mon, Apr 20, 2015 at 6:01 PM, Christos Vasilakis wrote: > > > On Mon, Apr 20, 2015 at 2:54 PM, Corinne Krych > wrote: > >> Hello All, >> >> Let me give you an update on Swift 1.2: all Swift repos has been updated >> (PR sent and under review). See [1] >> >> The only missing part is the lack of Travis support for Xcode 6.3. >> >> Although initial announcement from April 9th says: good news will happen >> "next week" (ie: last week), we still don't have xcode63 support. iOS and >> OSX community is eagerly asking for it [2] but no clear answer so far :( >> >> Given the iOS 2.3 planned release end of this week, I'd propose to merge >> this PRs without travis support. And keep an eyes on Travis Xcode63 support. >> >> Thoughts? >> >> > +1 let's not block cause of delay's of Travis and release the bits > > - > Christos > > > >> ++ >> Corinne >> >> [1] https://issues.jboss.org/browse/AGIOS-428 >> [2] https://twitter.com/rob_rix/status/589774192813432832 >> >> On 14 April 2015 at 11:16, Corinne Krych wrote: >> >>> Off course >>> I'm doing it atm >>> ++ >>> Corinne >>> >>> On 14 April 2015 at 11:12, Matthias Wessendorf >>> wrote: >>> >>>> Corinne, >>>> >>>> will you update this app as well ? >>>> >>>> https://github.com/jboss-mobile/unified-push-helloworld/tree/swift/ios-swift >>>> >>>> >>>> >>>> On Fri, Apr 10, 2015 at 3:41 PM, Corinne Krych >>>> wrote: >>>> >>>>> Unfortunately Travis is not ready yet [1] >>>>> I will prepare the PR and test it so we can merge when Travis is ready. >>>>> ++ >>>>> Corinne >>>>> [1] http://blog.travis-ci.com/2015-04-09-this-week-in-travis-ci/ >>>>> [2] >>>>> https://travis-ci.org/corinnekrych/aerogear-ios-http-1/builds/57947586 >>>>> >>>>> On 10 April 2015 at 14:17, Corinne Krych >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On 10 April 2015 at 11:26, Christos Vasilakis >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Apr 10, 2015 at 9:57 AM, Corinne Krych < >>>>>>> corinnekrych at gmail.com> wrote: >>>>>>> >>>>>>>> Hello iOS lovers, >>>>>>>> >>>>>>>> Xcode 6.3 is officially out (since 2 days actually). >>>>>>>> And Travis build seems to be ready. >>>>>>>> >>>>>>>> Xcode 6.3 comes with Swift 1.2, so it implies some (minor) >>>>>>>> compilation changes. >>>>>>>> I think it?s time to move to this new stable version. I have >>>>>>>> created the JIRA epic/ticket [1] and I?ll start the migration targetting >>>>>>>> 2.3 iOS release (end of April). >>>>>>>> >>>>>>> >>>>>>> +9001 >>>>>>> >>>>>>> long time to see only one release out and no myriad of betas ;) >>>>>>> *http://tinyurl.com/po946bv * >>>>>>> >>>>>>> >>>>>> >>>>>> Indeed! >>>>>> :) >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Any questions, toughts? >>>>>>>> ++ >>>>>>>> Corinne >>>>>>>> [1] https://issues.jboss.org/browse/AGIOS-428 >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/e96075f7/attachment-0001.html From matzew at apache.org Tue Apr 21 03:44:02 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 21 Apr 2015 09:44:02 +0200 Subject: [aerogear-dev] UPS: Deleting 1.0.x branch ? In-Reply-To: References: Message-ID: adios and good bye! Branch deleted On Mon, Apr 20, 2015 at 2:15 PM, Luke Holmquist wrote: > do it > > On Wed, Apr 15, 2015 at 5:36 AM, Douglas Campos wrote: > >> +1 >> On Apr 15, 2015 3:38 AM, "Matthias Wessendorf" wrote: >> >>> Hi, >>> >>> the 1.0.x line is put to bed, and we have a tag for 1.0.3. >>> >>> Since there is no plan to have a 1.0.4, I'd propose deleting this branch. >>> >>> That said, if there is a need for a 1.0.4 (e.g. security issues), we can >>> branch of the 1.0.3 tag, therefore I see no sense in maintaining this >>> branch.. >>> >>> Any thoughts? >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/fcb747da/attachment.html From corinnekrych at gmail.com Tue Apr 21 05:34:28 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 21 Apr 2015 11:34:28 +0200 Subject: [aerogear-dev] Helping us to release iOS 2.3 Message-ID: Hello iOS lovers, We?re preparing iOS 2.3 release. Main focus of this release has been to move our Swift repo to iOS 8.3 (swift 1.2) and some improvement on OAuth2 support. As a result of the miration to Swift 1.2, most lib will need a release: ? aerogear-ios-push ? aerogear-ios-sync ? aerogear-ios-sync-client ? aerogear-ios-http ? aerogear-ios-oauth2 ? aerogear-ios-jsonsz ? aerogear-ios-cookbook Here is the content of our release: https://issues.jboss.org/browse/AGIOS/fixforversion/12325987 This thread is the place to shout it out loud if you find something wrong. If everything goes smooth, a tag and cocoapods release will happen on Fiday 24th April. ++ Corinne From matzew at apache.org Tue Apr 21 07:38:47 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 21 Apr 2015 13:38:47 +0200 Subject: [aerogear-dev] DBUnit and DB migration issue Message-ID: Hi team, merging/rebasing the migration PR, I am getting one test failure, with a weird "SQLGrammarException: could not prepare statement" error, when merging the categories: ------------------------------------------------------------------------------- Test set: org.jboss.aerogear.unifiedpush.jpa.InstallationDaoTest ------------------------------------------------------------------------------- Tests run: 34, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.519 sec <<< FAILURE! mergeCategories(org.jboss.aerogear.unifiedpush.jpa.InstallationDaoTest) Time elapsed: 0.041 sec <<< ERROR! javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not prepare statement at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.sql.compile.NextSequenceNode.bindExpression(Unknown Source) at org.apache.derby.impl.sql.compile.ValueNode.bindExpression(Unknown Source) at org.apache.derby.impl.sql.compile.ResultColumn.bindExpression(Unknown Source) at org.apache.derby.impl.sql.compile.ResultColumnList.bindExpressions(Unknown Source) at org.apache.derby.impl.sql.compile.RowResultSetNode.bindExpressions(Unknown Source) at org.apache.derby.impl.sql.compile.DMLStatementNode.bindExpressions(Unknown Source) at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(Unknown Source) at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(Unknown Source) at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source) at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source) at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement40.(Unknown Source) at org.apache.derby.jdbc.Driver40.newEmbedPreparedStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source) at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$1.doPrepare(StatementPreparerImpl.java:96) at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:183) at org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareStatement(StatementPreparerImpl.java:83) at org.hibernate.id.SequenceGenerator.generateHolder(SequenceGenerator.java:120) at org.hibernate.id.SequenceHiLoGenerator$1.getNextValue(SequenceHiLoGenerator.java:81) at org.hibernate.id.enhanced.OptimizerFactory$LegacyHiLoAlgorithmOptimizer.generate(OptimizerFactory.java:399) at org.hibernate.id.SequenceHiLoGenerator.generate(SequenceHiLoGenerator.java:78) at org.hibernate.event.internal.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:117) at org.hibernate.ejb.event.EJB3PersistEventListener.saveWithGeneratedId(EJB3PersistEventListener.java:78) at org.hibernate.event.internal.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:208) at org.hibernate.event.internal.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:151) at org.hibernate.internal.SessionImpl.firePersist(SessionImpl.java:762) at org.hibernate.internal.SessionImpl.persist(SessionImpl.java:755) at org.hibernate.ejb.engine.spi.EJB3CascadingAction$1.cascade(EJB3CascadingAction.java:53) at org.hibernate.engine.internal.Cascade.cascadeToOne(Cascade.java:396) at org.hibernate.engine.internal.Cascade.cascadeAssociation(Cascade.java:339) at org.hibernate.engine.internal.Cascade.cascadeProperty(Cascade.java:207) at org.hibernate.engine.internal.Cascade.cascadeCollectionElements(Cascade.java:426) at org.hibernate.engine.internal.Cascade.cascadeCollection(Cascade.java:366) at org.hibernate.engine.internal.Cascade.cascadeAssociation(Cascade.java:342) at org.hibernate.engine.internal.Cascade.cascadeProperty(Cascade.java:207) at org.hibernate.engine.internal.Cascade.cascade(Cascade.java:164) at org.hibernate.event.internal.AbstractSaveEventListener.cascadeAfterSave(AbstractSaveEventListener.java:449) at org.hibernate.event.internal.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:292) at org.hibernate.event.internal.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:192) at org.hibernate.event.internal.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:135) at org.hibernate.ejb.event.EJB3PersistEventListener.saveWithGeneratedId(EJB3PersistEventListener.java:78) at org.hibernate.event.internal.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:208) at org.hibernate.event.internal.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:151) at org.hibernate.event.internal.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:78) at org.hibernate.internal.SessionImpl.firePersist(SessionImpl.java:772) at org.hibernate.internal.SessionImpl.persist(SessionImpl.java:746) at org.hibernate.internal.SessionImpl.persist(SessionImpl.java:750) at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:875) at sun.reflect.GeneratedMethodAccessor163.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:44) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:105) at org.jboss.weld.proxies.EntityManager$1406262522$Proxy$_$$_WeldClientProxy.persist(EntityManager$1406262522$Proxy$_$$_WeldClientProxy.java) at org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPABaseDao.create(JPABaseDao.java:55) at org.jboss.aerogear.unifiedpush.jpa.InstallationDaoTest.mergeCategories(InstallationDaoTest.java:234) Looks like the error is due to the sequence table, added to ORM: https://github.com/aerogear/aerogear-unifiedpush-server/commit/d9a7ab913d907d742a9dd23238b8a743f177efa5 Now, the sequence table is part of the DDL script: https://github.com/matzew/aerogear-unifiedpush-server/blob/Migration_merge_latest/model/jpa/testData/create_db_content.ddl#L22-L36 But it's missing the dataset XML files for DBunit, however Erik Jan tried adding it here: https://github.com/edewit/aerogear-unifiedpush-server/commit/93a6a9af0b009d6e2f47c48e0f5980e5ab81b556 But that also does not help ;-( However, Gunnar (from Hibernate team) thinks the problem is that this ddl creates sequence as table, where SequenceGenerator is expecting an actual sequence I think I am a bit over asked here, from both DBUnit and the migration aspects. Therefore any feedback on these issues is more than welcome :-) Thanks a lot! -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/cfabf68b/attachment-0001.html From supittma at redhat.com Tue Apr 21 10:02:10 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 21 Apr 2015 10:02:10 -0400 Subject: [aerogear-dev] AeroGear Messaging Message-ID: So IoT is getting a lot of attention within the company (or at least within my monkeysphere). From the demo project I've noticed that a lot of the work is in messaging and message handling. What do you guys think about exploring this space more? How does it / can it /should it fit into our roadmap? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/9e51bcad/attachment.html From lholmqui at redhat.com Tue Apr 21 10:13:18 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 21 Apr 2015 10:13:18 -0400 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: References: Message-ID: like Notifier? On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman wrote: > So IoT is getting a lot of attention within the company (or at least > within my monkeysphere). From the demo project I've noticed that a lot of > the work is in messaging and message handling. What do you guys think > about exploring this space more? How does it / can it /should it fit into > our roadmap? > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/25247b3b/attachment.html From matzew at apache.org Tue Apr 21 10:19:52 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 21 Apr 2015 16:19:52 +0200 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: References: Message-ID: more something like a unified messanger platform, where we have real messaging hooks/adapters (client/server) for protocols like AMQP, MQTT, XMPP etc while having support for push notifications as well. That would be nice to have, at some point On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist wrote: > like Notifier? > > On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman > wrote: > >> So IoT is getting a lot of attention within the company (or at least >> within my monkeysphere). From the demo project I've noticed that a lot of >> the work is in messaging and message handling. What do you guys think >> about exploring this space more? How does it / can it /should it fit into >> our roadmap? >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/f172d40d/attachment.html From supittma at redhat.com Tue Apr 21 10:22:54 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 21 Apr 2015 10:22:54 -0400 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: References: Message-ID: On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf wrote: > more something like a unified messanger platform, where we have real > messaging hooks/adapters (client/server) for protocols like AMQP, MQTT, > XMPP etc while having support for push notifications as well. > We could probably extend the Push API. I mean it already does half the work for us ;) > > That would be nice to have, at some point > > On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist > wrote: > >> like Notifier? >> >> On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman >> wrote: >> >>> So IoT is getting a lot of attention within the company (or at least >>> within my monkeysphere). From the demo project I've noticed that a lot of >>> the work is in messaging and message handling. What do you guys think >>> about exploring this space more? How does it / can it /should it fit into >>> our roadmap? >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/a5ffe9b7/attachment.html From bsutter at redhat.com Tue Apr 21 10:43:41 2015 From: bsutter at redhat.com (Burr Sutter) Date: Tue, 21 Apr 2015 10:43:41 -0400 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: References: Message-ID: We already have ActiveMQ, a message broker that will deal with things like ?durable subscriptions?, holding messages until the subscriber wakes up and acknowledges receipt. There is also Mosca as a Node.js-based MQTT focused message broker. There will be a wide spectrum of Things - from most distributed edge sensors with energy harvesting (smart dust) to robust ?gateway? servers that look a lot like your typical datacenter server today. It is currently unclear to me which of the application protocols will ?win?. At this moment, MQTT is a winner (great support from numerous vendors) and I feel that CoAP will be a winner as well. AMQP or DDS may win on the beefier gateways but not so much edge intelligent things. > On Apr 21, 2015, at 10:22 AM, Summers Pittman wrote: > > > > On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf > wrote: > more something like a unified messanger platform, where we have real messaging hooks/adapters (client/server) for protocols like AMQP, MQTT, XMPP etc while having support for push notifications as well. > We could probably extend the Push API. I mean it already does half the work for us ;) > > That would be nice to have, at some point > > On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist > wrote: > like Notifier? > > On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman > wrote: > So IoT is getting a lot of attention within the company (or at least within my monkeysphere). From the demo project I've noticed that a lot of the work is in messaging and message handling. What do you guys think about exploring this space more? How does it / can it /should it fit into our roadmap? > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/c2cb70a9/attachment-0001.html From supittma at redhat.com Tue Apr 21 10:50:49 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 21 Apr 2015 10:50:49 -0400 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: References: Message-ID: On Tue, Apr 21, 2015 at 10:43 AM, Burr Sutter wrote: > We already have ActiveMQ, a message broker that will deal with things like > ?durable subscriptions?, holding messages until the subscriber wakes up and > acknowledges receipt. > > There is also Mosca as a Node.js-based MQTT focused message broker. > > There will be a wide spectrum of Things - from most distributed edge > sensors with energy harvesting (smart dust) to robust ?gateway? servers > that look a lot like your typical datacenter server today. It is > currently unclear to me which of the application protocols will ?win?. At > this moment, MQTT is a winner (great support from numerous vendors) and I > feel that CoAP will be a winner as well. > AMQP or DDS may win on the beefier gateways but not so much edge > intelligent things. > MQTT seems to work pretty OK on Android (last I checked). What type of messaging APIs would be useful on mobile hosts? Does an IOT webapp even make sense? (There is probably something to be said for ChromeOS apps) > > > On Apr 21, 2015, at 10:22 AM, Summers Pittman wrote: > > > > On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf > wrote: > >> more something like a unified messanger platform, where we have real >> messaging hooks/adapters (client/server) for protocols like AMQP, MQTT, >> XMPP etc while having support for push notifications as well. >> > We could probably extend the Push API. I mean it already does half the > work for us ;) > >> >> That would be nice to have, at some point >> >> On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist >> wrote: >> >>> like Notifier? >>> >>> On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman >>> wrote: >>> >>>> So IoT is getting a lot of attention within the company (or at least >>>> within my monkeysphere). From the demo project I've noticed that a lot of >>>> the work is in messaging and message handling. What do you guys think >>>> about exploring this space more? How does it / can it /should it fit into >>>> our roadmap? >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/2dc62146/attachment.html From bsutter at redhat.com Tue Apr 21 16:03:22 2015 From: bsutter at redhat.com (Burr Sutter) Date: Tue, 21 Apr 2015 16:03:22 -0400 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: References: Message-ID: <488C1C84-381B-40DC-9098-70031B8B10D3@redhat.com> > On Apr 21, 2015, at 10:50 AM, Summers Pittman wrote: > > > > On Tue, Apr 21, 2015 at 10:43 AM, Burr Sutter > wrote: > We already have ActiveMQ, a message broker that will deal with things like ?durable subscriptions?, holding messages until the subscriber wakes up and acknowledges receipt. > > There is also Mosca as a Node.js-based MQTT focused message broker. > > There will be a wide spectrum of Things - from most distributed edge sensors with energy harvesting (smart dust) to robust ?gateway? servers that look a lot like your typical datacenter server today. It is currently unclear to me which of the application protocols will ?win?. At this moment, MQTT is a winner (great support from numerous vendors) and I feel that CoAP will be a winner as well. > AMQP or DDS may win on the beefier gateways but not so much edge intelligent things. > > MQTT seems to work pretty OK on Android (last I checked). > > What type of messaging APIs would be useful on mobile hosts? I I am not sure?lots of folks here to provide some insights :-) > > Does an IOT webapp even make sense? (There is probably something to be said for ChromeOS apps) If the Thing is beefy enough to run a web browser then I consider it to be a mobile use case, less an IoT use case scenario. > > > >> On Apr 21, 2015, at 10:22 AM, Summers Pittman > wrote: >> >> >> >> On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf > wrote: >> more something like a unified messanger platform, where we have real messaging hooks/adapters (client/server) for protocols like AMQP, MQTT, XMPP etc while having support for push notifications as well. >> We could probably extend the Push API. I mean it already does half the work for us ;) >> >> That would be nice to have, at some point >> >> On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist > wrote: >> like Notifier? >> >> On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman > wrote: >> So IoT is getting a lot of attention within the company (or at least within my monkeysphere). From the demo project I've noticed that a lot of the work is in messaging and message handling. What do you guys think about exploring this space more? How does it / can it /should it fit into our roadmap? >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150421/91d5f37b/attachment-0001.html From matzew at apache.org Wed Apr 22 01:35:01 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 22 Apr 2015 07:35:01 +0200 Subject: [aerogear-dev] UPS: initial JMS support landed (on master) Message-ID: Hi, as a FYI, the master branch now contains initial JMS support. That also means we require WF/EAP running as full profile, as stated in the updated README: https://github.com/aerogear/aerogear-unifiedpush-server#getting-started For the 1.1.0.Final release there will be a few more JMS based enhancements, as we go: https://issues.jboss.org/browse/AGPUSH-1321 -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/6042fc8a/attachment.html From edewit at redhat.com Wed Apr 22 02:01:31 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 22 Apr 2015 08:01:31 +0200 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: <488C1C84-381B-40DC-9098-70031B8B10D3@redhat.com> References: <488C1C84-381B-40DC-9098-70031B8B10D3@redhat.com> Message-ID: So when I think IoT, I would think one of the challenges would be that you have a lot of things. So what would be useful would be a way to discover these devices on the network maybe? On Tue, Apr 21, 2015 at 10:03 PM, Burr Sutter wrote: > > On Apr 21, 2015, at 10:50 AM, Summers Pittman wrote: > > > > On Tue, Apr 21, 2015 at 10:43 AM, Burr Sutter wrote: >> >> We already have ActiveMQ, a message broker that will deal with things like >> ?durable subscriptions?, holding messages until the subscriber wakes up and >> acknowledges receipt. >> >> There is also Mosca as a Node.js-based MQTT focused message broker. >> >> There will be a wide spectrum of Things - from most distributed edge >> sensors with energy harvesting (smart dust) to robust ?gateway? servers >> that look a lot like your typical datacenter server today. It is currently >> unclear to me which of the application protocols will ?win?. At this >> moment, MQTT is a winner (great support from numerous vendors) and I feel >> that CoAP will be a winner as well. >> AMQP or DDS may win on the beefier gateways but not so much edge >> intelligent things. > > > MQTT seems to work pretty OK on Android (last I checked). > > What type of messaging APIs would be useful on mobile hosts? I > > > I am not sure?lots of folks here to provide some insights :-) > > > > Does an IOT webapp even make sense? (There is probably something to be said > for ChromeOS apps) > > If the Thing is beefy enough to run a web browser then I consider it to be a > mobile use case, less an IoT use case scenario. > > > >> >> >> >> On Apr 21, 2015, at 10:22 AM, Summers Pittman wrote: >> >> >> >> On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf >> wrote: >>> >>> more something like a unified messanger platform, where we have real >>> messaging hooks/adapters (client/server) for protocols like AMQP, MQTT, XMPP >>> etc while having support for push notifications as well. >> >> We could probably extend the Push API. I mean it already does half the >> work for us ;) >>> >>> >>> That would be nice to have, at some point >>> >>> On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist >>> wrote: >>>> >>>> like Notifier? >>>> >>>> On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman >>>> wrote: >>>>> >>>>> So IoT is getting a lot of attention within the company (or at least >>>>> within my monkeysphere). From the demo project I've noticed that a lot of >>>>> the work is in messaging and message handling. What do you guys think about >>>>> exploring this space more? How does it / can it /should it fit into our >>>>> roadmap? >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Cheers, Erik Jan From matzew at apache.org Wed Apr 22 04:31:15 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 22 Apr 2015 10:31:15 +0200 Subject: [aerogear-dev] UPS: initial JMS support landed (on master) In-Reply-To: References: Message-ID: Looks like some odd things are going on here, w/ Sequences and Derby.... I have no clue - anyone else? I tried other DBs (e.g. H2 or MySQL), but DBUnit is .... somewhat specific to Derby. Which is not great :-( I move the migration merge to master to beta.1. I am wondering if we really should do DBUnit w/ tests against Derby... especially since we only really support MySQL/Postgres. I think what we should to is: get rid of DBUnit and use Java to create the test data. Use Docker (once fully supported on Travis) and fire up Postgres and MySQL during the tests. -Matthias On Wed, Apr 22, 2015 at 7:35 AM, Matthias Wessendorf wrote: > Hi, > > as a FYI, the master branch now contains initial JMS support. That also > means we require WF/EAP running as full profile, as stated in the updated > README: > https://github.com/aerogear/aerogear-unifiedpush-server#getting-started > > > For the 1.1.0.Final release there will be a few more JMS based > enhancements, as we go: > https://issues.jboss.org/browse/AGPUSH-1321 > > -Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/92e27fc4/attachment.html From matzew at apache.org Wed Apr 22 04:42:11 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 22 Apr 2015 10:42:11 +0200 Subject: [aerogear-dev] UPS: initial JMS support landed (on master) In-Reply-To: References: Message-ID: or, instead of java having a .sql script for that test data creation On Wed, Apr 22, 2015 at 10:31 AM, Matthias Wessendorf wrote: > Looks like some odd things are going on here, w/ Sequences and Derby.... I > have no clue - anyone else? > > I tried other DBs (e.g. H2 or MySQL), but DBUnit is .... somewhat specific > to Derby. Which is not great :-( > > I move the migration merge to master to beta.1. I am wondering if we > really should do DBUnit w/ tests against Derby... especially since we only > really support MySQL/Postgres. > > I think what we should to is: get rid of DBUnit and use Java to create the > test data. Use Docker (once fully supported on Travis) and fire up Postgres > and MySQL during the tests. > > -Matthias > > On Wed, Apr 22, 2015 at 7:35 AM, Matthias Wessendorf > wrote: > >> Hi, >> >> as a FYI, the master branch now contains initial JMS support. That also >> means we require WF/EAP running as full profile, as stated in the updated >> README: >> https://github.com/aerogear/aerogear-unifiedpush-server#getting-started >> >> >> For the 1.1.0.Final release there will be a few more JMS based >> enhancements, as we go: >> https://issues.jboss.org/browse/AGPUSH-1321 >> >> -Matthias >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/4ff0c623/attachment.html From edewit at redhat.com Wed Apr 22 07:38:00 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 22 Apr 2015 13:38:00 +0200 Subject: [aerogear-dev] UPS: initial JMS support landed (on master) In-Reply-To: References: Message-ID: It must be something simple, can't believe it has anything to do with sequence being created wrong, because that would create duplicate keys, so the error would be different. DBUnit is not specific to Derby we can use other databases as well. Adding a whole lot of code in each test just to setup the database with data to test is in my opinion is not a nice thing to do, because it obscures the test. Let me have another crack at this, I could also try and use mysql as testdb making the tests even more valuable On Wed, Apr 22, 2015 at 10:42 AM, Matthias Wessendorf wrote: > or, instead of java having a .sql script for that test data creation > > On Wed, Apr 22, 2015 at 10:31 AM, Matthias Wessendorf > wrote: >> >> Looks like some odd things are going on here, w/ Sequences and Derby.... I >> have no clue - anyone else? >> >> I tried other DBs (e.g. H2 or MySQL), but DBUnit is .... somewhat specific >> to Derby. Which is not great :-( >> >> I move the migration merge to master to beta.1. I am wondering if we >> really should do DBUnit w/ tests against Derby... especially since we only >> really support MySQL/Postgres. >> >> I think what we should to is: get rid of DBUnit and use Java to create the >> test data. Use Docker (once fully supported on Travis) and fire up Postgres >> and MySQL during the tests. >> >> -Matthias >> >> On Wed, Apr 22, 2015 at 7:35 AM, Matthias Wessendorf >> wrote: >>> >>> Hi, >>> >>> as a FYI, the master branch now contains initial JMS support. That also >>> means we require WF/EAP running as full profile, as stated in the updated >>> README: >>> https://github.com/aerogear/aerogear-unifiedpush-server#getting-started >>> >>> >>> For the 1.1.0.Final release there will be a few more JMS based >>> enhancements, as we go: >>> https://issues.jboss.org/browse/AGPUSH-1321 >>> >>> -Matthias >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Cheers, Erik Jan From supittma at redhat.com Wed Apr 22 08:06:13 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 22 Apr 2015 08:06:13 -0400 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: References: <488C1C84-381B-40DC-9098-70031B8B10D3@redhat.com> Message-ID: On Wed, Apr 22, 2015 at 2:01 AM, Erik Jan de Wit wrote: > So when I think IoT, I would think one of the challenges would be that > you have a lot of things. So what would be useful would be a way to > discover these devices on the network maybe? > What type of network? I know with TCP/IP there are some utilities for finding things on your local subnet. There are also things wifi direct does but I am not familiar with them. What type of protocol do the iBeacon family of devices use over BLE? > On Tue, Apr 21, 2015 at 10:03 PM, Burr Sutter wrote: > > > > On Apr 21, 2015, at 10:50 AM, Summers Pittman > wrote: > > > > > > > > On Tue, Apr 21, 2015 at 10:43 AM, Burr Sutter > wrote: > >> > >> We already have ActiveMQ, a message broker that will deal with things > like > >> ?durable subscriptions?, holding messages until the subscriber wakes up > and > >> acknowledges receipt. > >> > >> There is also Mosca as a Node.js-based MQTT focused message broker. > >> > >> There will be a wide spectrum of Things - from most distributed edge > >> sensors with energy harvesting (smart dust) to robust ?gateway? servers > >> that look a lot like your typical datacenter server today. It is > currently > >> unclear to me which of the application protocols will ?win?. At this > >> moment, MQTT is a winner (great support from numerous vendors) and I > feel > >> that CoAP will be a winner as well. > >> AMQP or DDS may win on the beefier gateways but not so much edge > >> intelligent things. > > > > > > MQTT seems to work pretty OK on Android (last I checked). > > > > What type of messaging APIs would be useful on mobile hosts? I > > > > > > I am not sure?lots of folks here to provide some insights :-) > > > > > > > > Does an IOT webapp even make sense? (There is probably something to be > said > > for ChromeOS apps) > > > > If the Thing is beefy enough to run a web browser then I consider it to > be a > > mobile use case, less an IoT use case scenario. > > > > > > > >> > >> > >> > >> On Apr 21, 2015, at 10:22 AM, Summers Pittman > wrote: > >> > >> > >> > >> On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf < > matzew at apache.org> > >> wrote: > >>> > >>> more something like a unified messanger platform, where we have real > >>> messaging hooks/adapters (client/server) for protocols like AMQP, > MQTT, XMPP > >>> etc while having support for push notifications as well. > >> > >> We could probably extend the Push API. I mean it already does half the > >> work for us ;) > >>> > >>> > >>> That would be nice to have, at some point > >>> > >>> On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist > >>> wrote: > >>>> > >>>> like Notifier? > >>>> > >>>> On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman < > supittma at redhat.com> > >>>> wrote: > >>>>> > >>>>> So IoT is getting a lot of attention within the company (or at least > >>>>> within my monkeysphere). From the demo project I've noticed that a > lot of > >>>>> the work is in messaging and message handling. What do you guys > think about > >>>>> exploring this space more? How does it / can it /should it fit into > our > >>>>> roadmap? > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> aerogear-dev mailing list > >>>>> aerogear-dev at lists.jboss.org > >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> aerogear-dev mailing list > >>>> aerogear-dev at 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 > >>> > >>> _______________________________________________ > >>> aerogear-dev mailing list > >>> aerogear-dev at lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > >> > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/ec7ddb4f/attachment-0001.html From scm.blanc at gmail.com Wed Apr 22 08:37:35 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Wed, 22 Apr 2015 18:07:35 +0530 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: References: <488C1C84-381B-40DC-9098-70031B8B10D3@redhat.com> Message-ID: <44C20B07-A70C-47DD-A732-15504155BBCD@gmail.com> Envoy? de mon iPhone > Le 22 avr. 2015 ? 17:36, Summers Pittman a ?crit : > > > >> On Wed, Apr 22, 2015 at 2:01 AM, Erik Jan de Wit wrote: >> So when I think IoT, I would think one of the challenges would be that >> you have a lot of things. So what would be useful would be a way to >> discover these devices on the network maybe? > > What type of network? > > I know with TCP/IP there are some utilities for finding things on your local subnet. There are also things wifi direct does but I am not familiar with them. > > What type of protocol do the iBeacon family of devices use over BLE? I think beacons use Bluetooth and thus it's discovery facilities > >> On Tue, Apr 21, 2015 at 10:03 PM, Burr Sutter wrote: >> > >> > On Apr 21, 2015, at 10:50 AM, Summers Pittman wrote: >> > >> > >> > >> > On Tue, Apr 21, 2015 at 10:43 AM, Burr Sutter wrote: >> >> >> >> We already have ActiveMQ, a message broker that will deal with things like >> >> ?durable subscriptions?, holding messages until the subscriber wakes up and >> >> acknowledges receipt. >> >> >> >> There is also Mosca as a Node.js-based MQTT focused message broker. >> >> >> >> There will be a wide spectrum of Things - from most distributed edge >> >> sensors with energy harvesting (smart dust) to robust ?gateway? servers >> >> that look a lot like your typical datacenter server today. It is currently >> >> unclear to me which of the application protocols will ?win?. At this >> >> moment, MQTT is a winner (great support from numerous vendors) and I feel >> >> that CoAP will be a winner as well. >> >> AMQP or DDS may win on the beefier gateways but not so much edge >> >> intelligent things. >> > >> > >> > MQTT seems to work pretty OK on Android (last I checked). >> > >> > What type of messaging APIs would be useful on mobile hosts? I >> > >> > >> > I am not sure?lots of folks here to provide some insights :-) >> > >> > >> > >> > Does an IOT webapp even make sense? (There is probably something to be said >> > for ChromeOS apps) >> > >> > If the Thing is beefy enough to run a web browser then I consider it to be a >> > mobile use case, less an IoT use case scenario. >> > >> > >> > >> >> >> >> >> >> >> >> On Apr 21, 2015, at 10:22 AM, Summers Pittman wrote: >> >> >> >> >> >> >> >> On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf >> >> wrote: >> >>> >> >>> more something like a unified messanger platform, where we have real >> >>> messaging hooks/adapters (client/server) for protocols like AMQP, MQTT, XMPP >> >>> etc while having support for push notifications as well. >> >> >> >> We could probably extend the Push API. I mean it already does half the >> >> work for us ;) >> >>> >> >>> >> >>> That would be nice to have, at some point >> >>> >> >>> On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist >> >>> wrote: >> >>>> >> >>>> like Notifier? >> >>>> >> >>>> On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman >> >>>> wrote: >> >>>>> >> >>>>> So IoT is getting a lot of attention within the company (or at least >> >>>>> within my monkeysphere). From the demo project I've noticed that a lot of >> >>>>> the work is in messaging and message handling. What do you guys think about >> >>>>> exploring this space more? How does it / can it /should it fit into our >> >>>>> roadmap? >> >>>>> >> >>>>> >> >>>>> >> >>>>> _______________________________________________ >> >>>>> aerogear-dev mailing list >> >>>>> aerogear-dev at lists.jboss.org >> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >>>> >> >>>> >> >>>> >> >>>> _______________________________________________ >> >>>> aerogear-dev mailing list >> >>>> aerogear-dev at 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 >> >>> >> >>> _______________________________________________ >> >>> aerogear-dev mailing list >> >>> aerogear-dev at lists.jboss.org >> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> >> _______________________________________________ >> >> aerogear-dev mailing list >> >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> >> >> >> _______________________________________________ >> >> aerogear-dev mailing list >> >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > >> > >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/eafb3c8e/attachment.html From supittma at redhat.com Wed Apr 22 10:47:16 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 22 Apr 2015 10:47:16 -0400 Subject: [aerogear-dev] AeroGear Messaging In-Reply-To: <44C20B07-A70C-47DD-A732-15504155BBCD@gmail.com> References: <488C1C84-381B-40DC-9098-70031B8B10D3@redhat.com> <44C20B07-A70C-47DD-A732-15504155BBCD@gmail.com> Message-ID: On Wed, Apr 22, 2015 at 8:37 AM, S?bastien Blanc wrote: > > > Envoy? de mon iPhone > > Le 22 avr. 2015 ? 17:36, Summers Pittman a ?crit : > > > > On Wed, Apr 22, 2015 at 2:01 AM, Erik Jan de Wit > wrote: > >> So when I think IoT, I would think one of the challenges would be that >> you have a lot of things. So what would be useful would be a way to >> discover these devices on the network maybe? >> > > What type of network? > > I know with TCP/IP there are some utilities for finding things on your > local subnet. There are also things wifi direct does but I am not familiar > with them. > > What type of protocol do the iBeacon family of devices use over BLE? > > I think beacons use Bluetooth and thus it's discovery facilities > > I suppose that explains the B in BLE ;) > > >> On Tue, Apr 21, 2015 at 10:03 PM, Burr Sutter wrote: >> > >> > On Apr 21, 2015, at 10:50 AM, Summers Pittman >> wrote: >> > >> > >> > >> > On Tue, Apr 21, 2015 at 10:43 AM, Burr Sutter >> wrote: >> >> >> >> We already have ActiveMQ, a message broker that will deal with things >> like >> >> ?durable subscriptions?, holding messages until the subscriber wakes >> up and >> >> acknowledges receipt. >> >> >> >> There is also Mosca as a Node.js-based MQTT focused message broker. >> >> >> >> There will be a wide spectrum of Things - from most distributed edge >> >> sensors with energy harvesting (smart dust) to robust ?gateway? >> servers >> >> that look a lot like your typical datacenter server today. It is >> currently >> >> unclear to me which of the application protocols will ?win?. At this >> >> moment, MQTT is a winner (great support from numerous vendors) and I >> feel >> >> that CoAP will be a winner as well. >> >> AMQP or DDS may win on the beefier gateways but not so much edge >> >> intelligent things. >> > >> > >> > MQTT seems to work pretty OK on Android (last I checked). >> > >> > What type of messaging APIs would be useful on mobile hosts? I >> > >> > >> > I am not sure?lots of folks here to provide some insights :-) >> > >> > >> > >> > Does an IOT webapp even make sense? (There is probably something to be >> said >> > for ChromeOS apps) >> > >> > If the Thing is beefy enough to run a web browser then I consider it to >> be a >> > mobile use case, less an IoT use case scenario. >> > >> > >> > >> >> >> >> >> >> >> >> On Apr 21, 2015, at 10:22 AM, Summers Pittman >> wrote: >> >> >> >> >> >> >> >> On Tue, Apr 21, 2015 at 10:19 AM, Matthias Wessendorf < >> matzew at apache.org> >> >> wrote: >> >>> >> >>> more something like a unified messanger platform, where we have real >> >>> messaging hooks/adapters (client/server) for protocols like AMQP, >> MQTT, XMPP >> >>> etc while having support for push notifications as well. >> >> >> >> We could probably extend the Push API. I mean it already does half the >> >> work for us ;) >> >>> >> >>> >> >>> That would be nice to have, at some point >> >>> >> >>> On Tue, Apr 21, 2015 at 4:13 PM, Luke Holmquist >> >>> wrote: >> >>>> >> >>>> like Notifier? >> >>>> >> >>>> On Tue, Apr 21, 2015 at 10:02 AM, Summers Pittman < >> supittma at redhat.com> >> >>>> wrote: >> >>>>> >> >>>>> So IoT is getting a lot of attention within the company (or at least >> >>>>> within my monkeysphere). From the demo project I've noticed that a >> lot of >> >>>>> the work is in messaging and message handling. What do you guys >> think about >> >>>>> exploring this space more? How does it / can it /should it fit >> into our >> >>>>> roadmap? >> >>>>> >> >>>>> >> >>>>> >> >>>>> _______________________________________________ >> >>>>> aerogear-dev mailing list >> >>>>> aerogear-dev at lists.jboss.org >> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >>>> >> >>>> >> >>>> >> >>>> _______________________________________________ >> >>>> aerogear-dev mailing list >> >>>> aerogear-dev at 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 >> >>> >> >>> _______________________________________________ >> >>> aerogear-dev mailing list >> >>> aerogear-dev at lists.jboss.org >> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> >> _______________________________________________ >> >> aerogear-dev mailing list >> >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> >> >> >> _______________________________________________ >> >> aerogear-dev mailing list >> >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > >> > >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/fdcfa748/attachment-0001.html From matzew at apache.org Wed Apr 22 12:20:10 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 22 Apr 2015 18:20:10 +0200 Subject: [aerogear-dev] UPS: initial JMS support landed (on master) In-Reply-To: References: Message-ID: Thanks Erik, I saw your PR against my branch - will give it a shot 2nite -M On Wed, Apr 22, 2015 at 1:38 PM, Erik Jan de Wit wrote: > It must be something simple, can't believe it has anything to do with > sequence being created wrong, because that would create duplicate > keys, so the error would be different. DBUnit is not specific to Derby > we can use other databases as well. > > Adding a whole lot of code in each test just to setup the database > with data to test is in my opinion is not a nice thing to do, because > it obscures the test. > > Let me have another crack at this, I could also try and use mysql as > testdb making the tests even more valuable > > On Wed, Apr 22, 2015 at 10:42 AM, Matthias Wessendorf > wrote: > > or, instead of java having a .sql script for that test data creation > > > > On Wed, Apr 22, 2015 at 10:31 AM, Matthias Wessendorf > > > wrote: > >> > >> Looks like some odd things are going on here, w/ Sequences and > Derby.... I > >> have no clue - anyone else? > >> > >> I tried other DBs (e.g. H2 or MySQL), but DBUnit is .... somewhat > specific > >> to Derby. Which is not great :-( > >> > >> I move the migration merge to master to beta.1. I am wondering if we > >> really should do DBUnit w/ tests against Derby... especially since we > only > >> really support MySQL/Postgres. > >> > >> I think what we should to is: get rid of DBUnit and use Java to create > the > >> test data. Use Docker (once fully supported on Travis) and fire up > Postgres > >> and MySQL during the tests. > >> > >> -Matthias > >> > >> On Wed, Apr 22, 2015 at 7:35 AM, Matthias Wessendorf > > >> wrote: > >>> > >>> Hi, > >>> > >>> as a FYI, the master branch now contains initial JMS support. That also > >>> means we require WF/EAP running as full profile, as stated in the > updated > >>> README: > >>> > https://github.com/aerogear/aerogear-unifiedpush-server#getting-started > >>> > >>> > >>> For the 1.1.0.Final release there will be a few more JMS based > >>> enhancements, as we go: > >>> https://issues.jboss.org/browse/AGPUSH-1321 > >>> > >>> -Matthias > >>> > >>> -- > >>> Matthias Wessendorf > >>> > >>> blog: http://matthiaswessendorf.wordpress.com/ > >>> sessions: http://www.slideshare.net/mwessendorf > >>> twitter: http://twitter.com/mwessendorf > >> > >> > >> > >> > >> -- > >> Matthias Wessendorf > >> > >> blog: http://matthiaswessendorf.wordpress.com/ > >> sessions: http://www.slideshare.net/mwessendorf > >> twitter: http://twitter.com/mwessendorf > > > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/519e0ea7/attachment.html From banddk1 at gmail.com Wed Apr 22 16:17:39 2015 From: banddk1 at gmail.com (=?UTF-8?B?0JTQtdC90LjRgSDQmtCw0YDQv9C10L3QutC+?=) Date: Wed, 22 Apr 2015 23:17:39 +0300 Subject: [aerogear-dev] AeroDoc In-Reply-To: References: Message-ID: Hi everyone! I've made some changes in AeroDoc first page design. I'd like to hear your opinion about it. Denis. 2015-04-16 15:45 GMT+03:00 Matthias Wessendorf : > > > On Thu, Apr 16, 2015 at 2:37 PM, ????? ???????? wrote: > >> Hi Everyone ! >> I am going to start porting Aerodoc to Swift. So I'd like to know, what >> we will do with modifying the use-case - to not be "doctor" specific ? >> I see two options: >> 1) We continue to make the application for doctors. I will slightly >> change UI and port to swift. >> > > +1 > that makes sense for first run > > >> >> 2) We will make global changes. To do this, we need to come up with the >> theme of a new application, and sketch main features of it. >> >> P.S I think the app for doctors is ok, and with a new design, it can find >> a second life. >> >> >> Denis. >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/3110d12a/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: AeroDocFirstPage.jpg Type: image/jpeg Size: 21454 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/3110d12a/attachment-0001.jpg From lukas.fryc at gmail.com Wed Apr 22 16:50:18 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 22 Apr 2015 20:50:18 +0000 Subject: [aerogear-dev] UPS: UX Revamp for Alpha2 Message-ID: Hey guys, I've put together an initial version of UPS UX Revamp branch that can be merged to master and released as part of 1.1.0-alpha-2. https://github.com/aerogear/aerogear-unifiedpush-server/pull/537 Feel free to test it! Cheers, ~ Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150422/e07f942f/attachment.html From ivan.gurtler at ahead-itec.com Thu Apr 23 02:39:47 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Thu, 23 Apr 2015 08:39:47 +0200 Subject: [aerogear-dev] Unified Push - status Message-ID: Hi, I have some questions about server status. Is possible to check with some kind of ping (or something else) that DB is available from push server? How to check if platform push server (APNS...) is also available? Thanks *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150423/d5b2d561/attachment.html From edewit at redhat.com Thu Apr 23 02:55:53 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 23 Apr 2015 08:55:53 +0200 Subject: [aerogear-dev] Unified Push - status In-Reply-To: References: Message-ID: Hi Ivan, We have functionality for this available in the master branch on github. Go to /ag-push/rest/sys/info/health it will return json with the push network status and db status. This PR https://github.com/aerogear/aerogear-unifiedpush-server/pull/519 includes details about the returned json. Hope this helps... --- Cheers, Erik Jan On Thu, Apr 23, 2015 at 8:39 AM, Ivan G?rtler wrote: > Hi, > I have some questions about server status. > Is possible to check with some kind of ping (or something else) that DB is > available from push server? > How to check if platform push server (APNS...) is also available? > > > Thanks > > Mgr. Ivan G?rtler > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile security solutions > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Cheers, Erik Jan From agalante at redhat.com Thu Apr 23 08:28:06 2015 From: agalante at redhat.com (Andres Galante) Date: Thu, 23 Apr 2015 09:28:06 -0300 Subject: [aerogear-dev] AeroDoc In-Reply-To: References: Message-ID: Hi Denis, Great job! There is a very good reference website for mobile design patterns: http://pttrns.com You can for example search for login screens http://pttrns.com/?scid=17 Just a few tips that will make your design better: 1- label the input fields, with labels or placeholders, name them "email" or "username" and "password". 2- Make the input fields wider 3- Make the Login btn a button, with a coloured background and the same size as the inputs 4- Good Designers Copy, Great Designers Steal. Don't be ashamed, choose a reference you like and copy it. Its the best way to start learning design. About the logo, you could, if you want, work more on the proportions, if you want references, this is a good one: http://logopond.com If you want icon inspiration go here http://iosicongallery.com/ And if you just want more, check https://dribbble.com Good luck! On Wed, Apr 22, 2015 at 5:17 PM, ????? ???????? wrote: > Hi everyone! > I've made some changes in AeroDoc first page design. > I'd like to hear your opinion about it. > > Denis. > > > 2015-04-16 15:45 GMT+03:00 Matthias Wessendorf : > >> >> >> On Thu, Apr 16, 2015 at 2:37 PM, ????? ???????? >> wrote: >> >>> Hi Everyone ! >>> I am going to start porting Aerodoc to Swift. So I'd like to know, what >>> we will do with modifying the use-case - to not be "doctor" specific ? >>> I see two options: >>> 1) We continue to make the application for doctors. I will slightly >>> change UI and port to swift. >>> >> >> +1 >> that makes sense for first run >> >> >>> >>> 2) We will make global changes. To do this, we need to come up with the >>> theme of a new application, and sketch main features of it. >>> >>> P.S I think the app for doctors is ok, and with a new design, it can >>> find a second life. >>> >>> >>> Denis. >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150423/d41646b5/attachment.html From banddk1 at gmail.com Thu Apr 23 08:57:12 2015 From: banddk1 at gmail.com (=?UTF-8?B?0JTQtdC90LjRgSDQmtCw0YDQv9C10L3QutC+?=) Date: Thu, 23 Apr 2015 15:57:12 +0300 Subject: [aerogear-dev] AeroDoc In-Reply-To: References: Message-ID: Thank you Andres! I will definitely use your tips ! I've already labelled the input fields :) When I finish work on design, I'll send you full application design for review, ok? Denis. 2015-04-23 15:28 GMT+03:00 Andres Galante : > Hi Denis, > > Great job! There is a very good reference website for mobile design > patterns: http://pttrns.com > > You can for example search for login screens http://pttrns.com/?scid=17 > > Just a few tips that will make your design better: > > 1- label the input fields, with labels or placeholders, name them "email" > or "username" and "password". > 2- Make the input fields wider > 3- Make the Login btn a button, with a coloured background and the same > size as the inputs > 4- Good Designers Copy, Great Designers Steal. Don't be ashamed, choose a > reference you like and copy it. Its the best way to start learning design. > > About the logo, you could, if you want, work more on the proportions, if > you want references, this is a good one: http://logopond.com > > If you want icon inspiration go here http://iosicongallery.com/ > > And if you just want more, check https://dribbble.com > > Good luck! > > > > > On Wed, Apr 22, 2015 at 5:17 PM, ????? ???????? wrote: > >> Hi everyone! >> I've made some changes in AeroDoc first page design. >> I'd like to hear your opinion about it. >> >> Denis. >> >> >> 2015-04-16 15:45 GMT+03:00 Matthias Wessendorf : >> >>> >>> >>> On Thu, Apr 16, 2015 at 2:37 PM, ????? ???????? >>> wrote: >>> >>>> Hi Everyone ! >>>> I am going to start porting Aerodoc to Swift. So I'd like to know, what >>>> we will do with modifying the use-case - to not be "doctor" specific ? >>>> I see two options: >>>> 1) We continue to make the application for doctors. I will slightly >>>> change UI and port to swift. >>>> >>> >>> +1 >>> that makes sense for first run >>> >>> >>>> >>>> 2) We will make global changes. To do this, we need to come up with the >>>> theme of a new application, and sketch main features of it. >>>> >>>> P.S I think the app for doctors is ok, and with a new design, it can >>>> find a second life. >>>> >>>> >>>> Denis. >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150423/dfe4bb91/attachment-0001.html From ivan.gurtler at ahead-itec.com Thu Apr 23 08:58:31 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Thu, 23 Apr 2015 14:58:31 +0200 Subject: [aerogear-dev] Unified Push - status In-Reply-To: References: Message-ID: Hi, We have own fork ... and I sync with "aerogear:master". Master branch in fork is OK. I merge master to second branch. We changed model/jpa/src/main/resources/META-INF/orm.xml file in second branch because we use ORACLE *...* * * * ios* * * * * * * * * * * * * * * *...* *(*Second change in orm.xml file was because of Installation class, it was bigger than 4000 -> problem in ORACLE ... but in "aerogear:master" it was removed from orm.xml file*)* but when ... Run as ... Maven insall ... In console: *...* *Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.366 sec* *Results :* *Failed tests: * * Expected exception: javax.persistence.PersistenceException* *Tests in error: * * PushApplicationDaoTest.updatePushApplication:125 ? Persistence org.hibernate.e...* * PushApplicationDaoTest.pushApplicationIDUnmodifiedAfterUpdate:159 ? Persistence* * PushApplicationDaoTest.deletePushApplicationIncludingVariantAndInstallations:194 ? Persistence* * PushApplicationDaoTest.findByPushApplicationID:116 ? Persistence org.hibernate...* * PushApplicationDaoTest.findAllForDeveloper:72 ? Persistence org.hibernate.exce...* * PushApplicationDaoTest.primaryKeyUnmodifiedAfterUpdate:174 ? Persistence org.h...* * PushApplicationDaoTest.findAllIDsForDeveloper:96 ? Persistence org.hibernate.e...* * PushApplicationDaoTest.findByPushApplicationIDForDeveloper:103 ? Persistence o...* * PushApplicationDaoTest.updateAndDeletePushApplication:140 ? Persistence org.hi...* *Tests run: 75, Failures: 1, Errors: 9, Skipped: 0* *[INFO] ------------------------------------------------------------------------* *[INFO] Reactor Summary:* *[INFO] * *[INFO] AeroGear UnifiedPush Server ....................... SUCCESS [ 2.833 s]* *[INFO] UnifiedPush Model Layer ........................... SUCCESS [ 0.058 s]* *[INFO] UnifiedPush Server Model API ...................... SUCCESS [ 2.886 s]* *[INFO] UnifiedPush Server Model JPA implementation ....... FAILURE [ 32.992 s]* *[INFO] UnifiedPush Service Layer ......................... SKIPPED* *[INFO] UnifiedPush Sender Module ......................... SKIPPED* *[INFO] UnifiedPush Push Message Model .................... SKIPPED* *[INFO] UnifiedPush Push Notification Networks ............ SKIPPED* *[INFO] UnifiedPush RESTful Endpoint ...................... SKIPPED* *[INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED* *[INFO] UnifiedPush Dependencies Parent ................... SKIPPED* *[INFO] UnifiedPush Server Dependencies Server ............ SKIPPED* *[INFO] UnifiedPush Auth Server ........................... SKIPPED* *[INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED* *[INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED* *[INFO] UnifiedPush Servers Parent ........................ SKIPPED* *[INFO] ------------------------------------------------------------------------* *[INFO] BUILD FAILURE* *[INFO] ------------------------------------------------------------------------* *[INFO] Total time: 40.717 s* *[INFO] Finished at: 2015-04-23T14:35:45+01:00* *[INFO] Final Memory: 21M/420M* *[INFO] ------------------------------------------------------------------------* *[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test (default-test) on project unifiedpush-model-jpa: There are test failures.* *[ERROR] * *[ERROR] Please refer to C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports for the individual test results.* *[ERROR] -> [Help 1]* *[ERROR] * *[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.* *[ERROR] Re-run Maven using the -X switch to enable full debug logging.* *[ERROR] * *[ERROR] For more information about the errors and possible solutions, please read the following articles:* *[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException * *[ERROR] * *[ERROR] After correcting the problems, you can resume the build with the command* *[ERROR] mvn -rf :unifiedpush-model-jpa* --------------------------------------------------------------------------------------------------------------------------------------------------------------- Do you have any idea where is the problem and how to solve it? Thanks *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-04-23 8:55 GMT+02:00 Erik Jan de Wit : > Hi Ivan, > > We have functionality for this available in the master branch on > github. Go to /ag-push/rest/sys/info/health it will return > json with the push network status and db status. This PR > https://github.com/aerogear/aerogear-unifiedpush-server/pull/519 > includes details about the returned json. > > Hope this helps... > > --- > Cheers, > Erik Jan > > On Thu, Apr 23, 2015 at 8:39 AM, Ivan G?rtler > wrote: > > Hi, > > I have some questions about server status. > > Is possible to check with some kind of ping (or something else) that DB > is > > available from push server? > > How to check if platform push server (APNS...) is also available? > > > > > > Thanks > > > > Mgr. Ivan G?rtler > > Mobile software developer > > > > AHEAD iTec, s.r.o., Botanick? 554/68a, > > 602 00 Brno (Czech Republic) > > > > www.ahead-itec.com | twitter | mobile security solutions > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150423/041880b9/attachment.html From edewit at redhat.com Thu Apr 23 09:05:32 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 23 Apr 2015 15:05:32 +0200 Subject: [aerogear-dev] Unified Push - status In-Reply-To: References: Message-ID: Hi Ivan, Try running without the test `mvn install -DskipTests`, because they are testing against another schema. Or see why the tests fail in the C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports directory and fix those tests, by changing model\jpa\test\create_db_content.ddl On Thu, Apr 23, 2015 at 2:58 PM, Ivan G?rtler wrote: > Hi, > We have own fork ... and I sync with "aerogear:master". Master branch in > fork is OK. > I merge master to second branch. We changed > model/jpa/src/main/resources/META-INF/orm.xml file in second branch because > we use ORACLE > ... > > ios > > > > > > > > ... > (Second change in orm.xml file was because of Installation class, it was > bigger than 4000 -> problem in ORACLE ... but in "aerogear:master" it was > removed from orm.xml file) > but when ... Run as ... Maven insall ... In console: > ... > Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.366 sec > Results : > Failed tests: > Expected exception: javax.persistence.PersistenceException > Tests in error: > PushApplicationDaoTest.updatePushApplication:125 ? Persistence > org.hibernate.e... > PushApplicationDaoTest.pushApplicationIDUnmodifiedAfterUpdate:159 ? > Persistence > > PushApplicationDaoTest.deletePushApplicationIncludingVariantAndInstallations:194 > ? Persistence > PushApplicationDaoTest.findByPushApplicationID:116 ? Persistence > org.hibernate... > PushApplicationDaoTest.findAllForDeveloper:72 ? Persistence > org.hibernate.exce... > PushApplicationDaoTest.primaryKeyUnmodifiedAfterUpdate:174 ? Persistence > org.h... > PushApplicationDaoTest.findAllIDsForDeveloper:96 ? Persistence > org.hibernate.e... > PushApplicationDaoTest.findByPushApplicationIDForDeveloper:103 ? > Persistence o... > PushApplicationDaoTest.updateAndDeletePushApplication:140 ? Persistence > org.hi... > Tests run: 75, Failures: 1, Errors: 9, Skipped: 0 > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] AeroGear UnifiedPush Server ....................... SUCCESS [ 2.833 > s] > [INFO] UnifiedPush Model Layer ........................... SUCCESS [ 0.058 > s] > [INFO] UnifiedPush Server Model API ...................... SUCCESS [ 2.886 > s] > [INFO] UnifiedPush Server Model JPA implementation ....... FAILURE [ 32.992 > s] > [INFO] UnifiedPush Service Layer ......................... SKIPPED > [INFO] UnifiedPush Sender Module ......................... SKIPPED > [INFO] UnifiedPush Push Message Model .................... SKIPPED > [INFO] UnifiedPush Push Notification Networks ............ SKIPPED > [INFO] UnifiedPush RESTful Endpoint ...................... SKIPPED > [INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED > [INFO] UnifiedPush Dependencies Parent ................... SKIPPED > [INFO] UnifiedPush Server Dependencies Server ............ SKIPPED > [INFO] UnifiedPush Auth Server ........................... SKIPPED > [INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED > [INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED > [INFO] UnifiedPush Servers Parent ........................ SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 40.717 s > [INFO] Finished at: 2015-04-23T14:35:45+01:00 > [INFO] Final Memory: 21M/420M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test (default-test) on > project unifiedpush-model-jpa: There are test failures. > [ERROR] > [ERROR] Please refer to > C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports > for the individual test results. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :unifiedpush-model-jpa > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > Do you have any idea where is the problem and how to solve it? > Thanks > > Mgr. Ivan G?rtler > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile security solutions > > 2015-04-23 8:55 GMT+02:00 Erik Jan de Wit : >> >> Hi Ivan, >> >> We have functionality for this available in the master branch on >> github. Go to /ag-push/rest/sys/info/health it will return >> json with the push network status and db status. This PR >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/519 >> includes details about the returned json. >> >> Hope this helps... >> >> --- >> Cheers, >> Erik Jan >> >> On Thu, Apr 23, 2015 at 8:39 AM, Ivan G?rtler >> wrote: >> > Hi, >> > I have some questions about server status. >> > Is possible to check with some kind of ping (or something else) that DB >> > is >> > available from push server? >> > How to check if platform push server (APNS...) is also available? >> > >> > >> > Thanks >> > >> > Mgr. Ivan G?rtler >> > Mobile software developer >> > >> > AHEAD iTec, s.r.o., Botanick? 554/68a, >> > 602 00 Brno (Czech Republic) >> > >> > www.ahead-itec.com | twitter | mobile security solutions >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Cheers, Erik Jan From ivan.gurtler at ahead-itec.com Thu Apr 23 09:30:07 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Thu, 23 Apr 2015 15:30:07 +0200 Subject: [aerogear-dev] Unified Push - status In-Reply-To: References: Message-ID: In report file for PushApplicationDaoTest ... i found: ... javax.persistence.PersistenceException: org.hibernate.exception.DataException: could not initialize a collection: [org.jboss.aerogear.unifiedpush.api.PushApplication.variants#1] at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.ConnectionChild.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedResultSet.dataTypeConversion(Unknown Source) at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) at org.hibernate.type.descriptor.sql.ClobTypeDescriptor$1.doExtract(ClobTypeDescriptor.java:60) at org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:64) at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:265) at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:261) at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:251) at org.hibernate.type.AbstractStandardBasicType.hydrate(AbstractStandardBasicType.java:336) at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2924) at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1695) at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1627) at org.hibernate.loader.Loader.getRow(Loader.java:1509) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:719) at org.hibernate.loader.Loader.processResultSet(Loader.java:949) at org.hibernate.loader.Loader.doQuery(Loader.java:917) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:348) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:318) at org.hibernate.loader.Loader.loadCollection(Loader.java:2262) at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:65) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:674) at org.hibernate.event.internal.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:86) at org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1774) at org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:696) at org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:1037) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:353) at org.hibernate.loader.Loader.doList(Loader.java:2550) at org.hibernate.loader.Loader.doList(Loader.java:2536) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2366) at org.hibernate.loader.Loader.list(Loader.java:2361) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:495) at org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:357) at org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:198) at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1194) at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:264) at org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPABaseDao.getSingleResultForQuery(JPABaseDao.java:93) at org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPAPushApplicationDao.findByPushApplicationID(JPAPushApplicationDao.java:73) at org.jboss.aerogear.unifiedpush.jpa.PushApplicationDaoTest.updatePushApplication(PushApplicationDaoTest.java:125) ... In aerogear:master version two mounth ago it was without problems. I found commit "Use JMS message queues for sending notifications in batches AGPUSH-1348" ... in this commit was changed orm.xml file ... but I dont know background of commit change. *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-04-23 15:05 GMT+02:00 Erik Jan de Wit : > Hi Ivan, > > Try running without the test `mvn install -DskipTests`, because they > are testing against another schema. Or see why the tests fail in the > > C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports > directory and fix those tests, by changing > model\jpa\test\create_db_content.ddl > > On Thu, Apr 23, 2015 at 2:58 PM, Ivan G?rtler > wrote: > > Hi, > > We have own fork ... and I sync with "aerogear:master". Master branch in > > fork is OK. > > I merge master to second branch. We changed > > model/jpa/src/main/resources/META-INF/orm.xml file in second branch > because > > we use ORACLE > > ... > > > > ios > > > > > > > > > > > > > > > > ... > > (Second change in orm.xml file was because of Installation class, it was > > bigger than 4000 -> problem in ORACLE ... but in "aerogear:master" it was > > removed from orm.xml file) > > but when ... Run as ... Maven insall ... In console: > > ... > > Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.366 > sec > > Results : > > Failed tests: > > Expected exception: javax.persistence.PersistenceException > > Tests in error: > > PushApplicationDaoTest.updatePushApplication:125 ? Persistence > > org.hibernate.e... > > PushApplicationDaoTest.pushApplicationIDUnmodifiedAfterUpdate:159 ? > > Persistence > > > > > PushApplicationDaoTest.deletePushApplicationIncludingVariantAndInstallations:194 > > ? Persistence > > PushApplicationDaoTest.findByPushApplicationID:116 ? Persistence > > org.hibernate... > > PushApplicationDaoTest.findAllForDeveloper:72 ? Persistence > > org.hibernate.exce... > > PushApplicationDaoTest.primaryKeyUnmodifiedAfterUpdate:174 ? > Persistence > > org.h... > > PushApplicationDaoTest.findAllIDsForDeveloper:96 ? Persistence > > org.hibernate.e... > > PushApplicationDaoTest.findByPushApplicationIDForDeveloper:103 ? > > Persistence o... > > PushApplicationDaoTest.updateAndDeletePushApplication:140 ? Persistence > > org.hi... > > Tests run: 75, Failures: 1, Errors: 9, Skipped: 0 > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Reactor Summary: > > [INFO] > > [INFO] AeroGear UnifiedPush Server ....................... SUCCESS [ > 2.833 > > s] > > [INFO] UnifiedPush Model Layer ........................... SUCCESS [ > 0.058 > > s] > > [INFO] UnifiedPush Server Model API ...................... SUCCESS [ > 2.886 > > s] > > [INFO] UnifiedPush Server Model JPA implementation ....... FAILURE [ > 32.992 > > s] > > [INFO] UnifiedPush Service Layer ......................... SKIPPED > > [INFO] UnifiedPush Sender Module ......................... SKIPPED > > [INFO] UnifiedPush Push Message Model .................... SKIPPED > > [INFO] UnifiedPush Push Notification Networks ............ SKIPPED > > [INFO] UnifiedPush RESTful Endpoint ...................... SKIPPED > > [INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED > > [INFO] UnifiedPush Dependencies Parent ................... SKIPPED > > [INFO] UnifiedPush Server Dependencies Server ............ SKIPPED > > [INFO] UnifiedPush Auth Server ........................... SKIPPED > > [INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED > > [INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED > > [INFO] UnifiedPush Servers Parent ........................ SKIPPED > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] BUILD FAILURE > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Total time: 40.717 s > > [INFO] Finished at: 2015-04-23T14:35:45+01:00 > > [INFO] Final Memory: 21M/420M > > [INFO] > > ------------------------------------------------------------------------ > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test > (default-test) on > > project unifiedpush-model-jpa: There are test failures. > > [ERROR] > > [ERROR] Please refer to > > > C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports > > for the individual test results. > > [ERROR] -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e > > switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > please > > read the following articles: > > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > > [ERROR] > > [ERROR] After correcting the problems, you can resume the build with the > > command > > [ERROR] mvn -rf :unifiedpush-model-jpa > > > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Do you have any idea where is the problem and how to solve it? > > Thanks > > > > Mgr. Ivan G?rtler > > Mobile software developer > > > > AHEAD iTec, s.r.o., Botanick? 554/68a, > > 602 00 Brno (Czech Republic) > > > > www.ahead-itec.com | twitter | mobile security solutions > > > > 2015-04-23 8:55 GMT+02:00 Erik Jan de Wit : > >> > >> Hi Ivan, > >> > >> We have functionality for this available in the master branch on > >> github. Go to /ag-push/rest/sys/info/health it will return > >> json with the push network status and db status. This PR > >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/519 > >> includes details about the returned json. > >> > >> Hope this helps... > >> > >> --- > >> Cheers, > >> Erik Jan > >> > >> On Thu, Apr 23, 2015 at 8:39 AM, Ivan G?rtler > >> wrote: > >> > Hi, > >> > I have some questions about server status. > >> > Is possible to check with some kind of ping (or something else) that > DB > >> > is > >> > available from push server? > >> > How to check if platform push server (APNS...) is also available? > >> > > >> > > >> > Thanks > >> > > >> > Mgr. Ivan G?rtler > >> > Mobile software developer > >> > > >> > AHEAD iTec, s.r.o., Botanick? 554/68a, > >> > 602 00 Brno (Czech Republic) > >> > > >> > www.ahead-itec.com | twitter | mobile security solutions > >> > > >> > _______________________________________________ > >> > aerogear-dev mailing list > >> > aerogear-dev at lists.jboss.org > >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > >> > >> > >> -- > >> Cheers, > >> Erik Jan > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150423/8bf63b11/attachment-0001.html From edewit at redhat.com Thu Apr 23 09:34:23 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 23 Apr 2015 15:34:23 +0200 Subject: [aerogear-dev] Unified Push - status In-Reply-To: References: Message-ID: I'm not sure what it is you changed why not build without running the tests? On Thu, Apr 23, 2015 at 3:30 PM, Ivan G?rtler wrote: > In report file for PushApplicationDaoTest ... i found: > > ... > javax.persistence.PersistenceException: > org.hibernate.exception.DataException: could not initialize a collection: > [org.jboss.aerogear.unifiedpush.api.PushApplication.variants#1] > at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown > Source) > at > org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown > Source) > at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown > Source) > at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) > at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) > at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown > Source) > at org.apache.derby.impl.jdbc.ConnectionChild.newSQLException(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedResultSet.dataTypeConversion(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) > at > org.hibernate.type.descriptor.sql.ClobTypeDescriptor$1.doExtract(ClobTypeDescriptor.java:60) > at > org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:64) > at > org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:265) > at > org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:261) > at > org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:251) > at > org.hibernate.type.AbstractStandardBasicType.hydrate(AbstractStandardBasicType.java:336) > at > org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2924) > at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1695) > at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1627) > at org.hibernate.loader.Loader.getRow(Loader.java:1509) > at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:719) > at org.hibernate.loader.Loader.processResultSet(Loader.java:949) > at org.hibernate.loader.Loader.doQuery(Loader.java:917) > at > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:348) > at > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:318) > at org.hibernate.loader.Loader.loadCollection(Loader.java:2262) > at > org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:65) > at > org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:674) > at > org.hibernate.event.internal.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:86) > at > org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1774) > at > org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:696) > at > org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:1037) > at > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:353) > at org.hibernate.loader.Loader.doList(Loader.java:2550) > at org.hibernate.loader.Loader.doList(Loader.java:2536) > at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2366) > at org.hibernate.loader.Loader.list(Loader.java:2361) > at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:495) > at > org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:357) > at > org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:198) > at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1194) > at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101) > at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:264) > at > org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPABaseDao.getSingleResultForQuery(JPABaseDao.java:93) > at > org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPAPushApplicationDao.findByPushApplicationID(JPAPushApplicationDao.java:73) > at > org.jboss.aerogear.unifiedpush.jpa.PushApplicationDaoTest.updatePushApplication(PushApplicationDaoTest.java:125) > ... > > > In aerogear:master version two mounth ago it was without problems. I found > commit "Use JMS message queues for sending notifications in batches > AGPUSH-1348" ... in this commit was changed orm.xml file ... but I dont know > background of commit change. > > Mgr. Ivan G?rtler > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile security solutions > > 2015-04-23 15:05 GMT+02:00 Erik Jan de Wit : >> >> Hi Ivan, >> >> Try running without the test `mvn install -DskipTests`, because they >> are testing against another schema. Or see why the tests fail in the >> >> C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports >> directory and fix those tests, by changing >> model\jpa\test\create_db_content.ddl >> >> On Thu, Apr 23, 2015 at 2:58 PM, Ivan G?rtler >> wrote: >> > Hi, >> > We have own fork ... and I sync with "aerogear:master". Master branch in >> > fork is OK. >> > I merge master to second branch. We changed >> > model/jpa/src/main/resources/META-INF/orm.xml file in second branch >> > because >> > we use ORACLE >> > ... >> > >> > ios >> > >> > >> > >> > >> > >> > >> > >> > ... >> > (Second change in orm.xml file was because of Installation class, it was >> > bigger than 4000 -> problem in ORACLE ... but in "aerogear:master" it >> > was >> > removed from orm.xml file) >> > but when ... Run as ... Maven insall ... In console: >> > ... >> > Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.366 >> > sec >> > Results : >> > Failed tests: >> > Expected exception: javax.persistence.PersistenceException >> > Tests in error: >> > PushApplicationDaoTest.updatePushApplication:125 ? Persistence >> > org.hibernate.e... >> > PushApplicationDaoTest.pushApplicationIDUnmodifiedAfterUpdate:159 ? >> > Persistence >> > >> > >> > PushApplicationDaoTest.deletePushApplicationIncludingVariantAndInstallations:194 >> > ? Persistence >> > PushApplicationDaoTest.findByPushApplicationID:116 ? Persistence >> > org.hibernate... >> > PushApplicationDaoTest.findAllForDeveloper:72 ? Persistence >> > org.hibernate.exce... >> > PushApplicationDaoTest.primaryKeyUnmodifiedAfterUpdate:174 ? >> > Persistence >> > org.h... >> > PushApplicationDaoTest.findAllIDsForDeveloper:96 ? Persistence >> > org.hibernate.e... >> > PushApplicationDaoTest.findByPushApplicationIDForDeveloper:103 ? >> > Persistence o... >> > PushApplicationDaoTest.updateAndDeletePushApplication:140 ? >> > Persistence >> > org.hi... >> > Tests run: 75, Failures: 1, Errors: 9, Skipped: 0 >> > [INFO] >> > ------------------------------------------------------------------------ >> > [INFO] Reactor Summary: >> > [INFO] >> > [INFO] AeroGear UnifiedPush Server ....................... SUCCESS [ >> > 2.833 >> > s] >> > [INFO] UnifiedPush Model Layer ........................... SUCCESS [ >> > 0.058 >> > s] >> > [INFO] UnifiedPush Server Model API ...................... SUCCESS [ >> > 2.886 >> > s] >> > [INFO] UnifiedPush Server Model JPA implementation ....... FAILURE [ >> > 32.992 >> > s] >> > [INFO] UnifiedPush Service Layer ......................... SKIPPED >> > [INFO] UnifiedPush Sender Module ......................... SKIPPED >> > [INFO] UnifiedPush Push Message Model .................... SKIPPED >> > [INFO] UnifiedPush Push Notification Networks ............ SKIPPED >> > [INFO] UnifiedPush RESTful Endpoint ...................... SKIPPED >> > [INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED >> > [INFO] UnifiedPush Dependencies Parent ................... SKIPPED >> > [INFO] UnifiedPush Server Dependencies Server ............ SKIPPED >> > [INFO] UnifiedPush Auth Server ........................... SKIPPED >> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED >> > [INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED >> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED >> > [INFO] >> > ------------------------------------------------------------------------ >> > [INFO] BUILD FAILURE >> > [INFO] >> > ------------------------------------------------------------------------ >> > [INFO] Total time: 40.717 s >> > [INFO] Finished at: 2015-04-23T14:35:45+01:00 >> > [INFO] Final Memory: 21M/420M >> > [INFO] >> > ------------------------------------------------------------------------ >> > [ERROR] Failed to execute goal >> > org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test >> > (default-test) on >> > project unifiedpush-model-jpa: There are test failures. >> > [ERROR] >> > [ERROR] Please refer to >> > >> > C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports >> > for the individual test results. >> > [ERROR] -> [Help 1] >> > [ERROR] >> > [ERROR] To see the full stack trace of the errors, re-run Maven with the >> > -e >> > switch. >> > [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> > [ERROR] >> > [ERROR] For more information about the errors and possible solutions, >> > please >> > read the following articles: >> > [ERROR] [Help 1] >> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >> > [ERROR] >> > [ERROR] After correcting the problems, you can resume the build with the >> > command >> > [ERROR] mvn -rf :unifiedpush-model-jpa >> > >> > --------------------------------------------------------------------------------------------------------------------------------------------------------------- >> > Do you have any idea where is the problem and how to solve it? >> > Thanks >> > >> > Mgr. Ivan G?rtler >> > Mobile software developer >> > >> > AHEAD iTec, s.r.o., Botanick? 554/68a, >> > 602 00 Brno (Czech Republic) >> > >> > www.ahead-itec.com | twitter | mobile security solutions >> > >> > 2015-04-23 8:55 GMT+02:00 Erik Jan de Wit : >> >> >> >> Hi Ivan, >> >> >> >> We have functionality for this available in the master branch on >> >> github. Go to /ag-push/rest/sys/info/health it will return >> >> json with the push network status and db status. This PR >> >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/519 >> >> includes details about the returned json. >> >> >> >> Hope this helps... >> >> >> >> --- >> >> Cheers, >> >> Erik Jan >> >> >> >> On Thu, Apr 23, 2015 at 8:39 AM, Ivan G?rtler >> >> wrote: >> >> > Hi, >> >> > I have some questions about server status. >> >> > Is possible to check with some kind of ping (or something else) that >> >> > DB >> >> > is >> >> > available from push server? >> >> > How to check if platform push server (APNS...) is also available? >> >> > >> >> > >> >> > Thanks >> >> > >> >> > Mgr. Ivan G?rtler >> >> > Mobile software developer >> >> > >> >> > AHEAD iTec, s.r.o., Botanick? 554/68a, >> >> > 602 00 Brno (Czech Republic) >> >> > >> >> > www.ahead-itec.com | twitter | mobile security solutions >> >> > >> >> > _______________________________________________ >> >> > aerogear-dev mailing list >> >> > aerogear-dev at lists.jboss.org >> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> >> >> >> -- >> >> Cheers, >> >> Erik Jan >> >> >> >> _______________________________________________ >> >> aerogear-dev mailing list >> >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > >> > >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Cheers, Erik Jan From ivan.gurtler at ahead-itec.com Thu Apr 23 09:37:20 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Thu, 23 Apr 2015 15:37:20 +0200 Subject: [aerogear-dev] Unified Push - status In-Reply-To: References: Message-ID: ... oh :D sorry ... I found /model /jpa /testData /*create_db_content.ddl ... *I try it ... *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-04-23 15:30 GMT+02:00 Ivan G?rtler : > In report file for PushApplicationDaoTest ... i found: > > ... > javax.persistence.PersistenceException: > org.hibernate.exception.DataException: could not initialize a collection: > [org.jboss.aerogear.unifiedpush.api.PushApplication.variants#1] > at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown > Source) > at > org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown > Source) > at > org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown > Source) > at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) > at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) > at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown > Source) > at org.apache.derby.impl.jdbc.ConnectionChild.newSQLException(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedResultSet.dataTypeConversion(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) > at > org.hibernate.type.descriptor.sql.ClobTypeDescriptor$1.doExtract(ClobTypeDescriptor.java:60) > at > org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:64) > at > org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:265) > at > org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:261) > at > org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:251) > at > org.hibernate.type.AbstractStandardBasicType.hydrate(AbstractStandardBasicType.java:336) > at > org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2924) > at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1695) > at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1627) > at org.hibernate.loader.Loader.getRow(Loader.java:1509) > at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:719) > at org.hibernate.loader.Loader.processResultSet(Loader.java:949) > at org.hibernate.loader.Loader.doQuery(Loader.java:917) > at > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:348) > at > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:318) > at org.hibernate.loader.Loader.loadCollection(Loader.java:2262) > at > org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:65) > at > org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:674) > at > org.hibernate.event.internal.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:86) > at > org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1774) > at > org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:696) > at > org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:1037) > at > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:353) > at org.hibernate.loader.Loader.doList(Loader.java:2550) > at org.hibernate.loader.Loader.doList(Loader.java:2536) > at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2366) > at org.hibernate.loader.Loader.list(Loader.java:2361) > at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:495) > at > org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:357) > at > org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:198) > at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1194) > at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101) > at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:264) > at > org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPABaseDao.getSingleResultForQuery(JPABaseDao.java:93) > at > org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPAPushApplicationDao.findByPushApplicationID(JPAPushApplicationDao.java:73) > at > org.jboss.aerogear.unifiedpush.jpa.PushApplicationDaoTest.updatePushApplication(PushApplicationDaoTest.java:125) > ... > > > In aerogear:master version two mounth ago it was without problems. I found > commit "Use JMS message queues for sending notifications in batches > AGPUSH-1348" ... in this commit was changed orm.xml file ... but I dont > know background of commit change. > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-04-23 15:05 GMT+02:00 Erik Jan de Wit : > >> Hi Ivan, >> >> Try running without the test `mvn install -DskipTests`, because they >> are testing against another schema. Or see why the tests fail in the >> >> C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports >> directory and fix those tests, by changing >> model\jpa\test\create_db_content.ddl >> >> On Thu, Apr 23, 2015 at 2:58 PM, Ivan G?rtler >> wrote: >> > Hi, >> > We have own fork ... and I sync with "aerogear:master". Master branch in >> > fork is OK. >> > I merge master to second branch. We changed >> > model/jpa/src/main/resources/META-INF/orm.xml file in second branch >> because >> > we use ORACLE >> > ... >> > >> > ios >> > >> > >> > >> > >> > >> > >> > >> > ... >> > (Second change in orm.xml file was because of Installation class, it was >> > bigger than 4000 -> problem in ORACLE ... but in "aerogear:master" it >> was >> > removed from orm.xml file) >> > but when ... Run as ... Maven insall ... In console: >> > ... >> > Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.366 >> sec >> > Results : >> > Failed tests: >> > Expected exception: javax.persistence.PersistenceException >> > Tests in error: >> > PushApplicationDaoTest.updatePushApplication:125 ? Persistence >> > org.hibernate.e... >> > PushApplicationDaoTest.pushApplicationIDUnmodifiedAfterUpdate:159 ? >> > Persistence >> > >> > >> PushApplicationDaoTest.deletePushApplicationIncludingVariantAndInstallations:194 >> > ? Persistence >> > PushApplicationDaoTest.findByPushApplicationID:116 ? Persistence >> > org.hibernate... >> > PushApplicationDaoTest.findAllForDeveloper:72 ? Persistence >> > org.hibernate.exce... >> > PushApplicationDaoTest.primaryKeyUnmodifiedAfterUpdate:174 ? >> Persistence >> > org.h... >> > PushApplicationDaoTest.findAllIDsForDeveloper:96 ? Persistence >> > org.hibernate.e... >> > PushApplicationDaoTest.findByPushApplicationIDForDeveloper:103 ? >> > Persistence o... >> > PushApplicationDaoTest.updateAndDeletePushApplication:140 ? >> Persistence >> > org.hi... >> > Tests run: 75, Failures: 1, Errors: 9, Skipped: 0 >> > [INFO] >> > ------------------------------------------------------------------------ >> > [INFO] Reactor Summary: >> > [INFO] >> > [INFO] AeroGear UnifiedPush Server ....................... SUCCESS [ >> 2.833 >> > s] >> > [INFO] UnifiedPush Model Layer ........................... SUCCESS [ >> 0.058 >> > s] >> > [INFO] UnifiedPush Server Model API ...................... SUCCESS [ >> 2.886 >> > s] >> > [INFO] UnifiedPush Server Model JPA implementation ....... FAILURE [ >> 32.992 >> > s] >> > [INFO] UnifiedPush Service Layer ......................... SKIPPED >> > [INFO] UnifiedPush Sender Module ......................... SKIPPED >> > [INFO] UnifiedPush Push Message Model .................... SKIPPED >> > [INFO] UnifiedPush Push Notification Networks ............ SKIPPED >> > [INFO] UnifiedPush RESTful Endpoint ...................... SKIPPED >> > [INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED >> > [INFO] UnifiedPush Dependencies Parent ................... SKIPPED >> > [INFO] UnifiedPush Server Dependencies Server ............ SKIPPED >> > [INFO] UnifiedPush Auth Server ........................... SKIPPED >> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED >> > [INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED >> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED >> > [INFO] >> > ------------------------------------------------------------------------ >> > [INFO] BUILD FAILURE >> > [INFO] >> > ------------------------------------------------------------------------ >> > [INFO] Total time: 40.717 s >> > [INFO] Finished at: 2015-04-23T14:35:45+01:00 >> > [INFO] Final Memory: 21M/420M >> > [INFO] >> > ------------------------------------------------------------------------ >> > [ERROR] Failed to execute goal >> > org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test >> (default-test) on >> > project unifiedpush-model-jpa: There are test failures. >> > [ERROR] >> > [ERROR] Please refer to >> > >> C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports >> > for the individual test results. >> > [ERROR] -> [Help 1] >> > [ERROR] >> > [ERROR] To see the full stack trace of the errors, re-run Maven with >> the -e >> > switch. >> > [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> > [ERROR] >> > [ERROR] For more information about the errors and possible solutions, >> please >> > read the following articles: >> > [ERROR] [Help 1] >> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >> > [ERROR] >> > [ERROR] After correcting the problems, you can resume the build with the >> > command >> > [ERROR] mvn -rf :unifiedpush-model-jpa >> > >> --------------------------------------------------------------------------------------------------------------------------------------------------------------- >> > Do you have any idea where is the problem and how to solve it? >> > Thanks >> > >> > Mgr. Ivan G?rtler >> > Mobile software developer >> > >> > AHEAD iTec, s.r.o., Botanick? 554/68a, >> > 602 00 Brno (Czech Republic) >> > >> > www.ahead-itec.com | twitter | mobile security solutions >> > >> > 2015-04-23 8:55 GMT+02:00 Erik Jan de Wit : >> >> >> >> Hi Ivan, >> >> >> >> We have functionality for this available in the master branch on >> >> github. Go to /ag-push/rest/sys/info/health it will return >> >> json with the push network status and db status. This PR >> >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/519 >> >> includes details about the returned json. >> >> >> >> Hope this helps... >> >> >> >> --- >> >> Cheers, >> >> Erik Jan >> >> >> >> On Thu, Apr 23, 2015 at 8:39 AM, Ivan G?rtler >> >> wrote: >> >> > Hi, >> >> > I have some questions about server status. >> >> > Is possible to check with some kind of ping (or something else) that >> DB >> >> > is >> >> > available from push server? >> >> > How to check if platform push server (APNS...) is also available? >> >> > >> >> > >> >> > Thanks >> >> > >> >> > Mgr. Ivan G?rtler >> >> > Mobile software developer >> >> > >> >> > AHEAD iTec, s.r.o., Botanick? 554/68a, >> >> > 602 00 Brno (Czech Republic) >> >> > >> >> > www.ahead-itec.com | twitter | mobile security solutions >> >> > >> >> > _______________________________________________ >> >> > aerogear-dev mailing list >> >> > aerogear-dev at lists.jboss.org >> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> >> >> >> -- >> >> Cheers, >> >> Erik Jan >> >> >> >> _______________________________________________ >> >> aerogear-dev mailing list >> >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > >> > >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150423/e1f2b668/attachment-0001.html From corinnekrych at gmail.com Thu Apr 23 10:54:32 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 23 Apr 2015 16:54:32 +0200 Subject: [aerogear-dev] iOS7 support Message-ID: <3E33EEA9-35F2-4B36-9208-383A4B733316@gmail.com> Hello Swift lovers, We?ve already talked about iOS7 support for our Swift libs in this thread [0] but I?d like to start from fresh with a different approach. I?ve recently revisit the subject with some experiments and I ended up writing a blog post: How well does Swift play with iOS7? [1] where I take 2 examples: aerogear-ios-push and aerogear-ios-http with their demo apps: HelloWorld [2] and ChuckNorrisJokes [3] all written in Swift and run them in iOS7 device/simulator. This is just an experiment, but moving forward I?ve created a JIRA epic [4] to support iOS7 for our aerogear-ios Swift libraries. In the long run, we will have only one branch to maintain: master. All the libs should be tested with iOS7 and iOS8 examples. Some libs can stay in Objective-C (until we feel the need of moving them to Swift) like aerogear-ios-otp for example. A corraleted JIRA epic [5] is to test all aerogear-ios libs written in Objective-C with iOS8 and Swift. We might have issues around common crypto usage in Swift [6]. I?d like to adress those 2 epics for iOS 2.4 release and deprecate the 1.6.X branch maintenance. wdyt? ++ Corinne [0] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Swift-to-Objective-C-interop-one-aspect-of-iOS7-Swift-support-td10644.html [1] http://corinnekrych.blogspot.org/2015/04/how-well-does-swift-plays-on-ios7.html [2] https://github.com/corinnekrych/unified-push-helloworld/tree/ios7.experiment/ios-swift-ios7-nolib [3] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/ios7.support/ChuckNorrisJokes%2FPodfile#L4 [4] TODO when jira is up [5] TODO when jira is up [6] http://stackoverflow.com/questions/25248598/importing-commoncrypto-in-a-swift-framework From corinnekrych at gmail.com Fri Apr 24 02:59:39 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 24 Apr 2015 08:59:39 +0200 Subject: [aerogear-dev] Swift 1.2 is out! Xcode 6.3 is ready! In-Reply-To: References: <713929C4-435B-4547-9305-3E500B51CB83@gmail.com> Message-ID: <484E3779-5498-42D7-A276-C843983BD248@gmail.com> Hello guys, Travis gave us some news about its xcode 6.3 readiness [1] and?. it?s not so good :( I?m afraid we might wait a bit longer. couple of week to get Xcode.2 support and then they start tacking Xcode6.3. If I had to take a bet, i?d say maybe it?ll be ready by June. Let?s keep an eye. ++ Corinne [1] http://blog.travis-ci.com/2015-04-20-state-of-the-mac-infrastructure-on-travis-ci/ > On 20 Apr 2015, at 21:03, Sebastien Blanc wrote: > > +1 > We are way more cooler than travis ;) > > On Mon, Apr 20, 2015 at 6:01 PM, Christos Vasilakis wrote: > > > On Mon, Apr 20, 2015 at 2:54 PM, Corinne Krych wrote: > Hello All, > > Let me give you an update on Swift 1.2: all Swift repos has been updated (PR sent and under review). See [1] > > The only missing part is the lack of Travis support for Xcode 6.3. > > Although initial announcement from April 9th says: good news will happen "next week" (ie: last week), we still don't have xcode63 support. iOS and OSX community is eagerly asking for it [2] but no clear answer so far :( > > Given the iOS 2.3 planned release end of this week, I'd propose to merge this PRs without travis support. And keep an eyes on Travis Xcode63 support. > > Thoughts? > > > +1 let's not block cause of delay's of Travis and release the bits > > - > Christos > > > ++ > Corinne > > [1] https://issues.jboss.org/browse/AGIOS-428 > [2] https://twitter.com/rob_rix/status/589774192813432832 > > On 14 April 2015 at 11:16, Corinne Krych wrote: > Off course > I'm doing it atm > ++ > Corinne > > On 14 April 2015 at 11:12, Matthias Wessendorf wrote: > Corinne, > > will you update this app as well ? > https://github.com/jboss-mobile/unified-push-helloworld/tree/swift/ios-swift > > > > On Fri, Apr 10, 2015 at 3:41 PM, Corinne Krych wrote: > Unfortunately Travis is not ready yet [1] > I will prepare the PR and test it so we can merge when Travis is ready. > ++ > Corinne > [1] http://blog.travis-ci.com/2015-04-09-this-week-in-travis-ci/ > [2] https://travis-ci.org/corinnekrych/aerogear-ios-http-1/builds/57947586 > > On 10 April 2015 at 14:17, Corinne Krych wrote: > > > On 10 April 2015 at 11:26, Christos Vasilakis wrote: > > > On Fri, Apr 10, 2015 at 9:57 AM, Corinne Krych wrote: > Hello iOS lovers, > > Xcode 6.3 is officially out (since 2 days actually). > And Travis build seems to be ready. > > Xcode 6.3 comes with Swift 1.2, so it implies some (minor) compilation changes. > I think it?s time to move to this new stable version. I have created the JIRA epic/ticket [1] and I?ll start the migration targetting 2.3 iOS release (end of April). > > +9001 > > long time to see only one release out and no myriad of betas ;) > http://tinyurl.com/po946bv > > > > Indeed! > :) > > > > > Any questions, toughts? > ++ > Corinne > [1] https://issues.jboss.org/browse/AGIOS-428 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From edewit at redhat.com Fri Apr 24 03:32:34 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 24 Apr 2015 09:32:34 +0200 Subject: [aerogear-dev] cordova otp 0.0.2 release Message-ID: With the addition of windows support it would be a good idea to release another version of the otp plugin. I've created a branch 0.0.2 for your testing pleasure. To test add the plugin from the branch: cordova plugin add https://github.com/aerogear/aerogear-cordova-otp.git#0.0.2 Release notes: Bug [AGCORDOVA-89] - Remove Podfile workaround [AGCORDOVA-90] - incorrect dependency on cordova otp plugin Feature Request [AGCORDOVA-60] - Add windows support for otp -- Cheers, Erik Jan From corinnekrych at gmail.com Fri Apr 24 06:43:14 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 24 Apr 2015 12:43:14 +0200 Subject: [aerogear-dev] Next release version for AeroGearSync, AeroGearSyncClient Message-ID: <8C6F568F-903A-4ED7-8EC1-4D59158F3AC1@gmail.com> Hello guys As part of umbrella iOS 2.3 release, we need a new cocoapods release for AeroGearSync and AeroGearSyncClient. The current version is tagged "1.0.0-alpha.1?, following semver next should be "1.0.0-alpha.2?. Fine for all? ++ Corinne From lukas.fryc at gmail.com Fri Apr 24 06:46:15 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Fri, 24 Apr 2015 10:46:15 +0000 Subject: [aerogear-dev] Next release version for AeroGearSync, AeroGearSyncClient In-Reply-To: <8C6F568F-903A-4ED7-8EC1-4D59158F3AC1@gmail.com> References: <8C6F568F-903A-4ED7-8EC1-4D59158F3AC1@gmail.com> Message-ID: +1 1.0.0-alpha.2 sounds appropriate even though it does not contain a huge changeset p? 24. 4. 2015 v 12:43 odes?latel Corinne Krych napsal: > Hello guys > > As part of umbrella iOS 2.3 release, we need a new cocoapods release for > AeroGearSync and AeroGearSyncClient. > The current version is tagged "1.0.0-alpha.1?, following semver next > should be "1.0.0-alpha.2?. > > Fine for all? > > ++ > Corinne > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150424/2e78f583/attachment.html From cvasilak at gmail.com Fri Apr 24 06:53:18 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Fri, 24 Apr 2015 13:53:18 +0300 Subject: [aerogear-dev] Next release version for AeroGearSync, AeroGearSyncClient In-Reply-To: References: <8C6F568F-903A-4ED7-8EC1-4D59158F3AC1@gmail.com> Message-ID: +1 sounds good On Fri, Apr 24, 2015 at 1:46 PM, Luk?? Fry? wrote: > +1 > > 1.0.0-alpha.2 sounds appropriate even though it does not contain a huge > changeset > > p? 24. 4. 2015 v 12:43 odes?latel Corinne Krych > napsal: > > Hello guys >> >> As part of umbrella iOS 2.3 release, we need a new cocoapods release for >> AeroGearSync and AeroGearSyncClient. >> The current version is tagged "1.0.0-alpha.1?, following semver next >> should be "1.0.0-alpha.2?. >> >> Fine for all? >> >> ++ >> Corinne >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150424/76dcc94e/attachment.html From ivan.gurtler at ahead-itec.com Fri Apr 24 07:21:52 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Fri, 24 Apr 2015 13:21:52 +0200 Subject: [aerogear-dev] Unified Push - status In-Reply-To: References: Message-ID: Hi, I tried mvn install without tests ... but deployment on EAP 6.3 server ended with error... I tried to repair test DB (*create_db_content.ddl*) for my case ... mvn install was ok but deployment with error ... and same error was also in case when I made mvn install on master branch and tried to deploy .... Failed to add Deployment ag-push.war Unexpected HTTP response: 500 Request { "operation" => "composite", "address" => [], "steps" => [ { "address" => [ ("server-group" => "main-server-group"), ("deployment" => "ag-push.war") ], "operation" => "add" }, { "address" => [ ("server-group" => "main-server-group"), ("deployment" => "ag-push.war") ], "operation" => "deploy" } ] } Response Internal Server Error { "outcome" => "failed", "result" => { "step-1" => {"outcome" => "success"}, "step-2" => {"outcome" => "success"} }, "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.", "rolled-back" => true, "server-groups" => {"main-server-group" => {"host" => {"master" => {"server-A" => {"response" => { "outcome" => "failed", "result" => { "step-1" => { "outcome" => "failed", "rolled-back" => true }, "step-2" => { "outcome" => "failed", "failure-description" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"ag-push.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ag-push.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"ag-push.war\" Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}, "rolled-back" => true } }, "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"ag-push.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ag-push.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"ag-push.war\" Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}}}, "rolled-back" => true }}}}}} } I dont know where the problem is now ... Thanks for your help ... *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-04-23 15:37 GMT+02:00 Ivan G?rtler : > ... oh :D sorry ... > I found /model > > /jpa > > /testData > > /*create_db_content.ddl ... *I try it ... > > *Mgr. Ivan G?rtler* > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile > security solutions > > 2015-04-23 15:30 GMT+02:00 Ivan G?rtler : > >> In report file for PushApplicationDaoTest ... i found: >> >> ... >> javax.persistence.PersistenceException: >> org.hibernate.exception.DataException: could not initialize a collection: >> [org.jboss.aerogear.unifiedpush.api.PushApplication.variants#1] >> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown >> Source) >> at >> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown >> Source) >> at >> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown >> Source) >> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) >> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) >> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) >> at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown >> Source) >> at org.apache.derby.impl.jdbc.ConnectionChild.newSQLException(Unknown >> Source) >> at org.apache.derby.impl.jdbc.EmbedResultSet.dataTypeConversion(Unknown >> Source) >> at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) >> at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) >> at >> org.hibernate.type.descriptor.sql.ClobTypeDescriptor$1.doExtract(ClobTypeDescriptor.java:60) >> at >> org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:64) >> at >> org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:265) >> at >> org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:261) >> at >> org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:251) >> at >> org.hibernate.type.AbstractStandardBasicType.hydrate(AbstractStandardBasicType.java:336) >> at >> org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2924) >> at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1695) >> at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1627) >> at org.hibernate.loader.Loader.getRow(Loader.java:1509) >> at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:719) >> at org.hibernate.loader.Loader.processResultSet(Loader.java:949) >> at org.hibernate.loader.Loader.doQuery(Loader.java:917) >> at >> org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:348) >> at >> org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:318) >> at org.hibernate.loader.Loader.loadCollection(Loader.java:2262) >> at >> org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:65) >> at >> org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:674) >> at >> org.hibernate.event.internal.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:86) >> at >> org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1774) >> at >> org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:696) >> at >> org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:1037) >> at >> org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:353) >> at org.hibernate.loader.Loader.doList(Loader.java:2550) >> at org.hibernate.loader.Loader.doList(Loader.java:2536) >> at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2366) >> at org.hibernate.loader.Loader.list(Loader.java:2361) >> at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:495) >> at >> org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:357) >> at >> org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:198) >> at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1194) >> at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101) >> at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:264) >> at >> org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPABaseDao.getSingleResultForQuery(JPABaseDao.java:93) >> at >> org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPAPushApplicationDao.findByPushApplicationID(JPAPushApplicationDao.java:73) >> at >> org.jboss.aerogear.unifiedpush.jpa.PushApplicationDaoTest.updatePushApplication(PushApplicationDaoTest.java:125) >> ... >> >> >> In aerogear:master version two mounth ago it was without problems. I >> found commit "Use JMS message queues for sending notifications in >> batches AGPUSH-1348" ... in this commit was changed orm.xml file ... but >> I dont know background of commit change. >> >> *Mgr. Ivan G?rtler* >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | >> mobile security solutions >> >> 2015-04-23 15:05 GMT+02:00 Erik Jan de Wit : >> >>> Hi Ivan, >>> >>> Try running without the test `mvn install -DskipTests`, because they >>> are testing against another schema. Or see why the tests fail in the >>> >>> C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports >>> directory and fix those tests, by changing >>> model\jpa\test\create_db_content.ddl >>> >>> On Thu, Apr 23, 2015 at 2:58 PM, Ivan G?rtler >>> wrote: >>> > Hi, >>> > We have own fork ... and I sync with "aerogear:master". Master branch >>> in >>> > fork is OK. >>> > I merge master to second branch. We changed >>> > model/jpa/src/main/resources/META-INF/orm.xml file in second branch >>> because >>> > we use ORACLE >>> > ... >>> > >>> > ios >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > ... >>> > (Second change in orm.xml file was because of Installation class, it >>> was >>> > bigger than 4000 -> problem in ORACLE ... but in "aerogear:master" it >>> was >>> > removed from orm.xml file) >>> > but when ... Run as ... Maven insall ... In console: >>> > ... >>> > Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.366 >>> sec >>> > Results : >>> > Failed tests: >>> > Expected exception: javax.persistence.PersistenceException >>> > Tests in error: >>> > PushApplicationDaoTest.updatePushApplication:125 ? Persistence >>> > org.hibernate.e... >>> > PushApplicationDaoTest.pushApplicationIDUnmodifiedAfterUpdate:159 ? >>> > Persistence >>> > >>> > >>> PushApplicationDaoTest.deletePushApplicationIncludingVariantAndInstallations:194 >>> > ? Persistence >>> > PushApplicationDaoTest.findByPushApplicationID:116 ? Persistence >>> > org.hibernate... >>> > PushApplicationDaoTest.findAllForDeveloper:72 ? Persistence >>> > org.hibernate.exce... >>> > PushApplicationDaoTest.primaryKeyUnmodifiedAfterUpdate:174 ? >>> Persistence >>> > org.h... >>> > PushApplicationDaoTest.findAllIDsForDeveloper:96 ? Persistence >>> > org.hibernate.e... >>> > PushApplicationDaoTest.findByPushApplicationIDForDeveloper:103 ? >>> > Persistence o... >>> > PushApplicationDaoTest.updateAndDeletePushApplication:140 ? >>> Persistence >>> > org.hi... >>> > Tests run: 75, Failures: 1, Errors: 9, Skipped: 0 >>> > [INFO] >>> > >>> ------------------------------------------------------------------------ >>> > [INFO] Reactor Summary: >>> > [INFO] >>> > [INFO] AeroGear UnifiedPush Server ....................... SUCCESS [ >>> 2.833 >>> > s] >>> > [INFO] UnifiedPush Model Layer ........................... SUCCESS [ >>> 0.058 >>> > s] >>> > [INFO] UnifiedPush Server Model API ...................... SUCCESS [ >>> 2.886 >>> > s] >>> > [INFO] UnifiedPush Server Model JPA implementation ....... FAILURE [ >>> 32.992 >>> > s] >>> > [INFO] UnifiedPush Service Layer ......................... SKIPPED >>> > [INFO] UnifiedPush Sender Module ......................... SKIPPED >>> > [INFO] UnifiedPush Push Message Model .................... SKIPPED >>> > [INFO] UnifiedPush Push Notification Networks ............ SKIPPED >>> > [INFO] UnifiedPush RESTful Endpoint ...................... SKIPPED >>> > [INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED >>> > [INFO] UnifiedPush Dependencies Parent ................... SKIPPED >>> > [INFO] UnifiedPush Server Dependencies Server ............ SKIPPED >>> > [INFO] UnifiedPush Auth Server ........................... SKIPPED >>> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED >>> > [INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED >>> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED >>> > [INFO] >>> > >>> ------------------------------------------------------------------------ >>> > [INFO] BUILD FAILURE >>> > [INFO] >>> > >>> ------------------------------------------------------------------------ >>> > [INFO] Total time: 40.717 s >>> > [INFO] Finished at: 2015-04-23T14:35:45+01:00 >>> > [INFO] Final Memory: 21M/420M >>> > [INFO] >>> > >>> ------------------------------------------------------------------------ >>> > [ERROR] Failed to execute goal >>> > org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test >>> (default-test) on >>> > project unifiedpush-model-jpa: There are test failures. >>> > [ERROR] >>> > [ERROR] Please refer to >>> > >>> C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports >>> > for the individual test results. >>> > [ERROR] -> [Help 1] >>> > [ERROR] >>> > [ERROR] To see the full stack trace of the errors, re-run Maven with >>> the -e >>> > switch. >>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> > [ERROR] >>> > [ERROR] For more information about the errors and possible solutions, >>> please >>> > read the following articles: >>> > [ERROR] [Help 1] >>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>> > [ERROR] >>> > [ERROR] After correcting the problems, you can resume the build with >>> the >>> > command >>> > [ERROR] mvn -rf :unifiedpush-model-jpa >>> > >>> --------------------------------------------------------------------------------------------------------------------------------------------------------------- >>> > Do you have any idea where is the problem and how to solve it? >>> > Thanks >>> > >>> > Mgr. Ivan G?rtler >>> > Mobile software developer >>> > >>> > AHEAD iTec, s.r.o., Botanick? 554/68a, >>> > 602 00 Brno (Czech Republic) >>> > >>> > www.ahead-itec.com | twitter | mobile security solutions >>> > >>> > 2015-04-23 8:55 GMT+02:00 Erik Jan de Wit : >>> >> >>> >> Hi Ivan, >>> >> >>> >> We have functionality for this available in the master branch on >>> >> github. Go to /ag-push/rest/sys/info/health it will return >>> >> json with the push network status and db status. This PR >>> >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/519 >>> >> includes details about the returned json. >>> >> >>> >> Hope this helps... >>> >> >>> >> --- >>> >> Cheers, >>> >> Erik Jan >>> >> >>> >> On Thu, Apr 23, 2015 at 8:39 AM, Ivan G?rtler >>> >> wrote: >>> >> > Hi, >>> >> > I have some questions about server status. >>> >> > Is possible to check with some kind of ping (or something else) >>> that DB >>> >> > is >>> >> > available from push server? >>> >> > How to check if platform push server (APNS...) is also available? >>> >> > >>> >> > >>> >> > Thanks >>> >> > >>> >> > Mgr. Ivan G?rtler >>> >> > Mobile software developer >>> >> > >>> >> > AHEAD iTec, s.r.o., Botanick? 554/68a, >>> >> > 602 00 Brno (Czech Republic) >>> >> > >>> >> > www.ahead-itec.com | twitter | mobile security solutions >>> >> > >>> >> > _______________________________________________ >>> >> > aerogear-dev mailing list >>> >> > aerogear-dev at lists.jboss.org >>> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >>> >> >>> >> >>> >> -- >>> >> Cheers, >>> >> Erik Jan >>> >> >>> >> _______________________________________________ >>> >> aerogear-dev mailing list >>> >> aerogear-dev at lists.jboss.org >>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> > >>> > >>> > >>> > _______________________________________________ >>> > aerogear-dev mailing list >>> > aerogear-dev at lists.jboss.org >>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> -- >>> Cheers, >>> Erik Jan >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150424/4a1b3e59/attachment-0001.html From edewit at redhat.com Fri Apr 24 07:49:00 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 24 Apr 2015 13:49:00 +0200 Subject: [aerogear-dev] Unified Push - status In-Reply-To: References: Message-ID: Do you have some more logs, all you shared now is that it's not deployed but not why. On Fri, Apr 24, 2015 at 1:21 PM, Ivan G?rtler wrote: > Hi, > > I tried mvn install without tests ... but deployment on EAP 6.3 server ended > with error... > I tried to repair test DB (create_db_content.ddl) for my case ... mvn > install was ok but deployment with error ... > > and same error was also in case when I made mvn install on master branch and > tried to deploy .... > > > Failed to add Deployment ag-push.war > > Unexpected HTTP response: 500 > > Request > { > "operation" => "composite", > "address" => [], > "steps" => [ > { > "address" => [ > ("server-group" => "main-server-group"), > ("deployment" => "ag-push.war") > ], > "operation" => "add" > }, > { > "address" => [ > ("server-group" => "main-server-group"), > ("deployment" => "ag-push.war") > ], > "operation" => "deploy" > } > ] > } > > Response > > Internal Server Error > { > "outcome" => "failed", > "result" => { > "step-1" => {"outcome" => "success"}, > "step-2" => {"outcome" => "success"} > }, > "failure-description" => "JBAS010839: Operation failed or was rolled > back on all servers.", > "rolled-back" => true, > "server-groups" => {"main-server-group" => {"host" => {"master" => > {"server-A" => {"response" => { > "outcome" => "failed", > "result" => { > "step-1" => { > "outcome" => "failed", > "rolled-back" => true > }, > "step-2" => { > "outcome" => "failed", > "failure-description" => {"JBAS014671: Failed services" => > {"jboss.deployment.unit.\"ag-push.war\".PARSE" => > "org.jboss.msc.service.StartException in service > jboss.deployment.unit.\"ag-push.war\".PARSE: JBAS018733: Failed to process > phase PARSE of deployment \"ag-push.war\" > Caused by: org.jboss.msc.service.ServiceNotFoundException: Service > service jboss.ejb.default-resource-adapter-name-service not found"}}, > "rolled-back" => true > } > }, > "failure-description" => {"JBAS014653: Composite operation failed > and was rolled back. Steps that failed:" => {"Operation step-2" => > {"JBAS014671: Failed services" => > {"jboss.deployment.unit.\"ag-push.war\".PARSE" => > "org.jboss.msc.service.StartException in service > jboss.deployment.unit.\"ag-push.war\".PARSE: JBAS018733: Failed to process > phase PARSE of deployment \"ag-push.war\" > Caused by: org.jboss.msc.service.ServiceNotFoundException: Service > service jboss.ejb.default-resource-adapter-name-service not found"}}}}, > "rolled-back" => true > }}}}}} > } > > > I dont know where the problem is now ... > Thanks for your help ... > > > Mgr. Ivan G?rtler > Mobile software developer > > AHEAD iTec, s.r.o., Botanick? 554/68a, > 602 00 Brno (Czech Republic) > > www.ahead-itec.com | twitter | mobile security solutions > > 2015-04-23 15:37 GMT+02:00 Ivan G?rtler : >> >> ... oh :D sorry ... >> I found /model/jpa/testData/create_db_content.ddl ... I try it ... >> >> Mgr. Ivan G?rtler >> Mobile software developer >> >> AHEAD iTec, s.r.o., Botanick? 554/68a, >> 602 00 Brno (Czech Republic) >> >> www.ahead-itec.com | twitter | mobile security solutions >> >> 2015-04-23 15:30 GMT+02:00 Ivan G?rtler : >>> >>> In report file for PushApplicationDaoTest ... i found: >>> >>> ... >>> javax.persistence.PersistenceException: >>> org.hibernate.exception.DataException: could not initialize a collection: >>> [org.jboss.aerogear.unifiedpush.api.PushApplication.variants#1] >>> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown >>> Source) >>> at >>> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown >>> Source) >>> at >>> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown >>> Source) >>> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) >>> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) >>> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) >>> at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown >>> Source) >>> at org.apache.derby.impl.jdbc.ConnectionChild.newSQLException(Unknown >>> Source) >>> at org.apache.derby.impl.jdbc.EmbedResultSet.dataTypeConversion(Unknown >>> Source) >>> at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) >>> at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) >>> at >>> org.hibernate.type.descriptor.sql.ClobTypeDescriptor$1.doExtract(ClobTypeDescriptor.java:60) >>> at >>> org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:64) >>> at >>> org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:265) >>> at >>> org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:261) >>> at >>> org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:251) >>> at >>> org.hibernate.type.AbstractStandardBasicType.hydrate(AbstractStandardBasicType.java:336) >>> at >>> org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2924) >>> at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1695) >>> at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1627) >>> at org.hibernate.loader.Loader.getRow(Loader.java:1509) >>> at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:719) >>> at org.hibernate.loader.Loader.processResultSet(Loader.java:949) >>> at org.hibernate.loader.Loader.doQuery(Loader.java:917) >>> at >>> org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:348) >>> at >>> org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:318) >>> at org.hibernate.loader.Loader.loadCollection(Loader.java:2262) >>> at >>> org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:65) >>> at >>> org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:674) >>> at >>> org.hibernate.event.internal.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:86) >>> at >>> org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1774) >>> at >>> org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:696) >>> at >>> org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:1037) >>> at >>> org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:353) >>> at org.hibernate.loader.Loader.doList(Loader.java:2550) >>> at org.hibernate.loader.Loader.doList(Loader.java:2536) >>> at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2366) >>> at org.hibernate.loader.Loader.list(Loader.java:2361) >>> at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:495) >>> at >>> org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:357) >>> at >>> org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:198) >>> at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1194) >>> at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101) >>> at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:264) >>> at >>> org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPABaseDao.getSingleResultForQuery(JPABaseDao.java:93) >>> at >>> org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPAPushApplicationDao.findByPushApplicationID(JPAPushApplicationDao.java:73) >>> at >>> org.jboss.aerogear.unifiedpush.jpa.PushApplicationDaoTest.updatePushApplication(PushApplicationDaoTest.java:125) >>> ... >>> >>> >>> In aerogear:master version two mounth ago it was without problems. I >>> found commit "Use JMS message queues for sending notifications in batches >>> AGPUSH-1348" ... in this commit was changed orm.xml file ... but I dont know >>> background of commit change. >>> >>> Mgr. Ivan G?rtler >>> Mobile software developer >>> >>> AHEAD iTec, s.r.o., Botanick? 554/68a, >>> 602 00 Brno (Czech Republic) >>> >>> www.ahead-itec.com | twitter | mobile security solutions >>> >>> 2015-04-23 15:05 GMT+02:00 Erik Jan de Wit : >>>> >>>> Hi Ivan, >>>> >>>> Try running without the test `mvn install -DskipTests`, because they >>>> are testing against another schema. Or see why the tests fail in the >>>> >>>> C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports >>>> directory and fix those tests, by changing >>>> model\jpa\test\create_db_content.ddl >>>> >>>> On Thu, Apr 23, 2015 at 2:58 PM, Ivan G?rtler >>>> wrote: >>>> > Hi, >>>> > We have own fork ... and I sync with "aerogear:master". Master branch >>>> > in >>>> > fork is OK. >>>> > I merge master to second branch. We changed >>>> > model/jpa/src/main/resources/META-INF/orm.xml file in second branch >>>> > because >>>> > we use ORACLE >>>> > ... >>>> > >>>> > ios >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > ... >>>> > (Second change in orm.xml file was because of Installation class, it >>>> > was >>>> > bigger than 4000 -> problem in ORACLE ... but in "aerogear:master" it >>>> > was >>>> > removed from orm.xml file) >>>> > but when ... Run as ... Maven insall ... In console: >>>> > ... >>>> > Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.366 >>>> > sec >>>> > Results : >>>> > Failed tests: >>>> > Expected exception: javax.persistence.PersistenceException >>>> > Tests in error: >>>> > PushApplicationDaoTest.updatePushApplication:125 ? Persistence >>>> > org.hibernate.e... >>>> > PushApplicationDaoTest.pushApplicationIDUnmodifiedAfterUpdate:159 ? >>>> > Persistence >>>> > >>>> > >>>> > PushApplicationDaoTest.deletePushApplicationIncludingVariantAndInstallations:194 >>>> > ? Persistence >>>> > PushApplicationDaoTest.findByPushApplicationID:116 ? Persistence >>>> > org.hibernate... >>>> > PushApplicationDaoTest.findAllForDeveloper:72 ? Persistence >>>> > org.hibernate.exce... >>>> > PushApplicationDaoTest.primaryKeyUnmodifiedAfterUpdate:174 ? >>>> > Persistence >>>> > org.h... >>>> > PushApplicationDaoTest.findAllIDsForDeveloper:96 ? Persistence >>>> > org.hibernate.e... >>>> > PushApplicationDaoTest.findByPushApplicationIDForDeveloper:103 ? >>>> > Persistence o... >>>> > PushApplicationDaoTest.updateAndDeletePushApplication:140 ? >>>> > Persistence >>>> > org.hi... >>>> > Tests run: 75, Failures: 1, Errors: 9, Skipped: 0 >>>> > [INFO] >>>> > >>>> > ------------------------------------------------------------------------ >>>> > [INFO] Reactor Summary: >>>> > [INFO] >>>> > [INFO] AeroGear UnifiedPush Server ....................... SUCCESS [ >>>> > 2.833 >>>> > s] >>>> > [INFO] UnifiedPush Model Layer ........................... SUCCESS [ >>>> > 0.058 >>>> > s] >>>> > [INFO] UnifiedPush Server Model API ...................... SUCCESS [ >>>> > 2.886 >>>> > s] >>>> > [INFO] UnifiedPush Server Model JPA implementation ....... FAILURE [ >>>> > 32.992 >>>> > s] >>>> > [INFO] UnifiedPush Service Layer ......................... SKIPPED >>>> > [INFO] UnifiedPush Sender Module ......................... SKIPPED >>>> > [INFO] UnifiedPush Push Message Model .................... SKIPPED >>>> > [INFO] UnifiedPush Push Notification Networks ............ SKIPPED >>>> > [INFO] UnifiedPush RESTful Endpoint ...................... SKIPPED >>>> > [INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED >>>> > [INFO] UnifiedPush Dependencies Parent ................... SKIPPED >>>> > [INFO] UnifiedPush Server Dependencies Server ............ SKIPPED >>>> > [INFO] UnifiedPush Auth Server ........................... SKIPPED >>>> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED >>>> > [INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED >>>> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED >>>> > [INFO] >>>> > >>>> > ------------------------------------------------------------------------ >>>> > [INFO] BUILD FAILURE >>>> > [INFO] >>>> > >>>> > ------------------------------------------------------------------------ >>>> > [INFO] Total time: 40.717 s >>>> > [INFO] Finished at: 2015-04-23T14:35:45+01:00 >>>> > [INFO] Final Memory: 21M/420M >>>> > [INFO] >>>> > >>>> > ------------------------------------------------------------------------ >>>> > [ERROR] Failed to execute goal >>>> > org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test >>>> > (default-test) on >>>> > project unifiedpush-model-jpa: There are test failures. >>>> > [ERROR] >>>> > [ERROR] Please refer to >>>> > >>>> > C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports >>>> > for the individual test results. >>>> > [ERROR] -> [Help 1] >>>> > [ERROR] >>>> > [ERROR] To see the full stack trace of the errors, re-run Maven with >>>> > the -e >>>> > switch. >>>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>>> > [ERROR] >>>> > [ERROR] For more information about the errors and possible solutions, >>>> > please >>>> > read the following articles: >>>> > [ERROR] [Help 1] >>>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>>> > [ERROR] >>>> > [ERROR] After correcting the problems, you can resume the build with >>>> > the >>>> > command >>>> > [ERROR] mvn -rf :unifiedpush-model-jpa >>>> > >>>> > --------------------------------------------------------------------------------------------------------------------------------------------------------------- >>>> > Do you have any idea where is the problem and how to solve it? >>>> > Thanks >>>> > >>>> > Mgr. Ivan G?rtler >>>> > Mobile software developer >>>> > >>>> > AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> > 602 00 Brno (Czech Republic) >>>> > >>>> > www.ahead-itec.com | twitter | mobile security solutions >>>> > >>>> > 2015-04-23 8:55 GMT+02:00 Erik Jan de Wit : >>>> >> >>>> >> Hi Ivan, >>>> >> >>>> >> We have functionality for this available in the master branch on >>>> >> github. Go to /ag-push/rest/sys/info/health it will return >>>> >> json with the push network status and db status. This PR >>>> >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/519 >>>> >> includes details about the returned json. >>>> >> >>>> >> Hope this helps... >>>> >> >>>> >> --- >>>> >> Cheers, >>>> >> Erik Jan >>>> >> >>>> >> On Thu, Apr 23, 2015 at 8:39 AM, Ivan G?rtler >>>> >> wrote: >>>> >> > Hi, >>>> >> > I have some questions about server status. >>>> >> > Is possible to check with some kind of ping (or something else) >>>> >> > that DB >>>> >> > is >>>> >> > available from push server? >>>> >> > How to check if platform push server (APNS...) is also available? >>>> >> > >>>> >> > >>>> >> > Thanks >>>> >> > >>>> >> > Mgr. Ivan G?rtler >>>> >> > Mobile software developer >>>> >> > >>>> >> > AHEAD iTec, s.r.o., Botanick? 554/68a, >>>> >> > 602 00 Brno (Czech Republic) >>>> >> > >>>> >> > www.ahead-itec.com | twitter | mobile security solutions >>>> >> > >>>> >> > _______________________________________________ >>>> >> > aerogear-dev mailing list >>>> >> > aerogear-dev at lists.jboss.org >>>> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Cheers, >>>> >> Erik Jan >>>> >> >>>> >> _______________________________________________ >>>> >> aerogear-dev mailing list >>>> >> aerogear-dev at lists.jboss.org >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> > >>>> > >>>> > >>>> > _______________________________________________ >>>> > aerogear-dev mailing list >>>> > aerogear-dev at lists.jboss.org >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Erik Jan >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Cheers, Erik Jan From ivan.gurtler at ahead-itec.com Fri Apr 24 08:28:14 2015 From: ivan.gurtler at ahead-itec.com (=?UTF-8?Q?Ivan_G=C3=BCrtler?=) Date: Fri, 24 Apr 2015 14:28:14 +0200 Subject: [aerogear-dev] Unified Push - status In-Reply-To: References: Message-ID: Log on server ... 14:26:47,614 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "ag-push.war" (runtime-name: "ag-push.war") 14:26:50,337 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."ag-push.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ag-push.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "ag-push.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:625) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:278) at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:155) at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:82) at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:58) at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:81) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] ... 5 more 14:26:50,349 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 250) JBAS015870: Deploy of deployment "ag-push.war" was rolled back with the following failure message: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"ag-push.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ag-push.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"ag-push.war\" Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}} 14:26:50,373 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment ag-push.war (runtime-name: ag-push.war) in 23ms 14:26:50,374 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 250) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."ag-push.war".PARSE *Mgr. Ivan G?rtler* Mobile software developer AHEAD iTec, s.r.o., Botanick? 554/68a, 602 00 Brno (Czech Republic) www.ahead-itec.com | twitter | mobile security solutions 2015-04-24 13:49 GMT+02:00 Erik Jan de Wit : > Do you have some more logs, all you shared now is that it's not > deployed but not why. > > On Fri, Apr 24, 2015 at 1:21 PM, Ivan G?rtler > wrote: > > Hi, > > > > I tried mvn install without tests ... but deployment on EAP 6.3 server > ended > > with error... > > I tried to repair test DB (create_db_content.ddl) for my case ... mvn > > install was ok but deployment with error ... > > > > and same error was also in case when I made mvn install on master branch > and > > tried to deploy .... > > > > > > Failed to add Deployment ag-push.war > > > > Unexpected HTTP response: 500 > > > > Request > > { > > "operation" => "composite", > > "address" => [], > > "steps" => [ > > { > > "address" => [ > > ("server-group" => "main-server-group"), > > ("deployment" => "ag-push.war") > > ], > > "operation" => "add" > > }, > > { > > "address" => [ > > ("server-group" => "main-server-group"), > > ("deployment" => "ag-push.war") > > ], > > "operation" => "deploy" > > } > > ] > > } > > > > Response > > > > Internal Server Error > > { > > "outcome" => "failed", > > "result" => { > > "step-1" => {"outcome" => "success"}, > > "step-2" => {"outcome" => "success"} > > }, > > "failure-description" => "JBAS010839: Operation failed or was rolled > > back on all servers.", > > "rolled-back" => true, > > "server-groups" => {"main-server-group" => {"host" => {"master" => > > {"server-A" => {"response" => { > > "outcome" => "failed", > > "result" => { > > "step-1" => { > > "outcome" => "failed", > > "rolled-back" => true > > }, > > "step-2" => { > > "outcome" => "failed", > > "failure-description" => {"JBAS014671: Failed services" > => > > {"jboss.deployment.unit.\"ag-push.war\".PARSE" => > > "org.jboss.msc.service.StartException in service > > jboss.deployment.unit.\"ag-push.war\".PARSE: JBAS018733: Failed to > process > > phase PARSE of deployment \"ag-push.war\" > > Caused by: org.jboss.msc.service.ServiceNotFoundException: Service > > service jboss.ejb.default-resource-adapter-name-service not found"}}, > > "rolled-back" => true > > } > > }, > > "failure-description" => {"JBAS014653: Composite operation failed > > and was rolled back. Steps that failed:" => {"Operation step-2" => > > {"JBAS014671: Failed services" => > > {"jboss.deployment.unit.\"ag-push.war\".PARSE" => > > "org.jboss.msc.service.StartException in service > > jboss.deployment.unit.\"ag-push.war\".PARSE: JBAS018733: Failed to > process > > phase PARSE of deployment \"ag-push.war\" > > Caused by: org.jboss.msc.service.ServiceNotFoundException: Service > > service jboss.ejb.default-resource-adapter-name-service not found"}}}}, > > "rolled-back" => true > > }}}}}} > > } > > > > > > I dont know where the problem is now ... > > Thanks for your help ... > > > > > > Mgr. Ivan G?rtler > > Mobile software developer > > > > AHEAD iTec, s.r.o., Botanick? 554/68a, > > 602 00 Brno (Czech Republic) > > > > www.ahead-itec.com | twitter | mobile security solutions > > > > 2015-04-23 15:37 GMT+02:00 Ivan G?rtler : > >> > >> ... oh :D sorry ... > >> I found /model/jpa/testData/create_db_content.ddl ... I try it ... > >> > >> Mgr. Ivan G?rtler > >> Mobile software developer > >> > >> AHEAD iTec, s.r.o., Botanick? 554/68a, > >> 602 00 Brno (Czech Republic) > >> > >> www.ahead-itec.com | twitter | mobile security solutions > >> > >> 2015-04-23 15:30 GMT+02:00 Ivan G?rtler : > >>> > >>> In report file for PushApplicationDaoTest ... i found: > >>> > >>> ... > >>> javax.persistence.PersistenceException: > >>> org.hibernate.exception.DataException: could not initialize a > collection: > >>> [org.jboss.aerogear.unifiedpush.api.PushApplication.variants#1] > >>> at > org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown > >>> Source) > >>> at > >>> > org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown > >>> Source) > >>> at > >>> > org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown > >>> Source) > >>> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) > >>> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) > >>> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown > Source) > >>> at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown > >>> Source) > >>> at org.apache.derby.impl.jdbc.ConnectionChild.newSQLException(Unknown > >>> Source) > >>> at org.apache.derby.impl.jdbc.EmbedResultSet.dataTypeConversion(Unknown > >>> Source) > >>> at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) > >>> at org.apache.derby.impl.jdbc.EmbedResultSet.getClob(Unknown Source) > >>> at > >>> > org.hibernate.type.descriptor.sql.ClobTypeDescriptor$1.doExtract(ClobTypeDescriptor.java:60) > >>> at > >>> > org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:64) > >>> at > >>> > org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:265) > >>> at > >>> > org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:261) > >>> at > >>> > org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:251) > >>> at > >>> > org.hibernate.type.AbstractStandardBasicType.hydrate(AbstractStandardBasicType.java:336) > >>> at > >>> > org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2924) > >>> at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1695) > >>> at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1627) > >>> at org.hibernate.loader.Loader.getRow(Loader.java:1509) > >>> at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:719) > >>> at org.hibernate.loader.Loader.processResultSet(Loader.java:949) > >>> at org.hibernate.loader.Loader.doQuery(Loader.java:917) > >>> at > >>> > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:348) > >>> at > >>> > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:318) > >>> at org.hibernate.loader.Loader.loadCollection(Loader.java:2262) > >>> at > >>> > org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:65) > >>> at > >>> > org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:674) > >>> at > >>> > org.hibernate.event.internal.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:86) > >>> at > >>> > org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1774) > >>> at > >>> > org.hibernate.collection.internal.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:696) > >>> at > >>> > org.hibernate.engine.internal.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:1037) > >>> at > >>> > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:353) > >>> at org.hibernate.loader.Loader.doList(Loader.java:2550) > >>> at org.hibernate.loader.Loader.doList(Loader.java:2536) > >>> at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2366) > >>> at org.hibernate.loader.Loader.list(Loader.java:2361) > >>> at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:495) > >>> at > >>> > org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:357) > >>> at > >>> > org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:198) > >>> at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1194) > >>> at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101) > >>> at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:264) > >>> at > >>> > org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPABaseDao.getSingleResultForQuery(JPABaseDao.java:93) > >>> at > >>> > org.jboss.aerogear.unifiedpush.jpa.dao.impl.JPAPushApplicationDao.findByPushApplicationID(JPAPushApplicationDao.java:73) > >>> at > >>> > org.jboss.aerogear.unifiedpush.jpa.PushApplicationDaoTest.updatePushApplication(PushApplicationDaoTest.java:125) > >>> ... > >>> > >>> > >>> In aerogear:master version two mounth ago it was without problems. I > >>> found commit "Use JMS message queues for sending notifications in > batches > >>> AGPUSH-1348" ... in this commit was changed orm.xml file ... but I > dont know > >>> background of commit change. > >>> > >>> Mgr. Ivan G?rtler > >>> Mobile software developer > >>> > >>> AHEAD iTec, s.r.o., Botanick? 554/68a, > >>> 602 00 Brno (Czech Republic) > >>> > >>> www.ahead-itec.com | twitter | mobile security solutions > >>> > >>> 2015-04-23 15:05 GMT+02:00 Erik Jan de Wit : > >>>> > >>>> Hi Ivan, > >>>> > >>>> Try running without the test `mvn install -DskipTests`, because they > >>>> are testing against another schema. Or see why the tests fail in the > >>>> > >>>> > C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports > >>>> directory and fix those tests, by changing > >>>> model\jpa\test\create_db_content.ddl > >>>> > >>>> On Thu, Apr 23, 2015 at 2:58 PM, Ivan G?rtler > >>>> wrote: > >>>> > Hi, > >>>> > We have own fork ... and I sync with "aerogear:master". Master > branch > >>>> > in > >>>> > fork is OK. > >>>> > I merge master to second branch. We changed > >>>> > model/jpa/src/main/resources/META-INF/orm.xml file in second branch > >>>> > because > >>>> > we use ORACLE > >>>> > ... > >>>> > > >>>> > ios > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > ... > >>>> > (Second change in orm.xml file was because of Installation class, it > >>>> > was > >>>> > bigger than 4000 -> problem in ORACLE ... but in "aerogear:master" > it > >>>> > was > >>>> > removed from orm.xml file) > >>>> > but when ... Run as ... Maven insall ... In console: > >>>> > ... > >>>> > Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 2.366 > >>>> > sec > >>>> > Results : > >>>> > Failed tests: > >>>> > Expected exception: javax.persistence.PersistenceException > >>>> > Tests in error: > >>>> > PushApplicationDaoTest.updatePushApplication:125 ? Persistence > >>>> > org.hibernate.e... > >>>> > PushApplicationDaoTest.pushApplicationIDUnmodifiedAfterUpdate:159 > ? > >>>> > Persistence > >>>> > > >>>> > > >>>> > > PushApplicationDaoTest.deletePushApplicationIncludingVariantAndInstallations:194 > >>>> > ? Persistence > >>>> > PushApplicationDaoTest.findByPushApplicationID:116 ? Persistence > >>>> > org.hibernate... > >>>> > PushApplicationDaoTest.findAllForDeveloper:72 ? Persistence > >>>> > org.hibernate.exce... > >>>> > PushApplicationDaoTest.primaryKeyUnmodifiedAfterUpdate:174 ? > >>>> > Persistence > >>>> > org.h... > >>>> > PushApplicationDaoTest.findAllIDsForDeveloper:96 ? Persistence > >>>> > org.hibernate.e... > >>>> > PushApplicationDaoTest.findByPushApplicationIDForDeveloper:103 ? > >>>> > Persistence o... > >>>> > PushApplicationDaoTest.updateAndDeletePushApplication:140 ? > >>>> > Persistence > >>>> > org.hi... > >>>> > Tests run: 75, Failures: 1, Errors: 9, Skipped: 0 > >>>> > [INFO] > >>>> > > >>>> > > ------------------------------------------------------------------------ > >>>> > [INFO] Reactor Summary: > >>>> > [INFO] > >>>> > [INFO] AeroGear UnifiedPush Server ....................... SUCCESS [ > >>>> > 2.833 > >>>> > s] > >>>> > [INFO] UnifiedPush Model Layer ........................... SUCCESS [ > >>>> > 0.058 > >>>> > s] > >>>> > [INFO] UnifiedPush Server Model API ...................... SUCCESS [ > >>>> > 2.886 > >>>> > s] > >>>> > [INFO] UnifiedPush Server Model JPA implementation ....... FAILURE [ > >>>> > 32.992 > >>>> > s] > >>>> > [INFO] UnifiedPush Service Layer ......................... SKIPPED > >>>> > [INFO] UnifiedPush Sender Module ......................... SKIPPED > >>>> > [INFO] UnifiedPush Push Message Model .................... SKIPPED > >>>> > [INFO] UnifiedPush Push Notification Networks ............ SKIPPED > >>>> > [INFO] UnifiedPush RESTful Endpoint ...................... SKIPPED > >>>> > [INFO] UnifiedPush Server (Admin UI) ..................... SKIPPED > >>>> > [INFO] UnifiedPush Dependencies Parent ................... SKIPPED > >>>> > [INFO] UnifiedPush Server Dependencies Server ............ SKIPPED > >>>> > [INFO] UnifiedPush Auth Server ........................... SKIPPED > >>>> > [INFO] UnifiedPush Server for JBossAS (WAR) .............. SKIPPED > >>>> > [INFO] UnifiedPush Server for Wildfly (WAR) .............. SKIPPED > >>>> > [INFO] UnifiedPush Servers Parent ........................ SKIPPED > >>>> > [INFO] > >>>> > > >>>> > > ------------------------------------------------------------------------ > >>>> > [INFO] BUILD FAILURE > >>>> > [INFO] > >>>> > > >>>> > > ------------------------------------------------------------------------ > >>>> > [INFO] Total time: 40.717 s > >>>> > [INFO] Finished at: 2015-04-23T14:35:45+01:00 > >>>> > [INFO] Final Memory: 21M/420M > >>>> > [INFO] > >>>> > > >>>> > > ------------------------------------------------------------------------ > >>>> > [ERROR] Failed to execute goal > >>>> > org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test > >>>> > (default-test) on > >>>> > project unifiedpush-model-jpa: There are test failures. > >>>> > [ERROR] > >>>> > [ERROR] Please refer to > >>>> > > >>>> > > C:\Users\Ivan\Documents\aerogear-unifiedpush-server\model\jpa\target\surefire-reports > >>>> > for the individual test results. > >>>> > [ERROR] -> [Help 1] > >>>> > [ERROR] > >>>> > [ERROR] To see the full stack trace of the errors, re-run Maven with > >>>> > the -e > >>>> > switch. > >>>> > [ERROR] Re-run Maven using the -X switch to enable full debug > logging. > >>>> > [ERROR] > >>>> > [ERROR] For more information about the errors and possible > solutions, > >>>> > please > >>>> > read the following articles: > >>>> > [ERROR] [Help 1] > >>>> > > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > >>>> > [ERROR] > >>>> > [ERROR] After correcting the problems, you can resume the build with > >>>> > the > >>>> > command > >>>> > [ERROR] mvn -rf :unifiedpush-model-jpa > >>>> > > >>>> > > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > >>>> > Do you have any idea where is the problem and how to solve it? > >>>> > Thanks > >>>> > > >>>> > Mgr. Ivan G?rtler > >>>> > Mobile software developer > >>>> > > >>>> > AHEAD iTec, s.r.o., Botanick? 554/68a, > >>>> > 602 00 Brno (Czech Republic) > >>>> > > >>>> > www.ahead-itec.com | twitter | mobile security solutions > >>>> > > >>>> > 2015-04-23 8:55 GMT+02:00 Erik Jan de Wit : > >>>> >> > >>>> >> Hi Ivan, > >>>> >> > >>>> >> We have functionality for this available in the master branch on > >>>> >> github. Go to /ag-push/rest/sys/info/health it will return > >>>> >> json with the push network status and db status. This PR > >>>> >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/519 > >>>> >> includes details about the returned json. > >>>> >> > >>>> >> Hope this helps... > >>>> >> > >>>> >> --- > >>>> >> Cheers, > >>>> >> Erik Jan > >>>> >> > >>>> >> On Thu, Apr 23, 2015 at 8:39 AM, Ivan G?rtler > >>>> >> wrote: > >>>> >> > Hi, > >>>> >> > I have some questions about server status. > >>>> >> > Is possible to check with some kind of ping (or something else) > >>>> >> > that DB > >>>> >> > is > >>>> >> > available from push server? > >>>> >> > How to check if platform push server (APNS...) is also available? > >>>> >> > > >>>> >> > > >>>> >> > Thanks > >>>> >> > > >>>> >> > Mgr. Ivan G?rtler > >>>> >> > Mobile software developer > >>>> >> > > >>>> >> > AHEAD iTec, s.r.o., Botanick? 554/68a, > >>>> >> > 602 00 Brno (Czech Republic) > >>>> >> > > >>>> >> > www.ahead-itec.com | twitter | mobile security solutions > >>>> >> > > >>>> >> > _______________________________________________ > >>>> >> > aerogear-dev mailing list > >>>> >> > aerogear-dev at lists.jboss.org > >>>> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>> >> > >>>> >> > >>>> >> > >>>> >> -- > >>>> >> Cheers, > >>>> >> Erik Jan > >>>> >> > >>>> >> _______________________________________________ > >>>> >> aerogear-dev mailing list > >>>> >> aerogear-dev at lists.jboss.org > >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>> > > >>>> > > >>>> > > >>>> > _______________________________________________ > >>>> > aerogear-dev mailing list > >>>> > aerogear-dev at lists.jboss.org > >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>> > >>>> > >>>> > >>>> -- > >>>> Cheers, > >>>> Erik Jan > >>>> > >>>> _______________________________________________ > >>>> aerogear-dev mailing list > >>>> aerogear-dev at lists.jboss.org > >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>> > >>> > >> > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150424/1ddf7cfa/attachment-0001.html From lukas.fryc at gmail.com Fri Apr 24 10:39:16 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Fri, 24 Apr 2015 14:39:16 +0000 Subject: [aerogear-dev] UPS: UX Revamp for Alpha2 In-Reply-To: References: Message-ID: The UX Revamp branch has finally landed on master. We can tag UPS 1.0.0-alpha.2 at Monday then. ~ Lukas st 22. 4. 2015 v 22:50 odes?latel Luk?? Fry? napsal: > Hey guys, > > I've put together an initial version of UPS UX Revamp branch that can be > merged to master and released as part of 1.1.0-alpha-2. > > https://github.com/aerogear/aerogear-unifiedpush-server/pull/537 > > Feel free to test it! > > Cheers, > > ~ Lukas > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150424/0fb7305e/attachment.html From corinnekrych at gmail.com Fri Apr 24 14:38:49 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 24 Apr 2015 20:38:49 +0200 Subject: [aerogear-dev] iOS 2.3 release is out Message-ID: <91B59E49-05CF-46E8-802E-F81FC3E42A46@gmail.com> Hello iOS lovers, Our iOS 2.3 release is out! To learn more about, have a look to the announcement: https://aerogear.org/news/2015/04/24/aerogear-ios-2.3/index.html ++ Corinne From bromanv at gmail.com Tue Apr 21 10:55:54 2015 From: bromanv at gmail.com (bromanv) Date: Tue, 21 Apr 2015 07:55:54 -0700 (MST) Subject: [aerogear-dev] error 500 on send push Message-ID: <1429628154813-11465.post@n5.nabble.com> hi i fished to install the unifiedpush on openshift, after send the firsth push notification the admin console return internal error 500 how can view the log or more details about why can send an other test notification -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/error-500-on-send-push-tp11465.html Sent from the aerogear-dev mailing list archive at Nabble.com. From cvasilak at gmail.com Mon Apr 27 02:36:57 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 27 Apr 2015 09:36:57 +0300 Subject: [aerogear-dev] Team Meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-04.27.2015 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/279bd3f9/attachment.html From matzew at apache.org Mon Apr 27 03:45:44 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 27 Apr 2015 09:45:44 +0200 Subject: [aerogear-dev] UnifiedPush Server 1.1.0-alpha.2 Message-ID: Hi, after month of work, here is the second alpha release for the UPS 1.1.0. It contains an all new UI, JMS for enhanced scalability and a lot of other improvements: https://issues.jboss.org/browse/AGPUSH/fixforversion/12326455 Please test the staged release: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5398/ Since we now have JMS hooks, please make sure you use a full profile WildFly or EAP server for tests By Wednesday I'd like to press the button to release it to the wild. PS: Since this is an alhpa release we won't yet be updating our Openshift cartridge - that will stay on 1.0.3 (stable) for a little longer time. For the next release (beta.1) in a few weeks we may get to this Openshift update Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/29eadc88/attachment.html From dpassos at redhat.com Mon Apr 27 08:59:22 2015 From: dpassos at redhat.com (Daniel Passos) Date: Mon, 27 Apr 2015 09:59:22 -0300 Subject: [aerogear-dev] Remove old AGDroid GH repos Message-ID: Hey Guys, We've moved all our example apps[1], [2], [3] for the cookbook[4] and also split the old integration test project[5] into your respective modules. Should we remove the old repos? Wdyt? [1] https://github.com/aerogear/aerogear-aerodoc-android [2] https://github.com/aerogear/aerogear-otp-android-demo [3] https://github.com/aerogear/aerogear-crypto-android-demo [4] https://github.com/aerogear/aerogear-android-cookbook [5] https://github.com/aerogear/aerogear-android-integration-tests -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/e92868e3/attachment.html From matzew at apache.org Mon Apr 27 09:04:07 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 27 Apr 2015 15:04:07 +0200 Subject: [aerogear-dev] Remove old AGDroid GH repos In-Reply-To: References: Message-ID: +1 let's remove all of them! I am happy to do so, once we get agreement on this subject :-) On Mon, Apr 27, 2015 at 2:59 PM, Daniel Passos wrote: > Hey Guys, > > We've moved all our example apps[1], [2], [3] for the cookbook[4] and also > split the old integration test project[5] into your respective modules. > Should we remove the old repos? Wdyt? > > [1] https://github.com/aerogear/aerogear-aerodoc-android > [2] https://github.com/aerogear/aerogear-otp-android-demo > [3] https://github.com/aerogear/aerogear-crypto-android-demo > [4] https://github.com/aerogear/aerogear-android-cookbook > [5] https://github.com/aerogear/aerogear-android-integration-tests > > -- > -- Passos > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/e283ccd3/attachment.html From lukas.fryc at gmail.com Mon Apr 27 09:19:30 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Mon, 27 Apr 2015 15:19:30 +0200 Subject: [aerogear-dev] UnifiedPush Server 1.1.0-alpha.2 In-Reply-To: References: Message-ID: ad) Testing new UI: When testing, please bear in mind, that there are still lot of UI leftovers (such as wrong links). Some of them we already know of. The main functionality/paths should be available though: - creating apps - creating variants - sending push messages - reading activity log Andres and myself already put together a list items that needs to be fixed for Beta, but none of them are anyhow critical to have in Alpha release. Thanks, ~ Lukas On Mon, Apr 27, 2015 at 9:45 AM, Matthias Wessendorf wrote: > Hi, > > after month of work, here is the second alpha release for the UPS 1.1.0. > It contains an all new UI, JMS for enhanced scalability and a lot of other > improvements: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12326455 > > > Please test the staged release: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5398/ > > Since we now have JMS hooks, please make sure you use a full profile > WildFly or EAP server for tests > > By Wednesday I'd like to press the button to release it to the wild. > > PS: Since this is an alhpa release we won't yet be updating our Openshift > cartridge - that will stay on 1.0.3 (stable) for a little longer time. For > the next release (beta.1) in a few weeks we may get to this Openshift update > > Thanks, > Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/7e7f5646/attachment-0001.html From supittma at redhat.com Mon Apr 27 10:05:45 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 27 Apr 2015 10:05:45 -0400 Subject: [aerogear-dev] Remove old AGDroid GH repos In-Reply-To: References: Message-ID: Just as a note, 1,2,3,5 are the ones we want to remove. 4 is the cook book and should stay :) On Mon, Apr 27, 2015 at 9:04 AM, Matthias Wessendorf wrote: > +1 let's remove all of them! > > I am happy to do so, once we get agreement on this subject :-) > > On Mon, Apr 27, 2015 at 2:59 PM, Daniel Passos wrote: > >> Hey Guys, >> >> We've moved all our example apps[1], [2], [3] for the cookbook[4] and >> also split the old integration test project[5] into your respective >> modules. Should we remove the old repos? Wdyt? >> >> [1] https://github.com/aerogear/aerogear-aerodoc-android >> [2] https://github.com/aerogear/aerogear-otp-android-demo >> [3] https://github.com/aerogear/aerogear-crypto-android-demo >> [4] https://github.com/aerogear/aerogear-android-cookbook >> [5] https://github.com/aerogear/aerogear-android-integration-tests >> >> -- >> -- Passos >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/8a223d8f/attachment.html From cvasilak at gmail.com Mon Apr 27 10:13:26 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 27 Apr 2015 17:13:26 +0300 Subject: [aerogear-dev] Team Meeting In-Reply-To: References: Message-ID: fyi, meeting minutes: Meeting ended Mon Apr 27 14:11:30 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-27-14.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-27-14.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-04-27-14.00.log.html On Mon, Apr 27, 2015 at 9:36 AM, Christos Vasilakis wrote: > Agenda: > > http://oksoclap.com/p/aerogear-team-mgt-04.27.2015 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/7bcaa028/attachment.html From lholmqui at redhat.com Mon Apr 27 10:55:27 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Mon, 27 Apr 2015 10:55:27 -0400 Subject: [aerogear-dev] error 500 on send push In-Reply-To: <1429628154813-11465.post@n5.nabble.com> References: <1429628154813-11465.post@n5.nabble.com> Message-ID: I'm also seeing this on my instance running on OpenShift. running the 1.0.3 community version. On Tue, Apr 21, 2015 at 10:55 AM, bromanv wrote: > hi i fished to install the unifiedpush on openshift, after send the firsth > push notification > the admin console return internal error 500 how can view the log or more > details about why can send an other test notification > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/error-500-on-send-push-tp11465.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/1225ce8f/attachment.html From lholmqui at redhat.com Mon Apr 27 11:10:02 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Mon, 27 Apr 2015 11:10:02 -0400 Subject: [aerogear-dev] error 500 on send push In-Reply-To: References: <1429628154813-11465.post@n5.nabble.com> Message-ID: sorry last reply was a bit vague. So to get this working again, i had to do the command line thing "rhc force-stop-app -a app-name" then a "rhc start-app -a app-name" This is the first time since friday i had tried to do this, so perhaps something with the idle stuff that happens on OS On Mon, Apr 27, 2015 at 10:55 AM, Luke Holmquist wrote: > I'm also seeing this on my instance running on OpenShift. > > running the 1.0.3 community version. > > > > On Tue, Apr 21, 2015 at 10:55 AM, bromanv wrote: > >> hi i fished to install the unifiedpush on openshift, after send the firsth >> push notification >> the admin console return internal error 500 how can view the log or more >> details about why can send an other test notification >> >> >> >> -- >> View this message in context: >> http://aerogear-dev.1069024.n5.nabble.com/error-500-on-send-push-tp11465.html >> Sent from the aerogear-dev mailing list archive at Nabble.com. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/6b572812/attachment.html From cvasilak at gmail.com Mon Apr 27 11:22:11 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 27 Apr 2015 18:22:11 +0300 Subject: [aerogear-dev] UnifiedPush Server 1.1.0-alpha.2 In-Reply-To: References: Message-ID: registered Android/iOS variants and successfully sent/receive notifications with the activity log being updated accordingly. great work! +1 ? On Mon, Apr 27, 2015 at 4:19 PM, Luk?? Fry? wrote: > ad) Testing new UI: > > When testing, please bear in mind, that there are still lot of UI > leftovers (such as wrong links). Some of them we already know of. > > The main functionality/paths should be available though: > > - creating apps > - creating variants > - sending push messages > - reading activity log > > Andres and myself already put together a list items that needs to be fixed > for Beta, but none of them are anyhow critical to have in Alpha release. > > > Thanks, > > ~ Lukas > > On Mon, Apr 27, 2015 at 9:45 AM, Matthias Wessendorf > wrote: > >> Hi, >> >> after month of work, here is the second alpha release for the UPS 1.1.0. >> It contains an all new UI, JMS for enhanced scalability and a lot of other >> improvements: >> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326455 >> >> >> Please test the staged release: >> >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5398/ >> >> Since we now have JMS hooks, please make sure you use a full profile >> WildFly or EAP server for tests >> >> By Wednesday I'd like to press the button to release it to the wild. >> >> PS: Since this is an alhpa release we won't yet be updating our Openshift >> cartridge - that will stay on 1.0.3 (stable) for a little longer time. For >> the next release (beta.1) in a few weeks we may get to this Openshift update >> >> Thanks, >> Matthias >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/cafa9f6a/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: UPS-alpha.2.png Type: image/png Size: 167968 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/cafa9f6a/attachment-0001.png From matzew at apache.org Mon Apr 27 11:22:26 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 27 Apr 2015 17:22:26 +0200 Subject: [aerogear-dev] error 500 on send push In-Reply-To: References: <1429628154813-11465.post@n5.nabble.com> Message-ID: any details from the log ? On Mon, Apr 27, 2015 at 5:10 PM, Luke Holmquist wrote: > sorry last reply was a bit vague. > > So to get this working again, i had to do the command line thing "rhc > force-stop-app -a app-name" > > then a "rhc start-app -a app-name" > > This is the first time since friday i had tried to do this, so perhaps > something with the idle stuff that happens on OS > > On Mon, Apr 27, 2015 at 10:55 AM, Luke Holmquist > wrote: > >> I'm also seeing this on my instance running on OpenShift. >> >> running the 1.0.3 community version. >> >> >> >> On Tue, Apr 21, 2015 at 10:55 AM, bromanv wrote: >> >>> hi i fished to install the unifiedpush on openshift, after send the >>> firsth >>> push notification >>> the admin console return internal error 500 how can view the log or more >>> details about why can send an other test notification >>> >>> >>> >>> -- >>> View this message in context: >>> http://aerogear-dev.1069024.n5.nabble.com/error-500-on-send-push-tp11465.html >>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/e035497a/attachment.html From lholmqui at redhat.com Mon Apr 27 11:23:51 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Mon, 27 Apr 2015 11:23:51 -0400 Subject: [aerogear-dev] error 500 on send push In-Reply-To: References: <1429628154813-11465.post@n5.nabble.com> Message-ID: that would've been smart of me to check that too. let me see if i can find some On Mon, Apr 27, 2015 at 11:22 AM, Matthias Wessendorf wrote: > any details from the log ? > > On Mon, Apr 27, 2015 at 5:10 PM, Luke Holmquist > wrote: > >> sorry last reply was a bit vague. >> >> So to get this working again, i had to do the command line thing "rhc >> force-stop-app -a app-name" >> >> then a "rhc start-app -a app-name" >> >> This is the first time since friday i had tried to do this, so perhaps >> something with the idle stuff that happens on OS >> >> On Mon, Apr 27, 2015 at 10:55 AM, Luke Holmquist >> wrote: >> >>> I'm also seeing this on my instance running on OpenShift. >>> >>> running the 1.0.3 community version. >>> >>> >>> >>> On Tue, Apr 21, 2015 at 10:55 AM, bromanv wrote: >>> >>>> hi i fished to install the unifiedpush on openshift, after send the >>>> firsth >>>> push notification >>>> the admin console return internal error 500 how can view the log or more >>>> details about why can send an other test notification >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://aerogear-dev.1069024.n5.nabble.com/error-500-on-send-push-tp11465.html >>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150427/2af10bad/attachment.html From bruno at abstractj.org Mon Apr 27 13:22:25 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 27 Apr 2015 14:22:25 -0300 Subject: [aerogear-dev] Remove old AGDroid GH repos In-Reply-To: References: Message-ID: <20150427172225.GA9806@abstractj.org> Go ahead +1 On 2015-04-27, Summers Pittman wrote: > Just as a note, 1,2,3,5 are the ones we want to remove. 4 is the cook book > and should stay :) > > On Mon, Apr 27, 2015 at 9:04 AM, Matthias Wessendorf > wrote: > > > +1 let's remove all of them! > > > > I am happy to do so, once we get agreement on this subject :-) > > > > On Mon, Apr 27, 2015 at 2:59 PM, Daniel Passos wrote: > > > >> Hey Guys, > >> > >> We've moved all our example apps[1], [2], [3] for the cookbook[4] and > >> also split the old integration test project[5] into your respective > >> modules. Should we remove the old repos? Wdyt? > >> > >> [1] https://github.com/aerogear/aerogear-aerodoc-android > >> [2] https://github.com/aerogear/aerogear-otp-android-demo > >> [3] https://github.com/aerogear/aerogear-crypto-android-demo > >> [4] https://github.com/aerogear/aerogear-android-cookbook > >> [5] https://github.com/aerogear/aerogear-android-integration-tests > >> > >> -- > >> -- Passos > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at 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 > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj PGP: 0x84DC9914 From scm.blanc at gmail.com Tue Apr 28 02:04:29 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Tue, 28 Apr 2015 08:04:29 +0200 Subject: [aerogear-dev] Remove old AGDroid GH repos In-Reply-To: References: Message-ID: <996D809A-272E-4752-A384-6BAEB18FD7AE@gmail.com> +1 Envoy? de mon iPhone > Le 27 avr. 2015 ? 14:59, Daniel Passos a ?crit : > > Hey Guys, > > We've moved all our example apps[1], [2], [3] for the cookbook[4] and also split the old integration test project[5] into your respective modules. Should we remove the old repos? Wdyt? > > [1] https://github.com/aerogear/aerogear-aerodoc-android > [2] https://github.com/aerogear/aerogear-otp-android-demo > [3] https://github.com/aerogear/aerogear-crypto-android-demo > [4] https://github.com/aerogear/aerogear-android-cookbook > [5] https://github.com/aerogear/aerogear-android-integration-tests > > -- > -- Passos > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/ade672ae/attachment.html From lukas.fryc at gmail.com Tue Apr 28 03:45:02 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 28 Apr 2015 07:45:02 +0000 Subject: [aerogear-dev] UnifiedPush Server 1.1.0-alpha.2 In-Reply-To: References: Message-ID: I have tested with EAP 6.4 and MySQL, and successfully sent message to Android emulator. During that testing I've found one issue, that should not IMO block the release: https://issues.jboss.org/browse/AGPUSH-1375 I'm +1 po 27. 4. 2015 v 17:22 odes?latel Christos Vasilakis napsal: > registered Android/iOS variants and successfully sent/receive > notifications with the activity log being updated accordingly. > > great work! > > +1 > > > ? > > On Mon, Apr 27, 2015 at 4:19 PM, Luk?? Fry? wrote: > >> ad) Testing new UI: >> >> When testing, please bear in mind, that there are still lot of UI >> leftovers (such as wrong links). Some of them we already know of. >> >> The main functionality/paths should be available though: >> >> - creating apps >> - creating variants >> - sending push messages >> - reading activity log >> >> Andres and myself already put together a list items that needs to be >> fixed for Beta, but none of them are anyhow critical to have in Alpha >> release. >> >> >> Thanks, >> >> ~ Lukas >> >> On Mon, Apr 27, 2015 at 9:45 AM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> after month of work, here is the second alpha release for the UPS 1.1.0. >>> It contains an all new UI, JMS for enhanced scalability and a lot of other >>> improvements: >>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12326455 >>> >>> >>> Please test the staged release: >>> >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-5398/ >>> >>> Since we now have JMS hooks, please make sure you use a full profile >>> WildFly or EAP server for tests >>> >>> By Wednesday I'd like to press the button to release it to the wild. >>> >>> PS: Since this is an alhpa release we won't yet be updating our >>> Openshift cartridge - that will stay on 1.0.3 (stable) for a little longer >>> time. For the next release (beta.1) in a few weeks we may get to this >>> Openshift update >>> >>> Thanks, >>> Matthias >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/4167a3ad/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: UPS-alpha.2.png Type: image/png Size: 167968 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/4167a3ad/attachment-0001.png From artur.dryomov at gmail.com Tue Apr 28 03:29:20 2015 From: artur.dryomov at gmail.com (Artur Dryomov) Date: Tue, 28 Apr 2015 10:29:20 +0300 Subject: [aerogear-dev] [GSoC] Hawkular Android Client Message-ID: Hi everyone, This year I will be working on the Hawkular Android client application as part of the Google Summer of Code 2015 program. The application itself will use Hawkular API and AeroGear SDK. In coming days I?ll research these areas, especially documentation, and will try to create some sort of architecture and basic design. Thank you all for this opportunity! Artur. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/fd028bba/attachment.html From matzew at apache.org Tue Apr 28 07:13:56 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 28 Apr 2015 13:13:56 +0200 Subject: [aerogear-dev] [GSoC] Hawkular Android Client In-Reply-To: References: Message-ID: Hello Artur! welcome to our community/communities and congratulations on getting a seat at the GSoC program! We are looking forward to your contributions to our mailing lists and code repos :-) Good luck! On Tue, Apr 28, 2015 at 9:29 AM, Artur Dryomov wrote: > Hi everyone, > > This year I will be working on the Hawkular Android client application as > part of the Google Summer of Code 2015 program. > > The application itself will use Hawkular API and AeroGear SDK. In coming > days I?ll research these areas, especially documentation, and will try to > create some sort of architecture and basic design. > > Thank you all for this opportunity! > Artur. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/aad77144/attachment.html From edewit at redhat.com Tue Apr 28 07:50:46 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 28 Apr 2015 13:50:46 +0200 Subject: [aerogear-dev] cordova otp release Message-ID: Hi, We are glad to announce that the cordova otp plugin 0.0.2 has been released: Bug [AGCORDOVA-89] - Remove Podfile workaround [AGCORDOVA-90] - incorrect dependency on cordova otp plugin Feature Request [AGCORDOVA-60] - Add windows support for otp -- Cheers, Erik Jan From scm.blanc at gmail.com Tue Apr 28 08:21:03 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 28 Apr 2015 14:21:03 +0200 Subject: [aerogear-dev] cordova otp release In-Reply-To: References: Message-ID: Nice ! On Tue, Apr 28, 2015 at 1:50 PM, Erik Jan de Wit wrote: > Hi, > > We are glad to announce that the cordova otp plugin 0.0.2 has been > released: > > Bug > > [AGCORDOVA-89] - Remove Podfile workaround > [AGCORDOVA-90] - incorrect dependency on cordova otp plugin > > Feature Request > > [AGCORDOVA-60] - Add windows support for otp > > > -- > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/8bcd88a9/attachment.html From jbalunas at redhat.com Tue Apr 28 08:41:54 2015 From: jbalunas at redhat.com (Jay Balunas) Date: Tue, 28 Apr 2015 08:41:54 -0400 Subject: [aerogear-dev] [GSoC] Hawkular Android Client In-Reply-To: References: Message-ID: +1, Great to have you and can't wait to see your contributions and ideas! On Tue, Apr 28, 2015 at 7:13 AM, Matthias Wessendorf wrote: > Hello Artur! > > welcome to our community/communities and congratulations on getting a seat > at the GSoC program! > > We are looking forward to your contributions to our mailing lists and code > repos :-) > > Good luck! > > On Tue, Apr 28, 2015 at 9:29 AM, Artur Dryomov > wrote: > >> Hi everyone, >> >> This year I will be working on the Hawkular Android client application as >> part of the Google Summer of Code 2015 program. >> >> The application itself will use Hawkular API and AeroGear SDK. In coming >> days I?ll research these areas, especially documentation, and will try to >> create some sort of architecture and basic design. >> >> Thank you all for this opportunity! >> Artur. >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/74ef7fe4/attachment.html From supittma at redhat.com Tue Apr 28 09:27:49 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 28 Apr 2015 09:27:49 -0400 Subject: [aerogear-dev] [GSoC] Hawkular Android Client In-Reply-To: References: Message-ID: Hi, Arur and welcome. Look for me (summersp) and passos (passos) in IRC. We are the two main Android developers. Abstractj and qmx tend to help out a lot too. Summers On Tue, Apr 28, 2015 at 8:41 AM, Jay Balunas wrote: > +1, Great to have you and can't wait to see your contributions and ideas! > > > On Tue, Apr 28, 2015 at 7:13 AM, Matthias Wessendorf > wrote: > >> Hello Artur! >> >> welcome to our community/communities and congratulations on getting a >> seat at the GSoC program! >> >> We are looking forward to your contributions to our mailing lists and >> code repos :-) >> >> Good luck! >> >> On Tue, Apr 28, 2015 at 9:29 AM, Artur Dryomov >> wrote: >> >>> Hi everyone, >>> >>> This year I will be working on the Hawkular Android client application >>> as part of the Google Summer of Code 2015 program. >>> >>> The application itself will use Hawkular API and AeroGear SDK. In coming >>> days I?ll research these areas, especially documentation, and will try to >>> create some sort of architecture and basic design. >>> >>> Thank you all for this opportunity! >>> Artur. >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/a290435b/attachment.html From lholmqui at redhat.com Tue Apr 28 11:19:18 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 28 Apr 2015 11:19:18 -0400 Subject: [aerogear-dev] error 500 on send push In-Reply-To: References: <1429628154813-11465.post@n5.nabble.com> Message-ID: so i'm encountering this again, but this time when actually trying to access the admin console itself, log from yesterday https://gist.github.com/lholmquist/fac38776dd1c41ac01af Looks like it is running out of memory after a period of time. On Mon, Apr 27, 2015 at 11:23 AM, Luke Holmquist wrote: > that would've been smart of me to check that too. > > let me see if i can find some > > On Mon, Apr 27, 2015 at 11:22 AM, Matthias Wessendorf > wrote: > >> any details from the log ? >> >> On Mon, Apr 27, 2015 at 5:10 PM, Luke Holmquist >> wrote: >> >>> sorry last reply was a bit vague. >>> >>> So to get this working again, i had to do the command line thing "rhc >>> force-stop-app -a app-name" >>> >>> then a "rhc start-app -a app-name" >>> >>> This is the first time since friday i had tried to do this, so perhaps >>> something with the idle stuff that happens on OS >>> >>> On Mon, Apr 27, 2015 at 10:55 AM, Luke Holmquist >>> wrote: >>> >>>> I'm also seeing this on my instance running on OpenShift. >>>> >>>> running the 1.0.3 community version. >>>> >>>> >>>> >>>> On Tue, Apr 21, 2015 at 10:55 AM, bromanv wrote: >>>> >>>>> hi i fished to install the unifiedpush on openshift, after send the >>>>> firsth >>>>> push notification >>>>> the admin console return internal error 500 how can view the log or >>>>> more >>>>> details about why can send an other test notification >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://aerogear-dev.1069024.n5.nabble.com/error-500-on-send-push-tp11465.html >>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/21f3126e/attachment-0001.html From matzew at apache.org Tue Apr 28 11:37:34 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 28 Apr 2015 17:37:34 +0200 Subject: [aerogear-dev] error 500 on send push In-Reply-To: References: <1429628154813-11465.post@n5.nabble.com> Message-ID: what did you do to cause that ? On Tue, Apr 28, 2015 at 5:19 PM, Luke Holmquist wrote: > so i'm encountering this again, but this time when actually trying to > access the admin console itself, > > log from yesterday > > https://gist.github.com/lholmquist/fac38776dd1c41ac01af > > > Looks like it is running out of memory after a period of time. > > On Mon, Apr 27, 2015 at 11:23 AM, Luke Holmquist > wrote: > >> that would've been smart of me to check that too. >> >> let me see if i can find some >> >> On Mon, Apr 27, 2015 at 11:22 AM, Matthias Wessendorf >> wrote: >> >>> any details from the log ? >>> >>> On Mon, Apr 27, 2015 at 5:10 PM, Luke Holmquist >>> wrote: >>> >>>> sorry last reply was a bit vague. >>>> >>>> So to get this working again, i had to do the command line thing "rhc >>>> force-stop-app -a app-name" >>>> >>>> then a "rhc start-app -a app-name" >>>> >>>> This is the first time since friday i had tried to do this, so perhaps >>>> something with the idle stuff that happens on OS >>>> >>>> On Mon, Apr 27, 2015 at 10:55 AM, Luke Holmquist >>>> wrote: >>>> >>>>> I'm also seeing this on my instance running on OpenShift. >>>>> >>>>> running the 1.0.3 community version. >>>>> >>>>> >>>>> >>>>> On Tue, Apr 21, 2015 at 10:55 AM, bromanv wrote: >>>>> >>>>>> hi i fished to install the unifiedpush on openshift, after send the >>>>>> firsth >>>>>> push notification >>>>>> the admin console return internal error 500 how can view the log or >>>>>> more >>>>>> details about why can send an other test notification >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://aerogear-dev.1069024.n5.nabble.com/error-500-on-send-push-tp11465.html >>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/ed65f9da/attachment.html From lholmqui at redhat.com Tue Apr 28 11:40:45 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 28 Apr 2015 11:40:45 -0400 Subject: [aerogear-dev] error 500 on send push In-Reply-To: References: <1429628154813-11465.post@n5.nabble.com> Message-ID: was idle for like 12 hours. sent some push notifications a little earlier in the day, but i only have 2 installations On Tue, Apr 28, 2015 at 11:37 AM, Matthias Wessendorf wrote: > what did you do to cause that ? > > On Tue, Apr 28, 2015 at 5:19 PM, Luke Holmquist > wrote: > >> so i'm encountering this again, but this time when actually trying to >> access the admin console itself, >> >> log from yesterday >> >> https://gist.github.com/lholmquist/fac38776dd1c41ac01af >> >> >> Looks like it is running out of memory after a period of time. >> >> On Mon, Apr 27, 2015 at 11:23 AM, Luke Holmquist >> wrote: >> >>> that would've been smart of me to check that too. >>> >>> let me see if i can find some >>> >>> On Mon, Apr 27, 2015 at 11:22 AM, Matthias Wessendorf >> > wrote: >>> >>>> any details from the log ? >>>> >>>> On Mon, Apr 27, 2015 at 5:10 PM, Luke Holmquist >>>> wrote: >>>> >>>>> sorry last reply was a bit vague. >>>>> >>>>> So to get this working again, i had to do the command line thing "rhc >>>>> force-stop-app -a app-name" >>>>> >>>>> then a "rhc start-app -a app-name" >>>>> >>>>> This is the first time since friday i had tried to do this, so perhaps >>>>> something with the idle stuff that happens on OS >>>>> >>>>> On Mon, Apr 27, 2015 at 10:55 AM, Luke Holmquist >>>>> wrote: >>>>> >>>>>> I'm also seeing this on my instance running on OpenShift. >>>>>> >>>>>> running the 1.0.3 community version. >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Apr 21, 2015 at 10:55 AM, bromanv wrote: >>>>>> >>>>>>> hi i fished to install the unifiedpush on openshift, after send the >>>>>>> firsth >>>>>>> push notification >>>>>>> the admin console return internal error 500 how can view the log or >>>>>>> more >>>>>>> details about why can send an other test notification >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> View this message in context: >>>>>>> http://aerogear-dev.1069024.n5.nabble.com/error-500-on-send-push-tp11465.html >>>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/a6a9df77/attachment.html From matzew at apache.org Tue Apr 28 11:42:22 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 28 Apr 2015 17:42:22 +0200 Subject: [aerogear-dev] error 500 on send push In-Reply-To: References: <1429628154813-11465.post@n5.nabble.com> Message-ID: lol tjat's odd :) On Tue, Apr 28, 2015 at 5:40 PM, Luke Holmquist wrote: > was idle for like 12 hours. sent some push notifications a little > earlier in the day, but i only have 2 installations > > On Tue, Apr 28, 2015 at 11:37 AM, Matthias Wessendorf > wrote: > >> what did you do to cause that ? >> >> On Tue, Apr 28, 2015 at 5:19 PM, Luke Holmquist >> wrote: >> >>> so i'm encountering this again, but this time when actually trying to >>> access the admin console itself, >>> >>> log from yesterday >>> >>> https://gist.github.com/lholmquist/fac38776dd1c41ac01af >>> >>> >>> Looks like it is running out of memory after a period of time. >>> >>> On Mon, Apr 27, 2015 at 11:23 AM, Luke Holmquist >>> wrote: >>> >>>> that would've been smart of me to check that too. >>>> >>>> let me see if i can find some >>>> >>>> On Mon, Apr 27, 2015 at 11:22 AM, Matthias Wessendorf < >>>> matzew at apache.org> wrote: >>>> >>>>> any details from the log ? >>>>> >>>>> On Mon, Apr 27, 2015 at 5:10 PM, Luke Holmquist >>>>> wrote: >>>>> >>>>>> sorry last reply was a bit vague. >>>>>> >>>>>> So to get this working again, i had to do the command line thing "rhc >>>>>> force-stop-app -a app-name" >>>>>> >>>>>> then a "rhc start-app -a app-name" >>>>>> >>>>>> This is the first time since friday i had tried to do this, so >>>>>> perhaps something with the idle stuff that happens on OS >>>>>> >>>>>> On Mon, Apr 27, 2015 at 10:55 AM, Luke Holmquist >>>>> > wrote: >>>>>> >>>>>>> I'm also seeing this on my instance running on OpenShift. >>>>>>> >>>>>>> running the 1.0.3 community version. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Apr 21, 2015 at 10:55 AM, bromanv wrote: >>>>>>> >>>>>>>> hi i fished to install the unifiedpush on openshift, after send the >>>>>>>> firsth >>>>>>>> push notification >>>>>>>> the admin console return internal error 500 how can view the log or >>>>>>>> more >>>>>>>> details about why can send an other test notification >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> View this message in context: >>>>>>>> http://aerogear-dev.1069024.n5.nabble.com/error-500-on-send-push-tp11465.html >>>>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/32186156/attachment-0001.html From agalante at redhat.com Tue Apr 28 22:14:06 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 28 Apr 2015 22:14:06 -0400 Subject: [aerogear-dev] [GSoC] Hawkular Android Client In-Reply-To: References: Message-ID: And if you are looking for design help you can ping Gabriel gcardoso at redhat.com he is the UX dedicated to Hawkular and a great designer. On Tue, Apr 28, 2015 at 9:27 AM, Summers Pittman wrote: > Hi, Arur and welcome. > > Look for me (summersp) and passos (passos) in IRC. We are the two main > Android developers. Abstractj and qmx tend to help out a lot too. > > Summers > > On Tue, Apr 28, 2015 at 8:41 AM, Jay Balunas wrote: > >> +1, Great to have you and can't wait to see your contributions and ideas! >> >> >> On Tue, Apr 28, 2015 at 7:13 AM, Matthias Wessendorf >> wrote: >> >>> Hello Artur! >>> >>> welcome to our community/communities and congratulations on getting a >>> seat at the GSoC program! >>> >>> We are looking forward to your contributions to our mailing lists and >>> code repos :-) >>> >>> Good luck! >>> >>> On Tue, Apr 28, 2015 at 9:29 AM, Artur Dryomov >>> wrote: >>> >>>> Hi everyone, >>>> >>>> This year I will be working on the Hawkular Android client application >>>> as part of the Google Summer of Code 2015 program. >>>> >>>> The application itself will use Hawkular API and AeroGear SDK. In >>>> coming days I?ll research these areas, especially documentation, and will >>>> try to create some sort of architecture and basic design. >>>> >>>> Thank you all for this opportunity! >>>> Artur. >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150428/d895f97c/attachment.html From lukas.fryc at gmail.com Wed Apr 29 02:48:26 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 29 Apr 2015 06:48:26 +0000 Subject: [aerogear-dev] WildFly-Swarm for building UPS appliance dist? Message-ID: Morning guys, I came across WildFly-Swarm, seems it could be a simplification how to build appliance distribution from UPS war, isn't it? https://github.com/wildfly-swarm/wildfly-swarm Cheers, ~ Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/a9d1a710/attachment.html From matzew at apache.org Wed Apr 29 02:57:01 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 29 Apr 2015 08:57:01 +0200 Subject: [aerogear-dev] [GSoC] Hawkular Android Client In-Reply-To: References: Message-ID: On Wed, Apr 29, 2015 at 4:14 AM, Andres Galante wrote: > And if you are looking for design help you can ping Gabriel > gcardoso at redhat.com he is the UX dedicated to Hawkular and a great > designer. > let's not reach out directly - mailing list is the key channel ;-) > > On Tue, Apr 28, 2015 at 9:27 AM, Summers Pittman > wrote: > >> Hi, Arur and welcome. >> >> Look for me (summersp) and passos (passos) in IRC. We are the two main >> Android developers. Abstractj and qmx tend to help out a lot too. >> >> Summers >> >> On Tue, Apr 28, 2015 at 8:41 AM, Jay Balunas wrote: >> >>> +1, Great to have you and can't wait to see your contributions and ideas! >>> >>> >>> On Tue, Apr 28, 2015 at 7:13 AM, Matthias Wessendorf >>> wrote: >>> >>>> Hello Artur! >>>> >>>> welcome to our community/communities and congratulations on getting a >>>> seat at the GSoC program! >>>> >>>> We are looking forward to your contributions to our mailing lists and >>>> code repos :-) >>>> >>>> Good luck! >>>> >>>> On Tue, Apr 28, 2015 at 9:29 AM, Artur Dryomov >>> > wrote: >>>> >>>>> Hi everyone, >>>>> >>>>> This year I will be working on the Hawkular Android client application >>>>> as part of the Google Summer of Code 2015 program. >>>>> >>>>> The application itself will use Hawkular API and AeroGear SDK. In >>>>> coming days I?ll research these areas, especially documentation, and will >>>>> try to create some sort of architecture and basic design. >>>>> >>>>> Thank you all for this opportunity! >>>>> Artur. >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/fc14495d/attachment.html From edewit at redhat.com Wed Apr 29 03:21:08 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 29 Apr 2015 09:21:08 +0200 Subject: [aerogear-dev] WildFly-Swarm for building UPS appliance dist? In-Reply-To: References: Message-ID: That would build a executable jar file containing everything, but we would still need to setup a database right? On Wed, Apr 29, 2015 at 8:48 AM, Luk?? Fry? wrote: > Morning guys, > > I came across WildFly-Swarm, seems it could be a simplification how to build > appliance distribution from UPS war, isn't it? > > https://github.com/wildfly-swarm/wildfly-swarm > > Cheers, > > ~ Lukas > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Cheers, Erik Jan From lukas.fryc at gmail.com Wed Apr 29 03:39:12 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 29 Apr 2015 07:39:12 +0000 Subject: [aerogear-dev] WildFly-Swarm for building UPS appliance dist? In-Reply-To: References: Message-ID: That's right, but we can always set it up in Main method by using client API and database connector. Or improve Swarm to provide this functionality/hooks. st 29. 4. 2015 v 9:21 odes?latel Erik Jan de Wit napsal: > That would build a executable jar file containing everything, but we > would still need to setup a database right? > > On Wed, Apr 29, 2015 at 8:48 AM, Luk?? Fry? wrote: > > Morning guys, > > > > I came across WildFly-Swarm, seems it could be a simplification how to > build > > appliance distribution from UPS war, isn't it? > > > > https://github.com/wildfly-swarm/wildfly-swarm > > > > Cheers, > > > > ~ Lukas > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/4e7c7af5/attachment-0001.html From matzew at apache.org Wed Apr 29 06:18:18 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 29 Apr 2015 12:18:18 +0200 Subject: [aerogear-dev] WildFly-Swarm for building UPS appliance dist? In-Reply-To: References: Message-ID: yeah, I saw that and indded it is interesting. However not sure in EAP related impacts On Wednesday, April 29, 2015, Erik Jan de Wit wrote: > That would build a executable jar file containing everything, but we > would still need to setup a database right? > > On Wed, Apr 29, 2015 at 8:48 AM, Luk?? Fry? > wrote: > > Morning guys, > > > > I came across WildFly-Swarm, seems it could be a simplification how to > build > > appliance distribution from UPS war, isn't it? > > > > https://github.com/wildfly-swarm/wildfly-swarm > > > > Cheers, > > > > ~ Lukas > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/aa2c6d24/attachment.html From ken at kenfinnigan.me Wed Apr 29 06:19:29 2015 From: ken at kenfinnigan.me (Ken Finnigan) Date: Wed, 29 Apr 2015 06:19:29 -0400 Subject: [aerogear-dev] WildFly-Swarm for building UPS appliance dist? In-Reply-To: References: Message-ID: Bob and I would welcome any additional ways to improve WildFly Swarm! Bob's been working on the datasource connector only this week, and I think we're also looking at defaulting to H2 setup if an application doesn't provide details of a datasource. There isn't currently a mailing list for the project, but by all means open github issues to discuss items. Ken On Wed, Apr 29, 2015 at 3:39 AM, Luk?? Fry? wrote: > That's right, but we can always set it up in Main method by using client > API and database connector. > > Or improve Swarm to provide this functionality/hooks. > > st 29. 4. 2015 v 9:21 odes?latel Erik Jan de Wit > napsal: > > That would build a executable jar file containing everything, but we >> would still need to setup a database right? >> >> On Wed, Apr 29, 2015 at 8:48 AM, Luk?? Fry? wrote: >> > Morning guys, >> > >> > I came across WildFly-Swarm, seems it could be a simplification how to >> build >> > appliance distribution from UPS war, isn't it? >> > >> > https://github.com/wildfly-swarm/wildfly-swarm >> > >> > Cheers, >> > >> > ~ Lukas >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/76778178/attachment.html From ken at kenfinnigan.me Wed Apr 29 06:20:44 2015 From: ken at kenfinnigan.me (Ken Finnigan) Date: Wed, 29 Apr 2015 06:20:44 -0400 Subject: [aerogear-dev] WildFly-Swarm for building UPS appliance dist? In-Reply-To: References: Message-ID: Matthias, Currently the changes required to make WildFly work in this way are part of WildFly Core and WildFly 9. It might be possible to backport those changes to WildFly 8/EAP, but it's not something we've currently investigated Ken On Wed, Apr 29, 2015 at 6:19 AM, Ken Finnigan wrote: > Bob and I would welcome any additional ways to improve WildFly Swarm! > > Bob's been working on the datasource connector only this week, and I think > we're also looking at defaulting to H2 setup if an application doesn't > provide details of a datasource. > > There isn't currently a mailing list for the project, but by all means > open github issues to discuss items. > > Ken > > On Wed, Apr 29, 2015 at 3:39 AM, Luk?? Fry? wrote: > >> That's right, but we can always set it up in Main method by using client >> API and database connector. >> >> Or improve Swarm to provide this functionality/hooks. >> >> st 29. 4. 2015 v 9:21 odes?latel Erik Jan de Wit >> napsal: >> >> That would build a executable jar file containing everything, but we >>> would still need to setup a database right? >>> >>> On Wed, Apr 29, 2015 at 8:48 AM, Luk?? Fry? >>> wrote: >>> > Morning guys, >>> > >>> > I came across WildFly-Swarm, seems it could be a simplification how to >>> build >>> > appliance distribution from UPS war, isn't it? >>> > >>> > https://github.com/wildfly-swarm/wildfly-swarm >>> > >>> > Cheers, >>> > >>> > ~ Lukas >>> > >>> > _______________________________________________ >>> > aerogear-dev mailing list >>> > aerogear-dev at lists.jboss.org >>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> -- >>> Cheers, >>> Erik Jan >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/e077730a/attachment.html From idel.pivnitskiy at gmail.com Wed Apr 29 11:44:04 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Wed, 29 Apr 2015 18:44:04 +0300 Subject: [aerogear-dev] [jboss-gsoc] [GSoC 2015] WebPush support for mobile cloud services Message-ID: Hi all! I'm Idel Pivnitskiy and I'm a final year undergraduate student from National Research Nuclear University MEPhI at Moscow, but I don't work with nuclear physics :) I learn Computer Science at Cybernetic and Information Security department. On my work we use JBoss technologies and build your applications and services on WildFly or JBoss AS with Hibernate, RESTEasy, RichFaces, AeroGear, Infinispan, GateIn and other JBoss projects. Last summer I worked on Various compression codecs [1] for Netty [2]. It was my first experience with FOSS and I very glad that I was involved to this community! This summer I will work on Aerogear WebPush Server [3]. This is an implementation of the WebPush Protocol specification [4], which now in the draft mode. I will maintain WebPush Server to use the latest WebPush Protocol specification and add WebPush support to the UnifiedPush Server [5]. Also I will implement a lightweight Java client of the WebPush wire protocol and show how it works on IoT devices with UPS. [1] https://www.google-melange.com/gsoc/project/details/google/gsoc2014/idel/5693417237512192 [2] http://netty.io/ [3] https://github.com/aerogear/aerogear-webpush-server/ [4] http://tools.ietf.org/html/draft-thomson-webpush-http2-02 [5] https://aerogear.org/getstarted/downloads/#unifiedpush Best regards, Idel Pivnitskiy -- E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/d21a87a1/attachment.html From lukas.fryc at gmail.com Wed Apr 29 11:50:04 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 29 Apr 2015 15:50:04 +0000 Subject: [aerogear-dev] Sender REST endpoint returns text/plain Message-ID: Hey guys, one issues Tadeas identified during testing sender endpoint via Java Sender lib is connected to this quiet change in the REST response from REST Sender endpoint (we added text/plain response specification): https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L107 As we were always responding with "Job submitted", admin-ui client started to complain about the response not being JSON. So obvious fix was change that to text/plain, right? Not really.. some clients like Java Sender lib already expects application/json and JAX-RS then refuses these requests: https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/http/HttpClient.java#L82 The question is, what should be the correct response? There are many options, I would be perfectly fine with 204 No Content reply, but JSON might be more appropriate for future extensions, we may want to return e.g. PushMessageInformation#id or something else as part of the response. So, wouldn't be application/json more appropriate than text/plain? We may send empty body now {}. Is this something we want to address for Alpha? Or should we release fixed Java Sender lib? Cheers, ~ Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/d4b6aabd/attachment-0001.html From matzew at apache.org Wed Apr 29 11:54:37 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 29 Apr 2015 17:54:37 +0200 Subject: [aerogear-dev] Sender REST endpoint returns text/plain In-Reply-To: References: Message-ID: On Wed, Apr 29, 2015 at 5:50 PM, Luk?? Fry? wrote: > Hey guys, > > one issues Tadeas identified during testing sender endpoint via Java > Sender lib is connected to this quiet change in the REST response from REST > Sender endpoint (we added text/plain response specification): > > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L107 > > > As we were always responding with "Job submitted", admin-ui client started > to complain about the response not being JSON. So obvious fix was change > that to text/plain, right? > > Not really.. some clients like Java Sender lib already expects > application/json and JAX-RS then refuses these requests: > > > https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/http/HttpClient.java#L82 > > > > The question is, what should be the correct response? > > There are many options, I would be perfectly fine with 204 No Content > reply, > 201/accept is the way to go - since the server accepts a job, for further processing. HOWEVER, I am fine w/ skipping the content "jib submitted" on the beta.1 release > > but JSON might be more appropriate for future extensions, we may want to > return e.g. PushMessageInformation#id or something else as part of the > response. > > So, wouldn't be application/json more appropriate than text/plain? We may > send empty body now {}. > > > Is this something we want to address for Alpha? Or should we release fixed > Java Sender lib? > if needed, we need an update of the sender lib - I think due to the new format for sending pushes, we anyways need a 1.1.0-alpha.n release of that lib. Perhaps we can have one after the server is out, Sebi? > > > Cheers, > > ~ Lukas > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/1e4416ed/attachment.html From matzew at apache.org Wed Apr 29 11:58:57 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 29 Apr 2015 17:58:57 +0200 Subject: [aerogear-dev] Sender REST endpoint returns text/plain In-Reply-To: References: Message-ID: sorry accepted is 202, not 201 On Wednesday, April 29, 2015, Matthias Wessendorf wrote: > > > On Wed, Apr 29, 2015 at 5:50 PM, Luk?? Fry? > wrote: > >> Hey guys, >> >> one issues Tadeas identified during testing sender endpoint via Java >> Sender lib is connected to this quiet change in the REST response from REST >> Sender endpoint (we added text/plain response specification): >> >> >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L107 >> >> >> As we were always responding with "Job submitted", admin-ui client >> started to complain about the response not being JSON. So obvious fix was >> change that to text/plain, right? >> >> Not really.. some clients like Java Sender lib already expects >> application/json and JAX-RS then refuses these requests: >> >> >> https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/http/HttpClient.java#L82 >> >> >> >> The question is, what should be the correct response? >> >> There are many options, I would be perfectly fine with 204 No Content >> reply, >> > > > 201/accept is the way to go - since the server accepts a job, for further > processing. > > > HOWEVER, I am fine w/ skipping the content "jib submitted" on the beta.1 > release > > > >> >> but JSON might be more appropriate for future extensions, we may want to >> return e.g. PushMessageInformation#id or something else as part of the >> response. >> >> So, wouldn't be application/json more appropriate than text/plain? We may >> send empty body now {}. >> >> >> Is this something we want to address for Alpha? Or should we release >> fixed Java Sender lib? >> > > if needed, we need an update of the sender lib - I think due to the new > format for sending pushes, we anyways need a 1.1.0-alpha.n release of that > lib. Perhaps we can have one after the server is out, Sebi? > > >> >> >> Cheers, >> >> ~ Lukas >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/0853809d/attachment.html From scm.blanc at gmail.com Wed Apr 29 12:00:02 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 29 Apr 2015 18:00:02 +0200 Subject: [aerogear-dev] Sender REST endpoint returns text/plain In-Reply-To: References: Message-ID: On Wed, Apr 29, 2015 at 5:54 PM, Matthias Wessendorf wrote: > > > On Wed, Apr 29, 2015 at 5:50 PM, Luk?? Fry? wrote: > >> Hey guys, >> >> one issues Tadeas identified during testing sender endpoint via Java >> Sender lib is connected to this quiet change in the REST response from REST >> Sender endpoint (we added text/plain response specification): >> >> >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L107 >> >> >> As we were always responding with "Job submitted", admin-ui client >> started to complain about the response not being JSON. So obvious fix was >> change that to text/plain, right? >> >> Not really.. some clients like Java Sender lib already expects >> application/json and JAX-RS then refuses these requests: >> >> >> https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/http/HttpClient.java#L82 >> >> >> >> The question is, what should be the correct response? >> >> There are many options, I would be perfectly fine with 204 No Content >> reply, >> > > > 201/accept is the way to go - since the server accepts a job, for further > processing. > 202 > > > HOWEVER, I am fine w/ skipping the content "jib submitted" on the beta.1 > release > +1 > > > >> >> but JSON might be more appropriate for future extensions, we may want to >> return e.g. PushMessageInformation#id or something else as part of the >> response. >> >> So, wouldn't be application/json more appropriate than text/plain? We may >> send empty body now {}. >> >> >> Is this something we want to address for Alpha? Or should we release >> fixed Java Sender lib? >> > > if needed, we need an update of the sender lib - I think due to the new > format for sending pushes, we anyways need a 1.1.0-alpha.n release of that > lib. Perhaps we can have one after the server is out, Sebi? > Yes we need to do a release anyway/. @Lukas, could you open a jira to track this ? > > >> >> >> Cheers, >> >> ~ Lukas >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/3affae70/attachment.html From matzew at apache.org Wed Apr 29 12:00:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 29 Apr 2015 18:00:41 +0200 Subject: [aerogear-dev] [jboss-gsoc] [GSoC 2015] WebPush support for mobile cloud services In-Reply-To: References: Message-ID: Hi Idel, welcome and congrats on getting a slot in the program! I am looking forward to contributions! Cheers, Matthias On Wednesday, April 29, 2015, Idel Pivnitskiy wrote: > Hi all! > > I'm Idel Pivnitskiy and I'm a final year undergraduate student > from National Research Nuclear University MEPhI at Moscow, but I don't work > with nuclear physics :) I learn Computer Science at Cybernetic and > Information Security department. > > On my work we use JBoss technologies and build your applications and > services on WildFly or JBoss AS with Hibernate, RESTEasy, RichFaces, > AeroGear, Infinispan, GateIn and other JBoss projects. > > Last summer I worked on Various compression codecs [1] for Netty [2]. It > was my first experience with FOSS and I very glad that I was involved to > this community! > > This summer I will work on Aerogear WebPush Server [3]. This is an > implementation of the WebPush Protocol specification [4], which now in the > draft mode. I will maintain WebPush Server to use the latest WebPush > Protocol specification and add WebPush support to the UnifiedPush Server > [5]. Also I will implement a lightweight Java client of the WebPush wire > protocol and show how it works on IoT devices with UPS. > > [1] > https://www.google-melange.com/gsoc/project/details/google/gsoc2014/idel/5693417237512192 > [2] http://netty.io/ > [3] https://github.com/aerogear/aerogear-webpush-server/ > [4] http://tools.ietf.org/html/draft-thomson-webpush-http2-02 > [5] https://aerogear.org/getstarted/downloads/#unifiedpush > > Best regards, > Idel Pivnitskiy > -- > E-mail: Idel.Pivnitskiy at gmail.com > > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/682281b2/attachment-0001.html From idel.pivnitskiy at gmail.com Wed Apr 29 12:07:55 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Wed, 29 Apr 2015 19:07:55 +0300 Subject: [aerogear-dev] Sender REST endpoint returns text/plain In-Reply-To: References: Message-ID: Hello, It is a good remark! I noticed it when worked on REST api doc generation [1]. In my REST services I always use JSON or empty body and it looks like a pure api. text/plain is not compatible with it. Think, that it will be better to fix it in later releases. [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/526 Best regards, Idel Pivnitskiy -- E-mail: Idel.Pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy 2015-04-29 18:50 GMT+03:00 Luk?? Fry? : > Hey guys, > > one issues Tadeas identified during testing sender endpoint via Java > Sender lib is connected to this quiet change in the REST response from REST > Sender endpoint (we added text/plain response specification): > > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L107 > > > As we were always responding with "Job submitted", admin-ui client started > to complain about the response not being JSON. So obvious fix was change > that to text/plain, right? > > Not really.. some clients like Java Sender lib already expects > application/json and JAX-RS then refuses these requests: > > > https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/http/HttpClient.java#L82 > > > > The question is, what should be the correct response? > > There are many options, I would be perfectly fine with 204 No Content > reply, > > but JSON might be more appropriate for future extensions, we may want to > return e.g. PushMessageInformation#id or something else as part of the > response. > > So, wouldn't be application/json more appropriate than text/plain? We may > send empty body now {}. > > > Is this something we want to address for Alpha? Or should we release fixed > Java Sender lib? > > > Cheers, > > ~ Lukas > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/294bc8d9/attachment.html From dpassos at redhat.com Wed Apr 29 19:28:50 2015 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 29 Apr 2015 20:28:50 -0300 Subject: [aerogear-dev] AeroGear Windows Push - Build Status Image Message-ID: Hi, I figured out the aerogear-windows-push[1] repo has a broke build status image. I started fix it[2], but figured we don't have travis[3] enable for that. Should we remove the build status image or enable travis for this repo? [1] https://github.com/aerogear/aerogear-windows-push/ [2] https://github.com/aerogear/aerogear-windows-push/compare/master...danielpassos:fix-build-status [3] https://travis-ci.org/aerogear/aerogear-windows-push -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150429/cf5cb70f/attachment.html From scm.blanc at gmail.com Thu Apr 30 01:50:26 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 30 Apr 2015 07:50:26 +0200 Subject: [aerogear-dev] [jboss-gsoc] [GSoC 2015] WebPush support for mobile cloud services In-Reply-To: References: Message-ID: Welcome on board Idel ! This is a really exciting project on which you will be working ! Sebi On Wed, Apr 29, 2015 at 6:00 PM, Matthias Wessendorf wrote: > Hi Idel, > > welcome and congrats on getting a slot in the program! I am looking > forward to contributions! > > Cheers, > Matthias > > On Wednesday, April 29, 2015, Idel Pivnitskiy > wrote: > >> Hi all! >> >> I'm Idel Pivnitskiy and I'm a final year undergraduate student >> from National Research Nuclear University MEPhI at Moscow, but I don't work >> with nuclear physics :) I learn Computer Science at Cybernetic and >> Information Security department. >> >> On my work we use JBoss technologies and build your applications and >> services on WildFly or JBoss AS with Hibernate, RESTEasy, RichFaces, >> AeroGear, Infinispan, GateIn and other JBoss projects. >> >> Last summer I worked on Various compression codecs [1] for Netty [2]. It >> was my first experience with FOSS and I very glad that I was involved to >> this community! >> >> This summer I will work on Aerogear WebPush Server [3]. This is an >> implementation of the WebPush Protocol specification [4], which now in the >> draft mode. I will maintain WebPush Server to use the latest WebPush >> Protocol specification and add WebPush support to the UnifiedPush Server >> [5]. Also I will implement a lightweight Java client of the WebPush wire >> protocol and show how it works on IoT devices with UPS. >> >> [1] >> https://www.google-melange.com/gsoc/project/details/google/gsoc2014/idel/5693417237512192 >> [2] http://netty.io/ >> [3] https://github.com/aerogear/aerogear-webpush-server/ >> [4] http://tools.ietf.org/html/draft-thomson-webpush-http2-02 >> [5] https://aerogear.org/getstarted/downloads/#unifiedpush >> >> Best regards, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> > > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150430/fd969e77/attachment.html From lukas.fryc at gmail.com Thu Apr 30 02:01:01 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Thu, 30 Apr 2015 06:01:01 +0000 Subject: [aerogear-dev] Sender REST endpoint returns text/plain In-Reply-To: References: Message-ID: We have discussed this a bit this morning at IRC, and agreed to use 202 Accepted status code and empty JSON body {} (here we may later expose ID of the operation). Additionally Java Sender lib should be changed to send Accept header "application-json; text-plain", so that it keeps working with future and past versions. st 29. 4. 2015 v 18:14 odes?latel Idel Pivnitskiy napsal: > Hello, > > It is a good remark! I noticed it when worked on REST api doc generation > [1]. > In my REST services I always use JSON or empty body and it looks like a > pure api. text/plain is not compatible with it. Think, that it will be > better to fix it in later releases. > > [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/526 > > Best regards, > Idel Pivnitskiy > -- > E-mail: Idel.Pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > 2015-04-29 18:50 GMT+03:00 Luk?? Fry? : > >> Hey guys, >> >> one issues Tadeas identified during testing sender endpoint via Java >> Sender lib is connected to this quiet change in the REST response from REST >> Sender endpoint (we added text/plain response specification): >> >> >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L107 >> >> >> As we were always responding with "Job submitted", admin-ui client >> started to complain about the response not being JSON. So obvious fix was >> change that to text/plain, right? >> >> Not really.. some clients like Java Sender lib already expects >> application/json and JAX-RS then refuses these requests: >> >> >> https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/http/HttpClient.java#L82 >> >> >> >> The question is, what should be the correct response? >> >> There are many options, I would be perfectly fine with 204 No Content >> reply, >> >> but JSON might be more appropriate for future extensions, we may want to >> return e.g. PushMessageInformation#id or something else as part of the >> response. >> >> So, wouldn't be application/json more appropriate than text/plain? We may >> send empty body now {}. >> >> >> Is this something we want to address for Alpha? Or should we release >> fixed Java Sender lib? >> >> >> Cheers, >> >> ~ Lukas >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150430/4dde7a26/attachment-0001.html From cvasilak at gmail.com Thu Apr 30 02:37:38 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 30 Apr 2015 09:37:38 +0300 Subject: [aerogear-dev] [jboss-gsoc] [GSoC 2015] WebPush support for mobile cloud services In-Reply-To: References: Message-ID: Welcome Idel! - Christos On Thu, Apr 30, 2015 at 8:50 AM, Sebastien Blanc wrote: > Welcome on board Idel ! > > This is a really exciting project on which you will be working ! > > Sebi > > On Wed, Apr 29, 2015 at 6:00 PM, Matthias Wessendorf > wrote: > >> Hi Idel, >> >> welcome and congrats on getting a slot in the program! I am looking >> forward to contributions! >> >> Cheers, >> Matthias >> >> On Wednesday, April 29, 2015, Idel Pivnitskiy >> wrote: >> >>> Hi all! >>> >>> I'm Idel Pivnitskiy and I'm a final year undergraduate student >>> from National Research Nuclear University MEPhI at Moscow, but I don't work >>> with nuclear physics :) I learn Computer Science at Cybernetic and >>> Information Security department. >>> >>> On my work we use JBoss technologies and build your applications and >>> services on WildFly or JBoss AS with Hibernate, RESTEasy, RichFaces, >>> AeroGear, Infinispan, GateIn and other JBoss projects. >>> >>> Last summer I worked on Various compression codecs [1] for Netty [2]. It >>> was my first experience with FOSS and I very glad that I was involved to >>> this community! >>> >>> This summer I will work on Aerogear WebPush Server [3]. This is an >>> implementation of the WebPush Protocol specification [4], which now in the >>> draft mode. I will maintain WebPush Server to use the latest WebPush >>> Protocol specification and add WebPush support to the UnifiedPush Server >>> [5]. Also I will implement a lightweight Java client of the WebPush wire >>> protocol and show how it works on IoT devices with UPS. >>> >>> [1] >>> https://www.google-melange.com/gsoc/project/details/google/gsoc2014/idel/5693417237512192 >>> [2] http://netty.io/ >>> [3] https://github.com/aerogear/aerogear-webpush-server/ >>> [4] http://tools.ietf.org/html/draft-thomson-webpush-http2-02 >>> [5] https://aerogear.org/getstarted/downloads/#unifiedpush >>> >>> Best regards, >>> Idel Pivnitskiy >>> -- >>> E-mail: Idel.Pivnitskiy at gmail.com >>> Twitter: @idelpivnitskiy >>> GitHub: @idelpivnitskiy >>> >> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150430/5cad3d37/attachment.html From edewit at redhat.com Thu Apr 30 02:41:44 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 30 Apr 2015 08:41:44 +0200 Subject: [aerogear-dev] AeroGear Windows Push - Build Status Image In-Reply-To: References: Message-ID: Hi, Travis can't build windows phone projects, the build image is not from travis but from appveyor [1]. Seems that the last build status was removed, I've started the build again and the image should be fixed now. [1] https://ci.appveyor.com/project/edewit/aerogear-windows-push On Thu, Apr 30, 2015 at 1:28 AM, Daniel Passos wrote: > Hi, > > I figured out the aerogear-windows-push[1] repo has a broke build status > image. I started fix it[2], but figured we don't have travis[3] enable for > that. > > Should we remove the build status image or enable travis for this repo? > > [1] https://github.com/aerogear/aerogear-windows-push/ > [2] > https://github.com/aerogear/aerogear-windows-push/compare/master...danielpassos:fix-build-status > [3] https://travis-ci.org/aerogear/aerogear-windows-push > > -- Passos > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Cheers, Erik Jan From daniel.bevenius at gmail.com Thu Apr 30 03:23:45 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Thu, 30 Apr 2015 09:23:45 +0200 Subject: [aerogear-dev] [jboss-gsoc] [GSoC 2015] WebPush support for mobile cloud services In-Reply-To: References: Message-ID: Very pleased to hear this! torsdag 30 april 2015 skrev Christos Vasilakis : > Welcome Idel! > > > - > Christos > > > On Thu, Apr 30, 2015 at 8:50 AM, Sebastien Blanc > wrote: > >> Welcome on board Idel ! >> >> This is a really exciting project on which you will be working ! >> >> Sebi >> >> On Wed, Apr 29, 2015 at 6:00 PM, Matthias Wessendorf > > wrote: >> >>> Hi Idel, >>> >>> welcome and congrats on getting a slot in the program! I am looking >>> forward to contributions! >>> >>> Cheers, >>> Matthias >>> >>> On Wednesday, April 29, 2015, Idel Pivnitskiy >> > wrote: >>> >>>> Hi all! >>>> >>>> I'm Idel Pivnitskiy and I'm a final year undergraduate student >>>> from National Research Nuclear University MEPhI at Moscow, but I don't work >>>> with nuclear physics :) I learn Computer Science at Cybernetic and >>>> Information Security department. >>>> >>>> On my work we use JBoss technologies and build your applications and >>>> services on WildFly or JBoss AS with Hibernate, RESTEasy, RichFaces, >>>> AeroGear, Infinispan, GateIn and other JBoss projects. >>>> >>>> Last summer I worked on Various compression codecs [1] for Netty [2]. >>>> It was my first experience with FOSS and I very glad that I was involved to >>>> this community! >>>> >>>> This summer I will work on Aerogear WebPush Server [3]. This is an >>>> implementation of the WebPush Protocol specification [4], which now in the >>>> draft mode. I will maintain WebPush Server to use the latest WebPush >>>> Protocol specification and add WebPush support to the UnifiedPush Server >>>> [5]. Also I will implement a lightweight Java client of the WebPush wire >>>> protocol and show how it works on IoT devices with UPS. >>>> >>>> [1] >>>> https://www.google-melange.com/gsoc/project/details/google/gsoc2014/idel/5693417237512192 >>>> [2] http://netty.io/ >>>> [3] https://github.com/aerogear/aerogear-webpush-server/ >>>> [4] http://tools.ietf.org/html/draft-thomson-webpush-http2-02 >>>> [5] https://aerogear.org/getstarted/downloads/#unifiedpush >>>> >>>> Best regards, >>>> Idel Pivnitskiy >>>> -- >>>> E-mail: Idel.Pivnitskiy at gmail.com >>>> Twitter: @idelpivnitskiy >>>> GitHub: @idelpivnitskiy >>>> >>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150430/12bda28a/attachment.html From idel.pivnitskiy at gmail.com Thu Apr 30 04:18:43 2015 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Thu, 30 Apr 2015 11:18:43 +0300 Subject: [aerogear-dev] Sender REST endpoint returns text/plain In-Reply-To: References: Message-ID: Good decision! Could I work on this issue? My JIRA account is "idelpivnitskiy". Thanks, Idel 2015-04-30 9:01 GMT+03:00 Luk?? Fry? : > We have discussed this a bit this morning at IRC, > > and agreed to use 202 Accepted status code and empty JSON body {} (here we > may later expose ID of the operation). > > Additionally Java Sender lib should be changed to send Accept header > "application-json; text-plain", so that it keeps working with future and > past versions. > > st 29. 4. 2015 v 18:14 odes?latel Idel Pivnitskiy < > idel.pivnitskiy at gmail.com> napsal: > > Hello, >> >> It is a good remark! I noticed it when worked on REST api doc generation >> [1]. >> In my REST services I always use JSON or empty body and it looks like a >> pure api. text/plain is not compatible with it. Think, that it will be >> better to fix it in later releases. >> >> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/526 >> >> Best regards, >> Idel Pivnitskiy >> -- >> E-mail: Idel.Pivnitskiy at gmail.com >> Twitter: @idelpivnitskiy >> GitHub: @idelpivnitskiy >> 2015-04-29 18:50 GMT+03:00 Luk?? Fry? : >> >>> Hey guys, >>> >>> one issues Tadeas identified during testing sender endpoint via Java >>> Sender lib is connected to this quiet change in the REST response from REST >>> Sender endpoint (we added text/plain response specification): >>> >>> >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L107 >>> >>> >>> As we were always responding with "Job submitted", admin-ui client >>> started to complain about the response not being JSON. So obvious fix was >>> change that to text/plain, right? >>> >>> Not really.. some clients like Java Sender lib already expects >>> application/json and JAX-RS then refuses these requests: >>> >>> >>> https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/http/HttpClient.java#L82 >>> >>> >>> >>> The question is, what should be the correct response? >>> >>> There are many options, I would be perfectly fine with 204 No Content >>> reply, >>> >>> but JSON might be more appropriate for future extensions, we may want to >>> return e.g. PushMessageInformation#id or something else as part of the >>> response. >>> >>> So, wouldn't be application/json more appropriate than text/plain? We >>> may send empty body now {}. >>> >>> >>> Is this something we want to address for Alpha? Or should we release >>> fixed Java Sender lib? >>> >>> >>> Cheers, >>> >>> ~ Lukas >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150430/57f3cdaa/attachment-0001.html From lukas.fryc at gmail.com Thu Apr 30 07:56:07 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Thu, 30 Apr 2015 11:56:07 +0000 Subject: [aerogear-dev] Sender REST endpoint returns text/plain In-Reply-To: References: Message-ID: Hey Idel, by all means, feel free to take it! :-) https://issues.jboss.org/browse/AGPUSH-1376 (there is a linked issue for accomodating sender libs) @matzew: could you please add idelpivnitskiy to appropriate JIRA group so that he can be assigned to the issue? Thanks! ~ Lukas ?t 30. 4. 2015 v 10:19 odes?latel Idel Pivnitskiy napsal: Good decision! > Could I work on this issue? My JIRA account is "idelpivnitskiy". > > Thanks, > Idel > > 2015-04-30 9:01 GMT+03:00 Luk?? Fry? : > >> We have discussed this a bit this morning at IRC, >> >> and agreed to use 202 Accepted status code and empty JSON body {} (here >> we may later expose ID of the operation). >> >> Additionally Java Sender lib should be changed to send Accept header >> "application-json; text-plain", so that it keeps working with future and >> past versions. >> >> st 29. 4. 2015 v 18:14 odes?latel Idel Pivnitskiy < >> idel.pivnitskiy at gmail.com> napsal: >> >> Hello, >>> >>> It is a good remark! I noticed it when worked on REST api doc generation >>> [1]. >>> In my REST services I always use JSON or empty body and it looks like a >>> pure api. text/plain is not compatible with it. Think, that it will be >>> better to fix it in later releases. >>> >>> [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/526 >>> >>> Best regards, >>> Idel Pivnitskiy >>> -- >>> E-mail: Idel.Pivnitskiy at gmail.com >>> Twitter: @idelpivnitskiy >>> GitHub: @idelpivnitskiy >>> 2015-04-29 18:50 GMT+03:00 Luk?? Fry? : >>> >>>> Hey guys, >>>> >>>> one issues Tadeas identified during testing sender endpoint via Java >>>> Sender lib is connected to this quiet change in the REST response from REST >>>> Sender endpoint (we added text/plain response specification): >>>> >>>> >>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/sender/PushNotificationSenderEndpoint.java#L107 >>>> >>>> >>>> As we were always responding with "Job submitted", admin-ui client >>>> started to complain about the response not being JSON. So obvious fix was >>>> change that to text/plain, right? >>>> >>>> Not really.. some clients like Java Sender lib already expects >>>> application/json and JAX-RS then refuses these requests: >>>> >>>> >>>> https://github.com/aerogear/aerogear-unifiedpush-java-client/blob/master/src/main/java/org/jboss/aerogear/unifiedpush/http/HttpClient.java#L82 >>>> >>>> >>>> >>>> The question is, what should be the correct response? >>>> >>>> There are many options, I would be perfectly fine with 204 No Content >>>> reply, >>>> >>>> but JSON might be more appropriate for future extensions, we may want >>>> to return e.g. PushMessageInformation#id or something else as part of the >>>> response. >>>> >>>> So, wouldn't be application/json more appropriate than text/plain? We >>>> may send empty body now {}. >>>> >>>> >>>> Is this something we want to address for Alpha? Or should we release >>>> fixed Java Sender lib? >>>> >>>> >>>> Cheers, >>>> >>>> ~ Lukas >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150430/ee265c71/attachment.html From scm.blanc at gmail.com Thu Apr 30 09:43:44 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 30 Apr 2015 15:43:44 +0200 Subject: [aerogear-dev] Advanced Analtyics, new PR and call to the client tech leads Message-ID: Hi, The Advanced Analytics task[1] has a new PR[2] that has been rebased on the latest master and got a lot of polishing. Could the Client Tech Leads take a look at it [3] and review ? The only "breaking" change is the rename of the header's name that identifies a Push Notification, it's called now "aerogear-push-id" Seb [1] https://issues.jboss.org/browse/AGPUSH-971 [2] https://github.com/aerogear/aerogear-unifiedpush-server/pull/540 [3] Subtasks of https://issues.jboss.org/browse/AGPUSH-971 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150430/f22b0a78/attachment.html From supittma at redhat.com Thu Apr 30 11:04:49 2015 From: supittma at redhat.com (Summers Pittman) Date: Thu, 30 Apr 2015 11:04:49 -0400 Subject: [aerogear-dev] OAuth2 with native Broswer in Android Message-ID: In Android I have a solution for using the native browser to perform an OAuth2 sign in. There are some limititions however. In general to use this you need an activity which has an intent filter to consume the redirect URL. This works best if you use a custom URI scheme. Google, Yahoo, and Facebook (as well as other I'm sure) only allow redirects to http or https. This means that unless you are using a third party to redirect a custom schema the browser my preempt your application and consume the redirect. Other services such as KeyCloak and Spotify allow custom schemas and these work perfectly with my solution. If we document the limitations of the Intent and when using an Intent vs using a WebView is appropriate, is a solution with these limitations adequate? I think it is. Thoughts? Summers PS: a link to my poc : https://github.com/secondsun/aerogear-android-authz/tree/AGDROID-319/ PPS: You can use this on the KeyCloakHelper in Shoot and Share by adding `setWithIntent(true)` to the configuration in that class. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150430/0ba7d32d/attachment.html From cvasilak at gmail.com Thu Apr 30 13:25:10 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 30 Apr 2015 20:25:10 +0300 Subject: [aerogear-dev] OAuth2 with native Broswer in Android In-Reply-To: References: Message-ID: On Thu, Apr 30, 2015 at 6:04 PM, Summers Pittman wrote: > In Android I have a solution for using the native browser to perform an > OAuth2 sign in. There are some limititions however. > > In general to use this you need an activity which has an intent filter to > consume the redirect URL. This works best if you use a custom URI scheme. > Google, Yahoo, and Facebook (as well as other I'm sure) only allow > redirects to http or https. This means that unless you are using a third > party to redirect a custom schema the browser my preempt your application > and consume the redirect. Other services such as KeyCloak and Spotify > allow custom schemas and these work perfectly with my solution. > > If we document the limitations of the Intent and when using an Intent vs > using a WebView is appropriate, is a solution with these limitations > adequate? I think it is. > +1 since generic OAuth2 provider is the goal, the intricacies of some should not interfere with the ?correct? spec flow. btw interesting enough, in the iOS side of things the Bundle_ID can be used as the prefix in the redirect_uri registration and works correctly. Now why the Android 'Package name? can?t be used similarly here is a mystery. Oh well.. - Christos > Thoughts? > > Summers > > PS: a link to my poc : > https://github.com/secondsun/aerogear-android-authz/tree/AGDROID-319/ > PPS: You can use this on the KeyCloakHelper in Shoot and Share by adding > `setWithIntent(true)` to the configuration in that class. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150430/e77159cc/attachment.html From aliok at apache.org Thu Apr 30 18:35:03 2015 From: aliok at apache.org (Ali Ok) Date: Fri, 1 May 2015 00:35:03 +0200 Subject: [aerogear-dev] Sync examples : Ionic/Angular and canvas Message-ID: Hi all, I prepared 2 Sync examples for AeroGear JS cookbook: * Ionic/Angular : https://github.com/aerogear/aerogear-js-cookbook/tree/master/diff-sync-ionic --> Demonstrating Sync's real-time updates with an Ionic application. Compatible with Sync example applications of other platforms. * Canvas : https://github.com/aerogear/aerogear-js-cookbook/tree/master/diff-sync-canvas --> Demonstrating a very very simple collaborative drawing application For the lazy: see the screencasts in both pages :) Thanks Luk?? Fry? for the code review and Lucas Holmquist for the PR merge. Cheers, Ali -- My Blog: http://blog.aliok.com.tr Twitter: http://twitter.com/aliok_tr -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150501/e07f63ea/attachment-0001.html