From lukas.fryc at gmail.com Mon Jan 5 03:24:51 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Mon, 5 Jan 2015 09:24:51 +0100 Subject: [aerogear-dev] [Aerogear-users] [Poll] AeroGear.org Web Site Color Test In-Reply-To: References: <700DA584-7D60-49DE-8F13-E9BD5D522CB0@redhat.com> <1243248424.836778.1418241264918.JavaMail.zimbra@redhat.com> Message-ID: Hey guys, as for the results, it seems people really like the Blue color as it is in the current prototype the most: http://andresgalante.com/aerogearwebsite/ Results: * 8x Blue - same blue as in the logo * 3x Blue - alternative one * 1x Orange - alternative * 1x Orange - same orange as in the logo But I must agree that the yellow color does not play nice with the rest of the page. Thanks for everyone who participated, I have left the poll opened especially long over the holidays, but the responses were recorded during first two days, just FYI. ;-) ~ Lukas On Thu, Dec 11, 2014 at 10:09 AM, Corinne Krych wrote: > > > On 10 Dec 2014, at 20:54, Andres Galante wrote: > > > > ...and the orange from the logo just doesn't have enough contrast, these > are test with the exact same color of the logo, the logo from the inner "G" > gear and an even lighter version of the same color: > > > > https://dl.dropboxusercontent.com/u/4371641/logo-color.png > > https://dl.dropboxusercontent.com/u/4371641/logo-color2.png > > I have a 404 for logo-color2 :( > > > https://dl.dropboxusercontent.com/u/4371641/logo-color3.png > > > > > > Is not even orange... is a kind of pinkish salmon color :p > > > > > > > > ----- Original Message ----- > > From: "Lucas Holmquist" > > To: aerogear-users at lists.jboss.org > > Cc: "AeroGear Developer Mailing List" > > Sent: Wednesday, December 10, 2014 4:20:15 PM > > Subject: Re: [aerogear-dev] [Aerogear-users] [Poll] AeroGear.org Web > Site Color Test > > > > i like the blue(color from the logo, voted for that one), but on the > prototyped site, i think the yellow is to bright for the words, maybe the > orange for the words? > > > > > > > > On Dec 10, 2014, at 1:27 PM, Luk?? Fry? < lukas.fryc at gmail.com > wrote: > > > > Hello good people, > > > > Andres came with nice colour sets for a new Aerogear.org site. > > > > We would like you to consider which one fits the project best or simply > which is a best option in your eyes! > > > > See the the poll here: > > > > http://goo.gl/forms/4YojF0DMbi > > > > > > Cheers! > > > > ~ Lukas > > _______________________________________________ > > Aerogear-users mailing list > > Aerogear-users at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-users > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20150105/982bbe20/attachment.html From lukas.fryc at gmail.com Mon Jan 5 03:28:39 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Mon, 5 Jan 2015 09:28:39 +0100 Subject: [aerogear-dev] Aerogear.org redesign In-Reply-To: <2008024913.178867.1419348204037.JavaMail.zimbra@redhat.com> References: <800994770.178074.1419347793901.JavaMail.zimbra@redhat.com> <2008024913.178867.1419348204037.JavaMail.zimbra@redhat.com> Message-ID: Hey guys, I believe we should get the page on today's meeting agenda to determine next steps (content-wise). >From the another thread, I've closed the poll for the colours and at the end, the current Blue won our hearts. Just people seem to not like the yellow colours for some widgets. @Andres, could you possibly look at the yellow coloring - change it to something more eye pleasant, maybe orange? I'm also taking look at bringing some more dynamic content to the page. Cheers! ~ Lukas On Tue, Dec 23, 2014 at 4:23 PM, Andres Galante wrote: > Hi! > I don't think there is much more I can do on the website by my own. I'll > need your help to: > > - Write text and correct typos. There is text to write on Homepage, > Modules (add more text for each module) and Guides, you'll notice the Lorem > ipsum :) > > - Review the structure for Downloads, Guides and Specs > > - What logos to put on the homepage footer > > - Review styles and design. Did I forget to change anything that was > requested? > > We can discuss this in january when everyone is back. For the ones that > are around: Happy holidays :) > > Thanks! > > Andr?s > > _______________________________________________ > 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/20150105/f6baeccf/attachment-0001.html From cvasilak at gmail.com Mon Jan 5 05:13:28 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 5 Jan 2015 12:13:28 +0200 Subject: [aerogear-dev] Team Meeting Message-ID: <829A06DC-01BC-409C-945A-3479C572E6DD@gmail.com> Hi team and Happy New Year to all! created agenda for todays meetings, feel free to add your items: http://oksoclap.com/p/meeting-05.01.15 - Christos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150105/3c2450b0/attachment.html From cvasilak at gmail.com Mon Jan 5 05:30:44 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 5 Jan 2015 12:30:44 +0200 Subject: [aerogear-dev] Team Meeting Message-ID: <5E6C4D4D-3740-4CF0-88C3-5E90A4BBB6D6@gmail.com> Hi team and Happy New Year to all! Agenda for todays meetings, feel free to add your items: http://oksoclap.com/p/meeting-05.01.15 - Christos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150105/e958d0af/attachment.html From matzew at apache.org Mon Jan 5 05:32:17 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 5 Jan 2015 11:32:17 +0100 Subject: [aerogear-dev] JIRA instances for Push... Message-ID: Hi, right now we have three different types of 'push servers': * UPS * SimplePush * WebPush Server The first two ones each have their own JIRA, but I was wondering if we use the AGPUSH jira for all three. To manage releases and bugs, we will go with different/more components, and for the releases, we could do what we do successfully on our Cordova project. We can, in JIRA, have releases like: ups-1.3.0 sps-1.0.0 wps-0.2.0 That way would have all push (server) bits on the same JIRA and differentiation is simply done using components and versions as discussed above. 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/20150105/abef316c/attachment.html From bruno at abstractj.org Mon Jan 5 06:53:05 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 5 Jan 2015 09:53:05 -0200 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: References: Message-ID: <20150105115305.GA49398@abstractj.org> I think makes sense having all of them under AGPUSH and creating components: ups, sps and wps and manage it with the release field. +1 On 2015-01-05, Matthias Wessendorf wrote: > Hi, > > right now we have three different types of 'push servers': > * UPS > * SimplePush > * WebPush Server > > The first two ones each have their own JIRA, but I was wondering if we use > the AGPUSH jira for all three. > > To manage releases and bugs, we will go with different/more components, and > for the releases, we could do what we do successfully on our Cordova > project. We can, in JIRA, have releases like: > > ups-1.3.0 > sps-1.0.0 > wps-0.2.0 > > That way would have all push (server) bits on the same JIRA and > differentiation is simply done using components and versions as discussed > above. > > 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 -- abstractj PGP: 0x84DC9914 From agalante at redhat.com Mon Jan 5 08:10:23 2015 From: agalante at redhat.com (Andres Galante) Date: Mon, 5 Jan 2015 08:10:23 -0500 (EST) Subject: [aerogear-dev] Aerogear.org redesign In-Reply-To: References: <800994770.178074.1419347793901.JavaMail.zimbra@redhat.com> <2008024913.178867.1419348204037.JavaMail.zimbra@redhat.com> Message-ID: <1620398785.591802.1420463423379.JavaMail.zimbra@redhat.com> Hi! Can you test this color: https://dl.dropboxusercontent.com/u/4371641/orange_final.jpg Does it still hurt your eyes? ----- Original Message ----- From: "Luk?? Fry?" To: "AeroGear Developer Mailing List" Sent: Monday, January 5, 2015 5:28:39 AM Subject: Re: [aerogear-dev] Aerogear.org redesign Hey guys, I believe we should get the page on today's meeting agenda to determine next steps (content-wise). >From the another thread, I've closed the poll for the colours and at the end, the current Blue won our hearts. Just people seem to not like the yellow colours for some widgets. @Andres, could you possibly look at the yellow coloring - change it to something more eye pleasant, maybe orange? I'm also taking look at bringing some more dynamic content to the page. Cheers! ~ Lukas On Tue, Dec 23, 2014 at 4:23 PM, Andres Galante < agalante at redhat.com > wrote: Hi! I don't think there is much more I can do on the website by my own. I'll need your help to: - Write text and correct typos. There is text to write on Homepage, Modules (add more text for each module) and Guides, you'll notice the Lorem ipsum :) - Review the structure for Downloads, Guides and Specs - What logos to put on the homepage footer - Review styles and design. Did I forget to change anything that was requested? We can discuss this in january when everyone is back. For the ones that are around: Happy holidays :) Thanks! Andr?s _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.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 matzew at apache.org Mon Jan 5 08:35:31 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 5 Jan 2015 14:35:31 +0100 Subject: [aerogear-dev] AeroGear.org - a first thought on changing our roadmap docs In-Reply-To: <1961678578.1169094.1418671350236.JavaMail.zimbra@redhat.com> References: <90466273.1130732.1418653076247.JavaMail.zimbra@redhat.com> <3F023A03-AB42-4834-9ECE-D2D5753E5C2A@gmail.com> <1961678578.1169094.1418671350236.JavaMail.zimbra@redhat.com> Message-ID: here is the second part of it: https://github.com/aerogear/aerogear.org/pull/455 removing duplicated roadmap files, and pointing to JIRA entry pages for the different parts On Mon, Dec 15, 2014 at 8:22 PM, Andres Galante wrote: > On the roadmap page there is a place to show the latest jira and github > activity: > http://andresgalante.com/aerogearwebsite/roadmap.html > > I'll adapt that to show a more extensive roadmap of epics > > ----- Original Message ----- > From: "S?bastien Blanc" > To: "AeroGear Developer Mailing List" > Sent: Monday, December 15, 2014 4:04:12 PM > Subject: Re: [aerogear-dev] AeroGear.org - a first thought on changing > our roadmap docs > > > > Envoy? de mon iPhone > > Le 15 d?c. 2014 ? 17:41, Matthias Wessendorf < matzew at apache.org > a > ?crit : > > > > > > > On Mon, Dec 15, 2014 at 5:31 PM, Luk?? Fry? < lukas.fryc at gmail.com > > wrote: > > > +1 to having JIRA as single source of truth > > > Eventually, we can really poll the JIRA REST API during the site build and > populate the roadmap (together with linking to it). > > E.g. list all Epics associated with the given version on the built site, > and link to the full roadmap. > > > ok - that's an option, we could look into. > +1 to show the epics > > > > > > > > > On Mon, Dec 15, 2014 at 3:23 PM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > > On Mon, Dec 15, 2014 at 3:17 PM, Andres Galante < agalante at redhat.com > > wrote: > > Can't we have some kind of aggregator that reads the roadmaps from JIRA > and print it on the website? > > Not sure. Since JIRA is the main tool to manage and plan releases, let's > link straight to it. That's also the place where users actually would file > tickets (e.g. bugs or feature requests) > > -M > > > > > > ----- Original Message ----- > From: "Daniel Bevenius" < daniel.bevenius at gmail.com > > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > > Sent: Monday, December 15, 2014 11:08:31 AM > Subject: Re: [aerogear-dev] AeroGear.org - a first thought on changing our > roadmap docs > > > First step: replace existing roadmaps with links to JIRAs, where > possible. > > >Next step: re-think the entire roadmaps section. I am currently on that, > and it's not 100% yet clear, what's best. Once I have more on this, I will > share thoughts > Sounds good! > > On 15 December 2014 at 15:05, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > Hey, > > that's what I am currently looking at - by doing the analysis of the site, > I noticed that our current roadmap docs just duplicate info from JIRA > > First step: replace existing roadmaps with links to JIRAs, where possible. > > Next step: re-think the entire roadmaps section. I am currently on that, > and it's not 100% yet clear, what's best. Once I have more on this, I will > share thoughts > > > > On Mon, Dec 15, 2014 at 2:40 PM, Bruno Oliveira < bruno at abstractj.org > > wrote: > > Alright, let's think about the following scenario. I'm a newcomer, going > aerogear.org to learn more about AeroGear and want to know what's planned > for the future > releases. Where should I look? > > On 2014-12-15, Matthias Wessendorf wrote: > > On Mon, Dec 15, 2014 at 2:25 PM, Bruno Oliveira < bruno at abstractj.org > > wrote: > > > > > > Speaking from the security side of the things, to me is impossible to > > > have a feature driven roadmap, because it's a cross cutting concern. > > > > > > > right :-) > > > > looking at [1] I see different types of roadmaps > > > > 1) Project roadmap > > 2) Platform roadmaps (e.g. Android, Cordova, iOS and JS) > > 3) cross cutting concerns (e.g. security) > > 4) specific roadmaps (E.g. UPS/WebPush or even the WebSite roadmap) > > > > > > And that's fine :) For now, I'd really just like to get rid of the pages > > that basically duplicate info, available on JIRA :-) > > > > > > > > > > > > > > About removing the roadmap from website, as long as we make it clear > > > por people outside AeroGear, I'm fine. > > > > > > On 2014-12-15, Matthias Wessendorf wrote: > > > > Hi team, > > > > > > > > while thinking about restructuring our roadmaps, I was wondering > about > > > our > > > > existing roadmaps on [1]. Overall I'd like to have the AG roadmaps > more > > > > feature driven, but that requires some more thoughts/changes? > > > > > > > > However, here is what I am wondering about... > > > > > > > > Most of our roadmaps we link to from [1], are really just pointing to > > > > different JIRAs. > > > > > > > > > > > > Let's take one example, UPS: > > > > https://aerogear.org/docs/planning/roadmaps/UnifiedPush/ > > > > > > > > Basically all info on the above page is present in JIRA (including > the > > > > 'archived' roadmap of older releases). Since JIRA should be the > central > > > > tool for planing releases, features and future versions, I think > that our > > > > roadmap docs are not adding too much value, since they repeat info > that > > > is > > > > available on a different place (JIRA). > > > > > > > > Also, maintaining the roadmaps is tedious: You make a change on the > > > actual > > > > JIRA (e.g. move the date of a release or add a new feature). To keep > the > > > > roadmap up-to-date, you put the same info on the roadmap doc and > send a > > > PR. > > > > > > > > > > > > Can we remove these roadmap docs? > > > > > > > > For UPS that would mean, that the link on [1] would go against: > > > > > > > > https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel > > > > > > > > instead of here: > > > > https://aerogear.org/docs/planning/roadmaps/UnifiedPush/ > > > > > > > > -Matthias > > > > > > > > [1] https://aerogear.org/docs/planning/ > > > > > > > > > > > > -- > > > > 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 > > > > > > > > > -- > > > > > > abstractj > > > PGP: 0x84DC9914 > > > _______________________________________________ > > > 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 > > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > 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 > > > -- > 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/20150105/e94680a1/attachment-0001.html From lholmqui at redhat.com Mon Jan 5 09:11:31 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 5 Jan 2015 09:11:31 -0500 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: <20150105115305.GA49398@abstractj.org> References: <20150105115305.GA49398@abstractj.org> Message-ID: <7A169884-9B6E-4254-85A4-40F2BF478630@redhat.com> this sounds reasonable. Would we go back and rename previous AGPUSH releases to ups-* and also recreate the current old sps releases in AGPUSH? > On Jan 5, 2015, at 6:53 AM, Bruno Oliveira wrote: > > I think makes sense having all of them under AGPUSH and creating > components: ups, sps and wps and manage it with the release field. > > +1 > > On 2015-01-05, Matthias Wessendorf wrote: >> Hi, >> >> right now we have three different types of 'push servers': >> * UPS >> * SimplePush >> * WebPush Server >> >> The first two ones each have their own JIRA, but I was wondering if we use >> the AGPUSH jira for all three. >> >> To manage releases and bugs, we will go with different/more components, and >> for the releases, we could do what we do successfully on our Cordova >> project. We can, in JIRA, have releases like: >> >> ups-1.3.0 >> sps-1.0.0 >> wps-0.2.0 >> >> That way would have all push (server) bits on the same JIRA and >> differentiation is simply done using components and versions as discussed >> above. >> >> 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 > > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Mon Jan 5 09:13:43 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 5 Jan 2015 15:13:43 +0100 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: <7A169884-9B6E-4254-85A4-40F2BF478630@redhat.com> References: <20150105115305.GA49398@abstractj.org> <7A169884-9B6E-4254-85A4-40F2BF478630@redhat.com> Message-ID: On Mon, Jan 5, 2015 at 3:11 PM, Lucas Holmquist wrote: > this sounds reasonable. > > > Would we go back and rename previous AGPUSH releases to ups-* and also > recreate the current old sps releases in AGPUSH? > yes, that's a good idea. > > > > > On Jan 5, 2015, at 6:53 AM, Bruno Oliveira wrote: > > > > I think makes sense having all of them under AGPUSH and creating > > components: ups, sps and wps and manage it with the release field. > > > > +1 > > > > On 2015-01-05, Matthias Wessendorf wrote: > >> Hi, > >> > >> right now we have three different types of 'push servers': > >> * UPS > >> * SimplePush > >> * WebPush Server > >> > >> The first two ones each have their own JIRA, but I was wondering if we > use > >> the AGPUSH jira for all three. > >> > >> To manage releases and bugs, we will go with different/more components, > and > >> for the releases, we could do what we do successfully on our Cordova > >> project. We can, in JIRA, have releases like: > >> > >> ups-1.3.0 > >> sps-1.0.0 > >> wps-0.2.0 > >> > >> That way would have all push (server) bits on the same JIRA and > >> differentiation is simply done using components and versions as > discussed > >> above. > >> > >> 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 > > > > > > -- > > > > abstractj > > PGP: 0x84DC9914 > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20150105/569f6438/attachment.html From matzew at apache.org Mon Jan 5 09:28:23 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 5 Jan 2015 15:28:23 +0100 Subject: [aerogear-dev] Aerogear.org redesign In-Reply-To: <1620398785.591802.1420463423379.JavaMail.zimbra@redhat.com> References: <800994770.178074.1419347793901.JavaMail.zimbra@redhat.com> <2008024913.178867.1419348204037.JavaMail.zimbra@redhat.com> <1620398785.591802.1420463423379.JavaMail.zimbra@redhat.com> Message-ID: oh, wow - that looks great! love it On Mon, Jan 5, 2015 at 2:10 PM, Andres Galante wrote: > Hi! > Can you test this color: > https://dl.dropboxusercontent.com/u/4371641/orange_final.jpg > > Does it still hurt your eyes? > > > ----- Original Message ----- > From: "Luk?? Fry?" > To: "AeroGear Developer Mailing List" > Sent: Monday, January 5, 2015 5:28:39 AM > Subject: Re: [aerogear-dev] Aerogear.org redesign > > Hey guys, > > I believe we should get the page on today's meeting agenda to determine > next steps (content-wise). > > From the another thread, I've closed the poll for the colours and at the > end, the current Blue won our hearts. Just people seem to not like the > yellow colours for some widgets. > > @Andres, could you possibly look at the yellow coloring - change it to > something more eye pleasant, maybe orange? > > I'm also taking look at bringing some more dynamic content to the page. > > > Cheers! > > ~ Lukas > > On Tue, Dec 23, 2014 at 4:23 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Hi! > I don't think there is much more I can do on the website by my own. I'll > need your help to: > > - Write text and correct typos. There is text to write on Homepage, > Modules (add more text for each module) and Guides, you'll notice the Lorem > ipsum :) > > - Review the structure for Downloads, Guides and Specs > > - What logos to put on the homepage footer > > - Review styles and design. Did I forget to change anything that was > requested? > > We can discuss this in january when everyone is back. For the ones that > are around: Happy holidays :) > > Thanks! > > Andr?s > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150105/8345ddbc/attachment.html From cvasilak at gmail.com Mon Jan 5 10:14:41 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 5 Jan 2015 17:14:41 +0200 Subject: [aerogear-dev] Team Meeting In-Reply-To: <829A06DC-01BC-409C-945A-3479C572E6DD@gmail.com> References: <829A06DC-01BC-409C-945A-3479C572E6DD@gmail.com> Message-ID: <04A05FD0-75CA-423F-9D96-73FACCC6D034@gmail.com> fyi, meeting minutes: Meeting ended Mon Jan 5 15:11:15 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-01-05-15.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-05-15.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-05-15.00.log.html > On Jan 5, 2015, at 12:13 PM, Christos Vasilakis wrote: > > Hi team and Happy New Year to all! > > created agenda for todays meetings, feel free to add your items: > > http://oksoclap.com/p/meeting-05.01.15 > > - > Christos > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150105/c7aaab26/attachment.html From kpiwko at redhat.com Mon Jan 5 10:21:11 2015 From: kpiwko at redhat.com (Karel Piwko) Date: Mon, 05 Jan 2015 16:21:11 +0100 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: References: Message-ID: <1420471271.11233.6.camel@kpiwko-x220> +1. Less JIRA instances, the better imho. Karel On Mon, 2015-01-05 at 11:32 +0100, Matthias Wessendorf wrote: > Hi, > > > right now we have three different types of 'push servers': > * UPS > * SimplePush > * WebPush Server > > > The first two ones each have their own JIRA, but I was wondering if we > use the AGPUSH jira for all three. > > > To manage releases and bugs, we will go with different/more > components, and for the releases, we could do what we do successfully > on our Cordova project. We can, in JIRA, have releases like: > > > ups-1.3.0 > sps-1.0.0 > wps-0.2.0 > > > That way would have all push (server) bits on the same JIRA and > differentiation is simply done using components and versions as > discussed above. > > > 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 From lholmqui at redhat.com Mon Jan 5 11:32:17 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 5 Jan 2015 11:32:17 -0500 Subject: [aerogear-dev] POC - Service Workers and Conflict Resolution Message-ID: <64AD907E-AA9E-4B06-B021-5CFE20AF41F7@redhat.com> Here is my blog post on using Service Workers for Conflict Resolution http://blog.lholmquist.org/service-workers-can-settle-conflicts-too/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150105/99cc5285/attachment.html From agalante at redhat.com Mon Jan 5 11:53:27 2015 From: agalante at redhat.com (Andres Galante) Date: Mon, 5 Jan 2015 11:53:27 -0500 (EST) Subject: [aerogear-dev] UP console questions In-Reply-To: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> Message-ID: <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> Hey! I am working on the push console, and I have some questions: 1- What is the main action on the console? What is the main goal a user want to achieve? I notice that the console is center on creating and seeing up apps and not so much in sending notifications. Is sending notifications usually done on code and not the console? 2- Under each app we have some information mixed with actions: No variants - Activity - Send Push - admin What does "admin" do, can an app be manage by other thats not the admin? 3- Once you click on an app name you get a yellow box with "Sending push notifications" set up information. But when you create a variant you also get an specific info box for each variant. What is the difference between them? Thanks! From daniel.bevenius at gmail.com Mon Jan 5 12:15:08 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 5 Jan 2015 18:15:08 +0100 Subject: [aerogear-dev] POC - Service Workers and Conflict Resolution In-Reply-To: <64AD907E-AA9E-4B06-B021-5CFE20AF41F7@redhat.com> References: <64AD907E-AA9E-4B06-B021-5CFE20AF41F7@redhat.com> Message-ID: nice work! m?ndag 5 januari 2015 skrev Lucas Holmquist : > Here is my blog post on using Service Workers for Conflict Resolution > > > http://blog.lholmquist.org/service-workers-can-settle-conflicts-too/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150105/a6e07344/attachment.html From matzew at apache.org Tue Jan 6 02:40:53 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 6 Jan 2015 08:40:53 +0100 Subject: [aerogear-dev] UPS : How to get notified when an installation is deleted/updated In-Reply-To: <004701d020d1$4b42ff40$e1c8fdc0$@pinelabs.com> References: <004701d020d1$4b42ff40$e1c8fdc0$@pinelabs.com> Message-ID: Hi Vivek, sorry for the late reply, but all of us went on a longer break :-) On Fri, Dec 26, 2014 at 7:00 AM, Vivek Pandey wrote: > Hello UPS team, > > > > Hope you had a wonderful Christmas!! > > > > I am using UPS 1.0.2 (on postgres/wildfly 8.1) and wanted to understand > the best strategy to sync deletions of installation in UPS to my own db. > > My current implementation stores the push token in my own db and registers > them to UPS periodically. However, currently I do not have any strategy to > sync deletions to my own db. > > > > Does UPS publish deletion events? > Nope, we don't have that > Or there is any bulk query mechanism to fetch a paginated list of active > installations? > yes, that's the request we submit behind the installations details page: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/InstallationManagementEndpoint.java#L55 > > > Thanks, > > Vivek > > ------------------------------ > This message may contain privileged and confidential information and is > solely for the use of intended recipient. The views expressed in this email > are those of the sender and not of Pine Labs. The recipient should check > this email and attachments for the presence of viruses / malwares etc. Pine > Labs accepts no liability for any damage caused by any virus transmitted by > this email. Pine Labs may monitor and record all emails. > ------------------------------ > > > _______________________________________________ > 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/20150106/b416bd0a/attachment.html From lukas.fryc at gmail.com Tue Jan 6 03:38:02 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 6 Jan 2015 09:38:02 +0100 Subject: [aerogear-dev] POC - Service Workers and Conflict Resolution In-Reply-To: References: <64AD907E-AA9E-4B06-B021-5CFE20AF41F7@redhat.com> Message-ID: It is very good idea, and a nice way how to integrate with existing libraries. It shields user from one round of conflict resolution handling. I have created a small diagram to better understand that and it revealed one more fact: https://docs.google.com/drawings/d/1vIqYjfukHwb9HVuYAlf9eO5U_Eopgl9EOZyG22wEV2s/edit?usp=sharing As seen on the diagram, user would still have to Merge on the programmatic layer, where we could offer a DiffMatchPatch alghoritm, and/or integration with selected existing libraries (e.g. AngularJS ResoureProvider or Restangular or similar Ember approach). I believe we don't have to handle "I work for second and later requests" problem you mentioned in the blog, since I assume ServiceWorker will react on the REST calls from the application once it is registered (not sure that's the case). That's with a question mark. :-) On Mon, Jan 5, 2015 at 6:15 PM, Daniel Bevenius wrote: > nice work! > > m?ndag 5 januari 2015 skrev Lucas Holmquist : > > Here is my blog post on using Service Workers for Conflict Resolution >> >> >> http://blog.lholmquist.org/service-workers-can-settle-conflicts-too/ >> > > _______________________________________________ > 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/20150106/f86317cd/attachment.html From vivek.pandey at pinelabs.com Tue Jan 6 03:42:46 2015 From: vivek.pandey at pinelabs.com (Vivek Pandey) Date: Tue, 6 Jan 2015 14:12:46 +0530 Subject: [aerogear-dev] UPS : How to get notified when an installation is deleted/updated In-Reply-To: References: <004701d020d1$4b42ff40$e1c8fdc0$@pinelabs.com> Message-ID: <008801d0298c$bec535a0$3c4fa0e0$@pinelabs.com> Thanks Matthias, Currently, I have gone ahead with a database trigger on installation table. It records tokens of deleted installations in a separate table. I periodically query this table from my application and update the data as required. Thanks, Vivek From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: Tuesday, January 06, 2015 1:11 PM To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] UPS : How to get notified when an installation is deleted/updated Hi Vivek, sorry for the late reply, but all of us went on a longer break :-) On Fri, Dec 26, 2014 at 7:00 AM, Vivek Pandey wrote: Hello UPS team, Hope you had a wonderful Christmas!! I am using UPS 1.0.2 (on postgres/wildfly 8.1) and wanted to understand the best strategy to sync deletions of installation in UPS to my own db. My current implementation stores the push token in my own db and registers them to UPS periodically. However, currently I do not have any strategy to sync deletions to my own db. Does UPS publish deletion events? Nope, we don't have that Or there is any bulk query mechanism to fetch a paginated list of active installations? yes, that's the request we submit behind the installations details page: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/InstallationManagementEndpoint.java#L55 Thanks, Vivek _____ This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails. _____ _______________________________________________ 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 This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150106/fc6ecaf7/attachment-0001.html From matzew at apache.org Tue Jan 6 03:57:52 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 6 Jan 2015 09:57:52 +0100 Subject: [aerogear-dev] UP console questions In-Reply-To: <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> References: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> Message-ID: On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante wrote: > Hey! > > I am working on the push console, and I have some questions: > > 1- What is the main action on the console? What is the main goal a user > want to achieve? > I notice that the console is center on creating and seeing up apps and not > so much in sending notifications. Is sending notifications usually done on > code and not the console? > the console is nice to send test messages. But in reality a backend (e.g. a MBaaS) will send a request to UPS to force it to deliver the push to Apple and GCM. The main goal is managaement (and overview/stats) around Apps, their Variants and their installations. > > 2- Under each app we have some information mixed with actions: > No variants - Activity - Send Push - admin > What does "admin" do, can an app be manage by other thats not the admin? > we allow to roles: * admin * user a user (like Andres or Matthias) can do all the CRUD actions. Andres see his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from both users Andres and Matthias > 3- Once you click on an app name you get a yellow box with "Sending push > notifications" set up information. But when you create a variant you also > get an specific info box for each variant. > What is the difference between them? > not sure what you are asking > > Thanks! > _______________________________________________ > 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/20150106/a4a31fb5/attachment.html From corinnekrych at gmail.com Tue Jan 6 04:44:18 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 6 Jan 2015 10:44:18 +0100 Subject: [aerogear-dev] iOS team meeting Message-ID: <967BA31E-5D4F-4DC3-92F5-E0AF150A1A05@gmail.com> Hello all, Our iOS meeting will take place this afternoon, usual time 4pm. Here is the agenda: http://oksoclap.com/p/ios_meeting_6th_January_2015 ++ Corinne From daniel at passos.me Tue Jan 6 05:35:31 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 6 Jan 2015 08:35:31 -0200 Subject: [aerogear-dev] UP console questions In-Reply-To: References: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Jan 6, 2015 at 6:57 AM, Matthias Wessendorf wrote: > > On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante > wrote: > >> Hey! >> >> I am working on the push console, and I have some questions: >> >> 1- What is the main action on the console? What is the main goal a user >> want to achieve? >> I notice that the console is center on creating and seeing up apps and >> not so much in sending notifications. Is sending notifications usually done >> on code and not the console? >> > > the console is nice to send test messages. But in reality a backend (e.g. > a MBaaS) will send a request to UPS to force it to deliver the push to > Apple and GCM. > > The main goal is managaement (and overview/stats) around Apps, their > Variants and their installations. > > >> >> 2- Under each app we have some information mixed with actions: >> No variants - Activity - Send Push - admin >> What does "admin" do, can an app be manage by other thats not the admin? >> > > we allow to roles: > * admin > * user > > a user (like Andres or Matthias) can do all the CRUD actions. Andres see > his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from > both users Andres and Matthias > > >> 3- Once you click on an app name you get a yellow box with "Sending push >> notifications" set up information. But when you create a variant you also >> get an specific info box for each variant. >> What is the difference between them? >> > > not sure what you are asking > The first box (*Sending push notifications*) when you create a new application is a snippet of code to you use in you backend (using our sender API[1]) to send a message to UPS and it delivery to the devices like it[2]. The second box (*Registering installations*) when you create a variant is a snippet of code to you use in you mobile app to register you device in that application like it[3] [1] https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ [2] https://github.com/danielpassos/aerogear-jaxrs-backend/blob/master/src/main/java/me/passos/talks/aerogear/ProductService.java#L56-L69 [3] https://github.com/danielpassos/AeroProduct/blob/master/src/me/passos/talks/aerogear/AeroProductsApplication.java#L36-L60 > >> >> Thanks! > > ? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150106/b1d6fb0f/attachment.html From daniel at passos.me Tue Jan 6 05:52:16 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 6 Jan 2015 08:52:16 -0200 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: <1420471271.11233.6.camel@kpiwko-x220> References: <1420471271.11233.6.camel@kpiwko-x220> Message-ID: +1 for the same Jira project, and use components -- Passos On Mon, Jan 5, 2015 at 1:21 PM, Karel Piwko wrote: > +1. Less JIRA instances, the better imho. > > Karel > > On Mon, 2015-01-05 at 11:32 +0100, Matthias Wessendorf wrote: > > Hi, > > > > > > right now we have three different types of 'push servers': > > * UPS > > * SimplePush > > * WebPush Server > > > > > > The first two ones each have their own JIRA, but I was wondering if we > > use the AGPUSH jira for all three. > > > > > > To manage releases and bugs, we will go with different/more > > components, and for the releases, we could do what we do successfully > > on our Cordova project. We can, in JIRA, have releases like: > > > > > > ups-1.3.0 > > sps-1.0.0 > > wps-0.2.0 > > > > > > That way would have all push (server) bits on the same JIRA and > > differentiation is simply done using components and versions as > > discussed above. > > > > > > 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/20150106/1c343e3f/attachment-0001.html From matzew at apache.org Tue Jan 6 06:55:14 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 6 Jan 2015 12:55:14 +0100 Subject: [aerogear-dev] UP console questions In-Reply-To: References: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Jan 6, 2015 at 11:35 AM, Daniel Passos wrote: > On Tue, Jan 6, 2015 at 6:57 AM, Matthias Wessendorf > wrote: > > >> >> On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante >> wrote: >> >>> Hey! >>> >>> I am working on the push console, and I have some questions: >>> >>> 1- What is the main action on the console? What is the main goal a user >>> want to achieve? >>> I notice that the console is center on creating and seeing up apps and >>> not so much in sending notifications. Is sending notifications usually done >>> on code and not the console? >>> >> >> the console is nice to send test messages. But in reality a backend (e.g. >> a MBaaS) will send a request to UPS to force it to deliver the push to >> Apple and GCM. >> >> The main goal is managaement (and overview/stats) around Apps, their >> Variants and their installations. >> >> >>> >>> 2- Under each app we have some information mixed with actions: >>> No variants - Activity - Send Push - admin >>> What does "admin" do, can an app be manage by other thats not the admin? >>> >> >> we allow to roles: >> * admin >> * user >> >> a user (like Andres or Matthias) can do all the CRUD actions. Andres see >> his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from >> both users Andres and Matthias >> >> >>> 3- Once you click on an app name you get a yellow box with "Sending push >>> notifications" set up information. But when you create a variant you also >>> get an specific info box for each variant. >>> What is the difference between them? >>> >> >> not sure what you are asking >> > The first box (*Sending push notifications*) when you create a new > application is a snippet of code to you use in you backend (using our > sender API[1]) to send a message to UPS and it delivery to the devices like > it[2]. The second box (*Registering installations*) when you create a > variant is a snippet of code to you use in you mobile app to register you > device in that application like it[3] > Ah, ok. I now think that the provide text/headers and icons for the two different boxes are perhaps not good enough. Andres, would it make sense to be more explicit there? I think some of what passos wrote could be perhaps baked into the boxes, right ? > [1] https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ > [2] > https://github.com/danielpassos/aerogear-jaxrs-backend/blob/master/src/main/java/me/passos/talks/aerogear/ProductService.java#L56-L69 > [3] > https://github.com/danielpassos/AeroProduct/blob/master/src/me/passos/talks/aerogear/AeroProductsApplication.java#L36-L60 > > >> >>> >>> Thanks! >> >> ? > > _______________________________________________ > 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/20150106/de6ae233/attachment.html From agalante at redhat.com Tue Jan 6 07:22:36 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 6 Jan 2015 07:22:36 -0500 (EST) Subject: [aerogear-dev] UP console questions In-Reply-To: References: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> Message-ID: <1130368354.745509.1420546956587.JavaMail.zimbra@redhat.com> Thanks Matthias and Daniel. This really helps. Matthias we do need to be more explicit along the way. For first time users we need a blank slate[1] followed by a wizard. Plus blank slate for each empty page (like no variants). We can't assume that everyone will read the documentation first. Apart from that we need to guide users as they set up backend and device configuration. I am working on all this and rearranging IA so it makes more sense. [1] https://dl.dropboxusercontent.com/u/4371641/blank.jpg ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Tuesday, January 6, 2015 8:55:14 AM Subject: Re: [aerogear-dev] UP console questions On Tue, Jan 6, 2015 at 11:35 AM, Daniel Passos < daniel at passos.me > wrote: On Tue, Jan 6, 2015 at 6:57 AM, Matthias Wessendorf < matzew at apache.org > wrote: On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante < agalante at redhat.com > wrote: Hey! I am working on the push console, and I have some questions: 1- What is the main action on the console? What is the main goal a user want to achieve? I notice that the console is center on creating and seeing up apps and not so much in sending notifications. Is sending notifications usually done on code and not the console? the console is nice to send test messages. But in reality a backend (e.g. a MBaaS) will send a request to UPS to force it to deliver the push to Apple and GCM. The main goal is managaement (and overview/stats) around Apps, their Variants and their installations. 2- Under each app we have some information mixed with actions: No variants - Activity - Send Push - admin What does "admin" do, can an app be manage by other thats not the admin? we allow to roles: * admin * user a user (like Andres or Matthias) can do all the CRUD actions. Andres see his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from both users Andres and Matthias 3- Once you click on an app name you get a yellow box with "Sending push notifications" set up information. But when you create a variant you also get an specific info box for each variant. What is the difference between them? not sure what you are asking The first box ( Sending push notifications ) when you create a new application is a snippet of code to you use in you backend (using our sender API[1]) to send a message to UPS and it delivery to the devices like it[2]. The second box ( Registering installations ) when you create a variant is a snippet of code to you use in you mobile app to register you device in that application like it[3] Ah, ok. I now think that the provide text/headers and icons for the two different boxes are perhaps not good enough. Andres, would it make sense to be more explicit there? I think some of what passos wrote could be perhaps baked into the boxes, right ? [1] https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ [2] https://github.com/danielpassos/aerogear-jaxrs-backend/blob/master/src/main/java/me/passos/talks/aerogear/ProductService.java#L56-L69 [3] https://github.com/danielpassos/AeroProduct/blob/master/src/me/passos/talks/aerogear/AeroProductsApplication.java#L36-L60 Thanks! ? _______________________________________________ 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 From matzew at apache.org Tue Jan 6 08:22:06 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 6 Jan 2015 14:22:06 +0100 Subject: [aerogear-dev] UP console questions In-Reply-To: <1130368354.745509.1420546956587.JavaMail.zimbra@redhat.com> References: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> <1130368354.745509.1420546956587.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Jan 6, 2015 at 1:22 PM, Andres Galante wrote: > Thanks Matthias and Daniel. This really helps. > > Matthias we do need to be more explicit along the way. > For first time users we need a blank slate[1] followed by a wizard. Plus > blank slate for each empty page (like no variants). We can't assume that > everyone will read the documentation first. > the notifications from GH are just an example here, right? And we would need this being applied to Push Apps and Variants, right? Because it's not the intention of the UPS console to actually read the notifcations. Sure the dashboard shows them and info, but thats more monitoring (e.g. did something go wrong while delivering to Apple/Google/Microsoft) > Apart from that we need to guide users as they set up backend and device > configuration. > yeah, we had previously thought about a better integration of our doc. The doc for the UPS is here: https://aerogear.org/docs/unifiedpush/ups_userguide/ > > I am working on all this and rearranging IA so it makes more sense. > > [1] https://dl.dropboxusercontent.com/u/4371641/blank.jpg > > ----- Original Message ----- > From: "Matthias Wessendorf" > To: "AeroGear Developer Mailing List" > Sent: Tuesday, January 6, 2015 8:55:14 AM > Subject: Re: [aerogear-dev] UP console questions > > > > On Tue, Jan 6, 2015 at 11:35 AM, Daniel Passos < daniel at passos.me > wrote: > > > > > > On Tue, Jan 6, 2015 at 6:57 AM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > > > > > > > On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Hey! > > I am working on the push console, and I have some questions: > > 1- What is the main action on the console? What is the main goal a user > want to achieve? > I notice that the console is center on creating and seeing up apps and not > so much in sending notifications. Is sending notifications usually done on > code and not the console? > > the console is nice to send test messages. But in reality a backend (e.g. > a MBaaS) will send a request to UPS to force it to deliver the push to > Apple and GCM. > > The main goal is managaement (and overview/stats) around Apps, their > Variants and their installations. > > > > 2- Under each app we have some information mixed with actions: > No variants - Activity - Send Push - admin > What does "admin" do, can an app be manage by other thats not the admin? > > we allow to roles: > * admin > * user > a user (like Andres or Matthias) can do all the CRUD actions. Andres see > his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from > both users Andres and Matthias > > > > > 3- Once you click on an app name you get a yellow box with "Sending push > notifications" set up information. But when you create a variant you also > get an specific info box for each variant. > What is the difference between them? > > not sure what you are asking > > > > > > > > The first box ( Sending push notifications ) when you create a new > application is a snippet of code to you use in you backend (using our > sender API[1]) to send a message to UPS and it delivery to the devices like > it[2]. The second box ( Registering installations ) when you create a > variant is a snippet of code to you use in you mobile app to register you > device in that application like it[3] > > Ah, ok. I now think that the provide text/headers and icons for the two > different boxes are perhaps not good enough. Andres, would it make sense to > be more explicit there? I think some of what passos wrote could be perhaps > baked into the boxes, right ? > > > > > > [1] https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ > [2] > https://github.com/danielpassos/aerogear-jaxrs-backend/blob/master/src/main/java/me/passos/talks/aerogear/ProductService.java#L56-L69 > [3] > https://github.com/danielpassos/AeroProduct/blob/master/src/me/passos/talks/aerogear/AeroProductsApplication.java#L36-L60 > > > > > > > > > > > Thanks! > > > > > > > ? > > _______________________________________________ > 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/20150106/cbf5cc7e/attachment-0001.html From agalante at redhat.com Tue Jan 6 08:39:14 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 6 Jan 2015 08:39:14 -0500 (EST) Subject: [aerogear-dev] UP console questions In-Reply-To: References: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> <1130368354.745509.1420546956587.JavaMail.zimbra@redhat.com> Message-ID: <867121725.753994.1420551554396.JavaMail.zimbra@redhat.com> Matthias, I was trying to show how GH handles screens when they are empty, it doesn't matter its NO notifications or NO variants or NO apps. The idea is what to show when there ir nothing to show :) Patternfly doesn't have a pattern for blank slates, so we are discussing with the UX team how to show them on our consoles. It will probably follow what we do on our console. ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Tuesday, January 6, 2015 10:22:06 AM Subject: Re: [aerogear-dev] UP console questions On Tue, Jan 6, 2015 at 1:22 PM, Andres Galante < agalante at redhat.com > wrote: Thanks Matthias and Daniel. This really helps. Matthias we do need to be more explicit along the way. For first time users we need a blank slate[1] followed by a wizard. Plus blank slate for each empty page (like no variants). We can't assume that everyone will read the documentation first. the notifications from GH are just an example here, right? And we would need this being applied to Push Apps and Variants, right? Because it's not the intention of the UPS console to actually read the notifcations. Sure the dashboard shows them and info, but thats more monitoring (e.g. did something go wrong while delivering to Apple/Google/Microsoft) Apart from that we need to guide users as they set up backend and device configuration. yeah, we had previously thought about a better integration of our doc. The doc for the UPS is here: https://aerogear.org/docs/unifiedpush/ups_userguide/ I am working on all this and rearranging IA so it makes more sense. [1] https://dl.dropboxusercontent.com/u/4371641/blank.jpg ----- Original Message ----- From: "Matthias Wessendorf" < matzew at apache.org > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Tuesday, January 6, 2015 8:55:14 AM Subject: Re: [aerogear-dev] UP console questions On Tue, Jan 6, 2015 at 11:35 AM, Daniel Passos < daniel at passos.me > wrote: On Tue, Jan 6, 2015 at 6:57 AM, Matthias Wessendorf < matzew at apache.org > wrote: On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante < agalante at redhat.com > wrote: Hey! I am working on the push console, and I have some questions: 1- What is the main action on the console? What is the main goal a user want to achieve? I notice that the console is center on creating and seeing up apps and not so much in sending notifications. Is sending notifications usually done on code and not the console? the console is nice to send test messages. But in reality a backend (e.g. a MBaaS) will send a request to UPS to force it to deliver the push to Apple and GCM. The main goal is managaement (and overview/stats) around Apps, their Variants and their installations. 2- Under each app we have some information mixed with actions: No variants - Activity - Send Push - admin What does "admin" do, can an app be manage by other thats not the admin? we allow to roles: * admin * user a user (like Andres or Matthias) can do all the CRUD actions. Andres see his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from both users Andres and Matthias 3- Once you click on an app name you get a yellow box with "Sending push notifications" set up information. But when you create a variant you also get an specific info box for each variant. What is the difference between them? not sure what you are asking The first box ( Sending push notifications ) when you create a new application is a snippet of code to you use in you backend (using our sender API[1]) to send a message to UPS and it delivery to the devices like it[2]. The second box ( Registering installations ) when you create a variant is a snippet of code to you use in you mobile app to register you device in that application like it[3] Ah, ok. I now think that the provide text/headers and icons for the two different boxes are perhaps not good enough. Andres, would it make sense to be more explicit there? I think some of what passos wrote could be perhaps baked into the boxes, right ? [1] https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ [2] https://github.com/danielpassos/aerogear-jaxrs-backend/blob/master/src/main/java/me/passos/talks/aerogear/ProductService.java#L56-L69 [3] https://github.com/danielpassos/AeroProduct/blob/master/src/me/passos/talks/aerogear/AeroProductsApplication.java#L36-L60 Thanks! ? _______________________________________________ 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 From lholmqui at redhat.com Tue Jan 6 08:40:01 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 6 Jan 2015 08:40:01 -0500 Subject: [aerogear-dev] POC - Service Workers and Conflict Resolution In-Reply-To: References: <64AD907E-AA9E-4B06-B021-5CFE20AF41F7@redhat.com> Message-ID: <1D97221E-C64D-460F-A61E-580CB4B6F4CB@redhat.com> > On Jan 6, 2015, at 3:38 AM, Luk?? Fry? wrote: > > It is very good idea, and a nice way how to integrate with existing libraries. > > It shields user from one round of conflict resolution handling. > > I have created a small diagram to better understand that and it revealed one more fact: > > https://docs.google.com/drawings/d/1vIqYjfukHwb9HVuYAlf9eO5U_Eopgl9EOZyG22wEV2s/edit?usp=sharing > > As seen on the diagram, user would still have to Merge on the programmatic layer, where we could offer a DiffMatchPatch alghoritm, i think i use that algorithm in the repo example > and/or integration with selected existing libraries (e.g. AngularJS ResoureProvider or Restangular or similar Ember approach). correct, however that particular lib deals with a 409 error, then they can keep doing what they are doing > > I believe we don't have to handle "I work for second and later requests" problem you mentioned in the blog, since I assume ServiceWorker will react on the REST calls from the application once it is registered (not sure that's the case). That's with a question mark. :-) this section explains this a little more: https://github.com/slightlyoff/ServiceWorker/blob/master/explainer.md#so-im-controlling-pages-now however the last line : ?However, a ServiceWorker can call event.replace() during the install event to do an immediate takeover of all pages within scope? i?m not sure if that means ?take over the page without having to refresh? or not. i will play with that > > On Mon, Jan 5, 2015 at 6:15 PM, Daniel Bevenius > wrote: > nice work! > > m?ndag 5 januari 2015 skrev Lucas Holmquist >: > > Here is my blog post on using Service Workers for Conflict Resolution > > > http://blog.lholmquist.org/service-workers-can-settle-conflicts-too/ > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150106/1d91c3ee/attachment.html From agalante at redhat.com Tue Jan 6 09:00:39 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 6 Jan 2015 09:00:39 -0500 (EST) Subject: [aerogear-dev] UP console questions In-Reply-To: References: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> <1130368354.745509.1420546956587.JavaMail.zimbra@redhat.com> Message-ID: <1837698768.757349.1420552839950.JavaMail.zimbra@redhat.com> just a little bit more about black slates: "First impressions are crucial. If you fail to design a thoughtful blank slate, you'll create a negative (and false) impression of your application or service." https://gettingreal.37signals.com/ch09_The_Blank_Slate.php ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Tuesday, January 6, 2015 10:22:06 AM Subject: Re: [aerogear-dev] UP console questions On Tue, Jan 6, 2015 at 1:22 PM, Andres Galante < agalante at redhat.com > wrote: Thanks Matthias and Daniel. This really helps. Matthias we do need to be more explicit along the way. For first time users we need a blank slate[1] followed by a wizard. Plus blank slate for each empty page (like no variants). We can't assume that everyone will read the documentation first. the notifications from GH are just an example here, right? And we would need this being applied to Push Apps and Variants, right? Because it's not the intention of the UPS console to actually read the notifcations. Sure the dashboard shows them and info, but thats more monitoring (e.g. did something go wrong while delivering to Apple/Google/Microsoft) Apart from that we need to guide users as they set up backend and device configuration. yeah, we had previously thought about a better integration of our doc. The doc for the UPS is here: https://aerogear.org/docs/unifiedpush/ups_userguide/ I am working on all this and rearranging IA so it makes more sense. [1] https://dl.dropboxusercontent.com/u/4371641/blank.jpg ----- Original Message ----- From: "Matthias Wessendorf" < matzew at apache.org > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Tuesday, January 6, 2015 8:55:14 AM Subject: Re: [aerogear-dev] UP console questions On Tue, Jan 6, 2015 at 11:35 AM, Daniel Passos < daniel at passos.me > wrote: On Tue, Jan 6, 2015 at 6:57 AM, Matthias Wessendorf < matzew at apache.org > wrote: On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante < agalante at redhat.com > wrote: Hey! I am working on the push console, and I have some questions: 1- What is the main action on the console? What is the main goal a user want to achieve? I notice that the console is center on creating and seeing up apps and not so much in sending notifications. Is sending notifications usually done on code and not the console? the console is nice to send test messages. But in reality a backend (e.g. a MBaaS) will send a request to UPS to force it to deliver the push to Apple and GCM. The main goal is managaement (and overview/stats) around Apps, their Variants and their installations. 2- Under each app we have some information mixed with actions: No variants - Activity - Send Push - admin What does "admin" do, can an app be manage by other thats not the admin? we allow to roles: * admin * user a user (like Andres or Matthias) can do all the CRUD actions. Andres see his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from both users Andres and Matthias 3- Once you click on an app name you get a yellow box with "Sending push notifications" set up information. But when you create a variant you also get an specific info box for each variant. What is the difference between them? not sure what you are asking The first box ( Sending push notifications ) when you create a new application is a snippet of code to you use in you backend (using our sender API[1]) to send a message to UPS and it delivery to the devices like it[2]. The second box ( Registering installations ) when you create a variant is a snippet of code to you use in you mobile app to register you device in that application like it[3] Ah, ok. I now think that the provide text/headers and icons for the two different boxes are perhaps not good enough. Andres, would it make sense to be more explicit there? I think some of what passos wrote could be perhaps baked into the boxes, right ? [1] https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ [2] https://github.com/danielpassos/aerogear-jaxrs-backend/blob/master/src/main/java/me/passos/talks/aerogear/ProductService.java#L56-L69 [3] https://github.com/danielpassos/AeroProduct/blob/master/src/me/passos/talks/aerogear/AeroProductsApplication.java#L36-L60 Thanks! ? _______________________________________________ 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 From lholmqui at redhat.com Tue Jan 6 09:37:29 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 6 Jan 2015 09:37:29 -0500 Subject: [aerogear-dev] Concern with es6 modules and AeroGear.js Message-ID: for those of you don?t use http based email, i?m looking at you qmx and abstractj, this might be a little ugly I want to start off by saying that i think ES6 modules are cool and that i like them. I think the concern that i have in their current state is that there is to much "processesing" that needs to be done to make them work with existing browsers. While this processing is done with automated grunt tasks, i feel that it puts to much "extra" code in the library for not that much reward. Another concern with the processing is that it adds lots more development dependecies. One of which is upgrading to npm 2.0, which wasn't as straightforward as i was thinking. I do want to commend Lukas, for all his hard work on the es6 modules branch, Good Work My Friend!! As "developers on the edge"? we are exposed to new shiny tech that we want to use right away like modules, AMD, browserfy, etc... But i wonder about the other 90% and what they are looking for. Do they even care about AMD, etc... I think as a mobile library, we need to not add extra overhead. But i think we should keep working on the ES6-modules branch and keep it up to date and direct people to that if they would like to try it. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150106/0c9bdb3b/attachment-0001.html From matzew at apache.org Tue Jan 6 09:47:34 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 6 Jan 2015 15:47:34 +0100 Subject: [aerogear-dev] UP console questions In-Reply-To: <867121725.753994.1420551554396.JavaMail.zimbra@redhat.com> References: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> <817988044.640236.1420476807864.JavaMail.zimbra@redhat.com> <1130368354.745509.1420546956587.JavaMail.zimbra@redhat.com> <867121725.753994.1420551554396.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Jan 6, 2015 at 2:39 PM, Andres Galante wrote: > Matthias, I was trying to show how GH handles screens when they are empty, > it doesn't matter its NO notifications or NO variants or NO apps. The idea > is what to show when there ir nothing to show :) > > Patternfly doesn't have a pattern for blank slates, so we are discussing > with the UX team how to show them on our consoles. It will probably follow > what we do on our console. > +1 sounds good, integrating this theme into patternfly > > > ----- Original Message ----- > From: "Matthias Wessendorf" > To: "AeroGear Developer Mailing List" > Sent: Tuesday, January 6, 2015 10:22:06 AM > Subject: Re: [aerogear-dev] UP console questions > > > > On Tue, Jan 6, 2015 at 1:22 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Thanks Matthias and Daniel. This really helps. > > Matthias we do need to be more explicit along the way. > For first time users we need a blank slate[1] followed by a wizard. Plus > blank slate for each empty page (like no variants). We can't assume that > everyone will read the documentation first. > > the notifications from GH are just an example here, right? And we would > need this being applied to Push Apps and Variants, right? > Because it's not the intention of the UPS console to actually read the > notifcations. Sure the dashboard shows them and info, but thats more > monitoring (e.g. did something go wrong while delivering to > Apple/Google/Microsoft) > > > Apart from that we need to guide users as they set up backend and device > configuration. > > yeah, we had previously thought about a better integration of our doc. The > doc for the UPS is here: > https://aerogear.org/docs/unifiedpush/ups_userguide/ > > > > I am working on all this and rearranging IA so it makes more sense. > > [1] https://dl.dropboxusercontent.com/u/4371641/blank.jpg > > ----- Original Message ----- > From: "Matthias Wessendorf" < matzew at apache.org > > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > > Sent: Tuesday, January 6, 2015 8:55:14 AM > Subject: Re: [aerogear-dev] UP console questions > > > > On Tue, Jan 6, 2015 at 11:35 AM, Daniel Passos < daniel at passos.me > wrote: > > > > > > On Tue, Jan 6, 2015 at 6:57 AM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > > > > > > > On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Hey! > > I am working on the push console, and I have some questions: > > 1- What is the main action on the console? What is the main goal a user > want to achieve? > I notice that the console is center on creating and seeing up apps and not > so much in sending notifications. Is sending notifications usually done on > code and not the console? > > the console is nice to send test messages. But in reality a backend (e.g. > a MBaaS) will send a request to UPS to force it to deliver the push to > Apple and GCM. > > The main goal is managaement (and overview/stats) around Apps, their > Variants and their installations. > > > > 2- Under each app we have some information mixed with actions: > No variants - Activity - Send Push - admin > What does "admin" do, can an app be manage by other thats not the admin? > > we allow to roles: > * admin > * user > a user (like Andres or Matthias) can do all the CRUD actions. Andres see > his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from > both users Andres and Matthias > > > > > 3- Once you click on an app name you get a yellow box with "Sending push > notifications" set up information. But when you create a variant you also > get an specific info box for each variant. > What is the difference between them? > > not sure what you are asking > > > > > > > > The first box ( Sending push notifications ) when you create a new > application is a snippet of code to you use in you backend (using our > sender API[1]) to send a message to UPS and it delivery to the devices like > it[2]. The second box ( Registering installations ) when you create a > variant is a snippet of code to you use in you mobile app to register you > device in that application like it[3] > > Ah, ok. I now think that the provide text/headers and icons for the two > different boxes are perhaps not good enough. Andres, would it make sense to > be more explicit there? I think some of what passos wrote could be perhaps > baked into the boxes, right ? > > > > > > [1] https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ > [2] > https://github.com/danielpassos/aerogear-jaxrs-backend/blob/master/src/main/java/me/passos/talks/aerogear/ProductService.java#L56-L69 > [3] > https://github.com/danielpassos/AeroProduct/blob/master/src/me/passos/talks/aerogear/AeroProductsApplication.java#L36-L60 > > > > > > > > > > > Thanks! > > > > > > > ? > > _______________________________________________ > 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/20150106/4bb74423/attachment.html From matzew at apache.org Tue Jan 6 09:52:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 6 Jan 2015 15:52:41 +0100 Subject: [aerogear-dev] Concern with es6 modules and AeroGear.js In-Reply-To: References: Message-ID: On Tue, Jan 6, 2015 at 3:37 PM, Lucas Holmquist wrote: > for those of you don?t use http based email, i?m looking at you qmx and > abstractj, this might be a little ugly > > > > I want to start off by saying that i think ES6 modules are cool and that i > like them. > > I think the concern that i have in their current state is that there is to > much "processesing" that needs to be done to make them work with existing > browsers. > > While this processing is done with automated grunt tasks, i feel that it > puts to much "extra" code in the library for not that much reward. > and therefore being slower than it should be right? legacy browsers ftw :) > Another concern with the processing is that it adds lots more development > dependecies. One of which is upgrading to npm 2.0, which wasn't as > straightforward as i was thinking. > ouch > I do want to commend Lukas, for all his hard work on the es6 modules > branch, Good Work My Friend!! > > As "developers on the edge"? we are exposed to new shiny tech that we want > to use right away like modules, AMD, browserfy, etc... > > But i wonder about the other 90% and what they are looking for. Do they > even care about AMD, etc... > perhaps not, or not yet - especially when coming from "web development" for intranet apps, in traditional shops > I think as a mobile library, we need to not add extra overhead. > +9001 > But i think we should keep working on the ES6-modules branch and keep it > up to date and direct people to that if they would like to try it. > I fully agree - also this is not throwing away work. This was a needed research, we came to a conclusion: not yet ready; but that does not mean, we won't be looking at it again, let's say in two years or so. times are changing fast. great job, Luke and Lucas! > > _______________________________________________ > 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/20150106/9e38b88c/attachment.html From lukas.fryc at gmail.com Tue Jan 6 10:45:01 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 6 Jan 2015 16:45:01 +0100 Subject: [aerogear-dev] Concern with es6 modules and AeroGear.js In-Reply-To: References: Message-ID: TL;DR: agree with keeping the ES6 on the branch --- Keeping aside the personal preference, I believe that ES6 modules have huge potential in mobile applications space since they are bringing so-needed structure and thus allow for compile-time optimizations (that are even more crucial on mobile than on desktop). But as Luke said, this is not feature that would talk to everyone. What we got in ES6 branch is a solution that works for: * global namespace users * people preferring browser modules (AMD, but CommonJS is possible) * people looking into the future with ES6 But how many people preferring one or another form of modules we can find? I would agree with Luke's 10% of users considering the use of modules, and fraction of it using in current projects. Unless we won't be proved to be wrong and we find a community members really trying the ES6 branch, I would stay aside of it as suggested. Our research definitely helped to prepare a path and if nothing else, it helped me understand deeply both, the Aerogear.js code and its build process. On Tue, Jan 6, 2015 at 3:52 PM, Matthias Wessendorf wrote: > > > On Tue, Jan 6, 2015 at 3:37 PM, Lucas Holmquist > wrote: > >> for those of you don?t use http based email, i?m looking at you qmx and >> abstractj, this might be a little ugly >> >> >> >> I want to start off by saying that i think ES6 modules are cool and that >> i like them. >> >> I think the concern that i have in their current state is that there is >> to much "processesing" that needs to be done to make them work with >> existing browsers. >> >> While this processing is done with automated grunt tasks, i feel that it >> puts to much "extra" code in the library for not that much reward. >> > > and therefore being slower than it should be right? legacy browsers ftw :) > > > > >> Another concern with the processing is that it adds lots more development >> dependecies. One of which is upgrading to npm 2.0, which wasn't as >> straightforward as i was thinking. >> > > ouch > > >> I do want to commend Lukas, for all his hard work on the es6 modules >> branch, Good Work My Friend!! >> >> As "developers on the edge"? we are exposed to new shiny tech that we >> want to use right away like modules, AMD, browserfy, etc... >> >> But i wonder about the other 90% and what they are looking for. Do they >> even care about AMD, etc... >> > perhaps not, or not yet - especially when coming from "web development" > for intranet apps, in traditional shops > > > >> I think as a mobile library, we need to not add extra overhead. >> > > +9001 > > > >> But i think we should keep working on the ES6-modules branch and keep it >> up to date and direct people to that if they would like to try it. >> > > I fully agree - also this is not throwing away work. This was a needed > research, we came to a conclusion: not yet ready; but that does not mean, > we won't be looking at it again, let's say in two years or so. times are > changing fast. > > great job, Luke and Lucas! > > >> >> _______________________________________________ >> 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/20150106/4768090a/attachment-0001.html From matzew at apache.org Tue Jan 6 11:09:56 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 6 Jan 2015 17:09:56 +0100 Subject: [aerogear-dev] New page - initial feed back (was: Re: Aerogear.org redesign) Message-ID: Hey Andres, awesome job on the new design - I love it! *Home I love the animation, on initial browsing. Not sure it's great to always have it, when clicking on the 'Home' link *Modules Not 100% sure on 'Core'. I am overasked here atm. sorry, will get to this later. Others please jump in :-) Perhaps we need a few more modules, like OAuth2, and Offline *Get started Is it possible to highlight the current section? E.g. I clicked Demos and when I click the 'Get started' again, it would be nice to have a highlighted 'Demos' link, to indicate I am on demos. *Docs On "Docs/Road Maps", not sure I understand the "AeroGear Core Project" and its "Aerogear Jira latest update", "Aerogear Github latest update" children. Let's remove that. But guess this was just "dummy text"? *Community - is the team info pulled from somewhere? I think Sebi's location is incorrect - the contributors is perhaps also not up-to-date :-) * News Would it be possible to apply the new layout to the existing one, so that we get our iteration of actual blog posts ? IMO what's left is content, but that's fine :) Andres, again, it's a great site, and it looks so professional! great job!! Greetings, Matthias On Mon, Jan 5, 2015 at 3:28 PM, Matthias Wessendorf wrote: > oh, wow - that looks great! love it > > On Mon, Jan 5, 2015 at 2:10 PM, Andres Galante > wrote: > >> Hi! >> Can you test this color: >> https://dl.dropboxusercontent.com/u/4371641/orange_final.jpg >> >> Does it still hurt your eyes? >> >> >> ----- Original Message ----- >> From: "Luk?? Fry?" >> To: "AeroGear Developer Mailing List" >> Sent: Monday, January 5, 2015 5:28:39 AM >> Subject: Re: [aerogear-dev] Aerogear.org redesign >> >> Hey guys, >> >> I believe we should get the page on today's meeting agenda to determine >> next steps (content-wise). >> >> From the another thread, I've closed the poll for the colours and at the >> end, the current Blue won our hearts. Just people seem to not like the >> yellow colours for some widgets. >> >> @Andres, could you possibly look at the yellow coloring - change it to >> something more eye pleasant, maybe orange? >> >> I'm also taking look at bringing some more dynamic content to the page. >> >> >> Cheers! >> >> ~ Lukas >> >> On Tue, Dec 23, 2014 at 4:23 PM, Andres Galante < agalante at redhat.com > >> wrote: >> >> >> Hi! >> I don't think there is much more I can do on the website by my own. I'll >> need your help to: >> >> - Write text and correct typos. There is text to write on Homepage, >> Modules (add more text for each module) and Guides, you'll notice the Lorem >> ipsum :) >> >> - Review the structure for Downloads, Guides and Specs >> >> - What logos to put on the homepage footer >> >> - Review styles and design. Did I forget to change anything that was >> requested? >> >> We can discuss this in january when everyone is back. For the ones that >> are around: Happy holidays :) >> >> Thanks! >> >> Andr?s >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150106/9945e6cb/attachment.html From cvasilak at gmail.com Tue Jan 6 11:12:53 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Tue, 6 Jan 2015 18:12:53 +0200 Subject: [aerogear-dev] iOS team meeting In-Reply-To: <967BA31E-5D4F-4DC3-92F5-E0AF150A1A05@gmail.com> References: <967BA31E-5D4F-4DC3-92F5-E0AF150A1A05@gmail.com> Message-ID: fyi, meeting minutes: Meeting ended Tue Jan 6 16:08:18 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-01-06-15.44.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-06-15.44.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-06-15.44.log.html On Tue, Jan 6, 2015 at 11:44 AM, Corinne Krych wrote: > Hello all, > > Our iOS meeting will take place this afternoon, usual time 4pm. Here is > the agenda: > > http://oksoclap.com/p/ios_meeting_6th_January_2015 > > ++ > 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/20150106/005e7b19/attachment.html From agalante at redhat.com Tue Jan 6 12:07:06 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 6 Jan 2015 12:07:06 -0500 (EST) Subject: [aerogear-dev] New page - initial feed back (was: Re: Aerogear.org redesign) In-Reply-To: References: Message-ID: <1156760456.793832.1420564026935.JavaMail.zimbra@redhat.com> ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Tuesday, January 6, 2015 1:09:56 PM Subject: [aerogear-dev] New page - initial feed back (was: Re: Aerogear.org redesign) Hey Andres, awesome job on the new design - I love it! *Home I love the animation, on initial browsing. Not sure it's great to always have it, when clicking on the 'Home' link This is a css class that makes the animation work. Lukas can you do some js magic to remove that class after the first run? *Modules Not 100% sure on 'Core'. I am overasked here atm. sorry, will get to this later. Others please jump in :-) Perhaps we need a few more modules, like OAuth2, and Offline *Get started Is it possible to highlight the current section? E.g. I clicked Demos and when I click the 'Get started' again, it would be nice to have a highlighted 'Demos' link, to indicate I am on demos. *Docs On "Docs/Road Maps", not sure I understand the "AeroGear Core Project" and its "Aerogear Jira latest update", "Aerogear Github latest update" children. Let's remove that. But guess this was just "dummy text"? "AeroGear Core Project" is something that was there when I pick the project. Jira and github updates is an idea we had of showing Jira and github activity. We can remove it. *Community - is the team info pulled from somewhere? I think Sebi's location is incorrect It is hardcoded on /_data/team.yml we can make it to can pull info from github or we can just updated it whenever some wants to. - the contributors is perhaps also not up-to-date :-) This is going to pull info from github. Lukas is working on it * News Would it be possible to apply the new layout to the existing one, so that we get our iteration of actual blog posts ? Yes, Lukas is taking care of it. The idea is to also pull info about events, videos or external blogposts related to aerogear. And show that also on the homepage. IMO what's left is content, but that's fine :) Andres, again, it's a great site, and it looks so professional! great job!! Greetings, Matthias On Mon, Jan 5, 2015 at 3:28 PM, Matthias Wessendorf < matzew at apache.org > wrote: oh, wow - that looks great! love it On Mon, Jan 5, 2015 at 2:10 PM, Andres Galante < agalante at redhat.com > wrote: Hi! Can you test this color: https://dl.dropboxusercontent.com/u/4371641/orange_final.jpg Does it still hurt your eyes? ----- Original Message ----- From: "Luk?? Fry?" < lukas.fryc at gmail.com > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Monday, January 5, 2015 5:28:39 AM Subject: Re: [aerogear-dev] Aerogear.org redesign Hey guys, I believe we should get the page on today's meeting agenda to determine next steps (content-wise). >From the another thread, I've closed the poll for the colours and at the end, the current Blue won our hearts. Just people seem to not like the yellow colours for some widgets. @Andres, could you possibly look at the yellow coloring - change it to something more eye pleasant, maybe orange? I'm also taking look at bringing some more dynamic content to the page. Cheers! ~ Lukas On Tue, Dec 23, 2014 at 4:23 PM, Andres Galante < agalante at redhat.com > wrote: Hi! I don't think there is much more I can do on the website by my own. I'll need your help to: - Write text and correct typos. There is text to write on Homepage, Modules (add more text for each module) and Guides, you'll notice the Lorem ipsum :) - Review the structure for Downloads, Guides and Specs - What logos to put on the homepage footer - Review styles and design. Did I forget to change anything that was requested? We can discuss this in january when everyone is back. For the ones that are around: Happy holidays :) Thanks! Andr?s _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.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 From matzew at apache.org Tue Jan 6 15:19:54 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 6 Jan 2015 21:19:54 +0100 Subject: [aerogear-dev] New page - initial feed back (was: Re: Aerogear.org redesign) In-Reply-To: <1156760456.793832.1420564026935.JavaMail.zimbra@redhat.com> References: <1156760456.793832.1420564026935.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Jan 6, 2015 at 6:07 PM, Andres Galante wrote: > > > ----- Original Message ----- > From: "Matthias Wessendorf" > To: "AeroGear Developer Mailing List" > Sent: Tuesday, January 6, 2015 1:09:56 PM > Subject: [aerogear-dev] New page - initial feed back (was: Re: > Aerogear.org redesign) > > Hey Andres, > > awesome job on the new design - I love it! > > *Home > > I love the animation, on initial browsing. Not sure it's great to always > have it, when clicking on the 'Home' link > > This is a css class that makes the animation work. Lukas can you do some > js magic to remove that class after the first run? > > *Modules > > Not 100% sure on 'Core'. I am overasked here atm. sorry, will get to this > later. Others please jump in :-) > > Perhaps we need a few more modules, like OAuth2, and Offline > > *Get started > > Is it possible to highlight the current section? E.g. I clicked Demos and > when I click the 'Get started' again, it would be nice to have a > highlighted 'Demos' link, to indicate I am on demos. > > *Docs > > On "Docs/Road Maps", not sure I understand the "AeroGear Core Project" and > its "Aerogear Jira latest update", "Aerogear Github latest update" > children. Let's remove that. But guess this was just "dummy text"? > > "AeroGear Core Project" is something that was there when I pick the > project. > Jira and github updates is an idea we had of showing Jira and github > activity. We can remove it. > +1 also removing is part of the content work ;-) I was mainly reviewing from structure and design perspective > > *Community > > - is the team info pulled from somewhere? I think Sebi's location is > incorrect > It is hardcoded on /_data/team.yml we can make it to can pull info from > github or we can just updated it whenever some wants to. > > - the contributors is perhaps also not up-to-date :-) > This is going to pull info from github. Lukas is working on it > awesome, thanks Lukas > > * News > > Would it be possible to apply the new layout to the existing one, so that > we get our iteration of actual blog posts ? > > Yes, Lukas is taking care of it. The idea is to also pull info about > events, videos or external blogposts related to aerogear. And show that > also on the homepage. > cool! I really like the work of this effort. good job everyone! > > > IMO what's left is content, but that's fine :) Andres, again, it's a great > site, and it looks so professional! great job!! > > > Greetings, > Matthias > > On Mon, Jan 5, 2015 at 3:28 PM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > oh, wow - that looks great! love it > > On Mon, Jan 5, 2015 at 2:10 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Hi! > Can you test this color: > https://dl.dropboxusercontent.com/u/4371641/orange_final.jpg > > Does it still hurt your eyes? > > > ----- Original Message ----- > From: "Luk?? Fry?" < lukas.fryc at gmail.com > > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > > Sent: Monday, January 5, 2015 5:28:39 AM > Subject: Re: [aerogear-dev] Aerogear.org redesign > > Hey guys, > > I believe we should get the page on today's meeting agenda to determine > next steps (content-wise). > > >From the another thread, I've closed the poll for the colours and at the > end, the current Blue won our hearts. Just people seem to not like the > yellow colours for some widgets. > > @Andres, could you possibly look at the yellow coloring - change it to > something more eye pleasant, maybe orange? > > I'm also taking look at bringing some more dynamic content to the page. > > > Cheers! > > ~ Lukas > > On Tue, Dec 23, 2014 at 4:23 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Hi! > I don't think there is much more I can do on the website by my own. I'll > need your help to: > > - Write text and correct typos. There is text to write on Homepage, > Modules (add more text for each module) and Guides, you'll notice the Lorem > ipsum :) > > - Review the structure for Downloads, Guides and Specs > > - What logos to put on the homepage footer > > - Review styles and design. Did I forget to change anything that was > requested? > > We can discuss this in january when everyone is back. For the ones that > are around: Happy holidays :) > > Thanks! > > Andr?s > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150106/6b5e640c/attachment-0001.html From scm.blanc at gmail.com Wed Jan 7 03:59:02 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 7 Jan 2015 09:59:02 +0100 Subject: [aerogear-dev] [POC] Unified Geo Server In-Reply-To: <791508465.52269.1419097333413.JavaMail.yahoo@jws10001g.mail.ne1.yahoo.com> References: <791508465.52269.1419097333413.JavaMail.yahoo@jws10001g.mail.ne1.yahoo.com> Message-ID: On Sat, Dec 20, 2014 at 6:42 PM, Raj Nukala wrote: > This is great . > Thx > I missed the screencast is there a recording somewhere? > Sure, you can watch it here https://www.youtube.com/watch?v=R-qdLJh4EWQ > For my project i need geofencing features and if only this is well > documented and there is a binary i would love to use it . > It's not (yet) related to the Geo Server but we have a geofencing Cordova plugin : https://github.com/aerogear/aerogear-geo-cordova > > Regards > Raj > > ------------------------------ > *From:* Matthias Wessendorf > *To:* AeroGear Developer Mailing List > *Sent:* Tuesday, December 16, 2014 12:13 AM > *Subject:* Re: [aerogear-dev] [POC] Unified Geo Server > > > > On Mon, Dec 15, 2014 at 11:32 PM, Bruno Oliveira > wrote: > > On 2014-12-15, Matthias Wessendorf wrote: > > On Mon, Dec 15, 2014 at 9:08 PM, Bruno Oliveira > wrote: > > > > > > Good morning, first nice screencast Sebi and even knowing this is just > a > > > PoC I have some considerations: > > > > > > 1. What would be the use case scenario to justify a separated server > > > instead of just a module on AGPUSH? > > > > > > > I think main discussion around this at F2F meeting was, it might be > useful > > for other scenarios as well, > > and we don't want to hard-wire geo to the push server > > Which scenarios? > > > anything else that may require geo data. E.g. other systems may benefit > from interacting with geo as well. > I really do not see a reason why geo is hard-wired to push. > > the geo server should be a system to store any sorts of geo data > (long/lat) + some APIs to query. > > > > > > > > > > > > > > > > 2. How do you plan to prevent people from faking their location? > > > > > > > I'd assume that a Geo SDK would be based on-top of the mobile OS's > > facility, to receive the long/lat values. > > I think in the future we can have some sort of checks, like validating > the > > users IP address, if it somewhat matches the submitted geo data. > > I think Geo based on IPs are a bad idea. This is a very inaccurate method > and should be our last resort, it's easy to spoof IPs. > > > :-) yeah. I'd assume that we offer minimal/simple SDKs for iOS/Android, > which underneath > leverage the OS facilities for Geo-Data. Like CoreLocation on iOS. > > Regarding the IP, I had this in mind (not sure if that is a good idea or > not): > * if long/lat (can be faked with man-in-the-middle) says Germany, but IP > says singapore, > our server could see: something is wrong. > > or if we get weird long/lats from the same device (.e.g. 12:00 Germany, > 12:30 UK, 14:00 USA, 14:30 China), > we might know something is wrong too. But that's perhaps not for the > initial scope of the poc > > > > > > > > > > > > > > 3. Do we have a privacy policy to make the developer real aware about > > > what's being collected? > > > > > > > I think that the level of collected geo data is up to the developer of > the > > app, using the Geo SDK. > > I'm sorry, but I have to disagree. If we don't provide a policy about the > usage of the Geo > server, we're pretty much accountable for it. > > Nothing huge, only a simple txt documenting what's being collected and > why. > > > I'd think that, if we provide an SDK (and the POC will get us there), we > do not really track anything 'silently'. > I hope that the SDK would allow me to get the current position (e.g. using > CoreLocation), and store it with a name (e.g. home, work, my fav. cinema) > and some metadata (e.g. username). > > But I'd not imagine our SDK constantly tracks all positions and silently > sends them to the Geo Server. > > > > > > > > > > > > > > > 4. Will collecting geo location be opt in or default? > > > > > > > If the Geo-data SDK is used w/in an app, I think it will still ask, > > up-front, if location based services are OK to use (at least apple). And > > I'd argue that users can still disable the geo usage, per app (at least > > apple) > > Most of users have no idea that their data is being collected. I'm > confused about your answer, is that an yes or no? > > > I mean yes, see above. > > > -MAtthias > > > > > > > > > > > > > > > > 5. Why is necessary to store current user's position? > > > > > > I think that's up to the use case, and its usage of the Geo SDK. > > Currently we store. I know this is just a proof of concept. > But I insist to be the boring, and avoid it if possible. > > > > > > > > > Couldn't admin > > > specify a range and check how many devices are active on that region? > > > Into this way you don't need to store their positions. I'm not the Geo > > > specialist here but the idea is: > > > > > > 1. Admin specify the range when a push message must be sent. For > > > example: Whole Florida > > > 2. Client opt in and sent her its position to the server > > > 3. Server compares and sent the push message > > > > > > I'm very concerned about privacy here, I'm not against the > > > solution, but Geo location is like to open a Pandora box. > > > > > > > yeah, it's also creepy :) I have not much services that I give my geo > data > > > > > > > > > > We might be careful about unintentional disclosure of geolocation > > > information, > > > because it carries physical risks to the client (theft, to stalking, > > > kidnapping > > > and domestic violence ? I'm not exaggerating). > > > > > > > +1 I'd argue that the "Geo server" would be, initially, a 'simple' back > > end, that is able to store n pairs of long/lat values (grouped by a > > user/device). > > The mobile SDK for it basically store the 'collected' data to this > backend > > (somewhat similar to the push registration SDK) > > > > > > > > > > Again, I know this is a proof of concept, but sooner we have it in > mind, > > > the > > > better. > > > > > > > +1 fully agree. Replied to your questions with my POV on this > > > > > > > > > > > > > > > > > > > > > On 2014-12-10, Sebastien Blanc wrote: > > > > Hi all, > > > > > > > > I have been working on a POC around geolocation. Like we discussed in > > > > another thread, we decided not to have a "deep" integration with the > Push > > > > server but instead a separate component / microservice. Well the POC > is > > > > more a miniservice ;) > > > > > > > > So, the idea is to have a server to which devices can register by > > > providing > > > > their positions. On the other side, the server provide an endpoint to > > > make > > > > spatial queries, like give me all the installations within a radius > of 10 > > > > km around this lat/ltg. > > > > > > > > Thanks to Forge, I created/scaffolded a really simple server > providing > > > the > > > > registration endpoint and the search endpoint. > > > > > > > > I tried to make a decent readme that will give you more details : > > > > > > > > https://github.com/sebastienblanc/unified-geo-server > > > > > > > > And as usual, I made a little screencast showing all that in action > ;) > > > > > > > > https://www.youtube.com/watch?v=R-qdLJh4EWQ > > > > > > > > Please remember this is a POC, so the security is almost inexistant, > the > > > > console is awful ;) > > > > > > > > What about the Client SDKs ? > > > > > > > > If we reach some kind of consensus arounf the concept of Unfied Geo > > > Server > > > > we can start building the Client SDKs / POCs , they will be quite > simple > > > : > > > > retrieve geolocation and register to the geo endpoint. > > > > > > > > Sebi > > > > > > > _______________________________________________ > > > > 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 > > > > > > > > > -- > > 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 > > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > 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/20150107/8057d8f5/attachment-0001.html From scm.blanc at gmail.com Wed Jan 7 04:01:38 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 7 Jan 2015 10:01:38 +0100 Subject: [aerogear-dev] [POC] Unified Geo Server In-Reply-To: <1630913627.1022215.1419105637581.JavaMail.yahoo@jws100210.mail.ne1.yahoo.com> References: <1630913627.1022215.1419105637581.JavaMail.yahoo@jws100210.mail.ne1.yahoo.com> Message-ID: On Sat, Dec 20, 2014 at 9:00 PM, Raj Nukala wrote: > Great work sebi . How frequently are the lat longs sent to the geo > server? > This will be configurable and will depend on the native platform capabilities > and what is the backend db for the geo server ? is it mongo ? > In this POC, the DB is not really relevant (I use H2) because the geo search is performed by Hibernate Search (that use Lucene). But it would be nice to have this POC working with a mongodb since it supports "natively" geospatial queries. > > Regards > > > ------------------------------ > *From:* Sebastien Blanc > *To:* AeroGear Developer Mailing List > *Sent:* Monday, December 15, 2014 6:10 PM > *Subject:* Re: [aerogear-dev] [POC] Unified Geo Server > > > > On Mon, Dec 15, 2014 at 11:32 PM, Bruno Oliveira > wrote: > > On 2014-12-15, Matthias Wessendorf wrote: > > On Mon, Dec 15, 2014 at 9:08 PM, Bruno Oliveira > wrote: > > > > > > Good morning, first nice screencast Sebi and even knowing this is just > a > > > PoC I have some considerations: > > > > > > 1. What would be the use case scenario to justify a separated server > > > instead of just a module on AGPUSH? > > > > > > > I think main discussion around this at F2F meeting was, it might be > useful > > for other scenarios as well, > > and we don't want to hard-wire geo to the push server > > Which scenarios? > > The are several scenarios where geo is needed without push. > For instance, think of a backend system for a transport company that needs > to run analysis each night based on the current location of the truck > drivers in order to plan efficiently the logistics for the next day. > > > > > > > > > > > > > > 2. How do you plan to prevent people from faking their location? > > > > > > > I'd assume that a Geo SDK would be based on-top of the mobile OS's > > facility, to receive the long/lat values. > > I think in the future we can have some sort of checks, like validating > the > > users IP address, if it somewhat matches the submitted geo data. > > I think Geo based on IPs are a bad idea. This is a very inaccurate method > and should be our last resort, it's easy to spoof IPs. > > > > > > > > > > > > > 3. Do we have a privacy policy to make the developer real aware about > > > what's being collected? > > > > > > > I think that the level of collected geo data is up to the developer of > the > > app, using the Geo SDK. > > I'm sorry, but I have to disagree. If we don't provide a policy about the > usage of the Geo > server, we're pretty much accountable for it. > > Nothing huge, only a simple txt documenting what's being collected and > why. > > > > > > > > > > > 4. Will collecting geo location be opt in or default? > > > > > > > If the Geo-data SDK is used w/in an app, I think it will still ask, > > up-front, if location based services are OK to use (at least apple). And > > I'd argue that users can still disable the geo usage, per app (at least > > apple) > > Most of users have no idea that their data is being collected. I'm > confused about your answer, is that an yes or no? > > I think what Matthias means is that when using gelolocation on the device, > being iOS, Android or even Web, the users will be prompted to allow or not > access to his geodata. So, yes it's an opt-in and also, like Matthias said > a the possibility to opt-out. > > > > > > > > > > > > > > > > 5. Why is necessary to store current user's position? > > > > > > I think that's up to the use case, and its usage of the Geo SDK. > > Currently we store. I know this is just a proof of concept. > But I insist to be the boring, and avoid it if possible. > > If we don't store we can not make geo queries. Without these queries the > question of having a geo server is quite useless ... > > But we could think of a "flavor" or variant ;) where the geo data is not > persisted but just pass through (to a queue, another REST endpoint), It > will more act then like a broker, but again not sure if I can find a > usecase for that. > > > > > > > > > > > > Couldn't admin > > > specify a range and check how many devices are active on that region? > > > Into this way you don't need to store their positions. I'm not the Geo > > > specialist here but the idea is: > > > > > > 1. Admin specify the range when a push message must be sent. For > > > example: Whole Florida > > > 2. Client opt in and sent her its position to the server > > > 3. Server compares and sent the push message > > > > > > I'm very concerned about privacy here, I'm not against the > > > solution, but Geo location is like to open a Pandora box. > > > > > > > yeah, it's also creepy :) I have not much services that I give my geo > data > > > > > > > > > > We might be careful about unintentional disclosure of geolocation > > > information, > > > because it carries physical risks to the client (theft, to stalking, > > > kidnapping > > > and domestic violence ? I'm not exaggerating). > > > > > > > +1 I'd argue that the "Geo server" would be, initially, a 'simple' back > > end, that is able to store n pairs of long/lat values (grouped by a > > user/device). > > The mobile SDK for it basically store the 'collected' data to this > backend > > (somewhat similar to the push registration SDK) > > > > > > > > > > Again, I know this is a proof of concept, but sooner we have it in > mind, > > > the > > > better. > > > > > > > +1 fully agree. Replied to your questions with my POV on this > > > > > > > > > > > > > > > > > > > > > On 2014-12-10, Sebastien Blanc wrote: > > > > Hi all, > > > > > > > > I have been working on a POC around geolocation. Like we discussed in > > > > another thread, we decided not to have a "deep" integration with the > Push > > > > server but instead a separate component / microservice. Well the POC > is > > > > more a miniservice ;) > > > > > > > > So, the idea is to have a server to which devices can register by > > > providing > > > > their positions. On the other side, the server provide an endpoint to > > > make > > > > spatial queries, like give me all the installations within a radius > of 10 > > > > km around this lat/ltg. > > > > > > > > Thanks to Forge, I created/scaffolded a really simple server > providing > > > the > > > > registration endpoint and the search endpoint. > > > > > > > > I tried to make a decent readme that will give you more details : > > > > > > > > https://github.com/sebastienblanc/unified-geo-server > > > > > > > > And as usual, I made a little screencast showing all that in action > ;) > > > > > > > > https://www.youtube.com/watch?v=R-qdLJh4EWQ > > > > > > > > Please remember this is a POC, so the security is almost inexistant, > the > > > > console is awful ;) > > > > > > > > What about the Client SDKs ? > > > > > > > > If we reach some kind of consensus arounf the concept of Unfied Geo > > > Server > > > > we can start building the Client SDKs / POCs , they will be quite > simple > > > : > > > > retrieve geolocation and register to the geo endpoint. > > > > > > > > Sebi > > > > > > > _______________________________________________ > > > > 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 > > > > > > > > > -- > > 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 > > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150107/f1ca7e1f/attachment.html From bruno at abstractj.org Wed Jan 7 07:12:12 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 7 Jan 2015 10:12:12 -0200 Subject: [aerogear-dev] [Cancelled] - Security Meeting Message-ID: <20150107121212.GA53077@abstractj.org> Good morning my friends, we're still recovering from fireworks and in this very first week we don't have too much to discuss. That said, I'm cancelling the meeting today. If you have something to discuss, just talk to me. -- abstractj PGP: 0x84DC9914 From agalante at redhat.com Wed Jan 7 07:50:57 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 7 Jan 2015 07:50:57 -0500 (EST) Subject: [aerogear-dev] UP console questions In-Reply-To: References: <2086994448.638908.1420476457983.JavaMail.zimbra@redhat.com> <1130368354.745509.1420546956587.JavaMail.zimbra@redhat.com> <867121725.753994.1420551554396.JavaMail.zimbra@redhat.com> Message-ID: <1266936301.896274.1420635057551.JavaMail.zimbra@redhat.com> The console shows "Warnings". Can you help me with a list of warnings that may happened and where they show on the current console? Thanks! ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Tuesday, January 6, 2015 11:47:34 AM Subject: Re: [aerogear-dev] UP console questions On Tue, Jan 6, 2015 at 2:39 PM, Andres Galante < agalante at redhat.com > wrote: Matthias, I was trying to show how GH handles screens when they are empty, it doesn't matter its NO notifications or NO variants or NO apps. The idea is what to show when there ir nothing to show :) Patternfly doesn't have a pattern for blank slates, so we are discussing with the UX team how to show them on our consoles. It will probably follow what we do on our console. +1 sounds good, integrating this theme into patternfly ----- Original Message ----- From: "Matthias Wessendorf" < matzew at apache.org > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Tuesday, January 6, 2015 10:22:06 AM Subject: Re: [aerogear-dev] UP console questions On Tue, Jan 6, 2015 at 1:22 PM, Andres Galante < agalante at redhat.com > wrote: Thanks Matthias and Daniel. This really helps. Matthias we do need to be more explicit along the way. For first time users we need a blank slate[1] followed by a wizard. Plus blank slate for each empty page (like no variants). We can't assume that everyone will read the documentation first. the notifications from GH are just an example here, right? And we would need this being applied to Push Apps and Variants, right? Because it's not the intention of the UPS console to actually read the notifcations. Sure the dashboard shows them and info, but thats more monitoring (e.g. did something go wrong while delivering to Apple/Google/Microsoft) Apart from that we need to guide users as they set up backend and device configuration. yeah, we had previously thought about a better integration of our doc. The doc for the UPS is here: https://aerogear.org/docs/unifiedpush/ups_userguide/ I am working on all this and rearranging IA so it makes more sense. [1] https://dl.dropboxusercontent.com/u/4371641/blank.jpg ----- Original Message ----- From: "Matthias Wessendorf" < matzew at apache.org > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Tuesday, January 6, 2015 8:55:14 AM Subject: Re: [aerogear-dev] UP console questions On Tue, Jan 6, 2015 at 11:35 AM, Daniel Passos < daniel at passos.me > wrote: On Tue, Jan 6, 2015 at 6:57 AM, Matthias Wessendorf < matzew at apache.org > wrote: On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante < agalante at redhat.com > wrote: Hey! I am working on the push console, and I have some questions: 1- What is the main action on the console? What is the main goal a user want to achieve? I notice that the console is center on creating and seeing up apps and not so much in sending notifications. Is sending notifications usually done on code and not the console? the console is nice to send test messages. But in reality a backend (e.g. a MBaaS) will send a request to UPS to force it to deliver the push to Apple and GCM. The main goal is managaement (and overview/stats) around Apps, their Variants and their installations. 2- Under each app we have some information mixed with actions: No variants - Activity - Send Push - admin What does "admin" do, can an app be manage by other thats not the admin? we allow to roles: * admin * user a user (like Andres or Matthias) can do all the CRUD actions. Andres see his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from both users Andres and Matthias 3- Once you click on an app name you get a yellow box with "Sending push notifications" set up information. But when you create a variant you also get an specific info box for each variant. What is the difference between them? not sure what you are asking The first box ( Sending push notifications ) when you create a new application is a snippet of code to you use in you backend (using our sender API[1]) to send a message to UPS and it delivery to the devices like it[2]. The second box ( Registering installations ) when you create a variant is a snippet of code to you use in you mobile app to register you device in that application like it[3] Ah, ok. I now think that the provide text/headers and icons for the two different boxes are perhaps not good enough. Andres, would it make sense to be more explicit there? I think some of what passos wrote could be perhaps baked into the boxes, right ? [1] https://aerogear.org/docs/unifiedpush/GetStartedwithJavaSender/ [2] https://github.com/danielpassos/aerogear-jaxrs-backend/blob/master/src/main/java/me/passos/talks/aerogear/ProductService.java#L56-L69 [3] https://github.com/danielpassos/AeroProduct/blob/master/src/me/passos/talks/aerogear/AeroProductsApplication.java#L36-L60 Thanks! ? _______________________________________________ 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 From edewit at redhat.com Wed Jan 7 09:27:46 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 07 Jan 2015 15:27:46 +0100 Subject: [aerogear-dev] windows oauth2 Message-ID: <54AD4262.7090902@redhat.com> Hi all, We are about to release a initial version of the windows oauth2 library. To make testing easy I've deployed a pre release version on nuget [1]. You can test it with the Shoot and share windows cookbook [2] or with the demo inside the solution [3]. Let me know if there are any issues if not we'll release the version 1.0.0 to nuget. Cheers, Erik Jan [1] https://www.nuget.org/packages/aerogear-windows-oauth2 [2] https://github.com/edewit/aerogear-windows-cookbook [3] https://github.com/edewit/aerogear-windows-oauth2 From edewit at redhat.com Wed Jan 7 11:33:56 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 07 Jan 2015 17:33:56 +0100 Subject: [aerogear-dev] better windows push notification support Message-ID: <54AD5FF4.6010102@redhat.com> Hi, Right now push is supported for windows, but only so called `Toast Notifications`. I want to add the other message types to the as described in this gist [1]. Now in the new message format this would mean to add a couple of fields that are windows specific they should be ignored by the other push services. So I'm wondering if we should do that, or if we should put these fields into a sub category called windows for example: { "message":{ "alert":"HELLO!", "user-data":{ "key":"value" }, "windows": { "template" : "cycle", "title" : "Contoso", "count" : 10, "smallBackgroundImage" : "/Assets/Tiles/smallBackgroundImage.jpg", "cycleImages" : [ "/Assets/Tiles/cycleImage1.jpg", "/Assets/Tiles/cycleImage2.jpg", "/Assets/Tiles/cycleImage3.jpg", "/Assets/Tiles/cycleImage4.jpg", "/Assets/Tiles/cycleImage5.jpg", "/Assets/Tiles/cycleImage6.jpg", "/Assets/Tiles/cycleImage7.jpg", "/Assets/Tiles/cycleImage8.jpg", "/Assets/Tiles/cycleImage9.jpg" ] } } } What do you think? [1] https://gist.github.com/edewit/305d76c31960aa6254a9 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150107/b5e91bb3/attachment.html From lukas.fryc at gmail.com Wed Jan 7 12:26:35 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 7 Jan 2015 18:26:35 +0100 Subject: [aerogear-dev] better windows push notification support In-Reply-To: <54AD5FF4.6010102@redhat.com> References: <54AD5FF4.6010102@redhat.com> Message-ID: Hi Erik, I'd prefer a structured format (under "windows" property) it makes more readable code than a flat structure and avoids collisions. Do we have other platform-specific switches we'd need to align with? Cheers, ~ Lukas On Wed, Jan 7, 2015 at 5:33 PM, Erik Jan de Wit wrote: > Hi, > > Right now push is supported for windows, but only so called `Toast > Notifications`. I want to add the other message types to the as described > in this gist [1]. Now in the new message format this would mean to add a > couple of fields that are windows specific they should be ignored by the > other push services. So I'm wondering if we should do that, or if we should > put these fields into a sub category called windows for example: > > { > "message":{ > "alert":"HELLO!", > "user-data":{ > "key":"value" > }, > "windows": { > "template" : "cycle", > "title" : "Contoso", > "count" : 10, > "smallBackgroundImage" : "/Assets/Tiles/smallBackgroundImage.jpg", > "cycleImages" : > [ > "/Assets/Tiles/cycleImage1.jpg", > "/Assets/Tiles/cycleImage2.jpg", > "/Assets/Tiles/cycleImage3.jpg", > "/Assets/Tiles/cycleImage4.jpg", > "/Assets/Tiles/cycleImage5.jpg", > "/Assets/Tiles/cycleImage6.jpg", > "/Assets/Tiles/cycleImage7.jpg", > "/Assets/Tiles/cycleImage8.jpg", > "/Assets/Tiles/cycleImage9.jpg" > ] > } > } > } > > > > What do you think? > > [1] https://gist.github.com/edewit/305d76c31960aa6254a9 > > _______________________________________________ > 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/20150107/3092a9ea/attachment-0001.html From edewit at redhat.com Thu Jan 8 02:21:47 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 08 Jan 2015 08:21:47 +0100 Subject: [aerogear-dev] better windows push notification support In-Reply-To: References: <54AD5FF4.6010102@redhat.com> Message-ID: <54AE300B.5010204@redhat.com> If we like that settings that are network depended, in a separate 'property', then should we then also move 'content-available' and 'action-category' to a 'apns' property as these are only relevant for apple? On 07/01/2015 18:26, Luk?? Fry? wrote: > Hi Erik, > > I'd prefer a structured format (under "windows" property) > > it makes more readable code than a flat structure and avoids collisions. > > Do we have other platform-specific switches we'd need to align with? > > > Cheers, > > ~ Lukas > > On Wed, Jan 7, 2015 at 5:33 PM, Erik Jan de Wit > wrote: > > Hi, > > Right now push is supported for windows, but only so called `Toast > Notifications`. I want to add the other message types to the as > described in this gist [1]. Now in the new message format this > would mean to add a couple of fields that are windows specific > they should be ignored by the other push services. So I'm > wondering if we should do that, or if we should put these fields > into a sub category called windows for example: > > { > "message":{ > "alert":"HELLO!", > "user-data":{ > "key":"value" > }, > "windows": { > "template" : "cycle", > "title" : "Contoso", > "count" : 10, > "smallBackgroundImage" : "/Assets/Tiles/smallBackgroundImage.jpg", > "cycleImages" : > [ > "/Assets/Tiles/cycleImage1.jpg", > "/Assets/Tiles/cycleImage2.jpg", > "/Assets/Tiles/cycleImage3.jpg", > "/Assets/Tiles/cycleImage4.jpg", > "/Assets/Tiles/cycleImage5.jpg", > "/Assets/Tiles/cycleImage6.jpg", > "/Assets/Tiles/cycleImage7.jpg", > "/Assets/Tiles/cycleImage8.jpg", > "/Assets/Tiles/cycleImage9.jpg" > ] > } > } > } > > > > What do you think? > > [1] https://gist.github.com/edewit/305d76c31960aa6254a9 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150108/9020737a/attachment.html From lukas.fryc at gmail.com Thu Jan 8 10:09:28 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Thu, 8 Jan 2015 16:09:28 +0100 Subject: [aerogear-dev] better windows push notification support In-Reply-To: <54AE300B.5010204@redhat.com> References: <54AD5FF4.6010102@redhat.com> <54AE300B.5010204@redhat.com> Message-ID: I believe that is a way to go, but also definitely a breaking change, so something to discuss widely. We would need to setup a backward-compatibility layer and thus cluttering code. The benefit is a clean API though. On Thu, Jan 8, 2015 at 8:21 AM, Erik Jan de Wit wrote: > If we like that settings that are network depended, in a separate > 'property', then should we then also move 'content-available' and > 'action-category' to a 'apns' property as these are only relevant for apple? > > > On 07/01/2015 18:26, Luk?? Fry? wrote: > > Hi Erik, > > I'd prefer a structured format (under "windows" property) > > it makes more readable code than a flat structure and avoids collisions. > > Do we have other platform-specific switches we'd need to align with? > > > Cheers, > > ~ Lukas > > On Wed, Jan 7, 2015 at 5:33 PM, Erik Jan de Wit wrote: > >> Hi, >> >> Right now push is supported for windows, but only so called `Toast >> Notifications`. I want to add the other message types to the as described >> in this gist [1]. Now in the new message format this would mean to add a >> couple of fields that are windows specific they should be ignored by the >> other push services. So I'm wondering if we should do that, or if we should >> put these fields into a sub category called windows for example: >> >> { >> "message":{ >> "alert":"HELLO!", >> "user-data":{ >> "key":"value" >> }, >> "windows": { >> "template" : "cycle", >> "title" : "Contoso", >> "count" : 10, >> "smallBackgroundImage" : "/Assets/Tiles/smallBackgroundImage.jpg", >> "cycleImages" : >> [ >> "/Assets/Tiles/cycleImage1.jpg", >> "/Assets/Tiles/cycleImage2.jpg", >> "/Assets/Tiles/cycleImage3.jpg", >> "/Assets/Tiles/cycleImage4.jpg", >> "/Assets/Tiles/cycleImage5.jpg", >> "/Assets/Tiles/cycleImage6.jpg", >> "/Assets/Tiles/cycleImage7.jpg", >> "/Assets/Tiles/cycleImage8.jpg", >> "/Assets/Tiles/cycleImage9.jpg" >> ] >> } >> } >> } >> >> >> >> What do you think? >> >> [1] https://gist.github.com/edewit/305d76c31960aa6254a9 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.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/20150108/c28e5aea/attachment.html From edewit at redhat.com Thu Jan 8 10:17:08 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 08 Jan 2015 16:17:08 +0100 Subject: [aerogear-dev] better windows push notification support In-Reply-To: References: <54AD5FF4.6010102@redhat.com> <54AE300B.5010204@redhat.com> Message-ID: <54AE9F74.3080803@redhat.com> > > We would need to setup a backward-compatibility layer and thus > cluttering code. The benefit is a clean API though. > This is not an issue as we have a filter in place that converts from the old api to the new one. From corinnekrych at gmail.com Thu Jan 8 10:34:54 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 8 Jan 2015 16:34:54 +0100 Subject: [aerogear-dev] better windows push notification support In-Reply-To: <54AE9F74.3080803@redhat.com> References: <54AD5FF4.6010102@redhat.com> <54AE300B.5010204@redhat.com> <54AE9F74.3080803@redhat.com> Message-ID: <20FC3638-AC91-44C1-8B30-F94267A6739F@gmail.com> We had similar discussion in this previous thread [1] If we go platform specific section, there are also some iOS only fields (for interactive notification, silent one) that should go in ios section. ++ Corinne [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-message-format-change-proposal-td8977.html > On 08 Jan 2015, at 16:17, Erik Jan de Wit wrote: > > >> >> We would need to setup a backward-compatibility layer and thus >> cluttering code. The benefit is a clean API though. >> > This is not an issue as we have a filter in place that converts from the > old api to the new one. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Fri Jan 9 04:36:51 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 9 Jan 2015 10:36:51 +0100 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: References: <1420471271.11233.6.camel@kpiwko-x220> Message-ID: anyone else ? On Tue, Jan 6, 2015 at 11:52 AM, Daniel Passos wrote: > +1 for the same Jira project, and use components > > -- Passos > > > On Mon, Jan 5, 2015 at 1:21 PM, Karel Piwko wrote: > >> +1. Less JIRA instances, the better imho. >> >> Karel >> >> On Mon, 2015-01-05 at 11:32 +0100, Matthias Wessendorf wrote: >> > Hi, >> > >> > >> > right now we have three different types of 'push servers': >> > * UPS >> > * SimplePush >> > * WebPush Server >> > >> > >> > The first two ones each have their own JIRA, but I was wondering if we >> > use the AGPUSH jira for all three. >> > >> > >> > To manage releases and bugs, we will go with different/more >> > components, and for the releases, we could do what we do successfully >> > on our Cordova project. We can, in JIRA, have releases like: >> > >> > >> > ups-1.3.0 >> > sps-1.0.0 >> > wps-0.2.0 >> > >> > >> > That way would have all push (server) bits on the same JIRA and >> > differentiation is simply done using components and versions as >> > discussed above. >> > >> > >> > 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/20150109/2cf6d22e/attachment.html From daniel.bevenius at gmail.com Fri Jan 9 04:38:17 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Fri, 9 Jan 2015 10:38:17 +0100 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: References: <1420471271.11233.6.camel@kpiwko-x220> Message-ID: +1 Sounds good. On 9 January 2015 at 10:36, Matthias Wessendorf wrote: > anyone else ? > > On Tue, Jan 6, 2015 at 11:52 AM, Daniel Passos wrote: > >> +1 for the same Jira project, and use components >> >> -- Passos >> >> >> On Mon, Jan 5, 2015 at 1:21 PM, Karel Piwko wrote: >> >>> +1. Less JIRA instances, the better imho. >>> >>> Karel >>> >>> On Mon, 2015-01-05 at 11:32 +0100, Matthias Wessendorf wrote: >>> > Hi, >>> > >>> > >>> > right now we have three different types of 'push servers': >>> > * UPS >>> > * SimplePush >>> > * WebPush Server >>> > >>> > >>> > The first two ones each have their own JIRA, but I was wondering if we >>> > use the AGPUSH jira for all three. >>> > >>> > >>> > To manage releases and bugs, we will go with different/more >>> > components, and for the releases, we could do what we do successfully >>> > on our Cordova project. We can, in JIRA, have releases like: >>> > >>> > >>> > ups-1.3.0 >>> > sps-1.0.0 >>> > wps-0.2.0 >>> > >>> > >>> > That way would have all push (server) bits on the same JIRA and >>> > differentiation is simply done using components and versions as >>> > discussed above. >>> > >>> > >>> > 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 > > _______________________________________________ > 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/20150109/c07aa261/attachment.html From agalante at redhat.com Fri Jan 9 08:00:10 2015 From: agalante at redhat.com (Andres Galante) Date: Fri, 9 Jan 2015 08:00:10 -0500 (EST) Subject: [aerogear-dev] Demo apps In-Reply-To: <1656498495.1220267.1420808409756.JavaMail.zimbra@redhat.com> Message-ID: <1432824790.1220268.1420808410940.JavaMail.zimbra@redhat.com> Just something to think for our next demo app: https://medium.com/@romannurik/walk-then-talk-3b935bfe5484 From matzew at apache.org Fri Jan 9 08:49:26 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 9 Jan 2015 14:49:26 +0100 Subject: [aerogear-dev] windows oauth2 In-Reply-To: <54AD4262.7090902@redhat.com> References: <54AD4262.7090902@redhat.com> Message-ID: I am unable to test it, lack of Windows device On Wed, Jan 7, 2015 at 3:27 PM, Erik Jan de Wit wrote: > Hi all, > > We are about to release a initial version of the windows oauth2 library. > To make testing easy I've deployed a pre release version on nuget [1]. > You can test it with the Shoot and share windows cookbook [2] or with > the demo inside the solution [3]. Let me know if there are any issues if > not we'll release the version 1.0.0 to nuget. > > Cheers, > Erik Jan > > [1] https://www.nuget.org/packages/aerogear-windows-oauth2 > [2] https://github.com/edewit/aerogear-windows-cookbook > [3] https://github.com/edewit/aerogear-windows-oauth2 > _______________________________________________ > 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/20150109/7e1fb9e3/attachment.html From matzew at apache.org Fri Jan 9 08:53:42 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 9 Jan 2015 14:53:42 +0100 Subject: [aerogear-dev] Demo apps In-Reply-To: <1432824790.1220268.1420808410940.JavaMail.zimbra@redhat.com> References: <1656498495.1220267.1420808409756.JavaMail.zimbra@redhat.com> <1432824790.1220268.1420808410940.JavaMail.zimbra@redhat.com> Message-ID: to some degree we followed that, with a few examples. E.g. Shoot-n-Share, was made, shared and than talked about (same with AeroDoc) On Fri, Jan 9, 2015 at 2:00 PM, Andres Galante wrote: > Just something to think for our next demo app: > > https://medium.com/@romannurik/walk-then-talk-3b935bfe5484 > > _______________________________________________ > 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/20150109/0dee0dcc/attachment.html From matzew at apache.org Fri Jan 9 08:56:20 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 9 Jan 2015 14:56:20 +0100 Subject: [aerogear-dev] better windows push notification support In-Reply-To: <20FC3638-AC91-44C1-8B30-F94267A6739F@gmail.com> References: <54AD5FF4.6010102@redhat.com> <54AE300B.5010204@redhat.com> <54AE9F74.3080803@redhat.com> <20FC3638-AC91-44C1-8B30-F94267A6739F@gmail.com> Message-ID: On Thu, Jan 8, 2015 at 4:34 PM, Corinne Krych wrote: > We had similar discussion in this previous thread [1] > If we go platform specific section, there are also some iOS only fields > (for interactive notification, silent one) that should go in ios section. > yeah, that's probably true. However, I always liked the unified API, making it somewhat simple to reach a lot of platforms with a simple request to the UPS. If we add more and more nested objects (e.g. android, windows, ios), it can go wild, pretty easy. Perhaps for more complex messages, this might be needed :-/ > > ++ > Corinne > [1] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-message-format-change-proposal-td8977.html > > > On 08 Jan 2015, at 16:17, Erik Jan de Wit wrote: > > > > > >> > >> We would need to setup a backward-compatibility layer and thus > >> cluttering code. The benefit is a clean API though. > >> > > This is not an issue as we have a filter in place that converts from the > > old api to the new one. > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20150109/7687bbbe/attachment-0001.html From supittma at redhat.com Fri Jan 9 10:26:47 2015 From: supittma at redhat.com (Summers Pittman) Date: Fri, 09 Jan 2015 10:26:47 -0500 Subject: [aerogear-dev] Demo apps In-Reply-To: <1432824790.1220268.1420808410940.JavaMail.zimbra@redhat.com> References: <1432824790.1220268.1420808410940.JavaMail.zimbra@redhat.com> Message-ID: <54AFF337.4030305@redhat.com> On 01/09/2015 08:00 AM, Andres Galante wrote: > Just something to think for our next demo app: > > https://medium.com/@romannurik/walk-then-talk-3b935bfe5484 I have to say, the Google I/O app is one of the best resources for Android development. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From agalante at redhat.com Fri Jan 9 11:15:12 2015 From: agalante at redhat.com (Andres Galante) Date: Fri, 9 Jan 2015 11:15:12 -0500 (EST) Subject: [aerogear-dev] Demo apps In-Reply-To: References: <1656498495.1220267.1420808409756.JavaMail.zimbra@redhat.com> <1432824790.1220268.1420808410940.JavaMail.zimbra@redhat.com> Message-ID: <901985308.1265663.1420820112126.JavaMail.zimbra@redhat.com> Thats is true, the process was done. It would be nice to do an app that not only work as a demo, but that is actually useful. Shot n' Share is nice but taking and picture and share them can be done by any phone without having to install an app. I am sure we all have good ideas for apps and we don't have enough time or resources to build it by ourself. On the other hand the team together can pull out anything. Maybe if we can have a place to share and refine those ideas we can create a Demo app that will be useful, be based on aerogear technology. ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Friday, January 9, 2015 10:53:42 AM Subject: Re: [aerogear-dev] Demo apps to some degree we followed that, with a few examples. E.g. Shoot-n-Share, was made, shared and than talked about (same with AeroDoc) On Fri, Jan 9, 2015 at 2:00 PM, Andres Galante < agalante at redhat.com > wrote: Just something to think for our next demo app: https://medium.com/@romannurik/walk-then-talk-3b935bfe5484 _______________________________________________ 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 From daniel.bevenius at gmail.com Sun Jan 11 04:53:35 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Sun, 11 Jan 2015 10:53:35 +0100 Subject: [aerogear-dev] Team meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-20150112 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150111/4437ad69/attachment.html From supittma at redhat.com Mon Jan 12 09:24:05 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 12 Jan 2015 09:24:05 -0500 Subject: [aerogear-dev] Demo apps In-Reply-To: <901985308.1265663.1420820112126.JavaMail.zimbra@redhat.com> References: <1656498495.1220267.1420808409756.JavaMail.zimbra@redhat.com> <1432824790.1220268.1420808410940.JavaMail.zimbra@redhat.com> <901985308.1265663.1420820112126.JavaMail.zimbra@redhat.com> Message-ID: <54B3D905.9060400@redhat.com> On 01/09/2015 11:15 AM, Andres Galante wrote: > Thats is true, the process was done. It would be nice to do an app that not only work as a demo, but that is actually useful. Shot n' Share is nice but taking and picture and share them can be done by any phone without having to install an app. > > I am sure we all have good ideas for apps and we don't have enough time or resources to build it by ourself. On the other hand the team together can pull out anything. Maybe if we can have a place to share and refine those ideas we can create a Demo app that will be useful, be based on aerogear technology. https://github.com/secondsun/devnexus-android-2015 *toots horn* > > ----- Original Message ----- > From: "Matthias Wessendorf" > To: "AeroGear Developer Mailing List" > Sent: Friday, January 9, 2015 10:53:42 AM > Subject: Re: [aerogear-dev] Demo apps > > to some degree we followed that, with a few examples. E.g. Shoot-n-Share, was made, shared and than talked about (same with AeroDoc) > > On Fri, Jan 9, 2015 at 2:00 PM, Andres Galante < agalante at redhat.com > wrote: > > > Just something to think for our next demo app: > > https://medium.com/@romannurik/walk-then-talk-3b935bfe5484 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From supittma at redhat.com Mon Jan 12 09:26:29 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 12 Jan 2015 09:26:29 -0500 Subject: [aerogear-dev] windows oauth2 In-Reply-To: <54AD4262.7090902@redhat.com> References: <54AD4262.7090902@redhat.com> Message-ID: <54B3D995.4070700@redhat.com> On 01/07/2015 09:27 AM, Erik Jan de Wit wrote: > Hi all, > > We are about to release a initial version of the windows oauth2 library. > To make testing easy I've deployed a pre release version on nuget [1]. > You can test it with the Shoot and share windows cookbook [2] or with > the demo inside the solution [3]. Let me know if there are any issues if > not we'll release the version 1.0.0 to nuget. > > Cheers, > Erik Jan > > [1] https://www.nuget.org/packages/aerogear-windows-oauth2 > [2] https://github.com/edewit/aerogear-windows-cookbook > [3] https://github.com/edewit/aerogear-windows-oauth2 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev I'll take a look today as soon as I reboot. -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From supittma at redhat.com Mon Jan 12 15:00:10 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 12 Jan 2015 15:00:10 -0500 Subject: [aerogear-dev] windows oauth2 In-Reply-To: <54B3D995.4070700@redhat.com> References: <54AD4262.7090902@redhat.com> <54B3D995.4070700@redhat.com> Message-ID: <54B427CA.7060507@redhat.com> On 1/12/2015 9:26 AM, Summers Pittman wrote: > On 01/07/2015 09:27 AM, Erik Jan de Wit wrote: >> Hi all, >> >> We are about to release a initial version of the windows oauth2 library. >> To make testing easy I've deployed a pre release version on nuget [1]. >> You can test it with the Shoot and share windows cookbook [2] or with >> the demo inside the solution [3]. Let me know if there are any issues if >> not we'll release the version 1.0.0 to nuget. So I've cloned the cook book and followed the readme for setting up google, but I get a 401. I used "iOS client"and I set my bundle id to "org.aerogear.shoot". That is the value in my package manifest for Protocol. >> >> Cheers, >> Erik Jan >> >> [1] https://www.nuget.org/packages/aerogear-windows-oauth2 >> [2] https://github.com/edewit/aerogear-windows-cookbook >> [3] https://github.com/edewit/aerogear-windows-oauth2 >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > I'll take a look today as soon as I reboot. > From cvasilak at gmail.com Mon Jan 12 10:17:52 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 12 Jan 2015 17:17:52 +0200 Subject: [aerogear-dev] Team meeting In-Reply-To: References: Message-ID: fyi, meeting minutes: Meeting ended Mon Jan 12 15:16:15 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-01-12-15.01.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-12-15.01.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-12-15.01.log.html > On Jan 11, 2015, at 11:53 AM, Daniel Bevenius wrote: > > Agenda: > http://oksoclap.com/p/aerogear-team-mgt-20150112 > _______________________________________________ > 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/20150112/57c8f4c8/attachment.html From matzew at apache.org Mon Jan 12 10:55:28 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 12 Jan 2015 16:55:28 +0100 Subject: [aerogear-dev] UPS: Migration strategy and moving forward Message-ID: Hi, Erik has been kicking ass and did some scripts for users to migrate from 1.0.0 release to the next 1.0.3 release: https://github.com/aerogear/aerogear-unifiedpush-server/pull/460 For the Keycloak part (our 1.0.0 to 1.0.3), some manual migration is needed as well (since we picked a non-final release of Keycloak for our own 1.0.0): https://github.com/aerogear/aerogear-unifiedpush-server/pull/459 (there will be a new chapter in our user guide on this, I am currently on this) Moving on, Keycloak provides manual migration... but the above scripts are needed when migrating from UPS 1.0.0 to 1.0.3 (out soon) Now, some users may already be on 1.0.2 and migration path to 1.0.3 is extremely simple here: nothing to do :=) Once the 1.0.3 will be out, the team will focus on the 1.1.x series, and regarding migration I *think* the only migration we should support is going from 1.0.3 (not 1.0.0.Final) to the latest greatest of the 1.1.x series Any thoughts? -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/20150112/00052a4f/attachment.html From edewit at redhat.com Tue Jan 13 02:46:37 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 13 Jan 2015 08:46:37 +0100 Subject: [aerogear-dev] windows oauth2 In-Reply-To: <54B427CA.7060507@redhat.com> References: <54AD4262.7090902@redhat.com> <54B3D995.4070700@redhat.com> <54B427CA.7060507@redhat.com> Message-ID: <54B4CD5D.4060303@redhat.com> > So I've cloned the cook book and followed the readme for setting up > google, but I get a 401. I used "iOS client"and I set my bundle id to > "org.aerogear.shoot". That is the value in my package manifest for > Protocol. > Thanks for testing, could you elaborate a bit more on this. The bundle id and protocol are set correctly if the app gets launched when the browser has been shown. From scm.blanc at gmail.com Tue Jan 13 03:48:27 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 13 Jan 2015 09:48:27 +0100 Subject: [aerogear-dev] UPS: Migration strategy and moving forward In-Reply-To: References: Message-ID: On Mon, Jan 12, 2015 at 4:55 PM, Matthias Wessendorf wrote: > Hi, > > Erik has been kicking ass and did some scripts for users to migrate from > 1.0.0 release to the next 1.0.3 release: > https://github.com/aerogear/aerogear-unifiedpush-server/pull/460 > > For the Keycloak part (our 1.0.0 to 1.0.3), some manual migration is > needed as well (since we picked a non-final release of Keycloak for our own > 1.0.0): > https://github.com/aerogear/aerogear-unifiedpush-server/pull/459 > > > (there will be a new chapter in our user guide on this, I am currently on > this) > > > > Moving on, Keycloak provides manual migration... but the above scripts are > needed when migrating from UPS 1.0.0 to 1.0.3 (out soon) > > Now, some users may already be on 1.0.2 and migration path to 1.0.3 is > extremely simple here: nothing to do :=) > > > Once the 1.0.3 will be out, the team will focus on the 1.1.x series, and > regarding migration I *think* the only migration we should support is going > from 1.0.3 (not 1.0.0.Final) to the latest greatest of the 1.1.x series > Agreed but we should also be able to help people migrating from 1.0.0.Final to 1.1 (because I'm pretty sure, there will be people in this case) > > Any thoughts? > > -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/20150113/553a387c/attachment.html From matzew at apache.org Tue Jan 13 03:58:07 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 13 Jan 2015 09:58:07 +0100 Subject: [aerogear-dev] UPS: Migration strategy and moving forward In-Reply-To: References: Message-ID: On Tue, Jan 13, 2015 at 9:48 AM, Sebastien Blanc wrote: > > > On Mon, Jan 12, 2015 at 4:55 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> Erik has been kicking ass and did some scripts for users to migrate from >> 1.0.0 release to the next 1.0.3 release: >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/460 >> >> For the Keycloak part (our 1.0.0 to 1.0.3), some manual migration is >> needed as well (since we picked a non-final release of Keycloak for our own >> 1.0.0): >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/459 >> >> >> (there will be a new chapter in our user guide on this, I am currently on >> this) >> >> >> >> Moving on, Keycloak provides manual migration... but the above scripts >> are needed when migrating from UPS 1.0.0 to 1.0.3 (out soon) >> >> Now, some users may already be on 1.0.2 and migration path to 1.0.3 is >> extremely simple here: nothing to do :=) >> >> >> Once the 1.0.3 will be out, the team will focus on the 1.1.x series, and >> regarding migration I *think* the only migration we should support is going >> from 1.0.3 (not 1.0.0.Final) to the latest greatest of the 1.1.x series >> > Agreed but we should also be able to help people migrating from > 1.0.0.Final to 1.1 (because I'm pretty sure, there will be people in this > case) > I think we should focus on the latest greatest. That said, from 1.0.0.Final to 1.0.3 is supported, so going from 1.0.3 to 1.1.x may be just a few extra steps to be executed. We can have a little paragraph on it, I agree. > >> Any thoughts? >> >> -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 > -- 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/20150113/993f0745/attachment.html From corinnekrych at gmail.com Tue Jan 13 04:41:33 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 13 Jan 2015 10:41:33 +0100 Subject: [aerogear-dev] iOS tema meeting Message-ID: <0F02EA0C-BE2F-43B5-8F18-F5CD56520921@gmail.com> Hello iOS lovers Our iOS IRC meeting will take place usual time (4pm GMT+1) this afternoon, here is the agenda: Main focus on clearing up 2.1 tickets. http://oksoclap.com/p/aerogear_ios_meeting_13th_january-2015 ++ Corinne From daniel at passos.me Tue Jan 13 09:14:48 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 13 Jan 2015 12:14:48 -0200 Subject: [aerogear-dev] AeroGear Android 2.0.0 Message-ID: Hey Everyone, Finally we are ready to release AeroGear Android 2.0.0. It was staged on Nexus. I know you are excited to play with it, so, go ahead and let me know wdyt Library Repository Core https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4616/ Security https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4617/ Store https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4618/ Pipe https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4619/ Auth https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4629/ Authz https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4630/ Push https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4623/ We already updated our docs for the new libraries[1], our cookbook[2] example apps and our JavaDoc[3] Take a look at the release announce draft[4] We planned release it to Maven central next friday. [1] http://staging.aerogear.org/docs/guides/aerogear-android/ [2] https://github.com/aerogear/aerogear-android-cookbook/pull/38 [3] https://github.com/aerogear/aerogear.org/pull/461 [4] https://gist.github.com/secondsun/6f57b756bd2b3f85423c ? Passos ? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150113/5a8346b9/attachment-0001.html From bruno at abstractj.org Tue Jan 13 09:42:23 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 13 Jan 2015 12:42:23 -0200 Subject: [aerogear-dev] NPE after migrate to 1.1.0.x series Message-ID: <20150113144223.GA95244@abstractj.org> Good morning, after banging my head against the wall I decided to ask for help. We started the tests with Keycloak 1.1.0.Beta1 and Beta2, although after deploying it we get NPE on UPS. What I identified was that after the commit 94de88ef3b305ad971f81d8610e98a5297f97cd0 the DefaultKeycloakSession will raise the NPE at: public T getProvider(Class clazz) { Integer hash = clazz.hashCode(); T provider = (T) providers.get(hash); if (provider == null) { ProviderFactory providerFactory = factory.getProviderFactory(clazz); if (providerFactory != null) { provider = providerFactory.create(this); providers.put(hash, provider); } } return provider; //Provider will return null here } Maybe is some misconfiguration at https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/auth-server/src/main/resources/META-INF/keycloak-server.json, but after dig into KC sources I couldn't find anything weird. To reproduce the issues with WildFly 8.2.0.final just go to keycloak/project-integrations and run: mvn -Pwildfly clean install wildfly:deploy. Thanks in advance. -- abstractj PGP: 0x84DC9914 From bruno at abstractj.org Tue Jan 13 09:45:35 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 13 Jan 2015 12:45:35 -0200 Subject: [aerogear-dev] NPE after migrate to 1.1.0.x series In-Reply-To: <20150113144223.GA95244@abstractj.org> References: <20150113144223.GA95244@abstractj.org> Message-ID: <20150113144535.GC95244@abstractj.org> Please ignore this e-mail. It was supposed to be sent to keycloak-dev. I'm sorry. On 2015-01-13, Bruno Oliveira wrote: > Good morning, after banging my head against the wall I decided to ask for help. We started the > tests with Keycloak 1.1.0.Beta1 and Beta2, although after deploying it we get NPE on UPS. > > What I identified was that after the commit 94de88ef3b305ad971f81d8610e98a5297f97cd0 the DefaultKeycloakSession > will raise the NPE at: > > public T getProvider(Class clazz) { > Integer hash = clazz.hashCode(); > T provider = (T) providers.get(hash); > if (provider == null) { > ProviderFactory providerFactory = factory.getProviderFactory(clazz); > if (providerFactory != null) { > provider = providerFactory.create(this); > providers.put(hash, provider); > } > } > return provider; //Provider will return null here > } > > Maybe is some misconfiguration at https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/auth-server/src/main/resources/META-INF/keycloak-server.json, but after dig into KC sources I couldn't find anything weird. > > To reproduce the issues with WildFly 8.2.0.final just go to keycloak/project-integrations and run: mvn -Pwildfly clean install wildfly:deploy. > > Thanks in advance. > > -- > > abstractj > PGP: 0x84DC9914 -- abstractj PGP: 0x84DC9914 From cvasilak at gmail.com Tue Jan 13 10:32:25 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Tue, 13 Jan 2015 17:32:25 +0200 Subject: [aerogear-dev] iOS tema meeting In-Reply-To: <0F02EA0C-BE2F-43B5-8F18-F5CD56520921@gmail.com> References: <0F02EA0C-BE2F-43B5-8F18-F5CD56520921@gmail.com> Message-ID: <3436BF7D-BD94-43E8-AA8C-76499341FAEF@gmail.com> fyi meetiing minutes: Meeting ended Tue Jan 13 15:29:49 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-01-13-15.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.log.html > On Jan 13, 2015, at 11:41 AM, Corinne Krych wrote: > > Hello iOS lovers > > Our iOS IRC meeting will take place usual time (4pm GMT+1) this afternoon, here is the agenda: > Main focus on clearing up 2.1 tickets. > > http://oksoclap.com/p/aerogear_ios_meeting_13th_january-2015 > > ++ > 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/20150113/1915f832/attachment.html From kpiwko at redhat.com Wed Jan 14 05:56:58 2015 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 14 Jan 2015 11:56:58 +0100 Subject: [aerogear-dev] iOS tema meeting In-Reply-To: <3436BF7D-BD94-43E8-AA8C-76499341FAEF@gmail.com> References: <0F02EA0C-BE2F-43B5-8F18-F5CD56520921@gmail.com> <3436BF7D-BD94-43E8-AA8C-76499341FAEF@gmail.com> Message-ID: <1421233018.4529.31.camel@kpiwko-x220> To circle back on iOS integration tests question: We do have full stack setup for tests for Cordova being pushed into UPS integration tests: https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/tree/extension-war/ Consists of: 1/ Fetch UPS and QS sources 2/ Configure UPS (enable direct grant, set password, enable proxy for msg interception) 3/ Add push app and variant into UPS 4/ Modify QS to contain push config from UPS 5/ Build QS 6/ Run tests (can be written in any language) While this setup works just for Cordova atm, we are working to span over to Android and iOS natives. Would that be something you, Christos, was looking for? The only concern CI wise is that we don't have Travis Mac OS X support but still it would make tedious QS verification work execute-and-wait-for-results available for anybody on his local machine. Karel On Tue, 2015-01-13 at 17:32 +0200, Christos Vasilakis wrote: > fyi > > > meetiing minutes: > > > Meeting ended Tue Jan 13 15:29:49 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-01-13-15.00.html > Minutes > (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.txt > Log: > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.log.html > > > > > On Jan 13, 2015, at 11:41 AM, Corinne Krych > > wrote: > > > > Hello iOS lovers > > > > Our iOS IRC meeting will take place usual time (4pm GMT+1) this > > afternoon, here is the agenda: > > Main focus on clearing up 2.1 tickets. > > > > http://oksoclap.com/p/aerogear_ios_meeting_13th_january-2015 > > > > ++ > > 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 From matzew at apache.org Wed Jan 14 06:43:09 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 14 Jan 2015 12:43:09 +0100 Subject: [aerogear-dev] iOS tema meeting In-Reply-To: <1421233018.4529.31.camel@kpiwko-x220> References: <0F02EA0C-BE2F-43B5-8F18-F5CD56520921@gmail.com> <3436BF7D-BD94-43E8-AA8C-76499341FAEF@gmail.com> <1421233018.4529.31.camel@kpiwko-x220> Message-ID: On Wed, Jan 14, 2015 at 11:56 AM, Karel Piwko wrote: > To circle back on iOS integration tests question: > > We do have full stack setup for tests for Cordova being pushed into UPS > integration tests: > > https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/tree/extension-war/ > > Consists of: > 1/ Fetch UPS and QS sources > 2/ Configure UPS (enable direct grant, set password, enable proxy for > msg interception) > 3/ Add push app and variant into UPS > 4/ Modify QS to contain push config from UPS > 5/ Build QS > 6/ Run tests (can be written in any language) > > While this setup works just for Cordova atm, we are working to span over > to Android and iOS natives. Would that be something you, Christos, was > looking for? > yes, something like this sounds like a pretty advanced and separated integration test suite. > > The only concern CI wise is that we don't have Travis Mac OS X support > but still it would make tedious QS verification work > execute-and-wait-for-results available for anybody on his local machine. > > Karel > > On Tue, 2015-01-13 at 17:32 +0200, Christos Vasilakis wrote: > > fyi > > > > > > meetiing minutes: > > > > > > Meeting ended Tue Jan 13 15:29:49 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-01-13-15.00.html > > Minutes > > (text): > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.txt > > Log: > > > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.log.html > > > > > > > > > On Jan 13, 2015, at 11:41 AM, Corinne Krych > > > wrote: > > > > > > Hello iOS lovers > > > > > > Our iOS IRC meeting will take place usual time (4pm GMT+1) this > > > afternoon, here is the agenda: > > > Main focus on clearing up 2.1 tickets. > > > > > > http://oksoclap.com/p/aerogear_ios_meeting_13th_january-2015 > > > > > > ++ > > > 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 > > > _______________________________________________ > 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/20150114/c57eb64d/attachment.html From cvasilak at gmail.com Wed Jan 14 07:54:15 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Wed, 14 Jan 2015 14:54:15 +0200 Subject: [aerogear-dev] iOS tema meeting In-Reply-To: <1421233018.4529.31.camel@kpiwko-x220> References: <0F02EA0C-BE2F-43B5-8F18-F5CD56520921@gmail.com> <3436BF7D-BD94-43E8-AA8C-76499341FAEF@gmail.com> <1421233018.4529.31.camel@kpiwko-x220> Message-ID: <635C357D-A2D5-4A47-8732-1CF06145253B@gmail.com> Hi Karel, > On Jan 14, 2015, at 12:56 PM, Karel Piwko wrote: > > To circle back on iOS integration tests question: > > We do have full stack setup for tests for Cordova being pushed into UPS > integration tests: > https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/tree/extension-war/ > > Consists of: > 1/ Fetch UPS and QS sources > 2/ Configure UPS (enable direct grant, set password, enable proxy for > msg interception) > 3/ Add push app and variant into UPS > 4/ Modify QS to contain push config from UPS > 5/ Build QS > 6/ Run tests (can be written in any language) > > While this setup works just for Cordova atm, we are working to span over > to Android and iOS natives. Would that be something you, Christos, was > looking for? sounds very interesting and definitely something too look at. Please feel free to ping us when work starts to support iOS / Android natives to provide possible help in the area. For a short term solution, Corinne is already looking on the best possible way to support our integration tests and ways to embed in our current testing flow. Once details are shorted out we will update our ML accordingly. Thanks for taking the time to respond. - Christos > > The only concern CI wise is that we don't have Travis Mac OS X support > but still it would make tedious QS verification work > execute-and-wait-for-results available for anybody on his local machine. > > Karel > > On Tue, 2015-01-13 at 17:32 +0200, Christos Vasilakis wrote: >> fyi >> >> >> meetiing minutes: >> >> >> Meeting ended Tue Jan 13 15:29:49 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-01-13-15.00.html >> Minutes >> (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.txt >> Log: >> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.log.html >> >> >> >>> On Jan 13, 2015, at 11:41 AM, Corinne Krych >>> wrote: >>> >>> Hello iOS lovers >>> >>> Our iOS IRC meeting will take place usual time (4pm GMT+1) this >>> afternoon, here is the agenda: >>> Main focus on clearing up 2.1 tickets. >>> >>> http://oksoclap.com/p/aerogear_ios_meeting_13th_january-2015 >>> >>> ++ >>> 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From corinnekrych at gmail.com Wed Jan 14 09:52:34 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 14 Jan 2015 15:52:34 +0100 Subject: [aerogear-dev] iOS tema meeting In-Reply-To: <635C357D-A2D5-4A47-8732-1CF06145253B@gmail.com> References: <0F02EA0C-BE2F-43B5-8F18-F5CD56520921@gmail.com> <3436BF7D-BD94-43E8-AA8C-76499341FAEF@gmail.com> <1421233018.4529.31.camel@kpiwko-x220> <635C357D-A2D5-4A47-8732-1CF06145253B@gmail.com> Message-ID: <2C08BD59-9819-4239-873D-FC99D0D321D7@gmail.com> > On 14 Jan 2015, at 13:54, Christos Vasilakis wrote: > > Hi Karel, > >> On Jan 14, 2015, at 12:56 PM, Karel Piwko wrote: >> >> To circle back on iOS integration tests question: >> >> We do have full stack setup for tests for Cordova being pushed into UPS >> integration tests: >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/tree/extension-war/ >> >> Consists of: >> 1/ Fetch UPS and QS sources >> 2/ Configure UPS (enable direct grant, set password, enable proxy for >> msg interception) >> 3/ Add push app and variant into UPS >> 4/ Modify QS to contain push config from UPS >> 5/ Build QS >> 6/ Run tests (can be written in any language) >> >> While this setup works just for Cordova atm, we are working to span over >> to Android and iOS natives. Would that be something you, Christos, was >> looking for? > > > sounds very interesting and definitely something too look at. Please feel free to ping us when work starts to support iOS / Android natives to provide possible help in the area. For a short term solution, Corinne is already looking on the best possible way to support our integration tests and ways to embed in our current testing flow. Once details are shorted out we will update our ML accordingly. I?m looking at unit tests. Once ticket AGIOS-329 is solved we will have mocked unit tests for our aerogear-ios-http lib. As we agreed, unit tests should come first for our libs. For integration tests for ios-http (AGIOS-330), the discussion is all open. No rush on that, no short term needed. Let me move this ticket for next release. Christos proposed using httpbin.org server side and run the integration tests through Xcode integration schema. This is supported well with Travis. The proposed solution was to include integration test in the same gh repository. @Karel what do you think about that proposed approach for integration tests? > > Thanks for taking the time to respond. > > - > Christos > > >> >> The only concern CI wise is that we don't have Travis Mac OS X support >> but still it would make tedious QS verification work >> execute-and-wait-for-results available for anybody on his local machine. >> >> Karel >> >> On Tue, 2015-01-13 at 17:32 +0200, Christos Vasilakis wrote: >>> fyi >>> >>> >>> meetiing minutes: >>> >>> >>> Meeting ended Tue Jan 13 15:29:49 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-01-13-15.00.html >>> Minutes >>> (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.txt >>> Log: >>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.log.html >>> >>> >>> >>>> On Jan 13, 2015, at 11:41 AM, Corinne Krych >>>> wrote: >>>> >>>> Hello iOS lovers >>>> >>>> Our iOS IRC meeting will take place usual time (4pm GMT+1) this >>>> afternoon, here is the agenda: >>>> Main focus on clearing up 2.1 tickets. >>>> >>>> http://oksoclap.com/p/aerogear_ios_meeting_13th_january-2015 >>>> >>>> ++ >>>> 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 >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 matzew at apache.org Wed Jan 14 12:04:54 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 14 Jan 2015 18:04:54 +0100 Subject: [aerogear-dev] Data-Sync: Versioning in JIRA Message-ID: Hi, moving forward with the data-sync, inside of JIRA, I'd need to create versions like: *sync-1.0.0.alpha.1 *sync-1.0.0.alpha.2, * ..., *...beta.1, "sync-1.0.0.final" Do these versions, across JIRA instances (AGJS, AGDROID, AGOIS and AEROGEAR) make sense? Or is there a different preference? 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/20150114/14251de2/attachment.html From matzew at apache.org Wed Jan 14 12:35:15 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 14 Jan 2015 18:35:15 +0100 Subject: [aerogear-dev] aerogear parent Message-ID: Hi! after these two PRs are merged: https://github.com/aerogear/aerogear-parent/pulls I'd like to release the parent. Any concers, or do you need to apply a few more updates to used versions? greetings, matthias -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150114/52e85dd3/attachment.html From bruno at abstractj.org Wed Jan 14 14:14:41 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 14 Jan 2015 17:14:41 -0200 Subject: [aerogear-dev] aerogear parent In-Reply-To: References: Message-ID: <20150114191441.GB5843@abstractj.org> Go for it. On 2015-01-14, Matthias Wessendorf wrote: > Hi! > > after these two PRs are merged: > https://github.com/aerogear/aerogear-parent/pulls > > I'd like to release the parent. Any concers, or do you need to apply a few > more updates to used versions? > > greetings, > matthias > > > -- > Sent from Gmail Mobile > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj PGP: 0x84DC9914 From supittma at redhat.com Wed Jan 14 14:22:57 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 14 Jan 2015 14:22:57 -0500 Subject: [aerogear-dev] Data-Sync: Versioning in JIRA In-Reply-To: References: Message-ID: <54B6C211.4050108@redhat.com> On 01/14/2015 12:04 PM, Matthias Wessendorf wrote: > Hi, > > moving forward with the data-sync, inside of JIRA, I'd need to create > versions like: > *sync-1.0.0.alpha.1 > *sync-1.0.0.alpha.2, > * ..., > *...beta.1, > "sync-1.0.0.final" > > Do these versions, across JIRA instances (AGJS, AGDROID, AGOIS and > AEROGEAR) make sense? Or is there a different preference? So we would have components in the project with versions separate from the release version in the project? > > 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 -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150114/f9b85890/attachment.html From daniel at passos.me Wed Jan 14 14:24:08 2015 From: daniel at passos.me (Daniel Passos) Date: Wed, 14 Jan 2015 17:24:08 -0200 Subject: [aerogear-dev] aerogear parent In-Reply-To: <20150114191441.GB5843@abstractj.org> References: <20150114191441.GB5843@abstractj.org> Message-ID: Go ahead On Wed, Jan 14, 2015 at 5:14 PM, Bruno Oliveira wrote: > Go for it. > > On 2015-01-14, Matthias Wessendorf wrote: > > Hi! > > > > after these two PRs are merged: > > https://github.com/aerogear/aerogear-parent/pulls > > > > I'd like to release the parent. Any concers, or do you need to apply a > few > > more updates to used versions? > > > > greetings, > > matthias > > > > > > -- > > Sent from Gmail Mobile > > > _______________________________________________ > > 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/20150114/ae6c4f87/attachment.html From matzew at apache.org Thu Jan 15 00:21:09 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 15 Jan 2015 06:21:09 +0100 Subject: [aerogear-dev] Data-Sync: Versioning in JIRA In-Reply-To: <54B6C211.4050108@redhat.com> References: <54B6C211.4050108@redhat.com> Message-ID: On Wed, Jan 14, 2015 at 8:22 PM, Summers Pittman wrote: > On 01/14/2015 12:04 PM, Matthias Wessendorf wrote: > > Hi, > > moving forward with the data-sync, inside of JIRA, I'd need to create > versions like: > *sync-1.0.0.alpha.1 > *sync-1.0.0.alpha.2, > * ..., > *...beta.1, > "sync-1.0.0.final" > > Do these versions, across JIRA instances (AGJS, AGDROID, AGOIS and > AEROGEAR) make sense? Or is there a different preference? > > So we would have components in the project with versions separate from the > release version in the project? > Good point :-) Actually, let's keep the versions as they are (makes things easier) but we could use the "sync-1.0.0.alpha.1" etc simply as a label. The benefit would be the same: you click on a specific label (e.g. sync-1.0.0.alpha.1) and get a list of all JIRA tickets, labeled with that label, across different JIRA instances. So new things for SYNC would be still versioned AGDROID-2.x.y, but just get a "sync-1.0.0.alpha.1" label. For the 1.0.0.Final of UPS we used the same process, and it worked very well > > Thanks, > Matthias > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > -- 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/20150115/287094dd/attachment-0001.html From daniel.bevenius at gmail.com Thu Jan 15 00:59:50 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Thu, 15 Jan 2015 06:59:50 +0100 Subject: [aerogear-dev] Data-Sync: Versioning in JIRA In-Reply-To: References: <54B6C211.4050108@redhat.com> Message-ID: +1 Sounds good using a label. On 15 January 2015 at 06:21, Matthias Wessendorf wrote: > > > On Wed, Jan 14, 2015 at 8:22 PM, Summers Pittman > wrote: > >> On 01/14/2015 12:04 PM, Matthias Wessendorf wrote: >> >> Hi, >> >> moving forward with the data-sync, inside of JIRA, I'd need to create >> versions like: >> *sync-1.0.0.alpha.1 >> *sync-1.0.0.alpha.2, >> * ..., >> *...beta.1, >> "sync-1.0.0.final" >> >> Do these versions, across JIRA instances (AGJS, AGDROID, AGOIS and >> AEROGEAR) make sense? Or is there a different preference? >> >> So we would have components in the project with versions separate from >> the release version in the project? >> > > Good point :-) > > Actually, let's keep the versions as they are (makes things easier) but we > could use the "sync-1.0.0.alpha.1" etc simply as a label. The benefit would > be the same: you click on a specific label (e.g. sync-1.0.0.alpha.1) and > get a list of all JIRA tickets, labeled with that label, across different > JIRA instances. > > So new things for SYNC would be still versioned AGDROID-2.x.y, but just > get a "sync-1.0.0.alpha.1" label. > > For the 1.0.0.Final of UPS we used the same process, and it worked very > well > > >> >> Thanks, >> Matthias >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> >> _______________________________________________ >> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Summers Pittman >> >>Phone:404 941 4698 >> >>Java is my crack. >> >> > > > -- > 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/20150115/a9ac211f/attachment.html From kpiwko at redhat.com Thu Jan 15 03:10:27 2015 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 15 Jan 2015 09:10:27 +0100 Subject: [aerogear-dev] iOS tema meeting In-Reply-To: <635C357D-A2D5-4A47-8732-1CF06145253B@gmail.com> References: <0F02EA0C-BE2F-43B5-8F18-F5CD56520921@gmail.com> <3436BF7D-BD94-43E8-AA8C-76499341FAEF@gmail.com> <1421233018.4529.31.camel@kpiwko-x220> <635C357D-A2D5-4A47-8732-1CF06145253B@gmail.com> Message-ID: <1421309427.15974.4.camel@localhost> On Wed, 2015-01-14 at 14:54 +0200, Christos Vasilakis wrote: > Hi Karel, > > > On Jan 14, 2015, at 12:56 PM, Karel Piwko wrote: > > > > To circle back on iOS integration tests question: > > > > We do have full stack setup for tests for Cordova being pushed into UPS > > integration tests: > > https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/tree/extension-war/ > > > > Consists of: > > 1/ Fetch UPS and QS sources > > 2/ Configure UPS (enable direct grant, set password, enable proxy for > > msg interception) > > 3/ Add push app and variant into UPS > > 4/ Modify QS to contain push config from UPS > > 5/ Build QS > > 6/ Run tests (can be written in any language) > > > > While this setup works just for Cordova atm, we are working to span over > > to Android and iOS natives. Would that be something you, Christos, was > > looking for? > > > sounds very interesting and definitely something too look at. Please feel free to ping us when work starts to support iOS / Android natives to provide possible help in the area. For a short term solution, Corinne is already looking on the best possible way to support our integration tests and ways to embed in our current testing flow. Once details are shorted out we will update our ML accordingly. > > Thanks for taking the time to respond. My pleasure! Please ping me anytime. We do have iOS/Android native close to ready, I expect that we'll release iOS alpha1 and Android alpha6/beta1 bits early next week, Stefan and Tadeas can provide more details. > > - > Christos > > > > > > The only concern CI wise is that we don't have Travis Mac OS X support > > but still it would make tedious QS verification work > > execute-and-wait-for-results available for anybody on his local machine. > > > > Karel > > > > On Tue, 2015-01-13 at 17:32 +0200, Christos Vasilakis wrote: > >> fyi > >> > >> > >> meetiing minutes: > >> > >> > >> Meeting ended Tue Jan 13 15:29:49 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-01-13-15.00.html > >> Minutes > >> (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.txt > >> Log: > >> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.log.html > >> > >> > >> > >>> On Jan 13, 2015, at 11:41 AM, Corinne Krych > >>> wrote: > >>> > >>> Hello iOS lovers > >>> > >>> Our iOS IRC meeting will take place usual time (4pm GMT+1) this > >>> afternoon, here is the agenda: > >>> Main focus on clearing up 2.1 tickets. > >>> > >>> http://oksoclap.com/p/aerogear_ios_meeting_13th_january-2015 > >>> > >>> ++ > >>> 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 > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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 kpiwko at redhat.com Thu Jan 15 03:44:02 2015 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 15 Jan 2015 09:44:02 +0100 Subject: [aerogear-dev] iOS tema meeting In-Reply-To: <2C08BD59-9819-4239-873D-FC99D0D321D7@gmail.com> References: <0F02EA0C-BE2F-43B5-8F18-F5CD56520921@gmail.com> <3436BF7D-BD94-43E8-AA8C-76499341FAEF@gmail.com> <1421233018.4529.31.camel@kpiwko-x220> <635C357D-A2D5-4A47-8732-1CF06145253B@gmail.com> <2C08BD59-9819-4239-873D-FC99D0D321D7@gmail.com> Message-ID: <1421311442.15974.9.camel@localhost> On Wed, 2015-01-14 at 15:52 +0100, Corinne Krych wrote: > > On 14 Jan 2015, at 13:54, Christos Vasilakis wrote: > > > > Hi Karel, > > > >> On Jan 14, 2015, at 12:56 PM, Karel Piwko wrote: > >> > >> To circle back on iOS integration tests question: > >> > >> We do have full stack setup for tests for Cordova being pushed into UPS > >> integration tests: > >> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/tree/extension-war/ > >> > >> Consists of: > >> 1/ Fetch UPS and QS sources > >> 2/ Configure UPS (enable direct grant, set password, enable proxy for > >> msg interception) > >> 3/ Add push app and variant into UPS > >> 4/ Modify QS to contain push config from UPS > >> 5/ Build QS > >> 6/ Run tests (can be written in any language) > >> > >> While this setup works just for Cordova atm, we are working to span over > >> to Android and iOS natives. Would that be something you, Christos, was > >> looking for? > > > > > > sounds very interesting and definitely something too look at. Please feel free to ping us when work starts to support iOS / Android natives to provide possible help in the area. For a short term solution, Corinne is already looking on the best possible way to support our integration tests and ways to embed in our current testing flow. Once details are shorted out we will update our ML accordingly. > > > I?m looking at unit tests. > > Once ticket AGIOS-329 is solved we will have mocked unit tests for our aerogear-ios-http lib. > As we agreed, unit tests should come first for our libs. > > For integration tests for ios-http (AGIOS-330), the discussion is all open. No rush on that, no short term needed. Let me move this ticket for next release. > Christos proposed using httpbin.org server side and run the integration tests through Xcode integration schema. This is supported well with Travis. > The proposed solution was to include integration test in the same gh repository. > > @Karel what do you think about that proposed approach for integration tests? Using httpbin.org + xcode integration seems to be a nice way how to test iOS bits without UPS. I think both approaches proposed have their benefits and they could be nicely combined together to increase coverage. Definitely +1 for including tests in the same repository. > > > > > > > Thanks for taking the time to respond. > > > > - > > Christos > > > > > >> > >> The only concern CI wise is that we don't have Travis Mac OS X support > >> but still it would make tedious QS verification work > >> execute-and-wait-for-results available for anybody on his local machine. > >> > >> Karel > >> > >> On Tue, 2015-01-13 at 17:32 +0200, Christos Vasilakis wrote: > >>> fyi > >>> > >>> > >>> meetiing minutes: > >>> > >>> > >>> Meeting ended Tue Jan 13 15:29:49 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-01-13-15.00.html > >>> Minutes > >>> (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.txt > >>> Log: > >>> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-13-15.00.log.html > >>> > >>> > >>> > >>>> On Jan 13, 2015, at 11:41 AM, Corinne Krych > >>>> wrote: > >>>> > >>>> Hello iOS lovers > >>>> > >>>> Our iOS IRC meeting will take place usual time (4pm GMT+1) this > >>>> afternoon, here is the agenda: > >>>> Main focus on clearing up 2.1 tickets. > >>>> > >>>> http://oksoclap.com/p/aerogear_ios_meeting_13th_january-2015 > >>>> > >>>> ++ > >>>> 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 > >> > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.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 Thu Jan 15 08:09:57 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 15 Jan 2015 14:09:57 +0100 Subject: [aerogear-dev] auth2 cordova Message-ID: Hi, We?ve updated some documentation and fixed a small bug and would like to release a new version of the auth2 cordova plugin. The new version is going to be 1.0.1 and fixes bug https://issues.jboss.org/browse/AGCORDOVA-50 you can test it by testing branch https://github.com/aerogear/aerogear-oauth2-cordova/tree/release-1.0.1 if nothing was found I?ll release it to plugins.cordova.io Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150115/74d9885f/attachment.html From lholmqui at redhat.com Thu Jan 15 08:35:30 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Thu, 15 Jan 2015 08:35:30 -0500 Subject: [aerogear-dev] Data-Sync: Versioning in JIRA In-Reply-To: References: <54B6C211.4050108@redhat.com> Message-ID: <78A9C86C-C8DE-42CB-9674-0AE2D8AB6346@redhat.com> yup, labels should work > On Jan 15, 2015, at 12:59 AM, Daniel Bevenius wrote: > > +1 Sounds good using a label. > > On 15 January 2015 at 06:21, Matthias Wessendorf > wrote: > > > On Wed, Jan 14, 2015 at 8:22 PM, Summers Pittman > wrote: > On 01/14/2015 12:04 PM, Matthias Wessendorf wrote: >> Hi, >> >> moving forward with the data-sync, inside of JIRA, I'd need to create versions like: >> *sync-1.0.0.alpha.1 >> *sync-1.0.0.alpha.2, >> * ..., >> *...beta.1, >> "sync-1.0.0.final" >> >> Do these versions, across JIRA instances (AGJS, AGDROID, AGOIS and AEROGEAR) make sense? Or is there a different preference? > So we would have components in the project with versions separate from the release version in the project? > > Good point :-) > > Actually, let's keep the versions as they are (makes things easier) but we could use the "sync-1.0.0.alpha.1" etc simply as a label. The benefit would be the same: you click on a specific label (e.g. sync-1.0.0.alpha.1) and get a list of all JIRA tickets, labeled with that label, across different JIRA instances. > > So new things for SYNC would be still versioned AGDROID-2.x.y, but just get a "sync-1.0.0.alpha.1" label. > > For the 1.0.0.Final of UPS we used the same process, and it worked very well > >> >> 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 > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > > -- > 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/20150115/e9258571/attachment-0001.html From corinnekrych at gmail.com Thu Jan 15 10:29:49 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 15 Jan 2015 16:29:49 +0100 Subject: [aerogear-dev] Data-Sync: Versioning in JIRA In-Reply-To: <78A9C86C-C8DE-42CB-9674-0AE2D8AB6346@redhat.com> References: <54B6C211.4050108@redhat.com> <78A9C86C-C8DE-42CB-9674-0AE2D8AB6346@redhat.com> Message-ID: <107A71D6-C8FA-4849-9E0C-DB2236B46233@gmail.com> +1 > On 15 Jan 2015, at 14:35, Lucas Holmquist wrote: > > yup, labels should work >> On Jan 15, 2015, at 12:59 AM, Daniel Bevenius wrote: >> >> +1 Sounds good using a label. >> >> On 15 January 2015 at 06:21, Matthias Wessendorf wrote: >> >> >> On Wed, Jan 14, 2015 at 8:22 PM, Summers Pittman wrote: >> On 01/14/2015 12:04 PM, Matthias Wessendorf wrote: >>> Hi, >>> >>> moving forward with the data-sync, inside of JIRA, I'd need to create versions like: >>> *sync-1.0.0.alpha.1 >>> *sync-1.0.0.alpha.2, >>> * ..., >>> *...beta.1, >>> "sync-1.0.0.final" >>> >>> Do these versions, across JIRA instances (AGJS, AGDROID, AGOIS and AEROGEAR) make sense? Or is there a different preference? >> So we would have components in the project with versions separate from the release version in the project? >> >> Good point :-) >> >> Actually, let's keep the versions as they are (makes things easier) but we could use the "sync-1.0.0.alpha.1" etc simply as a label. The benefit would be the same: you click on a specific label (e.g. sync-1.0.0.alpha.1) and get a list of all JIRA tickets, labeled with that label, across different JIRA instances. >> >> So new things for SYNC would be still versioned AGDROID-2.x.y, but just get a "sync-1.0.0.alpha.1" label. >> >> For the 1.0.0.Final of UPS we used the same process, and it worked very well >> >>> >>> 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 >> >> >> -- >> Summers Pittman >> >>Phone: >> 404 941 4698 >> >> >>Java is my crack. >> >> >> >> >> -- >> 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 From agalante at redhat.com Thu Jan 15 11:55:19 2015 From: agalante at redhat.com (Andres Galante) Date: Thu, 15 Jan 2015 11:55:19 -0500 (EST) Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> Message-ID: <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> Hi, I've been working on UPS console redesign for the last couple of weeks and I am finally able to share it with you :) Here is a screencast walk through: http://youtu.be/-ab4-F4OCJM And here is the prototype for you to click around: http://andresgalante.com/ups-console/wizard01.html There are a bunch of details to take care about, specially on step 2 of the wizard, we need to make it goes as smooth as possible. Please take a close look and try to find holes in the interaction. Let me know what you think. Thanks! From matzew at apache.org Thu Jan 15 12:12:08 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 15 Jan 2015 18:12:08 +0100 Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> Message-ID: Hin Andres! Wow! awesome - I love it! Where can I sign? :-) I watched the excelent video and here are a few coments on the new UI *Wizzard* After "Mobile device: Setup variant", when clicking "Continue", it brings us to the "test push" UI. Note - for that it is mandatory that the previous step was really executed: meaning the app needs to be launched on a (test) device - otherwise nothing to send the "test push" to :-) Perhaps we should bake that SKIP option a bit into the TEXT - so that it is obvious "Applications overview" wow -> that looks great :) Glad the navigation bar is gone - you are right -> way better. I also like the dashboard location. "App and its Variants overview" -> with no installations: not sure we do always, in that case, immediately show the source code. But I can be wrong -> with installations: let's integrate pagination. e.g. 10 per page! the table looks fantastic "Sender API" We do have more than Java. also Node.js; I think we could use some sort of TAB for the actual platform (similar to the client code) I do really like the INFO _above_ the code. All info in one place - good stuff "Send Notification to App" I like the popup/dialog, including the disabled button when there are no devices. Sweet! Skip Wizzard -> nice, overview with the blank screens Again, awesome work - I am really looking to get this implemented On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante wrote: > Hi, > > I've been working on UPS console redesign for the last couple of weeks and > I am finally able to share it with you :) > > Here is a screencast walk through: > http://youtu.be/-ab4-F4OCJM > > And here is the prototype for you to click around: > http://andresgalante.com/ups-console/wizard01.html > > > There are a bunch of details to take care about, specially on step 2 of > the wizard, we need to make it goes as smooth as possible. > > Please take a close look and try to find holes in the interaction. Let me > know what you think. > > Thanks! > _______________________________________________ > 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/20150115/b886e6fc/attachment.html From scm.blanc at gmail.com Thu Jan 15 12:26:54 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 15 Jan 2015 18:26:54 +0100 Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> Message-ID: On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf wrote: > Hin Andres! > > Wow! awesome - I love it! Where can I sign? :-) > > > I watched the excelent video and here are a few coments on the new UI > > > *Wizzard* > > After "Mobile device: Setup variant", when clicking "Continue", it brings > us to the "test push" UI. > > Note - for that it is mandatory that the previous step was really > executed: meaning the app needs to be launched on a (test) device - > otherwise nothing to send the "test push" to :-) > Perhaps we should bake that SKIP option a bit into the TEXT - so that it > is obvious > I have discussed that a bit with Andres. What we could do is after the user has enter the details of the variant (GCM ApiKey / iOS cert), we could send a dummy message to the vendors network in order to check if these settings are correct. This would already be a nice check. Regarding the device itself, indeed, hard to check/test, but what we could do is check the DB if an installation has been added. (The developer registers the device and then click next) > > > "Applications overview" > > wow -> that looks great :) Glad the navigation bar is gone - you are right > -> way better. I also like the dashboard location. > > > "App and its Variants overview" > -> with no installations: not sure we do always, in that case, immediately > show the source code. But I can be wrong > -> with installations: let's integrate pagination. e.g. 10 per page! the > table looks fantastic > > > > "Sender API" > We do have more than Java. also Node.js; I think we could use some sort of > TAB for the actual platform (similar to the client code) > > I do really like the INFO _above_ the code. All info in one place - good > stuff > > > "Send Notification to App" I like the popup/dialog, including the disabled > button when there are no devices. Sweet! > > > > Skip Wizzard -> nice, overview with the blank screens > > > Again, awesome work - I am really looking to get this implemented > > > > On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante > wrote: > >> Hi, >> >> I've been working on UPS console redesign for the last couple of weeks >> and I am finally able to share it with you :) >> >> Here is a screencast walk through: >> http://youtu.be/-ab4-F4OCJM >> >> And here is the prototype for you to click around: >> http://andresgalante.com/ups-console/wizard01.html >> >> >> There are a bunch of details to take care about, specially on step 2 of >> the wizard, we need to make it goes as smooth as possible. >> >> Please take a close look and try to find holes in the interaction. Let me >> know what you think. >> >> Thanks! >> _______________________________________________ >> 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/20150115/29619f4c/attachment.html From agalante at redhat.com Thu Jan 15 12:38:59 2015 From: agalante at redhat.com (Andres Galante) Date: Thu, 15 Jan 2015 12:38:59 -0500 (EST) Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> Message-ID: <858264483.2097612.1421343539505.JavaMail.zimbra@redhat.com> Step 3 of the wizard is tricky. We don't want the user to get stuck, on the other hand we want to help him successfully install a variant and test it. I'll put together the different scenarios to make it more clear. About Sender API tab, Patternfly supports subnavigation under tabs: https://www.patternfly.org/wp-content/uploads/patternfly/tests/tab.html Maybe it is a good idea to use it to show Java, node and other api information. I'll test that out. ----- Original Message ----- From: "Sebastien Blanc" To: "AeroGear Developer Mailing List" Sent: Thursday, January 15, 2015 2:26:54 PM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf < matzew at apache.org > wrote: Hin Andres! Wow! awesome - I love it! Where can I sign? :-) I watched the excelent video and here are a few coments on the new UI *Wizzard* After "Mobile device: Setup variant", when clicking "Continue", it brings us to the "test push" UI. Note - for that it is mandatory that the previous step was really executed: meaning the app needs to be launched on a (test) device - otherwise nothing to send the "test push" to :-) Perhaps we should bake that SKIP option a bit into the TEXT - so that it is obvious I have discussed that a bit with Andres. What we could do is after the user has enter the details of the variant (GCM ApiKey / iOS cert), we could send a dummy message to the vendors network in order to check if these settings are correct. This would already be a nice check. Regarding the device itself, indeed, hard to check/test, but what we could do is check the DB if an installation has been added. (The developer registers the device and then click next) "Applications overview" wow -> that looks great :) Glad the navigation bar is gone - you are right -> way better. I also like the dashboard location. "App and its Variants overview" -> with no installations: not sure we do always, in that case, immediately show the source code. But I can be wrong -> with installations: let's integrate pagination. e.g. 10 per page! the table looks fantastic "Sender API" We do have more than Java. also Node.js; I think we could use some sort of TAB for the actual platform (similar to the client code) I do really like the INFO _above_ the code. All info in one place - good stuff "Send Notification to App" I like the popup/dialog, including the disabled button when there are no devices. Sweet! Skip Wizzard -> nice, overview with the blank screens Again, awesome work - I am really looking to get this implemented On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante < agalante at redhat.com > wrote: Hi, I've been working on UPS console redesign for the last couple of weeks and I am finally able to share it with you :) Here is a screencast walk through: http://youtu.be/-ab4-F4OCJM And here is the prototype for you to click around: http://andresgalante.com/ups-console/wizard01.html There are a bunch of details to take care about, specially on step 2 of the wizard, we need to make it goes as smooth as possible. Please take a close look and try to find holes in the interaction. Let me know what you think. Thanks! _______________________________________________ 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 From matzew at apache.org Thu Jan 15 12:43:03 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 15 Jan 2015 18:43:03 +0100 Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> Message-ID: On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc wrote: > > > On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf > wrote: > >> Hin Andres! >> >> Wow! awesome - I love it! Where can I sign? :-) >> >> >> I watched the excelent video and here are a few coments on the new UI >> >> >> *Wizzard* >> >> After "Mobile device: Setup variant", when clicking "Continue", it >> brings us to the "test push" UI. >> >> Note - for that it is mandatory that the previous step was really >> executed: meaning the app needs to be launched on a (test) device - >> otherwise nothing to send the "test push" to :-) >> Perhaps we should bake that SKIP option a bit into the TEXT - so that it >> is obvious >> > I have discussed that a bit with Andres. What we could do is after the > user has enter the details of the variant (GCM ApiKey / iOS cert), we could > send a dummy message to the vendors network in order to check if these > settings are correct. This would already be a nice check. > well, not much will happen: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 > > Regarding the device itself, indeed, hard to check/test, but what we could > do is check the DB if an installation has been added. (The developer > registers the device and then click next) > You mean present the "Send dialog" only if there is at least one device already registered? Otherwise, we can again state: now it's time to get a device registered... or something like that - not sure > >> >> "Applications overview" >> >> wow -> that looks great :) Glad the navigation bar is gone - you are >> right -> way better. I also like the dashboard location. >> >> >> "App and its Variants overview" >> -> with no installations: not sure we do always, in that case, >> immediately show the source code. But I can be wrong >> -> with installations: let's integrate pagination. e.g. 10 per page! the >> table looks fantastic >> >> >> >> "Sender API" >> We do have more than Java. also Node.js; I think we could use some sort >> of TAB for the actual platform (similar to the client code) >> >> I do really like the INFO _above_ the code. All info in one place - good >> stuff >> >> >> "Send Notification to App" I like the popup/dialog, including the >> disabled button when there are no devices. Sweet! >> >> >> >> Skip Wizzard -> nice, overview with the blank screens >> >> >> Again, awesome work - I am really looking to get this implemented >> >> >> >> On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante >> wrote: >> >>> Hi, >>> >>> I've been working on UPS console redesign for the last couple of weeks >>> and I am finally able to share it with you :) >>> >>> Here is a screencast walk through: >>> http://youtu.be/-ab4-F4OCJM >>> >>> And here is the prototype for you to click around: >>> http://andresgalante.com/ups-console/wizard01.html >>> >>> >>> There are a bunch of details to take care about, specially on step 2 of >>> the wizard, we need to make it goes as smooth as possible. >>> >>> Please take a close look and try to find holes in the interaction. Let >>> me know what you think. >>> >>> Thanks! >>> _______________________________________________ >>> 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/20150115/da18318a/attachment.html From scm.blanc at gmail.com Thu Jan 15 13:09:51 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 15 Jan 2015 19:09:51 +0100 Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> Message-ID: On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf wrote: > > > On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc > wrote: > >> >> >> On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf >> wrote: >> >>> Hin Andres! >>> >>> Wow! awesome - I love it! Where can I sign? :-) >>> >>> >>> I watched the excelent video and here are a few coments on the new UI >>> >>> >>> *Wizzard* >>> >>> After "Mobile device: Setup variant", when clicking "Continue", it >>> brings us to the "test push" UI. >>> >>> Note - for that it is mandatory that the previous step was really >>> executed: meaning the app needs to be launched on a (test) device - >>> otherwise nothing to send the "test push" to :-) >>> Perhaps we should bake that SKIP option a bit into the TEXT - so that it >>> is obvious >>> >> I have discussed that a bit with Andres. What we could do is after the >> user has enter the details of the variant (GCM ApiKey / iOS cert), we could >> send a dummy message to the vendors network in order to check if these >> settings are correct. This would already be a nice check. >> > > well, not much will happen: > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 > Ah right :) Because there are no installation but beside that "implementation issue" , would be nice to have a way to test if the API Key etc ... are valid . > > > >> >> Regarding the device itself, indeed, hard to check/test, but what we >> could do is check the DB if an installation has been added. (The developer >> registers the device and then click next) >> > > You mean present the "Send dialog" only if there is at least one device > already registered? Otherwise, we can again state: now it's time to get a > device registered... or something like that - not sure > > >> >>> >>> "Applications overview" >>> >>> wow -> that looks great :) Glad the navigation bar is gone - you are >>> right -> way better. I also like the dashboard location. >>> >>> >>> "App and its Variants overview" >>> -> with no installations: not sure we do always, in that case, >>> immediately show the source code. But I can be wrong >>> -> with installations: let's integrate pagination. e.g. 10 per page! the >>> table looks fantastic >>> >>> >>> >>> "Sender API" >>> We do have more than Java. also Node.js; I think we could use some sort >>> of TAB for the actual platform (similar to the client code) >>> >>> I do really like the INFO _above_ the code. All info in one place - good >>> stuff >>> >>> >>> "Send Notification to App" I like the popup/dialog, including the >>> disabled button when there are no devices. Sweet! >>> >>> >>> >>> Skip Wizzard -> nice, overview with the blank screens >>> >>> >>> Again, awesome work - I am really looking to get this implemented >>> >>> >>> >>> On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante >>> wrote: >>> >>>> Hi, >>>> >>>> I've been working on UPS console redesign for the last couple of weeks >>>> and I am finally able to share it with you :) >>>> >>>> Here is a screencast walk through: >>>> http://youtu.be/-ab4-F4OCJM >>>> >>>> And here is the prototype for you to click around: >>>> http://andresgalante.com/ups-console/wizard01.html >>>> >>>> >>>> There are a bunch of details to take care about, specially on step 2 of >>>> the wizard, we need to make it goes as smooth as possible. >>>> >>>> Please take a close look and try to find holes in the interaction. Let >>>> me know what you think. >>>> >>>> Thanks! >>>> _______________________________________________ >>>> 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/20150115/fcb5c841/attachment-0001.html From matzew at apache.org Thu Jan 15 13:15:12 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 15 Jan 2015 19:15:12 +0100 Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> Message-ID: On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc wrote: > > > On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf > wrote: > >> >> >> On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc >> wrote: >> >>> >>> >>> On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf >>> wrote: >>> >>>> Hin Andres! >>>> >>>> Wow! awesome - I love it! Where can I sign? :-) >>>> >>>> >>>> I watched the excelent video and here are a few coments on the new UI >>>> >>>> >>>> *Wizzard* >>>> >>>> After "Mobile device: Setup variant", when clicking "Continue", it >>>> brings us to the "test push" UI. >>>> >>>> Note - for that it is mandatory that the previous step was really >>>> executed: meaning the app needs to be launched on a (test) device - >>>> otherwise nothing to send the "test push" to :-) >>>> Perhaps we should bake that SKIP option a bit into the TEXT - so that >>>> it is obvious >>>> >>> I have discussed that a bit with Andres. What we could do is after the >>> user has enter the details of the variant (GCM ApiKey / iOS cert), we could >>> send a dummy message to the vendors network in order to check if these >>> settings are correct. This would already be a nice check. >>> >> >> well, not much will happen: >> >> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 >> > Ah right :) Because there are no installation but beside that > "implementation issue" , would be nice to have a way to test if the API Key > etc ... are valid . > I agree - we can change it, I think we even have a ticket for that already > >> >> >>> >>> Regarding the device itself, indeed, hard to check/test, but what we >>> could do is check the DB if an installation has been added. (The developer >>> registers the device and then click next) >>> >> >> You mean present the "Send dialog" only if there is at least one device >> already registered? Otherwise, we can again state: now it's time to get a >> device registered... or something like that - not sure >> >> >>> >>>> >>>> "Applications overview" >>>> >>>> wow -> that looks great :) Glad the navigation bar is gone - you are >>>> right -> way better. I also like the dashboard location. >>>> >>>> >>>> "App and its Variants overview" >>>> -> with no installations: not sure we do always, in that case, >>>> immediately show the source code. But I can be wrong >>>> -> with installations: let's integrate pagination. e.g. 10 per page! >>>> the table looks fantastic >>>> >>>> >>>> >>>> "Sender API" >>>> We do have more than Java. also Node.js; I think we could use some sort >>>> of TAB for the actual platform (similar to the client code) >>>> >>>> I do really like the INFO _above_ the code. All info in one place - >>>> good stuff >>>> >>>> >>>> "Send Notification to App" I like the popup/dialog, including the >>>> disabled button when there are no devices. Sweet! >>>> >>>> >>>> >>>> Skip Wizzard -> nice, overview with the blank screens >>>> >>>> >>>> Again, awesome work - I am really looking to get this implemented >>>> >>>> >>>> >>>> On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I've been working on UPS console redesign for the last couple of weeks >>>>> and I am finally able to share it with you :) >>>>> >>>>> Here is a screencast walk through: >>>>> http://youtu.be/-ab4-F4OCJM >>>>> >>>>> And here is the prototype for you to click around: >>>>> http://andresgalante.com/ups-console/wizard01.html >>>>> >>>>> >>>>> There are a bunch of details to take care about, specially on step 2 >>>>> of the wizard, we need to make it goes as smooth as possible. >>>>> >>>>> Please take a close look and try to find holes in the interaction. Let >>>>> me know what you think. >>>>> >>>>> Thanks! >>>>> _______________________________________________ >>>>> 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/20150115/8069d3a7/attachment.html From matzew at apache.org Thu Jan 15 13:16:29 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 15 Jan 2015 19:16:29 +0100 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: References: <1420471271.11233.6.camel@kpiwko-x220> Message-ID: Hi, all SPS tickets have been migrated to AGPUSH. I also created a JIRA admin ticket for Jay to get rid of the (now) empty AGSMPLPUSH instance. -M On Fri, Jan 9, 2015 at 10:38 AM, Daniel Bevenius wrote: > +1 Sounds good. > > On 9 January 2015 at 10:36, Matthias Wessendorf wrote: > >> anyone else ? >> >> On Tue, Jan 6, 2015 at 11:52 AM, Daniel Passos wrote: >> >>> +1 for the same Jira project, and use components >>> >>> -- Passos >>> >>> >>> On Mon, Jan 5, 2015 at 1:21 PM, Karel Piwko wrote: >>> >>>> +1. Less JIRA instances, the better imho. >>>> >>>> Karel >>>> >>>> On Mon, 2015-01-05 at 11:32 +0100, Matthias Wessendorf wrote: >>>> > Hi, >>>> > >>>> > >>>> > right now we have three different types of 'push servers': >>>> > * UPS >>>> > * SimplePush >>>> > * WebPush Server >>>> > >>>> > >>>> > The first two ones each have their own JIRA, but I was wondering if we >>>> > use the AGPUSH jira for all three. >>>> > >>>> > >>>> > To manage releases and bugs, we will go with different/more >>>> > components, and for the releases, we could do what we do successfully >>>> > on our Cordova project. We can, in JIRA, have releases like: >>>> > >>>> > >>>> > ups-1.3.0 >>>> > sps-1.0.0 >>>> > wps-0.2.0 >>>> > >>>> > >>>> > That way would have all push (server) bits on the same JIRA and >>>> > differentiation is simply done using components and versions as >>>> > discussed above. >>>> > >>>> > >>>> > 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150115/c21b453a/attachment-0001.html From matzew at apache.org Thu Jan 15 13:20:54 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 15 Jan 2015 19:20:54 +0100 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: References: <1420471271.11233.6.camel@kpiwko-x220> Message-ID: For WebPush I also created versions on AGPUSH (wps-alpha.1, wps-alpha.2, wps-beta.1, wps-beta.2 and wps-future) -Matthias On Thu, Jan 15, 2015 at 7:16 PM, Matthias Wessendorf wrote: > Hi, > > all SPS tickets have been migrated to AGPUSH. I also created a JIRA admin > ticket for Jay to get rid of the (now) empty AGSMPLPUSH instance. > > -M > > On Fri, Jan 9, 2015 at 10:38 AM, Daniel Bevenius < > daniel.bevenius at gmail.com> wrote: > >> +1 Sounds good. >> >> On 9 January 2015 at 10:36, Matthias Wessendorf >> wrote: >> >>> anyone else ? >>> >>> On Tue, Jan 6, 2015 at 11:52 AM, Daniel Passos wrote: >>> >>>> +1 for the same Jira project, and use components >>>> >>>> -- Passos >>>> >>>> >>>> On Mon, Jan 5, 2015 at 1:21 PM, Karel Piwko wrote: >>>> >>>>> +1. Less JIRA instances, the better imho. >>>>> >>>>> Karel >>>>> >>>>> On Mon, 2015-01-05 at 11:32 +0100, Matthias Wessendorf wrote: >>>>> > Hi, >>>>> > >>>>> > >>>>> > right now we have three different types of 'push servers': >>>>> > * UPS >>>>> > * SimplePush >>>>> > * WebPush Server >>>>> > >>>>> > >>>>> > The first two ones each have their own JIRA, but I was wondering if >>>>> we >>>>> > use the AGPUSH jira for all three. >>>>> > >>>>> > >>>>> > To manage releases and bugs, we will go with different/more >>>>> > components, and for the releases, we could do what we do successfully >>>>> > on our Cordova project. We can, in JIRA, have releases like: >>>>> > >>>>> > >>>>> > ups-1.3.0 >>>>> > sps-1.0.0 >>>>> > wps-0.2.0 >>>>> > >>>>> > >>>>> > That way would have all push (server) bits on the same JIRA and >>>>> > differentiation is simply done using components and versions as >>>>> > discussed above. >>>>> > >>>>> > >>>>> > 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20150115/70ce3692/attachment.html From daniel.bevenius at gmail.com Thu Jan 15 13:40:41 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Thu, 15 Jan 2015 19:40:41 +0100 Subject: [aerogear-dev] JIRA instances for Push... In-Reply-To: References: <1420471271.11233.6.camel@kpiwko-x220> Message-ID: Great! torsdag 15 januari 2015 skrev Matthias Wessendorf : > For WebPush I also created versions on AGPUSH (wps-alpha.1, wps-alpha.2, > wps-beta.1, wps-beta.2 and wps-future) > > -Matthias > > > On Thu, Jan 15, 2015 at 7:16 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> all SPS tickets have been migrated to AGPUSH. I also created a JIRA admin >> ticket for Jay to get rid of the (now) empty AGSMPLPUSH instance. >> >> -M >> >> On Fri, Jan 9, 2015 at 10:38 AM, Daniel Bevenius < >> daniel.bevenius at gmail.com >> > wrote: >> >>> +1 Sounds good. >>> >>> On 9 January 2015 at 10:36, Matthias Wessendorf >> > wrote: >>> >>>> anyone else ? >>>> >>>> On Tue, Jan 6, 2015 at 11:52 AM, Daniel Passos >>> > wrote: >>>> >>>>> +1 for the same Jira project, and use components >>>>> >>>>> -- Passos >>>>> >>>>> >>>>> On Mon, Jan 5, 2015 at 1:21 PM, Karel Piwko >>>> > wrote: >>>>> >>>>>> +1. Less JIRA instances, the better imho. >>>>>> >>>>>> Karel >>>>>> >>>>>> On Mon, 2015-01-05 at 11:32 +0100, Matthias Wessendorf wrote: >>>>>> > Hi, >>>>>> > >>>>>> > >>>>>> > right now we have three different types of 'push servers': >>>>>> > * UPS >>>>>> > * SimplePush >>>>>> > * WebPush Server >>>>>> > >>>>>> > >>>>>> > The first two ones each have their own JIRA, but I was wondering if >>>>>> we >>>>>> > use the AGPUSH jira for all three. >>>>>> > >>>>>> > >>>>>> > To manage releases and bugs, we will go with different/more >>>>>> > components, and for the releases, we could do what we do >>>>>> successfully >>>>>> > on our Cordova project. We can, in JIRA, have releases like: >>>>>> > >>>>>> > >>>>>> > ups-1.3.0 >>>>>> > sps-1.0.0 >>>>>> > wps-0.2.0 >>>>>> > >>>>>> > >>>>>> > That way would have all push (server) bits on the same JIRA and >>>>>> > differentiation is simply done using components and versions as >>>>>> > discussed above. >>>>>> > >>>>>> > >>>>>> > 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> >>>> https://lists.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/20150115/ae800626/attachment.html From matzew at apache.org Fri Jan 16 03:43:59 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 09:43:59 +0100 Subject: [aerogear-dev] auth2 cordova In-Reply-To: References: Message-ID: sounds good to me - great seeing QE catching these items On Thu, Jan 15, 2015 at 2:09 PM, Erik Jan de Wit wrote: > Hi, > > We?ve updated some documentation and fixed a small bug and would like to > release a new version of the auth2 cordova plugin. The new version is going > to be 1.0.1 and fixes bug https://issues.jboss.org/browse/AGCORDOVA-50 you > can test it by testing branch > https://github.com/aerogear/aerogear-oauth2-cordova/tree/release-1.0.1 if > nothing was found I?ll release it to plugins.cordova.io > > 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/20150116/b193e795/attachment-0001.html From matzew at apache.org Fri Jan 16 03:44:17 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 09:44:17 +0100 Subject: [aerogear-dev] AeroGear Android 2.0.0 In-Reply-To: References: Message-ID: Perfect! ship it! :) On Tue, Jan 13, 2015 at 3:14 PM, Daniel Passos wrote: > Hey Everyone, > > Finally we are ready to release AeroGear Android 2.0.0. It was staged on > Nexus. I know you are excited to play with it, so, go ahead and let me know > wdyt > Library Repository Core > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4616/ > Security > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4617/ > Store > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4618/ > Pipe > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4619/ > Auth > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4629/ > Authz > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4630/ > Push > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4623/ > > We already updated our docs for the new libraries[1], our cookbook[2] > example apps and our JavaDoc[3] > > Take a look at the release announce draft[4] > > We planned release it to Maven central next friday. > > [1] http://staging.aerogear.org/docs/guides/aerogear-android/ > [2] https://github.com/aerogear/aerogear-android-cookbook/pull/38 > [3] https://github.com/aerogear/aerogear.org/pull/461 > [4] https://gist.github.com/secondsun/6f57b756bd2b3f85423c > > ? 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/20150116/83c0d138/attachment.html From matzew at apache.org Fri Jan 16 04:45:19 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 10:45:19 +0100 Subject: [aerogear-dev] Data-Sync: Versioning in JIRA In-Reply-To: <107A71D6-C8FA-4849-9E0C-DB2236B46233@gmail.com> References: <54B6C211.4050108@redhat.com> <78A9C86C-C8DE-42CB-9674-0AE2D8AB6346@redhat.com> <107A71D6-C8FA-4849-9E0C-DB2236B46233@gmail.com> Message-ID: Here is a filter, for all the JIRAs that are now labeled as " sync-1.0.0.alpha.1": https://issues.jboss.org/issues/?filter=12323088 -Matthias On Thu, Jan 15, 2015 at 4:29 PM, Corinne Krych wrote: > +1 > > On 15 Jan 2015, at 14:35, Lucas Holmquist wrote: > > > > yup, labels should work > >> On Jan 15, 2015, at 12:59 AM, Daniel Bevenius < > daniel.bevenius at gmail.com> wrote: > >> > >> +1 Sounds good using a label. > >> > >> On 15 January 2015 at 06:21, Matthias Wessendorf > wrote: > >> > >> > >> On Wed, Jan 14, 2015 at 8:22 PM, Summers Pittman > wrote: > >> On 01/14/2015 12:04 PM, Matthias Wessendorf wrote: > >>> Hi, > >>> > >>> moving forward with the data-sync, inside of JIRA, I'd need to create > versions like: > >>> *sync-1.0.0.alpha.1 > >>> *sync-1.0.0.alpha.2, > >>> * ..., > >>> *...beta.1, > >>> "sync-1.0.0.final" > >>> > >>> Do these versions, across JIRA instances (AGJS, AGDROID, AGOIS and > AEROGEAR) make sense? Or is there a different preference? > >> So we would have components in the project with versions separate from > the release version in the project? > >> > >> Good point :-) > >> > >> Actually, let's keep the versions as they are (makes things easier) but > we could use the "sync-1.0.0.alpha.1" etc simply as a label. The benefit > would be the same: you click on a specific label (e.g. sync-1.0.0.alpha.1) > and get a list of all JIRA tickets, labeled with that label, across > different JIRA instances. > >> > >> So new things for SYNC would be still versioned AGDROID-2.x.y, but just > get a "sync-1.0.0.alpha.1" label. > >> > >> For the 1.0.0.Final of UPS we used the same process, and it worked very > well > >> > >>> > >>> 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 > >> > >> > >> -- > >> Summers Pittman > >> >>Phone: > >> 404 941 4698 > >> > >> >>Java is my crack. > >> > >> > >> > >> > >> -- > >> 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/20150116/927f4f9b/attachment.html From daniel at passos.me Fri Jan 16 04:56:23 2015 From: daniel at passos.me (Daniel Passos) Date: Fri, 16 Jan 2015 07:56:23 -0200 Subject: [aerogear-dev] AeroGear Android 2.0.0 In-Reply-To: References: Message-ID: I've just clicked in release button. I think it will be available in Maven central next Monday. -- Passos On Fri, Jan 16, 2015 at 6:44 AM, Matthias Wessendorf wrote: > Perfect! ship it! :) > > On Tue, Jan 13, 2015 at 3:14 PM, Daniel Passos wrote: > >> Hey Everyone, >> >> Finally we are ready to release AeroGear Android 2.0.0. It was staged on >> Nexus. I know you are excited to play with it, so, go ahead and let me know >> wdyt >> Library Repository Core >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4616/ >> Security >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4617/ >> Store >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4618/ >> Pipe >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4619/ >> Auth >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4629/ >> Authz >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4630/ >> Push >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4623/ >> >> We already updated our docs for the new libraries[1], our cookbook[2] >> example apps and our JavaDoc[3] >> >> Take a look at the release announce draft[4] >> >> We planned release it to Maven central next friday. >> >> [1] http://staging.aerogear.org/docs/guides/aerogear-android/ >> [2] https://github.com/aerogear/aerogear-android-cookbook/pull/38 >> [3] https://github.com/aerogear/aerogear.org/pull/461 >> [4] https://gist.github.com/secondsun/6f57b756bd2b3f85423c >> >> ? 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/20150116/ec40d019/attachment-0001.html From matzew at apache.org Fri Jan 16 05:07:25 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 11:07:25 +0100 Subject: [aerogear-dev] AeroGear Android 2.0.0 In-Reply-To: References: Message-ID: yay! On Fri, Jan 16, 2015 at 10:56 AM, Daniel Passos wrote: > I've just clicked in release button. I think it will be available in Maven > central next Monday. > > -- Passos > > On Fri, Jan 16, 2015 at 6:44 AM, Matthias Wessendorf > wrote: > >> Perfect! ship it! :) >> >> On Tue, Jan 13, 2015 at 3:14 PM, Daniel Passos wrote: >> >>> Hey Everyone, >>> >>> Finally we are ready to release AeroGear Android 2.0.0. It was staged on >>> Nexus. I know you are excited to play with it, so, go ahead and let me know >>> wdyt >>> Library Repository Core >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4616/ >>> Security >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4617/ >>> Store >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4618/ >>> Pipe >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4619/ >>> Auth >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4629/ >>> Authz >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4630/ >>> Push >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4623/ >>> >>> We already updated our docs for the new libraries[1], our cookbook[2] >>> example apps and our JavaDoc[3] >>> >>> Take a look at the release announce draft[4] >>> >>> We planned release it to Maven central next friday. >>> >>> [1] http://staging.aerogear.org/docs/guides/aerogear-android/ >>> [2] https://github.com/aerogear/aerogear-android-cookbook/pull/38 >>> [3] https://github.com/aerogear/aerogear.org/pull/461 >>> [4] https://gist.github.com/secondsun/6f57b756bd2b3f85423c >>> >>> ? 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 > -- 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/20150116/8c9e2372/attachment.html From daniel.bevenius at gmail.com Fri Jan 16 05:20:08 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Fri, 16 Jan 2015 11:20:08 +0100 Subject: [aerogear-dev] AeroGear Android 2.0.0 In-Reply-To: References: Message-ID: Nice! On 16 January 2015 at 11:07, Matthias Wessendorf wrote: > yay! > > On Fri, Jan 16, 2015 at 10:56 AM, Daniel Passos wrote: > >> I've just clicked in release button. I think it will be available in >> Maven central next Monday. >> >> -- Passos >> >> On Fri, Jan 16, 2015 at 6:44 AM, Matthias Wessendorf >> wrote: >> >>> Perfect! ship it! :) >>> >>> On Tue, Jan 13, 2015 at 3:14 PM, Daniel Passos wrote: >>> >>>> Hey Everyone, >>>> >>>> Finally we are ready to release AeroGear Android 2.0.0. It was staged >>>> on Nexus. I know you are excited to play with it, so, go ahead and let me >>>> know wdyt >>>> Library Repository Core >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4616/ >>>> Security >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4617/ >>>> Store >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4618/ >>>> Pipe >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4619/ >>>> Auth >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4629/ >>>> Authz >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4630/ >>>> Push >>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4623/ >>>> >>>> We already updated our docs for the new libraries[1], our cookbook[2] >>>> example apps and our JavaDoc[3] >>>> >>>> Take a look at the release announce draft[4] >>>> >>>> We planned release it to Maven central next friday. >>>> >>>> [1] http://staging.aerogear.org/docs/guides/aerogear-android/ >>>> [2] https://github.com/aerogear/aerogear-android-cookbook/pull/38 >>>> [3] https://github.com/aerogear/aerogear.org/pull/461 >>>> [4] https://gist.github.com/secondsun/6f57b756bd2b3f85423c >>>> >>>> ? 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 >> > > > > -- > 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/20150116/c8bcd9e2/attachment-0001.html From agalante at redhat.com Fri Jan 16 07:37:31 2015 From: agalante at redhat.com (Andres Galante) Date: Fri, 16 Jan 2015 07:37:31 -0500 (EST) Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> Message-ID: <1934250777.2228019.1421411851156.JavaMail.zimbra@redhat.com> Good morning! I added tabs on the code snippet (click on the one that has no installations): http://andresgalante.com/ups-console/app-detail-variants.html and sub menu for node.js or other Sender API: http://andresgalante.com/ups-console/app-detail.html As for step 2 and 3 of the wizard I still working on different flow options. I'll share with you something today to continue the discussion. Thanks ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Thursday, January 15, 2015 3:15:12 PM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc < scm.blanc at gmail.com > wrote: On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf < matzew at apache.org > wrote: On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc < scm.blanc at gmail.com > wrote: On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf < matzew at apache.org > wrote: Hin Andres! Wow! awesome - I love it! Where can I sign? :-) I watched the excelent video and here are a few coments on the new UI *Wizzard* After "Mobile device: Setup variant", when clicking "Continue", it brings us to the "test push" UI. Note - for that it is mandatory that the previous step was really executed: meaning the app needs to be launched on a (test) device - otherwise nothing to send the "test push" to :-) Perhaps we should bake that SKIP option a bit into the TEXT - so that it is obvious I have discussed that a bit with Andres. What we could do is after the user has enter the details of the variant (GCM ApiKey / iOS cert), we could send a dummy message to the vendors network in order to check if these settings are correct. This would already be a nice check. well, not much will happen: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 Ah right :) Because there are no installation but beside that "implementation issue" , would be nice to have a way to test if the API Key etc ... are valid . I agree - we can change it, I think we even have a ticket for that already Regarding the device itself, indeed, hard to check/test, but what we could do is check the DB if an installation has been added. (The developer registers the device and then click next) You mean present the "Send dialog" only if there is at least one device already registered? Otherwise, we can again state: now it's time to get a device registered... or something like that - not sure "Applications overview" wow -> that looks great :) Glad the navigation bar is gone - you are right -> way better. I also like the dashboard location. "App and its Variants overview" -> with no installations: not sure we do always, in that case, immediately show the source code. But I can be wrong -> with installations: let's integrate pagination. e.g. 10 per page! the table looks fantastic "Sender API" We do have more than Java. also Node.js; I think we could use some sort of TAB for the actual platform (similar to the client code) I do really like the INFO _above_ the code. All info in one place - good stuff "Send Notification to App" I like the popup/dialog, including the disabled button when there are no devices. Sweet! Skip Wizzard -> nice, overview with the blank screens Again, awesome work - I am really looking to get this implemented On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante < agalante at redhat.com > wrote: Hi, I've been working on UPS console redesign for the last couple of weeks and I am finally able to share it with you :) Here is a screencast walk through: http://youtu.be/-ab4-F4OCJM And here is the prototype for you to click around: http://andresgalante.com/ups-console/wizard01.html There are a bunch of details to take care about, specially on step 2 of the wizard, we need to make it goes as smooth as possible. Please take a close look and try to find holes in the interaction. Let me know what you think. Thanks! _______________________________________________ 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 From matzew at apache.org Fri Jan 16 07:47:57 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 13:47:57 +0100 Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: <1934250777.2228019.1421411851156.JavaMail.zimbra@redhat.com> References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <243384199.2090436.1421340919115.JavaMail.zimbra@redhat.com> <1934250777.2228019.1421411851156.JavaMail.zimbra@redhat.com> Message-ID: On Fri, Jan 16, 2015 at 1:37 PM, Andres Galante wrote: > Good morning! > > I added tabs on the code snippet (click on the one that has no > installations): > http://andresgalante.com/ups-console/app-detail-variants.html > > and sub menu for node.js or other Sender API: > http://andresgalante.com/ups-console/app-detail.html > > good stuff! > As for step 2 and 3 of the wizard I still working on different flow > options. I'll share with you something today to continue the discussion. > cool! looking forward to that :-) > > Thanks > > ----- Original Message ----- > From: "Matthias Wessendorf" > To: "AeroGear Developer Mailing List" > Sent: Thursday, January 15, 2015 3:15:12 PM > Subject: Re: [aerogear-dev] UPS console redesign screencast and demo > > > > On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc < scm.blanc at gmail.com > > wrote: > > > > > > On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > > > On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc < scm.blanc at gmail.com > > wrote: > > > > > > On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > Hin Andres! > > Wow! awesome - I love it! Where can I sign? :-) > > > I watched the excelent video and here are a few coments on the new UI > > > *Wizzard* > > After "Mobile device: Setup variant", when clicking "Continue", it brings > us to the "test push" UI. > > Note - for that it is mandatory that the previous step was really > executed: meaning the app needs to be launched on a (test) device - > otherwise nothing to send the "test push" to :-) > Perhaps we should bake that SKIP option a bit into the TEXT - so that it > is obvious > I have discussed that a bit with Andres. What we could do is after the > user has enter the details of the variant (GCM ApiKey / iOS cert), we could > send a dummy message to the vendors network in order to check if these > settings are correct. This would already be a nice check. > > well, not much will happen: > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 > Ah right :) Because there are no installation but beside that > "implementation issue" , would be nice to have a way to test if the API Key > etc ... are valid . > > I agree - we can change it, I think we even have a ticket for that already > > > > > > > > > > > > > Regarding the device itself, indeed, hard to check/test, but what we could > do is check the DB if an installation has been added. (The developer > registers the device and then click next) > > You mean present the "Send dialog" only if there is at least one device > already registered? Otherwise, we can again state: now it's time to get a > device registered... or something like that - not sure > > > > > > > > > "Applications overview" > > wow -> that looks great :) Glad the navigation bar is gone - you are right > -> way better. I also like the dashboard location. > > > "App and its Variants overview" > -> with no installations: not sure we do always, in that case, immediately > show the source code. But I can be wrong > -> with installations: let's integrate pagination. e.g. 10 per page! the > table looks fantastic > > > > "Sender API" > We do have more than Java. also Node.js; I think we could use some sort of > TAB for the actual platform (similar to the client code) > > I do really like the INFO _above_ the code. All info in one place - good > stuff > > > "Send Notification to App" I like the popup/dialog, including the disabled > button when there are no devices. Sweet! > > > > Skip Wizzard -> nice, overview with the blank screens > > > Again, awesome work - I am really looking to get this implemented > > > > On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Hi, > > I've been working on UPS console redesign for the last couple of weeks and > I am finally able to share it with you :) > > Here is a screencast walk through: > http://youtu.be/-ab4-F4OCJM > > And here is the prototype for you to click around: > http://andresgalante.com/ups-console/wizard01.html > > > There are a bunch of details to take care about, specially on step 2 of > the wizard, we need to make it goes as smooth as possible. > > Please take a close look and try to find holes in the interaction. Let me > know what you think. > > Thanks! > _______________________________________________ > 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 > -- 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/20150116/36e320b5/attachment.html From matzew at apache.org Fri Jan 16 08:16:55 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 14:16:55 +0100 Subject: [aerogear-dev] Push Server user? Message-ID: hello, if you are using the UnifedPush Server, feel free to add your company/project to this new wiki page: https://github.com/aerogear/aerogear-unifiedpush-server/wiki/Users-of-the- UnifiedPush-Server Thanks :-) -- 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/20150116/72f49510/attachment-0001.html From matzew at apache.org Fri Jan 16 09:01:14 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 15:01:14 +0100 Subject: [aerogear-dev] Data-Sync: client-xmpp Message-ID: Hi, should we move the Android client-xmpp to its own repo? Right now, when building the server (and with an incomplete Android setup (aka new, clean repo)) you have to comment it out in order to build the server for running the JS demo. IMO it would be nice if that gets moved out to something like "aerogear-android-xmpp-client". 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/20150116/6752b096/attachment.html From daniel.bevenius at gmail.com Fri Jan 16 09:04:08 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Fri, 16 Jan 2015 15:04:08 +0100 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: References: Message-ID: Yeah, something needs to be done about this. Either moving it out, or having it only enabled with a profile (Summers mentioned this yesterday). On 16 January 2015 at 15:01, Matthias Wessendorf wrote: > Hi, > > should we move the Android client-xmpp to its own repo? Right now, when > building the server (and with an incomplete Android setup (aka new, clean > repo)) you have to comment it out in order to build the server for running > the JS demo. > > IMO it would be nice if that gets moved out to something like > "aerogear-android-xmpp-client". > > 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/20150116/2422a087/attachment.html From matzew at apache.org Fri Jan 16 09:10:35 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 15:10:35 +0100 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: References: Message-ID: On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius wrote: > Yeah, something needs to be done about this. Either moving it out, or > having it only enabled with a profile (Summers mentioned this yesterday). > -1 on profile. IMO the goal is to create a sync client lib, similar to iOS (which is also on its own repo), so that should not be included on the java server. Eventually we should move out the JS bits as well > > > On 16 January 2015 at 15:01, Matthias Wessendorf > wrote: > >> Hi, >> >> should we move the Android client-xmpp to its own repo? Right now, when >> building the server (and with an incomplete Android setup (aka new, clean >> repo)) you have to comment it out in order to build the server for running >> the JS demo. >> >> IMO it would be nice if that gets moved out to something like >> "aerogear-android-xmpp-client". >> >> 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 > -- 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/20150116/75a51b4c/attachment.html From matzew at apache.org Fri Jan 16 09:20:36 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 15:20:36 +0100 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: References: Message-ID: On Fri, Jan 16, 2015 at 3:10 PM, Matthias Wessendorf wrote: > > > On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius < > daniel.bevenius at gmail.com> wrote: > >> Yeah, something needs to be done about this. Either moving it out, or >> having it only enabled with a profile (Summers mentioned this yesterday). >> > > -1 on profile. > > IMO the goal is to create a sync client lib, similar to iOS (which is also > on its own repo), so that should not be included on the java server. > Eventually we should move out the JS bits as well > https://issues.jboss.org/browse/AEROGEAR-1562 For the JS part I am not sure what's the best way, since it's not just library, it's also demo > > >> >> >> On 16 January 2015 at 15:01, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> should we move the Android client-xmpp to its own repo? Right now, when >>> building the server (and with an incomplete Android setup (aka new, clean >>> repo)) you have to comment it out in order to build the server for running >>> the JS demo. >>> >>> IMO it would be nice if that gets moved out to something like >>> "aerogear-android-xmpp-client". >>> >>> 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 >> > > > > -- > 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/20150116/7b4a1d53/attachment.html From daniel.bevenius at gmail.com Fri Jan 16 09:20:45 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Fri, 16 Jan 2015 15:20:45 +0100 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: References: Message-ID: >IMO the goal is to create a sync client lib, similar to iOS Sorry, I was actually thinking about the server. The clients (xmpp and Java) could be moved out into separate projects. The servers are currently integrated, so there is a dependency to xmpp there which might still cause people wanting to try out the server having to update Android on their system. We could extract this integrated server into a separate module for those how want to try it out. On 16 January 2015 at 15:10, Matthias Wessendorf wrote: > > > On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius < > daniel.bevenius at gmail.com> wrote: > >> Yeah, something needs to be done about this. Either moving it out, or >> having it only enabled with a profile (Summers mentioned this yesterday). >> > > -1 on profile. > > IMO the goal is to create a sync client lib, similar to iOS (which is also > on its own repo), so that should not be included on the java server. > Eventually we should move out the JS bits as well > > >> >> >> On 16 January 2015 at 15:01, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> should we move the Android client-xmpp to its own repo? Right now, when >>> building the server (and with an incomplete Android setup (aka new, clean >>> repo)) you have to comment it out in order to build the server for running >>> the JS demo. >>> >>> IMO it would be nice if that gets moved out to something like >>> "aerogear-android-xmpp-client". >>> >>> 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 >> > > > > -- > 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/20150116/b6fcd6b5/attachment-0001.html From supittma at redhat.com Fri Jan 16 09:30:46 2015 From: supittma at redhat.com (Summers Pittman) Date: Fri, 16 Jan 2015 09:30:46 -0500 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: References: Message-ID: <54B92096.1080904@redhat.com> On 01/16/2015 09:20 AM, Daniel Bevenius wrote: > >IMO the goal is to create a sync client lib, similar to iOS > Sorry, I was actually thinking about the server. The clients (xmpp and > Java) could be moved out into separate projects. > > The servers are currently integrated, so there is a dependency to xmpp > there which might still cause people wanting to try out the server > having to update Android on their system. We could extract this > integrated server into a separate module for those how want to try it out. The server xmpp is only reliant on some xmpp library, not on Google stuff and def not android stuff. I'm fine with creating aas and moving the sync stuff into it. > > > > On 16 January 2015 at 15:10, Matthias Wessendorf > wrote: > > > > On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius > > wrote: > > Yeah, something needs to be done about this. Either moving it > out, or having it only enabled with a profile (Summers > mentioned this yesterday). > > > -1 on profile. > > IMO the goal is to create a sync client lib, similar to iOS (which > is also on its own repo), so that should not be included on the > java server. Eventually we should move out the JS bits as well > > > > On 16 January 2015 at 15:01, Matthias Wessendorf > > wrote: > > Hi, > > should we move the Android client-xmpp to its own repo? > Right now, when building the server (and with an > incomplete Android setup (aka new, clean repo)) you have > to comment it out in order to build the server for running > the JS demo. > > IMO it would be nice if that gets moved out to something > like "aerogear-android-xmpp-client". > > 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 > > > > > -- > 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 -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150116/21bae302/attachment.html From agalante at redhat.com Fri Jan 16 09:36:52 2015 From: agalante at redhat.com (Andres Galante) Date: Fri, 16 Jan 2015 09:36:52 -0500 (EST) Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <1934250777.2228019.1421411851156.JavaMail.zimbra@redhat.com> Message-ID: <718817877.2255519.1421419012990.JavaMail.zimbra@redhat.com> This is the wizard flow, please check if we can do it: 1- Creates the app http://andresgalante.com/ups-console/wizard01.html 2- Creates the variant (we validate this form before moving forward) http://andresgalante.com/ups-console/wizard02.html 3- Information on how to set up the variant. We need to write very good instructions: http://andresgalante.com/ups-console/wizard03.html 4 a- IF we have one installation we let him send the notification: http://andresgalante.com/ups-console/wizard04.html 4 b- IF we have NO installations we give the user the option to skip this step or go back and get instruction to set up his device: http://andresgalante.com/ups-console/wizard04-alt.html 5- set up sender API..... I also added links to edit variant info or app name. What do you think? ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Friday, January 16, 2015 9:47:57 AM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo On Fri, Jan 16, 2015 at 1:37 PM, Andres Galante < agalante at redhat.com > wrote: Good morning! I added tabs on the code snippet (click on the one that has no installations): http://andresgalante.com/ups-console/app-detail-variants.html and sub menu for node.js or other Sender API: http://andresgalante.com/ups-console/app-detail.html good stuff! As for step 2 and 3 of the wizard I still working on different flow options. I'll share with you something today to continue the discussion. cool! looking forward to that :-) Thanks ----- Original Message ----- From: "Matthias Wessendorf" < matzew at apache.org > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Thursday, January 15, 2015 3:15:12 PM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc < scm.blanc at gmail.com > wrote: On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf < matzew at apache.org > wrote: On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc < scm.blanc at gmail.com > wrote: On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf < matzew at apache.org > wrote: Hin Andres! Wow! awesome - I love it! Where can I sign? :-) I watched the excelent video and here are a few coments on the new UI *Wizzard* After "Mobile device: Setup variant", when clicking "Continue", it brings us to the "test push" UI. Note - for that it is mandatory that the previous step was really executed: meaning the app needs to be launched on a (test) device - otherwise nothing to send the "test push" to :-) Perhaps we should bake that SKIP option a bit into the TEXT - so that it is obvious I have discussed that a bit with Andres. What we could do is after the user has enter the details of the variant (GCM ApiKey / iOS cert), we could send a dummy message to the vendors network in order to check if these settings are correct. This would already be a nice check. well, not much will happen: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 Ah right :) Because there are no installation but beside that "implementation issue" , would be nice to have a way to test if the API Key etc ... are valid . I agree - we can change it, I think we even have a ticket for that already Regarding the device itself, indeed, hard to check/test, but what we could do is check the DB if an installation has been added. (The developer registers the device and then click next) You mean present the "Send dialog" only if there is at least one device already registered? Otherwise, we can again state: now it's time to get a device registered... or something like that - not sure "Applications overview" wow -> that looks great :) Glad the navigation bar is gone - you are right -> way better. I also like the dashboard location. "App and its Variants overview" -> with no installations: not sure we do always, in that case, immediately show the source code. But I can be wrong -> with installations: let's integrate pagination. e.g. 10 per page! the table looks fantastic "Sender API" We do have more than Java. also Node.js; I think we could use some sort of TAB for the actual platform (similar to the client code) I do really like the INFO _above_ the code. All info in one place - good stuff "Send Notification to App" I like the popup/dialog, including the disabled button when there are no devices. Sweet! Skip Wizzard -> nice, overview with the blank screens Again, awesome work - I am really looking to get this implemented On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante < agalante at redhat.com > wrote: Hi, I've been working on UPS console redesign for the last couple of weeks and I am finally able to share it with you :) Here is a screencast walk through: http://youtu.be/-ab4-F4OCJM And here is the prototype for you to click around: http://andresgalante.com/ups-console/wizard01.html There are a bunch of details to take care about, specially on step 2 of the wizard, we need to make it goes as smooth as possible. Please take a close look and try to find holes in the interaction. Let me know what you think. Thanks! _______________________________________________ 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 -- 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 From lholmqui at redhat.com Fri Jan 16 09:37:13 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Fri, 16 Jan 2015 09:37:13 -0500 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: References: Message-ID: <827197BA-AA2F-44F5-81BA-AD1C16F0C255@redhat.com> > On Jan 16, 2015, at 9:20 AM, Matthias Wessendorf wrote: > > > > On Fri, Jan 16, 2015 at 3:10 PM, Matthias Wessendorf > wrote: > > > On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius > wrote: > Yeah, something needs to be done about this. Either moving it out, or having it only enabled with a profile (Summers mentioned this yesterday). > > -1 on profile. > > IMO the goal is to create a sync client lib, similar to iOS (which is also on its own repo), so that should not be included on the java server. Eventually we should move out the JS bits as well > > https://issues.jboss.org/browse/AEROGEAR-1562 > > For the JS part I am not sure what's the best way, since it's not just library, it's also demo Currently the js-client is in a feature branch, https://github.com/aerogear/aerogear-js/tree/diff-sync-client and the demo is also going into the js cookbook, https://issues.jboss.org/browse/AGJS-268 > > > > > > On 16 January 2015 at 15:01, Matthias Wessendorf > wrote: > Hi, > > should we move the Android client-xmpp to its own repo? Right now, when building the server (and with an incomplete Android setup (aka new, clean repo)) you have to comment it out in order to build the server for running the JS demo. > > IMO it would be nice if that gets moved out to something like "aerogear-android-xmpp-client". > > 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 > > > > -- > 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/20150116/e5f684ca/attachment-0001.html From matzew at apache.org Fri Jan 16 09:57:32 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 15:57:32 +0100 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: References: Message-ID: On Fri, Jan 16, 2015 at 3:20 PM, Daniel Bevenius wrote: > >IMO the goal is to create a sync client lib, similar to iOS > Sorry, I was actually thinking about the server. The clients (xmpp and > Java) could be moved out into separate projects. > > The servers are currently integrated, so there is a dependency to xmpp > there which might still cause people wanting to try out the server having > to update Android on their system. We could extract this integrated server > into a separate module for those how want to try it out. > yeah, I was not speaking about that :-) With a fresh repo, I have to comment out the client-xmpp folder, to make it compile. That's what I'd like to get factored out > > > > On 16 January 2015 at 15:10, Matthias Wessendorf > wrote: > >> >> >> On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius < >> daniel.bevenius at gmail.com> wrote: >> >>> Yeah, something needs to be done about this. Either moving it out, or >>> having it only enabled with a profile (Summers mentioned this yesterday). >>> >> >> -1 on profile. >> >> IMO the goal is to create a sync client lib, similar to iOS (which is >> also on its own repo), so that should not be included on the java server. >> Eventually we should move out the JS bits as well >> >> >>> >>> >>> On 16 January 2015 at 15:01, Matthias Wessendorf >>> wrote: >>> >>>> Hi, >>>> >>>> should we move the Android client-xmpp to its own repo? Right now, when >>>> building the server (and with an incomplete Android setup (aka new, clean >>>> repo)) you have to comment it out in order to build the server for running >>>> the JS demo. >>>> >>>> IMO it would be nice if that gets moved out to something like >>>> "aerogear-android-xmpp-client". >>>> >>>> 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 >>> >> >> >> >> -- >> 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/20150116/86895bc7/attachment.html From matzew at apache.org Fri Jan 16 09:58:25 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 15:58:25 +0100 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: <827197BA-AA2F-44F5-81BA-AD1C16F0C255@redhat.com> References: <827197BA-AA2F-44F5-81BA-AD1C16F0C255@redhat.com> Message-ID: On Fri, Jan 16, 2015 at 3:37 PM, Lucas Holmquist wrote: > > On Jan 16, 2015, at 9:20 AM, Matthias Wessendorf > wrote: > > > > On Fri, Jan 16, 2015 at 3:10 PM, Matthias Wessendorf > wrote: > >> >> >> On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius < >> daniel.bevenius at gmail.com> wrote: >> >>> Yeah, something needs to be done about this. Either moving it out, or >>> having it only enabled with a profile (Summers mentioned this yesterday). >>> >> >> -1 on profile. >> >> IMO the goal is to create a sync client lib, similar to iOS (which is >> also on its own repo), so that should not be included on the java server. >> Eventually we should move out the JS bits as well >> > > https://issues.jboss.org/browse/AEROGEAR-1562 > > For the JS part I am not sure what's the best way, since it's not just > library, it's also demo > > > Currently the js-client is in a feature branch, > https://github.com/aerogear/aerogear-js/tree/diff-sync-client > > and the demo is also going into the js cookbook, > https://issues.jboss.org/browse/AGJS-268 > perfect! so, that answers my question :-) > > > > >> >> >>> >>> >>> On 16 January 2015 at 15:01, Matthias Wessendorf >>> wrote: >>> >>>> Hi, >>>> >>>> should we move the Android client-xmpp to its own repo? Right now, when >>>> building the server (and with an incomplete Android setup (aka new, clean >>>> repo)) you have to comment it out in order to build the server for running >>>> the JS demo. >>>> >>>> IMO it would be nice if that gets moved out to something like >>>> "aerogear-android-xmpp-client". >>>> >>>> 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 >>> >> >> >> >> -- >> 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/20150116/b7631a92/attachment.html From matzew at apache.org Fri Jan 16 09:59:06 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 15:59:06 +0100 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: <54B92096.1080904@redhat.com> References: <54B92096.1080904@redhat.com> Message-ID: On Fri, Jan 16, 2015 at 3:30 PM, Summers Pittman wrote: > On 01/16/2015 09:20 AM, Daniel Bevenius wrote: > > >IMO the goal is to create a sync client lib, similar to iOS > Sorry, I was actually thinking about the server. The clients (xmpp and > Java) could be moved out into separate projects. > > The servers are currently integrated, so there is a dependency to xmpp > there which might still cause people wanting to try out the server having > to update Android on their system. We could extract this integrated server > into a separate module for those how want to try it out. > > The server xmpp is only reliant on some xmpp library, not on Google stuff > and def not android stuff. > Right, that's not an issue - we can keep that in there - at the end, if (or when) the server will support XMPP, this lib/dependency is needed there anyways > > I'm fine with creating aas and moving the sync stuff into it. > > > > > On 16 January 2015 at 15:10, Matthias Wessendorf > wrote: > >> >> >> On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius < >> daniel.bevenius at gmail.com> wrote: >> >>> Yeah, something needs to be done about this. Either moving it out, or >>> having it only enabled with a profile (Summers mentioned this yesterday). >>> >> >> -1 on profile. >> >> IMO the goal is to create a sync client lib, similar to iOS (which is >> also on its own repo), so that should not be included on the java server. >> Eventually we should move out the JS bits as well >> >> >>> >>> >>> On 16 January 2015 at 15:01, Matthias Wessendorf >>> wrote: >>> >>>> Hi, >>>> >>>> should we move the Android client-xmpp to its own repo? Right now, >>>> when building the server (and with an incomplete Android setup (aka new, >>>> clean repo)) you have to comment it out in order to build the server for >>>> running the JS demo. >>>> >>>> IMO it would be nice if that gets moved out to something like >>>> "aerogear-android-xmpp-client". >>>> >>>> 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 >>> >> >> >> >> -- >> 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 listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > 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/20150116/9304a396/attachment-0001.html From agalante at redhat.com Fri Jan 16 10:15:02 2015 From: agalante at redhat.com (Andres Galante) Date: Fri, 16 Jan 2015 10:15:02 -0500 (EST) Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: <718817877.2255519.1421419012990.JavaMail.zimbra@redhat.com> References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <1934250777.2228019.1421411851156.JavaMail.zimbra@redhat.com> <718817877.2255519.1421419012990.JavaMail.zimbra@redhat.com> Message-ID: <2129836080.2266706.1421421302258.JavaMail.zimbra@redhat.com> This diagram illustrates the flow better: https://dl.dropboxusercontent.com/u/4371641/wizard-flow.png ----- Original Message ----- From: "Andres Galante" To: "AeroGear Developer Mailing List" Sent: Friday, January 16, 2015 11:36:52 AM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo This is the wizard flow, please check if we can do it: 1- Creates the app http://andresgalante.com/ups-console/wizard01.html 2- Creates the variant (we validate this form before moving forward) http://andresgalante.com/ups-console/wizard02.html 3- Information on how to set up the variant. We need to write very good instructions: http://andresgalante.com/ups-console/wizard03.html 4 a- IF we have one installation we let him send the notification: http://andresgalante.com/ups-console/wizard04.html 4 b- IF we have NO installations we give the user the option to skip this step or go back and get instruction to set up his device: http://andresgalante.com/ups-console/wizard04-alt.html 5- set up sender API..... I also added links to edit variant info or app name. What do you think? ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Friday, January 16, 2015 9:47:57 AM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo On Fri, Jan 16, 2015 at 1:37 PM, Andres Galante < agalante at redhat.com > wrote: Good morning! I added tabs on the code snippet (click on the one that has no installations): http://andresgalante.com/ups-console/app-detail-variants.html and sub menu for node.js or other Sender API: http://andresgalante.com/ups-console/app-detail.html good stuff! As for step 2 and 3 of the wizard I still working on different flow options. I'll share with you something today to continue the discussion. cool! looking forward to that :-) Thanks ----- Original Message ----- From: "Matthias Wessendorf" < matzew at apache.org > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Thursday, January 15, 2015 3:15:12 PM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc < scm.blanc at gmail.com > wrote: On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf < matzew at apache.org > wrote: On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc < scm.blanc at gmail.com > wrote: On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf < matzew at apache.org > wrote: Hin Andres! Wow! awesome - I love it! Where can I sign? :-) I watched the excelent video and here are a few coments on the new UI *Wizzard* After "Mobile device: Setup variant", when clicking "Continue", it brings us to the "test push" UI. Note - for that it is mandatory that the previous step was really executed: meaning the app needs to be launched on a (test) device - otherwise nothing to send the "test push" to :-) Perhaps we should bake that SKIP option a bit into the TEXT - so that it is obvious I have discussed that a bit with Andres. What we could do is after the user has enter the details of the variant (GCM ApiKey / iOS cert), we could send a dummy message to the vendors network in order to check if these settings are correct. This would already be a nice check. well, not much will happen: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 Ah right :) Because there are no installation but beside that "implementation issue" , would be nice to have a way to test if the API Key etc ... are valid . I agree - we can change it, I think we even have a ticket for that already Regarding the device itself, indeed, hard to check/test, but what we could do is check the DB if an installation has been added. (The developer registers the device and then click next) You mean present the "Send dialog" only if there is at least one device already registered? Otherwise, we can again state: now it's time to get a device registered... or something like that - not sure "Applications overview" wow -> that looks great :) Glad the navigation bar is gone - you are right -> way better. I also like the dashboard location. "App and its Variants overview" -> with no installations: not sure we do always, in that case, immediately show the source code. But I can be wrong -> with installations: let's integrate pagination. e.g. 10 per page! the table looks fantastic "Sender API" We do have more than Java. also Node.js; I think we could use some sort of TAB for the actual platform (similar to the client code) I do really like the INFO _above_ the code. All info in one place - good stuff "Send Notification to App" I like the popup/dialog, including the disabled button when there are no devices. Sweet! Skip Wizzard -> nice, overview with the blank screens Again, awesome work - I am really looking to get this implemented On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante < agalante at redhat.com > wrote: Hi, I've been working on UPS console redesign for the last couple of weeks and I am finally able to share it with you :) Here is a screencast walk through: http://youtu.be/-ab4-F4OCJM And here is the prototype for you to click around: http://andresgalante.com/ups-console/wizard01.html There are a bunch of details to take care about, specially on step 2 of the wizard, we need to make it goes as smooth as possible. Please take a close look and try to find holes in the interaction. Let me know what you think. Thanks! _______________________________________________ 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 -- 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 From matzew at apache.org Fri Jan 16 10:20:59 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 16:20:59 +0100 Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: <718817877.2255519.1421419012990.JavaMail.zimbra@redhat.com> References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <1934250777.2228019.1421411851156.JavaMail.zimbra@redhat.com> <718817877.2255519.1421419012990.JavaMail.zimbra@redhat.com> Message-ID: +1 on 4a and 4b On Fri, Jan 16, 2015 at 3:36 PM, Andres Galante wrote: > This is the wizard flow, please check if we can do it: > > 1- Creates the app > http://andresgalante.com/ups-console/wizard01.html > > 2- Creates the variant (we validate this form before moving forward) > http://andresgalante.com/ups-console/wizard02.html > > 3- Information on how to set up the variant. We need to write very good > instructions: > http://andresgalante.com/ups-console/wizard03.html > > 4 a- IF we have one installation we let him send the notification: > http://andresgalante.com/ups-console/wizard04.html > > 4 b- IF we have NO installations we give the user the option to skip this > step or go back and get instruction to set up his device: > http://andresgalante.com/ups-console/wizard04-alt.html > > 5- set up sender API..... > > I also added links to edit variant info or app name. > > What do you think? > > > ----- Original Message ----- > From: "Matthias Wessendorf" > To: "AeroGear Developer Mailing List" > Sent: Friday, January 16, 2015 9:47:57 AM > Subject: Re: [aerogear-dev] UPS console redesign screencast and demo > > > > On Fri, Jan 16, 2015 at 1:37 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Good morning! > > I added tabs on the code snippet (click on the one that has no > installations): > http://andresgalante.com/ups-console/app-detail-variants.html > > and sub menu for node.js or other Sender API: > http://andresgalante.com/ups-console/app-detail.html > > > good stuff! > > > As for step 2 and 3 of the wizard I still working on different flow > options. I'll share with you something today to continue the discussion. > > cool! looking forward to that :-) > > > > Thanks > > ----- Original Message ----- > From: "Matthias Wessendorf" < matzew at apache.org > > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > > Sent: Thursday, January 15, 2015 3:15:12 PM > Subject: Re: [aerogear-dev] UPS console redesign screencast and demo > > > > On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc < scm.blanc at gmail.com > > wrote: > > > > > > On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > > > On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc < scm.blanc at gmail.com > > wrote: > > > > > > On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > Hin Andres! > > Wow! awesome - I love it! Where can I sign? :-) > > > I watched the excelent video and here are a few coments on the new UI > > > *Wizzard* > > After "Mobile device: Setup variant", when clicking "Continue", it brings > us to the "test push" UI. > > Note - for that it is mandatory that the previous step was really > executed: meaning the app needs to be launched on a (test) device - > otherwise nothing to send the "test push" to :-) > Perhaps we should bake that SKIP option a bit into the TEXT - so that it > is obvious > I have discussed that a bit with Andres. What we could do is after the > user has enter the details of the variant (GCM ApiKey / iOS cert), we could > send a dummy message to the vendors network in order to check if these > settings are correct. This would already be a nice check. > > well, not much will happen: > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 > Ah right :) Because there are no installation but beside that > "implementation issue" , would be nice to have a way to test if the API Key > etc ... are valid . > > I agree - we can change it, I think we even have a ticket for that already > > > > > > > > > > > > > Regarding the device itself, indeed, hard to check/test, but what we could > do is check the DB if an installation has been added. (The developer > registers the device and then click next) > > You mean present the "Send dialog" only if there is at least one device > already registered? Otherwise, we can again state: now it's time to get a > device registered... or something like that - not sure > > > > > > > > > "Applications overview" > > wow -> that looks great :) Glad the navigation bar is gone - you are right > -> way better. I also like the dashboard location. > > > "App and its Variants overview" > -> with no installations: not sure we do always, in that case, immediately > show the source code. But I can be wrong > -> with installations: let's integrate pagination. e.g. 10 per page! the > table looks fantastic > > > > "Sender API" > We do have more than Java. also Node.js; I think we could use some sort of > TAB for the actual platform (similar to the client code) > > I do really like the INFO _above_ the code. All info in one place - good > stuff > > > "Send Notification to App" I like the popup/dialog, including the disabled > button when there are no devices. Sweet! > > > > Skip Wizzard -> nice, overview with the blank screens > > > Again, awesome work - I am really looking to get this implemented > > > > On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Hi, > > I've been working on UPS console redesign for the last couple of weeks and > I am finally able to share it with you :) > > Here is a screencast walk through: > http://youtu.be/-ab4-F4OCJM > > And here is the prototype for you to click around: > http://andresgalante.com/ups-console/wizard01.html > > > There are a bunch of details to take care about, specially on step 2 of > the wizard, we need to make it goes as smooth as possible. > > Please take a close look and try to find holes in the interaction. Let me > know what you think. > > Thanks! > _______________________________________________ > 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 > > > > -- > 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/20150116/c568f0df/attachment-0001.html From scm.blanc at gmail.com Fri Jan 16 10:31:03 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 16 Jan 2015 16:31:03 +0100 Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: <718817877.2255519.1421419012990.JavaMail.zimbra@redhat.com> References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <1934250777.2228019.1421411851156.JavaMail.zimbra@redhat.com> <718817877.2255519.1421419012990.JavaMail.zimbra@redhat.com> Message-ID: On Fri, Jan 16, 2015 at 3:36 PM, Andres Galante wrote: > This is the wizard flow, please check if we can do it: > > 1- Creates the app > http://andresgalante.com/ups-console/wizard01.html > > 2- Creates the variant (we validate this form before moving forward) > http://andresgalante.com/ups-console/wizard02.html > > 3- Information on how to set up the variant. We need to write very good > instructions: > http://andresgalante.com/ups-console/wizard03.html The code snippet take the whole screen and you have to scroll down to click "continue", maybe it could be collapsed or having the button "continue" at another place ? > > > 4 a- IF we have one installation we let him send the notification: > http://andresgalante.com/ups-console/wizard04.html > > 4 b- IF we have NO installations we give the user the option to skip this > step or go back and get instruction to set up his device: > http://andresgalante.com/ups-console/wizard04-alt.html > > 5- set up sender API..... > > I also added links to edit variant info or app name. > > What do you think? > > > ----- Original Message ----- > From: "Matthias Wessendorf" > To: "AeroGear Developer Mailing List" > Sent: Friday, January 16, 2015 9:47:57 AM > Subject: Re: [aerogear-dev] UPS console redesign screencast and demo > > > > On Fri, Jan 16, 2015 at 1:37 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Good morning! > > I added tabs on the code snippet (click on the one that has no > installations): > http://andresgalante.com/ups-console/app-detail-variants.html > > and sub menu for node.js or other Sender API: > http://andresgalante.com/ups-console/app-detail.html > > > good stuff! > > > As for step 2 and 3 of the wizard I still working on different flow > options. I'll share with you something today to continue the discussion. > > cool! looking forward to that :-) > > > > Thanks > > ----- Original Message ----- > From: "Matthias Wessendorf" < matzew at apache.org > > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > > Sent: Thursday, January 15, 2015 3:15:12 PM > Subject: Re: [aerogear-dev] UPS console redesign screencast and demo > > > > On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc < scm.blanc at gmail.com > > wrote: > > > > > > On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > > > On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc < scm.blanc at gmail.com > > wrote: > > > > > > On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > Hin Andres! > > Wow! awesome - I love it! Where can I sign? :-) > > > I watched the excelent video and here are a few coments on the new UI > > > *Wizzard* > > After "Mobile device: Setup variant", when clicking "Continue", it brings > us to the "test push" UI. > > Note - for that it is mandatory that the previous step was really > executed: meaning the app needs to be launched on a (test) device - > otherwise nothing to send the "test push" to :-) > Perhaps we should bake that SKIP option a bit into the TEXT - so that it > is obvious > I have discussed that a bit with Andres. What we could do is after the > user has enter the details of the variant (GCM ApiKey / iOS cert), we could > send a dummy message to the vendors network in order to check if these > settings are correct. This would already be a nice check. > > well, not much will happen: > > https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 > Ah right :) Because there are no installation but beside that > "implementation issue" , would be nice to have a way to test if the API Key > etc ... are valid . > > I agree - we can change it, I think we even have a ticket for that already > > > > > > > > > > > > > Regarding the device itself, indeed, hard to check/test, but what we could > do is check the DB if an installation has been added. (The developer > registers the device and then click next) > > You mean present the "Send dialog" only if there is at least one device > already registered? Otherwise, we can again state: now it's time to get a > device registered... or something like that - not sure > > > > > > > > > "Applications overview" > > wow -> that looks great :) Glad the navigation bar is gone - you are right > -> way better. I also like the dashboard location. > > > "App and its Variants overview" > -> with no installations: not sure we do always, in that case, immediately > show the source code. But I can be wrong > -> with installations: let's integrate pagination. e.g. 10 per page! the > table looks fantastic > > > > "Sender API" > We do have more than Java. also Node.js; I think we could use some sort of > TAB for the actual platform (similar to the client code) > > I do really like the INFO _above_ the code. All info in one place - good > stuff > > > "Send Notification to App" I like the popup/dialog, including the disabled > button when there are no devices. Sweet! > > > > Skip Wizzard -> nice, overview with the blank screens > > > Again, awesome work - I am really looking to get this implemented > > > > On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante < agalante at redhat.com > > wrote: > > > Hi, > > I've been working on UPS console redesign for the last couple of weeks and > I am finally able to share it with you :) > > Here is a screencast walk through: > http://youtu.be/-ab4-F4OCJM > > And here is the prototype for you to click around: > http://andresgalante.com/ups-console/wizard01.html > > > There are a bunch of details to take care about, specially on step 2 of > the wizard, we need to make it goes as smooth as possible. > > Please take a close look and try to find holes in the interaction. Let me > know what you think. > > Thanks! > _______________________________________________ > 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 > > > > -- > 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/20150116/56bb10ed/attachment.html From supittma at redhat.com Fri Jan 16 10:39:59 2015 From: supittma at redhat.com (Summers Pittman) Date: Fri, 16 Jan 2015 10:39:59 -0500 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: References: Message-ID: <54B930CF.50600@redhat.com> On 01/16/2015 09:57 AM, Matthias Wessendorf wrote: > > > On Fri, Jan 16, 2015 at 3:20 PM, Daniel Bevenius > > wrote: > > >IMO the goal is to create a sync client lib, similar to iOS > Sorry, I was actually thinking about the server. The clients (xmpp > and Java) could be moved out into separate projects. > > The servers are currently integrated, so there is a dependency to > xmpp there which might still cause people wanting to try out the > server having to update Android on their system. We could extract > this integrated server into a separate module for those how want > to try it out. > > > yeah, I was not speaking about that :-) With a fresh repo, I have to > comment out the client-xmpp folder, to make it compile. That's what > I'd like to get factored out Or you just keep the Android stuff installed. That way you are also ready to help with testing/reviewing Android code. ;) > > > > > On 16 January 2015 at 15:10, Matthias Wessendorf > > wrote: > > > > On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius > > > wrote: > > Yeah, something needs to be done about this. Either moving > it out, or having it only enabled with a profile (Summers > mentioned this yesterday). > > > -1 on profile. > > IMO the goal is to create a sync client lib, similar to iOS > (which is also on its own repo), so that should not be > included on the java server. Eventually we should move out the > JS bits as well > > > > On 16 January 2015 at 15:01, Matthias Wessendorf > > wrote: > > Hi, > > should we move the Android client-xmpp to its own > repo? Right now, when building the server (and with an > incomplete Android setup (aka new, clean repo)) you > have to comment it out in order to build the server > for running the JS demo. > > IMO it would be nice if that gets moved out to > something like "aerogear-android-xmpp-client". > > 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 > > > > > -- > 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 -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150116/c5d4e8e3/attachment-0001.html From agalante at redhat.com Fri Jan 16 10:42:10 2015 From: agalante at redhat.com (Andres Galante) Date: Fri, 16 Jan 2015 10:42:10 -0500 (EST) Subject: [aerogear-dev] UPS console redesign screencast and demo In-Reply-To: References: <1580533422.2088112.1421340130638.JavaMail.zimbra@redhat.com> <1934250777.2228019.1421411851156.JavaMail.zimbra@redhat.com> <718817877.2255519.1421419012990.JavaMail.zimbra@redhat.com> Message-ID: <1717157996.2274393.1421422930424.JavaMail.zimbra@redhat.com> I want to avoid the user to click Continue without setting up the variant (or event read about it). I'll build a prototype with the btn at the top, gather users and do a usability test next week and to check this behaviour, and the rest of the console. ----- Original Message ----- From: "Sebastien Blanc" To: "AeroGear Developer Mailing List" Sent: Friday, January 16, 2015 12:31:03 PM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo On Fri, Jan 16, 2015 at 3:36 PM, Andres Galante < agalante at redhat.com > wrote: This is the wizard flow, please check if we can do it: 1- Creates the app http://andresgalante.com/ups-console/wizard01.html 2- Creates the variant (we validate this form before moving forward) http://andresgalante.com/ups-console/wizard02.html 3- Information on how to set up the variant. We need to write very good instructions: http://andresgalante.com/ups-console/wizard03.html The code snippet take the whole screen and you have to scroll down to click "continue", maybe it could be collapsed or having the button "continue" at another place ? 4 a- IF we have one installation we let him send the notification: http://andresgalante.com/ups-console/wizard04.html 4 b- IF we have NO installations we give the user the option to skip this step or go back and get instruction to set up his device: http://andresgalante.com/ups-console/wizard04-alt.html 5- set up sender API..... I also added links to edit variant info or app name. What do you think? ----- Original Message ----- From: "Matthias Wessendorf" < matzew at apache.org > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Friday, January 16, 2015 9:47:57 AM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo On Fri, Jan 16, 2015 at 1:37 PM, Andres Galante < agalante at redhat.com > wrote: Good morning! I added tabs on the code snippet (click on the one that has no installations): http://andresgalante.com/ups-console/app-detail-variants.html and sub menu for node.js or other Sender API: http://andresgalante.com/ups-console/app-detail.html good stuff! As for step 2 and 3 of the wizard I still working on different flow options. I'll share with you something today to continue the discussion. cool! looking forward to that :-) Thanks ----- Original Message ----- From: "Matthias Wessendorf" < matzew at apache.org > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Thursday, January 15, 2015 3:15:12 PM Subject: Re: [aerogear-dev] UPS console redesign screencast and demo On Thu, Jan 15, 2015 at 7:09 PM, Sebastien Blanc < scm.blanc at gmail.com > wrote: On Thu, Jan 15, 2015 at 6:43 PM, Matthias Wessendorf < matzew at apache.org > wrote: On Thu, Jan 15, 2015 at 6:26 PM, Sebastien Blanc < scm.blanc at gmail.com > wrote: On Thu, Jan 15, 2015 at 6:12 PM, Matthias Wessendorf < matzew at apache.org > wrote: Hin Andres! Wow! awesome - I love it! Where can I sign? :-) I watched the excelent video and here are a few coments on the new UI *Wizzard* After "Mobile device: Setup variant", when clicking "Continue", it brings us to the "test push" UI. Note - for that it is mandatory that the previous step was really executed: meaning the app needs to be launched on a (test) device - otherwise nothing to send the "test push" to :-) Perhaps we should bake that SKIP option a bit into the TEXT - so that it is obvious I have discussed that a bit with Andres. What we could do is after the user has enter the details of the variant (GCM ApiKey / iOS cert), we could send a dummy message to the vendors network in order to check if these settings are correct. This would already be a nice check. well, not much will happen: https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L57-L59 Ah right :) Because there are no installation but beside that "implementation issue" , would be nice to have a way to test if the API Key etc ... are valid . I agree - we can change it, I think we even have a ticket for that already Regarding the device itself, indeed, hard to check/test, but what we could do is check the DB if an installation has been added. (The developer registers the device and then click next) You mean present the "Send dialog" only if there is at least one device already registered? Otherwise, we can again state: now it's time to get a device registered... or something like that - not sure "Applications overview" wow -> that looks great :) Glad the navigation bar is gone - you are right -> way better. I also like the dashboard location. "App and its Variants overview" -> with no installations: not sure we do always, in that case, immediately show the source code. But I can be wrong -> with installations: let's integrate pagination. e.g. 10 per page! the table looks fantastic "Sender API" We do have more than Java. also Node.js; I think we could use some sort of TAB for the actual platform (similar to the client code) I do really like the INFO _above_ the code. All info in one place - good stuff "Send Notification to App" I like the popup/dialog, including the disabled button when there are no devices. Sweet! Skip Wizzard -> nice, overview with the blank screens Again, awesome work - I am really looking to get this implemented On Thu, Jan 15, 2015 at 5:55 PM, Andres Galante < agalante at redhat.com > wrote: Hi, I've been working on UPS console redesign for the last couple of weeks and I am finally able to share it with you :) Here is a screencast walk through: http://youtu.be/-ab4-F4OCJM And here is the prototype for you to click around: http://andresgalante.com/ups-console/wizard01.html There are a bunch of details to take care about, specially on step 2 of the wizard, we need to make it goes as smooth as possible. Please take a close look and try to find holes in the interaction. Let me know what you think. Thanks! _______________________________________________ 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 -- 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 From matzew at apache.org Fri Jan 16 10:50:48 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 16:50:48 +0100 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: <54B930CF.50600@redhat.com> References: <54B930CF.50600@redhat.com> Message-ID: On Fri, Jan 16, 2015 at 4:39 PM, Summers Pittman wrote: > On 01/16/2015 09:57 AM, Matthias Wessendorf wrote: > > > > On Fri, Jan 16, 2015 at 3:20 PM, Daniel Bevenius < > daniel.bevenius at gmail.com> wrote: > >> >IMO the goal is to create a sync client lib, similar to iOS >> Sorry, I was actually thinking about the server. The clients (xmpp and >> Java) could be moved out into separate projects. >> >> The servers are currently integrated, so there is a dependency to xmpp >> there which might still cause people wanting to try out the server having >> to update Android on their system. We could extract this integrated server >> into a separate module for those how want to try it out. >> > > yeah, I was not speaking about that :-) With a fresh repo, I have to > comment out the client-xmpp folder, to make it compile. That's what I'd > like to get factored out > > Or you just keep the Android stuff installed. That way you are also ready > to help with testing/reviewing Android code. ;) > ehehe - yeah, but a user that just wants the server and perhaps JS, should not be forced to also do the Android dance. But I think you agree here too > > > >> >> >> >> On 16 January 2015 at 15:10, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius < >>> daniel.bevenius at gmail.com> wrote: >>> >>>> Yeah, something needs to be done about this. Either moving it out, or >>>> having it only enabled with a profile (Summers mentioned this yesterday). >>>> >>> >>> -1 on profile. >>> >>> IMO the goal is to create a sync client lib, similar to iOS (which is >>> also on its own repo), so that should not be included on the java server. >>> Eventually we should move out the JS bits as well >>> >>> >>>> >>>> >>>> On 16 January 2015 at 15:01, Matthias Wessendorf >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> should we move the Android client-xmpp to its own repo? Right now, >>>>> when building the server (and with an incomplete Android setup (aka new, >>>>> clean repo)) you have to comment it out in order to build the server for >>>>> running the JS demo. >>>>> >>>>> IMO it would be nice if that gets moved out to something like >>>>> "aerogear-android-xmpp-client". >>>>> >>>>> 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 >>>> >>> >>> >>> >>> -- >>> 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 listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > 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/20150116/efd33f45/attachment-0001.html From supittma at redhat.com Fri Jan 16 10:53:59 2015 From: supittma at redhat.com (Summers Pittman) Date: Fri, 16 Jan 2015 10:53:59 -0500 Subject: [aerogear-dev] Data-Sync: client-xmpp In-Reply-To: References: <54B930CF.50600@redhat.com> Message-ID: <54B93417.5080207@redhat.com> On 01/16/2015 10:50 AM, Matthias Wessendorf wrote: > > > On Fri, Jan 16, 2015 at 4:39 PM, Summers Pittman > wrote: > > On 01/16/2015 09:57 AM, Matthias Wessendorf wrote: >> >> >> On Fri, Jan 16, 2015 at 3:20 PM, Daniel Bevenius >> > wrote: >> >> >IMO the goal is to create a sync client lib, similar to iOS >> Sorry, I was actually thinking about the server. The clients >> (xmpp and Java) could be moved out into separate projects. >> >> The servers are currently integrated, so there is a >> dependency to xmpp there which might still cause people >> wanting to try out the server having to update Android on >> their system. We could extract this integrated server into a >> separate module for those how want to try it out. >> >> >> yeah, I was not speaking about that :-) With a fresh repo, I have >> to comment out the client-xmpp folder, to make it compile. That's >> what I'd like to get factored out > Or you just keep the Android stuff installed. That way you are > also ready to help with testing/reviewing Android code. ;) > > > ehehe - yeah, but a user that just wants the server and perhaps JS, > should not be forced to also do the Android dance. But I think you > agree here too Yup, just giving you a hard time ;). > >> >> >> >> On 16 January 2015 at 15:10, Matthias Wessendorf >> > wrote: >> >> >> >> On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius >> > > wrote: >> >> Yeah, something needs to be done about this. Either >> moving it out, or having it only enabled with a >> profile (Summers mentioned this yesterday). >> >> >> -1 on profile. >> >> IMO the goal is to create a sync client lib, similar to >> iOS (which is also on its own repo), so that should not >> be included on the java server. Eventually we should move >> out the JS bits as well >> >> >> >> On 16 January 2015 at 15:01, Matthias Wessendorf >> > wrote: >> >> Hi, >> >> should we move the Android client-xmpp to its own >> repo? Right now, when building the server (and >> with an incomplete Android setup (aka new, clean >> repo)) you have to comment it out in order to >> build the server for running the JS demo. >> >> IMO it would be nice if that gets moved out to >> something like "aerogear-android-xmpp-client". >> >> 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 >> >> >> >> >> -- >> 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 > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > 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 -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150116/e7da0d50/attachment-0001.html From matzew at apache.org Fri Jan 16 15:05:32 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 21:05:32 +0100 Subject: [aerogear-dev] Releasing new parent/bom (0.2.11) Message-ID: Hi All, I?d like to run a new release of our parent/bom. Here is some changes related to newer versions: * Keycloak update (including jpa-liquibase) * new version of java-apns * bump to Arquillian non-deploying container 0.3.0 * bump to Arquillian Spacelift 1.0.0.Alpha3 Feel free to test it. I have plan to release it next Tuesday. The staging repo is here: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4655/ Cheers, 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/20150116/2b947c75/attachment.html From matzew at apache.org Fri Jan 16 15:50:01 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 16 Jan 2015 21:50:01 +0100 Subject: [aerogear-dev] HTTP layer libraries: handling 4xx status codes Message-ID: Hi, looking at https://twitter.com/mjackson/status/556152800883662848 And yes, this is not specific to iOS, it is IMO a more general thought, but I really think, the author makes a good point with "should be a user concern, not the lib" Deeper in the thread the author of the AFNetworking library has an interesting suggestion, for a lib: https://twitter.com/mattt/status/556181001836449793 I found this debate interesting and felt like sharing :-) -- 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/20150116/58b0d11a/attachment.html From corinnekrych at gmail.com Fri Jan 16 15:57:39 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 16 Jan 2015 21:57:39 +0100 Subject: [aerogear-dev] HTTP layer libraries: handling 4xx status codes In-Reply-To: References: Message-ID: <194EA38E-40F0-49A2-B65C-9E0004039E39@gmail.com> Indeed an interesting question. It?s actually a discussion we had with Christos about what is valid or not. As Mattt stated it in its tweet, this could be configurable and defaulted. In Alamofire there is this notion of pluggable closure for validation: https://github.com/Alamofire/Alamofire/blob/master/Source%2FAlamofire.swift#L848 I think it?s worth a ticket for ios-http lib. ++ Corinne > On 16 Jan 2015, at 21:50, Matthias Wessendorf wrote: > > Hi, > > looking at https://twitter.com/mjackson/status/556152800883662848 > > And yes, this is not specific to iOS, it is IMO a more general thought, but I really think, the author makes a good point with "should be a user concern, not the lib" > > Deeper in the thread the author of the AFNetworking library has an interesting suggestion, for a lib: > https://twitter.com/mattt/status/556181001836449793 > > I found this debate interesting and felt like sharing :-) > > -- > 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 From daniel.bevenius at gmail.com Sun Jan 18 10:54:11 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Sun, 18 Jan 2015 16:54:11 +0100 Subject: [aerogear-dev] Team meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-20150119 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150118/4e240d4e/attachment.html From edewit at redhat.com Mon Jan 19 03:48:03 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 19 Jan 2015 09:48:03 +0100 Subject: [aerogear-dev] oauth2 cordova plugin Message-ID: <624CA255-CD00-478F-A698-DCF1489F129D@redhat.com> Hi, We are pleased to announce that we?ve released version 1.0.1 of the oauth2 cordova plugin, you can find it on plugins.cordova.io like mentioned before this fixes AGCORDOVA-50 and updated some of the documentation on how to use this. Cheers, Erik Jan From cvasilak at gmail.com Mon Jan 19 10:14:49 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 19 Jan 2015 17:14:49 +0200 Subject: [aerogear-dev] Team meeting In-Reply-To: References: Message-ID: fyi, meeting minutes: Meeting ended Mon Jan 19 15:13:18 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-01-19-15.01.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-19-15.01.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-19-15.01.log.html > On Jan 18, 2015, at 5:54 PM, Daniel Bevenius wrote: > > Agenda: > http://oksoclap.com/p/aerogear-team-mgt-20150119 > _______________________________________________ > 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/20150119/2df0dd30/attachment.html From edewit at redhat.com Tue Jan 20 03:47:54 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 20 Jan 2015 09:47:54 +0100 Subject: [aerogear-dev] native ui Message-ID: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> Hi, My idea having a native UI, but all logic in javascript has to have a name so let?s call it hybrid Cordova. I experimented a bit yesterday with the idea and it seems very feasible. On the Cordova home page they have already a guide how to include the Cordova web view on a native project, with that creating a interface to be able to call javascript is almost to easy. What I have now is a native (android) button that calls a javascript function. It uses a plugin to call the javascript and offers a static method for the execution. So to take this to the next level, I think we need a bit of a javascript api to do page navigation. And have a bit of a Java Api to initialise the WebView and specify the name of the script to load. Or just pickup all scripts in a assets directory. WDYT, is it worth exploring further? Cheers, Erik Jan From corinnekrych at gmail.com Tue Jan 20 04:24:03 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 20 Jan 2015 10:24:03 +0100 Subject: [aerogear-dev] native ui In-Reply-To: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> References: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> Message-ID: > On 20 Jan 2015, at 09:47, Erik Jan de Wit wrote: > > Hi, > > My idea having a native UI, but all logic in javascript has to have a name so let?s call it hybrid Cordova. > > I experimented a bit yesterday with the idea and it seems very feasible. On the Cordova home page they have already a guide how to include the Cordova web view on a native project, with that creating a interface to be able to call javascript is almost to easy. > some links: http://cordova.apache.org/docs/en/4.0.0/guide_hybrid_webviews_index.md.html#Embedding%20WebViews an interesting blog post on iOS/Codova embedded webview: http://devgirl.org/2014/07/22/mixing-cordova-phonegap-components-with-nativ/ > What I have now is a native (android) button that calls a javascript function. It uses a plugin to call the javascript and offers a static method for the execution. > mind to share a demo repo? > So to take this to the next level, I think we need a bit of a javascript api to do page navigation. And have a bit of a Java Api to initialise the WebView and specify the name of the script to load. Or just pickup all scripts in a assets directory. > > WDYT, is it worth exploring further? yeap, not sure yet what the js api need to look like but this could be useful for a form-based cordova screen you?d like to integrate with a more complex native apps. we can deal with navigation and data storage. to be investigated further. > > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Tue Jan 20 04:25:03 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 20 Jan 2015 10:25:03 +0100 Subject: [aerogear-dev] native ui In-Reply-To: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> References: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> Message-ID: Sounds like a good project for a student on the "Google Summer of Code"? On Tue, Jan 20, 2015 at 9:47 AM, Erik Jan de Wit wrote: > Hi, > > My idea having a native UI, but all logic in javascript has to have a name > so let?s call it hybrid Cordova. > > I experimented a bit yesterday with the idea and it seems very feasible. > On the Cordova home page they have already a guide how to include the > Cordova web view on a native project, with that creating a interface to be > able to call javascript is almost to easy. > > What I have now is a native (android) button that calls a javascript > function. It uses a plugin to call the javascript and offers a static > method for the execution. > > So to take this to the next level, I think we need a bit of a javascript > api to do page navigation. And have a bit of a Java Api to initialise the > WebView and specify the name of the script to load. Or just pickup all > scripts in a assets directory. > > WDYT, is it worth exploring further? > > 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/20150120/e7ffeb0b/attachment-0001.html From edewit at redhat.com Tue Jan 20 04:39:45 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 20 Jan 2015 10:39:45 +0100 Subject: [aerogear-dev] native ui In-Reply-To: References: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> Message-ID: <6F8A5CC1-1404-4AD5-B1C0-568EEA69C52E@redhat.com> > > mind to share a demo repo? https://github.com/edewit/CordovaCommunication > >> So to take this to the next level, I think we need a bit of a javascript api to do page navigation. And have a bit of a Java Api to initialise the WebView and specify the name of the script to load. Or just pickup all scripts in a assets directory. >> >> WDYT, is it worth exploring further? > > yeap, not sure yet what the js api need to look like but this could be useful for a form-based cordova screen you?d like to integrate with a more complex native apps. > we can deal with navigation and data storage. > to be investigated further. Cool thing about this you could still use all cordova plugins, so you could have data storage as a native still. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150120/58c1bb9c/attachment.html From edewit at redhat.com Tue Jan 20 04:40:42 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 20 Jan 2015 10:40:42 +0100 Subject: [aerogear-dev] native ui In-Reply-To: References: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> Message-ID: <65B14300-CCCB-4614-BEC8-BD9C5B1442BB@redhat.com> > Sounds like a good project for a student on the "Google Summer of Code"? > Right, or I could do it while I ?wait? for iOS and android sync libraries From agalante at redhat.com Tue Jan 20 07:04:34 2015 From: agalante at redhat.com (Andres Galante) Date: Tue, 20 Jan 2015 07:04:34 -0500 (EST) Subject: [aerogear-dev] AeroGear.org website UI Done In-Reply-To: <26458751.2707757.1421755196470.JavaMail.zimbra@redhat.com> Message-ID: <1443176583.2708973.1421755474773.JavaMail.zimbra@redhat.com> Hi! Before I continue with UPS console redesign, I want to make sure that everyone has review the new website. >From your point of view UI is done. What is left to be done: 1- Review overall design and UI again. 2- JS on news and the parts, Lukas is taking care of it. 3- Check if index pages (roadmap, guides, docs and demos) are ok and pointing to the right direction. 4- Text! Review text, make sure there are no typos and dummy texts are fill out. 5- Am I missing something? You can see this on new-design branch: https://github.com/andresgalante/aerogear.org/tree/new-design Thanks! Andr?s From matzew at apache.org Tue Jan 20 11:01:14 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 20 Jan 2015 17:01:14 +0100 Subject: [aerogear-dev] Feature based landing page (and new UI) Message-ID: Hi, for all of our different push offerings, we have a central landing page ([1]), and soon that page will also list our work on the WebPush spec ([2]) Since this model is quite handy, having a centralized landing page, I'd propose we do that for other features, like OAuth2 and Sync as well. With the new design, the "feature" is more a module, which is fine. The Screenshot of the modules page ([3]), we list all of our feature, or more modules ;-) While for PUSH we have more than just one repo (UPS, SimplePush and now WebPush + demos), I think the getting started should go to a 'feature' (or module) landing page. For AeroGearPush that would be [1], or something similar. Basically, on this "module landing page", I'd like to list all relevant GH repos, link to JIRA and perhaps other resources. Any thoughts? Now, taking a different example, sync, we would list these repos: iOS: https://github.com/aerogear/aerogear-ios-sync https://github.com/aerogear/aerogear-ios-sync-client https://github.com/aerogear/aerogear-ios-sync-demo Android: https://github.com/aerogear/aerogear-android-sync JS: https://github.com/aerogear/aerogear-js (part of the lib) https://github.com/aerogear/aerogear-js-cookbook (a sync demo, based on node) Sync-Server: https://github.com/aerogear/aerogear-sync-server + linking to the JIRAs tracked for the different Sync milestones (currently the ones with the 'sync-1.0.0.alpha.1' label) When we have clear "module" entry or landing pages, it's easy for new users, to get an understanding what it is all about. Instead of jump around on the site (which is why we generally do the new site :-)) Does that make sense ? -Matthias [1] https://aerogear.org/push/ [2] https://github.com/aerogear/aerogear.org/pull/468 [3] https://www.dropbox.com/s/zypkqd3nn3wma9w/Screen%20Shot%202015-01-20%20at%2016.38.33.png?dl=0 -- 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/20150120/542b6001/attachment.html From daniel at passos.me Tue Jan 20 11:19:52 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 20 Jan 2015 14:19:52 -0200 Subject: [aerogear-dev] [GitHub] Subscribed to 4 aerogear repositories In-Reply-To: <54be4df3d9a82_46f33ffd658b72a0425625@github-lowworker11-cp1-prd.iad.github.net.mail> References: <54be4df3d9a82_46f33ffd658b72a0425625@github-lowworker11-cp1-prd.iad.github.net.mail> Message-ID: On Tue, Jan 20, 2015 at 10:45 AM, GitHub wrote: > Hey there, we're just writing to let you know that you've automatically > started watching several repositories on GitHub. > > You'll receive notifications for all issues, pull requests, and comments > that happen inside the repository. If you would like to stop watching any > of these repositories, you can manage your settings here: > > https://github.com/aerogear/aerogear-ios-sync-demo/subscription Why not add it on cookbook instead of create a new repo? -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150120/f0d8c3d9/attachment.html From lholmqui at redhat.com Tue Jan 20 11:23:12 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 20 Jan 2015 11:23:12 -0500 Subject: [aerogear-dev] Website Guides Links Message-ID: <6A557996-2E11-4231-BB00-696DD2C0EDC8@redhat.com> https://aerogear.org/docs/guides/ So a couple things First, looking at this list under the ?Getting Started? section. I?m wondering how much of it can be removed FAQ Get Started With AeroGear.js Get Started With HTML5 Mobile Web Development Get Started with Hybrid Application Frameworks Get Started with iOS and Xcode Get Started with iOS and AeroGear Xcode Template Deploying HTML5 Applications to Openshift HTML5 Mobile Quickstart & Archetype Deep Dive HTML5 + REST Applications Cordova Setup Converting an AeroGear HTML5 + REST Web App to a Hybrid App with Apache Cordova Tutorial: Android Development w/ PhoneGap/Apache Cordova in JBoss Developer Studio 5 The getting started with AeroGear.js talks about pipes as does the FAQ. The various HTML5 links are very much out of date and i think are better taken care of by the JBoss Developer quickstarts http://www.jboss.org/get-started/ I would like to remove this section and just use section below it ?User Guides? which link to the cookbooks Second, The "Supported Platforms? section i think is a bit outdated also, in terms of browser support, at least wrt IE and mobile browsers. I wonder if this section can be removed also, and I can just add the browser targets to the README of the aerogear.js repo -Luke -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150120/fe107d35/attachment-0001.html From corinnekrych at gmail.com Tue Jan 20 11:26:36 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 20 Jan 2015 17:26:36 +0100 Subject: [aerogear-dev] [GitHub] Subscribed to 4 aerogear repositories In-Reply-To: References: <54be4df3d9a82_46f33ffd658b72a0425625@github-lowworker11-cp1-prd.iad.github.net.mail> Message-ID: <1063CAD0-F858-44FE-8B02-490ACC7C1767@gmail.com> That?s a good question we also have other demo on separate repos though? in that case, we add a link in README.md + gh submodule link. let me create a jira to track that... > On 20 Jan 2015, at 17:19, Daniel Passos wrote: > > On Tue, Jan 20, 2015 at 10:45 AM, GitHub wrote: > Hey there, we're just writing to let you know that you've automatically started watching several repositories on GitHub. > > You'll receive notifications for all issues, pull requests, and comments that happen inside the repository. If you would like to stop watching any of these repositories, you can manage your settings here: > > https://github.com/aerogear/aerogear-ios-sync-demo/subscription > > Why not add it on cookbook instead of create a new repo? > > -- Passos > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Tue Jan 20 11:28:38 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 20 Jan 2015 17:28:38 +0100 Subject: [aerogear-dev] [GitHub] Subscribed to 4 aerogear repositories In-Reply-To: References: <54be4df3d9a82_46f33ffd658b72a0425625@github-lowworker11-cp1-prd.iad.github.net.mail> Message-ID: good idea. Here is the ticket: https://issues.jboss.org/browse/AGIOS-337 I just imported all of the src to the aerogear org, so that we all can push to it On Tue, Jan 20, 2015 at 5:19 PM, Daniel Passos wrote: > On Tue, Jan 20, 2015 at 10:45 AM, GitHub wrote: > >> Hey there, we're just writing to let you know that you've automatically >> started watching several repositories on GitHub. >> >> You'll receive notifications for all issues, pull requests, and comments >> that happen inside the repository. If you would like to stop watching any >> of these repositories, you can manage your settings here: >> >> https://github.com/aerogear/aerogear-ios-sync-demo/subscription > > > Why not add it on cookbook instead of create a new repo? > > -- 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/20150120/271a5803/attachment.html From daniel.bevenius at gmail.com Tue Jan 20 11:33:00 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Tue, 20 Jan 2015 17:33:00 +0100 Subject: [aerogear-dev] Website Guides Links In-Reply-To: <6A557996-2E11-4231-BB00-696DD2C0EDC8@redhat.com> References: <6A557996-2E11-4231-BB00-696DD2C0EDC8@redhat.com> Message-ID: +1 on removing tisdag 20 januari 2015 skrev Lucas Holmquist : > https://aerogear.org/docs/guides/ > > > So a couple things > > First, looking at this list under the ?Getting Started? section. I?m > wondering how much of it can be removed > > > - FAQ > - Get Started With AeroGear.js > > - Get Started With HTML5 Mobile Web Development > > - Get Started with Hybrid Application Frameworks > > - Get Started with iOS and Xcode > > - Get Started with iOS and AeroGear Xcode Template > > - Deploying HTML5 Applications to Openshift > > - HTML5 Mobile Quickstart & Archetype Deep Dive > > - HTML5 + REST Applications > > - Cordova Setup > > - Converting an AeroGear HTML5 + REST Web App to a Hybrid App with > Apache Cordova > > - Tutorial: Android Development w/ PhoneGap/Apache Cordova in JBoss > Developer Studio 5 > > > > The getting started with AeroGear.js talks about pipes as does the FAQ. > > The various HTML5 links are very much out of date and i think are better > taken care of by the JBoss Developer quickstarts > http://www.jboss.org/get-started/ > > I would like to remove this section and just use section below it ?User > Guides? which link to the cookbooks > > > Second, The "Supported Platforms? section i think is a bit outdated also, > in terms of browser support, at least wrt IE and mobile browsers. > > I wonder if this section can be removed also, and I can just add the > browser targets to the README of the aerogear.js repo > > > -Luke > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150120/08de0899/attachment.html From matzew at apache.org Tue Jan 20 11:33:18 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 20 Jan 2015 17:33:18 +0100 Subject: [aerogear-dev] Website Guides Links In-Reply-To: <6A557996-2E11-4231-BB00-696DD2C0EDC8@redhat.com> References: <6A557996-2E11-4231-BB00-696DD2C0EDC8@redhat.com> Message-ID: On Tue, Jan 20, 2015 at 5:23 PM, Lucas Holmquist wrote: > https://aerogear.org/docs/guides/ > > > So a couple things > > First, looking at this list under the ?Getting Started? section. I?m > wondering how much of it can be removed > > > - FAQ > - Get Started With AeroGear.js > > - Get Started With HTML5 Mobile Web Development > > - Get Started with Hybrid Application Frameworks > > - Get Started with iOS and Xcode > > - Get Started with iOS and AeroGear Xcode Template > > - Deploying HTML5 Applications to Openshift > > - HTML5 Mobile Quickstart & Archetype Deep Dive > > - HTML5 + REST Applications > > - Cordova Setup > > - Converting an AeroGear HTML5 + REST Web App to a Hybrid App with > Apache Cordova > > - Tutorial: Android Development w/ PhoneGap/Apache Cordova in JBoss > Developer Studio 5 > > > > The getting started with AeroGear.js talks about pipes as does the FAQ. > > The various HTML5 links are very much out of date and i think are better > taken care of by the JBoss Developer quickstarts > http://www.jboss.org/get-started/ > > I would like to remove this section and just use section below it ?User > Guides? which link to the cookbooks > +1000 also the cookbooks is not JUST code, they do (should) also give a very detailed explanation about code and want not. In fact, it's a better tutorial, that comes with code :-) Since the cookbooks have different demos, perhaps it could have a GETTING_STARTED.md file that links to (external?) pages: how to setup Xcode or Android Studio in those cases you need a IDE (yeah, JS a text editor is good enough) > > > Second, The "Supported Platforms? section i think is a bit outdated also, > in terms of browser support, at least wrt IE and mobile browsers. > > I wonder if this section can be removed also, and I can just add the > browser targets to the README of the aerogear.js repo > Right. do it! :) The native platforms all have a landing page and there we should say "supports version blah and later" > > > -Luke > > > > _______________________________________________ > 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/20150120/b6cdc430/attachment.html From daniel at passos.me Tue Jan 20 11:35:35 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 20 Jan 2015 14:35:35 -0200 Subject: [aerogear-dev] [GitHub] Subscribed to 4 aerogear repositories In-Reply-To: <1063CAD0-F858-44FE-8B02-490ACC7C1767@gmail.com> References: <54be4df3d9a82_46f33ffd658b72a0425625@github-lowworker11-cp1-prd.iad.github.net.mail> <1063CAD0-F858-44FE-8B02-490ACC7C1767@gmail.com> Message-ID: On Tue, Jan 20, 2015 at 2:26 PM, Corinne Krych wrote: > That?s a good question > we also have other demo on separate repos though? > I know, but IMHO (except by pushhelloword/quickstart) we need move all example apps to the cookbook repo. That is what we (Android land) are doing. > in that case, we add a link in README.md + gh submodule link. > -1 to submodules, +1 to add on README > let me create a jira to track that... > > > On 20 Jan 2015, at 17:19, Daniel Passos wrote: > > > > On Tue, Jan 20, 2015 at 10:45 AM, GitHub wrote: > > Hey there, we're just writing to let you know that you've automatically > started watching several repositories on GitHub. > > > > You'll receive notifications for all issues, pull requests, and comments > that happen inside the repository. If you would like to stop watching any > of these repositories, you can manage your settings here: > > > > https://github.com/aerogear/aerogear-ios-sync-demo/subscription > > > > Why not add it on cookbook instead of create a new repo? > > > > -- 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/20150120/67845ed1/attachment-0001.html From daniel at passos.me Tue Jan 20 11:36:45 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 20 Jan 2015 14:36:45 -0200 Subject: [aerogear-dev] Website Guides Links In-Reply-To: References: <6A557996-2E11-4231-BB00-696DD2C0EDC8@redhat.com> Message-ID: +9001 On Tue, Jan 20, 2015 at 2:33 PM, Matthias Wessendorf wrote: > > > On Tue, Jan 20, 2015 at 5:23 PM, Lucas Holmquist > wrote: > >> https://aerogear.org/docs/guides/ >> >> >> So a couple things >> >> First, looking at this list under the ?Getting Started? section. I?m >> wondering how much of it can be removed >> >> >> - FAQ >> - Get Started With AeroGear.js >> >> - Get Started With HTML5 Mobile Web Development >> >> - Get Started with Hybrid Application Frameworks >> >> - Get Started with iOS and Xcode >> >> - Get Started with iOS and AeroGear Xcode Template >> >> - Deploying HTML5 Applications to Openshift >> >> - HTML5 Mobile Quickstart & Archetype Deep Dive >> >> - HTML5 + REST Applications >> >> - Cordova Setup >> >> - Converting an AeroGear HTML5 + REST Web App to a Hybrid App with >> Apache Cordova >> >> - Tutorial: Android Development w/ PhoneGap/Apache Cordova in JBoss >> Developer Studio 5 >> >> >> >> The getting started with AeroGear.js talks about pipes as does the FAQ. >> >> The various HTML5 links are very much out of date and i think are better >> taken care of by the JBoss Developer quickstarts >> http://www.jboss.org/get-started/ >> >> I would like to remove this section and just use section below it ?User >> Guides? which link to the cookbooks >> > > +1000 > > also the cookbooks is not JUST code, they do (should) also give a very > detailed explanation about code and want not. In fact, it's a better > tutorial, that comes with code :-) > > Since the cookbooks have different demos, perhaps it could have a > GETTING_STARTED.md file that links to (external?) pages: how to setup Xcode > or Android Studio in those cases you need a IDE (yeah, JS a text editor is > good enough) > > > > >> >> >> Second, The "Supported Platforms? section i think is a bit outdated >> also, in terms of browser support, at least wrt IE and mobile browsers. >> >> I wonder if this section can be removed also, and I can just add the >> browser targets to the README of the aerogear.js repo >> > > Right. do it! :) > > The native platforms all have a landing page and there we should say > "supports version blah and later" > > > > >> >> >> -Luke >> >> >> >> _______________________________________________ >> 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/20150120/d6c33d88/attachment.html From matzew at apache.org Tue Jan 20 11:43:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 20 Jan 2015 17:43:41 +0100 Subject: [aerogear-dev] [GitHub] Subscribed to 4 aerogear repositories In-Reply-To: References: <54be4df3d9a82_46f33ffd658b72a0425625@github-lowworker11-cp1-prd.iad.github.net.mail> <1063CAD0-F858-44FE-8B02-490ACC7C1767@gmail.com> Message-ID: On Tue, Jan 20, 2015 at 5:35 PM, Daniel Passos wrote: > On Tue, Jan 20, 2015 at 2:26 PM, Corinne Krych > wrote: > >> That?s a good question >> we also have other demo on separate repos though? >> > > I know, but IMHO (except by pushhelloword/quickstart) we need move all > example apps to the cookbook repo. That is what we (Android land) are doing. > > >> in that case, we add a link in README.md + gh submodule link. >> > > -1 to submodules, +1 to add on README > yeah, submodules suck - see my earlier email, I created a JIRA for including the sync demo to the cookbook -M > > >> let me create a jira to track that... >> >> > On 20 Jan 2015, at 17:19, Daniel Passos wrote: >> > >> > On Tue, Jan 20, 2015 at 10:45 AM, GitHub wrote: >> > Hey there, we're just writing to let you know that you've automatically >> started watching several repositories on GitHub. >> > >> > You'll receive notifications for all issues, pull requests, and >> comments that happen inside the repository. If you would like to stop >> watching any of these repositories, you can manage your settings here: >> > >> > https://github.com/aerogear/aerogear-ios-sync-demo/subscription >> > >> > Why not add it on cookbook instead of create a new repo? >> > >> > -- 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 > -- 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/20150120/fcd24001/attachment.html From supittma at redhat.com Tue Jan 20 12:38:19 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 20 Jan 2015 12:38:19 -0500 Subject: [aerogear-dev] native ui In-Reply-To: <65B14300-CCCB-4614-BEC8-BD9C5B1442BB@redhat.com> References: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> <65B14300-CCCB-4614-BEC8-BD9C5B1442BB@redhat.com> Message-ID: <54BE928B.7090902@redhat.com> On 01/20/2015 04:40 AM, Erik Jan de Wit wrote: >> Sounds like a good project for a student on the "Google Summer of Code"? >> > Right, or I could do it while I ?wait? for iOS and android sync libraries Or you could help us with the sync libraries. Right now passos and I are discussing making APIs to connect with the sync server and FeedHenry's services. After we figure out what that will look like from an API/usage standpoint we can begin designing that code. After that point we will need to figure out how to work it into the Android Sync Adapter framework (which will probably require some work on the auth/authz end). We've got a planning gist right now to define our epics before we make individual JIRA tasks. https://gist.github.com/secondsun/68cbbc54366b653f57d6 If you could become a FH sync expert this week it would do amazing things for our ability to move forward. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From matzew at apache.org Tue Jan 20 12:49:00 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 20 Jan 2015 18:49:00 +0100 Subject: [aerogear-dev] native ui In-Reply-To: <54BE928B.7090902@redhat.com> References: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> <65B14300-CCCB-4614-BEC8-BD9C5B1442BB@redhat.com> <54BE928B.7090902@redhat.com> Message-ID: On Tue, Jan 20, 2015 at 6:38 PM, Summers Pittman wrote: > On 01/20/2015 04:40 AM, Erik Jan de Wit wrote: > >> Sounds like a good project for a student on the "Google Summer of Code"? > >> > > Right, or I could do it while I ?wait? for iOS and android sync libraries > Or you could help us with the sync libraries. > that or anything else, is way higher priority > > Right now passos and I are discussing making APIs to connect with the > sync server and FeedHenry's services. Not sure we should duplicate functionality that's already available inside of the FH SDK. My pref. here is focusing on our real-time sync server first..... I don't get why using the FH SDK for accessing the sync framework from feedhenry is not good enough > After we figure out what that > will look like from an API/usage standpoint we can begin designing that > code. After that point we will need to figure out how to work it into > the Android Sync Adapter framework (which will probably require some > work on the auth/authz end). > > We've got a planning gist right now to define our epics before we make > individual JIRA tasks. > > https://gist.github.com/secondsun/68cbbc54366b653f57d6 > > If you could become a FH sync expert this week it would do amazing > things for our ability to move forward. > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > _______________________________________________ > 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/20150120/3d877100/attachment-0001.html From supittma at redhat.com Tue Jan 20 12:54:19 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 20 Jan 2015 12:54:19 -0500 Subject: [aerogear-dev] native ui In-Reply-To: References: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> <65B14300-CCCB-4614-BEC8-BD9C5B1442BB@redhat.com> <54BE928B.7090902@redhat.com> Message-ID: <54BE964B.4010107@redhat.com> On 01/20/2015 12:49 PM, Matthias Wessendorf wrote: > > > On Tue, Jan 20, 2015 at 6:38 PM, Summers Pittman > wrote: > > On 01/20/2015 04:40 AM, Erik Jan de Wit wrote: > >> Sounds like a good project for a student on the "Google Summer > of Code"? > >> > > Right, or I could do it while I ?wait? for iOS and android sync > libraries > Or you could help us with the sync libraries. > > > that or anything else, is way higher priority > > > Right now passos and I are discussing making APIs to connect with the > sync server and FeedHenry's services. > > > Not sure we should duplicate functionality that's already available > inside of the FH SDK. > My pref. here is focusing on our real-time sync server first..... I > don't get why using the FH SDK for accessing the sync framework from > feedhenry is not good enough It may be enough. I don't have enough information to make this claim however. At the very least there will need to be shim code to make sure it plays nicely with the other Aerogear things. For instance we may want to use a Keycloak OAuth solution to retrieve tokens to talk to FH.sync. We will need to have enough support in AG.sync to pass those tokens to FH.sync. Also the FH Android SDK is very incomplete right now and is missing features that are in the FH JS SDK and in AG Android. They will need to be written at some point by someone. > > After we figure out what that > will look like from an API/usage standpoint we can begin designing > that > code. After that point we will need to figure out how to work it into > the Android Sync Adapter framework (which will probably require some > work on the auth/authz end). > > We've got a planning gist right now to define our epics before we make > individual JIRA tasks. > > https://gist.github.com/secondsun/68cbbc54366b653f57d6 > > If you could become a FH sync expert this week it would do amazing > things for our ability to move forward. > > > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > _______________________________________________ > 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 -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150120/d524c0c5/attachment.html From matzew at apache.org Tue Jan 20 13:02:06 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 20 Jan 2015 19:02:06 +0100 Subject: [aerogear-dev] native ui In-Reply-To: <54BE964B.4010107@redhat.com> References: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> <65B14300-CCCB-4614-BEC8-BD9C5B1442BB@redhat.com> <54BE928B.7090902@redhat.com> <54BE964B.4010107@redhat.com> Message-ID: On Tue, Jan 20, 2015 at 6:54 PM, Summers Pittman wrote: > On 01/20/2015 12:49 PM, Matthias Wessendorf wrote: > > > > On Tue, Jan 20, 2015 at 6:38 PM, Summers Pittman > wrote: > >> On 01/20/2015 04:40 AM, Erik Jan de Wit wrote: >> >> Sounds like a good project for a student on the "Google Summer of >> Code"? >> >> >> > Right, or I could do it while I ?wait? for iOS and android sync >> libraries >> Or you could help us with the sync libraries. >> > > that or anything else, is way higher priority > > >> >> Right now passos and I are discussing making APIs to connect with the >> sync server and FeedHenry's services. > > > Not sure we should duplicate functionality that's already available > inside of the FH SDK. > My pref. here is focusing on our real-time sync server first..... I > don't get why using the FH SDK for accessing the sync framework from > feedhenry is not good enough > > It may be enough. I don't have enough information to make this claim > however. At the very least there will need to be shim code to make sure it > plays nicely with the other Aerogear things. For instance we may want to > use a Keycloak OAuth solution to retrieve tokens to talk to FH.sync. We > will need to have enough support in AG.sync to pass those tokens to FH.sync. > Again, my preference here is to limit our current sync work on the real-time stuff. We can do the FH 'adapter' always at a later time (e.g. this summer or fall) -Matthias > > Also the FH Android SDK is very incomplete right now and is missing > features that are in the FH JS SDK and in AG Android. They will need to be > written at some point by someone. > > > > > > > >> After we figure out what that >> will look like from an API/usage standpoint we can begin designing that >> code. After that point we will need to figure out how to work it into >> the Android Sync Adapter framework (which will probably require some >> work on the auth/authz end). >> >> We've got a planning gist right now to define our epics before we make >> individual JIRA tasks. >> >> https://gist.github.com/secondsun/68cbbc54366b653f57d6 >> >> If you could become a FH sync expert this week it would do amazing >> things for our ability to move forward. > > >> >> >> > >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> -- >> Summers Pittman >> >>Phone:404 941 4698 >> >>Java is my crack. >> >> _______________________________________________ >> 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 listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > -- 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/20150120/f57c765d/attachment.html From lholmqui at redhat.com Tue Jan 20 13:39:30 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 20 Jan 2015 13:39:30 -0500 Subject: [aerogear-dev] Website Guides Links In-Reply-To: References: <6A557996-2E11-4231-BB00-696DD2C0EDC8@redhat.com> Message-ID: Here is the PR for this, https://github.com/aerogear/aerogear.org/pull/470 > On Jan 20, 2015, at 11:36 AM, Daniel Passos wrote: > > +9001 > > On Tue, Jan 20, 2015 at 2:33 PM, Matthias Wessendorf > wrote: > > > On Tue, Jan 20, 2015 at 5:23 PM, Lucas Holmquist > wrote: > https://aerogear.org/docs/guides/ > > > So a couple things > > First, looking at this list under the ?Getting Started? section. I?m wondering how much of it can be removed > > FAQ > Get Started With AeroGear.js > Get Started With HTML5 Mobile Web Development > Get Started with Hybrid Application Frameworks > Get Started with iOS and Xcode > Get Started with iOS and AeroGear Xcode Template > Deploying HTML5 Applications to Openshift > HTML5 Mobile Quickstart & Archetype Deep Dive > HTML5 + REST Applications > Cordova Setup > Converting an AeroGear HTML5 + REST Web App to a Hybrid App with Apache Cordova > Tutorial: Android Development w/ PhoneGap/Apache Cordova in JBoss Developer Studio 5 > > The getting started with AeroGear.js talks about pipes as does the FAQ. > > The various HTML5 links are very much out of date and i think are better taken care of by the JBoss Developer quickstarts http://www.jboss.org/get-started/ > > I would like to remove this section and just use section below it ?User Guides? which link to the cookbooks > > +1000 > > also the cookbooks is not JUST code, they do (should) also give a very detailed explanation about code and want not. In fact, it's a better tutorial, that comes with code :-) > > Since the cookbooks have different demos, perhaps it could have a GETTING_STARTED.md file that links to (external?) pages: how to setup Xcode or Android Studio in those cases you need a IDE (yeah, JS a text editor is good enough) > > > > > > Second, The "Supported Platforms? section i think is a bit outdated also, in terms of browser support, at least wrt IE and mobile browsers. > > I wonder if this section can be removed also, and I can just add the browser targets to the README of the aerogear.js repo > > Right. do it! :) > > The native platforms all have a landing page and there we should say "supports version blah and later" > > > > > > -Luke > > > > _______________________________________________ > 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/20150120/f23000d3/attachment-0001.html From edewit at redhat.com Tue Jan 20 13:50:47 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 20 Jan 2015 19:50:47 +0100 Subject: [aerogear-dev] native ui In-Reply-To: References: <67A34064-8482-4BF0-8EA5-497BE4BC8143@redhat.com> <65B14300-CCCB-4614-BEC8-BD9C5B1442BB@redhat.com> <54BE928B.7090902@redhat.com> Message-ID: On 20 Jan,2015, at 18:49 , Matthias Wessendorf wrote: > > > On Tue, Jan 20, 2015 at 6:38 PM, Summers Pittman wrote: > On 01/20/2015 04:40 AM, Erik Jan de Wit wrote: > >> Sounds like a good project for a student on the "Google Summer of Code"? > >> > > Right, or I could do it while I ?wait? for iOS and android sync libraries > Or you could help us with the sync libraries. > > that or anything else, is way higher priority don?t have other ideas atm -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150120/aa5feafb/attachment.html From corinnekrych at gmail.com Tue Jan 20 14:59:54 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 20 Jan 2015 20:59:54 +0100 Subject: [aerogear-dev] Website Guides Links In-Reply-To: References: <6A557996-2E11-4231-BB00-696DD2C0EDC8@redhat.com> Message-ID: I?d like to keep the content of: ? Get Started with iOS and AeroGear Xcode Template as we?ll have new swift template coming out in AeorGear iOS 2.2 (AGIOS-291) Let me review your PR? ++ Corinne > On 20 Jan 2015, at 19:39, Lucas Holmquist wrote: > > Here is the PR for this, https://github.com/aerogear/aerogear.org/pull/470 >> On Jan 20, 2015, at 11:36 AM, Daniel Passos wrote: >> >> +9001 >> >> On Tue, Jan 20, 2015 at 2:33 PM, Matthias Wessendorf wrote: >> >> >> On Tue, Jan 20, 2015 at 5:23 PM, Lucas Holmquist wrote: >> https://aerogear.org/docs/guides/ >> >> >> So a couple things >> >> First, looking at this list under the ?Getting Started? section. I?m wondering how much of it can be removed >> >> ? FAQ >> ? Get Started With AeroGear.js >> ? Get Started With HTML5 Mobile Web Development >> ? Get Started with Hybrid Application Frameworks >> ? Get Started with iOS and Xcode >> ? Get Started with iOS and AeroGear Xcode Template >> ? Deploying HTML5 Applications to Openshift >> ? HTML5 Mobile Quickstart & Archetype Deep Dive >> ? HTML5 + REST Applications >> ? Cordova Setup >> ? Converting an AeroGear HTML5 + REST Web App to a Hybrid App with Apache Cordova >> ? Tutorial: Android Development w/ PhoneGap/Apache Cordova in JBoss Developer Studio 5 >> >> The getting started with AeroGear.js talks about pipes as does the FAQ. >> >> The various HTML5 links are very much out of date and i think are better taken care of by the JBoss Developer quickstarts http://www.jboss.org/get-started/ >> >> I would like to remove this section and just use section below it ?User Guides? which link to the cookbooks >> >> +1000 >> >> also the cookbooks is not JUST code, they do (should) also give a very detailed explanation about code and want not. In fact, it's a better tutorial, that comes with code :-) >> >> Since the cookbooks have different demos, perhaps it could have a GETTING_STARTED.md file that links to (external?) pages: how to setup Xcode or Android Studio in those cases you need a IDE (yeah, JS a text editor is good enough) >> >> >> >> >> >> Second, The "Supported Platforms? section i think is a bit outdated also, in terms of browser support, at least wrt IE and mobile browsers. >> >> I wonder if this section can be removed also, and I can just add the browser targets to the README of the aerogear.js repo >> >> Right. do it! :) >> >> The native platforms all have a landing page and there we should say "supports version blah and later" >> >> >> >> >> >> -Luke >> >> >> >> _______________________________________________ >> 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 From corinnekrych at gmail.com Tue Jan 20 15:58:15 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 20 Jan 2015 21:58:15 +0100 Subject: [aerogear-dev] Feature based landing page (and new UI) In-Reply-To: References: Message-ID: <16864897-C35F-4869-92EC-80DCB1465BA1@gmail.com> > On 20 Jan 2015, at 17:01, Matthias Wessendorf wrote: > > Hi, > > for all of our different push offerings, we have a central landing page ([1]), and soon that page will also list our work on the WebPush spec ([2]) > Since this model is quite handy, having a centralized landing page, I'd propose we do that for other features, like OAuth2 and Sync as well. > > > With the new design, the "feature" is more a module, which is fine. The Screenshot of the modules page ([3]), we list all of our feature, or more modules ;-) > While for PUSH we have more than just one repo (UPS, SimplePush and now WebPush + demos), I think the getting started should go to a 'feature' (or module) landing page. For AeroGearPush that would be [1], or something similar. Basically, on this "module landing page", I'd like to list all relevant GH repos, link to JIRA and perhaps other resources. > > Any thoughts? > > > Now, taking a different example, sync, we would list these repos: > > iOS: > https://github.com/aerogear/aerogear-ios-sync > https://github.com/aerogear/aerogear-ios-sync-client > https://github.com/aerogear/aerogear-ios-sync-demo > > Android: > https://github.com/aerogear/aerogear-android-sync > > JS: > https://github.com/aerogear/aerogear-js (part of the lib) > https://github.com/aerogear/aerogear-js-cookbook (a sync demo, based on node) > > Sync-Server: > https://github.com/aerogear/aerogear-sync-server > > > + linking to the JIRAs tracked for the different Sync milestones (currently the ones with the 'sync-1.0.0.alpha.1' label) > Do you mean adding a fifth button ?List of JIRA tickets" after ?github repo? or this JIRA button is only accessible via Doc->roadmap menu? > > When we have clear "module" entry or landing pages, it's easy for new users, to get an understanding what it is all about. Instead of jump around on the site (which is why we generally do the new site :-)) > > > Does that make sense ? > > > -Matthias > > [1] https://aerogear.org/push/ > [2] https://github.com/aerogear/aerogear.org/pull/468 > [3] https://www.dropbox.com/s/zypkqd3nn3wma9w/Screen%20Shot%202015-01-20%20at%2016.38.33.png?dl=0 > > > -- > 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 From matzew at apache.org Tue Jan 20 17:22:09 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 20 Jan 2015 23:22:09 +0100 Subject: [aerogear-dev] Feature based landing page (and new UI) In-Reply-To: <16864897-C35F-4869-92EC-80DCB1465BA1@gmail.com> References: <16864897-C35F-4869-92EC-80DCB1465BA1@gmail.com> Message-ID: On Tue, Jan 20, 2015 at 9:58 PM, Corinne Krych wrote: > > > On 20 Jan 2015, at 17:01, Matthias Wessendorf wrote: > > > > Hi, > > > > for all of our different push offerings, we have a central landing page > ([1]), and soon that page will also list our work on the WebPush spec ([2]) > > Since this model is quite handy, having a centralized landing page, I'd > propose we do that for other features, like OAuth2 and Sync as well. > > > > > > With the new design, the "feature" is more a module, which is fine. The > Screenshot of the modules page ([3]), we list all of our feature, or more > modules ;-) > > While for PUSH we have more than just one repo (UPS, SimplePush and now > WebPush + demos), I think the getting started should go to a 'feature' (or > module) landing page. For AeroGearPush that would be [1], or something > similar. Basically, on this "module landing page", I'd like to list all > relevant GH repos, link to JIRA and perhaps other resources. > > > > Any thoughts? > > > > > > Now, taking a different example, sync, we would list these repos: > > > > iOS: > > https://github.com/aerogear/aerogear-ios-sync > > https://github.com/aerogear/aerogear-ios-sync-client > > https://github.com/aerogear/aerogear-ios-sync-demo > > > > Android: > > https://github.com/aerogear/aerogear-android-sync > > > > JS: > > https://github.com/aerogear/aerogear-js (part of the lib) > > https://github.com/aerogear/aerogear-js-cookbook (a sync demo, based on > node) > > > > Sync-Server: > > https://github.com/aerogear/aerogear-sync-server > > > > > > + linking to the JIRAs tracked for the different Sync milestones > (currently the ones with the 'sync-1.0.0.alpha.1' label) > > > > Do you mean adding a fifth button ?List of JIRA tickets" after ?github > repo? or this JIRA button is only accessible via Doc->roadmap menu? > I think it is a good thing to have another link, to all the upcoming JIRAs from a 'feature' or 'modules' page. Users of the current bits may be also interested, to some degree, into what's coming next. While a 'link' from Docs/Roadmaps is good as well. -M > > > > > When we have clear "module" entry or landing pages, it's easy for new > users, to get an understanding what it is all about. Instead of jump around > on the site (which is why we generally do the new site :-)) > > > > > > Does that make sense ? > > > > > > -Matthias > > > > [1] https://aerogear.org/push/ > > [2] https://github.com/aerogear/aerogear.org/pull/468 > > [3] > https://www.dropbox.com/s/zypkqd3nn3wma9w/Screen%20Shot%202015-01-20%20at%2016.38.33.png?dl=0 > > > > > > -- > > 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/20150120/07ec335d/attachment.html From agalante at redhat.com Wed Jan 21 08:50:53 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 21 Jan 2015 08:50:53 -0500 (EST) Subject: [aerogear-dev] Feature based landing page (and new UI) In-Reply-To: References: <16864897-C35F-4869-92EC-80DCB1465BA1@gmail.com> Message-ID: <2029241269.3041516.1421848253051.JavaMail.zimbra@redhat.com> Should I add single "modules" pages for each module? ----- Original Message ----- From: "Matthias Wessendorf" To: "AeroGear Developer Mailing List" Sent: Tuesday, January 20, 2015 7:22:09 PM Subject: Re: [aerogear-dev] Feature based landing page (and new UI) On Tue, Jan 20, 2015 at 9:58 PM, Corinne Krych < corinnekrych at gmail.com > wrote: > On 20 Jan 2015, at 17:01, Matthias Wessendorf < matzew at apache.org > wrote: > > Hi, > > for all of our different push offerings, we have a central landing page ([1]), and soon that page will also list our work on the WebPush spec ([2]) > Since this model is quite handy, having a centralized landing page, I'd propose we do that for other features, like OAuth2 and Sync as well. > > > With the new design, the "feature" is more a module, which is fine. The Screenshot of the modules page ([3]), we list all of our feature, or more modules ;-) > While for PUSH we have more than just one repo (UPS, SimplePush and now WebPush + demos), I think the getting started should go to a 'feature' (or module) landing page. For AeroGearPush that would be [1], or something similar. Basically, on this "module landing page", I'd like to list all relevant GH repos, link to JIRA and perhaps other resources. > > Any thoughts? > > > Now, taking a different example, sync, we would list these repos: > > iOS: > https://github.com/aerogear/aerogear-ios-sync > https://github.com/aerogear/aerogear-ios-sync-client > https://github.com/aerogear/aerogear-ios-sync-demo > > Android: > https://github.com/aerogear/aerogear-android-sync > > JS: > https://github.com/aerogear/aerogear-js (part of the lib) > https://github.com/aerogear/aerogear-js-cookbook (a sync demo, based on node) > > Sync-Server: > https://github.com/aerogear/aerogear-sync-server > > > + linking to the JIRAs tracked for the different Sync milestones (currently the ones with the 'sync-1.0.0.alpha.1' label) > Do you mean adding a fifth button ?List of JIRA tickets" after ?github repo? or this JIRA button is only accessible via Doc->roadmap menu? I think it is a good thing to have another link, to all the upcoming JIRAs from a 'feature' or 'modules' page. Users of the current bits may be also interested, to some degree, into what's coming next. While a 'link' from Docs/Roadmaps is good as well. -M > > When we have clear "module" entry or landing pages, it's easy for new users, to get an understanding what it is all about. Instead of jump around on the site (which is why we generally do the new site :-)) > > > Does that make sense ? > > > -Matthias > > [1] https://aerogear.org/push/ > [2] https://github.com/aerogear/aerogear.org/pull/468 > [3] https://www.dropbox.com/s/zypkqd3nn3wma9w/Screen%20Shot%202015-01-20%20at%2016.38.33.png?dl=0 > > > -- > 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 From matzew at apache.org Wed Jan 21 08:57:41 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 21 Jan 2015 14:57:41 +0100 Subject: [aerogear-dev] Feature based landing page (and new UI) In-Reply-To: <2029241269.3041516.1421848253051.JavaMail.zimbra@redhat.com> References: <16864897-C35F-4869-92EC-80DCB1465BA1@gmail.com> <2029241269.3041516.1421848253051.JavaMail.zimbra@redhat.com> Message-ID: yeah! that would be awesome! On Wednesday, January 21, 2015, Andres Galante wrote: > Should I add single "modules" pages for each module? > > ----- Original Message ----- > From: "Matthias Wessendorf" > > To: "AeroGear Developer Mailing List" > > Sent: Tuesday, January 20, 2015 7:22:09 PM > Subject: Re: [aerogear-dev] Feature based landing page (and new UI) > > > > On Tue, Jan 20, 2015 at 9:58 PM, Corinne Krych < corinnekrych at gmail.com > > wrote: > > > > > On 20 Jan 2015, at 17:01, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > Hi, > > > > for all of our different push offerings, we have a central landing page > ([1]), and soon that page will also list our work on the WebPush spec ([2]) > > Since this model is quite handy, having a centralized landing page, I'd > propose we do that for other features, like OAuth2 and Sync as well. > > > > > > With the new design, the "feature" is more a module, which is fine. The > Screenshot of the modules page ([3]), we list all of our feature, or more > modules ;-) > > While for PUSH we have more than just one repo (UPS, SimplePush and now > WebPush + demos), I think the getting started should go to a 'feature' (or > module) landing page. For AeroGearPush that would be [1], or something > similar. Basically, on this "module landing page", I'd like to list all > relevant GH repos, link to JIRA and perhaps other resources. > > > > Any thoughts? > > > > > > Now, taking a different example, sync, we would list these repos: > > > > iOS: > > https://github.com/aerogear/aerogear-ios-sync > > https://github.com/aerogear/aerogear-ios-sync-client > > https://github.com/aerogear/aerogear-ios-sync-demo > > > > Android: > > https://github.com/aerogear/aerogear-android-sync > > > > JS: > > https://github.com/aerogear/aerogear-js (part of the lib) > > https://github.com/aerogear/aerogear-js-cookbook (a sync demo, based on > node) > > > > Sync-Server: > > https://github.com/aerogear/aerogear-sync-server > > > > > > + linking to the JIRAs tracked for the different Sync milestones > (currently the ones with the 'sync-1.0.0.alpha.1' label) > > > > Do you mean adding a fifth button ?List of JIRA tickets" after ?github > repo? or this JIRA button is only accessible via Doc->roadmap menu? > > I think it is a good thing to have another link, to all the upcoming JIRAs > from a 'feature' or 'modules' page. Users of the current bits may be also > interested, to some degree, into what's coming next. > > While a 'link' from Docs/Roadmaps is good as well. > > -M > > > > > > > > > When we have clear "module" entry or landing pages, it's easy for new > users, to get an understanding what it is all about. Instead of jump around > on the site (which is why we generally do the new site :-)) > > > > > > Does that make sense ? > > > > > > -Matthias > > > > [1] https://aerogear.org/push/ > > [2] https://github.com/aerogear/aerogear.org/pull/468 > > [3] > https://www.dropbox.com/s/zypkqd3nn3wma9w/Screen%20Shot%202015-01-20%20at%2016.38.33.png?dl=0 > > > > > > -- > > 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 -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150121/06ed60e9/attachment.html From edewit at redhat.com Wed Jan 21 10:40:38 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 21 Jan 2015 16:40:38 +0100 Subject: [aerogear-dev] UPS unit tests Message-ID: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> Hi, The database unit tests of the UPS contain a lot of setup code as setting up the database is done within the test method. I?m proposing to remove this ?noise? from the test and put it in a separate file. Another thing that is setting up the dao's, when we use arquillian weld container we can use injection in our tests to further reduce the boilerplate, have a look at an example: https://github.com/edewit/aerogear-unifiedpush-server/blob/4bb63adce319df25e8e77d505f2844cf80ff5644/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/PushApplicationDaoTest.java If you like I could do this for all these tests. Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150121/d0b39cc9/attachment.html From matzew at apache.org Wed Jan 21 10:50:31 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 21 Jan 2015 16:50:31 +0100 Subject: [aerogear-dev] UPS unit tests In-Reply-To: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> References: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> Message-ID: I think the problem that I have with using Arquillian is the time of execution for these integration tests. It boots up a container and stuff and just makes the test execution take a very long time. We spoke about that in the past, and didn't do Aquillian due to that. Not sure how others feel about it, but I'd prefer we dont boot a container inside our tests On Wed, Jan 21, 2015 at 4:40 PM, Erik Jan de Wit wrote: > Hi, > > The database unit tests of the UPS contain a lot of setup code as setting > up the database is done within the test method. I?m proposing to remove > this ?noise? from the test and put it in a separate file. Another thing > that is setting up the dao's, when we use arquillian weld container we can > use injection in our tests to further reduce the boilerplate, have a look > at an example: > > > https://github.com/edewit/aerogear-unifiedpush-server/blob/4bb63adce319df25e8e77d505f2844cf80ff5644/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/PushApplicationDaoTest.java > > If you like I could do this for all these tests. > > 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/20150121/05490554/attachment.html From edewit at redhat.com Wed Jan 21 10:59:25 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 21 Jan 2015 16:59:25 +0100 Subject: [aerogear-dev] UPS unit tests In-Reply-To: References: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> Message-ID: <2CC009AA-6C1A-4F4E-99AB-60A39169A740@redhat.com> This is using weld container, that is not a application container it doesn?t add a lot of execution time. It only enables CDI in tests. On 21 Jan,2015, at 16:50 , Matthias Wessendorf wrote: > I think the problem that I have with using Arquillian is the time of execution for these integration tests. It boots up a container and stuff and just makes the test execution take a very long time. We spoke about that in the past, and didn't do Aquillian due to that. > > Not sure how others feel about it, but I'd prefer we dont boot a container inside our tests > > On Wed, Jan 21, 2015 at 4:40 PM, Erik Jan de Wit wrote: > Hi, > > The database unit tests of the UPS contain a lot of setup code as setting up the database is done within the test method. I?m proposing to remove this ?noise? from the test and put it in a separate file. Another thing that is setting up the dao's, when we use arquillian weld container we can use injection in our tests to further reduce the boilerplate, have a look at an example: > > https://github.com/edewit/aerogear-unifiedpush-server/blob/4bb63adce319df25e8e77d505f2844cf80ff5644/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/PushApplicationDaoTest.java > > If you like I could do this for all these tests. > > 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 > _______________________________________________ > 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/20150121/d945ead0/attachment-0001.html From edewit at redhat.com Wed Jan 21 11:02:09 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 21 Jan 2015 17:02:09 +0100 Subject: [aerogear-dev] UPS unit tests In-Reply-To: <2CC009AA-6C1A-4F4E-99AB-60A39169A740@redhat.com> References: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> <2CC009AA-6C1A-4F4E-99AB-60A39169A740@redhat.com> Message-ID: Original test on my machine executes in 8.5 seconds the ?new? test in 15.115s On 21 Jan,2015, at 16:59 , Erik Jan de Wit wrote: > This is using weld container, that is not a application container it doesn?t add a lot of execution time. It only enables CDI in tests. > > On 21 Jan,2015, at 16:50 , Matthias Wessendorf wrote: > >> I think the problem that I have with using Arquillian is the time of execution for these integration tests. It boots up a container and stuff and just makes the test execution take a very long time. We spoke about that in the past, and didn't do Aquillian due to that. >> >> Not sure how others feel about it, but I'd prefer we dont boot a container inside our tests >> >> On Wed, Jan 21, 2015 at 4:40 PM, Erik Jan de Wit wrote: >> Hi, >> >> The database unit tests of the UPS contain a lot of setup code as setting up the database is done within the test method. I?m proposing to remove this ?noise? from the test and put it in a separate file. Another thing that is setting up the dao's, when we use arquillian weld container we can use injection in our tests to further reduce the boilerplate, have a look at an example: >> >> https://github.com/edewit/aerogear-unifiedpush-server/blob/4bb63adce319df25e8e77d505f2844cf80ff5644/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/PushApplicationDaoTest.java >> >> If you like I could do this for all these tests. >> >> 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 >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150121/532f597f/attachment.html From matzew at apache.org Wed Jan 21 11:05:14 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 21 Jan 2015 17:05:14 +0100 Subject: [aerogear-dev] UPS unit tests In-Reply-To: <2CC009AA-6C1A-4F4E-99AB-60A39169A740@redhat.com> References: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> <2CC009AA-6C1A-4F4E-99AB-60A39169A740@redhat.com> Message-ID: On Wed, Jan 21, 2015 at 4:59 PM, Erik Jan de Wit wrote: > This is using weld container, that is not a application container it > doesn?t add a lot of execution time. It only enables CDI in tests. > Oh - ok - great. On the service layer we do similar, using OpenEJB and OpenWebBeans :). Please send a PR for the model - perhaps we can take on that for services as well :) > > On 21 Jan,2015, at 16:50 , Matthias Wessendorf wrote: > > I think the problem that I have with using Arquillian is the time of > execution for these integration tests. It boots up a container and stuff > and just makes the test execution take a very long time. We spoke about > that in the past, and didn't do Aquillian due to that. > > Not sure how others feel about it, but I'd prefer we dont boot a container > inside our tests > > On Wed, Jan 21, 2015 at 4:40 PM, Erik Jan de Wit > wrote: > >> Hi, >> >> The database unit tests of the UPS contain a lot of setup code as setting >> up the database is done within the test method. I?m proposing to remove >> this ?noise? from the test and put it in a separate file. Another thing >> that is setting up the dao's, when we use arquillian weld container we can >> use injection in our tests to further reduce the boilerplate, have a look >> at an example: >> >> >> https://github.com/edewit/aerogear-unifiedpush-server/blob/4bb63adce319df25e8e77d505f2844cf80ff5644/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/PushApplicationDaoTest.java >> >> If you like I could do this for all these tests. >> >> 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 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20150121/a436a522/attachment.html From matzew at apache.org Wed Jan 21 11:09:40 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 21 Jan 2015 17:09:40 +0100 Subject: [aerogear-dev] Feature based landing page (and new UI) In-Reply-To: References: <16864897-C35F-4869-92EC-80DCB1465BA1@gmail.com> <2029241269.3041516.1421848253051.JavaMail.zimbra@redhat.com> Message-ID: Andres, to give some insights. The modules would list all of our modules, while each of them contains more info on it, like: https://aerogear.org/push/ https://aerogear.org/sync/ (yes, both are a bit different - but with the new UI, I am hoping to get them unified) On Wed, Jan 21, 2015 at 2:57 PM, Matthias Wessendorf wrote: > yeah! that would be awesome! > > > On Wednesday, January 21, 2015, Andres Galante > wrote: > >> Should I add single "modules" pages for each module? >> >> ----- Original Message ----- >> From: "Matthias Wessendorf" >> To: "AeroGear Developer Mailing List" >> Sent: Tuesday, January 20, 2015 7:22:09 PM >> Subject: Re: [aerogear-dev] Feature based landing page (and new UI) >> >> >> >> On Tue, Jan 20, 2015 at 9:58 PM, Corinne Krych < corinnekrych at gmail.com >> > wrote: >> >> >> >> > On 20 Jan 2015, at 17:01, Matthias Wessendorf < matzew at apache.org > >> wrote: >> > >> > Hi, >> > >> > for all of our different push offerings, we have a central landing page >> ([1]), and soon that page will also list our work on the WebPush spec ([2]) >> > Since this model is quite handy, having a centralized landing page, I'd >> propose we do that for other features, like OAuth2 and Sync as well. >> > >> > >> > With the new design, the "feature" is more a module, which is fine. The >> Screenshot of the modules page ([3]), we list all of our feature, or more >> modules ;-) >> > While for PUSH we have more than just one repo (UPS, SimplePush and now >> WebPush + demos), I think the getting started should go to a 'feature' (or >> module) landing page. For AeroGearPush that would be [1], or something >> similar. Basically, on this "module landing page", I'd like to list all >> relevant GH repos, link to JIRA and perhaps other resources. >> > >> > Any thoughts? >> > >> > >> > Now, taking a different example, sync, we would list these repos: >> > >> > iOS: >> > https://github.com/aerogear/aerogear-ios-sync >> > https://github.com/aerogear/aerogear-ios-sync-client >> > https://github.com/aerogear/aerogear-ios-sync-demo >> > >> > Android: >> > https://github.com/aerogear/aerogear-android-sync >> > >> > JS: >> > https://github.com/aerogear/aerogear-js (part of the lib) >> > https://github.com/aerogear/aerogear-js-cookbook (a sync demo, based >> on node) >> > >> > Sync-Server: >> > https://github.com/aerogear/aerogear-sync-server >> > >> > >> > + linking to the JIRAs tracked for the different Sync milestones >> (currently the ones with the 'sync-1.0.0.alpha.1' label) >> > >> >> Do you mean adding a fifth button ?List of JIRA tickets" after ?github >> repo? or this JIRA button is only accessible via Doc->roadmap menu? >> >> I think it is a good thing to have another link, to all the upcoming >> JIRAs from a 'feature' or 'modules' page. Users of the current bits may be >> also interested, to some degree, into what's coming next. >> >> While a 'link' from Docs/Roadmaps is good as well. >> >> -M >> >> >> >> >> >> > >> > When we have clear "module" entry or landing pages, it's easy for new >> users, to get an understanding what it is all about. Instead of jump around >> on the site (which is why we generally do the new site :-)) >> > >> > >> > Does that make sense ? >> > >> > >> > -Matthias >> > >> > [1] https://aerogear.org/push/ >> > [2] https://github.com/aerogear/aerogear.org/pull/468 >> > [3] >> https://www.dropbox.com/s/zypkqd3nn3wma9w/Screen%20Shot%202015-01-20%20at%2016.38.33.png?dl=0 >> > >> > >> > -- >> > 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 > > > > -- > Sent from Gmail Mobile > -- 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/20150121/c36e55fb/attachment-0001.html From supittma at redhat.com Wed Jan 21 11:29:38 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 21 Jan 2015 11:29:38 -0500 Subject: [aerogear-dev] UPS unit tests In-Reply-To: References: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> Message-ID: <54BFD3F2.6040906@redhat.com> On 01/21/2015 10:50 AM, Matthias Wessendorf wrote: > I think the problem that I have with using Arquillian is the time of > execution for these integration tests. It boots up a container and > stuff and just makes the test execution take a very long time. We > spoke about that in the past, and didn't do Aquillian due to that. I'm learning to alike Arquillian. Would it be terribly to put the Arq tests in a profile so they only get run if you pass -Pit or something? Eventually the tests may get to take long enough its important. The android-maven-plugin does that so you aren't always firing up Android VM's. > > Not sure how others feel about it, but I'd prefer we dont boot a > container inside our tests > > On Wed, Jan 21, 2015 at 4:40 PM, Erik Jan de Wit > wrote: > > Hi, > > The database unit tests of the UPS contain a lot of setup code as > setting up the database is done within the test method. I?m > proposing to remove this ?noise? from the test and put it in a > separate file. Another thing that is setting up the dao's, when we > use arquillian weld container we can use injection in our tests to > further reduce the boilerplate, have a look at an example: > > https://github.com/edewit/aerogear-unifiedpush-server/blob/4bb63adce319df25e8e77d505f2844cf80ff5644/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/PushApplicationDaoTest.java > > If you like I could do this for all these tests. > > 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150121/a747d4a0/attachment.html From matzew at apache.org Wed Jan 21 11:32:58 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 21 Jan 2015 17:32:58 +0100 Subject: [aerogear-dev] UPS unit tests In-Reply-To: <54BFD3F2.6040906@redhat.com> References: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> <54BFD3F2.6040906@redhat.com> Message-ID: On Wed, Jan 21, 2015 at 5:29 PM, Summers Pittman wrote: > On 01/21/2015 10:50 AM, Matthias Wessendorf wrote: > > I think the problem that I have with using Arquillian is the time of > execution for these integration tests. It boots up a container and stuff > and just makes the test execution take a very long time. We spoke about > that in the past, and didn't do Aquillian due to that. > > I'm learning to alike Arquillian. Would it be terribly to put the Arq > tests in a profile so they only get run if you pass -Pit or something? > nope - that sounds good, folder could be src/itest/java/.... and only enabled on a -Pit or -Pitests > Eventually the tests may get to take long enough its important. > > The android-maven-plugin does that so you aren't always firing up Android > VM's. > > > Not sure how others feel about it, but I'd prefer we dont boot a > container inside our tests > > On Wed, Jan 21, 2015 at 4:40 PM, Erik Jan de Wit > wrote: > >> Hi, >> >> The database unit tests of the UPS contain a lot of setup code as >> setting up the database is done within the test method. I?m proposing to >> remove this ?noise? from the test and put it in a separate file. Another >> thing that is setting up the dao's, when we use arquillian weld container >> we can use injection in our tests to further reduce the boilerplate, have a >> look at an example: >> >> >> https://github.com/edewit/aerogear-unifiedpush-server/blob/4bb63adce319df25e8e77d505f2844cf80ff5644/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/PushApplicationDaoTest.java >> >> If you like I could do this for all these tests. >> >> 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 > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > 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/20150121/eb0b2a44/attachment.html From agalante at redhat.com Wed Jan 21 17:55:48 2015 From: agalante at redhat.com (Andres Galante) Date: Wed, 21 Jan 2015 17:55:48 -0500 (EST) Subject: [aerogear-dev] UPS console new UI review In-Reply-To: <728634889.3194448.1421880007351.JavaMail.zimbra@redhat.com> Message-ID: <1773858727.3196748.1421880948843.JavaMail.zimbra@redhat.com> Hey! Today Lukas, Sebastien help me review UPS new UI. I also did some usability testing yesterday (over dinner with slightly drunk programmers friends of mine). Here are the results and a bunch of questions for us to discuss: - Code snippets need a ?copy? btn like http://getbootstrap.com/components/ - Descriptions on apps and variants. Can we just remove them? Are they useful? - "Add a variant" form. There is going to be a validation of the form to make sure connections are correctly set up. - Variants page [1]. If the user has lots of variants set up, the list would be huge. I am working on solutions, Lukas and Sebastien had very good ideas. - "Send notification" form has the same problem. Lukas suggested a great solution, to use Multiple select boxes https://select2.github.io/examples.html - Warnings. Where to show them? How to display them? How to make them disappear once the issue is solve? - Delete apps or variants takes a lot of time. there is a JIRA about this. - Add a progress bar to show progress of notifications been sent. - Add links to documentation everywhere. - We talked about adding sorting options on the variants list (by name, or by creation date) but it seems that search would be enough. although there was one tester that asked for sorting options. - It also come to my attention that the name ?Variant? is too general. Every non UPS developer I've shown the console asked me ?what are variants? and when I explain, they asked me ?Why don?t you find a better name that represent ?group of devices?? Lukas mention that a change of wording at this point would be very hard since we have the word ?Variant? all over our docs. But maybe for 2.0 we can think of a better way to help the user understand what a Variant is. Here is the prototype, click around and send feedback :) http://andresgalante.com/ups-console/login.html [1]http://andresgalante.com/ups-console/app-detail-variants.html From matzew at apache.org Thu Jan 22 04:54:23 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 22 Jan 2015 10:54:23 +0100 Subject: [aerogear-dev] UPS console new UI review In-Reply-To: <1773858727.3196748.1421880948843.JavaMail.zimbra@redhat.com> References: <728634889.3194448.1421880007351.JavaMail.zimbra@redhat.com> <1773858727.3196748.1421880948843.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Jan 21, 2015 at 11:55 PM, Andres Galante wrote: > Hey! > > Today Lukas, Sebastien help me review UPS new UI. > I also did some usability testing yesterday (over dinner with slightly > drunk programmers friends of mine). > > Here are the results and a bunch of questions for us to discuss: > > - Code snippets need a ?copy? btn like http://getbootstrap.com/components/ +1 > - Descriptions on apps and variants. Can we just remove them? Are they > useful? > yeah, I think we can remove them. Here is a JIRA for it: https://issues.jboss.org/browse/AGPUSH-1240 > > - "Add a variant" form. There is going to be a validation of the form to > make sure connections are correctly set up. > +1 created https://issues.jboss.org/browse/AGPUSH-1241 > > - Variants page [1]. If the user has lots of variants set up, the list > would be huge. I am working on solutions, Lukas and Sebastien had very good > ideas. > > - "Send notification" form has the same problem. Lukas suggested a great > solution, to use Multiple select boxes > https://select2.github.io/examples.html any details? > > > - Warnings. Where to show them? How to display them? I like how they are presented in the current UI > How to make them disappear once the issue is solve? > Not sure.... we keep them, and after 30 days there is a job to delete the warnings. I'd keep them, for tracking that there was a problem a few days ago. > > - Delete apps or variants takes a lot of time. there is a JIRA about this. > which one ? > > - Add a progress bar to show progress of notifications been sent. > Isn't that miss leading? We can not guarantee that the message are delivered to the phone. We just give them to Google/Apple/etc. If they move them to /dev/null - well :-) > - Add links to documentation everywhere. > yeah - do we have a JIRA for that ? > > - We talked about adding sorting options on the variants list (by name, or > by creation date) but it seems that search would be enough. although there > was one tester that asked for sorting options. > +1 for search only. Did you guys create a JIRA for that ? > > - It also come to my attention that the name ?Variant? is too general. > Every non UPS developer I've shown the console asked me ?what are variants? > and when I explain, they asked me ?Why don?t you find a better name that > represent ?group of devices?? > It's not just group of devices - it's also per platform. Imagine if there are paid and free versions of an app. That *can* be managed as two variants, on one app. I am open to improvements here > > Lukas mention that a change of wording at this point would be very hard > since we have the word ?Variant? all over our docs. But maybe for 2.0 we > can think of a better way to help the user understand what a Variant is. > +1 - perhaps we can improve the text on the UI ? > > Here is the prototype, click around and send feedback :) > http://andresgalante.com/ups-console/login.html I still think the *skip* is too small. Also, on the wizard, if it should always go to Send (but we had that on a different thread) > > > > [1]http://andresgalante.com/ups-console/app-detail-variants.html > > > > > > > > > > _______________________________________________ > 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/20150122/8be59d59/attachment-0001.html From matzew at apache.org Thu Jan 22 06:00:04 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 22 Jan 2015 12:00:04 +0100 Subject: [aerogear-dev] Google Summer of Code 2015 Message-ID: Hi, this year JBoss is again participating on GSoC ([1]). yay! For ideas from the AeroGear project, a few have been already discussed here. Erik has this idea: http://lists.jboss.org/pipermail/aerogear-dev/2015-January/010495.html Sebi and Dan did chat about some work for the WebPush Server, on IRC: * write a lightweight webpush java client for iot (I think the current client may run on several different devices) * add WebPush support to UPS For iOS Corinne mentioned the following: * touchID * WatchKit SDK for AeroGear We still have a time to think about more ideas. Greetings, Matthias [1] https://developer.jboss.org/wiki/GSOC15Ideas -- 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/20150122/32cc31c2/attachment.html From cvasilak at gmail.com Thu Jan 22 08:01:19 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 22 Jan 2015 15:01:19 +0200 Subject: [aerogear-dev] Parallel support for a Cocoapods Swift/Obj-c library Message-ID: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> Hi team, a little heads up on an issue that I?ve been looking the last days, on how to proper support both an Obj-C and a Swift library (in-parallel) on Cocoapods. There was a discussion on the cocoapods issues tracker[1] basically around two ideas: a) being a separate project, with a new name plus utilising Swift specific language propers. b) having one project, utilising cocoapods subspec mechanism to include specific files per spec requested. In a nutshell users will employ in their Podfile something of a form: ? pod ?MyFooBarLibrary/Objc? (objective-c) or pod ? MyFooBarLibrary/Swift? (Swift) ? Solution (b) was intrigued and went on to discover more, since I haven?t used before the subspec mechanism and was a good opportunity to learn. The issue mentioned two projects, QueryKit[2] and ReactiveCocoa[3] (their Swift branch) that utilise this mechanism, so I dive in trying to see how it works. My realisations: a) both projects are designed with ?Swift first? approach, employing _some_ 'Objective-C code? to ease the interaction in a mixed project e.g Objective-C code calling the ?Swift? library, see [4] where the author describes more details on this. b) since ?Swift first?, both produce frameworks where they can be integrated either in objective-c or swift language projects, no ?static-library? targets. c) both are designed for iOS >= 8.0 To make it short and from my understanding, the projects are _not_ designed around the idea of: take either the Objective-C or the Swift port in you project, but instead employ an Objective-C subspec to ?ease? the interaction in a mixed environment, aka Objective-C code calling the Swift library. Regardless and to better understand, I did some testing with our push-sdk: a) having a single Swift Project employing both the objective-c code and Swift code b) having a .workspace with a) Obj-c xcodeproj, b) Swift xcodeproj. In both cases, this mixed approaches, at the end caused issues and wasn?t able to generate a proper solution. Issues around a) cocoapods 'pod install? steps, b) tests on the library are done with two different dependencies c) various other integration issues? It?s my sense, the most clean way is to go with separate libraries, that is solution (a) described above (a solution proposed also from @orta [5]) This has the added benefit of cleaner 'logistics? that is: commit history, releases, static/framework library generations etc etc. But there is one issue if we go with separate approach: _cocoapods naming_, that is how to properly separate between the two. Currently searching for AeroGear-Push in cocoapods.org site we get the following: In my cocoapods PR [6] I went with the approach to name the ?Swift? equivalent library as 'AeroGear-Push-Swift?, so the same searching above will reveal: ? AeroGear-Push AeroGear-Push-Swift ? Some of you have already noticed, that the ?hyphen? character as a podspec name doesn?t work well with a Swift Project, cause the podspec name is used as the name of the final #import statement the user does. That is the following import statement doesn?t work: ? import AeroGear-Push-Swift ? Solving this, there are two approaches: a) rename both library podspecs : Objective-C to -> AeroGearPush and Swift to -> AeroGearPushSwift b) continue the same naming, but use the new ?module_name? podspec directive in the Swift project(added in cocoapods [6]) to specify the final module name the user will use on the import. That is the approach I have taken in my PR[6] If we go with (b) the entries will look like this: ?? Obj-c: (no changes needed) Podfile: pod 'AeroGear-Push? Class: #import Swift: Podfile: pod 'AeroGear-Push-Swift? Class: import ?AeroGearPush? (notice _no_ ?Swift? postfix is needed cause of the ?module_name? override) ?? I am fine with both albeit more towards (b) mostly not to break existing ?pod installs? the users may use and since support with the ?module_name? directive is provided from cocoapods. Current PR[6] goes with this approach. Let me know your comments and suggestions Thanks Christos [1] https://github.com/CocoaPods/CocoaPods/issues/3016 [2] https://github.com/QueryKit/QueryKit [3] https://github.com/ReactiveCocoa/ReactiveCocoa/tree/swift-development [4] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69092100 [5] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69073109 [6] https://github.com/aerogear/aerogear-ios-push/pull/41 [7] http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150122/a912e54c/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot 2015-01-22 13.56.36.png Type: image/png Size: 61997 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150122/a912e54c/attachment-0001.png From daniel.bevenius at gmail.com Thu Jan 22 08:18:39 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Thu, 22 Jan 2015 14:18:39 +0100 Subject: [aerogear-dev] Parallel support for a Cocoapods Swift/Obj-c library In-Reply-To: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> References: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> Message-ID: +1 on b On 22 January 2015 at 14:01, Christos Vasilakis wrote: > Hi team, > > a little heads up on an issue that I?ve been looking the last days, on how > to proper support both an Obj-C and a Swift library (in-parallel) on > Cocoapods. There was a discussion on the cocoapods issues tracker[1] > basically around two ideas: > > a) being a separate project, with a new name plus utilising Swift specific > language propers. > b) having one project, utilising cocoapods subspec mechanism to include > specific files per spec requested. In a nutshell users will employ in their > Podfile something of a form: > > ? > pod ?MyFooBarLibrary/Objc? (objective-c) > or > pod ? MyFooBarLibrary/Swift? (Swift) > ? > > Solution (b) was intrigued and went on to discover more, since I haven?t > used before the subspec mechanism and was a good opportunity to learn. The > issue mentioned two projects, QueryKit[2] and ReactiveCocoa[3] (their Swift > branch) that utilise this mechanism, so I dive in trying to see how it > works. > > My realisations: > a) both projects are designed with ?Swift first? approach, employing > _some_ 'Objective-C code? to ease the interaction in a mixed project e.g > Objective-C code calling the ?Swift? library, see [4] where the author > describes more details on this. > b) since ?Swift first?, both produce frameworks where they can be > integrated either in objective-c or swift language projects, no > ?static-library? targets. > c) both are designed for iOS >= 8.0 > > To make it short and from my understanding, the projects are _not_ > designed around the idea of: take either the Objective-C or the Swift port > in you project, but instead employ an Objective-C subspec to ?ease? the > interaction in a mixed environment, aka Objective-C code calling the Swift > library. > > Regardless and to better understand, I did some testing with our push-sdk: > > a) having a single Swift Project employing both the objective-c code and > Swift code > b) having a .workspace with a) Obj-c xcodeproj, b) Swift xcodeproj. > > In both cases, this mixed approaches, at the end caused issues and wasn?t > able to generate a proper solution. Issues around a) cocoapods 'pod > install? steps, b) tests on the library are done with two different > dependencies c) various other integration issues? > > It?s my sense, the most clean way is to go with separate libraries, that > is solution (a) described above (a solution proposed also from @orta [5]) > This has the added benefit of cleaner 'logistics? that is: commit history, > releases, static/framework library generations etc etc. > > But there is one issue if we go with separate approach: _cocoapods > naming_, that is how to properly separate between the two. > > Currently searching for AeroGear-Push in cocoapods.org site we get the > following: > > > > In my cocoapods PR [6] I went with the approach to name the ?Swift? > equivalent library as 'AeroGear-Push-Swift?, so the same searching above > will reveal: > > ? > AeroGear-Push > AeroGear-Push-Swift > ? > > Some of you have already noticed, that the ?hyphen? character as a podspec > name doesn?t work well with a Swift Project, cause the podspec name is used > as the name of the final #import statement the user does. That is the > following import statement doesn?t work: > > ? > import AeroGear-Push-Swift > ? > > Solving this, there are two approaches: > > a) rename both library podspecs : Objective-C to -> AeroGearPush and Swift > to -> AeroGearPushSwift > b) continue the same naming, but use the new ?module_name? podspec > directive in the Swift project(added in cocoapods [6]) to specify the final > module name the user will use on the import. That is the approach I have > taken in my PR[6] > > If we go with (b) the entries will look like this: > > ?? > Obj-c: (no changes needed) > > Podfile: pod 'AeroGear-Push? > > Class: #import > > > Swift: > > Podfile: pod 'AeroGear-Push-Swift? > > Class: import ?AeroGearPush? (notice _no_ ?Swift? postfix is needed > cause of the ?module_name? override) > > ?? > > I am fine with both albeit more towards (b) mostly not to break existing > ?pod installs? the users may use and since support with the ?module_name? > directive is provided from cocoapods. Current PR[6] goes with this > approach. > > Let me know your comments and suggestions > > Thanks > Christos > > [1] https://github.com/CocoaPods/CocoaPods/issues/3016 > [2] https://github.com/QueryKit/QueryKit > [3] https://github.com/ReactiveCocoa/ReactiveCocoa/tree/swift-development > [4] > https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69092100 > [5] > https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69073109 > [6] https://github.com/aerogear/aerogear-ios-push/pull/41 > [7] http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/ > > _______________________________________________ > 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/20150122/0e691bb5/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot 2015-01-22 13.56.36.png Type: image/png Size: 61997 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150122/0e691bb5/attachment-0001.png From lholmqui at redhat.com Thu Jan 22 08:58:25 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Thu, 22 Jan 2015 08:58:25 -0500 Subject: [aerogear-dev] Parallel support for a Cocoapods Swift/Obj-c library In-Reply-To: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> References: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> Message-ID: good info, i?d vote for the b approach so not to interfere with existing stuff. If someone wasn?t using cocoa pods, how would this affect them, wrt to the ?import? since it wouldn?t be using he module_name pod spec directive? > On Jan 22, 2015, at 8:01 AM, Christos Vasilakis wrote: > > Hi team, > > a little heads up on an issue that I?ve been looking the last days, on how to proper support both an Obj-C and a Swift library (in-parallel) on Cocoapods. There was a discussion on the cocoapods issues tracker[1] basically around two ideas: > > a) being a separate project, with a new name plus utilising Swift specific language propers. > b) having one project, utilising cocoapods subspec mechanism to include specific files per spec requested. In a nutshell users will employ in their Podfile something of a form: > > ? > pod ?MyFooBarLibrary/Objc? (objective-c) > or > pod ? MyFooBarLibrary/Swift? (Swift) > ? > > Solution (b) was intrigued and went on to discover more, since I haven?t used before the subspec mechanism and was a good opportunity to learn. The issue mentioned two projects, QueryKit[2] and ReactiveCocoa[3] (their Swift branch) that utilise this mechanism, so I dive in trying to see how it works. > > My realisations: > a) both projects are designed with ?Swift first? approach, employing _some_ 'Objective-C code? to ease the interaction in a mixed project e.g Objective-C code calling the ?Swift? library, see [4] where the author describes more details on this. > b) since ?Swift first?, both produce frameworks where they can be integrated either in objective-c or swift language projects, no ?static-library? targets. > c) both are designed for iOS >= 8.0 > > To make it short and from my understanding, the projects are _not_ designed around the idea of: take either the Objective-C or the Swift port in you project, but instead employ an Objective-C subspec to ?ease? the interaction in a mixed environment, aka Objective-C code calling the Swift library. > > Regardless and to better understand, I did some testing with our push-sdk: > > a) having a single Swift Project employing both the objective-c code and Swift code > b) having a .workspace with a) Obj-c xcodeproj, b) Swift xcodeproj. > > In both cases, this mixed approaches, at the end caused issues and wasn?t able to generate a proper solution. Issues around a) cocoapods 'pod install? steps, b) tests on the library are done with two different dependencies c) various other integration issues? > > It?s my sense, the most clean way is to go with separate libraries, that is solution (a) described above (a solution proposed also from @orta [5]) This has the added benefit of cleaner 'logistics? that is: commit history, releases, static/framework library generations etc etc. > > But there is one issue if we go with separate approach: _cocoapods naming_, that is how to properly separate between the two. > > Currently searching for AeroGear-Push in cocoapods.org site we get the following: > > > > > In my cocoapods PR [6] I went with the approach to name the ?Swift? equivalent library as 'AeroGear-Push-Swift?, so the same searching above will reveal: > > ? > AeroGear-Push > AeroGear-Push-Swift > ? > > Some of you have already noticed, that the ?hyphen? character as a podspec name doesn?t work well with a Swift Project, cause the podspec name is used as the name of the final #import statement the user does. That is the following import statement doesn?t work: > > ? > import AeroGear-Push-Swift > ? > > Solving this, there are two approaches: > > a) rename both library podspecs : Objective-C to -> AeroGearPush and Swift to -> AeroGearPushSwift > b) continue the same naming, but use the new ?module_name? podspec directive in the Swift project(added in cocoapods [6]) to specify the final module name the user will use on the import. That is the approach I have taken in my PR[6] > > If we go with (b) the entries will look like this: > > ?? > Obj-c: (no changes needed) > > Podfile: pod 'AeroGear-Push? > > Class: #import > > > Swift: > > Podfile: pod 'AeroGear-Push-Swift? > > Class: import ?AeroGearPush? (notice _no_ ?Swift? postfix is needed cause of the ?module_name? override) > > ?? > > I am fine with both albeit more towards (b) mostly not to break existing ?pod installs? the users may use and since support with the ?module_name? directive is provided from cocoapods. Current PR[6] goes with this approach. > > Let me know your comments and suggestions > > Thanks > Christos > > [1] https://github.com/CocoaPods/CocoaPods/issues/3016 > [2] https://github.com/QueryKit/QueryKit > [3] https://github.com/ReactiveCocoa/ReactiveCocoa/tree/swift-development > [4] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69092100 > [5] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69073109 > [6] https://github.com/aerogear/aerogear-ios-push/pull/41 > [7] http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/ _______________________________________________ > 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/20150122/4db4d892/attachment.html From matzew at apache.org Thu Jan 22 09:21:08 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 22 Jan 2015 15:21:08 +0100 Subject: [aerogear-dev] Parallel support for a Cocoapods Swift/Obj-c library In-Reply-To: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> References: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> Message-ID: Wow, thanks for all the details around here On Thu, Jan 22, 2015 at 2:01 PM, Christos Vasilakis wrote: > Hi team, > > a little heads up on an issue that I?ve been looking the last days, on how > to proper support both an Obj-C and a Swift library (in-parallel) on > Cocoapods. There was a discussion on the cocoapods issues tracker[1] > basically around two ideas: > > a) being a separate project, with a new name plus utilising Swift specific > language propers. > b) having one project, utilising cocoapods subspec mechanism to include > specific files per spec requested. In a nutshell users will employ in their > Podfile something of a form: > > ? > pod ?MyFooBarLibrary/Objc? (objective-c) > or > pod ? MyFooBarLibrary/Swift? (Swift) > ? > > Solution (b) was intrigued and went on to discover more, since I haven?t > used before the subspec mechanism and was a good opportunity to learn. The > issue mentioned two projects, QueryKit[2] and ReactiveCocoa[3] (their Swift > branch) that utilise this mechanism, so I dive in trying to see how it > works. > > My realisations: > a) both projects are designed with ?Swift first? approach, employing > _some_ 'Objective-C code? to ease the interaction in a mixed project e.g > Objective-C code calling the ?Swift? library, see [4] where the author > describes more details on this. > b) since ?Swift first?, both produce frameworks where they can be > integrated either in objective-c or swift language projects, no > ?static-library? targets. > c) both are designed for iOS >= 8.0 > ouch - what do they do for iOS7 ? > > To make it short and from my understanding, the projects are _not_ > designed around the idea of: take either the Objective-C or the Swift port > in you project, but instead employ an Objective-C subspec to ?ease? the > interaction in a mixed environment, aka Objective-C code calling the Swift > library. > > Regardless and to better understand, I did some testing with our push-sdk: > > a) having a single Swift Project employing both the objective-c code and > Swift code > b) having a .workspace with a) Obj-c xcodeproj, b) Swift xcodeproj. > > In both cases, this mixed approaches, at the end caused issues and wasn?t > able to generate a proper solution. Issues around a) cocoapods 'pod > install? steps, b) tests on the library are done with two different > dependencies c) various other integration issues? > > It?s my sense, the most clean way is to go with separate libraries, that > is solution (a) described above (a solution proposed also from @orta [5]) > This has the added benefit of cleaner 'logistics? that is: commit history, > releases, static/framework library generations etc etc. > +1000 :-) When reading, I was actually wondering about these logistics :) > > But there is one issue if we go with separate approach: _cocoapods > naming_, that is how to properly separate between the two. > > Currently searching for AeroGear-Push in cocoapods.org site we get the > following: > > > > In my cocoapods PR [6] I went with the approach to name the ?Swift? > equivalent library as 'AeroGear-Push-Swift?, so the same searching above > will reveal: > > ? > AeroGear-Push > AeroGear-Push-Swift > ? > > Some of you have already noticed, that the ?hyphen? character as a podspec > name doesn?t work well with a Swift Project, cause the podspec name is used > as the name of the final #import statement the user does. That is the > following import statement doesn?t work: > > ? > import AeroGear-Push-Swift > ? > > Solving this, there are two approaches: > > a) rename both library podspecs : Objective-C to -> AeroGearPush and Swift > to -> AeroGearPushSwift > b) continue the same naming, but use the new ?module_name? podspec > directive in the Swift project(added in cocoapods [6]) to specify the final > module name the user will use on the import. That is the approach I have > taken in my PR[6] > +1 on b), using the module_name - nice addon to CocoaPods > > If we go with (b) the entries will look like this: > > ?? > Obj-c: (no changes needed) > > Podfile: pod 'AeroGear-Push? > > Class: #import > > > Swift: > > Podfile: pod 'AeroGear-Push-Swift? > > Class: import ?AeroGearPush? (notice _no_ ?Swift? postfix is needed > cause of the ?module_name? override) > > ?? > > I am fine with both albeit more towards (b) mostly not to break existing > ?pod installs? the users may use and since support with the ?module_name? > directive is provided from cocoapods. Current PR[6] goes with this > approach. > > Let me know your comments and suggestions > > Thanks > Christos > > [1] https://github.com/CocoaPods/CocoaPods/issues/3016 > [2] https://github.com/QueryKit/QueryKit > [3] https://github.com/ReactiveCocoa/ReactiveCocoa/tree/swift-development > [4] > https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69092100 > [5] > https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69073109 > [6] https://github.com/aerogear/aerogear-ios-push/pull/41 > [7] http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/ > > _______________________________________________ > 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/20150122/89b6bf67/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot 2015-01-22 13.56.36.png Type: image/png Size: 61997 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150122/89b6bf67/attachment-0001.png From cvasilak at gmail.com Thu Jan 22 09:33:55 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 22 Jan 2015 16:33:55 +0200 Subject: [aerogear-dev] Parallel support for a Cocoapods Swift/Obj-c library In-Reply-To: References: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> Message-ID: <19DE7EE9-661C-4FFF-AAAB-955998B31D19@gmail.com> > On Jan 22, 2015, at 3:58 PM, Lucas Holmquist wrote: > > good info, > > > i?d vote for the b approach so not to interfere with existing stuff. > > > If someone wasn?t using cocoa pods, how would this affect them, wrt to the ?import? since it wouldn?t be using he module_name pod spec directive? oh yeap without cocoapods the user will continue to use the same directive, no affects there, that is: -- import AeroGearPush ? > >> On Jan 22, 2015, at 8:01 AM, Christos Vasilakis > wrote: >> >> Hi team, >> >> a little heads up on an issue that I?ve been looking the last days, on how to proper support both an Obj-C and a Swift library (in-parallel) on Cocoapods. There was a discussion on the cocoapods issues tracker[1] basically around two ideas: >> >> a) being a separate project, with a new name plus utilising Swift specific language propers. >> b) having one project, utilising cocoapods subspec mechanism to include specific files per spec requested. In a nutshell users will employ in their Podfile something of a form: >> >> ? >> pod ?MyFooBarLibrary/Objc? (objective-c) >> or >> pod ? MyFooBarLibrary/Swift? (Swift) >> ? >> >> Solution (b) was intrigued and went on to discover more, since I haven?t used before the subspec mechanism and was a good opportunity to learn. The issue mentioned two projects, QueryKit[2] and ReactiveCocoa[3] (their Swift branch) that utilise this mechanism, so I dive in trying to see how it works. >> >> My realisations: >> a) both projects are designed with ?Swift first? approach, employing _some_ 'Objective-C code? to ease the interaction in a mixed project e.g Objective-C code calling the ?Swift? library, see [4] where the author describes more details on this. >> b) since ?Swift first?, both produce frameworks where they can be integrated either in objective-c or swift language projects, no ?static-library? targets. >> c) both are designed for iOS >= 8.0 >> >> To make it short and from my understanding, the projects are _not_ designed around the idea of: take either the Objective-C or the Swift port in you project, but instead employ an Objective-C subspec to ?ease? the interaction in a mixed environment, aka Objective-C code calling the Swift library. >> >> Regardless and to better understand, I did some testing with our push-sdk: >> >> a) having a single Swift Project employing both the objective-c code and Swift code >> b) having a .workspace with a) Obj-c xcodeproj, b) Swift xcodeproj. >> >> In both cases, this mixed approaches, at the end caused issues and wasn?t able to generate a proper solution. Issues around a) cocoapods 'pod install? steps, b) tests on the library are done with two different dependencies c) various other integration issues? >> >> It?s my sense, the most clean way is to go with separate libraries, that is solution (a) described above (a solution proposed also from @orta [5]) This has the added benefit of cleaner 'logistics? that is: commit history, releases, static/framework library generations etc etc. >> >> But there is one issue if we go with separate approach: _cocoapods naming_, that is how to properly separate between the two. >> >> Currently searching for AeroGear-Push in cocoapods.org site we get the following: >> >> >> >> >> In my cocoapods PR [6] I went with the approach to name the ?Swift? equivalent library as 'AeroGear-Push-Swift?, so the same searching above will reveal: >> >> ? >> AeroGear-Push >> AeroGear-Push-Swift >> ? >> >> Some of you have already noticed, that the ?hyphen? character as a podspec name doesn?t work well with a Swift Project, cause the podspec name is used as the name of the final #import statement the user does. That is the following import statement doesn?t work: >> >> ? >> import AeroGear-Push-Swift >> ? >> >> Solving this, there are two approaches: >> >> a) rename both library podspecs : Objective-C to -> AeroGearPush and Swift to -> AeroGearPushSwift >> b) continue the same naming, but use the new ?module_name? podspec directive in the Swift project(added in cocoapods [6]) to specify the final module name the user will use on the import. That is the approach I have taken in my PR[6] >> >> If we go with (b) the entries will look like this: >> >> ?? >> Obj-c: (no changes needed) >> >> Podfile: pod 'AeroGear-Push? >> >> Class: #import >> >> >> Swift: >> >> Podfile: pod 'AeroGear-Push-Swift? >> >> Class: import ?AeroGearPush? (notice _no_ ?Swift? postfix is needed cause of the ?module_name? override) >> >> ?? >> >> I am fine with both albeit more towards (b) mostly not to break existing ?pod installs? the users may use and since support with the ?module_name? directive is provided from cocoapods. Current PR[6] goes with this approach. >> >> Let me know your comments and suggestions >> >> Thanks >> Christos >> >> [1] https://github.com/CocoaPods/CocoaPods/issues/3016 >> [2] https://github.com/QueryKit/QueryKit >> [3] https://github.com/ReactiveCocoa/ReactiveCocoa/tree/swift-development >> [4] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69092100 >> [5] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69073109 >> [6] https://github.com/aerogear/aerogear-ios-push/pull/41 >> [7] http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/ _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150122/f8287565/attachment.html From cvasilak at gmail.com Thu Jan 22 09:40:59 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 22 Jan 2015 16:40:59 +0200 Subject: [aerogear-dev] Parallel support for a Cocoapods Swift/Obj-c library In-Reply-To: References: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> Message-ID: <16F9E2F7-6C1C-4918-9FBF-0730B0441A42@gmail.com> > On Jan 22, 2015, at 4:21 PM, Matthias Wessendorf wrote: > > Wow, thanks for all the details around here > > On Thu, Jan 22, 2015 at 2:01 PM, Christos Vasilakis > wrote: > Hi team, > > a little heads up on an issue that I?ve been looking the last days, on how to proper support both an Obj-C and a Swift library (in-parallel) on Cocoapods. There was a discussion on the cocoapods issues tracker[1] basically around two ideas: > > a) being a separate project, with a new name plus utilising Swift specific language propers. > b) having one project, utilising cocoapods subspec mechanism to include specific files per spec requested. In a nutshell users will employ in their Podfile something of a form: > > ? > pod ?MyFooBarLibrary/Objc? (objective-c) > or > pod ? MyFooBarLibrary/Swift? (Swift) > ? > > Solution (b) was intrigued and went on to discover more, since I haven?t used before the subspec mechanism and was a good opportunity to learn. The issue mentioned two projects, QueryKit[2] and ReactiveCocoa[3] (their Swift branch) that utilise this mechanism, so I dive in trying to see how it works. > > My realisations: > a) both projects are designed with ?Swift first? approach, employing _some_ 'Objective-C code? to ease the interaction in a mixed project e.g Objective-C code calling the ?Swift? library, see [4] where the author describes more details on this. > b) since ?Swift first?, both produce frameworks where they can be integrated either in objective-c or swift language projects, no ?static-library? targets. > c) both are designed for iOS >= 8.0 > > ouch - what do they do for iOS7 ? no support for iOS 7, QueryKit and ReactiveCocoa(swift branch) are fairly new and designed to work on iOS 8 and later Note: ReactiveCocoa has a ?master' branch with support of iOS 7/8 but ?objective-c? only. > > > > To make it short and from my understanding, the projects are _not_ designed around the idea of: take either the Objective-C or the Swift port in you project, but instead employ an Objective-C subspec to ?ease? the interaction in a mixed environment, aka Objective-C code calling the Swift library. > > Regardless and to better understand, I did some testing with our push-sdk: > > a) having a single Swift Project employing both the objective-c code and Swift code > b) having a .workspace with a) Obj-c xcodeproj, b) Swift xcodeproj. > > In both cases, this mixed approaches, at the end caused issues and wasn?t able to generate a proper solution. Issues around a) cocoapods 'pod install? steps, b) tests on the library are done with two different dependencies c) various other integration issues? > > It?s my sense, the most clean way is to go with separate libraries, that is solution (a) described above (a solution proposed also from @orta [5]) This has the added benefit of cleaner 'logistics? that is: commit history, releases, static/framework library generations etc etc. > > +1000 :-) When reading, I was actually wondering about these logistics :) > > > But there is one issue if we go with separate approach: _cocoapods naming_, that is how to properly separate between the two. > > Currently searching for AeroGear-Push in cocoapods.org site we get the following: > > > > > In my cocoapods PR [6] I went with the approach to name the ?Swift? equivalent library as 'AeroGear-Push-Swift?, so the same searching above will reveal: > > ? > AeroGear-Push > AeroGear-Push-Swift > ? > > Some of you have already noticed, that the ?hyphen? character as a podspec name doesn?t work well with a Swift Project, cause the podspec name is used as the name of the final #import statement the user does. That is the following import statement doesn?t work: > > ? > import AeroGear-Push-Swift > ? > > Solving this, there are two approaches: > > a) rename both library podspecs : Objective-C to -> AeroGearPush and Swift to -> AeroGearPushSwift > b) continue the same naming, but use the new ?module_name? podspec directive in the Swift project(added in cocoapods [6]) to specify the final module name the user will use on the import. That is the approach I have taken in my PR[6] > > +1 on b), using the module_name - nice addon to CocoaPods > > > > If we go with (b) the entries will look like this: > > ?? > Obj-c: (no changes needed) > > Podfile: pod 'AeroGear-Push? > > Class: #import > > > Swift: > > Podfile: pod 'AeroGear-Push-Swift? > > Class: import ?AeroGearPush? (notice _no_ ?Swift? postfix is needed cause of the ?module_name? override) > > ?? > > I am fine with both albeit more towards (b) mostly not to break existing ?pod installs? the users may use and since support with the ?module_name? directive is provided from cocoapods. Current PR[6] goes with this approach. > > Let me know your comments and suggestions > > Thanks > Christos > > [1] https://github.com/CocoaPods/CocoaPods/issues/3016 > [2] https://github.com/QueryKit/QueryKit > [3] https://github.com/ReactiveCocoa/ReactiveCocoa/tree/swift-development > [4] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69092100 > [5] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69073109 > [6] https://github.com/aerogear/aerogear-ios-push/pull/41 > [7] http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/ > _______________________________________________ > 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/20150122/97f66b4f/attachment-0001.html From lukas.fryc at gmail.com Thu Jan 22 11:14:55 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Thu, 22 Jan 2015 17:14:55 +0100 Subject: [aerogear-dev] UPS console new UI review In-Reply-To: References: <728634889.3194448.1421880007351.JavaMail.zimbra@redhat.com> <1773858727.3196748.1421880948843.JavaMail.zimbra@redhat.com> Message-ID: On Thu, Jan 22, 2015 at 10:54 AM, Matthias Wessendorf wrote: > > > On Wed, Jan 21, 2015 at 11:55 PM, Andres Galante > wrote: > >> Hey! >> >> Today Lukas, Sebastien help me review UPS new UI. >> I also did some usability testing yesterday (over dinner with slightly >> drunk programmers friends of mine). >> >> Here are the results and a bunch of questions for us to discuss: >> >> - Code snippets need a ?copy? btn like >> http://getbootstrap.com/components/ > > > +1 > > >> - Descriptions on apps and variants. Can we just remove them? Are they >> useful? >> > > yeah, I think we can remove them. Here is a JIRA for it: > https://issues.jboss.org/browse/AGPUSH-1240 > > >> >> - "Add a variant" form. There is going to be a validation of the form to >> make sure connections are correctly set up. >> > > +1 created https://issues.jboss.org/browse/AGPUSH-1241 > > >> >> - Variants page [1]. If the user has lots of variants set up, the list >> would be huge. I am working on solutions, Lukas and Sebastien had very good >> ideas. >> >> - "Send notification" form has the same problem. Lukas suggested a great >> solution, to use Multiple select boxes >> https://select2.github.io/examples.html > > > any details? > Sebi commented on "Send notification" screen that checkboxes are not ideal way to select multiple variants when you have huge number of variants, say 20. In other to save screen space, we would need to make it scrollable OR put into several columns OR as I suggested, we may use a search selection box with groups per platform and auto-completion, such as "Multiple select boxes" sample on https://select2.github.io/examples.html > > >> >> >> - Warnings. Where to show them? How to display them? > > > I like how they are presented in the current UI > Andres presented us that warnings are shown on the variant screen: http://andresgalante.com/ups-console/app-detail-variants.html I just wondered when the warning disappears (what's a best approach from UX perspective). > > >> How to make them disappear once the issue is solve? >> > > Not sure.... we keep them, and after 30 days there is a job to delete the > warnings. I'd keep them, for tracking that there was a problem a few days > ago. > > >> >> - Delete apps or variants takes a lot of time. there is a JIRA about this. >> > > which one ? > > >> >> - Add a progress bar to show progress of notifications been sent. >> > > Isn't that miss leading? We can not guarantee that the message are > delivered to the phone. > We just give them to Google/Apple/etc. If they move them to /dev/null - > well :-) > I don't remember discussing this, I was talking about design of "progress indicators" in general - if the app is taking any action, the UI should not allow the user to do anything else unless the request is fully processed (which is not true in the 1.0.x) - and ideally show some action indicator - e.g. a spinner. :-) > > >> - Add links to documentation everywhere. >> > > yeah - do we have a JIRA for that ? > > >> >> - We talked about adding sorting options on the variants list (by name, >> or by creation date) but it seems that search would be enough. although >> there was one tester that asked for sorting options. >> > > +1 for search only. Did you guys create a JIRA for that ? > > >> >> - It also come to my attention that the name ?Variant? is too general. >> Every non UPS developer I've shown the console asked me ?what are variants? >> and when I explain, they asked me ?Why don?t you find a better name that >> represent ?group of devices?? >> > > It's not just group of devices - it's also per platform. Imagine if there > are paid and free versions of an app. That *can* be managed as two > variants, on one app. I am open to improvements here > > >> >> Lukas mention that a change of wording at this point would be very hard >> since we have the word ?Variant? all over our docs. But maybe for 2.0 we >> can think of a better way to help the user understand what a Variant is. >> > > +1 - perhaps we can improve the text on the UI ? > We should be far more descriptive about what "application" and "variant" and "installation" terms means. :-) It is not enough to describe it in the docs. > > >> >> Here is the prototype, click around and send feedback :) >> http://andresgalante.com/ups-console/login.html > > > > I still think the *skip* is too small. > > Also, on the wizard, if it should always go to Send (but we had that on a > different thread) > > >> >> >> >> [1]http://andresgalante.com/ups-console/app-detail-variants.html >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> 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/20150122/a0fb9462/attachment.html From cvasilak at gmail.com Thu Jan 22 11:26:07 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 22 Jan 2015 18:26:07 +0200 Subject: [aerogear-dev] Release push-sdk (swift) port in cocoapods Message-ID: <45F570E7-D172-4237-B15E-878A364F0BEC@gmail.com> Hi team, after [1] is merged I would like to tag and publish the library in cocoapods. For versioning, I am considering using 1.0.0 (same as in obj-c) with the relative tag 1.0.0-swift, in order not to conflict with the 1.0.0 tag of obj-c counterpart, since they share the same repo. wdyth? Thanks, Christos [1] https://github.com/aerogear/aerogear-ios-push/pull/41 From matzew at apache.org Thu Jan 22 11:29:40 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 22 Jan 2015 17:29:40 +0100 Subject: [aerogear-dev] Release push-sdk (swift) port in cocoapods In-Reply-To: <45F570E7-D172-4237-B15E-878A364F0BEC@gmail.com> References: <45F570E7-D172-4237-B15E-878A364F0BEC@gmail.com> Message-ID: On Thu, Jan 22, 2015 at 5:26 PM, Christos Vasilakis wrote: > Hi team, > > after [1] is merged I would like to tag and publish the library in > cocoapods. +1 ship it :-) > For versioning, I am considering using 1.0.0 (same as in obj-c) with the > relative tag 1.0.0-swift, in order not to conflict with the 1.0.0 tag of > obj-c counterpart, since they share the same repo. > that's fine w/ me - just wondering does a (slightly) different versioning confuse the cocoapod? :) > > wdyth? > > Thanks, > Christos > > [1] https://github.com/aerogear/aerogear-ios-push/pull/41 > _______________________________________________ > 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/20150122/a42d18d2/attachment.html From agalante at redhat.com Thu Jan 22 12:03:23 2015 From: agalante at redhat.com (Andres Galante) Date: Thu, 22 Jan 2015 12:03:23 -0500 (EST) Subject: [aerogear-dev] UPS console new UI review In-Reply-To: References: <728634889.3194448.1421880007351.JavaMail.zimbra@redhat.com> <1773858727.3196748.1421880948843.JavaMail.zimbra@redhat.com> Message-ID: <598678106.3348249.1421946203567.JavaMail.zimbra@redhat.com> Warning: I think that the warning should not disappear until the user sees where the error is. We should show him exactly where the mistake happened (lets say a notification not been sent), once he clicks on it we remove the warning. Progress indications: Thanks for the clarification, I misunderstood :p Variant page: What are the chances a user sets up lots of variants? Talking today with Tadeas Kriz, he says that his developer team never uses more than 2 variants per platform and if someone adds lots of variant he would be using wrongly the app. Would a user ever set up lots of variants or this is a made up behaviour? Skip link on wizard: I'll change the placement and make it more visible. This is something that came up as a UI issue on user testing also. ----- Original Message ----- From: "Luk?? Fry?" To: "AeroGear Developer Mailing List" Sent: Thursday, January 22, 2015 1:14:55 PM Subject: Re: [aerogear-dev] UPS console new UI review On Thu, Jan 22, 2015 at 10:54 AM, Matthias Wessendorf < matzew at apache.org > wrote: On Wed, Jan 21, 2015 at 11:55 PM, Andres Galante < agalante at redhat.com > wrote: Hey! Today Lukas, Sebastien help me review UPS new UI. I also did some usability testing yesterday (over dinner with slightly drunk programmers friends of mine). Here are the results and a bunch of questions for us to discuss: - Code snippets need a ?copy? btn like http://getbootstrap.com/components/ +1 - Descriptions on apps and variants. Can we just remove them? Are they useful? yeah, I think we can remove them. Here is a JIRA for it: https://issues.jboss.org/browse/AGPUSH-1240 - "Add a variant" form. There is going to be a validation of the form to make sure connections are correctly set up. +1 created https://issues.jboss.org/browse/AGPUSH-1241 - Variants page [1]. If the user has lots of variants set up, the list would be huge. I am working on solutions, Lukas and Sebastien had very good ideas. - "Send notification" form has the same problem. Lukas suggested a great solution, to use Multiple select boxes https://select2.github.io/examples.html any details? Sebi commented on "Send notification" screen that checkboxes are not ideal way to select multiple variants when you have huge number of variants, say 20. In other to save screen space, we would need to make it scrollable OR put into several columns OR as I suggested, we may use a search selection box with groups per platform and auto-completion, such as "Multiple select boxes" sample on https://select2.github.io/examples.html - Warnings. Where to show them? How to display them? I like how they are presented in the current UI Andres presented us that warnings are shown on the variant screen: http://andresgalante.com/ups-console/app-detail-variants.html I just wondered when the warning disappears (what's a best approach from UX perspective). How to make them disappear once the issue is solve? Not sure.... we keep them, and after 30 days there is a job to delete the warnings. I'd keep them, for tracking that there was a problem a few days ago. - Delete apps or variants takes a lot of time. there is a JIRA about this. which one ? - Add a progress bar to show progress of notifications been sent. Isn't that miss leading? We can not guarantee that the message are delivered to the phone. We just give them to Google/Apple/etc. If they move them to /dev/null - well :-) I don't remember discussing this, I was talking about design of "progress indicators" in general - if the app is taking any action, the UI should not allow the user to do anything else unless the request is fully processed (which is not true in the 1.0.x) - and ideally show some action indicator - e.g. a spinner. :-) - Add links to documentation everywhere. yeah - do we have a JIRA for that ? - We talked about adding sorting options on the variants list (by name, or by creation date) but it seems that search would be enough. although there was one tester that asked for sorting options. +1 for search only. Did you guys create a JIRA for that ? - It also come to my attention that the name ?Variant? is too general. Every non UPS developer I've shown the console asked me ?what are variants? and when I explain, they asked me ?Why don?t you find a better name that represent ?group of devices?? It's not just group of devices - it's also per platform. Imagine if there are paid and free versions of an app. That *can* be managed as two variants, on one app. I am open to improvements here Lukas mention that a change of wording at this point would be very hard since we have the word ?Variant? all over our docs. But maybe for 2.0 we can think of a better way to help the user understand what a Variant is. +1 - perhaps we can improve the text on the UI ? We should be far more descriptive about what "application" and "variant" and "installation" terms means. :-) It is not enough to describe it in the docs. Here is the prototype, click around and send feedback :) http://andresgalante.com/ups-console/login.html I still think the *skip* is too small. Also, on the wizard, if it should always go to Send (but we had that on a different thread) [1] http://andresgalante.com/ups-console/app-detail-variants.html _______________________________________________ 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 From cvasilak at gmail.com Thu Jan 22 12:34:47 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 22 Jan 2015 19:34:47 +0200 Subject: [aerogear-dev] Release push-sdk (swift) port in cocoapods In-Reply-To: References: <45F570E7-D172-4237-B15E-878A364F0BEC@gmail.com> Message-ID: > On Jan 22, 2015, at 6:29 PM, Matthias Wessendorf wrote: > > > > On Thu, Jan 22, 2015 at 5:26 PM, Christos Vasilakis > wrote: > Hi team, > > after [1] is merged I would like to tag and publish the library in cocoapods. > > +1 ship it :-) > > For versioning, I am considering using 1.0.0 (same as in obj-c) with the relative tag 1.0.0-swift, in order not to conflict with the 1.0.0 tag of obj-c counterpart, since they share the same repo. > > that's fine w/ me - just wondering does a (slightly) different versioning confuse the cocoapod? :) not, as long as the podspec tag points to the correct one it should be fine. Here it helps we are a different Podspec. s.source = { :git => 'https://github.com/aerogear/aerogear-ios-push.git', :tag => ?1.0.0.swift? } - Christos > > > wdyth? > > Thanks, > Christos > > [1] https://github.com/aerogear/aerogear-ios-push/pull/41 > _______________________________________________ > 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/20150122/75e5bcb1/attachment.html From corinnekrych at gmail.com Thu Jan 22 12:35:41 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 22 Jan 2015 18:35:41 +0100 Subject: [aerogear-dev] Parallel support for a Cocoapods Swift/Obj-c library In-Reply-To: <16F9E2F7-6C1C-4918-9FBF-0730B0441A42@gmail.com> References: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> <16F9E2F7-6C1C-4918-9FBF-0730B0441A42@gmail.com> Message-ID: <9E82C0AE-87F1-48CE-AE1B-C90FFA7881D7@gmail.com> Oki for b, make sense and is easy to understand. We go for 2 podspecs on 2 different branches. In aerogear-io-push on 1.x_dev brnach we keep podspec unchanged. on master branch (Swift version) podspec get renamed to AeroGear-Push-Swift On side note, interesting use case of QueryKit Swift-first lib, bridging from Swift to obj-c. How you turn strongly typed designed library to dynamic lg. Generics -> AnyObject like shown in [1] it could be the case for ex if you want ot use ou jsonsz lib in obj-c but i?d simply go: use obj-c fwk like mantle... ++ Corinne [1] https://github.com/QueryKit/QueryKit/blob/master/QueryKit%2FObjectiveC%2FQKAttribute.swift#L10 > On 22 Jan 2015, at 15:40, Christos Vasilakis wrote: > >> >> On Jan 22, 2015, at 4:21 PM, Matthias Wessendorf wrote: >> >> Wow, thanks for all the details around here >> >> On Thu, Jan 22, 2015 at 2:01 PM, Christos Vasilakis wrote: >> Hi team, >> >> a little heads up on an issue that I?ve been looking the last days, on how to proper support both an Obj-C and a Swift library (in-parallel) on Cocoapods. There was a discussion on the cocoapods issues tracker[1] basically around two ideas: >> >> a) being a separate project, with a new name plus utilising Swift specific language propers. >> b) having one project, utilising cocoapods subspec mechanism to include specific files per spec requested. In a nutshell users will employ in their Podfile something of a form: >> >> ? >> pod ?MyFooBarLibrary/Objc? (objective-c) >> or >> pod ? MyFooBarLibrary/Swift? (Swift) >> ? >> >> Solution (b) was intrigued and went on to discover more, since I haven?t used before the subspec mechanism and was a good opportunity to learn. The issue mentioned two projects, QueryKit[2] and ReactiveCocoa[3] (their Swift branch) that utilise this mechanism, so I dive in trying to see how it works. >> >> My realisations: >> a) both projects are designed with ?Swift first? approach, employing _some_ 'Objective-C code? to ease the interaction in a mixed project e.g Objective-C code calling the ?Swift? library, see [4] where the author describes more details on this. >> b) since ?Swift first?, both produce frameworks where they can be integrated either in objective-c or swift language projects, no ?static-library? targets. >> c) both are designed for iOS >= 8.0 >> >> ouch - what do they do for iOS7 ? > > no support for iOS 7, QueryKit and ReactiveCocoa(swift branch) are fairly new and designed to work on iOS 8 and later > > Note: ReactiveCocoa has a ?master' branch with support of iOS 7/8 but ?objective-c? only. > > >> >> >> >> To make it short and from my understanding, the projects are _not_ designed around the idea of: take either the Objective-C or the Swift port in you project, but instead employ an Objective-C subspec to ?ease? the interaction in a mixed environment, aka Objective-C code calling the Swift library. >> >> Regardless and to better understand, I did some testing with our push-sdk: >> >> a) having a single Swift Project employing both the objective-c code and Swift code >> b) having a .workspace with a) Obj-c xcodeproj, b) Swift xcodeproj. >> >> In both cases, this mixed approaches, at the end caused issues and wasn?t able to generate a proper solution. Issues around a) cocoapods 'pod install? steps, b) tests on the library are done with two different dependencies c) various other integration issues? >> >> It?s my sense, the most clean way is to go with separate libraries, that is solution (a) described above (a solution proposed also from @orta [5]) This has the added benefit of cleaner 'logistics? that is: commit history, releases, static/framework library generations etc etc. >> >> +1000 :-) When reading, I was actually wondering about these logistics :) >> >> >> But there is one issue if we go with separate approach: _cocoapods naming_, that is how to properly separate between the two. >> >> Currently searching for AeroGear-Push in cocoapods.org site we get the following: >> >> >> >> >> In my cocoapods PR [6] I went with the approach to name the ?Swift? equivalent library as 'AeroGear-Push-Swift?, so the same searching above will reveal: >> >> ? >> AeroGear-Push >> AeroGear-Push-Swift >> ? >> >> Some of you have already noticed, that the ?hyphen? character as a podspec name doesn?t work well with a Swift Project, cause the podspec name is used as the name of the final #import statement the user does. That is the following import statement doesn?t work: >> >> ? >> import AeroGear-Push-Swift >> ? >> >> Solving this, there are two approaches: >> >> a) rename both library podspecs : Objective-C to -> AeroGearPush and Swift to -> AeroGearPushSwift >> b) continue the same naming, but use the new ?module_name? podspec directive in the Swift project(added in cocoapods [6]) to specify the final module name the user will use on the import. That is the approach I have taken in my PR[6] >> >> +1 on b), using the module_name - nice addon to CocoaPods >> >> >> >> If we go with (b) the entries will look like this: >> >> ?? >> Obj-c: (no changes needed) >> >> Podfile: pod 'AeroGear-Push? >> >> Class: #import >> >> >> Swift: >> >> Podfile: pod 'AeroGear-Push-Swift? >> >> Class: import ?AeroGearPush? (notice _no_ ?Swift? postfix is needed cause of the ?module_name? override) >> >> ?? >> >> I am fine with both albeit more towards (b) mostly not to break existing ?pod installs? the users may use and since support with the ?module_name? directive is provided from cocoapods. Current PR[6] goes with this approach. >> >> Let me know your comments and suggestions >> >> Thanks >> Christos >> >> [1] https://github.com/CocoaPods/CocoaPods/issues/3016 >> [2] https://github.com/QueryKit/QueryKit >> [3] https://github.com/ReactiveCocoa/ReactiveCocoa/tree/swift-development >> [4] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69092100 >> [5] https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69073109 >> [6] https://github.com/aerogear/aerogear-ios-push/pull/41 >> [7] http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/ >> >> _______________________________________________ >> 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 From corinnekrych at gmail.com Fri Jan 23 03:30:42 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 23 Jan 2015 09:30:42 +0100 Subject: [aerogear-dev] Swift to Objective-C interop: one aspect of iOS7 Swift support Message-ID: Hello all, Yesterday I was discussing with Sebi about @objc and how you make a Swift class available in Objective-C Sebi has one issue, in its Swift protocol he wants to declare longitude/latitude Double and make them optional [1]. Because his protocol is swift only (not inheriting a Obj-c one) he uses @objc and this is when, compiler complains with ?Property cannot be marked @objc because its type cannot be represented in Objective-C?. This issue is well-explain in this stack overflow thread [2] One work-around (the one used by Sebi) is to use NSNumber and make then optional. To echo that issue, yesterday Christos on this thread [3] gave the example of QueryKit which uses pod subspec coupled with some Objective-C re-write classes (seen as temporary) to bridge the gap Swift to Objective-C fro a Swift first library. As we?re talking about iOS7 support for our Swift libs there are 2 aspect of it: - support from obj-c code is one aspect - dynamic fwk support as expained in this thread [4] is another one? All in one, it makes me wonder if it?s worth it? all those hacks in Swift code. Maybe the option we used for ios-push lib i.e.: having obj-c and swift version of the lib would be a better approach. ++ Corinne [1] https://github.com/sebastienblanc/helloworld-geo-ios/blob/master/UnifiedGeo%2FUnifiedGeo%2FAGClientDeviceInformation.swift#L46 [2] http://stackoverflow.com/questions/26366082/cannot-access-property-of-swift-type-from-objective-c [3] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Parallel-support-for-a-Cocoapods-Swift-Obj-c-library-td10632.html [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Swift-Frameworks-Static-libs-and-Cocoapods-tc8456.html From scm.blanc at gmail.com Fri Jan 23 03:45:27 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 23 Jan 2015 09:45:27 +0100 Subject: [aerogear-dev] Swift to Objective-C interop: one aspect of iOS7 Swift support In-Reply-To: References: Message-ID: On Fri, Jan 23, 2015 at 9:30 AM, Corinne Krych wrote: > Hello all, > > Yesterday I was discussing with Sebi about @objc and how you make a Swift > class available in Objective-C > > Sebi has one issue, in its Swift protocol he wants to declare > longitude/latitude Double and make them optional [1]. Because his protocol > is swift only (not inheriting a Obj-c one) he uses @objc and this is when, > compiler complains with ?Property cannot be marked @objc because its type > cannot be represented in Objective-C?. > > This issue is well-explain in this stack overflow thread [2] > One work-around (the one used by Sebi) is to use NSNumber and make then > optional. > > To echo that issue, yesterday Christos on this thread [3] gave the example > of QueryKit which uses pod subspec coupled with some Objective-C re-write > classes (seen as temporary) to bridge the gap Swift to Objective-C fro a > Swift first library. > > As we?re talking about iOS7 support for our Swift libs there are 2 aspect > of it: > - support from obj-c code is one aspect > - dynamic fwk support as expained in this thread [4] is another one? > > All in one, it makes me wonder if it?s worth it? all those hacks in Swift > code. Maybe the option we used for ios-push lib i.e.: having obj-c and > swift version of the lib would be a better approach. > +1 , better having 2 clean and robust libs , rather than 1 lib full of hacks. > > ++ > Corinne > [1] > https://github.com/sebastienblanc/helloworld-geo-ios/blob/master/UnifiedGeo%2FUnifiedGeo%2FAGClientDeviceInformation.swift#L46 > [2] > http://stackoverflow.com/questions/26366082/cannot-access-property-of-swift-type-from-objective-c > [3] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Parallel-support-for-a-Cocoapods-Swift-Obj-c-library-td10632.html > [4] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Swift-Frameworks-Static-libs-and-Cocoapods-tc8456.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/20150123/94181b20/attachment-0001.html From matzew at apache.org Fri Jan 23 04:00:29 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 23 Jan 2015 10:00:29 +0100 Subject: [aerogear-dev] Swift to Objective-C interop: one aspect of iOS7 Swift support In-Reply-To: References: Message-ID: On Fri, Jan 23, 2015 at 9:30 AM, Corinne Krych wrote: > Hello all, > > Yesterday I was discussing with Sebi about @objc and how you make a Swift > class available in Objective-C > > Sebi has one issue, in its Swift protocol he wants to declare > longitude/latitude Double and make them optional [1]. Because his protocol > is swift only (not inheriting a Obj-c one) he uses @objc and this is when, > compiler complains with ?Property cannot be marked @objc because its type > cannot be represented in Objective-C?. > > This issue is well-explain in this stack overflow thread [2] > One work-around (the one used by Sebi) is to use NSNumber and make then > optional. > > To echo that issue, yesterday Christos on this thread [3] gave the example > of QueryKit which uses pod subspec coupled with some Objective-C re-write > classes (seen as temporary) to bridge the gap Swift to Objective-C fro a > Swift first library. > > As we?re talking about iOS7 support for our Swift libs there are 2 aspect > of it: > - support from obj-c code is one aspect > - dynamic fwk support as expained in this thread [4] is another one? > > All in one, it makes me wonder if it?s worth it? all those hacks in Swift > code. +1 > Maybe the option we used for ios-push lib i.e.: having obj-c and swift > version of the lib would be a better approach. > that means we need to code the missing parts on our other libs, like http or oauth, right ? > > ++ > Corinne > [1] > https://github.com/sebastienblanc/helloworld-geo-ios/blob/master/UnifiedGeo%2FUnifiedGeo%2FAGClientDeviceInformation.swift#L46 > [2] > http://stackoverflow.com/questions/26366082/cannot-access-property-of-swift-type-from-objective-c > [3] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Parallel-support-for-a-Cocoapods-Swift-Obj-c-library-td10632.html > [4] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Swift-Frameworks-Static-libs-and-Cocoapods-tc8456.html > _______________________________________________ > 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/20150123/1777ba98/attachment.html From corinnekrych at gmail.com Fri Jan 23 04:04:45 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 23 Jan 2015 10:04:45 +0100 Subject: [aerogear-dev] Swift to Objective-C interop: one aspect of iOS7 Swift support In-Reply-To: References: Message-ID: > On 23 Jan 2015, at 10:00, Matthias Wessendorf wrote: > > > > On Fri, Jan 23, 2015 at 9:30 AM, Corinne Krych wrote: > Hello all, > > Yesterday I was discussing with Sebi about @objc and how you make a Swift class available in Objective-C > > Sebi has one issue, in its Swift protocol he wants to declare longitude/latitude Double and make them optional [1]. Because his protocol is swift only (not inheriting a Obj-c one) he uses @objc and this is when, compiler complains with ?Property cannot be marked @objc because its type cannot be represented in Objective-C?. > > This issue is well-explain in this stack overflow thread [2] > One work-around (the one used by Sebi) is to use NSNumber and make then optional. > > To echo that issue, yesterday Christos on this thread [3] gave the example of QueryKit which uses pod subspec coupled with some Objective-C re-write classes (seen as temporary) to bridge the gap Swift to Objective-C fro a Swift first library. > > As we?re talking about iOS7 support for our Swift libs there are 2 aspect of it: > - support from obj-c code is one aspect > - dynamic fwk support as expained in this thread [4] is another one? > > All in one, it makes me wonder if it?s worth it? all those hacks in Swift code. > > +1 > > Maybe the option we used for ios-push lib i.e.: having obj-c and swift version of the lib would be a better approach. > > that means we need to code the missing parts on our other libs, like http or oauth, right ? > > Yeap, OAuth2 will be a good one to start with? Part of it was already written in objc in 1.6.X code base. It?s based on AFNetworking for the http layer. Maybe we can keep using AFNet and no need to move ios-http to obj-c > > ++ > Corinne > [1] https://github.com/sebastienblanc/helloworld-geo-ios/blob/master/UnifiedGeo%2FUnifiedGeo%2FAGClientDeviceInformation.swift#L46 > [2] http://stackoverflow.com/questions/26366082/cannot-access-property-of-swift-type-from-objective-c > [3] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Parallel-support-for-a-Cocoapods-Swift-Obj-c-library-td10632.html > [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Swift-Frameworks-Static-libs-and-Cocoapods-tc8456.html > _______________________________________________ > 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 From matzew at apache.org Fri Jan 23 04:47:00 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 23 Jan 2015 10:47:00 +0100 Subject: [aerogear-dev] Swift to Objective-C interop: one aspect of iOS7 Swift support In-Reply-To: References: Message-ID: On Fri, Jan 23, 2015 at 10:04 AM, Corinne Krych wrote: > > > On 23 Jan 2015, at 10:00, Matthias Wessendorf wrote: > > > > > > > > On Fri, Jan 23, 2015 at 9:30 AM, Corinne Krych > wrote: > > Hello all, > > > > Yesterday I was discussing with Sebi about @objc and how you make a > Swift class available in Objective-C > > > > Sebi has one issue, in its Swift protocol he wants to declare > longitude/latitude Double and make them optional [1]. Because his protocol > is swift only (not inheriting a Obj-c one) he uses @objc and this is when, > compiler complains with ?Property cannot be marked @objc because its type > cannot be represented in Objective-C?. > > > > This issue is well-explain in this stack overflow thread [2] > > One work-around (the one used by Sebi) is to use NSNumber and make then > optional. > > > > To echo that issue, yesterday Christos on this thread [3] gave the > example of QueryKit which uses pod subspec coupled with some Objective-C > re-write classes (seen as temporary) to bridge the gap Swift to Objective-C > fro a Swift first library. > > > > As we?re talking about iOS7 support for our Swift libs there are 2 > aspect of it: > > - support from obj-c code is one aspect > > - dynamic fwk support as expained in this thread [4] is another one? > > > > All in one, it makes me wonder if it?s worth it? all those hacks in > Swift code. > > > > +1 > > > > Maybe the option we used for ios-push lib i.e.: having obj-c and swift > version of the lib would be a better approach. > > > > that means we need to code the missing parts on our other libs, like > http or oauth, right ? > > > > > > > Yeap, OAuth2 will be a good one to start with? > +1 > Part of it was already written in objc in 1.6.X code base. It?s based on > AFNetworking for the http layer. > Maybe we can keep using AFNet and no need to move ios-http to obj-c > +1000 > > > > > ++ > > Corinne > > [1] > https://github.com/sebastienblanc/helloworld-geo-ios/blob/master/UnifiedGeo%2FUnifiedGeo%2FAGClientDeviceInformation.swift#L46 > > [2] > http://stackoverflow.com/questions/26366082/cannot-access-property-of-swift-type-from-objective-c > > [3] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Parallel-support-for-a-Cocoapods-Swift-Obj-c-library-td10632.html > > [4] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Swift-Frameworks-Static-libs-and-Cocoapods-tc8456.html > > _______________________________________________ > > 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/20150123/426f1628/attachment.html From bruno at abstractj.org Fri Jan 23 09:23:33 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 23 Jan 2015 12:23:33 -0200 Subject: [aerogear-dev] Jira instance for AGSYNC Message-ID: <20150123142333.GA63479@abstractj.org> Good morning, like we discussed before http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-datasync-JIRA-component-name-td9876.html, I create the following Jira for planning data sync https://issues.jboss.org/browse/AEROGEAR-1586. If you totally disagree, vote, raise your hand or whatever. Thanks in advance. -- abstractj PGP: 0x84DC9914 From matzew at apache.org Fri Jan 23 09:30:45 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 23 Jan 2015 15:30:45 +0100 Subject: [aerogear-dev] Jira instance for AGSYNC In-Reply-To: <20150123142333.GA63479@abstractj.org> References: <20150123142333.GA63479@abstractj.org> Message-ID: +90001 On Fri, Jan 23, 2015 at 3:23 PM, Bruno Oliveira wrote: > Good morning, like we discussed before > > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-datasync-JIRA-component-name-td9876.html > , > I create the following Jira for planning data sync > https://issues.jboss.org/browse/AEROGEAR-1586. If you totally disagree, > vote, raise your hand or whatever. > > Thanks in advance. > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > 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/20150123/346b6185/attachment-0001.html From cvasilak at gmail.com Fri Jan 23 10:44:29 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Fri, 23 Jan 2015 17:44:29 +0200 Subject: [aerogear-dev] push-sdk (Swift) port v1.0 Message-ID: Hi all, since Swift as language seems to have stabilise a bit and no _big changes_ have occurred on the last Xcode releases, we thought it will be good to release an v1.0 port of our push-sdk library for those that are interested in and staring a new project. So, we have tagged and released the port on github[1] as well as on Cocoapods[2]. (If you use Cocoapods you will need to ensure the ?-pre? release is installed that brings support for Swift frameworks, but you know that right! :) Our HelloWorld[3] and Contacts[4] quick-starts have also been ported, and have been updated to the latest push-sdk release. So go ahead give it a try and let us know what you think. Enjoy! - Christos [1] https://github.com/aerogear/aerogear-ios-push/archive/1.0.0-swift.zip [2] http://cocoapods.org/?q=aerogear-push-swift [3] https://github.com/aerogear/aerogear-push-helloworld/tree/swift/ios-swift [4] https://github.com/aerogear/aerogear-push-quickstarts/tree/swift/client/contacts-mobile-ios-client-swift From agalante at redhat.com Fri Jan 23 13:29:59 2015 From: agalante at redhat.com (Andres Galante) Date: Fri, 23 Jan 2015 13:29:59 -0500 (EST) Subject: [aerogear-dev] Help to review UPS new UI. Am I missing something? In-Reply-To: <16615287.3628013.1422037346037.JavaMail.zimbra@redhat.com> Message-ID: <712197351.3629430.1422037799698.JavaMail.zimbra@redhat.com> Lots of small changes on UPS new UI: - Removed remember me and forget password from login page: http://andresgalante.com/ups-console/login.html - Added first step on wizard to make it more clear what to expect: http://andresgalante.com/ups-console/wizard01-welcome.html - Made Skip Wizard easier to find on wizard screens http://andresgalante.com/ups-console/wizard01.html - Added main warning alert: http://andresgalante.com/ups-console/index.html - Added validation alerts and styles to Add variant form (click add variant): http://andresgalante.com/ups-console/app-detail-variants.html - Change the way to select Variants on Send notification form (click send notification): http://andresgalante.com/ups-console/app-detail-variants.html - Change the way information is display on Sender API page, and warnings after clicking on change master secret: http://andresgalante.com/ups-console/app-detail.html - Added "Copy" btn on every code snippet. Plus there are small changes everywhere. If you have time please review everything and let me know what I am missing, otherwise I think this should be ready to start implementation. Thanks! Andr?s From matzew at apache.org Fri Jan 23 14:25:06 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 23 Jan 2015 20:25:06 +0100 Subject: [aerogear-dev] AeroGear-Parent: 0.2.9.1 release Message-ID: Hi, to fix a Keycloak bug on EAP ([1]), we need to pick up their new 1.0.5 release, which they ran just for us. Now, this release needs to be consumed on our 1.0.x series to get the 1.0.3 out! Since 1.0.x is using a slightly older parent (0.2.9) I created a new TAG 0.2.9.1 containing only the new KC version, basically to limit potential risks (and our latest parent is already on the _newer_ KC 1.1.x series). So, I have prepared the release for this, and did stage the 0.2.9.1 (which is exactly like 0.2.9, just has the new KC version). The staging repo is here: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4696/ Please test with the 1.0.x branch and let me know how that went. I plan to release the bits to maven central on Tuesday. Greetings, Matthias [1] https://issues.jboss.org/browse/KEYCLOAK-977 -- 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/20150123/ec1bf8d7/attachment.html From daniel at passos.me Fri Jan 23 20:12:03 2015 From: daniel at passos.me (Daniel Passos) Date: Fri, 23 Jan 2015 23:12:03 -0200 Subject: [aerogear-dev] Parallel support for a Cocoapods Swift/Obj-c library In-Reply-To: <9E82C0AE-87F1-48CE-AE1B-C90FFA7881D7@gmail.com> References: <440F2668-AC1F-4AD2-A512-1F639706EFFF@gmail.com> <16F9E2F7-6C1C-4918-9FBF-0730B0441A42@gmail.com> <9E82C0AE-87F1-48CE-AE1B-C90FFA7881D7@gmail.com> Message-ID: Thanks for the awesome heads up Christos +1 on b -- Passos On Thu, Jan 22, 2015 at 3:35 PM, Corinne Krych wrote: > Oki for b, make sense and is easy to understand. > > We go for 2 podspecs on 2 different branches. > In aerogear-io-push on 1.x_dev brnach we keep podspec unchanged. > on master branch (Swift version) podspec get renamed to AeroGear-Push-Swift > > On side note, interesting use case of QueryKit Swift-first lib, bridging > from Swift to obj-c. How you turn strongly typed designed library to > dynamic lg. Generics -> AnyObject like shown in [1] > it could be the case for ex if you want ot use ou jsonsz lib in obj-c but > i?d simply go: use obj-c fwk like mantle... > > ++ > Corinne > [1] > https://github.com/QueryKit/QueryKit/blob/master/QueryKit%2FObjectiveC%2FQKAttribute.swift#L10 > > > On 22 Jan 2015, at 15:40, Christos Vasilakis wrote: > > > >> > >> On Jan 22, 2015, at 4:21 PM, Matthias Wessendorf > wrote: > >> > >> Wow, thanks for all the details around here > >> > >> On Thu, Jan 22, 2015 at 2:01 PM, Christos Vasilakis > wrote: > >> Hi team, > >> > >> a little heads up on an issue that I?ve been looking the last days, on > how to proper support both an Obj-C and a Swift library (in-parallel) on > Cocoapods. There was a discussion on the cocoapods issues tracker[1] > basically around two ideas: > >> > >> a) being a separate project, with a new name plus utilising Swift > specific language propers. > >> b) having one project, utilising cocoapods subspec mechanism to include > specific files per spec requested. In a nutshell users will employ in their > Podfile something of a form: > >> > >> ? > >> pod ?MyFooBarLibrary/Objc? (objective-c) > >> or > >> pod ? MyFooBarLibrary/Swift? (Swift) > >> ? > >> > >> Solution (b) was intrigued and went on to discover more, since I > haven?t used before the subspec mechanism and was a good opportunity to > learn. The issue mentioned two projects, QueryKit[2] and ReactiveCocoa[3] > (their Swift branch) that utilise this mechanism, so I dive in trying to > see how it works. > >> > >> My realisations: > >> a) both projects are designed with ?Swift first? approach, employing > _some_ 'Objective-C code? to ease the interaction in a mixed project e.g > Objective-C code calling the ?Swift? library, see [4] where the author > describes more details on this. > >> b) since ?Swift first?, both produce frameworks where they can be > integrated either in objective-c or swift language projects, no > ?static-library? targets. > >> c) both are designed for iOS >= 8.0 > >> > >> ouch - what do they do for iOS7 ? > > > > no support for iOS 7, QueryKit and ReactiveCocoa(swift branch) are > fairly new and designed to work on iOS 8 and later > > > > Note: ReactiveCocoa has a ?master' branch with support of iOS 7/8 but > ?objective-c? only. > > > > > >> > >> > >> > >> To make it short and from my understanding, the projects are _not_ > designed around the idea of: take either the Objective-C or the Swift port > in you project, but instead employ an Objective-C subspec to ?ease? the > interaction in a mixed environment, aka Objective-C code calling the Swift > library. > >> > >> Regardless and to better understand, I did some testing with our > push-sdk: > >> > >> a) having a single Swift Project employing both the objective-c code > and Swift code > >> b) having a .workspace with a) Obj-c xcodeproj, b) Swift xcodeproj. > >> > >> In both cases, this mixed approaches, at the end caused issues and > wasn?t able to generate a proper solution. Issues around a) cocoapods 'pod > install? steps, b) tests on the library are done with two different > dependencies c) various other integration issues? > >> > >> It?s my sense, the most clean way is to go with separate libraries, > that is solution (a) described above (a solution proposed also from @orta > [5]) This has the added benefit of cleaner 'logistics? that is: commit > history, releases, static/framework library generations etc etc. > >> > >> +1000 :-) When reading, I was actually wondering about these logistics > :) > >> > >> > >> But there is one issue if we go with separate approach: _cocoapods > naming_, that is how to properly separate between the two. > >> > >> Currently searching for AeroGear-Push in cocoapods.org site we get the > following: > >> > >> > >> > >> > >> In my cocoapods PR [6] I went with the approach to name the ?Swift? > equivalent library as 'AeroGear-Push-Swift?, so the same searching above > will reveal: > >> > >> ? > >> AeroGear-Push > >> AeroGear-Push-Swift > >> ? > >> > >> Some of you have already noticed, that the ?hyphen? character as a > podspec name doesn?t work well with a Swift Project, cause the podspec name > is used as the name of the final #import statement the user does. That is > the following import statement doesn?t work: > >> > >> ? > >> import AeroGear-Push-Swift > >> ? > >> > >> Solving this, there are two approaches: > >> > >> a) rename both library podspecs : Objective-C to -> AeroGearPush and > Swift to -> AeroGearPushSwift > >> b) continue the same naming, but use the new ?module_name? podspec > directive in the Swift project(added in cocoapods [6]) to specify the final > module name the user will use on the import. That is the approach I have > taken in my PR[6] > >> > >> +1 on b), using the module_name - nice addon to CocoaPods > >> > >> > >> > >> If we go with (b) the entries will look like this: > >> > >> ?? > >> Obj-c: (no changes needed) > >> > >> Podfile: pod 'AeroGear-Push? > >> > >> Class: #import > >> > >> > >> Swift: > >> > >> Podfile: pod 'AeroGear-Push-Swift? > >> > >> Class: import ?AeroGearPush? (notice _no_ ?Swift? postfix is needed > cause of the ?module_name? override) > >> > >> ?? > >> > >> I am fine with both albeit more towards (b) mostly not to break > existing ?pod installs? the users may use and since support with the > ?module_name? directive is provided from cocoapods. Current PR[6] goes > with this approach. > >> > >> Let me know your comments and suggestions > >> > >> Thanks > >> Christos > >> > >> [1] https://github.com/CocoaPods/CocoaPods/issues/3016 > >> [2] https://github.com/QueryKit/QueryKit > >> [3] > https://github.com/ReactiveCocoa/ReactiveCocoa/tree/swift-development > >> [4] > https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69092100 > >> [5] > https://github.com/CocoaPods/CocoaPods/issues/3016#issuecomment-69073109 > >> [6] https://github.com/aerogear/aerogear-ios-push/pull/41 > >> [7] > http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/ > >> > >> _______________________________________________ > >> 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/20150123/39a863c1/attachment-0001.html From daniel.bevenius at gmail.com Sun Jan 25 04:08:58 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Sun, 25 Jan 2015 10:08:58 +0100 Subject: [aerogear-dev] Team meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-20150126 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150125/3af5bfa0/attachment.html From qmx at qmx.me Mon Jan 26 05:43:41 2015 From: qmx at qmx.me (Douglas Campos) Date: Mon, 26 Jan 2015 08:43:41 -0200 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy Message-ID: <20150126104341.GR13123@darkstar.local> Howdy! I've been envisioning a plan for UPS migrations, and would like to get some feedback from the community, so here it is: When there are model changes, it's kinda annoying to generate the sql migration files. This is one of the reasons Erik Jan de Wit started working to add liquibase to the project, allowing for seamless migrations. I'd like to build upon Erik's initial work and prepare a `ups-migrator` distribution: ups-migrator-VERSION.zip `--ups-migrator.jar `--ups-migrator-postgresql.properties `--ups-migrator-mysql.properties `--lib `-- `-- This migrator tool can be run with plain `java -jar` and deals with all the migrations needed up to `VERSION`, which means we would need only one migrator tool for both 1.0.x and HEAD. Thoughts? Comments? -- qmx From bruno at abstractj.org Mon Jan 26 05:57:24 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 26 Jan 2015 08:57:24 -0200 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: <20150126104341.GR13123@darkstar.local> References: <20150126104341.GR13123@darkstar.local> Message-ID: +1 On Mon, Jan 26, 2015 at 8:43 AM, Douglas Campos wrote: > Howdy! > > I've been envisioning a plan for UPS migrations, and would like to get > some feedback from the community, so here it is: > > When there are model changes, it's kinda annoying to generate the sql > migration files. This is one of the reasons Erik Jan de Wit started > working to add liquibase to the project, allowing for seamless > migrations. > > I'd like to build upon Erik's initial work and prepare a `ups-migrator` > distribution: > > ups-migrator-VERSION.zip > `--ups-migrator.jar > `--ups-migrator-postgresql.properties > `--ups-migrator-mysql.properties > `--lib > `-- > `-- > > This migrator tool can be run with plain `java -jar` and deals with all > the migrations needed up to `VERSION`, which means we would need only > one migrator tool for both 1.0.x and HEAD. > > Thoughts? Comments? > > -- > qmx > _______________________________________________ > 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/20150126/b2c5d918/attachment.html From daniel.bevenius at gmail.com Mon Jan 26 06:11:30 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 26 Jan 2015 12:11:30 +0100 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: References: <20150126104341.GR13123@darkstar.local> Message-ID: +1 Sounds nice On 26 January 2015 at 11:57, Bruno Oliveira wrote: > +1 > > On Mon, Jan 26, 2015 at 8:43 AM, Douglas Campos wrote: > >> Howdy! >> >> I've been envisioning a plan for UPS migrations, and would like to get >> some feedback from the community, so here it is: >> >> When there are model changes, it's kinda annoying to generate the sql >> migration files. This is one of the reasons Erik Jan de Wit started >> working to add liquibase to the project, allowing for seamless >> migrations. >> >> I'd like to build upon Erik's initial work and prepare a `ups-migrator` >> distribution: >> >> ups-migrator-VERSION.zip >> `--ups-migrator.jar >> `--ups-migrator-postgresql.properties >> `--ups-migrator-mysql.properties >> `--lib >> `-- >> `-- >> >> This migrator tool can be run with plain `java -jar` and deals with all >> the migrations needed up to `VERSION`, which means we would need only >> one migrator tool for both 1.0.x and HEAD. >> >> Thoughts? Comments? >> >> -- >> qmx >> _______________________________________________ >> 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/20150126/47c64415/attachment.html From matzew at apache.org Mon Jan 26 06:19:50 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 26 Jan 2015 12:19:50 +0100 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: <20150126104341.GR13123@darkstar.local> References: <20150126104341.GR13123@darkstar.local> Message-ID: On Mon, Jan 26, 2015 at 11:43 AM, Douglas Campos wrote: > Howdy! > > I've been envisioning a plan for UPS migrations, and would like to get > some feedback from the community, so here it is: > > When there are model changes, it's kinda annoying to generate the sql > migration files. This is one of the reasons Erik Jan de Wit started > working to add liquibase to the project, allowing for seamless > migrations. > > I'd like to build upon Erik's initial work and prepare a `ups-migrator` > distribution: > > ups-migrator-VERSION.zip > `--ups-migrator.jar > `--ups-migrator-postgresql.properties > `--ups-migrator-mysql.properties > `--lib > `-- > `-- > > This migrator tool can be run with plain `java -jar` and deals with all > the migrations needed up to `VERSION`, which means we would need only > one migrator tool for both 1.0.x and HEAD. > Sounds like a great idea. How do I specify the actual DB that I'd like to touch during the migration? Do I specify (cmd args?) which of the properties is picked up ? -Matthias > > Thoughts? Comments? > > -- > qmx > _______________________________________________ > 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/20150126/ee4879bc/attachment.html From edewit at redhat.com Mon Jan 26 06:22:41 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 26 Jan 2015 12:22:41 +0100 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: <20150126104341.GR13123@darkstar.local> References: <20150126104341.GR13123@darkstar.local> Message-ID: <54C62381.10707@redhat.com> On 26/01/2015 11:43, Douglas Campos wrote: > This migrator tool can be run with plain `java -jar` and deals with all > the migrations needed up to `VERSION`, which means we would need only > one migrator tool for both 1.0.x and HEAD. > > Thoughts? Comments? great idea, but why not use the maven plugin to execute the liquibase migration? From qmx at qmx.me Mon Jan 26 06:30:42 2015 From: qmx at qmx.me (Douglas Campos) Date: Mon, 26 Jan 2015 09:30:42 -0200 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: References: <20150126104341.GR13123@darkstar.local> Message-ID: <20150126113042.GT13123@darkstar.local> On Mon, Jan 26, 2015 at 12:19:50PM +0100, Matthias Wessendorf wrote: > On Mon, Jan 26, 2015 at 11:43 AM, Douglas Campos wrote: > Sounds like a great idea. How do I specify the actual DB that I'd like to > touch during the migration? Do I specify (cmd args?) which of the > properties is picked up ? I should've named the files ups-migrator-postgresql-example.properties. You just create a ups-migrator.properties :) -- qmx From matzew at apache.org Mon Jan 26 06:32:13 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 26 Jan 2015 12:32:13 +0100 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: <20150126113042.GT13123@darkstar.local> References: <20150126104341.GR13123@darkstar.local> <20150126113042.GT13123@darkstar.local> Message-ID: On Mon, Jan 26, 2015 at 12:30 PM, Douglas Campos wrote: > On Mon, Jan 26, 2015 at 12:19:50PM +0100, Matthias Wessendorf wrote: > > On Mon, Jan 26, 2015 at 11:43 AM, Douglas Campos wrote: > > Sounds like a great idea. How do I specify the actual DB that I'd like to > > touch during the migration? Do I specify (cmd args?) which of the > > properties is picked up ? > I should've named the files ups-migrator-postgresql-example.properties. > You just create a ups-migrator.properties :) > Sounds good to me ! > > > -- > qmx > _______________________________________________ > 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/20150126/827d20cc/attachment-0001.html From qmx at qmx.me Mon Jan 26 06:32:28 2015 From: qmx at qmx.me (Douglas Campos) Date: Mon, 26 Jan 2015 09:32:28 -0200 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: <54C62381.10707@redhat.com> References: <20150126104341.GR13123@darkstar.local> <54C62381.10707@redhat.com> Message-ID: <20150126113228.GU13123@darkstar.local> On Mon, Jan 26, 2015 at 12:22:41PM +0100, Erik Jan de Wit wrote: > > On 26/01/2015 11:43, Douglas Campos wrote: > > This migrator tool can be run with plain `java -jar` and deals with all > > the migrations needed up to `VERSION`, which means we would need only > > one migrator tool for both 1.0.x and HEAD. > > > > Thoughts? Comments? > great idea, but why not use the maven plugin to execute the liquibase > migration? There are several reasons, but the most important is to avoid asking our users which just deploy a war file into their appserver to clone the project, wait for maven to download the internet, then finally see the migration happening. Also, the maven plugin has less features than the liquibase cli tools. -- qmx From matzew at apache.org Mon Jan 26 06:38:04 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 26 Jan 2015 12:38:04 +0100 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: <20150126113228.GU13123@darkstar.local> References: <20150126104341.GR13123@darkstar.local> <54C62381.10707@redhat.com> <20150126113228.GU13123@darkstar.local> Message-ID: On Mon, Jan 26, 2015 at 12:32 PM, Douglas Campos wrote: > On Mon, Jan 26, 2015 at 12:22:41PM +0100, Erik Jan de Wit wrote: > > > > On 26/01/2015 11:43, Douglas Campos wrote: > > > This migrator tool can be run with plain `java -jar` and deals with all > > > the migrations needed up to `VERSION`, which means we would need only > > > one migrator tool for both 1.0.x and HEAD. > > > > > > Thoughts? Comments? > > great idea, but why not use the maven plugin to execute the liquibase > > migration? > There are several reasons, but the most important is to avoid asking our > users which just deploy a war file into their appserver to clone the > project, wait for maven to download the internet, then finally see the > migration happening. > That is true, not every user of UPS may have maven on his box! > > Also, the maven plugin has less features than the liquibase cli tools. > > -- > qmx > _______________________________________________ > 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/20150126/aee3d3a4/attachment.html From scm.blanc at gmail.com Mon Jan 26 06:39:23 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Mon, 26 Jan 2015 12:39:23 +0100 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: <20150126104341.GR13123@darkstar.local> References: <20150126104341.GR13123@darkstar.local> Message-ID: <3656C60E-FF87-4AF5-9F77-3F83A7FA6F8D@gmail.com> Sounds good ! Let's also make sure we will be able to run this tool on the OS cartridge Envoy? de mon iPhone > Le 26 janv. 2015 ? 11:43, Douglas Campos a ?crit : > > Howdy! > > I've been envisioning a plan for UPS migrations, and would like to get > some feedback from the community, so here it is: > > When there are model changes, it's kinda annoying to generate the sql > migration files. This is one of the reasons Erik Jan de Wit started > working to add liquibase to the project, allowing for seamless > migrations. > > I'd like to build upon Erik's initial work and prepare a `ups-migrator` > distribution: > > ups-migrator-VERSION.zip > `--ups-migrator.jar > `--ups-migrator-postgresql.properties > `--ups-migrator-mysql.properties > `--lib > `-- > `-- > > This migrator tool can be run with plain `java -jar` and deals with all > the migrations needed up to `VERSION`, which means we would need only > one migrator tool for both 1.0.x and HEAD. > > Thoughts? Comments? > > -- > qmx > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Mon Jan 26 07:48:29 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 26 Jan 2015 13:48:29 +0100 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: <3656C60E-FF87-4AF5-9F77-3F83A7FA6F8D@gmail.com> References: <20150126104341.GR13123@darkstar.local> <3656C60E-FF87-4AF5-9F77-3F83A7FA6F8D@gmail.com> Message-ID: On Mon, Jan 26, 2015 at 12:39 PM, S?bastien Blanc wrote: > Sounds good ! > Let's also make sure we will be able to run this tool on the OS cartridge > yeah, I think best is reaching out to Farah on that. Let me create a sub-ticket for Openshift hook > > Envoy? de mon iPhone > > > Le 26 janv. 2015 ? 11:43, Douglas Campos a ?crit : > > > > Howdy! > > > > I've been envisioning a plan for UPS migrations, and would like to get > > some feedback from the community, so here it is: > > > > When there are model changes, it's kinda annoying to generate the sql > > migration files. This is one of the reasons Erik Jan de Wit started > > working to add liquibase to the project, allowing for seamless > > migrations. > > > > I'd like to build upon Erik's initial work and prepare a `ups-migrator` > > distribution: > > > > ups-migrator-VERSION.zip > > `--ups-migrator.jar > > `--ups-migrator-postgresql.properties > > `--ups-migrator-mysql.properties > > `--lib > > `-- > > `-- > > > > This migrator tool can be run with plain `java -jar` and deals with all > > the migrations needed up to `VERSION`, which means we would need only > > one migrator tool for both 1.0.x and HEAD. > > > > Thoughts? Comments? > > > > -- > > qmx > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20150126/187d82f6/attachment.html From cvasilak at gmail.com Mon Jan 26 10:25:32 2015 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 26 Jan 2015 17:25:32 +0200 Subject: [aerogear-dev] Team meeting In-Reply-To: References: Message-ID: fyi, meeting minutes: Ending meeting. Generating minutes. Be patient :) Meeting ended Mon Jan 26 15:23:44 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-01-26-15.00.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-26-15.00.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2015/aerogear.2015-01-26-15.00.log.html > On Jan 25, 2015, at 11:08 AM, Daniel Bevenius wrote: > > Agenda: > http://oksoclap.com/p/aerogear-team-mgt-20150126 > _______________________________________________ > 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/20150126/fe4619e9/attachment.html From supittma at redhat.com Mon Jan 26 10:38:54 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 26 Jan 2015 10:38:54 -0500 Subject: [aerogear-dev] Sync Notes / Early issues Message-ID: <54C65F8E.9090907@redhat.com> Summary (From my POV on Android): Sync Server doesn't use any authentication or ownership tracking. GCM-XMPP bridge needs a lot of love We need to define a different connection lifecycle for GCM. The in memory data store is problematic because clients and servers must be stopped and started atomically We might want to show off syncing different types of documents (i.e. a todo list in addition to Luke's hobbies) Fixing the GCM bridge is probably a couple weeks of work to get it "solid". That will be a good alpha.1/preview to show off. So Last week I put together a demo to try and stretch the legs of the Android Sync Client APIs. It crashes, a lot. Which is a bit to be expected as the code hasn't really be used for, well, anything until now. We will get to that though. Here is the alpha.1 workflow. You log in and you see your docs. You can edit your docs or you can create new ones. In the future I would like to add sharing and collaboration but that's the future. Here's a flow chart for the visual thinkers out there (with real screen caps from the real working app) * https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing To make all of this work I use a RESTful server which tracks a user's username and the documents they "own". The sync server just syncs and serves the document you ask for. It has no authentication and any doc you ask for you get to be an editor on. The client uses the GCM XMPP? bridge I wrote while drunk on the side of a mountain and it shows. The biggest issue is that shadows for documents aren't getting created right sometimes because either 1) the client or server bounced and the data stores are no long synced or 2) the server thinks there are more clients than actually are connected. GCM-XMPP doesn't supply connection/disconnection information like WebSockets will. Instead we just know that some messages we sent a while ago weren't delivered. We need to figure out how to turn this into connection and disconnection information in a way that lets the shadows exist correctly. Another issue that needs to be addressed is using something other than the Luke Skywalker hobbies document. (Or maybe showing off multiple document types in the demo). I'm up for suggestions. Anyway, the principles (diff sync with a restful documentId broker for security) are sound. I think we can buff out some implementation details and have a good alpha/preview/poc release in the few weeks -> 1 month time frame for Android and the sync server. -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. Foot Notes: 1. The sync server has two client connection technologies : WebSockets and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the nasty connection handling code and gives let's Android deal with it. More info here : https://developer.android.com/google/gcm/ccs.html From lholmqui at redhat.com Mon Jan 26 10:43:29 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 26 Jan 2015 10:43:29 -0500 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <54C65F8E.9090907@redhat.com> References: <54C65F8E.9090907@redhat.com> Message-ID: <5C65E8D9-D033-4CC3-9771-7B7A7A89C016@redhat.com> > On Jan 26, 2015, at 10:38 AM, Summers Pittman wrote: > > > Summary (From my POV on Android): > > Sync Server doesn't use any authentication or ownership tracking. > GCM-XMPP bridge needs a lot of love > We need to define a different connection lifecycle for GCM. > The in memory data store is problematic because clients and servers > must be stopped and started atomically > We might want to show off syncing different types of documents (i.e. > a todo list in addition to Luke's hobbies) > Fixing the GCM bridge is probably a couple weeks of work to get it > "solid". That will be a good alpha.1/preview to show off. > > So Last week I put together a demo to try and stretch the legs of the > Android Sync Client APIs. > > It crashes, a lot. Which is a bit to be expected as the code hasn't > really be used for, well, anything until now. We will get to that though. > > Here is the alpha.1 workflow. You log in and you see your docs. You can > edit your docs or you can create new ones. In the future I would like > to add sharing and collaboration but that's the future. Here's a flow > chart for the visual thinkers out there (with real screen caps from the > real working app) > > * > https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing > > To make all of this work I use a RESTful server which tracks a user's > username and the documents they "own". The sync server just syncs and > serves the document you ask for. It has no authentication and any doc > you ask for you get to be an editor on. > > The client uses the GCM XMPP? bridge I wrote while drunk on the side of > a mountain and it shows. The biggest issue is that shadows for > documents aren't getting created right sometimes because either 1) the > client or server bounced and the data stores are no long synced or 2) > the server thinks there are more clients than actually are connected. > GCM-XMPP doesn't supply connection/disconnection information like > WebSockets will. Instead we just know that some messages we sent a > while ago weren't delivered. We need to figure out how to turn this > into connection and disconnection information in a way that lets the > shadows exist correctly. > > Another issue that needs to be addressed is using something other than > the Luke Skywalker hobbies document. (Or maybe showing off multiple > document types in the demo). I'm up for suggestions. i was actually thinking updating the example, to include more ?people?, but this demo might have worn out it?s welcome:) > > Anyway, the principles (diff sync with a restful documentId broker for > security) are sound. I think we can buff out some implementation > details and have a good alpha/preview/poc release in the few weeks -> 1 > month time frame for Android and the sync server. > > -- > Summers Pittman >>> Phone:404 941 4698 >>> Java is my crack. > > > > Foot Notes: > 1. The sync server has two client connection technologies : WebSockets > and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the > nasty connection handling code and gives let's Android deal with it. > More info here : https://developer.android.com/google/gcm/ccs.html > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From qmx at qmx.me Mon Jan 26 11:14:35 2015 From: qmx at qmx.me (Douglas Campos) Date: Mon, 26 Jan 2015 14:14:35 -0200 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: References: <20150126104341.GR13123@darkstar.local> <3656C60E-FF87-4AF5-9F77-3F83A7FA6F8D@gmail.com> Message-ID: <20150126161435.GV13123@darkstar.local> On Mon, Jan 26, 2015 at 01:48:29PM +0100, Matthias Wessendorf wrote: > On Mon, Jan 26, 2015 at 12:39 PM, S?bastien Blanc > wrote: > > > Sounds good ! > > Let's also make sure we will be able to run this tool on the OS cartridge > > > > yeah, I think best is reaching out to Farah on that. Let me create a > sub-ticket for Openshift hook Liquibase migrations are idempotent, so you can safely always run the migrator during deploy for openshift - it'll be a noop in the worst case ;) -- qmx From rhauch at redhat.com Mon Jan 26 11:26:53 2015 From: rhauch at redhat.com (Randall Hauch) Date: Mon, 26 Jan 2015 10:26:53 -0600 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <54C65F8E.9090907@redhat.com> References: <54C65F8E.9090907@redhat.com> Message-ID: <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> >From this and previous threads, it sounds like you?re targeting how multiple users could collaboratively edit the same document. Essentially, this is like Google Docs, though perhaps a bit lighter weight. Am I misunderstanding the scenario? For example, would this kind of data sync be useful when there are millions of shared documents/entities? For example, a Yelp-like app would probably want to have an entity/document for each restaurant or business, where that document contained an aggregation of information about that business. In my mind, these kinds of documents are more akin to JPA entities ? or rather akin to aggregates of related JPA entity objects. Best regards, Randall > On Jan 26, 2015, at 9:38 AM, Summers Pittman wrote: > > > Summary (From my POV on Android): > > Sync Server doesn't use any authentication or ownership tracking. > GCM-XMPP bridge needs a lot of love > We need to define a different connection lifecycle for GCM. > The in memory data store is problematic because clients and servers > must be stopped and started atomically > We might want to show off syncing different types of documents (i.e. > a todo list in addition to Luke's hobbies) > Fixing the GCM bridge is probably a couple weeks of work to get it > "solid". That will be a good alpha.1/preview to show off. > > So Last week I put together a demo to try and stretch the legs of the > Android Sync Client APIs. > > It crashes, a lot. Which is a bit to be expected as the code hasn't > really be used for, well, anything until now. We will get to that though. > > Here is the alpha.1 workflow. You log in and you see your docs. You can > edit your docs or you can create new ones. In the future I would like > to add sharing and collaboration but that's the future. Here's a flow > chart for the visual thinkers out there (with real screen caps from the > real working app) > > * > https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing > > To make all of this work I use a RESTful server which tracks a user's > username and the documents they "own". The sync server just syncs and > serves the document you ask for. It has no authentication and any doc > you ask for you get to be an editor on. > > The client uses the GCM XMPP? bridge I wrote while drunk on the side of > a mountain and it shows. The biggest issue is that shadows for > documents aren't getting created right sometimes because either 1) the > client or server bounced and the data stores are no long synced or 2) > the server thinks there are more clients than actually are connected. > GCM-XMPP doesn't supply connection/disconnection information like > WebSockets will. Instead we just know that some messages we sent a > while ago weren't delivered. We need to figure out how to turn this > into connection and disconnection information in a way that lets the > shadows exist correctly. > > Another issue that needs to be addressed is using something other than > the Luke Skywalker hobbies document. (Or maybe showing off multiple > document types in the demo). I'm up for suggestions. > > Anyway, the principles (diff sync with a restful documentId broker for > security) are sound. I think we can buff out some implementation > details and have a good alpha/preview/poc release in the few weeks -> 1 > month time frame for Android and the sync server. > > -- > Summers Pittman >>> Phone:404 941 4698 >>> Java is my crack. > > > > Foot Notes: > 1. The sync server has two client connection technologies : WebSockets > and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the > nasty connection handling code and gives let's Android deal with it. > More info here : https://developer.android.com/google/gcm/ccs.html > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From supittma at redhat.com Mon Jan 26 11:31:53 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 26 Jan 2015 11:31:53 -0500 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> References: <54C65F8E.9090907@redhat.com> <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> Message-ID: <54C66BF9.3050304@redhat.com> On 01/26/2015 11:26 AM, Randall Hauch wrote: > From this and previous threads, it sounds like you?re targeting how multiple users could collaboratively edit the same document. Essentially, this is like Google Docs, though perhaps a bit lighter weight. Am I misunderstanding the scenario? Document is a generic term. It is a wrapper around a JSON serializable object. > > For example, would this kind of data sync be useful when there are millions of shared documents/entities? For example, a Yelp-like app would probably want to have an entity/document for each restaurant or business, where that document contained an aggregation of information about that business. In my mind, these kinds of documents are more akin to JPA entities ? or rather akin to aggregates of related JPA entity objects. Yes ish. Right now the sync server is very young, but we can model the data as a single document and have the apps display views into it and make edits appropriately. The trick will be making sure that the serialization is always the same (IE two clients aren't constantly updating because they serialize data in different orders) > > Best regards, > > Randall > > >> On Jan 26, 2015, at 9:38 AM, Summers Pittman wrote: >> >> >> Summary (From my POV on Android): >> >> Sync Server doesn't use any authentication or ownership tracking. >> GCM-XMPP bridge needs a lot of love >> We need to define a different connection lifecycle for GCM. >> The in memory data store is problematic because clients and servers >> must be stopped and started atomically >> We might want to show off syncing different types of documents (i.e. >> a todo list in addition to Luke's hobbies) >> Fixing the GCM bridge is probably a couple weeks of work to get it >> "solid". That will be a good alpha.1/preview to show off. >> >> So Last week I put together a demo to try and stretch the legs of the >> Android Sync Client APIs. >> >> It crashes, a lot. Which is a bit to be expected as the code hasn't >> really be used for, well, anything until now. We will get to that though. >> >> Here is the alpha.1 workflow. You log in and you see your docs. You can >> edit your docs or you can create new ones. In the future I would like >> to add sharing and collaboration but that's the future. Here's a flow >> chart for the visual thinkers out there (with real screen caps from the >> real working app) >> >> * >> https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing >> >> To make all of this work I use a RESTful server which tracks a user's >> username and the documents they "own". The sync server just syncs and >> serves the document you ask for. It has no authentication and any doc >> you ask for you get to be an editor on. >> >> The client uses the GCM XMPP? bridge I wrote while drunk on the side of >> a mountain and it shows. The biggest issue is that shadows for >> documents aren't getting created right sometimes because either 1) the >> client or server bounced and the data stores are no long synced or 2) >> the server thinks there are more clients than actually are connected. >> GCM-XMPP doesn't supply connection/disconnection information like >> WebSockets will. Instead we just know that some messages we sent a >> while ago weren't delivered. We need to figure out how to turn this >> into connection and disconnection information in a way that lets the >> shadows exist correctly. >> >> Another issue that needs to be addressed is using something other than >> the Luke Skywalker hobbies document. (Or maybe showing off multiple >> document types in the demo). I'm up for suggestions. >> >> Anyway, the principles (diff sync with a restful documentId broker for >> security) are sound. I think we can buff out some implementation >> details and have a good alpha/preview/poc release in the few weeks -> 1 >> month time frame for Android and the sync server. >> >> -- >> Summers Pittman >>>> Phone:404 941 4698 >>>> Java is my crack. >> >> >> Foot Notes: >> 1. The sync server has two client connection technologies : WebSockets >> and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the >> nasty connection handling code and gives let's Android deal with it. >> More info here : https://developer.android.com/google/gcm/ccs.html >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From lholmqui at redhat.com Mon Jan 26 11:37:55 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 26 Jan 2015 11:37:55 -0500 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <54C66BF9.3050304@redhat.com> References: <54C65F8E.9090907@redhat.com> <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> <54C66BF9.3050304@redhat.com> Message-ID: <5BF00158-B30E-416C-A75F-8EA34312903F@redhat.com> Perhaps we have already brought this up, but what are we(our sync stuff) trying to be. Are we trying to be Dropbox/google docs/etc?.. or something else(what that is i?m not sure). What are our real use cases here? > On Jan 26, 2015, at 11:31 AM, Summers Pittman wrote: > > On 01/26/2015 11:26 AM, Randall Hauch wrote: >> From this and previous threads, it sounds like you?re targeting how multiple users could collaboratively edit the same document. Essentially, this is like Google Docs, though perhaps a bit lighter weight. Am I misunderstanding the scenario? > Document is a generic term. It is a wrapper around a JSON serializable > object. >> >> For example, would this kind of data sync be useful when there are millions of shared documents/entities? For example, a Yelp-like app would probably want to have an entity/document for each restaurant or business, where that document contained an aggregation of information about that business. In my mind, these kinds of documents are more akin to JPA entities ? or rather akin to aggregates of related JPA entity objects. > Yes ish. Right now the sync server is very young, but we can model the > data as a single document and have the apps display views into it and > make edits appropriately. The trick will be making sure that the > serialization is always the same (IE two clients aren't constantly > updating because they serialize data in different orders) >> >> Best regards, >> >> Randall >> >> >>> On Jan 26, 2015, at 9:38 AM, Summers Pittman wrote: >>> >>> >>> Summary (From my POV on Android): >>> >>> Sync Server doesn't use any authentication or ownership tracking. >>> GCM-XMPP bridge needs a lot of love >>> We need to define a different connection lifecycle for GCM. >>> The in memory data store is problematic because clients and servers >>> must be stopped and started atomically >>> We might want to show off syncing different types of documents (i.e. >>> a todo list in addition to Luke's hobbies) >>> Fixing the GCM bridge is probably a couple weeks of work to get it >>> "solid". That will be a good alpha.1/preview to show off. >>> >>> So Last week I put together a demo to try and stretch the legs of the >>> Android Sync Client APIs. >>> >>> It crashes, a lot. Which is a bit to be expected as the code hasn't >>> really be used for, well, anything until now. We will get to that though. >>> >>> Here is the alpha.1 workflow. You log in and you see your docs. You can >>> edit your docs or you can create new ones. In the future I would like >>> to add sharing and collaboration but that's the future. Here's a flow >>> chart for the visual thinkers out there (with real screen caps from the >>> real working app) >>> >>> * >>> https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing >>> >>> To make all of this work I use a RESTful server which tracks a user's >>> username and the documents they "own". The sync server just syncs and >>> serves the document you ask for. It has no authentication and any doc >>> you ask for you get to be an editor on. >>> >>> The client uses the GCM XMPP? bridge I wrote while drunk on the side of >>> a mountain and it shows. The biggest issue is that shadows for >>> documents aren't getting created right sometimes because either 1) the >>> client or server bounced and the data stores are no long synced or 2) >>> the server thinks there are more clients than actually are connected. >>> GCM-XMPP doesn't supply connection/disconnection information like >>> WebSockets will. Instead we just know that some messages we sent a >>> while ago weren't delivered. We need to figure out how to turn this >>> into connection and disconnection information in a way that lets the >>> shadows exist correctly. >>> >>> Another issue that needs to be addressed is using something other than >>> the Luke Skywalker hobbies document. (Or maybe showing off multiple >>> document types in the demo). I'm up for suggestions. >>> >>> Anyway, the principles (diff sync with a restful documentId broker for >>> security) are sound. I think we can buff out some implementation >>> details and have a good alpha/preview/poc release in the few weeks -> 1 >>> month time frame for Android and the sync server. >>> >>> -- >>> Summers Pittman >>>>> Phone:404 941 4698 >>>>> Java is my crack. >>> >>> >>> Foot Notes: >>> 1. The sync server has two client connection technologies : WebSockets >>> and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the >>> nasty connection handling code and gives let's Android deal with it. >>> More info here : https://developer.android.com/google/gcm/ccs.html >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman >>> Phone:404 941 4698 >>> Java is my crack. > > _______________________________________________ > 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/20150126/75e5c58d/attachment-0001.html From supittma at redhat.com Mon Jan 26 11:49:53 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 26 Jan 2015 11:49:53 -0500 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <5BF00158-B30E-416C-A75F-8EA34312903F@redhat.com> References: <54C65F8E.9090907@redhat.com> <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> <54C66BF9.3050304@redhat.com> <5BF00158-B30E-416C-A75F-8EA34312903F@redhat.com> Message-ID: <54C67031.8040207@redhat.com> On 01/26/2015 11:37 AM, Lucas Holmquist wrote: > Perhaps we have already brought this up, but what are we(our sync > stuff) trying to be. > > Are we trying to be Dropbox/google docs/etc?.. or something else(what > that is i?m not sure). > > What are our real use cases here? Here are some simple ones that I want the sync server for * A Conference app user synchronizes a personalized schedule among his devices * A Users preferences are restored / synchronized across his devices (filtered by some kind of profile. IE phone preference, tablet preferences, desktop preferences) * A list of content is continually updated (think Facebook feed) So this gives us two usage patterns 1. A single user-document synchronized across devices 2. A single document synchronized across all user*devices. I don't think anyone has thought of some truly collaborative things like Google docs where you have multiple users on multiple devices editing multiple documents all with different permission tuples. Many things can be fit in these two scenarios however. In the Dropbox use case you mention the "document" is the users files, metadata, and their location. The actual data will probably be hosted some place else. > > >> On Jan 26, 2015, at 11:31 AM, Summers Pittman > > wrote: >> >> On 01/26/2015 11:26 AM, Randall Hauch wrote: >>> From this and previous threads, it sounds like you?re targeting how >>> multiple users could collaboratively edit the same document. >>> Essentially, this is like Google Docs, though perhaps a bit lighter >>> weight. Am I misunderstanding the scenario? >> Document is a generic term. It is a wrapper around a JSON serializable >> object. >>> >>> For example, would this kind of data sync be useful when there are >>> millions of shared documents/entities? For example, a Yelp-like app >>> would probably want to have an entity/document for each restaurant >>> or business, where that document contained an aggregation of >>> information about that business. In my mind, these kinds of >>> documents are more akin to JPA entities ? or rather akin to >>> aggregates of related JPA entity objects. >> Yes ish. Right now the sync server is very young, but we can model the >> data as a single document and have the apps display views into it and >> make edits appropriately. The trick will be making sure that the >> serialization is always the same (IE two clients aren't constantly >> updating because they serialize data in different orders) >>> >>> Best regards, >>> >>> Randall >>> >>> >>>> On Jan 26, 2015, at 9:38 AM, Summers Pittman >>> > wrote: >>>> >>>> >>>> Summary (From my POV on Android): >>>> >>>> Sync Server doesn't use any authentication or ownership tracking. >>>> GCM-XMPP bridge needs a lot of love >>>> We need to define a different connection lifecycle for GCM. >>>> The in memory data store is problematic because clients and servers >>>> must be stopped and started atomically >>>> We might want to show off syncing different types of documents (i.e. >>>> a todo list in addition to Luke's hobbies) >>>> Fixing the GCM bridge is probably a couple weeks of work to get it >>>> "solid". That will be a good alpha.1/preview to show off. >>>> >>>> So Last week I put together a demo to try and stretch the legs of the >>>> Android Sync Client APIs. >>>> >>>> It crashes, a lot. Which is a bit to be expected as the code hasn't >>>> really be used for, well, anything until now. We will get to that >>>> though. >>>> >>>> Here is the alpha.1 workflow. You log in and you see your docs. >>>> You can >>>> edit your docs or you can create new ones. In the future I would like >>>> to add sharing and collaboration but that's the future. Here's a flow >>>> chart for the visual thinkers out there (with real screen caps from the >>>> real working app) >>>> >>>> * >>>> https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing >>>> >>>> To make all of this work I use a RESTful server which tracks a user's >>>> username and the documents they "own". The sync server just syncs and >>>> serves the document you ask for. It has no authentication and any doc >>>> you ask for you get to be an editor on. >>>> >>>> The client uses the GCM XMPP? bridge I wrote while drunk on the side of >>>> a mountain and it shows. The biggest issue is that shadows for >>>> documents aren't getting created right sometimes because either 1) the >>>> client or server bounced and the data stores are no long synced or 2) >>>> the server thinks there are more clients than actually are connected. >>>> GCM-XMPP doesn't supply connection/disconnection information like >>>> WebSockets will. Instead we just know that some messages we sent a >>>> while ago weren't delivered. We need to figure out how to turn this >>>> into connection and disconnection information in a way that lets the >>>> shadows exist correctly. >>>> >>>> Another issue that needs to be addressed is using something other than >>>> the Luke Skywalker hobbies document. (Or maybe showing off multiple >>>> document types in the demo). I'm up for suggestions. >>>> >>>> Anyway, the principles (diff sync with a restful documentId broker for >>>> security) are sound. I think we can buff out some implementation >>>> details and have a good alpha/preview/poc release in the few weeks -> 1 >>>> month time frame for Android and the sync server. >>>> >>>> -- >>>> Summers Pittman >>>>>> Phone:404 941 4698 >>>>>> Java is my crack. >>>> >>>> >>>> Foot Notes: >>>> 1. The sync server has two client connection technologies : WebSockets >>>> and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the >>>> nasty connection handling code and gives let's Android deal with it. >>>> More info here : https://developer.android.com/google/gcm/ccs.html >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> -- >> Summers Pittman >>>> Phone:404 941 4698 >>>> Java is my crack. >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150126/3ceedf80/attachment-0001.html From rhauch at redhat.com Mon Jan 26 12:00:55 2015 From: rhauch at redhat.com (Randall Hauch) Date: Mon, 26 Jan 2015 11:00:55 -0600 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <54C66BF9.3050304@redhat.com> References: <54C65F8E.9090907@redhat.com> <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> <54C66BF9.3050304@redhat.com> Message-ID: On a related note, I recently finished a prototype for a backend storage solution that stores JSON documents (entities) in collections and zones, and has a number of other features. There were several goals, including several that were just focused on backend technologies (e.g., fault tolerance, scalability, data safety, performance, what can be done without transactions, etc.). With limited time, I also wanted to focus on the more unknown and higher risk stuff, so I deferred several other far more straightforward things like wrapping with a server (e.g., Undertow, a LiveOak subsystem, etc.) and using AeroGear?s UPS. One thing I did look into is what kind of interchange might work best for mobile apps reading and updating data, and how mobile apps can synchronize their local state (e.g., data sync). I?m not sure what (if anything) are the next steps for this, but all of it is at https://github.com/rhauch/debezium . I?d be interested in getting feedback on the concept, the approach, the documentation, etc., so if you?re interested in learning more perhaps the best place to start it at the wiki: https://github.com/rhauch/debezium/wiki > On Jan 26, 2015, at 10:31 AM, Summers Pittman wrote: > > On 01/26/2015 11:26 AM, Randall Hauch wrote: >> From this and previous threads, it sounds like you?re targeting how multiple users could collaboratively edit the same document. Essentially, this is like Google Docs, though perhaps a bit lighter weight. Am I misunderstanding the scenario? > Document is a generic term. It is a wrapper around a JSON serializable object. >> >> For example, would this kind of data sync be useful when there are millions of shared documents/entities? For example, a Yelp-like app would probably want to have an entity/document for each restaurant or business, where that document contained an aggregation of information about that business. In my mind, these kinds of documents are more akin to JPA entities ? or rather akin to aggregates of related JPA entity objects. > Yes ish. Right now the sync server is very young, but we can model the data as a single document and have the apps display views into it and make edits appropriately. The trick will be making sure that the serialization is always the same (IE two clients aren't constantly updating because they serialize data in different orders) >> >> Best regards, >> >> Randall >> >> >>> On Jan 26, 2015, at 9:38 AM, Summers Pittman wrote: >>> >>> >>> Summary (From my POV on Android): >>> >>> Sync Server doesn't use any authentication or ownership tracking. >>> GCM-XMPP bridge needs a lot of love >>> We need to define a different connection lifecycle for GCM. >>> The in memory data store is problematic because clients and servers >>> must be stopped and started atomically >>> We might want to show off syncing different types of documents (i.e. >>> a todo list in addition to Luke's hobbies) >>> Fixing the GCM bridge is probably a couple weeks of work to get it >>> "solid". That will be a good alpha.1/preview to show off. >>> >>> So Last week I put together a demo to try and stretch the legs of the >>> Android Sync Client APIs. >>> >>> It crashes, a lot. Which is a bit to be expected as the code hasn't >>> really be used for, well, anything until now. We will get to that though. >>> >>> Here is the alpha.1 workflow. You log in and you see your docs. You can >>> edit your docs or you can create new ones. In the future I would like >>> to add sharing and collaboration but that's the future. Here's a flow >>> chart for the visual thinkers out there (with real screen caps from the >>> real working app) >>> >>> * >>> https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing >>> >>> To make all of this work I use a RESTful server which tracks a user's >>> username and the documents they "own". The sync server just syncs and >>> serves the document you ask for. It has no authentication and any doc >>> you ask for you get to be an editor on. >>> >>> The client uses the GCM XMPP? bridge I wrote while drunk on the side of >>> a mountain and it shows. The biggest issue is that shadows for >>> documents aren't getting created right sometimes because either 1) the >>> client or server bounced and the data stores are no long synced or 2) >>> the server thinks there are more clients than actually are connected. >>> GCM-XMPP doesn't supply connection/disconnection information like >>> WebSockets will. Instead we just know that some messages we sent a >>> while ago weren't delivered. We need to figure out how to turn this >>> into connection and disconnection information in a way that lets the >>> shadows exist correctly. >>> >>> Another issue that needs to be addressed is using something other than >>> the Luke Skywalker hobbies document. (Or maybe showing off multiple >>> document types in the demo). I'm up for suggestions. >>> >>> Anyway, the principles (diff sync with a restful documentId broker for >>> security) are sound. I think we can buff out some implementation >>> details and have a good alpha/preview/poc release in the few weeks -> 1 >>> month time frame for Android and the sync server. >>> >>> -- >>> Summers Pittman >>>>> Phone:404 941 4698 >>>>> Java is my crack. >>> >>> >>> Foot Notes: >>> 1. The sync server has two client connection technologies : WebSockets >>> and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the >>> nasty connection handling code and gives let's Android deal with it. >>> More info here : https://developer.android.com/google/gcm/ccs.html >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman >>> Phone:404 941 4698 >>> Java is my crack. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150126/34be749e/attachment.html From daniel at passos.me Mon Jan 26 14:06:04 2015 From: daniel at passos.me (Daniel Passos) Date: Mon, 26 Jan 2015 17:06:04 -0200 Subject: [aerogear-dev] [RFC] UPS DB Migration Strategy In-Reply-To: <20150126161435.GV13123@darkstar.local> References: <20150126104341.GR13123@darkstar.local> <3656C60E-FF87-4AF5-9F77-3F83A7FA6F8D@gmail.com> <20150126161435.GV13123@darkstar.local> Message-ID: Very nice idea! -- Passos On Mon, Jan 26, 2015 at 2:14 PM, Douglas Campos wrote: > On Mon, Jan 26, 2015 at 01:48:29PM +0100, Matthias Wessendorf wrote: > > On Mon, Jan 26, 2015 at 12:39 PM, S?bastien Blanc > > wrote: > > > > > Sounds good ! > > > Let's also make sure we will be able to run this tool on the OS > cartridge > > > > > > > yeah, I think best is reaching out to Farah on that. Let me create a > > sub-ticket for Openshift hook > Liquibase migrations are idempotent, so you can safely always run the > migrator during deploy for openshift - it'll be a noop in the worst case > ;) > > > -- > qmx > _______________________________________________ > 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/20150126/aaa8acac/attachment.html From lholmqui at redhat.com Mon Jan 26 14:36:49 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 26 Jan 2015 14:36:49 -0500 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <54C67031.8040207@redhat.com> References: <54C65F8E.9090907@redhat.com> <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> <54C66BF9.3050304@redhat.com> <5BF00158-B30E-416C-A75F-8EA34312903F@redhat.com> <54C67031.8040207@redhat.com> Message-ID: > On Jan 26, 2015, at 11:49 AM, Summers Pittman wrote: > > On 01/26/2015 11:37 AM, Lucas Holmquist wrote: >> Perhaps we have already brought this up, but what are we(our sync stuff) trying to be. >> >> Are we trying to be Dropbox/google docs/etc?.. or something else(what that is i?m not sure). >> >> What are our real use cases here? > Here are some simple ones that I want the sync server for > * A Conference app user synchronizes a personalized schedule among his devices i sort of like this one. it is somewhat a real-time thing. I guess the real question around what our Sync Stuff wants to be when it gets older, is does it want to be Real-Time? which i think we?ve probably agreed on more than once > * A Users preferences are restored / synchronized across his devices (filtered by some kind of profile. IE phone preference, tablet preferences, desktop preferences) > * A list of content is continually updated (think Facebook feed) > > So this gives us two usage patterns > > 1. A single user-document synchronized across devices > 2. A single document synchronized across all user*devices. > > I don't think anyone has thought of some truly collaborative things like Google docs where you have multiple users on multiple devices editing multiple documents all with different permission tuples. > > Many things can be fit in these two scenarios however. In the Dropbox use case you mention the "document" is the users files, metadata, and their location. The actual data will probably be hosted some place else. > >> >> >>> On Jan 26, 2015, at 11:31 AM, Summers Pittman > wrote: >>> >>> On 01/26/2015 11:26 AM, Randall Hauch wrote: >>>> From this and previous threads, it sounds like you?re targeting how multiple users could collaboratively edit the same document. Essentially, this is like Google Docs, though perhaps a bit lighter weight. Am I misunderstanding the scenario? >>> Document is a generic term. It is a wrapper around a JSON serializable >>> object. >>>> >>>> For example, would this kind of data sync be useful when there are millions of shared documents/entities? For example, a Yelp-like app would probably want to have an entity/document for each restaurant or business, where that document contained an aggregation of information about that business. In my mind, these kinds of documents are more akin to JPA entities ? or rather akin to aggregates of related JPA entity objects. >>> Yes ish. Right now the sync server is very young, but we can model the >>> data as a single document and have the apps display views into it and >>> make edits appropriately. The trick will be making sure that the >>> serialization is always the same (IE two clients aren't constantly >>> updating because they serialize data in different orders) >>>> >>>> Best regards, >>>> >>>> Randall >>>> >>>> >>>>> On Jan 26, 2015, at 9:38 AM, Summers Pittman > wrote: >>>>> >>>>> >>>>> Summary (From my POV on Android): >>>>> >>>>> Sync Server doesn't use any authentication or ownership tracking. >>>>> GCM-XMPP bridge needs a lot of love >>>>> We need to define a different connection lifecycle for GCM. >>>>> The in memory data store is problematic because clients and servers >>>>> must be stopped and started atomically >>>>> We might want to show off syncing different types of documents (i.e. >>>>> a todo list in addition to Luke's hobbies) >>>>> Fixing the GCM bridge is probably a couple weeks of work to get it >>>>> "solid". That will be a good alpha.1/preview to show off. >>>>> >>>>> So Last week I put together a demo to try and stretch the legs of the >>>>> Android Sync Client APIs. >>>>> >>>>> It crashes, a lot. Which is a bit to be expected as the code hasn't >>>>> really be used for, well, anything until now. We will get to that though. >>>>> >>>>> Here is the alpha.1 workflow. You log in and you see your docs. You can >>>>> edit your docs or you can create new ones. In the future I would like >>>>> to add sharing and collaboration but that's the future. Here's a flow >>>>> chart for the visual thinkers out there (with real screen caps from the >>>>> real working app) >>>>> >>>>> * >>>>> https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing >>>>> >>>>> To make all of this work I use a RESTful server which tracks a user's >>>>> username and the documents they "own". The sync server just syncs and >>>>> serves the document you ask for. It has no authentication and any doc >>>>> you ask for you get to be an editor on. >>>>> >>>>> The client uses the GCM XMPP? bridge I wrote while drunk on the side of >>>>> a mountain and it shows. The biggest issue is that shadows for >>>>> documents aren't getting created right sometimes because either 1) the >>>>> client or server bounced and the data stores are no long synced or 2) >>>>> the server thinks there are more clients than actually are connected. >>>>> GCM-XMPP doesn't supply connection/disconnection information like >>>>> WebSockets will. Instead we just know that some messages we sent a >>>>> while ago weren't delivered. We need to figure out how to turn this >>>>> into connection and disconnection information in a way that lets the >>>>> shadows exist correctly. >>>>> >>>>> Another issue that needs to be addressed is using something other than >>>>> the Luke Skywalker hobbies document. (Or maybe showing off multiple >>>>> document types in the demo). I'm up for suggestions. >>>>> >>>>> Anyway, the principles (diff sync with a restful documentId broker for >>>>> security) are sound. I think we can buff out some implementation >>>>> details and have a good alpha/preview/poc release in the few weeks -> 1 >>>>> month time frame for Android and the sync server. >>>>> >>>>> -- >>>>> Summers Pittman >>>>>>> Phone:404 941 4698 >>>>>>> Java is my crack. >>>>> >>>>> >>>>> Foot Notes: >>>>> 1. The sync server has two client connection technologies : WebSockets >>>>> and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the >>>>> nasty connection handling code and gives let's Android deal with it. >>>>> More info here : https://developer.android.com/google/gcm/ccs.html >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> -- >>> Summers Pittman >>>>> Phone:404 941 4698 >>>>> Java is my crack. >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > _______________________________________________ > 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/20150126/6c632de1/attachment-0001.html From lholmqui at redhat.com Mon Jan 26 14:50:04 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 26 Jan 2015 14:50:04 -0500 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: References: <54C65F8E.9090907@redhat.com> <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> <54C66BF9.3050304@redhat.com> <5BF00158-B30E-416C-A75F-8EA34312903F@redhat.com> <54C67031.8040207@redhat.com> Message-ID: <1945D66C-E048-4653-9C4D-545C4E8A8C38@redhat.com> > On Jan 26, 2015, at 2:36 PM, Lucas Holmquist wrote: > >> >> On Jan 26, 2015, at 11:49 AM, Summers Pittman > wrote: >> >> On 01/26/2015 11:37 AM, Lucas Holmquist wrote: >>> Perhaps we have already brought this up, but what are we(our sync stuff) trying to be. >>> >>> Are we trying to be Dropbox/google docs/etc?.. or something else(what that is i?m not sure). >>> >>> What are our real use cases here? >> Here are some simple ones that I want the sync server for >> * A Conference app user synchronizes a personalized schedule among his devices > > i sort of like this one. it is somewhat a real-time thing. > > I guess the real question around what our Sync Stuff wants to be when it gets older, is does it want to be Real-Time? which i think we?ve probably agreed on more than once > >> * A Users preferences are restored / synchronized across his devices (filtered by some kind of profile. IE phone preference, tablet preferences, desktop preferences) >> * A list of content is continually updated (think Facebook feed) >> >> So this gives us two usage patterns >> >> 1. A single user-document synchronized across devices >> 2. A single document synchronized across all user*devices. >> didn?t we also have an example of a building inspectors app, where people are entering information and then they go offline and come back and things sync up. I guess that is more for offline >> I don't think anyone has thought of some truly collaborative things like Google docs where you have multiple users on multiple devices editing multiple documents all with different permission tuples. >> >> Many things can be fit in these two scenarios however. In the Dropbox use case you mention the "document" is the users files, metadata, and their location. The actual data will probably be hosted some place else. >> >>> >>> >>>> On Jan 26, 2015, at 11:31 AM, Summers Pittman > wrote: >>>> >>>> On 01/26/2015 11:26 AM, Randall Hauch wrote: >>>>> From this and previous threads, it sounds like you?re targeting how multiple users could collaboratively edit the same document. Essentially, this is like Google Docs, though perhaps a bit lighter weight. Am I misunderstanding the scenario? >>>> Document is a generic term. It is a wrapper around a JSON serializable >>>> object. >>>>> >>>>> For example, would this kind of data sync be useful when there are millions of shared documents/entities? For example, a Yelp-like app would probably want to have an entity/document for each restaurant or business, where that document contained an aggregation of information about that business. In my mind, these kinds of documents are more akin to JPA entities ? or rather akin to aggregates of related JPA entity objects. >>>> Yes ish. Right now the sync server is very young, but we can model the >>>> data as a single document and have the apps display views into it and >>>> make edits appropriately. The trick will be making sure that the >>>> serialization is always the same (IE two clients aren't constantly >>>> updating because they serialize data in different orders) >>>>> >>>>> Best regards, >>>>> >>>>> Randall >>>>> >>>>> >>>>>> On Jan 26, 2015, at 9:38 AM, Summers Pittman > wrote: >>>>>> >>>>>> >>>>>> Summary (From my POV on Android): >>>>>> >>>>>> Sync Server doesn't use any authentication or ownership tracking. >>>>>> GCM-XMPP bridge needs a lot of love >>>>>> We need to define a different connection lifecycle for GCM. >>>>>> The in memory data store is problematic because clients and servers >>>>>> must be stopped and started atomically >>>>>> We might want to show off syncing different types of documents (i.e. >>>>>> a todo list in addition to Luke's hobbies) >>>>>> Fixing the GCM bridge is probably a couple weeks of work to get it >>>>>> "solid". That will be a good alpha.1/preview to show off. >>>>>> >>>>>> So Last week I put together a demo to try and stretch the legs of the >>>>>> Android Sync Client APIs. >>>>>> >>>>>> It crashes, a lot. Which is a bit to be expected as the code hasn't >>>>>> really be used for, well, anything until now. We will get to that though. >>>>>> >>>>>> Here is the alpha.1 workflow. You log in and you see your docs. You can >>>>>> edit your docs or you can create new ones. In the future I would like >>>>>> to add sharing and collaboration but that's the future. Here's a flow >>>>>> chart for the visual thinkers out there (with real screen caps from the >>>>>> real working app) >>>>>> >>>>>> * >>>>>> https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing >>>>>> >>>>>> To make all of this work I use a RESTful server which tracks a user's >>>>>> username and the documents they "own". The sync server just syncs and >>>>>> serves the document you ask for. It has no authentication and any doc >>>>>> you ask for you get to be an editor on. >>>>>> >>>>>> The client uses the GCM XMPP? bridge I wrote while drunk on the side of >>>>>> a mountain and it shows. The biggest issue is that shadows for >>>>>> documents aren't getting created right sometimes because either 1) the >>>>>> client or server bounced and the data stores are no long synced or 2) >>>>>> the server thinks there are more clients than actually are connected. >>>>>> GCM-XMPP doesn't supply connection/disconnection information like >>>>>> WebSockets will. Instead we just know that some messages we sent a >>>>>> while ago weren't delivered. We need to figure out how to turn this >>>>>> into connection and disconnection information in a way that lets the >>>>>> shadows exist correctly. >>>>>> >>>>>> Another issue that needs to be addressed is using something other than >>>>>> the Luke Skywalker hobbies document. (Or maybe showing off multiple >>>>>> document types in the demo). I'm up for suggestions. >>>>>> >>>>>> Anyway, the principles (diff sync with a restful documentId broker for >>>>>> security) are sound. I think we can buff out some implementation >>>>>> details and have a good alpha/preview/poc release in the few weeks -> 1 >>>>>> month time frame for Android and the sync server. >>>>>> >>>>>> -- >>>>>> Summers Pittman >>>>>>>> Phone:404 941 4698 >>>>>>>> Java is my crack. >>>>>> >>>>>> >>>>>> Foot Notes: >>>>>> 1. The sync server has two client connection technologies : WebSockets >>>>>> and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the >>>>>> nasty connection handling code and gives let's Android deal with it. >>>>>> More info here : https://developer.android.com/google/gcm/ccs.html >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> -- >>>> Summers Pittman >>>>>> Phone:404 941 4698 >>>>>> Java is my crack. >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> -- >> Summers Pittman >> >>Phone:404 941 4698 >> >>Java is my crack. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150126/0f661399/attachment-0001.html From matzew at apache.org Tue Jan 27 04:46:24 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 27 Jan 2015 10:46:24 +0100 Subject: [aerogear-dev] AeroGear-Parent: 0.2.9.1 release In-Reply-To: References: Message-ID: ok, I have clicked the button. On Fri, Jan 23, 2015 at 8:25 PM, Matthias Wessendorf wrote: > Hi, > > to fix a Keycloak bug on EAP ([1]), we need to pick up their new 1.0.5 > release, which they ran just for us. > > Now, this release needs to be consumed on our 1.0.x series to get the > 1.0.3 out! Since 1.0.x is using a slightly older parent (0.2.9) I created a > new TAG 0.2.9.1 containing only the new KC version, basically to limit > potential risks (and our latest parent is already on the _newer_ KC 1.1.x > series). > > So, I have prepared the release for this, and did stage the 0.2.9.1 (which > is exactly like 0.2.9, just has the new KC version). The staging repo is > here: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4696/ > > Please test with the 1.0.x branch and let me know how that went. I plan to > release the bits to maven central on Tuesday. > > Greetings, > Matthias > > [1] https://issues.jboss.org/browse/KEYCLOAK-977 > > -- > 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/20150127/6f0ecf66/attachment.html From lukas.fryc at gmail.com Tue Jan 27 05:19:35 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 27 Jan 2015 11:19:35 +0100 Subject: [aerogear-dev] Project Info to all projects Message-ID: Hey guys, me and passos brainstormed yesterday about the project info in the README files as it would be nice to unify them across all repositories (discussed elsewhere) and mainly allow people navigate from code repositories directly to locations where they can find more help, etc. As a result, we both liked: 1. brief Project Info in the header 2. more verbose Documentation / Development / Questions? / Found a bug? section in the footer Example for Android Core: https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b Let me know what you think. If I don't get any -1, I will send pull requests with the updates in all aerogear repositories at the end of this week. Cheers! ~ Lukas P.S.: aerogear-users has just a ordinary mailman archive while aerogear-dev uses nabble, which is far better for navigation / search, etc. (the request to add that feature to aerogear-users is tracked in https://issues.jboss.org/browse/AEROGEAR-1590 ) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150127/01e3c188/attachment.html From scm.blanc at gmail.com Tue Jan 27 05:22:31 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 27 Jan 2015 11:22:31 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: Message-ID: sounds good ! On Tue, Jan 27, 2015 at 11:19 AM, Luk?? Fry? wrote: > Hey guys, > > me and passos brainstormed yesterday about the project info in the README > files > > as it would be nice to unify them across all repositories (discussed > elsewhere) and mainly allow people navigate from code repositories directly > to locations where they can find more help, etc. > > > As a result, we both liked: > > 1. brief Project Info in the header > 2. more verbose Documentation / Development / Questions? / Found a bug? > section in the footer > > Example for Android Core: > https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b > > > Let me know what you think. > > If I don't get any -1, I will send pull requests with the updates in all > aerogear repositories at the end of this week. > > > Cheers! > > ~ Lukas > > > P.S.: aerogear-users has just a ordinary mailman archive while > aerogear-dev uses nabble, which is far better for navigation / search, etc. > (the request to add that feature to aerogear-users is tracked in > https://issues.jboss.org/browse/AEROGEAR-1590 ) > > _______________________________________________ > 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/20150127/c0b40acb/attachment.html From daniel.bevenius at gmail.com Tue Jan 27 05:24:26 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Tue, 27 Jan 2015 11:24:26 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: Message-ID: +1 That looks nice On 27 January 2015 at 11:22, Sebastien Blanc wrote: > sounds good ! > > On Tue, Jan 27, 2015 at 11:19 AM, Luk?? Fry? wrote: > >> Hey guys, >> >> me and passos brainstormed yesterday about the project info in the README >> files >> >> as it would be nice to unify them across all repositories (discussed >> elsewhere) and mainly allow people navigate from code repositories directly >> to locations where they can find more help, etc. >> >> >> As a result, we both liked: >> >> 1. brief Project Info in the header >> 2. more verbose Documentation / Development / Questions? / Found a bug? >> section in the footer >> >> Example for Android Core: >> https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b >> >> >> Let me know what you think. >> >> If I don't get any -1, I will send pull requests with the updates in all >> aerogear repositories at the end of this week. >> >> >> Cheers! >> >> ~ Lukas >> >> >> P.S.: aerogear-users has just a ordinary mailman archive while >> aerogear-dev uses nabble, which is far better for navigation / search, etc. >> (the request to add that feature to aerogear-users is tracked in >> https://issues.jboss.org/browse/AEROGEAR-1590 ) >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20150127/130ec7c0/attachment.html From corinnekrych at gmail.com Tue Jan 27 05:24:55 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 27 Jan 2015 11:24:55 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: Message-ID: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> it looks good, I?m just puzzled by the usage section in you gist: https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b#usage which contains more build instruction than usage of android-core? for our ios readme we have the same content, not foramtted the same way though but it shoudn?t be a pb to reformat. ++ Corinne > On 27 Jan 2015, at 11:22, Sebastien Blanc wrote: > > sounds good ! > > On Tue, Jan 27, 2015 at 11:19 AM, Luk?? Fry? wrote: > Hey guys, > > me and passos brainstormed yesterday about the project info in the README files > > as it would be nice to unify them across all repositories (discussed elsewhere) and mainly allow people navigate from code repositories directly to locations where they can find more help, etc. > > > As a result, we both liked: > > 1. brief Project Info in the header > 2. more verbose Documentation / Development / Questions? / Found a bug? section in the footer > > Example for Android Core: https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b > > > Let me know what you think. > > If I don't get any -1, I will send pull requests with the updates in all aerogear repositories at the end of this week. > > > Cheers! > > ~ Lukas > > > P.S.: aerogear-users has just a ordinary mailman archive while aerogear-dev uses nabble, which is far better for navigation / search, etc. (the request to add that feature to aerogear-users is tracked in https://issues.jboss.org/browse/AEROGEAR-1590 ) > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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 bruno at abstractj.org Tue Jan 27 07:01:09 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 27 Jan 2015 10:01:09 -0200 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: Message-ID: <20150127120109.GB21268@abstractj.org> Go ahead +1 On 2015-01-27, Luk?? Fry? wrote: > Hey guys, > > me and passos brainstormed yesterday about the project info in the README > files > > as it would be nice to unify them across all repositories (discussed > elsewhere) and mainly allow people navigate from code repositories directly > to locations where they can find more help, etc. > > > As a result, we both liked: > > 1. brief Project Info in the header > 2. more verbose Documentation / Development / Questions? / Found a bug? > section in the footer > > Example for Android Core: https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b > > > Let me know what you think. > > If I don't get any -1, I will send pull requests with the updates in all > aerogear repositories at the end of this week. > > > Cheers! > > ~ Lukas > > > P.S.: aerogear-users has just a ordinary mailman archive while aerogear-dev > uses nabble, which is far better for navigation / search, etc. (the request > to add that feature to aerogear-users is tracked in > https://issues.jboss.org/browse/AEROGEAR-1590 ) > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj PGP: 0x84DC9914 From matzew at apache.org Tue Jan 27 07:13:09 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 27 Jan 2015 13:13:09 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: Message-ID: yay!! On Tue, Jan 27, 2015 at 11:19 AM, Luk?? Fry? wrote: > Hey guys, > > me and passos brainstormed yesterday about the project info in the README > files > > as it would be nice to unify them across all repositories (discussed > elsewhere) and mainly allow people navigate from code repositories directly > to locations where they can find more help, etc. > > > As a result, we both liked: > > 1. brief Project Info in the header > 2. more verbose Documentation / Development / Questions? / Found a bug? > section in the footer > > Example for Android Core: > https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b > > > Let me know what you think. > > If I don't get any -1, I will send pull requests with the updates in all > aerogear repositories at the end of this week. > > > Cheers! > > ~ Lukas > > > P.S.: aerogear-users has just a ordinary mailman archive while > aerogear-dev uses nabble, which is far better for navigation / search, etc. > (the request to add that feature to aerogear-users is tracked in > https://issues.jboss.org/browse/AEROGEAR-1590 ) > > _______________________________________________ > 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/20150127/6e80e28e/attachment.html From harini.sekar at rntbci.com Tue Jan 27 07:08:24 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Tue, 27 Jan 2015 12:08:24 +0000 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: <20150127120109.GB21268@abstractj.org> References: <20150127120109.GB21268@abstractj.org> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188BF64765@UK-EX-MBX-005.NMCorp.Nissan.Biz> Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -----Original Message----- From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Bruno Oliveira Sent: 27 January 2015 PM 05:31 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] Project Info to all projects Go ahead +1 On 2015-01-27, Luk?? Fry? wrote: > Hey guys, > > me and passos brainstormed yesterday about the project info in the > README files > > as it would be nice to unify them across all repositories (discussed > elsewhere) and mainly allow people navigate from code repositories > directly to locations where they can find more help, etc. > > > As a result, we both liked: > > 1. brief Project Info in the header > 2. more verbose Documentation / Development / Questions? / Found a bug? > section in the footer > > Example for Android Core: > https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b > > > Let me know what you think. > > If I don't get any -1, I will send pull requests with the updates in > all aerogear repositories at the end of this week. > > > Cheers! > > ~ Lukas > > > P.S.: aerogear-users has just a ordinary mailman archive while > aerogear-dev uses nabble, which is far better for navigation / search, > etc. (the request to add that feature to aerogear-users is tracked in > https://issues.jboss.org/browse/AEROGEAR-1590 ) > _______________________________________________ > 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 *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** From matzew at apache.org Tue Jan 27 07:31:49 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 27 Jan 2015 13:31:49 +0100 Subject: [aerogear-dev] iOS push error Message-ID: Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini wrote: > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > -- 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/20150127/20bb60cb/attachment.html From pstribny at redhat.com Tue Jan 27 08:26:53 2015 From: pstribny at redhat.com (Petr Stribny) Date: Tue, 27 Jan 2015 08:26:53 -0500 (EST) Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: Message-ID: <1582288923.1749125.1422365213943.JavaMail.zimbra@redhat.com> Hi Lukas and others, Definitely +1 I don't know if you plan to cover cookbook repositories, but currently the information there is not structured and formatted in the same way. I would love to see more unified approach there :) --Petr ----- Original Message ----- From: "Luk?? Fry?" To: "AeroGear Developer Mailing List" Sent: Tuesday, 27 January, 2015 11:19:35 AM Subject: [aerogear-dev] Project Info to all projects Hey guys, me and passos brainstormed yesterday about the project info in the README files as it would be nice to unify them across all repositories (discussed elsewhere) and mainly allow people navigate from code repositories directly to locations where they can find more help, etc. As a result, we both liked: 1. brief Project Info in the header 2. more verbose Documentation / Development / Questions? / Found a bug? section in the footer Example for Android Core: https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b Let me know what you think. If I don't get any -1, I will send pull requests with the updates in all aerogear repositories at the end of this week. Cheers! ~ Lukas P.S.: aerogear-users has just a ordinary mailman archive while aerogear-dev uses nabble, which is far better for navigation / search, etc. (the request to add that feature to aerogear-users is tracked in https://issues.jboss.org/browse/AEROGEAR-1590 ) _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev From lukas.fryc at gmail.com Tue Jan 27 08:47:19 2015 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 27 Jan 2015 14:47:19 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: Yea, it would be nice if usage would show the code snippet, so Usage would cover: 1. how to add the library dependency to your project (which is covered in Android Core README) 2. a smallest possible snippet of the code that covers how to use the lib (that is not covered atm) + link to respective feature doc if needed I like what iOS has here [1], do we want to adopt this pattern for Android, Cordova and JS as well? [1] https://github.com/aerogear/aerogear-ios-oauth2 On Tue, Jan 27, 2015 at 11:24 AM, Corinne Krych wrote: > it looks good, I?m just puzzled by the usage section in you gist: > https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b#usage > which contains more build instruction than usage of android-core? > > for our ios readme we have the same content, not foramtted the same way > though but it shoudn?t be a pb to reformat. > > ++ > Corinne > > > On 27 Jan 2015, at 11:22, Sebastien Blanc wrote: > > > > sounds good ! > > > > On Tue, Jan 27, 2015 at 11:19 AM, Luk?? Fry? > wrote: > > Hey guys, > > > > me and passos brainstormed yesterday about the project info in the > README files > > > > as it would be nice to unify them across all repositories (discussed > elsewhere) and mainly allow people navigate from code repositories directly > to locations where they can find more help, etc. > > > > > > As a result, we both liked: > > > > 1. brief Project Info in the header > > 2. more verbose Documentation / Development / Questions? / Found a bug? > section in the footer > > > > Example for Android Core: > https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b > > > > > > Let me know what you think. > > > > If I don't get any -1, I will send pull requests with the updates in all > aerogear repositories at the end of this week. > > > > > > Cheers! > > > > ~ Lukas > > > > > > P.S.: aerogear-users has just a ordinary mailman archive while > aerogear-dev uses nabble, which is far better for navigation / search, etc. > (the request to add that feature to aerogear-users is tracked in > https://issues.jboss.org/browse/AEROGEAR-1590 ) > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20150127/3564218d/attachment.html From klinux at gmail.com Tue Jan 27 08:56:51 2015 From: klinux at gmail.com (Kleber Rocha) Date: Tue, 27 Jan 2015 11:56:51 -0200 Subject: [aerogear-dev] aerogear-push and sticky-session Message-ID: Hello, There any way to use aerogear-push with mod_cluster and sticky-session? I configured a wildfly and mod_cluster, with two nodes, but session is lost when changed the node. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150127/b2702305/attachment-0001.html From lholmqui at redhat.com Tue Jan 27 08:59:20 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 27 Jan 2015 08:59:20 -0500 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: Message-ID: http://img.pandawhale.com/101379-Jim-Carrey-I-like-it-alot-gif-GflM.gif > On Jan 27, 2015, at 5:19 AM, Luk?? Fry? wrote: > > Hey guys, > > me and passos brainstormed yesterday about the project info in the README files > > as it would be nice to unify them across all repositories (discussed elsewhere) and mainly allow people navigate from code repositories directly to locations where they can find more help, etc. > > > As a result, we both liked: > > 1. brief Project Info in the header > 2. more verbose Documentation / Development / Questions? / Found a bug? section in the footer > > Example for Android Core: https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b > > > Let me know what you think. > > If I don't get any -1, I will send pull requests with the updates in all aerogear repositories at the end of this week. > > > Cheers! > > ~ Lukas > > > P.S.: aerogear-users has just a ordinary mailman archive while aerogear-dev uses nabble, which is far better for navigation / search, etc. (the request to add that feature to aerogear-users is tracked in https://issues.jboss.org/browse/AEROGEAR-1590 ) > _______________________________________________ > 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/20150127/07a8fde9/attachment.html From kpiwko at redhat.com Tue Jan 27 09:43:41 2015 From: kpiwko at redhat.com (Karel Piwko) Date: Tue, 27 Jan 2015 15:43:41 +0100 Subject: [aerogear-dev] UPS unit tests In-Reply-To: References: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> <54BFD3F2.6040906@redhat.com> Message-ID: <1422369821.12188.6.camel@localhost> On Wed, 2015-01-21 at 17:32 +0100, Matthias Wessendorf wrote: > > > On Wed, Jan 21, 2015 at 5:29 PM, Summers Pittman > wrote: > On 01/21/2015 10:50 AM, Matthias Wessendorf wrote: > > > I think the problem that I have with using Arquillian is the > > time of execution for these integration tests. It boots up a > > container and stuff and just makes the test execution take a > > very long time. We spoke about that in the past, and didn't > > do Aquillian due to that. > I'm learning to alike Arquillian. Would it be terribly to put > the Arq tests in a profile so they only get run if you pass > -Pit or something? > > > nope - that sounds good, folder could be > src/itest/java/.... Definitely +1 to Erik's change. itest folder is by default executed if you run verify phase by maven-failsafe-plugin. Alternatively long running tests can be put into https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/ but I would not qualify 15s for a long running test (despite it is 100% increase ;-). > > > > and only enabled on a -Pit or -Pitests > > Eventually the tests may get to take long enough its > important. > > The android-maven-plugin does that so you aren't always firing > up Android VM's. > > > > > > Not sure how others feel about it, but I'd prefer we dont > > boot a container inside our tests > > > > On Wed, Jan 21, 2015 at 4:40 PM, Erik Jan de Wit > > wrote: > > Hi, > > > > > > The database unit tests of the UPS contain a lot of > > setup code as setting up the database is done within > > the test method. I?m proposing to remove this > > ?noise? from the test and put it in a separate file. > > Another thing that is setting up the dao's, when we > > use arquillian weld container we can use injection > > in our tests to further reduce the boilerplate, have > > a look at an example: > > > > > > https://github.com/edewit/aerogear-unifiedpush-server/blob/4bb63adce319df25e8e77d505f2844cf80ff5644/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/PushApplicationDaoTest.java > > > > > > If you like I could do this for all these tests. > > > > > > 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 > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > _______________________________________________ > 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 From supittma at redhat.com Tue Jan 27 11:27:39 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 27 Jan 2015 11:27:39 -0500 Subject: [aerogear-dev] Properties for Sync Client API Message-ID: <54C7BC7B.2010405@redhat.com> What data is needed for instanciating a sync client on each of the platforms? On Android we need the clientId (for the sync server) and the senderId (for the GCM-XMPP bridge). I know that for netty/websockets we also need a URL for the server but not the sender id. Am I missing anything else? -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From lholmqui at redhat.com Tue Jan 27 12:28:25 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 27 Jan 2015 12:28:25 -0500 Subject: [aerogear-dev] Properties for Sync Client API In-Reply-To: <54C7BC7B.2010405@redhat.com> References: <54C7BC7B.2010405@redhat.com> Message-ID: <46E25D9A-05D1-4B5C-9747-9FADB1604EAB@redhat.com> atm for JS, all we need is the url to the server. We also have optional params for callback functions, onopen, onsync, etc... > On Jan 27, 2015, at 11:27 AM, Summers Pittman wrote: > > What data is needed for instanciating a sync client on each of the > platforms? > > On Android we need the clientId (for the sync server) and the senderId > (for the GCM-XMPP bridge). > > I know that for netty/websockets we also need a URL for the server but > not the sender id. Am I missing anything else? > > -- > Summers Pittman >>> Phone:404 941 4698 >>> Java is my crack. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Tue Jan 27 13:03:52 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 27 Jan 2015 19:03:52 +0100 Subject: [aerogear-dev] Properties for Sync Client API In-Reply-To: <46E25D9A-05D1-4B5C-9747-9FADB1604EAB@redhat.com> References: <54C7BC7B.2010405@redhat.com> <46E25D9A-05D1-4B5C-9747-9FADB1604EAB@redhat.com> Message-ID: same for iOS https://github.com/aerogear/aerogear-ios-sync-demo/blob/master/AeroGearSyncDemo/Info.plist#L5-L8 -M On Tue, Jan 27, 2015 at 6:28 PM, Lucas Holmquist wrote: > atm for JS, all we need is the url to the server. We also have optional > params for callback functions, onopen, onsync, etc... > > On Jan 27, 2015, at 11:27 AM, Summers Pittman > wrote: > > > > What data is needed for instanciating a sync client on each of the > > platforms? > > > > On Android we need the clientId (for the sync server) and the senderId > > (for the GCM-XMPP bridge). > > > > I know that for netty/websockets we also need a URL for the server but > > not the sender id. Am I missing anything else? > > > > -- > > Summers Pittman > >>> Phone:404 941 4698 > >>> Java is my crack. > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20150127/6858e260/attachment.html From matzew at apache.org Tue Jan 27 13:32:43 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 27 Jan 2015 19:32:43 +0100 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <54C65F8E.9090907@redhat.com> References: <54C65F8E.9090907@redhat.com> Message-ID: On Mon, Jan 26, 2015 at 4:38 PM, Summers Pittman wrote: > > Summary (From my POV on Android): > > Sync Server doesn't use any authentication or ownership tracking. > that's fine, for alpha.1. Can you create a ticket to track this on AGSYNC for later alpha releases? Or do we have already such an issue > GCM-XMPP bridge needs a lot of love > We need to define a different connection lifecycle for GCM. > Similar to above, I think for initial alpha the current connection bridge may be OK. We have JIRAs for that ? > The in memory data store is problematic because clients and servers > must be stopped and started atomically > Dan created this for one of the later (alpha) releases: https://issues.jboss.org/browse/AGSYNC-23 > We might want to show off syncing different types of documents (i.e. > a todo list in addition to Luke's hobbies) > Let's make sure the epics for the demos are covering that. Perhaps worth to open a new thread, if we really need a new demo or so for the alpha.1 > Fixing the GCM bridge is probably a couple weeks of work to get it > "solid". That will be a good alpha.1/preview to show off. > ok, but I think if the only the current bridge makes it, it would not be the end of the world. > > So Last week I put together a demo to try and stretch the legs of the > Android Sync Client APIs. > > It crashes, a lot. Which is a bit to be expected as the code hasn't > really be used for, well, anything until now. We will get to that though. > > Here is the alpha.1 workflow. You log in and you see your docs. You can > edit your docs or you can create new ones. In the future I would like > to add sharing and collaboration but that's the future. +1 like the idea > Here's a flow > chart for the visual thinkers out there (with real screen caps from the > real working app) > > * > > https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing nice diagram - looks like a solid flow > > > To make all of this work I use a RESTful server which tracks a user's > username and the documents they "own". The sync server just syncs and > serves the document you ask for. It has no authentication and any doc > you ask for you get to be an editor on. > your restful server would be the backend, that should/clould be 'plugged' into the sync? (in a later release) > > The client uses the GCM XMPP? bridge I wrote while drunk on the side of > a mountain and it shows. :-) Ok, perhaps we should get it improved before we ship alpha.1 > The biggest issue is that shadows for > documents aren't getting created right sometimes because either 1) the > client or server bounced and the data stores are no long synced or 2) > the server thinks there are more clients than actually are connected. > sounds like a bug > GCM-XMPP doesn't supply connection/disconnection information like > WebSockets will. Instead we just know that some messages we sent a > while ago weren't delivered. We need to figure out how to turn this > into connection and disconnection information in a way that lets the > shadows exist correctly. > the messages that are arrving via GCM could be used to query for the version from the sync server. Eg. via a REST API? > > Another issue that needs to be addressed is using something other than > the Luke Skywalker hobbies document. (Or maybe showing off multiple > document types in the demo). I'm up for suggestions. > > Anyway, the principles (diff sync with a restful documentId broker for > security) are sound. I think we can buff out some implementation > details and have a good alpha/preview/poc release in the few weeks -> 1 > month time frame for Android and the sync server. > I think ideally the release would be ready around 20th of Feb, perhaps slightly later > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > > Foot Notes: > 1. The sync server has two client connection technologies : WebSockets > and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the > nasty connection handling code and gives let's Android deal with it. > More info here : https://developer.android.com/google/gcm/ccs.html > > _______________________________________________ > 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/20150127/7dd01bce/attachment-0001.html From matzew at apache.org Tue Jan 27 13:36:02 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 27 Jan 2015 19:36:02 +0100 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <54C67031.8040207@redhat.com> References: <54C65F8E.9090907@redhat.com> <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> <54C66BF9.3050304@redhat.com> <5BF00158-B30E-416C-A75F-8EA34312903F@redhat.com> <54C67031.8040207@redhat.com> Message-ID: On Mon, Jan 26, 2015 at 5:49 PM, Summers Pittman wrote: > On 01/26/2015 11:37 AM, Lucas Holmquist wrote: > > Perhaps we have already brought this up, but what are we(our sync stuff) > trying to be. > > Are we trying to be Dropbox/google docs/etc?.. or something else(what > that is i?m not sure). > > What are our real use cases here? > > Here are some simple ones that I want the sync server for > * A Conference app user synchronizes a personalized schedule among his > devices > * A Users preferences are restored / synchronized across his devices > (filtered by some kind of profile. IE phone preference, tablet > preferences, desktop preferences) > these are (to me) the main ones > * A list of content is continually updated (think Facebook feed) > > So this gives us two usage patterns > > 1. A single user-document synchronized across devices > 2. A single document synchronized across all user*devices. > > I don't think anyone has thought of some truly collaborative things like > Google docs where you have multiple users on multiple devices editing > multiple documents all with different permission tuples. > > Many things can be fit in these two scenarios however. In the Dropbox use > case you mention the "document" is the users files, metadata, and their > location. The actual data will probably be hosted some place else. > > > > On Jan 26, 2015, at 11:31 AM, Summers Pittman > wrote: > > On 01/26/2015 11:26 AM, Randall Hauch wrote: > > From this and previous threads, it sounds like you?re targeting how > multiple users could collaboratively edit the same document. Essentially, > this is like Google Docs, though perhaps a bit lighter weight. Am I > misunderstanding the scenario? > > Document is a generic term. It is a wrapper around a JSON serializable > object. > > > For example, would this kind of data sync be useful when there are > millions of shared documents/entities? For example, a Yelp-like app would > probably want to have an entity/document for each restaurant or business, > where that document contained an aggregation of information about that > business. In my mind, these kinds of documents are more akin to JPA > entities ? or rather akin to aggregates of related JPA entity objects. > > Yes ish. Right now the sync server is very young, but we can model the > data as a single document and have the apps display views into it and > make edits appropriately. The trick will be making sure that the > serialization is always the same (IE two clients aren't constantly > updating because they serialize data in different orders) > > > Best regards, > > Randall > > > On Jan 26, 2015, at 9:38 AM, Summers Pittman wrote: > > > Summary (From my POV on Android): > > Sync Server doesn't use any authentication or ownership tracking. > GCM-XMPP bridge needs a lot of love > We need to define a different connection lifecycle for GCM. > The in memory data store is problematic because clients and servers > must be stopped and started atomically > We might want to show off syncing different types of documents (i.e. > a todo list in addition to Luke's hobbies) > Fixing the GCM bridge is probably a couple weeks of work to get it > "solid". That will be a good alpha.1/preview to show off. > > So Last week I put together a demo to try and stretch the legs of the > Android Sync Client APIs. > > It crashes, a lot. Which is a bit to be expected as the code hasn't > really be used for, well, anything until now. We will get to that though. > > Here is the alpha.1 workflow. You log in and you see your docs. You can > edit your docs or you can create new ones. In the future I would like > to add sharing and collaboration but that's the future. Here's a flow > chart for the visual thinkers out there (with real screen caps from the > real working app) > > * > > https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing > > To make all of this work I use a RESTful server which tracks a user's > username and the documents they "own". The sync server just syncs and > serves the document you ask for. It has no authentication and any doc > you ask for you get to be an editor on. > > The client uses the GCM XMPP? bridge I wrote while drunk on the side of > a mountain and it shows. The biggest issue is that shadows for > documents aren't getting created right sometimes because either 1) the > client or server bounced and the data stores are no long synced or 2) > the server thinks there are more clients than actually are connected. > GCM-XMPP doesn't supply connection/disconnection information like > WebSockets will. Instead we just know that some messages we sent a > while ago weren't delivered. We need to figure out how to turn this > into connection and disconnection information in a way that lets the > shadows exist correctly. > > Another issue that needs to be addressed is using something other than > the Luke Skywalker hobbies document. (Or maybe showing off multiple > document types in the demo). I'm up for suggestions. > > Anyway, the principles (diff sync with a restful documentId broker for > security) are sound. I think we can buff out some implementation > details and have a good alpha/preview/poc release in the few weeks -> 1 > month time frame for Android and the sync server. > > -- > Summers Pittman > > Phone:404 941 4698 > Java is my crack. > > > > Foot Notes: > 1. The sync server has two client connection technologies : WebSockets > and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the > nasty connection handling code and gives let's Android deal with it. > More info here : https://developer.android.com/google/gcm/ccs.html > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > > Phone:404 941 4698 > Java is my crack. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > 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/20150127/8a99d500/attachment-0001.html From matzew at apache.org Tue Jan 27 13:39:51 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 27 Jan 2015 19:39:51 +0100 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: References: <54C65F8E.9090907@redhat.com> <1B8F8792-C955-4B6A-93A8-94ED0390FA4F@redhat.com> <54C66BF9.3050304@redhat.com> Message-ID: On Mon, Jan 26, 2015 at 6:00 PM, Randall Hauch wrote: > On a related note, I recently finished a prototype for a backend storage > solution that stores JSON documents (entities) in collections and zones, > and has a number of other features. There were several goals, including > several that were just focused on backend technologies (e.g., fault > tolerance, scalability, data safety, performance, what can be done without > transactions, etc.). With limited time, I also wanted to focus on the more > unknown and higher risk stuff, so I deferred several other far more > straightforward things like wrapping with a server (e.g., Undertow, a > LiveOak subsystem, etc.) and using AeroGear?s UPS. One thing I did look > into is what kind of interchange might work best for mobile apps reading > and updating data, and how mobile apps can synchronize their local state > (e.g., data sync). > > I?m not sure what (if anything) are the next steps for this, but all of it > is at https://github.com/rhauch/debezium. I?d be interested in getting > feedback on the concept, the approach, the documentation, etc., so if > you?re interested in learning more perhaps the best place to start it at > the wiki: https://github.com/rhauch/debezium/wiki > thanks for sharing. I create a ticket to evaluate this for a later (alpha) release: https://issues.jboss.org/browse/AGSYNC-27 -Matthias > > > On Jan 26, 2015, at 10:31 AM, Summers Pittman wrote: > > On 01/26/2015 11:26 AM, Randall Hauch wrote: > > From this and previous threads, it sounds like you?re targeting how > multiple users could collaboratively edit the same document. Essentially, > this is like Google Docs, though perhaps a bit lighter weight. Am I > misunderstanding the scenario? > > Document is a generic term. It is a wrapper around a JSON serializable > object. > > > For example, would this kind of data sync be useful when there are > millions of shared documents/entities? For example, a Yelp-like app would > probably want to have an entity/document for each restaurant or business, > where that document contained an aggregation of information about that > business. In my mind, these kinds of documents are more akin to JPA > entities ? or rather akin to aggregates of related JPA entity objects. > > Yes ish. Right now the sync server is very young, but we can model the > data as a single document and have the apps display views into it and make > edits appropriately. The trick will be making sure that the serialization > is always the same (IE two clients aren't constantly updating because they > serialize data in different orders) > > > Best regards, > > Randall > > > On Jan 26, 2015, at 9:38 AM, Summers Pittman wrote: > > > Summary (From my POV on Android): > > Sync Server doesn't use any authentication or ownership tracking. > GCM-XMPP bridge needs a lot of love > We need to define a different connection lifecycle for GCM. > The in memory data store is problematic because clients and servers > must be stopped and started atomically > We might want to show off syncing different types of documents (i.e. > a todo list in addition to Luke's hobbies) > Fixing the GCM bridge is probably a couple weeks of work to get it > "solid". That will be a good alpha.1/preview to show off. > > So Last week I put together a demo to try and stretch the legs of the > Android Sync Client APIs. > > It crashes, a lot. Which is a bit to be expected as the code hasn't > really be used for, well, anything until now. We will get to that though. > > Here is the alpha.1 workflow. You log in and you see your docs. You can > edit your docs or you can create new ones. In the future I would like > to add sharing and collaboration but that's the future. Here's a flow > chart for the visual thinkers out there (with real screen caps from the > real working app) > > * > > https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing > > To make all of this work I use a RESTful server which tracks a user's > username and the documents they "own". The sync server just syncs and > serves the document you ask for. It has no authentication and any doc > you ask for you get to be an editor on. > > The client uses the GCM XMPP? bridge I wrote while drunk on the side of > a mountain and it shows. The biggest issue is that shadows for > documents aren't getting created right sometimes because either 1) the > client or server bounced and the data stores are no long synced or 2) > the server thinks there are more clients than actually are connected. > GCM-XMPP doesn't supply connection/disconnection information like > WebSockets will. Instead we just know that some messages we sent a > while ago weren't delivered. We need to figure out how to turn this > into connection and disconnection information in a way that lets the > shadows exist correctly. > > Another issue that needs to be addressed is using something other than > the Luke Skywalker hobbies document. (Or maybe showing off multiple > document types in the demo). I'm up for suggestions. > > Anyway, the principles (diff sync with a restful documentId broker for > security) are sound. I think we can buff out some implementation > details and have a good alpha/preview/poc release in the few weeks -> 1 > month time frame for Android and the sync server. > > -- > Summers Pittman > > Phone:404 941 4698 > Java is my crack. > > > > Foot Notes: > 1. The sync server has two client connection technologies : WebSockets > and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the > nasty connection handling code and gives let's Android deal with it. > More info here : https://developer.android.com/google/gcm/ccs.html > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > > Phone:404 941 4698 > Java is my crack. > > > > > _______________________________________________ > 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/20150127/cbfa553f/attachment.html From supittma at redhat.com Tue Jan 27 14:43:44 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 27 Jan 2015 14:43:44 -0500 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: References: <54C65F8E.9090907@redhat.com> Message-ID: <54C7EA70.4040303@redhat.com> On 01/27/2015 01:32 PM, Matthias Wessendorf wrote: > > > On Mon, Jan 26, 2015 at 4:38 PM, Summers Pittman > wrote: > > > Summary (From my POV on Android): > > Sync Server doesn't use any authentication or ownership tracking. > > > that's fine, for alpha.1. Can you create a ticket to track this on > AGSYNC for later alpha releases? Or do we have already such an issue I'll figure this out with danbev. He mentioned better integration for J2EE flavored things is a thing to investigate. It may be that the sync-server is better served as a database styled thing and the app server is responsible for role based data security. > GCM-XMPP bridge needs a lot of love > We need to define a different connection lifecycle for GCM. > > > Similar to above, I think for initial alpha the current connection > bridge may be OK. We have JIRAs for that ? * https://issues.jboss.org/browse/AGSYNC-28 I schedule it for beta.1. Really this should be something that should be put together at the same time as persistent data. > The in memory data store is problematic because clients and servers > must be stopped and started atomically > > > Dan created this for one of the later (alpha) releases: > https://issues.jboss.org/browse/AGSYNC-23 > > We might want to show off syncing different types of documents (i.e. > a todo list in addition to Luke's hobbies) > > > Let's make sure the epics for the demos are covering that. Perhaps > worth to open a new thread, > if we really need a new demo or so for the alpha.1 > > Fixing the GCM bridge is probably a couple weeks of work to get it > "solid". That will be a good alpha.1/preview to show off. > > > ok, but I think if the only the current bridge makes it, it would not > be the end of the world. > > > So Last week I put together a demo to try and stretch the legs of the > Android Sync Client APIs. > > It crashes, a lot. Which is a bit to be expected as the code hasn't > really be used for, well, anything until now. We will get to that > though. > > Here is the alpha.1 workflow. You log in and you see your docs. > You can > edit your docs or you can create new ones. In the future I would like > to add sharing and collaboration but that's the future. > > > +1 like the idea > > Here's a flow > chart for the visual thinkers out there (with real screen caps > from the > real working app) > > * > https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing > > > nice diagram - looks like a solid flow > > > > To make all of this work I use a RESTful server which tracks a user's > username and the documents they "own". The sync server just syncs and > serves the document you ask for. It has no authentication and any doc > you ask for you get to be an editor on. > > > > your restful server would be the backend, that should/clould be > 'plugged' into the sync? (in a later release) I talked to lolquist about it yesterday. The final evolution of this idea is the only thing in the REST server is a secured endpoint which points you to a document on the sync server. This means all of your information will be hosted directly from the sync server. > > > The client uses the GCM XMPP? bridge I wrote while drunk on the > side of > a mountain and it shows. > > > :-) Ok, perhaps we should get it improved before we ship alpha.1 Already on it. I have a few JIRAs and have brainstormed a set of fixes with passos. Stay tuned. > The biggest issue is that shadows for > documents aren't getting created right sometimes because either 1) the > client or server bounced and the data stores are no long synced or 2) > the server thinks there are more clients than actually are connected. > > > sounds like a bug > > GCM-XMPP doesn't supply connection/disconnection information like > WebSockets will. Instead we just know that some messages we sent a > while ago weren't delivered. We need to figure out how to turn this > into connection and disconnection information in a way that lets the > shadows exist correctly. > > > the messages that are arrving via GCM could be used to query for the > version from the sync server. Eg. via a REST API? > > > Another issue that needs to be addressed is using something other than > the Luke Skywalker hobbies document. (Or maybe showing off multiple > document types in the demo). I'm up for suggestions. > > Anyway, the principles (diff sync with a restful documentId broker for > security) are sound. I think we can buff out some implementation > details and have a good alpha/preview/poc release in the few weeks > -> 1 > month time frame for Android and the sync server. > > > I think ideally the release would be ready around 20th of Feb, perhaps > slightly later Sounds like we agree :) > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > > Foot Notes: > 1. The sync server has two client connection technologies : WebSockets > and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the > nasty connection handling code and gives let's Android deal with it. > More info here : https://developer.android.com/google/gcm/ccs.html > > _______________________________________________ > 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 -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150127/b314ddf8/attachment-0001.html From matzew at apache.org Tue Jan 27 15:40:39 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 27 Jan 2015 21:40:39 +0100 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: <54C7EA70.4040303@redhat.com> References: <54C65F8E.9090907@redhat.com> <54C7EA70.4040303@redhat.com> Message-ID: On Tue, Jan 27, 2015 at 8:43 PM, Summers Pittman wrote: > On 01/27/2015 01:32 PM, Matthias Wessendorf wrote: > > > > On Mon, Jan 26, 2015 at 4:38 PM, Summers Pittman > wrote: > >> >> Summary (From my POV on Android): >> >> Sync Server doesn't use any authentication or ownership tracking. >> > > that's fine, for alpha.1. Can you create a ticket to track this on > AGSYNC for later alpha releases? Or do we have already such an issue > > > I'll figure this out with danbev. He mentioned better integration for > J2EE flavored things is a thing to investigate. It may be that the > sync-server is better served as a database styled thing and the app server > is responsible for role based data security. > e.g. like JAX-RS extensions/adapters that can community with the "sync-server" resource? > > > > >> GCM-XMPP bridge needs a lot of love >> We need to define a different connection lifecycle for GCM. >> > > Similar to above, I think for initial alpha the current connection > bridge may be OK. We have JIRAs for that ? > > > * https://issues.jboss.org/browse/AGSYNC-28 > > I schedule it for beta.1. Really this should be something that should be > put together at the same time as persistent data. > > > > >> The in memory data store is problematic because clients and servers >> must be stopped and started atomically >> > > Dan created this for one of the later (alpha) releases: > https://issues.jboss.org/browse/AGSYNC-23 > > >> We might want to show off syncing different types of documents (i.e. >> a todo list in addition to Luke's hobbies) >> > > Let's make sure the epics for the demos are covering that. Perhaps worth > to open a new thread, > if we really need a new demo or so for the alpha.1 > > > >> Fixing the GCM bridge is probably a couple weeks of work to get it >> "solid". That will be a good alpha.1/preview to show off. >> > > ok, but I think if the only the current bridge makes it, it would not be > the end of the world. > > >> >> So Last week I put together a demo to try and stretch the legs of the >> Android Sync Client APIs. >> >> It crashes, a lot. Which is a bit to be expected as the code hasn't >> really be used for, well, anything until now. We will get to that though. >> >> Here is the alpha.1 workflow. You log in and you see your docs. You can >> edit your docs or you can create new ones. In the future I would like >> to add sharing and collaboration but that's the future. > > > +1 like the idea > > > >> Here's a flow >> chart for the visual thinkers out there (with real screen caps from the >> real working app) >> >> * >> >> https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing > > > nice diagram - looks like a solid flow > > >> >> >> To make all of this work I use a RESTful server which tracks a user's >> username and the documents they "own". The sync server just syncs and >> serves the document you ask for. It has no authentication and any doc >> you ask for you get to be an editor on. >> > > > your restful server would be the backend, that should/clould be > 'plugged' into the sync? (in a later release) > > I talked to lolquist about it yesterday. The final evolution of this idea > is the only thing in the REST server is a secured endpoint which points you > to a document on the sync server. This means all of your information will > be hosted directly from the sync server. > ok > > > >> >> The client uses the GCM XMPP? bridge I wrote while drunk on the side of >> a mountain and it shows. > > > :-) Ok, perhaps we should get it improved before we ship alpha.1 > > > Already on it. I have a few JIRAs and have brainstormed a set of fixes > with passos. Stay tuned. > nice > > > > >> The biggest issue is that shadows for >> documents aren't getting created right sometimes because either 1) the >> client or server bounced and the data stores are no long synced or 2) >> the server thinks there are more clients than actually are connected. >> > > sounds like a bug > > >> GCM-XMPP doesn't supply connection/disconnection information like >> WebSockets will. Instead we just know that some messages we sent a >> while ago weren't delivered. We need to figure out how to turn this >> into connection and disconnection information in a way that lets the >> shadows exist correctly. >> > > the messages that are arrving via GCM could be used to query for the > version from the sync server. Eg. via a REST API? > >> >> Another issue that needs to be addressed is using something other than >> the Luke Skywalker hobbies document. (Or maybe showing off multiple >> document types in the demo). I'm up for suggestions. >> >> Anyway, the principles (diff sync with a restful documentId broker for >> security) are sound. I think we can buff out some implementation >> details and have a good alpha/preview/poc release in the few weeks -> 1 >> month time frame for Android and the sync server. >> > > I think ideally the release would be ready around 20th of Feb, perhaps > slightly later > > Sounds like we agree :) > perfect :-) > > > >> >> -- >> Summers Pittman >> >>Phone:404 941 4698 >> >>Java is my crack. >> >> >> >> Foot Notes: >> 1. The sync server has two client connection technologies : WebSockets >> and GCM-XMPP. Android uses the GCM-XMPP because it takes all of the >> nasty connection handling code and gives let's Android deal with it. >> More info here : https://developer.android.com/google/gcm/ccs.html >> >> _______________________________________________ >> 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 listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > 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/20150127/b1230f98/attachment.html From supittma at redhat.com Tue Jan 27 15:46:41 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 27 Jan 2015 15:46:41 -0500 Subject: [aerogear-dev] Sync Notes / Early issues In-Reply-To: References: <54C65F8E.9090907@redhat.com> <54C7EA70.4040303@redhat.com> Message-ID: <54C7F931.2050305@redhat.com> On 01/27/2015 03:40 PM, Matthias Wessendorf wrote: > > > On Tue, Jan 27, 2015 at 8:43 PM, Summers Pittman > wrote: > > On 01/27/2015 01:32 PM, Matthias Wessendorf wrote: >> >> >> On Mon, Jan 26, 2015 at 4:38 PM, Summers Pittman >> > wrote: >> >> >> Summary (From my POV on Android): >> >> Sync Server doesn't use any authentication or ownership >> tracking. >> >> >> that's fine, for alpha.1. Can you create a ticket to track this >> on AGSYNC for later alpha releases? Or do we have already such an >> issue > > I'll figure this out with danbev. He mentioned better integration > for J2EE flavored things is a thing to investigate. It may be > that the sync-server is better served as a database styled thing > and the app server is responsible for role based data security. > > > e.g. like JAX-RS extensions/adapters that can community with the > "sync-server" resource? Basically. Something something annotations and CDI > > > >> GCM-XMPP bridge needs a lot of love >> We need to define a different connection lifecycle for GCM. >> >> >> Similar to above, I think for initial alpha the current >> connection bridge may be OK. We have JIRAs for that ? > > * https://issues.jboss.org/browse/AGSYNC-28 > > I schedule it for beta.1. Really this should be something that > should be put together at the same time as persistent data. > > >> The in memory data store is problematic because clients and >> servers >> must be stopped and started atomically >> >> >> Dan created this for one of the later (alpha) releases: >> https://issues.jboss.org/browse/AGSYNC-23 >> >> We might want to show off syncing different types of >> documents (i.e. >> a todo list in addition to Luke's hobbies) >> >> >> Let's make sure the epics for the demos are covering that. >> Perhaps worth to open a new thread, >> if we really need a new demo or so for the alpha.1 >> >> Fixing the GCM bridge is probably a couple weeks of work to >> get it >> "solid". That will be a good alpha.1/preview to show off. >> >> >> ok, but I think if the only the current bridge makes it, it would >> not be the end of the world. >> >> >> So Last week I put together a demo to try and stretch the >> legs of the >> Android Sync Client APIs. >> >> It crashes, a lot. Which is a bit to be expected as the code >> hasn't >> really be used for, well, anything until now. We will get to >> that though. >> >> Here is the alpha.1 workflow. You log in and you see your >> docs. You can >> edit your docs or you can create new ones. In the future I >> would like >> to add sharing and collaboration but that's the future. >> >> >> +1 like the idea >> >> Here's a flow >> chart for the visual thinkers out there (with real screen >> caps from the >> real working app) >> >> * >> https://docs.google.com/drawings/d/145XuutxR1yY0k81w2nIIy980itDIwxzH_gcDE3jLrvc/edit?usp=sharing >> >> >> nice diagram - looks like a solid flow >> >> >> >> To make all of this work I use a RESTful server which tracks >> a user's >> username and the documents they "own". The sync server just >> syncs and >> serves the document you ask for. It has no authentication >> and any doc >> you ask for you get to be an editor on. >> >> >> >> your restful server would be the backend, that should/clould be >> 'plugged' into the sync? (in a later release) > I talked to lolquist about it yesterday. The final evolution of > this idea is the only thing in the REST server is a secured > endpoint which points you to a document on the sync server. This > means all of your information will be hosted directly from the > sync server. > > > ok > > >> >> The client uses the GCM XMPP? bridge I wrote while drunk on >> the side of >> a mountain and it shows. >> >> >> :-) Ok, perhaps we should get it improved before we ship alpha.1 > > Already on it. I have a few JIRAs and have brainstormed a set of > fixes with passos. Stay tuned. > > > nice > > > >> The biggest issue is that shadows for >> documents aren't getting created right sometimes because >> either 1) the >> client or server bounced and the data stores are no long >> synced or 2) >> the server thinks there are more clients than actually are >> connected. >> >> >> sounds like a bug >> >> GCM-XMPP doesn't supply connection/disconnection information like >> WebSockets will. Instead we just know that some messages we >> sent a >> while ago weren't delivered. We need to figure out how to >> turn this >> into connection and disconnection information in a way that >> lets the >> shadows exist correctly. >> >> >> the messages that are arrving via GCM could be used to query for >> the version from the sync server. Eg. via a REST API? >> >> >> Another issue that needs to be addressed is using something >> other than >> the Luke Skywalker hobbies document. (Or maybe showing off >> multiple >> document types in the demo). I'm up for suggestions. >> >> Anyway, the principles (diff sync with a restful documentId >> broker for >> security) are sound. I think we can buff out some implementation >> details and have a good alpha/preview/poc release in the few >> weeks -> 1 >> month time frame for Android and the sync server. >> >> >> I think ideally the release would be ready around 20th of Feb, >> perhaps slightly later > Sounds like we agree :) > > > perfect :-) > > >> >> -- >> Summers Pittman >> >>Phone:404 941 4698 >> >>Java is my crack. >> >> >> >> Foot Notes: >> 1. The sync server has two client connection technologies : >> WebSockets >> and GCM-XMPP. Android uses the GCM-XMPP because it takes all >> of the >> nasty connection handling code and gives let's Android deal >> with it. >> More info here : >> https://developer.android.com/google/gcm/ccs.html >> >> _______________________________________________ >> 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 > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > 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 -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150127/ecfa8788/attachment-0001.html From daniel at passos.me Tue Jan 27 20:35:20 2015 From: daniel at passos.me (Daniel Passos) Date: Tue, 27 Jan 2015 23:35:20 -0200 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: Hey Luk?s, I really don't like the ideia of add the some code snipped on README. I know it's very common and most libraries do this but, it's a lot of code to explain in a README and 2 different places to update when we change/improve/whatever our libraries. I really prefer link to the ag.org doc. In related news I'd like to add a link to a example app as we did[1] on push library [1] https://github.com/aerogear/aerogear-android-push#demo-apps -- Passos On Tue, Jan 27, 2015 at 11:47 AM, Luk?? Fry? wrote: > Yea, it would be nice if usage would show the code snippet, so Usage would > cover: > > 1. how to add the library dependency to your project (which is covered in > Android Core README) > 2. a smallest possible snippet of the code that covers how to use the lib > (that is not covered atm) + link to respective feature doc if needed > > I like what iOS has here [1], do we want to adopt this pattern for > Android, Cordova and JS as well? > > [1] https://github.com/aerogear/aerogear-ios-oauth2 > > On Tue, Jan 27, 2015 at 11:24 AM, Corinne Krych > wrote: > >> it looks good, I?m just puzzled by the usage section in you gist: >> https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b#usage >> which contains more build instruction than usage of android-core? >> >> for our ios readme we have the same content, not foramtted the same way >> though but it shoudn?t be a pb to reformat. >> >> ++ >> Corinne >> >> > On 27 Jan 2015, at 11:22, Sebastien Blanc wrote: >> > >> > sounds good ! >> > >> > On Tue, Jan 27, 2015 at 11:19 AM, Luk?? Fry? >> wrote: >> > Hey guys, >> > >> > me and passos brainstormed yesterday about the project info in the >> README files >> > >> > as it would be nice to unify them across all repositories (discussed >> elsewhere) and mainly allow people navigate from code repositories directly >> to locations where they can find more help, etc. >> > >> > >> > As a result, we both liked: >> > >> > 1. brief Project Info in the header >> > 2. more verbose Documentation / Development / Questions? / Found a bug? >> section in the footer >> > >> > Example for Android Core: >> https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b >> > >> > >> > Let me know what you think. >> > >> > If I don't get any -1, I will send pull requests with the updates in >> all aerogear repositories at the end of this week. >> > >> > >> > Cheers! >> > >> > ~ Lukas >> > >> > >> > P.S.: aerogear-users has just a ordinary mailman archive while >> aerogear-dev uses nabble, which is far better for navigation / search, etc. >> (the request to add that feature to aerogear-users is tracked in >> https://issues.jboss.org/browse/AEROGEAR-1590 ) >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.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/20150127/99f40d5f/attachment.html From harini.sekar at rntbci.com Tue Jan 27 22:23:36 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Wed, 28 Jan 2015 03:23:36 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: Message-ID: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150128/2b78aa8a/attachment-0001.html From matzew at apache.org Wed Jan 28 02:51:29 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 28 Jan 2015 08:51:29 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini wrote: > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > -- 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/20150128/0052ecbf/attachment.html From lukas at fryc.eu Wed Jan 28 03:08:35 2015 From: lukas at fryc.eu (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Wed, 28 Jan 2015 09:08:35 +0100 Subject: [aerogear-dev] Project Info to all projects In-Reply-To: References: <5CCEC7AF-B0F9-46AD-905D-9724BA5E57D5@gmail.com> Message-ID: Okay, lets make the example optional. As long as documentation can be found within 1 or 2 clicks, that should be fine. On Jan 28, 2015 2:35 AM, "Daniel Passos" wrote: > Hey Luk?s, > > I really don't like the ideia of add the some code snipped on README. I > know it's very common and most libraries do this but, it's a lot of code to > explain in a README and 2 different places to update when we > change/improve/whatever our libraries. I really prefer link to the ag.org > doc. > > In related news I'd like to add a link to a example app as we did[1] on > push library > > [1] https://github.com/aerogear/aerogear-android-push#demo-apps > > -- Passos > > > On Tue, Jan 27, 2015 at 11:47 AM, Luk?? Fry? wrote: > >> Yea, it would be nice if usage would show the code snippet, so Usage >> would cover: >> >> 1. how to add the library dependency to your project (which is covered in >> Android Core README) >> 2. a smallest possible snippet of the code that covers how to use the lib >> (that is not covered atm) + link to respective feature doc if needed >> >> I like what iOS has here [1], do we want to adopt this pattern for >> Android, Cordova and JS as well? >> >> [1] https://github.com/aerogear/aerogear-ios-oauth2 >> >> On Tue, Jan 27, 2015 at 11:24 AM, Corinne Krych >> wrote: >> >>> it looks good, I?m just puzzled by the usage section in you gist: >>> https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b#usage >>> which contains more build instruction than usage of android-core? >>> >>> for our ios readme we have the same content, not foramtted the same way >>> though but it shoudn?t be a pb to reformat. >>> >>> ++ >>> Corinne >>> >>> > On 27 Jan 2015, at 11:22, Sebastien Blanc wrote: >>> > >>> > sounds good ! >>> > >>> > On Tue, Jan 27, 2015 at 11:19 AM, Luk?? Fry? >>> wrote: >>> > Hey guys, >>> > >>> > me and passos brainstormed yesterday about the project info in the >>> README files >>> > >>> > as it would be nice to unify them across all repositories (discussed >>> elsewhere) and mainly allow people navigate from code repositories directly >>> to locations where they can find more help, etc. >>> > >>> > >>> > As a result, we both liked: >>> > >>> > 1. brief Project Info in the header >>> > 2. more verbose Documentation / Development / Questions? / Found a >>> bug? section in the footer >>> > >>> > Example for Android Core: >>> https://gist.github.com/lfryc/df0c9c9a9ba7acebfd7b >>> > >>> > >>> > Let me know what you think. >>> > >>> > If I don't get any -1, I will send pull requests with the updates in >>> all aerogear repositories at the end of this week. >>> > >>> > >>> > Cheers! >>> > >>> > ~ Lukas >>> > >>> > >>> > P.S.: aerogear-users has just a ordinary mailman archive while >>> aerogear-dev uses nabble, which is far better for navigation / search, etc. >>> (the request to add that feature to aerogear-users is tracked in >>> https://issues.jboss.org/browse/AEROGEAR-1590 ) >>> > >>> > _______________________________________________ >>> > aerogear-dev mailing list >>> > aerogear-dev at lists.jboss.org >>> > https://lists.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/20150128/1dab1ea1/attachment.html From corinnekrych at gmail.com Wed Jan 28 03:23:48 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 28 Jan 2015 09:23:48 +0100 Subject: [aerogear-dev] iOS team meeting Message-ID: <7F1871C2-CEA2-4DE6-81F6-9762071650BE@gmail.com> Hello All Out next iOS meeting will be on Thursday 29th January 4pm (GMT+1), here is the agenda: http://oksoclap.com/p/iOS-meeting-29thJanuary2015 Feel free to add topics, see you all there ++ Corinne From harini.sekar at rntbci.com Wed Jan 28 05:22:10 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Wed, 28 Jan 2015 10:22:10 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. [cid:image007.jpg at 01D03B12.6090B210] [cid:image008.jpg at 01D03B12.6090B210] [cid:image009.jpg at 01D03B12.6090B210] Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150128/6cf9ba33/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.jpg Type: image/jpeg Size: 32978 bytes Desc: image007.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150128/6cf9ba33/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.jpg Type: image/jpeg Size: 11323 bytes Desc: image008.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150128/6cf9ba33/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.jpg Type: image/jpeg Size: 10022 bytes Desc: image009.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150128/6cf9ba33/attachment-0005.jpg From matzew at apache.org Wed Jan 28 06:20:39 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 28 Jan 2015 12:20:39 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini wrote: > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > -- 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/20150128/0717fcf6/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.jpg Type: image/jpeg Size: 32978 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150128/0717fcf6/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.jpg Type: image/jpeg Size: 10022 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150128/0717fcf6/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.jpg Type: image/jpeg Size: 11323 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150128/0717fcf6/attachment-0005.jpg From supittma at redhat.com Wed Jan 28 09:33:07 2015 From: supittma at redhat.com (Summers Pittman) Date: Wed, 28 Jan 2015 09:33:07 -0500 Subject: [aerogear-dev] UPS unit tests In-Reply-To: References: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> <54BFD3F2.6040906@redhat.com> Message-ID: <54C8F323.5030004@redhat.com> On 01/21/2015 11:32 AM, Matthias Wessendorf wrote: > > > On Wed, Jan 21, 2015 at 5:29 PM, Summers Pittman > wrote: > > On 01/21/2015 10:50 AM, Matthias Wessendorf wrote: >> I think the problem that I have with using Arquillian is the time >> of execution for these integration tests. It boots up a container >> and stuff and just makes the test execution take a very long >> time. We spoke about that in the past, and didn't do Aquillian >> due to that. > I'm learning to alike Arquillian. Would it be terribly to put the > Arq tests in a profile so they only get run if you pass -Pit or > something? > > > nope - that sounds good, folder could be > src/itest/java/.... > > and only enabled on a -Pit or -Pitests Totally out of the blue, but is there a way to annotate test classes to make them run iff there is a flag set? If you put integration-tests in a different folder then you will also have to tell maven about them in the testSourceSet stanza which will cause them to get run anyway. (And if they aren't in source set for the default profile I'm not sure IDEs will pick them up)(Unless there is a third source set type I'm not familiar with) ---------- Buffer: *Backtrace* ---------- Debugger entered--Lisp error: (void-function this) (this is an unquoted list) eval((this is an unquoted list)) eval-last-sexp-1(nil) eval-last-sexp(nil) call-interactively(eval-last-sexp) ---------- Buffer: *Backtrace* ---------- Looks like I had too many parens on that ;) > Eventually the tests may get to take long enough its important. > > The android-maven-plugin does that so you aren't always firing up > Android VM's. >> >> Not sure how others feel about it, but I'd prefer we dont boot a >> container inside our tests >> >> On Wed, Jan 21, 2015 at 4:40 PM, Erik Jan de Wit >> > wrote: >> >> Hi, >> >> The database unit tests of the UPS contain a lot of setup >> code as setting up the database is done within the test >> method. I?m proposing to remove this ?noise? from the test >> and put it in a separate file. Another thing that is setting >> up the dao's, when we use arquillian weld container we can >> use injection in our tests to further reduce the boilerplate, >> have a look at an example: >> >> https://github.com/edewit/aerogear-unifiedpush-server/blob/4bb63adce319df25e8e77d505f2844cf80ff5644/model/jpa/src/test/java/org/jboss/aerogear/unifiedpush/jpa/PushApplicationDaoTest.java >> >> If you like I could do this for all these tests. >> >> 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 >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > -- > Summers Pittman > >>Phone:404 941 4698 > >>Java is my crack. > > > _______________________________________________ > 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 -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150128/59109382/attachment.html From harini.sekar at rntbci.com Wed Jan 28 23:55:10 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Thu, 29 Jan 2015 04:55:10 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. [cid:image001.jpg at 01D03BAD.DC091C70] [cid:image002.jpg at 01D03BAD.DC091C70] [cid:image003.jpg at 01D03BAD.DC091C70] Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/a6381405/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 32978 bytes Desc: image001.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/a6381405/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11323 bytes Desc: image002.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/a6381405/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10022 bytes Desc: image003.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/a6381405/attachment-0005.jpg From harini.sekar at rntbci.com Thu Jan 29 00:00:41 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Thu, 29 Jan 2015 05:00:41 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> Hi , When I try to integrate the JAVA Apns I am getting this error ?Exception in thread "main" com.notnoop.exceptions.NetworkIOException: java.net.UnknownHostException: gateway.push.apple.com? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Sekar, Harini Sent: 29 January 2015 AM 10:25 To: Matthias Wessendorf Cc: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. [cid:image001.jpg at 01D03BAE.A18FF9A0] [cid:image002.jpg at 01D03BAE.A18FF9A0] [cid:image003.jpg at 01D03BAE.A18FF9A0] Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/94d17797/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 32978 bytes Desc: image001.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/94d17797/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11323 bytes Desc: image002.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/94d17797/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10022 bytes Desc: image003.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/94d17797/attachment-0005.jpg From matzew at apache.org Thu Jan 29 00:51:45 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 29 Jan 2015 06:51:45 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: No, just a certificate, like described here: https://aerogear.org/docs/unifiedpush/aerogear-push-ios/ 1. Apple App ID and SSL Certificate for APNs On Thu, Jan 29, 2015 at 5:55 AM, Sekar, Harini wrote: > Hi, > > > > Do you require any ssl trusted certificate for aerogear ? > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 04:51 > > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > You are saying you are not getting push notifications delivered, even > after a reboot? I think there is something wrong with the certificate's > .p12 file. > > > > Do you have it locally ? If so, can you run a standalone test, using this > Java lib: > > https://github.com/notnoop/java-apns > > > > > > 1) get the APNs Servce: > > ApnsService service = > > APNS.newService() > > .withCert("/path/to/certificate.p12", "MyCertPassword") > > .withProductionDestination() // you said you are using production - > right ? otherwise it's Sandbox.... > > .build(); > > > > 2) get a token from the UI, ideally your own device, and send a push: > > String payload = APNS.newPayload().alertBody("Test test test").build(); > > String token = "your token goes here"; > > service.push(token, payload); > > > > > > That would help to isolate the issue. > > > > > > BTW. what version of the UPS are you running ? > > > > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: > > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > -- 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/20150129/56c6a963/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11323 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/56c6a963/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 32978 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/56c6a963/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10022 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/56c6a963/attachment-0005.jpg From harini.sekar at rntbci.com Thu Jan 29 00:58:30 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Thu, 29 Jan 2015 05:58:30 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C4691FF@UK-EX-MBX-005.NMCorp.Nissan.Biz> Hi, IOS push notification is working but still the error message is displaying Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:22 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error No, just a certificate, like described here: https://aerogear.org/docs/unifiedpush/aerogear-push-ios/ 1. Apple App ID and SSL Certificate for APNs On Thu, Jan 29, 2015 at 5:55 AM, Sekar, Harini > wrote: Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. [cid:image001.jpg at 01D03BB6.B55F9050] [cid:image002.jpg at 01D03BB6.B55F9050] [cid:image003.jpg at 01D03BB6.B55F9050] Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/7f4c4614/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 32978 bytes Desc: image001.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/7f4c4614/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11323 bytes Desc: image002.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/7f4c4614/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10022 bytes Desc: image003.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/7f4c4614/attachment-0005.jpg From matzew at apache.org Thu Jan 29 01:02:04 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 29 Jan 2015 07:02:04 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini wrote: > Hi , > > > > When I try to integrate the JAVA Apns I am getting this error ?Exception > in thread "main" *com.notnoop.exceptions.NetworkIOException*: > *java.net.UnknownHostException*: gateway.push.apple.com? > weird, I just tried this code: https://gist.github.com/matzew/461fb3f6fb26cfc092e7 and it works. Wondering, are you behind a firewall or so ? > > > Thanks & Regards > > Harini S > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Sekar, Harini > *Sent:* 29 January 2015 AM 10:25 > *To:* Matthias Wessendorf > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > Hi, > > > > Do you require any ssl trusted certificate for aerogear ? > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 04:51 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > You are saying you are not getting push notifications delivered, even > after a reboot? I think there is something wrong with the certificate's > .p12 file. > > > > Do you have it locally ? If so, can you run a standalone test, using this > Java lib: > > https://github.com/notnoop/java-apns > > > > > > 1) get the APNs Servce: > > ApnsService service = > > APNS.newService() > > .withCert("/path/to/certificate.p12", "MyCertPassword") > > .withProductionDestination() // you said you are using production - > right ? otherwise it's Sandbox.... > > .build(); > > > > 2) get a token from the UI, ideally your own device, and send a push: > > String payload = APNS.newPayload().alertBody("Test test test").build(); > > String token = "your token goes here"; > > service.push(token, payload); > > > > > > That would help to isolate the issue. > > > > > > BTW. what version of the UPS are you running ? > > > > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: > > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > -- 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/20150129/dfab643c/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10022 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/dfab643c/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 32978 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/dfab643c/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11323 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/dfab643c/attachment-0005.jpg From harini.sekar at rntbci.com Thu Jan 29 01:03:04 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Thu, 29 Jan 2015 06:03:04 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> Yes we are having proxy issue. How to set proxy for this APNS ? From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:32 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: Hi , When I try to integrate the JAVA Apns I am getting this error ?Exception in thread "main" com.notnoop.exceptions.NetworkIOException: java.net.UnknownHostException: gateway.push.apple.com? weird, I just tried this code: https://gist.github.com/matzew/461fb3f6fb26cfc092e7 and it works. Wondering, are you behind a firewall or so ? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Sekar, Harini Sent: 29 January 2015 AM 10:25 To: Matthias Wessendorf Cc: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. [cid:image001.jpg at 01D03BB7.588C5470] [cid:image002.jpg at 01D03BB7.588C5470] [cid:image003.jpg at 01D03BB7.588C5470] Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/c67e58e2/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 32978 bytes Desc: image001.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/c67e58e2/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11323 bytes Desc: image002.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/c67e58e2/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10022 bytes Desc: image003.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/c67e58e2/attachment-0005.jpg From matzew at apache.org Thu Jan 29 01:05:15 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 29 Jan 2015 07:05:15 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C4691FF@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691FF@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: On Thu, Jan 29, 2015 at 6:58 AM, Sekar, Harini wrote: > Hi, > > > > IOS push notification is working but still the error message is displaying > > *Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found* > AH!!!! yeah, that's what I tried to explain earlier: We are not yet cleaning up the messages, when you _had_ issues in the past. the history keeps track of it. That's why I asked to send again. The error should be associated w/ a date. In my screenshot from yesterday, I had an error from January 6 (almost three weeks away). But currently works. After 30 days, we drop the history. So, until than, all pushes (successful or not) are listed. And yes, unfortunately the warning goes not yet away. Here is the link to the JIRA to clean up the info https://issues.jboss.org/browse/AGPUSH-1248 Hope that helps > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:22 > > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > No, just a certificate, like described here: > > https://aerogear.org/docs/unifiedpush/aerogear-push-ios/ > > > > 1. Apple App ID and SSL Certificate for APNs > > > > On Thu, Jan 29, 2015 at 5:55 AM, Sekar, Harini > wrote: > > Hi, > > > > Do you require any ssl trusted certificate for aerogear ? > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 04:51 > > > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > You are saying you are not getting push notifications delivered, even > after a reboot? I think there is something wrong with the certificate's > .p12 file. > > > > Do you have it locally ? If so, can you run a standalone test, using this > Java lib: > > https://github.com/notnoop/java-apns > > > > > > 1) get the APNs Servce: > > ApnsService service = > > APNS.newService() > > .withCert("/path/to/certificate.p12", "MyCertPassword") > > .withProductionDestination() // you said you are using production - > right ? otherwise it's Sandbox.... > > .build(); > > > > 2) get a token from the UI, ideally your own device, and send a push: > > String payload = APNS.newPayload().alertBody("Test test test").build(); > > String token = "your token goes here"; > > service.push(token, payload); > > > > > > That would help to isolate the issue. > > > > > > BTW. what version of the UPS are you running ? > > > > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: > > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > -- 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/20150129/cc6d6b2d/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 32978 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/cc6d6b2d/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11323 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/cc6d6b2d/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10022 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/cc6d6b2d/attachment-0005.jpg From matzew at apache.org Thu Jan 29 01:07:29 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 29 Jan 2015 07:07:29 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini wrote: > Yes we are having proxy issue. How to set proxy for this APNS ? > That's currently not supported on the Unified Push Server, but we track the requirement in a ticket: https://issues.jboss.org/browse/AGPUSH-306 We didn't have much users requesting this, since usually they delpoy the Unified Push Server where they have access to the internet. Otherwise the device registration would be hard :-) -Matthias > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:32 > > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: > > Hi , > > > > When I try to integrate the JAVA Apns I am getting this error ?Exception > in thread "main" *com.notnoop.exceptions.NetworkIOException*: > *java.net.UnknownHostException*: gateway.push.apple.com? > > > > > > weird, I just tried this code: > > https://gist.github.com/matzew/461fb3f6fb26cfc092e7 > > > > > > and it works. Wondering, are you behind a firewall or so ? > > > > > > > > Thanks & Regards > > Harini S > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Sekar, Harini > *Sent:* 29 January 2015 AM 10:25 > *To:* Matthias Wessendorf > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > Hi, > > > > Do you require any ssl trusted certificate for aerogear ? > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 04:51 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > You are saying you are not getting push notifications delivered, even > after a reboot? I think there is something wrong with the certificate's > .p12 file. > > > > Do you have it locally ? If so, can you run a standalone test, using this > Java lib: > > https://github.com/notnoop/java-apns > > > > > > 1) get the APNs Servce: > > ApnsService service = > > APNS.newService() > > .withCert("/path/to/certificate.p12", "MyCertPassword") > > .withProductionDestination() // you said you are using production - > right ? otherwise it's Sandbox.... > > .build(); > > > > 2) get a token from the UI, ideally your own device, and send a push: > > String payload = APNS.newPayload().alertBody("Test test test").build(); > > String token = "your token goes here"; > > service.push(token, payload); > > > > > > That would help to isolate the issue. > > > > > > BTW. what version of the UPS are you running ? > > > > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: > > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > -- 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/20150129/4e0774b9/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10022 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/4e0774b9/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 32978 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/4e0774b9/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11323 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/4e0774b9/attachment-0005.jpg From harini.sekar at rntbci.com Thu Jan 29 01:29:28 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Thu, 29 Jan 2015 06:29:28 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> Hi, Thank u so much ? If I use Java sender client to send notification , then those activity will be listed in the History link in the Aero Gear Admin UI ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:37 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: Yes we are having proxy issue. How to set proxy for this APNS ? That's currently not supported on the Unified Push Server, but we track the requirement in a ticket: https://issues.jboss.org/browse/AGPUSH-306 We didn't have much users requesting this, since usually they delpoy the Unified Push Server where they have access to the internet. Otherwise the device registration would be hard :-) -Matthias From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:32 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: Hi , When I try to integrate the JAVA Apns I am getting this error ?Exception in thread "main" com.notnoop.exceptions.NetworkIOException: java.net.UnknownHostException: gateway.push.apple.com? weird, I just tried this code: https://gist.github.com/matzew/461fb3f6fb26cfc092e7 and it works. Wondering, are you behind a firewall or so ? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Sekar, Harini Sent: 29 January 2015 AM 10:25 To: Matthias Wessendorf Cc: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. [cid:image001.jpg at 01D03BBB.089574C0] [cid:image002.jpg at 01D03BBB.089574C0] [cid:image003.jpg at 01D03BBB.089574C0] Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/29dcb37b/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 32978 bytes Desc: image001.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/29dcb37b/attachment-0003.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 11323 bytes Desc: image002.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/29dcb37b/attachment-0004.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 10022 bytes Desc: image003.jpg Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/29dcb37b/attachment-0005.jpg From scm.blanc at gmail.com Thu Jan 29 01:48:02 2015 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Thu, 29 Jan 2015 07:48:02 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: Envoy? de mon iPhone > Le 29 janv. 2015 ? 07:29, Sekar, Harini a ?crit : > > Hi, > > Thank u so much J > If I use Java sender client to send notification , then those activity will be listed in the History link in the Aero Gear Admin UI ? > Yes , in the details you will even see it comes from the Java sender. > Thanks & Regards > Harini S > > From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf > Sent: 29 January 2015 AM 11:37 > To: Sekar, Harini > Cc: AeroGear Developer Mailing List > Subject: Re: iOS push error > > > > On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini wrote: > Yes we are having proxy issue. How to set proxy for this APNS ? > > That's currently not supported on the Unified Push Server, but we track the requirement in a ticket: > https://issues.jboss.org/browse/AGPUSH-306 > > We didn't have much users requesting this, since usually they delpoy the Unified Push Server where they have access to the internet. Otherwise the device registration would be hard :-) > > -Matthias > > > > From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf > Sent: 29 January 2015 AM 11:32 > > To: Sekar, Harini > Cc: AeroGear Developer Mailing List > Subject: Re: iOS push error > > > > On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini wrote: > Hi , > > When I try to integrate the JAVA Apns I am getting this error ?Exception in thread "main" com.notnoop.exceptions.NetworkIOException: java.net.UnknownHostException: gateway.push.apple.com? > > > weird, I just tried this code: > https://gist.github.com/matzew/461fb3f6fb26cfc092e7 > > > and it works. Wondering, are you behind a firewall or so ? > > > > Thanks & Regards > Harini S > > From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Sekar, Harini > Sent: 29 January 2015 AM 10:25 > To: Matthias Wessendorf > Cc: AeroGear Developer Mailing List > Subject: Re: [aerogear-dev] iOS push error > > Hi, > > Do you require any ssl trusted certificate for aerogear ? > > Thanks & Regards > Harini S > > From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf > Sent: 28 January 2015 PM 04:51 > To: Sekar, Harini > Cc: AeroGear Developer Mailing List > Subject: Re: iOS push error > > You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. > > Do you have it locally ? If so, can you run a standalone test, using this Java lib: > https://github.com/notnoop/java-apns > > > 1) get the APNs Servce: > ApnsService service = > APNS.newService() > .withCert("/path/to/certificate.p12", "MyCertPassword") > .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... > .build(); > > 2) get a token from the UI, ideally your own device, and send a push: > String payload = APNS.newPayload().alertBody("Test test test").build(); > String token = "your token goes here"; > service.push(token, payload); > > > That would help to isolate the issue. > > > BTW. what version of the UPS are you running ? > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini wrote: > Hi Matthias , > > Have attached the screenshots of the problem I am facing. > It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. > Kindly help me in sorting out this issue. > > > > > Thanks & Regards, > Harini S > > From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf > Sent: 28 January 2015 PM 01:21 > To: Sekar, Harini > Cc: AeroGear Developer Mailing List > Subject: Re: iOS push error > > Hi Harini, > > > Yes , but still that warning is there. > > we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). > > Here is an older error (on my test instance): > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > That error occured only on Jan 6th, but as said above, we do not yet clean that up > > > -Matthias > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini wrote: > Hello, > > It was working fine for one day. After that it started throwing the error. > I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. > > > Thanks & Regards > Harini S > > From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf > Sent: 27 January 2015 PM 06:02 > To: AeroGear Developer Mailing List; Sekar, Harini > Subject: iOS push error > > Hi Harini, > > I opened a new thread for this to make it easier to follow up on this subject. > > I just tested my Push Server and iOS just worked fine. Here are a few questions: > > * Did you upload the correct .p12 file for the iOS variant? > * Or did you replace a development cert with a production cert ? > * Did it work a few days ago? > * Did you try to reboot the instance via the openshift UI ? > > Thanks, > Matthias > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini wrote: > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is not working > Error : > reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. > *********************************************************************************************************** > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. > *********************************************************************************************************** > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. > *********************************************************************************************************** > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. > *********************************************************************************************************** > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. > *********************************************************************************************************** > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. > *********************************************************************************************************** > > _______________________________________________ > 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/20150129/c795584f/attachment-0001.html From harini.sekar at rntbci.com Thu Jan 29 02:03:26 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Thu, 29 Jan 2015 07:03:26 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> It works. Then why this error occurred while sending notification to IOS devices Error: Problem occurred during sending push notification(s) Edit Push Network... ________________________________ Variants: IOS APNS Failed 2 installations Android Succeeded 4 installations IOS APNS Failed 2 installations From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of S?bastien Blanc Sent: 29 January 2015 PM 12:18 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Envoy? de mon iPhone Le 29 janv. 2015 ? 07:29, Sekar, Harini > a ?crit : Hi, Thank u so much ? If I use Java sender client to send notification , then those activity will be listed in the History link in the Aero Gear Admin UI ? Yes , in the details you will even see it comes from the Java sender. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:37 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: Yes we are having proxy issue. How to set proxy for this APNS ? That's currently not supported on the Unified Push Server, but we track the requirement in a ticket: https://issues.jboss.org/browse/AGPUSH-306 We didn't have much users requesting this, since usually they delpoy the Unified Push Server where they have access to the internet. Otherwise the device registration would be hard :-) -Matthias From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:32 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: Hi , When I try to integrate the JAVA Apns I am getting this error ?Exception in thread "main" com.notnoop.exceptions.NetworkIOException: java.net.UnknownHostException: gateway.push.apple.com? weird, I just tried this code: https://gist.github.com/matzew/461fb3f6fb26cfc092e7 and it works. Wondering, are you behind a firewall or so ? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Sekar, Harini Sent: 29 January 2015 AM 10:25 To: Matthias Wessendorf Cc: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/1197ba5e/attachment-0001.html From matzew at apache.org Thu Jan 29 02:40:28 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 29 Jan 2015 08:40:28 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: is that from now ? how many devices do you have, for iOS? I guess two ? We had a bug with incorrect numbers. That is fixed in the upcoming 1.0.3 release On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini wrote: > It works. > > Then why this error occurred while sending notification to IOS devices > > > > Error: > > *Problem occurred during sending push notification(s)* > > *Edit Push Network... > * > ------------------------------ > > Variants: > > IOS APNS > > > Failed > > *2** installations* > > Android > > > Succeeded > > *4** installations* > > IOS APNS > > > Failed > > *2** installations* > > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *S?bastien Blanc > *Sent:* 29 January 2015 PM 12:18 > *To:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > > > Envoy? de mon iPhone > > > Le 29 janv. 2015 ? 07:29, Sekar, Harini a > ?crit : > > Hi, > > > > Thank u so much J > > If I use Java sender client to send notification , then those activity > will be listed in the History link in the Aero Gear Admin UI ? > > > > Yes , in the details you will even see it comes from the Java sender. > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:37 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: > > Yes we are having proxy issue. How to set proxy for this APNS ? > > > > That's currently not supported on the Unified Push Server, but we track > the requirement in a ticket: > > https://issues.jboss.org/browse/AGPUSH-306 > > > > We didn't have much users requesting this, since usually they delpoy > the Unified Push Server where they have access to the internet. Otherwise > the device registration would be hard :-) > > > > -Matthias > > > > > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:32 > > > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: > > Hi , > > > > When I try to integrate the JAVA Apns I am getting this error ?Exception > in thread "main" *com.notnoop.exceptions.NetworkIOException*: > *java.net.UnknownHostException*: gateway.push.apple.com? > > > > > > weird, I just tried this code: > > https://gist.github.com/matzew/461fb3f6fb26cfc092e7 > > > > > > and it works. Wondering, are you behind a firewall or so ? > > > > > > > > Thanks & Regards > > Harini S > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Sekar, Harini > *Sent:* 29 January 2015 AM 10:25 > *To:* Matthias Wessendorf > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > Hi, > > > > Do you require any ssl trusted certificate for aerogear ? > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 04:51 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > You are saying you are not getting push notifications delivered, even > after a reboot? I think there is something wrong with the certificate's > .p12 file. > > > > Do you have it locally ? If so, can you run a standalone test, using this > Java lib: > > https://github.com/notnoop/java-apns > > > > > > 1) get the APNs Servce: > > ApnsService service = > > APNS.newService() > > .withCert("/path/to/certificate.p12", "MyCertPassword") > > .withProductionDestination() // you said you are using production - > right ? otherwise it's Sandbox.... > > .build(); > > > > 2) get a token from the UI, ideally your own device, and send a push: > > String payload = APNS.newPayload().alertBody("Test test test").build(); > > String token = "your token goes here"; > > service.push(token, payload); > > > > > > That would help to isolate the issue. > > > > > > BTW. what version of the UPS are you running ? > > > > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: > > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > > > > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > 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/20150129/b73969e5/attachment-0001.html From harini.sekar at rntbci.com Thu Jan 29 03:32:10 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Thu, 29 Jan 2015 08:32:10 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C469319@UK-EX-MBX-005.NMCorp.Nissan.Biz> That?s great. When will be the new update will be released ? I want to know why sending push notification dint work in that particular time. Whether it problem with the AeroGear server or IOS certificate ? Yes only 2 IOS devices are there. When I try to register android in aero gear , in some cases it gets registered twice with different device token but they have same alias names(device uuid). Is this a bug ? For your better understanding I have attached the screen shot below [cid:image001.png at 01D03BCB.BC269770] From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 PM 01:10 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error is that from now ? how many devices do you have, for iOS? I guess two ? We had a bug with incorrect numbers. That is fixed in the upcoming 1.0.3 release On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini > wrote: It works. Then why this error occurred while sending notification to IOS devices Error: Problem occurred during sending push notification(s) Edit Push Network... ________________________________ Variants: IOS APNS Failed 2 installations Android Succeeded 4 installations IOS APNS Failed 2 installations From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of S?bastien Blanc Sent: 29 January 2015 PM 12:18 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Envoy? de mon iPhone Le 29 janv. 2015 ? 07:29, Sekar, Harini > a ?crit : Hi, Thank u so much ? If I use Java sender client to send notification , then those activity will be listed in the History link in the Aero Gear Admin UI ? Yes , in the details you will even see it comes from the Java sender. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:37 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: Yes we are having proxy issue. How to set proxy for this APNS ? That's currently not supported on the Unified Push Server, but we track the requirement in a ticket: https://issues.jboss.org/browse/AGPUSH-306 We didn't have much users requesting this, since usually they delpoy the Unified Push Server where they have access to the internet. Otherwise the device registration would be hard :-) -Matthias From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:32 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: Hi , When I try to integrate the JAVA Apns I am getting this error ?Exception in thread "main" com.notnoop.exceptions.NetworkIOException: java.net.UnknownHostException: gateway.push.apple.com? weird, I just tried this code: https://gist.github.com/matzew/461fb3f6fb26cfc092e7 and it works. Wondering, are you behind a firewall or so ? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Sekar, Harini Sent: 29 January 2015 AM 10:25 To: Matthias Wessendorf Cc: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ 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 *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/763cd45f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25534 bytes Desc: image001.png Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/763cd45f/attachment-0001.png From matzew at apache.org Thu Jan 29 03:38:08 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 29 Jan 2015 09:38:08 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C469319@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469319@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: On Thu, Jan 29, 2015 at 9:32 AM, Sekar, Harini wrote: > That?s great. When will be the new update will be released ? > 1.0.3 will be out in Feb. Here is the jIRA to track fixed and open issues: https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel > I want to know why sending push notification dint work in that particular > time. > > Whether it problem with the AeroGear server or IOS certificate ? > It works now, right ? Not sure what the actual issue was, tbh > > > Yes only 2 IOS devices are there. > > When I try to register android in aero gear , in some cases it gets > registered twice with different device token but they have same alias > names(device uuid). Is this a bug ? > > For your better understanding I have attached the screen shot below > that happens after uninstall. if you than reintall, it gets a new token from Google. So you have two tokens, but that is really one device. Not a big deal. AFTER sending the payload to Google, the response from there gives us those tokens that we can remove from the DB. With this being merged soon, we also clean up those tokens in the uninstall case: https://github.com/aerogear/aerogear-unifiedpush-server/pull/474 So, after the send, now, there should be only one. NOTE: for iOS we have a similar mechanism to clean up "invalid tokens", after a send (invalid means the user removed the iOS app or disabled push on the user settings_ HTH, Matthias > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 PM 01:10 > > *To:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > is that from now ? > > > > how many devices do you have, for iOS? I guess two ? We had a bug with > incorrect numbers. That is fixed in the upcoming 1.0.3 release > > > > On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini > wrote: > > It works. > > Then why this error occurred while sending notification to IOS devices > > > > Error: > > *Problem occurred during sending push notification(s)* > > *Edit Push Network... > * > ------------------------------ > > Variants: > > IOS APNS > > > Failed > > *2** installations* > > Android > > > Succeeded > > *4** installations* > > IOS APNS > > > Failed > > *2** installations* > > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *S?bastien Blanc > *Sent:* 29 January 2015 PM 12:18 > *To:* AeroGear Developer Mailing List > > *Subject:* Re: [aerogear-dev] iOS push error > > > > > > Envoy? de mon iPhone > > > Le 29 janv. 2015 ? 07:29, Sekar, Harini a > ?crit : > > Hi, > > > > Thank u so much J > > If I use Java sender client to send notification , then those activity > will be listed in the History link in the Aero Gear Admin UI ? > > > > Yes , in the details you will even see it comes from the Java sender. > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:37 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: > > Yes we are having proxy issue. How to set proxy for this APNS ? > > > > That's currently not supported on the Unified Push Server, but we track > the requirement in a ticket: > > https://issues.jboss.org/browse/AGPUSH-306 > > > > We didn't have much users requesting this, since usually they delpoy > the Unified Push Server where they have access to the internet. Otherwise > the device registration would be hard :-) > > > > -Matthias > > > > > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:32 > > > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: > > Hi , > > > > When I try to integrate the JAVA Apns I am getting this error ?Exception > in thread "main" *com.notnoop.exceptions.NetworkIOException*: > *java.net.UnknownHostException*: gateway.push.apple.com? > > > > > > weird, I just tried this code: > > https://gist.github.com/matzew/461fb3f6fb26cfc092e7 > > > > > > and it works. Wondering, are you behind a firewall or so ? > > > > > > > > Thanks & Regards > > Harini S > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Sekar, Harini > *Sent:* 29 January 2015 AM 10:25 > *To:* Matthias Wessendorf > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > Hi, > > > > Do you require any ssl trusted certificate for aerogear ? > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 04:51 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > You are saying you are not getting push notifications delivered, even > after a reboot? I think there is something wrong with the certificate's > .p12 file. > > > > Do you have it locally ? If so, can you run a standalone test, using this > Java lib: > > https://github.com/notnoop/java-apns > > > > > > 1) get the APNs Servce: > > ApnsService service = > > APNS.newService() > > .withCert("/path/to/certificate.p12", "MyCertPassword") > > .withProductionDestination() // you said you are using production - > right ? otherwise it's Sandbox.... > > .build(); > > > > 2) get a token from the UI, ideally your own device, and send a push: > > String payload = APNS.newPayload().alertBody("Test test test").build(); > > String token = "your token goes here"; > > service.push(token, payload); > > > > > > That would help to isolate the issue. > > > > > > BTW. what version of the UPS are you running ? > > > > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: > > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > > > > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > _______________________________________________ > 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 > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > 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/20150129/1bf0599b/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25534 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/1bf0599b/attachment-0001.png From harini.sekar at rntbci.com Thu Jan 29 03:49:46 2015 From: harini.sekar at rntbci.com (Sekar, Harini) Date: Thu, 29 Jan 2015 08:49:46 +0000 Subject: [aerogear-dev] iOS push error In-Reply-To: References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469319@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: <1998F0706E29344DAACDB185C0A06F9B188C46935F@UK-EX-MBX-005.NMCorp.Nissan.Biz> Sounds good. Also we tried to deploy the Aero Gear server in Virtual PC which is used only inside the our network. Aero Gear works only in localhost when we try to open it using the IP it is not working ? Do we need any signed SSL certificate to do so ? How to overcome this issue ? Currently , we have deployed aero gear in OpenShit. Later we have to move the same to our Virtual PC ? SSL by default By default the option "Require SSL" on Keycloak is enabled to make sure that UnifiedPush will run under SSL, except for localhost and Docker images. If you are deploying UPS on non-SSL environment, an exception like "request scheme: http ssl required" is expected. From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 PM 02:08 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error On Thu, Jan 29, 2015 at 9:32 AM, Sekar, Harini > wrote: That?s great. When will be the new update will be released ? 1.0.3 will be out in Feb. Here is the jIRA to track fixed and open issues: https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel I want to know why sending push notification dint work in that particular time. Whether it problem with the AeroGear server or IOS certificate ? It works now, right ? Not sure what the actual issue was, tbh Yes only 2 IOS devices are there. When I try to register android in aero gear , in some cases it gets registered twice with different device token but they have same alias names(device uuid). Is this a bug ? For your better understanding I have attached the screen shot below that happens after uninstall. if you than reintall, it gets a new token from Google. So you have two tokens, but that is really one device. Not a big deal. AFTER sending the payload to Google, the response from there gives us those tokens that we can remove from the DB. With this being merged soon, we also clean up those tokens in the uninstall case: https://github.com/aerogear/aerogear-unifiedpush-server/pull/474 So, after the send, now, there should be only one. NOTE: for iOS we have a similar mechanism to clean up "invalid tokens", after a send (invalid means the user removed the iOS app or disabled push on the user settings_ HTH, Matthias [cid:image001.png at 01D03BCE.50B008C0] From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 PM 01:10 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error is that from now ? how many devices do you have, for iOS? I guess two ? We had a bug with incorrect numbers. That is fixed in the upcoming 1.0.3 release On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini > wrote: It works. Then why this error occurred while sending notification to IOS devices Error: Problem occurred during sending push notification(s) Edit Push Network... ________________________________ Variants: IOS APNS Failed 2 installations Android Succeeded 4 installations IOS APNS Failed 2 installations From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of S?bastien Blanc Sent: 29 January 2015 PM 12:18 To: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Envoy? de mon iPhone Le 29 janv. 2015 ? 07:29, Sekar, Harini > a ?crit : Hi, Thank u so much ? If I use Java sender client to send notification , then those activity will be listed in the History link in the Aero Gear Admin UI ? Yes , in the details you will even see it comes from the Java sender. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:37 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: Yes we are having proxy issue. How to set proxy for this APNS ? That's currently not supported on the Unified Push Server, but we track the requirement in a ticket: https://issues.jboss.org/browse/AGPUSH-306 We didn't have much users requesting this, since usually they delpoy the Unified Push Server where they have access to the internet. Otherwise the device registration would be hard :-) -Matthias From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 29 January 2015 AM 11:32 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: Hi , When I try to integrate the JAVA Apns I am getting this error ?Exception in thread "main" com.notnoop.exceptions.NetworkIOException: java.net.UnknownHostException: gateway.push.apple.com? weird, I just tried this code: https://gist.github.com/matzew/461fb3f6fb26cfc092e7 and it works. Wondering, are you behind a firewall or so ? Thanks & Regards Harini S From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Sekar, Harini Sent: 29 January 2015 AM 10:25 To: Matthias Wessendorf Cc: AeroGear Developer Mailing List Subject: Re: [aerogear-dev] iOS push error Hi, Do you require any ssl trusted certificate for aerogear ? Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 04:51 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error You are saying you are not getting push notifications delivered, even after a reboot? I think there is something wrong with the certificate's .p12 file. Do you have it locally ? If so, can you run a standalone test, using this Java lib: https://github.com/notnoop/java-apns 1) get the APNs Servce: ApnsService service = APNS.newService() .withCert("/path/to/certificate.p12", "MyCertPassword") .withProductionDestination() // you said you are using production - right ? otherwise it's Sandbox.... .build(); 2) get a token from the UI, ideally your own device, and send a push: String payload = APNS.newPayload().alertBody("Test test test").build(); String token = "your token goes here"; service.push(token, payload); That would help to isolate the issue. BTW. what version of the UPS are you running ? On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: Hi Matthias , Have attached the screenshots of the problem I am facing. It was working till last Thursday (23/01/2015) and I was able to receive the notification too, later it started throwing this error. Kindly help me in sorting out this issue. Thanks & Regards, Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 28 January 2015 PM 01:21 To: Sekar, Harini Cc: AeroGear Developer Mailing List Subject: Re: iOS push error Hi Harini, > Yes , but still that warning is there. we do not (yet) clean up the warning, after the problem has been solved, however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) That said - does the push go through? Do you get a notification ? The warning itself is has a specific date (click on activity link to go to details). Here is an older error (on my test instance): https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 That error occured only on Jan 6th, but as said above, we do not yet clean that up -Matthias On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: Hello, It was working fine for one day. After that it started throwing the error. I am using free version of Openshit in this it doesn?t support custom ssl is this may be a problem ? ? Did you upload the correct .p12 file for the iOS variant? - Yes ? Or did you replace a development cert with a production cert ? ? No I am using oly production cert ? Did it work a few days ago? ? Yes it worked for only one day ? Did you try to reboot the instance via the openshift UI ? ? Yes , but still that warning is there. Thanks & Regards Harini S From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf Sent: 27 January 2015 PM 06:02 To: AeroGear Developer Mailing List; Sekar, Harini Subject: iOS push error Hi Harini, I opened a new thread for this to make it easier to follow up on this subject. I just tested my Push Server and iOS just worked fine. Here are a few questions: * Did you upload the correct .p12 file for the iOS variant? * Or did you replace a development cert with a production cert ? * Did it work a few days ago? * Did you try to reboot the instance via the openshift UI ? Thanks, Matthias On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: Hi guys, Have deployed the aerogear in openshit and push notification for IOS is not working Error : reason: Error sending payload to APNs server: sun.security.validator.ValidatorException: No trusted certificate found please help me sort this out Thanks & Regards Harini S -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ 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 *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** _______________________________________________ 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 *********************************************************************************************************** CONFIDENTIALITY NOTICE This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security at rntbci.com with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. RNTBCI and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks. RNTBCI is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection RNTBCI does not accept any liability. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them. *********************************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/b2db7c4f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25534 bytes Desc: image001.png Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/b2db7c4f/attachment-0001.png From matzew at apache.org Thu Jan 29 03:58:19 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 29 Jan 2015 09:58:19 +0100 Subject: [aerogear-dev] iOS push error In-Reply-To: <1998F0706E29344DAACDB185C0A06F9B188C46935F@UK-EX-MBX-005.NMCorp.Nissan.Biz> References: <1998F0706E29344DAACDB185C0A06F9B188BF64ABA@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C468D47@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691BC@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C4691C2@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469205@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469222@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46924A@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C469319@UK-EX-MBX-005.NMCorp.Nissan.Biz> <1998F0706E29344DAACDB185C0A06F9B188C46935F@UK-EX-MBX-005.NMCorp.Nissan.Biz> Message-ID: On Thu, Jan 29, 2015 at 9:49 AM, Sekar, Harini wrote: > Sounds good. > > Also we tried to deploy the Aero Gear server in Virtual PC which is used > only inside the our network. > > Aero Gear works only in localhost when we try to open it using the IP it > is not working ? > > Do we need any signed SSL certificate to do so ? How to overcome this > issue ? > yes, that is by design. You need to have a SSL cert for the HTTPS, when deploying on external interfaces We do have a docker based example for doing that, with a self-signed certificate: https://github.com/aerogear/dockerfiles/tree/master/wildfly/unifiedpush-wildfly Inside of the configuration data, there is some more details: https://github.com/aerogear/dockerfiles/blob/master/wildfly/configuration/certs/certificate.sh and the standalone.xml file, to reference the self signed certificate: https://github.com/aerogear/dockerfiles/blob/master/wildfly/configuration/xml/standalone-sample.xml > Currently , we have deployed aero gear in OpenShit. Later we have to move > the same to our Virtual PC ? > > > > *SSL by default* > > By default the option "Require SSL" on Keycloak is enabled to make sure > that UnifiedPush will run under SSL, except for *localhost* and *Docker* images. > If you are deploying UPS on non-SSL environment, an exception like "*request > scheme: http ssl required*" is expected. > > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 PM 02:08 > > *To:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 9:32 AM, Sekar, Harini > wrote: > > That?s great. When will be the new update will be released ? > > > > 1.0.3 will be out in Feb. Here is the jIRA to track fixed and open issues: > > > https://issues.jboss.org/browse/AGPUSH/fixforversion/12325082?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel > > > > I want to know why sending push notification dint work in that particular > time. > > Whether it problem with the AeroGear server or IOS certificate ? > > > > It works now, right ? Not sure what the actual issue was, tbh > > > > > > Yes only 2 IOS devices are there. > > When I try to register android in aero gear , in some cases it gets > registered twice with different device token but they have same alias > names(device uuid). Is this a bug ? > > For your better understanding I have attached the screen shot below > > > > that happens after uninstall. if you than reintall, it gets a new token > from Google. > > So you have two tokens, but that is really one device. Not a big deal. > > > > AFTER sending the payload to Google, the response from there gives us > those tokens that we can remove from the DB. With this being merged soon, > we also clean up those tokens in the uninstall case: > > https://github.com/aerogear/aerogear-unifiedpush-server/pull/474 > > > > So, after the send, now, there should be only one. > > > > > > > > NOTE: for iOS we have a similar mechanism to clean up "invalid tokens", > after a send (invalid means the user removed the iOS app or disabled push > on the user settings_ > > > > HTH, > > Matthias > > > > > > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 PM 01:10 > > > *To:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > is that from now ? > > > > how many devices do you have, for iOS? I guess two ? We had a bug with > incorrect numbers. That is fixed in the upcoming 1.0.3 release > > > > On Thu, Jan 29, 2015 at 8:03 AM, Sekar, Harini > wrote: > > It works. > > Then why this error occurred while sending notification to IOS devices > > > > Error: > > *Problem occurred during sending push notification(s)* > > *Edit Push Network... > * > ------------------------------ > > Variants: > > IOS APNS > > > Failed > > *2 installations* > > Android > > > Succeeded > > *4 installations* > > IOS APNS > > > Failed > > *2 installations* > > > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *S?bastien Blanc > *Sent:* 29 January 2015 PM 12:18 > *To:* AeroGear Developer Mailing List > > *Subject:* Re: [aerogear-dev] iOS push error > > > > > > Envoy? de mon iPhone > > > Le 29 janv. 2015 ? 07:29, Sekar, Harini a > ?crit : > > Hi, > > > > Thank u so much J > > If I use Java sender client to send notification , then those activity > will be listed in the History link in the Aero Gear Admin UI ? > > > > Yes , in the details you will even see it comes from the Java sender. > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:37 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 7:03 AM, Sekar, Harini > wrote: > > Yes we are having proxy issue. How to set proxy for this APNS ? > > > > That's currently not supported on the Unified Push Server, but we track > the requirement in a ticket: > > https://issues.jboss.org/browse/AGPUSH-306 > > > > We didn't have much users requesting this, since usually they delpoy > the Unified Push Server where they have access to the internet. Otherwise > the device registration would be hard :-) > > > > -Matthias > > > > > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 29 January 2015 AM 11:32 > > > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > > > > > On Thu, Jan 29, 2015 at 6:00 AM, Sekar, Harini > wrote: > > Hi , > > > > When I try to integrate the JAVA Apns I am getting this error ?Exception > in thread "main" *com.notnoop.exceptions.NetworkIOException*: > *java.net.UnknownHostException*: gateway.push.apple.com? > > > > > > weird, I just tried this code: > > https://gist.github.com/matzew/461fb3f6fb26cfc092e7 > > > > > > and it works. Wondering, are you behind a firewall or so ? > > > > > > > > Thanks & Regards > > Harini S > > > > *From:* aerogear-dev-bounces at lists.jboss.org [mailto: > aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Sekar, Harini > *Sent:* 29 January 2015 AM 10:25 > *To:* Matthias Wessendorf > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: [aerogear-dev] iOS push error > > > > Hi, > > > > Do you require any ssl trusted certificate for aerogear ? > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com > ] *On Behalf Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 04:51 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > You are saying you are not getting push notifications delivered, even > after a reboot? I think there is something wrong with the certificate's > .p12 file. > > > > Do you have it locally ? If so, can you run a standalone test, using this > Java lib: > > https://github.com/notnoop/java-apns > > > > > > 1) get the APNs Servce: > > ApnsService service = > > APNS.newService() > > .withCert("/path/to/certificate.p12", "MyCertPassword") > > .withProductionDestination() // you said you are using production - > right ? otherwise it's Sandbox.... > > .build(); > > > > 2) get a token from the UI, ideally your own device, and send a push: > > String payload = APNS.newPayload().alertBody("Test test test").build(); > > String token = "your token goes here"; > > service.push(token, payload); > > > > > > That would help to isolate the issue. > > > > > > BTW. what version of the UPS are you running ? > > > > > > On Wed, Jan 28, 2015 at 11:22 AM, Sekar, Harini > wrote: > > Hi Matthias , > > > > Have attached the screenshots of the problem I am facing. > > It was working till last Thursday (23/01/2015) and I was able to receive > the notification too, later it started throwing this error. > > Kindly help me in sorting out this issue. > > > > > > > > > > Thanks & Regards, > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 28 January 2015 PM 01:21 > *To:* Sekar, Harini > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: iOS push error > > > > Hi Harini, > > > > > Yes , but still that warning is there. > > > > we do not (yet) clean up the warning, after the problem has been solved, > however we plan to do so (see https://issues.jboss.org/browse/AGPUSH-1248) > > > > That said - does the push go through? Do you get a notification ? The > warning itself is has a specific date (click on activity link to go to > details). > > > > Here is an older error (on my test instance): > > > https://www.dropbox.com/s/nlrr9kd5dkfuae1/Screen%20Shot%202015-01-28%20at%2008.49.44.png?dl=0 > > > > That error occured only on Jan 6th, but as said above, we do not yet clean > that up > > > > > > -Matthias > > > > On Wed, Jan 28, 2015 at 4:23 AM, Sekar, Harini > wrote: > > Hello, > > > > It was working fine for one day. After that it started throwing the error. > > I am using free version of Openshit in this it doesn?t support custom ssl > is this may be a problem ? > > ? Did you upload the correct .p12 file for the iOS variant? - Yes > > ? Or did you replace a development cert with a production cert > ? ? No I am using oly production cert > > ? Did it work a few days ago? ? Yes it worked for only one day > > ? Did you try to reboot the instance via the openshift UI ? ? Yes > , but still that warning is there. > > > > Thanks & Regards > > Harini S > > > > *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf > Of *Matthias Wessendorf > *Sent:* 27 January 2015 PM 06:02 > *To:* AeroGear Developer Mailing List; Sekar, Harini > *Subject:* iOS push error > > > > Hi Harini, > > > > I opened a new thread for this to make it easier to follow up on this > subject. > > > > I just tested my Push Server and iOS just worked fine. Here are a few > questions: > > > > * Did you upload the correct .p12 file for the iOS variant? > > * Or did you replace a development cert with a production cert ? > > * Did it work a few days ago? > > * Did you try to reboot the instance via the openshift UI ? > > > > Thanks, > > Matthias > > > > > > > > On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini > wrote: > > Hi guys, > > Have deployed the aerogear in openshit and push notification for IOS is > not working > Error : > reason: Error sending payload to APNs server: > sun.security.validator.ValidatorException: No trusted certificate found > > please help me sort this out > > Thanks & Regards > Harini S > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > _______________________________________________ > 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 > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > > _______________________________________________ > 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 > > > *********************************************************************************************************** > CONFIDENTIALITY NOTICE > > This message is for the named person's use only. It may contain > confidential, proprietary or legally privileged information. > > If you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and notify us > by email to email.security at rntbci.com with a copy of this message. You > must not, directly or indirectly, use, disclose, distribute, print or copy > any part of this message if you are not the intended recipient. RNTBCI and > any of its subsidiaries each reserves the right to monitor all e-mail > communications through its networks. > > RNTBCI is neither liable for the proper, complete transmission of the > information contained in this communication nor any delay in its receipt. > This email was scanned for the presence of computer viruses. In the > unfortunate event of infection RNTBCI does not accept any liability. > > Any views expressed in this message are those of the individual sender, > except where the message states otherwise and the sender is authorised to > state them. > > *********************************************************************************************************** > > _______________________________________________ > 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/20150129/24f9f1e7/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25534 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/24f9f1e7/attachment-0001.png From scm.blanc at gmail.com Thu Jan 29 04:52:43 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 29 Jan 2015 10:52:43 +0100 Subject: [aerogear-dev] Amazon Device Messaging (ADM) support on UPS Message-ID: Hi Folks, I've just submitted a PR to support ADM (Amazon Device Messaging) on UPS[1] , yay ! A few notes : - The Java ADM connector is also managed by AeroGear [2], it's not yet on Maven Central, so you will need to clone it and build it - The Client SDK (and updated Cordova Plugin) is not yet available but to make this PR testable, we have adapted a Cordova App that Amazon use as sample to show ADM, this fork will register with UPS [3], this app contains also all the instructions to get started - About the client SDK, FireOS (Amazon's OS) is almost "just" Android, so we should be able to reuse most of our Android Lib [4], we jsut need to remove the GCM part and use the ADM library instead. I will start work on that today and ping our Android gods to see which is the best way to do that. So anyone who has a Amazon Tablet, please give it a shot and report on the PR ! Have fun ! Sebi [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/480 [2] https://github.com/aerogear/java-adm [3] https://github.com/sebastienblanc/adm-cordova-sample -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/d74a0873/attachment.html From kpiwko at redhat.com Thu Jan 29 06:39:00 2015 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 29 Jan 2015 12:39:00 +0100 Subject: [aerogear-dev] UPS unit tests In-Reply-To: <54C8F323.5030004@redhat.com> References: <3B3905CB-EF4D-408E-88AD-8C65978EBF4C@redhat.com> <54BFD3F2.6040906@redhat.com> <54C8F323.5030004@redhat.com> Message-ID: <1422531540.12188.27.camel@localhost> > Totally out of the blue, but is there a way to annotate test classes > to make them run iff there is a flag set? > If you put integration-tests in a different folder then you will also > have to tell maven about them in the testSourceSet stanza which will > cause them to get run anyway. (And if they aren't in source set for > the default profile I'm not sure IDEs will pick them up)(Unless there > is a third source set type I'm not familiar with) Yes, this is possible. You need to group your tests and then maven surefire can reference these groups - note that IDE will not pick surefire configuration but you can still set groups and excluded groups by system properties in Test Configuration. That's exactly what we are doing in UPS testsuite, for instance we don't want to execute UI tests by default: More here: https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/pom.xml#L60 https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/pom.xml#L275-L276 https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/src/test/java/org/jboss/aerogear/unifiedpush/admin/ui/test/PushServerAdminUiTestCase.java#L41 Karel From corinnekrych at gmail.com Thu Jan 29 06:41:36 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 29 Jan 2015 12:41:36 +0100 Subject: [aerogear-dev] iOS team meeting In-Reply-To: <7F1871C2-CEA2-4DE6-81F6-9762071650BE@gmail.com> References: <7F1871C2-CEA2-4DE6-81F6-9762071650BE@gmail.com> Message-ID: Hello guys, We're busy getting iOS 2.1 release out this week, watch out for the announcement :) So we're going to reschedule this iOS meeting for our Tuesday 3rd February same time 4pm (+1GMT) See you all there ++ Corinne On 28 January 2015 at 09:23, Corinne Krych wrote: > Hello All > > Out next iOS meeting will be on Thursday 29th January 4pm (GMT+1), here is > the agenda: > http://oksoclap.com/p/iOS-meeting-29thJanuary2015 > > Feel free to add topics, see you all there > > ++ > Corinne -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/57e152d1/attachment.html From matzew at apache.org Thu Jan 29 09:35:42 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 29 Jan 2015 15:35:42 +0100 Subject: [aerogear-dev] Parent-release: 0.2.12 Message-ID: Hi, our friends from Keycloak shipped their 1.1.0.Final. To reflect that on our UPS master branch, we need a released parent. The staging repo for it is here: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4729/ The main diff between .11 and .12 is simply the new KC version. Let me know if you have any questions, otherwise I'd like to release it over the weekend -- 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/20150129/a095f54c/attachment.html From scm.blanc at gmail.com Thu Jan 29 09:43:31 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 29 Jan 2015 15:43:31 +0100 Subject: [aerogear-dev] Parent-release: 0.2.12 In-Reply-To: References: Message-ID: +1 On Thu, Jan 29, 2015 at 3:35 PM, Matthias Wessendorf wrote: > Hi, > > our friends from Keycloak shipped their 1.1.0.Final. To reflect that on > our UPS master branch, we need a released parent. > > The staging repo for it is here: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4729/ > > The main diff between .11 and .12 is simply the new KC version. > > Let me know if you have any questions, otherwise I'd like to release it > over the weekend > > -- > 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/20150129/650fc56d/attachment.html From scm.blanc at gmail.com Thu Jan 29 11:15:46 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 29 Jan 2015 17:15:46 +0100 Subject: [aerogear-dev] Steps for adding a new Push Platform to the UnifiedPush Server Message-ID: Hi folk ! While I was adding ADM support to UPS I took some notes on the different steps. You can check these notes here : https://gist.github.com/sebastienblanc/9615439c67968ecb92da The purpose is to help anyone that would like to add a new Push Platform. Maybe, we could also add that somewhere on aerogear.org in the contribute section. Enjoy (and report if you find weird things in the Gist) Sebi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150129/c91490cf/attachment.html From daniel at passos.me Thu Jan 29 12:51:20 2015 From: daniel at passos.me (Daniel Passos) Date: Thu, 29 Jan 2015 15:51:20 -0200 Subject: [aerogear-dev] Parent-release: 0.2.12 In-Reply-To: References: Message-ID: +1 On Thu, Jan 29, 2015 at 12:35 PM, Matthias Wessendorf wrote: > Hi, > > our friends from Keycloak shipped their 1.1.0.Final. To reflect that on > our UPS master branch, we need a released parent. > > The staging repo for it is here: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4729/ > > The main diff between .11 and .12 is simply the new KC version. > > Let me know if you have any questions, otherwise I'd like to release it > over the weekend > > -- > 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/20150129/a5f21017/attachment-0001.html From daniel at passos.me Thu Jan 29 12:52:40 2015 From: daniel at passos.me (Daniel Passos) Date: Thu, 29 Jan 2015 15:52:40 -0200 Subject: [aerogear-dev] Steps for adding a new Push Platform to the UnifiedPush Server In-Reply-To: References: Message-ID: Nice "article". +1 to add it on ag.org as a doc or a blog post -- Passos On Thu, Jan 29, 2015 at 2:15 PM, Sebastien Blanc wrote: > Hi folk ! > > While I was adding ADM support to UPS I took some notes on the different > steps. You can check these notes here : > https://gist.github.com/sebastienblanc/9615439c67968ecb92da > > The purpose is to help anyone that would like to add a new Push Platform. > > Maybe, we could also add that somewhere on aerogear.org in the contribute > section. > > Enjoy (and report if you find weird things in the Gist) > > Sebi > > > _______________________________________________ > 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/20150129/345434be/attachment.html From bruno at abstractj.org Thu Jan 29 19:53:26 2015 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 29 Jan 2015 16:53:26 -0800 (PST) Subject: [aerogear-dev] Parent-release: 0.2.12 In-Reply-To: References: Message-ID: <1422579206193.c82589df@Nodemailer> Ship it ? abstractj PGP: 0x84DC9914 On Thu, Jan 29, 2015 at 12:35 PM, Matthias Wessendorf wrote: > Hi, > our friends from Keycloak shipped their 1.1.0.Final. To reflect that on our > UPS master branch, we need a released parent. > The staging repo for it is here: > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4729/ > The main diff between .11 and .12 is simply the new KC version. > Let me know if you have any questions, otherwise I'd like to release it > over the weekend > -- > 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/20150129/0be296ef/attachment.html From matzew at apache.org Fri Jan 30 02:47:04 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 30 Jan 2015 08:47:04 +0100 Subject: [aerogear-dev] Parent-release: 0.2.12 In-Reply-To: <1422579206193.c82589df@Nodemailer> References: <1422579206193.c82589df@Nodemailer> Message-ID: Thanks for voting! I have clicked the button! Once the pom is available on maven central, I will do a PR against master of UPS -Matthias On Fri, Jan 30, 2015 at 1:53 AM, Bruno Oliveira wrote: > Ship it > > ? > > abstractj > PGP: 0x84DC9914 > > > On Thu, Jan 29, 2015 at 12:35 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> our friends from Keycloak shipped their 1.1.0.Final. To reflect that on >> our UPS master branch, we need a released parent. >> >> The staging repo for it is here: >> >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4729/ >> >> The main diff between .11 and .12 is simply the new KC version. >> >> Let me know if you have any questions, otherwise I'd like to release it >> over the weekend >> >> -- >> 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 > -- 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/20150130/06dc9031/attachment.html From corinnekrych at gmail.com Fri Jan 30 04:15:26 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 30 Jan 2015 10:15:26 +0100 Subject: [aerogear-dev] Polishing our Jedi demo app for sync Message-ID: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> Hello All, For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld demo which do a great job to demo what we want to show in alpha1. Some small suggestions for the flow and look and feel: - could we have a first screen like a list of jedi (for now only one value i.e.: Luke is available). - could we have a list of hobbies as tableview with possibilities to add remove some hobbies? - could we have an update button so we can ?batch? input fields changes together? - does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). The button will be usefull for next release, but maybe for this one we can remove it. - last but not least, would it be possible to scheme it with a jedi theme: dark colors, stars, light blue colors? maybe @agalante can come up with some nice galaxy theme? On iOS side i?ve added AGIOS-358 to track those improving UI items (liked to epic AGIOS-350). I think we ca ?polish? the demo app without too much work involved. wdyt guys? ++ Corinne From daniel.bevenius at gmail.com Fri Jan 30 04:46:26 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Fri, 30 Jan 2015 10:46:26 +0100 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> Message-ID: I like the suggestions. The only concern would be having time to implement this. >does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). This was mostly for manually testing that we could disconnect from the server and then reconnect and continue working. But I think we should remove this for the demo as it think this will require more testing be be stable. Just for your information, we are currently making changes to the server side[1] to support different types of diffs/patches. The first type added, apart from the current DiffMatchPatch, is JSON Patch. So when developing the client libs/testing please use the branch mentioned in [1] which also contains links to how to start the servers. [1] https://issues.jboss.org/browse/AGSYNC-24 On 30 January 2015 at 10:15, Corinne Krych wrote: > Hello All, > > For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld > demo which do a great job to demo what we want to show in alpha1. > Some small suggestions for the flow and look and feel: > > - could we have a first screen like a list of jedi (for now only one value > i.e.: Luke is available). > - could we have a list of hobbies as tableview with possibilities to add > remove some hobbies? > - could we have an update button so we can ?batch? input fields changes > together? > - does the ?disconnect? button make sense for this alpha1 (as we don?t > demo offline support). The button will be usefull for next release, but > maybe for this one we can remove it. > - last but not least, would it be possible to scheme it with a jedi theme: > dark colors, stars, light blue colors? maybe @agalante can come up with > some nice galaxy theme? > > On iOS side i?ve added AGIOS-358 to track those improving UI items (liked > to epic AGIOS-350). I think we ca ?polish? the demo app without too much > work involved. > > wdyt guys? > > ++ > 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/20150130/4fe2817b/attachment.html From corinnekrych at gmail.com Fri Jan 30 05:46:13 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 30 Jan 2015 11:46:13 +0100 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> Message-ID: Let's say if it's not for alpha1, it will be alpha2 :) I agree we should based Jedi demo on json-patch approach I've created AGIOS-359 to move demo to that new approach (linked to ios client impl of json-patch) ++ Corinne On 30 January 2015 at 10:46, Daniel Bevenius wrote: > I like the suggestions. The only concern would be having time to implement > this. > > >does the ?disconnect? button make sense for this alpha1 (as we don?t > demo offline support). > This was mostly for manually testing that we could disconnect from the > server and then reconnect and continue working. But I think we should > remove this for the demo as it think this will require more testing be be > stable. > > Just for your information, we are currently making changes to the server > side[1] to support different types of diffs/patches. The first type added, > apart from the current DiffMatchPatch, is JSON Patch. So when developing > the client libs/testing please use the branch mentioned in [1] which also > contains links to how to start the servers. > > [1] https://issues.jboss.org/browse/AGSYNC-24 > > On 30 January 2015 at 10:15, Corinne Krych wrote: > >> Hello All, >> >> For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld >> demo which do a great job to demo what we want to show in alpha1. >> Some small suggestions for the flow and look and feel: >> >> - could we have a first screen like a list of jedi (for now only one >> value i.e.: Luke is available). >> - could we have a list of hobbies as tableview with possibilities to add >> remove some hobbies? >> - could we have an update button so we can ?batch? input fields changes >> together? >> - does the ?disconnect? button make sense for this alpha1 (as we don?t >> demo offline support). The button will be usefull for next release, but >> maybe for this one we can remove it. >> - last but not least, would it be possible to scheme it with a jedi >> theme: dark colors, stars, light blue colors? maybe @agalante can come up >> with some nice galaxy theme? >> >> On iOS side i?ve added AGIOS-358 to track those improving UI items (liked >> to epic AGIOS-350). I think we ca ?polish? the demo app without too much >> work involved. >> >> wdyt guys? >> >> ++ >> 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/20150130/924aec35/attachment-0001.html From agalante at redhat.com Fri Jan 30 07:37:07 2015 From: agalante at redhat.com (Andres Galante) Date: Fri, 30 Jan 2015 07:37:07 -0500 (EST) Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> Message-ID: <1994724724.1175688.1422621427179.JavaMail.zimbra@redhat.com> yay! 2015 just started and this might be the funnest project of the year. Is this based on the same hello-worold Contact list app we have? if there are differences, can you send me a screen capture of the new things in the app? Thanks a lot, Andr?s ----- Original Message ----- From: "Corinne Krych" To: "AeroGear Developer Mailing List" Sent: Friday, January 30, 2015 6:15:26 AM Subject: [aerogear-dev] Polishing our Jedi demo app for sync Hello All, For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld demo which do a great job to demo what we want to show in alpha1. Some small suggestions for the flow and look and feel: - could we have a first screen like a list of jedi (for now only one value i.e.: Luke is available). - could we have a list of hobbies as tableview with possibilities to add remove some hobbies? - could we have an update button so we can ?batch? input fields changes together? - does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). The button will be usefull for next release, but maybe for this one we can remove it. - last but not least, would it be possible to scheme it with a jedi theme: dark colors, stars, light blue colors? maybe @agalante can come up with some nice galaxy theme? On iOS side i?ve added AGIOS-358 to track those improving UI items (liked to epic AGIOS-350). I think we ca ?polish? the demo app without too much work involved. wdyt guys? ++ Corinne _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev From corinnekrych at gmail.com Fri Jan 30 08:04:54 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 30 Jan 2015 14:04:54 +0100 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: <1994724724.1175688.1422621427179.JavaMail.zimbra@redhat.com> References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> <1994724724.1175688.1422621427179.JavaMail.zimbra@redhat.com> Message-ID: @andres for now it?s really a helloworld app, there isn?t much than just the screen below. The goal of the app is to show sync between several installation of the app: across devices, users As suggested as we could have 2 screens: - one with a list of Jedis - one to view a jedii and add hobbies to his characters. we want to keep this app, hello world format, it?s not a show case app like contact (we?ll have another one) but with some icons and themes it could be much more fun :) > On 30 Jan 2015, at 13:37, Andres Galante wrote: > > yay! 2015 just started and this might be the funnest project of the year. > > Is this based on the same hello-worold Contact list app we have? > if there are differences, can you send me a screen capture of the new things in the app? > > Thanks a lot, > > Andr?s > > > ----- Original Message ----- > From: "Corinne Krych" > To: "AeroGear Developer Mailing List" > Sent: Friday, January 30, 2015 6:15:26 AM > Subject: [aerogear-dev] Polishing our Jedi demo app for sync > > Hello All, > > For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld demo which do a great job to demo what we want to show in alpha1. > Some small suggestions for the flow and look and feel: > > - could we have a first screen like a list of jedi (for now only one value i.e.: Luke is available). > - could we have a list of hobbies as tableview with possibilities to add remove some hobbies? > - could we have an update button so we can ?batch? input fields changes together? > - does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). The button will be usefull for next release, but maybe for this one we can remove it. > - last but not least, would it be possible to scheme it with a jedi theme: dark colors, stars, light blue colors? maybe @agalante can come up with some nice galaxy theme? > > On iOS side i?ve added AGIOS-358 to track those improving UI items (liked to epic AGIOS-350). I think we ca ?polish? the demo app without too much work involved. > > wdyt guys? > > ++ > 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/20150130/6f79fa97/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-3.png Type: image/png Size: 62382 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150130/6f79fa97/attachment-0001.png From lholmqui at redhat.com Fri Jan 30 08:21:14 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Fri, 30 Jan 2015 08:21:14 -0500 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> Message-ID: <0744647C-108B-4D47-B465-282A9E5A4756@redhat.com> i?m currently updating the JS version to use json-patch > On Jan 30, 2015, at 5:46 AM, Corinne Krych wrote: > > Let's say if it's not for alpha1, it will be alpha2 :) > > I agree we should based Jedi demo on json-patch approach > I've created AGIOS-359 to move demo to that new approach (linked to ios client impl of json-patch) > > ++ > Corinne > > > On 30 January 2015 at 10:46, Daniel Bevenius > wrote: > I like the suggestions. The only concern would be having time to implement this. > > >does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). > This was mostly for manually testing that we could disconnect from the server and then reconnect and continue working. But I think we should remove this for the demo as it think this will require more testing be be stable. > > Just for your information, we are currently making changes to the server side[1] to support different types of diffs/patches. The first type added, apart from the current DiffMatchPatch, is JSON Patch. So when developing the client libs/testing please use the branch mentioned in [1] which also contains links to how to start the servers. > > [1] https://issues.jboss.org/browse/AGSYNC-24 > > On 30 January 2015 at 10:15, Corinne Krych > wrote: > Hello All, > > For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld demo which do a great job to demo what we want to show in alpha1. > Some small suggestions for the flow and look and feel: > > - could we have a first screen like a list of jedi (for now only one value i.e.: Luke is available). > - could we have a list of hobbies as tableview with possibilities to add remove some hobbies? > - could we have an update button so we can ?batch? input fields changes together? > - does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). The button will be usefull for next release, but maybe for this one we can remove it. > - last but not least, would it be possible to scheme it with a jedi theme: dark colors, stars, light blue colors? maybe @agalante can come up with some nice galaxy theme? > > On iOS side i?ve added AGIOS-358 to track those improving UI items (liked to epic AGIOS-350). I think we ca ?polish? the demo app without too much work involved. > > wdyt guys? > > ++ > 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 > > _______________________________________________ > 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/20150130/907cde21/attachment.html From corinnekrych at gmail.com Fri Jan 30 08:31:54 2015 From: corinnekrych at gmail.com (Corinne Krych) Date: Fri, 30 Jan 2015 14:31:54 +0100 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: <0744647C-108B-4D47-B465-282A9E5A4756@redhat.com> References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> <0744647C-108B-4D47-B465-282A9E5A4756@redhat.com> Message-ID: @andres here are the JIRA for sync demo: Epic iOS Demo https://issues.jboss.org/browse/AGIOS-350 Ticket AGIOS-258 Enhance UI for jedi Epic Android Demo https://issues.jboss.org/browse/AGDROID-369 todo create a ticket linked to that epic Epic Android Demo https://issues.jboss.org/browse/AGJS-273 todo create a ticket linked to that epic > On 30 Jan 2015, at 14:21, Lucas Holmquist wrote: > > i?m currently updating the JS version to use json-patch >> On Jan 30, 2015, at 5:46 AM, Corinne Krych wrote: >> >> Let's say if it's not for alpha1, it will be alpha2 :) >> >> I agree we should based Jedi demo on json-patch approach >> I've created AGIOS-359 to move demo to that new approach (linked to ios client impl of json-patch) >> >> ++ >> Corinne >> >> >> On 30 January 2015 at 10:46, Daniel Bevenius wrote: >> I like the suggestions. The only concern would be having time to implement this. >> >> >does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). >> This was mostly for manually testing that we could disconnect from the server and then reconnect and continue working. But I think we should remove this for the demo as it think this will require more testing be be stable. >> >> Just for your information, we are currently making changes to the server side[1] to support different types of diffs/patches. The first type added, apart from the current DiffMatchPatch, is JSON Patch. So when developing the client libs/testing please use the branch mentioned in [1] which also contains links to how to start the servers. >> >> [1] https://issues.jboss.org/browse/AGSYNC-24 >> >> On 30 January 2015 at 10:15, Corinne Krych wrote: >> Hello All, >> >> For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld demo which do a great job to demo what we want to show in alpha1. >> Some small suggestions for the flow and look and feel: >> >> - could we have a first screen like a list of jedi (for now only one value i.e.: Luke is available). >> - could we have a list of hobbies as tableview with possibilities to add remove some hobbies? >> - could we have an update button so we can ?batch? input fields changes together? >> - does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). The button will be usefull for next release, but maybe for this one we can remove it. >> - last but not least, would it be possible to scheme it with a jedi theme: dark colors, stars, light blue colors? maybe @agalante can come up with some nice galaxy theme? >> >> On iOS side i?ve added AGIOS-358 to track those improving UI items (liked to epic AGIOS-350). I think we ca ?polish? the demo app without too much work involved. >> >> wdyt guys? >> >> ++ >> 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 matzew at apache.org Fri Jan 30 08:38:18 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 30 Jan 2015 14:38:18 +0100 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> <1994724724.1175688.1422621427179.JavaMail.zimbra@redhat.com> Message-ID: Hi, we have different epics for a demo, based on platform. I just created this one, to basically reference to the different platforms: https://issues.jboss.org/browse/AGSYNC-29 For a second release (later this year, likely in fall), it would be good to have some polished and improved UX - but not now. To have this as a reminder I listed this ticket underneath: https://issues.jboss.org/browse/AGSYNC-30 but that's also not relevant for now. At least that's my understanding. Dan, correct me if I am wrong On Fri, Jan 30, 2015 at 2:04 PM, Corinne Krych wrote: > @andres for now it?s really a helloworld app, there isn?t much than just > the screen below. > The goal of the app is to show sync between several installation of the > app: across devices, users > > As suggested as we could have 2 screens: > - one with a list of Jedis > - one to view a jedii and add hobbies to his characters. > > we want to keep this app, hello world format, it?s not a show case app > like contact (we?ll have another one) but with some icons and themes it > could be much more fun :) > > > > > On 30 Jan 2015, at 13:37, Andres Galante wrote: > > yay! 2015 just started and this might be the funnest project of the year. > > Is this based on the same hello-worold Contact list app we have? > if there are differences, can you send me a screen capture of the new > things in the app? > > Thanks a lot, > > Andr?s > > > ----- Original Message ----- > From: "Corinne Krych" > To: "AeroGear Developer Mailing List" > Sent: Friday, January 30, 2015 6:15:26 AM > Subject: [aerogear-dev] Polishing our Jedi demo app for sync > > Hello All, > > For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld > demo which do a great job to demo what we want to show in alpha1. > Some small suggestions for the flow and look and feel: > > - could we have a first screen like a list of jedi (for now only one value > i.e.: Luke is available). > - could we have a list of hobbies as tableview with possibilities to add > remove some hobbies? > - could we have an update button so we can ?batch? input fields changes > together? > - does the ?disconnect? button make sense for this alpha1 (as we don?t > demo offline support). The button will be usefull for next release, but > maybe for this one we can remove it. > - last but not least, would it be possible to scheme it with a jedi theme: > dark colors, stars, light blue colors? maybe @agalante can come up with > some nice galaxy theme? > > On iOS side i?ve added AGIOS-358 to track those improving UI items (liked > to epic AGIOS-350). I think we ca ?polish? the demo app without too much > work involved. > > wdyt guys? > > ++ > 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 > > > > _______________________________________________ > 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/20150130/fe49b142/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-3.png Type: image/png Size: 62382 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150130/fe49b142/attachment-0001.png From daniel.bevenius at gmail.com Fri Jan 30 08:43:19 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Fri, 30 Jan 2015 14:43:19 +0100 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> <1994724724.1175688.1422621427179.JavaMail.zimbra@redhat.com> Message-ID: >For a second release (later this year, likely in fall), it would be good to have some polished and improved UX - but not now. Yeah, unless this is something that can be provide in a very short time I think it might have to be pushed to a later release. The alpha1 release is scheduled for the end of Feb, just to give Andres an idea of the time frame. On 30 January 2015 at 14:38, Matthias Wessendorf wrote: > Hi, > > we have different epics for a demo, based on platform. I just created this > one, to basically reference to the different platforms: > https://issues.jboss.org/browse/AGSYNC-29 > > For a second release (later this year, likely in fall), it would be good > to have some polished and improved UX - but not now. > > To have this as a reminder I listed this ticket underneath: > https://issues.jboss.org/browse/AGSYNC-30 > > but that's also not relevant for now. At least that's my understanding. > Dan, correct me if I am wrong > > On Fri, Jan 30, 2015 at 2:04 PM, Corinne Krych > wrote: > >> @andres for now it?s really a helloworld app, there isn?t much than just >> the screen below. >> The goal of the app is to show sync between several installation of the >> app: across devices, users >> >> As suggested as we could have 2 screens: >> - one with a list of Jedis >> - one to view a jedii and add hobbies to his characters. >> >> we want to keep this app, hello world format, it?s not a show case app >> like contact (we?ll have another one) but with some icons and themes it >> could be much more fun :) >> >> >> >> >> On 30 Jan 2015, at 13:37, Andres Galante wrote: >> >> yay! 2015 just started and this might be the funnest project of the year. >> >> Is this based on the same hello-worold Contact list app we have? >> if there are differences, can you send me a screen capture of the new >> things in the app? >> >> Thanks a lot, >> >> Andr?s >> >> >> ----- Original Message ----- >> From: "Corinne Krych" >> To: "AeroGear Developer Mailing List" >> Sent: Friday, January 30, 2015 6:15:26 AM >> Subject: [aerogear-dev] Polishing our Jedi demo app for sync >> >> Hello All, >> >> For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld >> demo which do a great job to demo what we want to show in alpha1. >> Some small suggestions for the flow and look and feel: >> >> - could we have a first screen like a list of jedi (for now only one >> value i.e.: Luke is available). >> - could we have a list of hobbies as tableview with possibilities to add >> remove some hobbies? >> - could we have an update button so we can ?batch? input fields changes >> together? >> - does the ?disconnect? button make sense for this alpha1 (as we don?t >> demo offline support). The button will be usefull for next release, but >> maybe for this one we can remove it. >> - last but not least, would it be possible to scheme it with a jedi >> theme: dark colors, stars, light blue colors? maybe @agalante can come up >> with some nice galaxy theme? >> >> On iOS side i?ve added AGIOS-358 to track those improving UI items (liked >> to epic AGIOS-350). I think we ca ?polish? the demo app without too much >> work involved. >> >> wdyt guys? >> >> ++ >> 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 >> >> >> >> _______________________________________________ >> 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/20150130/e069509f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-3.png Type: image/png Size: 62382 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150130/e069509f/attachment-0001.png From matzew at apache.org Fri Jan 30 08:44:34 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 30 Jan 2015 14:44:34 +0100 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> <0744647C-108B-4D47-B465-282A9E5A4756@redhat.com> Message-ID: On Fri, Jan 30, 2015 at 2:31 PM, Corinne Krych wrote: > @andres here are the JIRA for sync demo: > > Epic iOS Demo https://issues.jboss.org/browse/AGIOS-350 > Ticket AGIOS-258 Enhance UI for jedi > > Epic Android Demo https://issues.jboss.org/browse/AGDROID-369 > todo create a ticket linked to that epic > done: AGDROID-374 > > Epic Android Demo https://issues.jboss.org/browse/AGJS-273 > todo create a ticket linked to that epic > Done: AGJS-276 > > > On 30 Jan 2015, at 14:21, Lucas Holmquist wrote: > > > > i?m currently updating the JS version to use json-patch > >> On Jan 30, 2015, at 5:46 AM, Corinne Krych > wrote: > >> > >> Let's say if it's not for alpha1, it will be alpha2 :) > >> > >> I agree we should based Jedi demo on json-patch approach > >> I've created AGIOS-359 to move demo to that new approach (linked to ios > client impl of json-patch) > >> > >> ++ > >> Corinne > >> > >> > >> On 30 January 2015 at 10:46, Daniel Bevenius > wrote: > >> I like the suggestions. The only concern would be having time to > implement this. > >> > >> >does the ?disconnect? button make sense for this alpha1 (as we don?t > demo offline support). > >> This was mostly for manually testing that we could disconnect from the > server and then reconnect and continue working. But I think we should > remove this for the demo as it think this will require more testing be be > stable. > >> > >> Just for your information, we are currently making changes to the > server side[1] to support different types of diffs/patches. The first type > added, apart from the current DiffMatchPatch, is JSON Patch. So when > developing the client libs/testing please use the branch mentioned in [1] > which also contains links to how to start the servers. > >> > >> [1] https://issues.jboss.org/browse/AGSYNC-24 > >> > >> On 30 January 2015 at 10:15, Corinne Krych > wrote: > >> Hello All, > >> > >> For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of > helloworld demo which do a great job to demo what we want to show in alpha1. > >> Some small suggestions for the flow and look and feel: > >> > >> - could we have a first screen like a list of jedi (for now only one > value i.e.: Luke is available). > >> - could we have a list of hobbies as tableview with possibilities to > add remove some hobbies? > >> - could we have an update button so we can ?batch? input fields changes > together? > >> - does the ?disconnect? button make sense for this alpha1 (as we don?t > demo offline support). The button will be usefull for next release, but > maybe for this one we can remove it. > >> - last but not least, would it be possible to scheme it with a jedi > theme: dark colors, stars, light blue colors? maybe @agalante can come up > with some nice galaxy theme? > >> > >> On iOS side i?ve added AGIOS-358 to track those improving UI items > (liked to epic AGIOS-350). I think we ca ?polish? the demo app without too > much work involved. > >> > >> wdyt guys? > >> > >> ++ > >> 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 > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.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/20150130/88ca05ca/attachment.html From agalante at redhat.com Fri Jan 30 09:00:09 2015 From: agalante at redhat.com (Andres Galante) Date: Fri, 30 Jan 2015 09:00:09 -0500 (EST) Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> <1994724724.1175688.1422621427179.JavaMail.zimbra@redhat.com> Message-ID: <1679802137.1200849.1422626409253.JavaMail.zimbra@redhat.com> Daniel, my part doesn't take much time, I can have this done by early next week (or even by today if necessary). The question is how much time does it take to implement it. I can do something just to style the screen Corinne sent as it is and later this year we can do something better. Do you think it is worth it? ----- Original Message ----- From: "Daniel Bevenius" To: "AeroGear Developer Mailing List" Sent: Friday, January 30, 2015 10:43:19 AM Subject: Re: [aerogear-dev] Polishing our Jedi demo app for sync > For a second release (later this year, likely in fall), it would be good to have some polished and improved UX - but not now. Yeah, unless this is something that can be provide in a very short time I think it might have to be pushed to a later release. The alpha1 release is scheduled for the end of Feb, just to give Andres an idea of the time frame. On 30 January 2015 at 14:38, Matthias Wessendorf < matzew at apache.org > wrote: Hi, we have different epics for a demo, based on platform. I just created this one, to basically reference to the different platforms: https://issues.jboss.org/browse/AGSYNC-29 For a second release (later this year, likely in fall), it would be good to have some polished and improved UX - but not now. To have this as a reminder I listed this ticket underneath: https://issues.jboss.org/browse/AGSYNC-30 but that's also not relevant for now. At least that's my understanding. Dan, correct me if I am wrong On Fri, Jan 30, 2015 at 2:04 PM, Corinne Krych < corinnekrych at gmail.com > wrote: @andres for now it?s really a helloworld app, there isn?t much than just the screen below. The goal of the app is to show sync between several installation of the app: across devices, users As suggested as we could have 2 screens: - one with a list of Jedis - one to view a jedii and add hobbies to his characters. we want to keep this app, hello world format, it?s not a show case app like contact (we?ll have another one) but with some icons and themes it could be much more fun :) On 30 Jan 2015, at 13:37, Andres Galante < agalante at redhat.com > wrote: yay! 2015 just started and this might be the funnest project of the year. Is this based on the same hello-worold Contact list app we have? if there are differences, can you send me a screen capture of the new things in the app? Thanks a lot, Andr?s ----- Original Message ----- From: "Corinne Krych" < corinnekrych at gmail.com > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > Sent: Friday, January 30, 2015 6:15:26 AM Subject: [aerogear-dev] Polishing our Jedi demo app for sync Hello All, For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld demo which do a great job to demo what we want to show in alpha1. Some small suggestions for the flow and look and feel: - could we have a first screen like a list of jedi (for now only one value i.e.: Luke is available). - could we have a list of hobbies as tableview with possibilities to add remove some hobbies? - could we have an update button so we can ?batch? input fields changes together? - does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). The button will be usefull for next release, but maybe for this one we can remove it. - last but not least, would it be possible to scheme it with a jedi theme: dark colors, stars, light blue colors? maybe @agalante can come up with some nice galaxy theme? On iOS side i?ve added AGIOS-358 to track those improving UI items (liked to epic AGIOS-350). I think we ca ?polish? the demo app without too much work involved. wdyt guys? ++ 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 _______________________________________________ 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 From daniel.bevenius at gmail.com Fri Jan 30 09:15:03 2015 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Fri, 30 Jan 2015 15:15:03 +0100 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: <1679802137.1200849.1422626409253.JavaMail.zimbra@redhat.com> References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> <1994724724.1175688.1422621427179.JavaMail.zimbra@redhat.com> <1679802137.1200849.1422626409253.JavaMail.zimbra@redhat.com> Message-ID: Andres, there is no rush. If you could provide something next week we could see if we could implement it. Would be a nice to have for sure and I think it would be worth it. On 30 January 2015 at 15:00, Andres Galante wrote: > Daniel, my part doesn't take much time, I can have this done by early next > week (or even by today if necessary). The question is how much time does it > take to implement it. > > I can do something just to style the screen Corinne sent as it is and > later this year we can do something better. > > Do you think it is worth it? > > > ----- Original Message ----- > From: "Daniel Bevenius" > To: "AeroGear Developer Mailing List" > Sent: Friday, January 30, 2015 10:43:19 AM > Subject: Re: [aerogear-dev] Polishing our Jedi demo app for sync > > > For a second release (later this year, likely in fall), it would be good > to have some polished and improved UX - but not now. > Yeah, unless this is something that can be provide in a very short time I > think it might have to be pushed to a later release. > The alpha1 release is scheduled for the end of Feb, just to give Andres an > idea of the time frame. > > > > On 30 January 2015 at 14:38, Matthias Wessendorf < matzew at apache.org > > wrote: > > > > Hi, > > we have different epics for a demo, based on platform. I just created this > one, to basically reference to the different platforms: > https://issues.jboss.org/browse/AGSYNC-29 > > For a second release (later this year, likely in fall), it would be good > to have some polished and improved UX - but not now. > > To have this as a reminder I listed this ticket underneath: > https://issues.jboss.org/browse/AGSYNC-30 > > but that's also not relevant for now. At least that's my understanding. > Dan, correct me if I am wrong > > On Fri, Jan 30, 2015 at 2:04 PM, Corinne Krych < corinnekrych at gmail.com > > wrote: > > > > @andres for now it?s really a helloworld app, there isn?t much than just > the screen below. > The goal of the app is to show sync between several installation of the > app: across devices, users > > As suggested as we could have 2 screens: > - one with a list of Jedis > - one to view a jedii and add hobbies to his characters. > > we want to keep this app, hello world format, it?s not a show case app > like contact (we?ll have another one) but with some icons and themes it > could be much more fun :) > > > > > > > On 30 Jan 2015, at 13:37, Andres Galante < agalante at redhat.com > wrote: > > yay! 2015 just started and this might be the funnest project of the year. > > Is this based on the same hello-worold Contact list app we have? > if there are differences, can you send me a screen capture of the new > things in the app? > > Thanks a lot, > > Andr?s > > > ----- Original Message ----- > From: "Corinne Krych" < corinnekrych at gmail.com > > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org > > Sent: Friday, January 30, 2015 6:15:26 AM > Subject: [aerogear-dev] Polishing our Jedi demo app for sync > > Hello All, > > For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld > demo which do a great job to demo what we want to show in alpha1. > Some small suggestions for the flow and look and feel: > > - could we have a first screen like a list of jedi (for now only one value > i.e.: Luke is available). > - could we have a list of hobbies as tableview with possibilities to add > remove some hobbies? > - could we have an update button so we can ?batch? input fields changes > together? > - does the ?disconnect? button make sense for this alpha1 (as we don?t > demo offline support). The button will be usefull for next release, but > maybe for this one we can remove it. > - last but not least, would it be possible to scheme it with a jedi theme: > dark colors, stars, light blue colors? maybe @agalante can come up with > some nice galaxy theme? > > On iOS side i?ve added AGIOS-358 to track those improving UI items (liked > to epic AGIOS-350). I think we ca ?polish? the demo app without too much > work involved. > > wdyt guys? > > ++ > 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 > > > _______________________________________________ > 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/20150130/4fc79ee0/attachment-0001.html From matzew at apache.org Fri Jan 30 09:22:31 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 30 Jan 2015 15:22:31 +0100 Subject: [aerogear-dev] Storing the payload of the push notification Message-ID: Hi, earlier this week there was some discussion about storing the payload of the push notifications ([1]). Right now, we store some metrics (e.g. client that send the push, number of devices, deliveryStatus etc) *and* the entire content of push notification. This includes custom key/value pairs, the name of the sound file or even the size of the badge. Is all of that, storing the entire push notification payload really needed? *No!* What do we need, and why? For counting the number of sent pushes (over time), the metrics are good enough. We do *NOT* need any of the push content for that, that's correct! But we want to do more on the 1.1.0 release. We want to introduce some analytic features, to give our app developers (our users) a better understanding of their push usage (see [2]). In order to see details on how successful a push was (or not), we need to only store the value of the alert key: https://aerogear.org/docs/unifiedpush/aerogear-push-ios/img/PushMessage.png Ok, let's change that (see [3])! For our app developers, using the UPS to reach out to their mobile app users ("user engagement"), it's important to understand which push was more successful: - "Get 10% discount today" (sent on a Monday) - "Our shop got new site, check it out and get 5% discount" (sent on a Friday) With the upcoming analytics we can help them to improve usage of their app. User interaction is very important to a successful mobile application and push is a key driver here! Our app developers want an app that is actively used by their users (Nobody wants his app sitting on the last page of the device or, even worse, in a folder together with Apple-Maps). Therefore it's critical for our app developers to understand the relevance of their push messages sent and how it impacts the usage of their app. That's why we do the analytics described in [2]. And, yes - only the alert, not the entire payload is needed for that. Privacy On the mentioned PR there was also some discussion about privacy violations and stuff, when we store the content of the notification. An example where *sensitive* data was sent over push was given. Something like: "Dear Mr. Joe, your blood donation appointment was scheduled for 3 p.m" 1. This is not how push notifications are used for mobile apps. Push is to signal, not carry actual (sensitive) data around. 2. In a lot of countries, at least almost all European countries, you are not even allowed, by EU law, to give "data" to 3rd party providers (like the push-networks of Microsoft, Apple or Google). How does the actual (sensitive) data come to an app? As said above a push is used to signal/ping an app, to indicate that there is real data for the mobile app user. In the background the mobile app tries to connect to the backend of the company, running/maintaining the mobile app. After the real data was fetched, "local notifcations" are used to give the user a visible notification, like "Dear Mr. Joe, your blood donation appointment was scheduled for 3 p.m", or simply "New appointment scheduled". If the app was a chat system (and not a blood donation app from the Red Cross), it would be the same: After a signal, the app connects to "chat server" and receives the actual chat message from there. A reply would go over the same "chat server" connection. None of this would go over a 3rd party push network provider like Google, Microsoft or Apple. What would we store from these silent notifications? Nothing, since there is no alert, we would just store the metrics (e.g. client that send the push, number of devices, deliveryStatus etc). If the signaling is actually done with an alert (e.g. alert:"you got a new Chat text" or "New appointment scheduled"), we would store that. I hope this helps a bit to understand what is stored and also why we do need a little bit of information. BTW. our documentation already says that push is used for signaling, not carrying actual data around, but based on this email I will update it to have explicit information on best practices. Also, the documentation will be clear about what (the alert only) is stored by the UPS, and why. (see [4]) Greetings, Matthias - [1] https://github.com/aerogear/aerogear-unifiedpush-server/pull/478 - [2] https://issues.jboss.org/browse/AGPUSH-971 - [3] JIRA TO CREATE: to only store ALERT and not the full payload - [4] JIRA TO CREATE: update doc regarding push message storage and best practices -- 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/20150130/6eb72916/attachment.html From lholmqui at redhat.com Fri Jan 30 09:57:35 2015 From: lholmqui at redhat.com (Lucas Holmquist) Date: Fri, 30 Jan 2015 09:57:35 -0500 Subject: [aerogear-dev] Polishing our Jedi demo app for sync In-Reply-To: References: <4379E7FC-DF77-467D-9CB9-A1BCE0224B03@gmail.com> Message-ID: <4EF64A8E-EAF8-41AC-82FB-B1B11BD1DC11@redhat.com> > On Jan 30, 2015, at 4:46 AM, Daniel Bevenius wrote: > > I like the suggestions. The only concern would be having time to implement this. > > >does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). > This was mostly for manually testing that we could disconnect from the server and then reconnect and continue working. But I think we should remove this for the demo as it think this will require more testing be be stable. > > Just for your information, we are currently making changes to the server side[1] to support different types of diffs/patches. The first type added, apart from the current DiffMatchPatch, is JSON Patch. So when developing the client libs/testing please use the branch mentioned in [1] which also contains links to how to start the servers. here is the branch for the js example, https://github.com/lholmquist/aerogear-js-cookbook/tree/diff-sync-json-patch/diff-sync , probably missing readme?s etc? but it?s hacked together :) > > [1] https://issues.jboss.org/browse/AGSYNC-24 > > On 30 January 2015 at 10:15, Corinne Krych > wrote: > Hello All, > > For our sync-1.0.0.alpha1 release we have our ?Jedi? kind of helloworld demo which do a great job to demo what we want to show in alpha1. > Some small suggestions for the flow and look and feel: > > - could we have a first screen like a list of jedi (for now only one value i.e.: Luke is available). > - could we have a list of hobbies as tableview with possibilities to add remove some hobbies? > - could we have an update button so we can ?batch? input fields changes together? > - does the ?disconnect? button make sense for this alpha1 (as we don?t demo offline support). The button will be usefull for next release, but maybe for this one we can remove it. > - last but not least, would it be possible to scheme it with a jedi theme: dark colors, stars, light blue colors? maybe @agalante can come up with some nice galaxy theme? > > On iOS side i?ve added AGIOS-358 to track those improving UI items (liked to epic AGIOS-350). I think we ca ?polish? the demo app without too much work involved. > > wdyt guys? > > ++ > 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/20150130/c9bd3a59/attachment.html