From corinnekrych at gmail.com Mon Mar 3 06:17:07 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 3 Mar 2014 12:17:07 +0100 Subject: [aerogear-dev] [ag.org revamp] GET IT page structure Message-ID: <7A9B8315-0712-4E89-91C7-5E7DF21ED712@gmail.com> Hello All, Following Hylke?s thread on web site restructure [1], I?d like to start a new thread to discuss GET IT pages in the mockup section [2]. Those pages will replace the ?get started? page on the current web site [3]. As Hylke said it, we don?t necesseraly have a the same split of libraries in the differents platforms. Some thing to carry on working on; for example in iOS, we do have a thread opened for iOS small libs [4]. To make an initial working GET IT page, we could have a list of libraries per features but we also need a link to a PLATFORM GET IT page. The PLATFORM GET IT page, it?s similar to the PLATFORM EXAMPLES page where we need a view per platform. We should have a iOS GET IT which split between sever/client and displays all libraries with code color for different features. For JavaScript this page will contain the custom builder tool [5]. @hbons How can we make the transition from GET IT to PLATFORM GET IT page? shall we add a link from HOME page to PLATFORM GET IT page? wdyt? ++ Corinne [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365 [2] https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png [3] http://aerogear.org/download/ [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html [5] http://aerogear.org/download/custom/ From hbons at redhat.com Mon Mar 3 07:03:20 2014 From: hbons at redhat.com (Hylke Bons) Date: Mon, 03 Mar 2014 12:03:20 +0000 Subject: [aerogear-dev] [ag.org revamp] GET IT page structure In-Reply-To: <7A9B8315-0712-4E89-91C7-5E7DF21ED712@gmail.com> References: <7A9B8315-0712-4E89-91C7-5E7DF21ED712@gmail.com> Message-ID: <53146F88.8090906@redhat.com> Hello, Can we hold a larger high level discussion about the project's package organisation and splits? I really think this is needed before we can actually come up with a good design for this. Otherwise I'm afraid we'll end up with inconsistent and confusing pages, not a whole lot better than our current download pages. I've already written down some of my thoughts on this: http://oksoclap.com/p/AeroGearModuleUntangling What I can do right now is mock up the flow from the download page to the different platform client setup pages. Hylke On 03/03/2014 11:17, Corinne Krych wrote: > Hello All, > > Following Hylke?s thread on web site restructure [1], I?d like to start a new thread to discuss GET IT pages in the mockup section [2]. Those pages will replace the ?get started? page on the current web site [3]. > > As Hylke said it, we don?t necesseraly have a the same split of libraries in the differents platforms. Some thing to carry on working on; for example in iOS, we do have a thread opened for iOS small libs [4]. > > To make an initial working GET IT page, we could have a list of libraries per features but we also need a link to a PLATFORM GET IT page. > > The PLATFORM GET IT page, it?s similar to the PLATFORM EXAMPLES page where we need a view per platform. We should have a iOS GET IT which split between sever/client and displays all libraries with code color for different features. For JavaScript this page will contain the custom builder tool [5]. > > @hbons How can we make the transition from GET IT to PLATFORM GET IT page? shall we add a link from HOME page to PLATFORM GET IT page? > > wdyt? > > ++ > Corinne > [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365 > [2] https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png > [3] http://aerogear.org/download/ > [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html > [5] http://aerogear.org/download/custom/ > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From kpiwko at redhat.com Mon Mar 3 08:26:30 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Mon, 3 Mar 2014 14:26:30 +0100 Subject: [aerogear-dev] Chrome Apps and UnifiedPush Server shinyness In-Reply-To: <5AD2B2BA-7A8B-488D-A4B9-CAC1C58BCAAE@redhat.com> References: <5AD2B2BA-7A8B-488D-A4B9-CAC1C58BCAAE@redhat.com> Message-ID: <20140303142630.1a25ba26@kapy-ntb-x220> Works good! However, I find "Terminate" button confusing. It looks to me like something that would bring UPS down which is fortunately not the case. On Fri, 28 Feb 2014 10:50:30 -0500 Lucas Holmquist wrote: > another friday, another shiny object. > > Lately i've been somewhat obsessed with coding Chrome Packaged Apps, and i > thought it would be cool to have a UnifiedPush Server chrome app. > > Chrome Apps have a webview, so this made it pretty easy > > this is the link to my POC: > > https://chrome.google.com/webstore/detail/aerogear-unified-push-chr/hcmjdjjffgdbiiidopdfhpnkpphiekai > > it's published, but only to people who have the link, so you can't search for > it > > > after you install and launch it, put in the url of your UnifiedPush Server > running somewhere, if you are OpenShift make sure you wake it up > > if everything goes ok, you should see your Admin UI in the app. > > ATM it is very bare bones, but again, it is just a POC. > > not sure if someone would be managing multiple UPS's at once, but you could > potentially do that( but not currently how the chrome app is written ) > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From lholmqui at redhat.com Mon Mar 3 08:28:07 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 3 Mar 2014 08:28:07 -0500 Subject: [aerogear-dev] Chrome Apps and UnifiedPush Server shinyness In-Reply-To: <20140303142630.1a25ba26@kapy-ntb-x220> References: <5AD2B2BA-7A8B-488D-A4B9-CAC1C58BCAAE@redhat.com> <20140303142630.1a25ba26@kapy-ntb-x220> Message-ID: <33FF1FEE-CEE3-4CC0-89C2-1A6D966642C6@redhat.com> On Mar 3, 2014, at 8:26 AM, Karel Piwko wrote: > Works good! > > However, I find "Terminate" button confusing. It looks to me like something > that would bring UPS down which is fortunately not the case. I just liked the name :) > > On Fri, 28 Feb 2014 10:50:30 -0500 > Lucas Holmquist wrote: > >> another friday, another shiny object. >> >> Lately i've been somewhat obsessed with coding Chrome Packaged Apps, and i >> thought it would be cool to have a UnifiedPush Server chrome app. >> >> Chrome Apps have a webview, so this made it pretty easy >> >> this is the link to my POC: >> >> https://chrome.google.com/webstore/detail/aerogear-unified-push-chr/hcmjdjjffgdbiiidopdfhpnkpphiekai >> >> it's published, but only to people who have the link, so you can't search for >> it >> >> >> after you install and launch it, put in the url of your UnifiedPush Server >> running somewhere, if you are OpenShift make sure you wake it up >> >> if everything goes ok, you should see your Admin UI in the app. >> >> ATM it is very bare bones, but again, it is just a POC. >> >> not sure if someone would be managing multiple UPS's at once, but you could >> potentially do that( but not currently how the chrome app is written ) >> _______________________________________________ aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 Mon Mar 3 08:39:43 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Mon, 3 Mar 2014 14:39:43 +0100 Subject: [aerogear-dev] Chrome Apps and UnifiedPush Server shinyness In-Reply-To: <33FF1FEE-CEE3-4CC0-89C2-1A6D966642C6@redhat.com> References: <5AD2B2BA-7A8B-488D-A4B9-CAC1C58BCAAE@redhat.com> <20140303142630.1a25ba26@kapy-ntb-x220> <33FF1FEE-CEE3-4CC0-89C2-1A6D966642C6@redhat.com> Message-ID: <20140303143943.64dd81ae@kapy-ntb-x220> On Mon, 3 Mar 2014 08:28:07 -0500 Lucas Holmquist wrote: > > On Mar 3, 2014, at 8:26 AM, Karel Piwko wrote: > > > Works good! > > > > However, I find "Terminate" button confusing. It looks to me like something > > that would bring UPS down which is fortunately not the case. > > I just liked the name :) :-) > > > > > On Fri, 28 Feb 2014 10:50:30 -0500 > > Lucas Holmquist wrote: > > > >> another friday, another shiny object. > >> > >> Lately i've been somewhat obsessed with coding Chrome Packaged Apps, and i > >> thought it would be cool to have a UnifiedPush Server chrome app. > >> > >> Chrome Apps have a webview, so this made it pretty easy > >> > >> this is the link to my POC: > >> > >> https://chrome.google.com/webstore/detail/aerogear-unified-push-chr/hcmjdjjffgdbiiidopdfhpnkpphiekai > >> > >> it's published, but only to people who have the link, so you can't search > >> for it > >> > >> > >> after you install and launch it, put in the url of your UnifiedPush Server > >> running somewhere, if you are OpenShift make sure you wake it up > >> > >> if everything goes ok, you should see your Admin UI in the app. > >> > >> ATM it is very bare bones, but again, it is just a POC. > >> > >> not sure if someone would be managing multiple UPS's at once, but you > >> could potentially do that( but not currently how the chrome app is > >> written ) _______________________________________________ aerogear-dev > >> mailing list aerogear-dev at lists.jboss.org > >> https://lists.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 Mon Mar 3 08:45:16 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 3 Mar 2014 14:45:16 +0100 Subject: [aerogear-dev] [ag.org revamp] GET IT page structure In-Reply-To: <53146F88.8090906@redhat.com> References: <7A9B8315-0712-4E89-91C7-5E7DF21ED712@gmail.com> <53146F88.8090906@redhat.com> Message-ID: <34AFA707-3E10-4142-A30B-D309261977AA@gmail.com> Hello Hylke I guess we had a different approach here: - You want to revisit our librairies split to fit in the web site restructure. - I want to fit the actual libraries split into your new web site, making adjustment to web site design. Let me detail out libraries a bit more. Here is a list of existing split with matching gh repo (when available) that we can use as a starting point for our GET IT page: ********* Core - Server: nope, just an example --- Core - Client iOS: https://github.com/aerogear/aerogear-ios Core - Client JS: https://github.com/aerogear/aerogear-js Core - Client Android: https://github.com/aerogear/aerogear-android Core - Client Cordova: n/a ********* Push - UnifiedPush Server: https://github.com/aerogear/aerogear-unifiedpush-server Push - UnifiedPush Server Java Sender API: https://github.com/aerogear/aerogear-unifiedpush-java-client Push - UnifiedPush Server Node Sender API (JS): https://github.com/aerogear/aerogear-unifiedpush-nodejs-client Push - SimplePush Server: https://github.com/aerogear/aerogear-simplepush-server Push - SimplePush Server Java Sender API: https://github.com/aerogear/aerogear-simplepush-java-client Push - SimplePush Server Node Sender API (JS): https://github.com/aerogear/aerogear-simplepush-node-client --- Push - Client iOS: UnifiedPush.Registration: https://github.com/aerogear/aerogear-push-ios-registration Push - Client JS: UnifiedPush.Registration: n/a Push - Client Android: UnifiedPush.Registration: Push - Client Cordova: UnifiedPush.Registration: https://github.com/aerogear/aerogear-pushplugin-cordova --- Push - Client iOS: SimpledPush: n/a Push - Client JS: SimplePush: JS core repo Push - Client Android: SimplePush: n/a Push - Client Cordova: SimplePush: n/a - nothing yet ********* Security - Server Shiro Adapter: https://github.com/aerogear/aerogear-security-shiro Security - Server PicketLink Adapter: https://github.com/aerogear/aerogear-security-picketlink Security - Server Hawk Adapter: https://github.com/aerogear/aerogear-security-hawk Security - Server Crypto: https://github.com/aerogear/aerogear-crypto-java --- Security - Client iOS Security.OTP: https://github.com/aerogear/aerogear-otp-ios Security - Client JS Security.OTP: https://github.com/aerogear/aerogear-otp-java Security - Client Android Security.OTP: https://github.com/aerogear/aerogear-otp-js Security - Client Cordova Security.OTP: https://github.com/aerogear/aerogear-otp-cordova --- Security - Client iOS Security.Crypto: https://github.com/aerogear/aerogear-crypto-ios Security - Client JS Security.Crypto: https://github.com/aerogear/aerogear-crypto-java Security - Client Android Security.Crypto: JS core repo Security - Client Cordova Security.Crypto: https://github.com/aerogear/aerogear-crypto-cordova ********* Note: that JavaScript libraries although not splitted into different repos still offer fine grained libraries with the Custom build feature. I didn?t know where to put: https://github.com/aerogear/aerogear-geo-cordova. @all, feel free to correct if I missed some repo. As you can see we have something that we could fit in our GET IT page. I?m convinced though, that a PLATFORM GET IT page (which would provide a PLATFORM view) will be really useful. ++ Corinne On 03 Mar 2014, at 13:03, Hylke Bons wrote: > Hello, > > Can we hold a larger high level discussion about the project's package > organisation and splits? I really think this is needed before we can > actually come up with a good design for this. > > Otherwise I'm afraid we'll end up with inconsistent and confusing pages, > not a whole lot better than our current download pages. > > I've already written down some of my thoughts on this: > http://oksoclap.com/p/AeroGearModuleUntangling > > What I can do right now is mock up the flow from the download page to > the different platform client setup pages. > > Hylke > > > On 03/03/2014 11:17, Corinne Krych wrote: >> Hello All, >> >> Following Hylke?s thread on web site restructure [1], I?d like to start a new thread to discuss GET IT pages in the mockup section [2]. Those pages will replace the ?get started? page on the current web site [3]. >> >> As Hylke said it, we don?t necesseraly have a the same split of libraries in the differents platforms. Some thing to carry on working on; for example in iOS, we do have a thread opened for iOS small libs [4]. >> >> To make an initial working GET IT page, we could have a list of libraries per features but we also need a link to a PLATFORM GET IT page. >> >> The PLATFORM GET IT page, it?s similar to the PLATFORM EXAMPLES page where we need a view per platform. We should have a iOS GET IT which split between sever/client and displays all libraries with code color for different features. For JavaScript this page will contain the custom builder tool [5]. >> >> @hbons How can we make the transition from GET IT to PLATFORM GET IT page? shall we add a link from HOME page to PLATFORM GET IT page? >> >> wdyt? >> >> ++ >> Corinne >> [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365 >> [2] https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png >> [3] http://aerogear.org/download/ >> [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html >> [5] http://aerogear.org/download/custom/ >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 scm.blanc at gmail.com Mon Mar 3 08:51:17 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 3 Mar 2014 14:51:17 +0100 Subject: [aerogear-dev] [ag.org revamp] GET IT page structure In-Reply-To: <34AFA707-3E10-4142-A30B-D309261977AA@gmail.com> References: <7A9B8315-0712-4E89-91C7-5E7DF21ED712@gmail.com> <53146F88.8090906@redhat.com> <34AFA707-3E10-4142-A30B-D309261977AA@gmail.com> Message-ID: On Mon, Mar 3, 2014 at 2:45 PM, Corinne Krych wrote: > Hello Hylke > > I guess we had a different approach here: > - You want to revisit our librairies split to fit in the web site > restructure. > - I want to fit the actual libraries split into your new web site, making > adjustment to web site design. > > Let me detail out libraries a bit more. Here is a list of existing split > with matching gh repo (when available) that we can use as a starting point > for our GET IT page: > > ********* > Core - Server: nope, just an example > --- > Core - Client iOS: https://github.com/aerogear/aerogear-ios > Core - Client JS: https://github.com/aerogear/aerogear-js > Core - Client Android: https://github.com/aerogear/aerogear-android > Core - Client Cordova: n/a > ********* > Push - UnifiedPush Server: > https://github.com/aerogear/aerogear-unifiedpush-server > Push - UnifiedPush Server Java Sender API: > https://github.com/aerogear/aerogear-unifiedpush-java-client > Push - UnifiedPush Server Node Sender API (JS): > https://github.com/aerogear/aerogear-unifiedpush-nodejs-client > Push - SimplePush Server: > https://github.com/aerogear/aerogear-simplepush-server > Push - SimplePush Server Java Sender API: > https://github.com/aerogear/aerogear-simplepush-java-client > Push - SimplePush Server Node Sender API (JS): > https://github.com/aerogear/aerogear-simplepush-node-client > --- > Push - Client iOS: UnifiedPush.Registration: > https://github.com/aerogear/aerogear-push-ios-registration > Push - Client JS: UnifiedPush.Registration: n/a > Actually, we have this in the JS core repo. > Push - Client Android: UnifiedPush.Registration: > Push - Client Cordova: UnifiedPush.Registration: > https://github.com/aerogear/aerogear-pushplugin-cordova > --- > Push - Client iOS: SimpledPush: n/a > Push - Client JS: SimplePush: JS core repo > Push - Client Android: SimplePush: n/a > Push - Client Cordova: SimplePush: n/a - nothing yet > ********* > Security - Server Shiro Adapter: > https://github.com/aerogear/aerogear-security-shiro > Security - Server PicketLink Adapter: > https://github.com/aerogear/aerogear-security-picketlink > Security - Server Hawk Adapter: > https://github.com/aerogear/aerogear-security-hawk > Security - Server Crypto: https://github.com/aerogear/aerogear-crypto-java > --- > Security - Client iOS Security.OTP: > https://github.com/aerogear/aerogear-otp-ios > Security - Client JS Security.OTP: > https://github.com/aerogear/aerogear-otp-java > Security - Client Android Security.OTP: > https://github.com/aerogear/aerogear-otp-js > Security - Client Cordova Security.OTP: > https://github.com/aerogear/aerogear-otp-cordova > --- > Security - Client iOS Security.Crypto: > https://github.com/aerogear/aerogear-crypto-ios > Security - Client JS Security.Crypto: > https://github.com/aerogear/aerogear-crypto-java > Security - Client Android Security.Crypto: JS core repo > Security - Client Cordova Security.Crypto: > https://github.com/aerogear/aerogear-crypto-cordova > ********* > Note: that JavaScript libraries although not splitted into different repos > still offer fine grained libraries with the Custom build feature. > I didn't know where to put: > https://github.com/aerogear/aerogear-geo-cordova. > > @all, feel free to correct if I missed some repo. > > As you can see we have something that we could fit in our GET IT page. I'm > convinced though, that a PLATFORM GET IT page (which would provide a > PLATFORM view) will be really useful. > > ++ > Corinne > > On 03 Mar 2014, at 13:03, Hylke Bons wrote: > > > Hello, > > > > Can we hold a larger high level discussion about the project's package > > organisation and splits? I really think this is needed before we can > > actually come up with a good design for this. > > > > Otherwise I'm afraid we'll end up with inconsistent and confusing pages, > > not a whole lot better than our current download pages. > > > > I've already written down some of my thoughts on this: > > http://oksoclap.com/p/AeroGearModuleUntangling > > > > What I can do right now is mock up the flow from the download page to > > the different platform client setup pages. > > > > Hylke > > > > > > On 03/03/2014 11:17, Corinne Krych wrote: > >> Hello All, > >> > >> Following Hylke's thread on web site restructure [1], I'd like to start > a new thread to discuss GET IT pages in the mockup section [2]. Those pages > will replace the "get started" page on the current web site [3]. > >> > >> As Hylke said it, we don't necesseraly have a the same split of > libraries in the differents platforms. Some thing to carry on working on; > for example in iOS, we do have a thread opened for iOS small libs [4]. > >> > >> To make an initial working GET IT page, we could have a list of > libraries per features but we also need a link to a PLATFORM GET IT page. > >> > >> The PLATFORM GET IT page, it's similar to the PLATFORM EXAMPLES page > where we need a view per platform. We should have a iOS GET IT which split > between sever/client and displays all libraries with code color for > different features. For JavaScript this page will contain the custom > builder tool [5]. > >> > >> @hbons How can we make the transition from GET IT to PLATFORM GET IT > page? shall we add a link from HOME page to PLATFORM GET IT page? > >> > >> wdyt? > >> > >> ++ > >> Corinne > >> [1] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365 > >> [2] > https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png > >> [3] http://aerogear.org/download/ > >> [4] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html > >> [5] http://aerogear.org/download/custom/ > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.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/20140303/18e4a86a/attachment-0001.html From corinnekrych at gmail.com Mon Mar 3 08:54:29 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 3 Mar 2014 14:54:29 +0100 Subject: [aerogear-dev] [ag.org revamp] GET IT page structure In-Reply-To: References: <7A9B8315-0712-4E89-91C7-5E7DF21ED712@gmail.com> <53146F88.8090906@redhat.com> <34AFA707-3E10-4142-A30B-D309261977AA@gmail.com> Message-ID: Thanks Sebi for the correction! ++ Corinne On 03 Mar 2014, at 14:51, Sebastien Blanc wrote: > > > > On Mon, Mar 3, 2014 at 2:45 PM, Corinne Krych wrote: > Hello Hylke > > I guess we had a different approach here: > - You want to revisit our librairies split to fit in the web site restructure. > - I want to fit the actual libraries split into your new web site, making adjustment to web site design. > > Let me detail out libraries a bit more. Here is a list of existing split with matching gh repo (when available) that we can use as a starting point for our GET IT page: > > ********* > Core - Server: nope, just an example > --- > Core - Client iOS: https://github.com/aerogear/aerogear-ios > Core - Client JS: https://github.com/aerogear/aerogear-js > Core - Client Android: https://github.com/aerogear/aerogear-android > Core - Client Cordova: n/a > ********* > Push - UnifiedPush Server: https://github.com/aerogear/aerogear-unifiedpush-server > Push - UnifiedPush Server Java Sender API: https://github.com/aerogear/aerogear-unifiedpush-java-client > Push - UnifiedPush Server Node Sender API (JS): https://github.com/aerogear/aerogear-unifiedpush-nodejs-client > Push - SimplePush Server: https://github.com/aerogear/aerogear-simplepush-server > Push - SimplePush Server Java Sender API: https://github.com/aerogear/aerogear-simplepush-java-client > Push - SimplePush Server Node Sender API (JS): https://github.com/aerogear/aerogear-simplepush-node-client > --- > Push - Client iOS: UnifiedPush.Registration: https://github.com/aerogear/aerogear-push-ios-registration > Push - Client JS: UnifiedPush.Registration: n/a > Actually, we have this in the JS core repo. > Push - Client Android: UnifiedPush.Registration: > Push - Client Cordova: UnifiedPush.Registration: https://github.com/aerogear/aerogear-pushplugin-cordova > --- > Push - Client iOS: SimpledPush: n/a > Push - Client JS: SimplePush: JS core repo > Push - Client Android: SimplePush: n/a > Push - Client Cordova: SimplePush: n/a - nothing yet > ********* > Security - Server Shiro Adapter: https://github.com/aerogear/aerogear-security-shiro > Security - Server PicketLink Adapter: https://github.com/aerogear/aerogear-security-picketlink > Security - Server Hawk Adapter: https://github.com/aerogear/aerogear-security-hawk > Security - Server Crypto: https://github.com/aerogear/aerogear-crypto-java > --- > Security - Client iOS Security.OTP: https://github.com/aerogear/aerogear-otp-ios > Security - Client JS Security.OTP: https://github.com/aerogear/aerogear-otp-java > Security - Client Android Security.OTP: https://github.com/aerogear/aerogear-otp-js > Security - Client Cordova Security.OTP: https://github.com/aerogear/aerogear-otp-cordova > --- > Security - Client iOS Security.Crypto: https://github.com/aerogear/aerogear-crypto-ios > Security - Client JS Security.Crypto: https://github.com/aerogear/aerogear-crypto-java > Security - Client Android Security.Crypto: JS core repo > Security - Client Cordova Security.Crypto: https://github.com/aerogear/aerogear-crypto-cordova > ********* > Note: that JavaScript libraries although not splitted into different repos still offer fine grained libraries with the Custom build feature. > I didn?t know where to put: https://github.com/aerogear/aerogear-geo-cordova. > > @all, feel free to correct if I missed some repo. > > As you can see we have something that we could fit in our GET IT page. I?m convinced though, that a PLATFORM GET IT page (which would provide a PLATFORM view) will be really useful. > > ++ > Corinne > > On 03 Mar 2014, at 13:03, Hylke Bons wrote: > > > Hello, > > > > Can we hold a larger high level discussion about the project's package > > organisation and splits? I really think this is needed before we can > > actually come up with a good design for this. > > > > Otherwise I'm afraid we'll end up with inconsistent and confusing pages, > > not a whole lot better than our current download pages. > > > > I've already written down some of my thoughts on this: > > http://oksoclap.com/p/AeroGearModuleUntangling > > > > What I can do right now is mock up the flow from the download page to > > the different platform client setup pages. > > > > Hylke > > > > > > On 03/03/2014 11:17, Corinne Krych wrote: > >> Hello All, > >> > >> Following Hylke?s thread on web site restructure [1], I?d like to start a new thread to discuss GET IT pages in the mockup section [2]. Those pages will replace the ?get started? page on the current web site [3]. > >> > >> As Hylke said it, we don?t necesseraly have a the same split of libraries in the differents platforms. Some thing to carry on working on; for example in iOS, we do have a thread opened for iOS small libs [4]. > >> > >> To make an initial working GET IT page, we could have a list of libraries per features but we also need a link to a PLATFORM GET IT page. > >> > >> The PLATFORM GET IT page, it?s similar to the PLATFORM EXAMPLES page where we need a view per platform. We should have a iOS GET IT which split between sever/client and displays all libraries with code color for different features. For JavaScript this page will contain the custom builder tool [5]. > >> > >> @hbons How can we make the transition from GET IT to PLATFORM GET IT page? shall we add a link from HOME page to PLATFORM GET IT page? > >> > >> wdyt? > >> > >> ++ > >> Corinne > >> [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365 > >> [2] https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png > >> [3] http://aerogear.org/download/ > >> [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html > >> [5] http://aerogear.org/download/custom/ > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.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 daniel.bevenius at gmail.com Mon Mar 3 09:02:29 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 3 Mar 2014 15:02:29 +0100 Subject: [aerogear-dev] Team meeting agenda Message-ID: http://oksoclap.com/p/aerogear-team-mgt-20140303 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140303/66fd268d/attachment.html From hbons at redhat.com Mon Mar 3 09:13:44 2014 From: hbons at redhat.com (Hylke Bons) Date: Mon, 03 Mar 2014 14:13:44 +0000 Subject: [aerogear-dev] [ag.org revamp] GET IT page structure In-Reply-To: References: <7A9B8315-0712-4E89-91C7-5E7DF21ED712@gmail.com> <53146F88.8090906@redhat.com> <34AFA707-3E10-4142-A30B-D309261977AA@gmail.com> Message-ID: <53148E18.6000209@redhat.com> Thanks Corinne and Sebastien for the list, that's useful to have. "- You want to revisit our librairies split to fit in the web site restructure." No, the website mockups are just one example how things can be structured. It makes many assumptions, some of which may not be possible right now. It doesn't neccesarily have to be according the the mockups. I _do_ want revisit the libraries split, because there are inconsistencies and no website redesign is going to fix them. I need your help to find out where the problems lie, and if we can't do it this way, let's find another one, but the current situation is problematic if we want to implement anything coherent. Thanks, Hylke On 03/03/2014 13:54, Corinne Krych wrote: > Thanks Sebi for the correction! > ++ > Corinne > On 03 Mar 2014, at 14:51, Sebastien Blanc wrote: > >> >> >> On Mon, Mar 3, 2014 at 2:45 PM, Corinne Krych wrote: >> Hello Hylke >> >> I guess we had a different approach here: >> - You want to revisit our librairies split to fit in the web site restructure. >> - I want to fit the actual libraries split into your new web site, making adjustment to web site design. >> >> Let me detail out libraries a bit more. Here is a list of existing split with matching gh repo (when available) that we can use as a starting point for our GET IT page: >> >> ********* >> Core - Server: nope, just an example >> --- >> Core - Client iOS: https://github.com/aerogear/aerogear-ios >> Core - Client JS: https://github.com/aerogear/aerogear-js >> Core - Client Android: https://github.com/aerogear/aerogear-android >> Core - Client Cordova: n/a >> ********* >> Push - UnifiedPush Server: https://github.com/aerogear/aerogear-unifiedpush-server >> Push - UnifiedPush Server Java Sender API: https://github.com/aerogear/aerogear-unifiedpush-java-client >> Push - UnifiedPush Server Node Sender API (JS): https://github.com/aerogear/aerogear-unifiedpush-nodejs-client >> Push - SimplePush Server: https://github.com/aerogear/aerogear-simplepush-server >> Push - SimplePush Server Java Sender API: https://github.com/aerogear/aerogear-simplepush-java-client >> Push - SimplePush Server Node Sender API (JS): https://github.com/aerogear/aerogear-simplepush-node-client >> --- >> Push - Client iOS: UnifiedPush.Registration: https://github.com/aerogear/aerogear-push-ios-registration >> Push - Client JS: UnifiedPush.Registration: n/a >> Actually, we have this in the JS core repo. >> Push - Client Android: UnifiedPush.Registration: >> Push - Client Cordova: UnifiedPush.Registration: https://github.com/aerogear/aerogear-pushplugin-cordova >> --- >> Push - Client iOS: SimpledPush: n/a >> Push - Client JS: SimplePush: JS core repo >> Push - Client Android: SimplePush: n/a >> Push - Client Cordova: SimplePush: n/a - nothing yet >> ********* >> Security - Server Shiro Adapter: https://github.com/aerogear/aerogear-security-shiro >> Security - Server PicketLink Adapter: https://github.com/aerogear/aerogear-security-picketlink >> Security - Server Hawk Adapter: https://github.com/aerogear/aerogear-security-hawk >> Security - Server Crypto: https://github.com/aerogear/aerogear-crypto-java >> --- >> Security - Client iOS Security.OTP: https://github.com/aerogear/aerogear-otp-ios >> Security - Client JS Security.OTP: https://github.com/aerogear/aerogear-otp-java >> Security - Client Android Security.OTP: https://github.com/aerogear/aerogear-otp-js >> Security - Client Cordova Security.OTP: https://github.com/aerogear/aerogear-otp-cordova >> --- >> Security - Client iOS Security.Crypto: https://github.com/aerogear/aerogear-crypto-ios >> Security - Client JS Security.Crypto: https://github.com/aerogear/aerogear-crypto-java >> Security - Client Android Security.Crypto: JS core repo >> Security - Client Cordova Security.Crypto: https://github.com/aerogear/aerogear-crypto-cordova >> ********* >> Note: that JavaScript libraries although not splitted into different repos still offer fine grained libraries with the Custom build feature. >> I didn?t know where to put: https://github.com/aerogear/aerogear-geo-cordova. >> >> @all, feel free to correct if I missed some repo. >> >> As you can see we have something that we could fit in our GET IT page. I?m convinced though, that a PLATFORM GET IT page (which would provide a PLATFORM view) will be really useful. >> >> ++ >> Corinne >> >> On 03 Mar 2014, at 13:03, Hylke Bons wrote: >> >>> Hello, >>> >>> Can we hold a larger high level discussion about the project's package >>> organisation and splits? I really think this is needed before we can >>> actually come up with a good design for this. >>> >>> Otherwise I'm afraid we'll end up with inconsistent and confusing pages, >>> not a whole lot better than our current download pages. >>> >>> I've already written down some of my thoughts on this: >>> http://oksoclap.com/p/AeroGearModuleUntangling >>> >>> What I can do right now is mock up the flow from the download page to >>> the different platform client setup pages. >>> >>> Hylke >>> >>> >>> On 03/03/2014 11:17, Corinne Krych wrote: >>>> Hello All, >>>> >>>> Following Hylke?s thread on web site restructure [1], I?d like to start a new thread to discuss GET IT pages in the mockup section [2]. Those pages will replace the ?get started? page on the current web site [3]. >>>> >>>> As Hylke said it, we don?t necesseraly have a the same split of libraries in the differents platforms. Some thing to carry on working on; for example in iOS, we do have a thread opened for iOS small libs [4]. >>>> >>>> To make an initial working GET IT page, we could have a list of libraries per features but we also need a link to a PLATFORM GET IT page. >>>> >>>> The PLATFORM GET IT page, it?s similar to the PLATFORM EXAMPLES page where we need a view per platform. We should have a iOS GET IT which split between sever/client and displays all libraries with code color for different features. For JavaScript this page will contain the custom builder tool [5]. >>>> >>>> @hbons How can we make the transition from GET IT to PLATFORM GET IT page? shall we add a link from HOME page to PLATFORM GET IT page? >>>> >>>> wdyt? >>>> >>>> ++ >>>> Corinne >>>> [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365 >>>> [2] https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png >>>> [3] http://aerogear.org/download/ >>>> [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html >>>> [5] http://aerogear.org/download/custom/ >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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 corinnekrych at gmail.com Mon Mar 3 09:18:39 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 3 Mar 2014 15:18:39 +0100 Subject: [aerogear-dev] [ag.org revamp] GET IT page structure In-Reply-To: <53148E18.6000209@redhat.com> References: <7A9B8315-0712-4E89-91C7-5E7DF21ED712@gmail.com> <53146F88.8090906@redhat.com> <34AFA707-3E10-4142-A30B-D309261977AA@gmail.com> <53148E18.6000209@redhat.com> Message-ID: <1CA87339-8B60-40C5-8A5F-24636C5AB98B@gmail.com> On 03 Mar 2014, at 15:13, Hylke Bons wrote: > Thanks Corinne and Sebastien for the list, that's useful to have. > > "- You want to revisit our librairies split to fit in the web site restructure." > > > No, the website mockups are just one example how things can be > structured. It makes many assumptions, some of which may not be possible > right now. It doesn't neccesarily have to be according the the mockups. > > I _do_ want revisit the libraries split, because there are > inconsistencies and no website redesign is going to fix them. With the list provided i think it?s doable. Where do you think there is a problem? Let?s be more specific. > I need > your help to find out where the problems lie, and if we can't do it this > way, let's find another one, but the current situation is problematic if > we want to implement anything coherent. > > Thanks, > > Hylke > > > On 03/03/2014 13:54, Corinne Krych wrote: >> Thanks Sebi for the correction! >> ++ >> Corinne >> On 03 Mar 2014, at 14:51, Sebastien Blanc wrote: >> >>> >>> >>> On Mon, Mar 3, 2014 at 2:45 PM, Corinne Krych wrote: >>> Hello Hylke >>> >>> I guess we had a different approach here: >>> - You want to revisit our librairies split to fit in the web site restructure. >>> - I want to fit the actual libraries split into your new web site, making adjustment to web site design. >>> >>> Let me detail out libraries a bit more. Here is a list of existing split with matching gh repo (when available) that we can use as a starting point for our GET IT page: >>> >>> ********* >>> Core - Server: nope, just an example >>> --- >>> Core - Client iOS: https://github.com/aerogear/aerogear-ios >>> Core - Client JS: https://github.com/aerogear/aerogear-js >>> Core - Client Android: https://github.com/aerogear/aerogear-android >>> Core - Client Cordova: n/a >>> ********* >>> Push - UnifiedPush Server: https://github.com/aerogear/aerogear-unifiedpush-server >>> Push - UnifiedPush Server Java Sender API: https://github.com/aerogear/aerogear-unifiedpush-java-client >>> Push - UnifiedPush Server Node Sender API (JS): https://github.com/aerogear/aerogear-unifiedpush-nodejs-client >>> Push - SimplePush Server: https://github.com/aerogear/aerogear-simplepush-server >>> Push - SimplePush Server Java Sender API: https://github.com/aerogear/aerogear-simplepush-java-client >>> Push - SimplePush Server Node Sender API (JS): https://github.com/aerogear/aerogear-simplepush-node-client >>> --- >>> Push - Client iOS: UnifiedPush.Registration: https://github.com/aerogear/aerogear-push-ios-registration >>> Push - Client JS: UnifiedPush.Registration: n/a >>> Actually, we have this in the JS core repo. >>> Push - Client Android: UnifiedPush.Registration: >>> Push - Client Cordova: UnifiedPush.Registration: https://github.com/aerogear/aerogear-pushplugin-cordova >>> --- >>> Push - Client iOS: SimpledPush: n/a >>> Push - Client JS: SimplePush: JS core repo >>> Push - Client Android: SimplePush: n/a >>> Push - Client Cordova: SimplePush: n/a - nothing yet >>> ********* >>> Security - Server Shiro Adapter: https://github.com/aerogear/aerogear-security-shiro >>> Security - Server PicketLink Adapter: https://github.com/aerogear/aerogear-security-picketlink >>> Security - Server Hawk Adapter: https://github.com/aerogear/aerogear-security-hawk >>> Security - Server Crypto: https://github.com/aerogear/aerogear-crypto-java >>> --- >>> Security - Client iOS Security.OTP: https://github.com/aerogear/aerogear-otp-ios >>> Security - Client JS Security.OTP: https://github.com/aerogear/aerogear-otp-java >>> Security - Client Android Security.OTP: https://github.com/aerogear/aerogear-otp-js >>> Security - Client Cordova Security.OTP: https://github.com/aerogear/aerogear-otp-cordova >>> --- >>> Security - Client iOS Security.Crypto: https://github.com/aerogear/aerogear-crypto-ios >>> Security - Client JS Security.Crypto: https://github.com/aerogear/aerogear-crypto-java >>> Security - Client Android Security.Crypto: JS core repo >>> Security - Client Cordova Security.Crypto: https://github.com/aerogear/aerogear-crypto-cordova >>> ********* >>> Note: that JavaScript libraries although not splitted into different repos still offer fine grained libraries with the Custom build feature. >>> I didn?t know where to put: https://github.com/aerogear/aerogear-geo-cordova. >>> >>> @all, feel free to correct if I missed some repo. >>> >>> As you can see we have something that we could fit in our GET IT page. I?m convinced though, that a PLATFORM GET IT page (which would provide a PLATFORM view) will be really useful. >>> >>> ++ >>> Corinne >>> >>> On 03 Mar 2014, at 13:03, Hylke Bons wrote: >>> >>>> Hello, >>>> >>>> Can we hold a larger high level discussion about the project's package >>>> organisation and splits? I really think this is needed before we can >>>> actually come up with a good design for this. >>>> >>>> Otherwise I'm afraid we'll end up with inconsistent and confusing pages, >>>> not a whole lot better than our current download pages. >>>> >>>> I've already written down some of my thoughts on this: >>>> http://oksoclap.com/p/AeroGearModuleUntangling >>>> >>>> What I can do right now is mock up the flow from the download page to >>>> the different platform client setup pages. >>>> >>>> Hylke >>>> >>>> >>>> On 03/03/2014 11:17, Corinne Krych wrote: >>>>> Hello All, >>>>> >>>>> Following Hylke?s thread on web site restructure [1], I?d like to start a new thread to discuss GET IT pages in the mockup section [2]. Those pages will replace the ?get started? page on the current web site [3]. >>>>> >>>>> As Hylke said it, we don?t necesseraly have a the same split of libraries in the differents platforms. Some thing to carry on working on; for example in iOS, we do have a thread opened for iOS small libs [4]. >>>>> >>>>> To make an initial working GET IT page, we could have a list of libraries per features but we also need a link to a PLATFORM GET IT page. >>>>> >>>>> The PLATFORM GET IT page, it?s similar to the PLATFORM EXAMPLES page where we need a view per platform. We should have a iOS GET IT which split between sever/client and displays all libraries with code color for different features. For JavaScript this page will contain the custom builder tool [5]. >>>>> >>>>> @hbons How can we make the transition from GET IT to PLATFORM GET IT page? shall we add a link from HOME page to PLATFORM GET IT page? >>>>> >>>>> wdyt? >>>>> >>>>> ++ >>>>> Corinne >>>>> [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-structure-and-the-website-td6364.html#a6365 >>>>> [2] https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-project.png >>>>> [3] http://aerogear.org/download/ >>>>> [4] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-iOS-small-libs-td6137.html >>>>> [5] http://aerogear.org/download/custom/ >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From tkriz at redhat.com Mon Mar 3 09:26:48 2014 From: tkriz at redhat.com (Tadeas Kriz) Date: Mon, 3 Mar 2014 15:26:48 +0100 Subject: [aerogear-dev] [aerogear-ios] Protocol draft for reading from pipe Message-ID: <75ABD301-B4EF-48E6-BC2E-DFDBA57F218D@redhat.com> Hey guys, I?ve been thinking about the way how reading from pipe and I thought of a way to do it a bit differently, so there?s no need to extend the NSMutableArray using the category (which for me doesn?t seem as the best way to do this). https://gist.github.com/TadeasKriz/9325698 What do you think? ? Tadeas Kriz tkriz at redhat.com From daniel.bevenius at gmail.com Mon Mar 3 10:11:30 2014 From: daniel.bevenius at gmail.com (danielbevenius) Date: Mon, 3 Mar 2014 07:11:30 -0800 (PST) Subject: [aerogear-dev] Team meeting agenda In-Reply-To: References: Message-ID: <1393859490493-6616.post@n5.nabble.com> Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-03-14.48.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-03-14.48.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-03-14.48.log.html -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Team-meeting-agenda-tp6612p6616.html Sent from the aerogear-dev mailing list archive at Nabble.com. From supittma at redhat.com Mon Mar 3 10:17:03 2014 From: supittma at redhat.com (Summers Pittman) Date: Mon, 03 Mar 2014 10:17:03 -0500 Subject: [aerogear-dev] Comparing sync in Android vs other platforms Message-ID: <53149CEF.5090509@redhat.com> For the DevNexus Android app[1] I used Android native sync APIs[2] + the sync strawman[3] I put out back in December. It worked surprisingly well with a few caveats. First a background on how Android sync works. Android sync is handled by three components: a SyncAdapter, a ContentProvider, and a Authenticator. The Sync Adapter performs as sync and returns a status object. The SyncAdapter is called from, managed by, etc the Android platform. It provides an onPerformSync that the developer implements. In the application the developer sends signals to Android which control scheduling sync (periodic, immediate, event based etc). Also Android will put in the "Account" settings page a control for the SyncAdapter. In this case the SQLSynchronizer I proposed was used to implement this method. The ContentProvider is responsible for CRUD operations on your data, exposing your data to other apps on the device, and notifying the system if data changes. This is managed by Android as well. In this case the CP was backed by a SQLStore. Finally the Android Authenticator is responsible for establishing and maintaining authentication with remote services. If the user is not signed in, or if fetching an auth token fails, the Authenticator will be called by Android to provide a Activity which can be used to refresh the users account. In this case I used two custom AuthenticationModules. One handled SSO with Google and the other handled keeping the cookie up to date. Both communicated with the DevNexus server to keep all of the tokens fresh. Overall, Android provides a very VERY slick (but very very complicated) way of managing sync AND keeping the sync state visible to the user. If you use Androids APIs then the OS handles things like Authentication errors, intermittent connectivity, etc while providing configuration for a variety of sync use cases (UI event based, polling, data listening, etc). I tried looking up what options are available in JS land but the closest I came to was a FFOS blurb about it is a TODO item and isn't a W3C proposal or anything yet. I tried looking at iOS but the docs made my eyes cross. So what does the PLATFORM support look like in these environments? ---- [1]https://github.com/secondsun/devnexusAndroid [2]http://developer.android.com/training/sync-adapters/index.html [3]https://github.com/secondsun/aerogear-android/tree/sync_strawman/src/org/jboss/aerogear/android/sync From matzew at apache.org Tue Mar 4 03:55:06 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 4 Mar 2014 09:55:06 +0100 Subject: [aerogear-dev] Compose Push UI - draft (was: Re: UnifiedPush: Sending notifications from the AdminUI) In-Reply-To: References: <530F76C5.1090702@redhat.com> <5310A471.5010609@redhat.com> Message-ID: On Fri, Feb 28, 2014 at 7:14 PM, Sebastien Blanc wrote: > I really like this version :) > Great work Hylke ! > yes. looks very good! > > > > On Fri, Feb 28, 2014 at 4:00 PM, Hylke Bons wrote: > >> Hey, >> >> I've iterated a bit more on the design taking in mind everyone's feedback: >> >> https://raw.github.com/hbons/aerogear-design/master/tests/send-message-iteration2.png >> >> We now have a single form, with more of a "hob and spokes" model for >> changing details as opposed to a "wizard", keeping all the previous >> functionality. This allows us to send messages quickly whilst always having >> a clear summary of what's going to happen before sending the notifications. >> >> Hylke >> >> >> >> >> On 27/02/2014 17:32, Hylke Bons wrote: >> >> Hey, >> >> After some discussion with Sebastien, here's the first iteration of the >> design: >> https://raw.github.com/hbons/aerogear-design/master/tests/send-message.png >> >> It shows a summary at the end of the form for review, as sending messages >> can go very badly if a mistake was made in the form. It may look a bit >> excessive with the different pages, but it's an important case with actions >> that can't be undone. >> >> Let me know your thoughts and whether this is at all possible. >> >> Hylke >> >> >> On 26/02/2014 09:15, Sebastien Blanc wrote: >> >> Hi, >> An update : here the latest screenshot of the current UI : >> >> >> And also now you can test it for real since I deployed a new version >> that manage the sending : : http://newpush-sblanc.rhcloud.com (admin >> /123) >> >> >> On Tue, Feb 25, 2014 at 11:36 AM, Matthias Wessendorf wrote: >> >>> Hello Sebi, >>> >>> that looks really nice! >>> >>> Hylke can you take a look at the first version, from a UX persons view? >>> >>> Thanks! >>> Matthias >>> >>> >>> On Tue, Feb 25, 2014 at 10:06 AM, Sebastien Blanc wrote: >>> >>>> Hi, >>>> I started to work on a new "Compose Message" page. The idea is that you >>>> can add criterias to your message , as you can see here on this screenshot >>>> : >>>> [image: compose2] >>>> >>> >> >> >>> I've also deployed a live version but *DICSLAIMER* this is just UI >>>> / Mockup work sending will not work for now : >>>> http://newpush-sblanc.rhcloud.com => Select an App and you will have >>>> a "Copomse Message" link on the next page. >>>> >>>> Feedback is welcome. >>>> Sebi >>>> >>>> >>>> On Mon, Feb 24, 2014 at 1:25 PM, Sebastien Blanc wrote: >>>> >>>>> >>>>> >>>>> >>>>> On Mon, Feb 24, 2014 at 12:52 PM, Hylke Bons wrote: >>>>> >>>>>> Sounds good. >>>>>> Let me know if you need any help with the mockup designs. ;) >>>>>> >>>>> Sure, I will ASAP submit a "raw" mockup on which you can work on. >>>>> What I would like is a dedicated page for the "Compose Push Message" >>>>> feature. >>>>> >>>>> We wil have a criteria section to choose to who we want to send the >>>>> message. I really like for instance how Jira do that like here >>>>> http://postimg.org/image/5ur2j9wh5/ >>>>> In our case we could have the drop downs for : "Variants", "Device >>>>> Type", "Alias" and "Categories" >>>>> And then below w will have a free text area to send a custom value. >>>>> >>>>> >>>>>> >>>>>> Hylke >>>>>> >>>>>> >>>>>> >>>>>> On 23/02/2014 12:08, Sebastien Blanc wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Sun, Feb 23, 2014 at 1:04 PM, Matthias Wessendorf < >>>>>> matzew at apache.org> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> over the weekend I spoke w/ a friend: His company is doing some >>>>>>> mobile (iOS/Android) apps which also support receiving push notifications. >>>>>>> >>>>>>> Two examples he told me. After receiving push notification: >>>>>>> >>>>>>> * One of their apps basically fetches the latest version of a CSV >>>>>>> file, stored on a public HTTP Server. >>>>>>> >>>>>>> * Another app is used to tell sales guys new brochure files (PDF) >>>>>>> are available on a protected resource of a webserver (which they _can_ than >>>>>>> download from w/in the app, if the like to) >>>>>>> >>>>>>> The company build a simple console (PHP) which allows them to send >>>>>>> new push messages, when ever their customers want to. >>>>>>> >>>>>>> I showed them our UnifiedPush Server and its usage via our AeroDoc >>>>>>> example (iOS / backend). They really liked the UnifiedPush Server. >>>>>>> Especially that it does store all the device metadata. >>>>>>> >>>>>>> But since a lot of their mobile apps don't have a backend >>>>>>> requirement, they would still have to use their own console (which than >>>>>>> connects to UPS) for submitting all the push messages they want. >>>>>>> >>>>>>> >>>>>>> >>>>>>> This brings me to [AGPUSH-38] and I really think we should >>>>>>> implement that feature. Not only for sending test messages! If our >>>>>>> UnifiedPush Server allows its users to simple send push messages to all of >>>>>>> their mobile apps, it would make the server even more attractive. >>>>>>> >>>>>>> I regret a bit that I was against [AGPUSH-38] in the beginning, I >>>>>>> guess that's due to my Java enterprise background, where you typically find >>>>>>> complex setups, and server talk to servers :-( >>>>>>> >>>>>>> Anyways, now I really think that the UPS has to have such a 'send >>>>>>> push' facility inside of the Admin UI :-) I believe that we could reach way >>>>>>> more potential users with something like that >>>>>>> >>>>>> +9001 and I already started thinking about this for a while. I will >>>>>> try to submit some mockups/POCs this week so we can discuss that and I have >>>>>> quickly a first working version on master. >>>>>> >>>>>> >>>>>>> Any thoughts? >>>>>>> >>>>>>> >>>>>>> Greetings, >>>>>>> Matthias >>>>>>> >>>>>>> >>>>>>> [AGPUSH-38] https://issues.jboss.org/browse/AGPUSH-38 >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Matthias Wessendorf >>>>>>> >>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>> sessions: http://www.slideshare.net/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 >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.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 >> >> >> >> >> _______________________________________________ >> 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 >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140304/e1f32458/attachment-0001.html From corinnekrych at gmail.com Tue Mar 4 05:02:36 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 4 Mar 2014 11:02:36 +0100 Subject: [aerogear-dev] [aerogear-ios] Protocol draft for reading from pipe In-Reply-To: <75ABD301-B4EF-48E6-BC2E-DFDBA57F218D@redhat.com> References: <75ABD301-B4EF-48E6-BC2E-DFDBA57F218D@redhat.com> Message-ID: <3A7F39EE-86BA-451D-9ABC-9A4BB1DEC49E@gmail.com> Hello Tadeas Talking a Pipe and Paging, when we were designing them we were discussing with JS and Android team, and in iOS we follow the same approach to provide a unified API. Compare Android impl [1] which extends List providing next and previous method to iOS counterpart [2] => It?s very similar. Instead of using Inheritance we?re using category[3] which is good fit for it. What do you mean by "for me doesn?t seem as the best way to do this?? However if you want to help on the topic of Paging, we?re missing a cool recipe app (see [4]) ! PR are always welcome. ++ Corinne [1] https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/pipeline/paging/PagedList.java [2] https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/pipeline/AGNSMutableArray%2BPaging.h#L114 [3] http://www.intertech.com/Blog/categories-in-objective-c/ [4] https://issues.jboss.org/browse/AGIOS-127 On 03 Mar 2014, at 15:26, Tadeas Kriz wrote: > Hey guys, > > I?ve been thinking about the way how reading from pipe and I thought of a way to do it a bit differently, so there?s no need to extend the NSMutableArray using the category (which for me doesn?t seem as the best way to do this). > > https://gist.github.com/TadeasKriz/9325698 > > What do you think? > > ? > Tadeas Kriz > tkriz at redhat.com > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From tkriz at redhat.com Tue Mar 4 06:34:41 2014 From: tkriz at redhat.com (Tadeas Kriz) Date: Tue, 4 Mar 2014 12:34:41 +0100 Subject: [aerogear-dev] [aerogear-ios] Protocol draft for reading from pipe In-Reply-To: <3A7F39EE-86BA-451D-9ABC-9A4BB1DEC49E@gmail.com> References: <75ABD301-B4EF-48E6-BC2E-DFDBA57F218D@redhat.com> <3A7F39EE-86BA-451D-9ABC-9A4BB1DEC49E@gmail.com> Message-ID: <39828547-0DBA-4E70-A6E2-6FBBB28CB870@redhat.com> ? Tadeas Kriz tkriz at redhat.com On 04 Mar 2014, at 11:02, Corinne Krych wrote: > Hello Tadeas > > Talking a Pipe and Paging, when we were designing them we were discussing with JS and Android team, and in iOS we follow the same approach to provide a unified API. > > Compare Android impl [1] which extends List providing next and previous method to iOS counterpart [2] > => It?s very similar. Instead of using Inheritance we?re using category[3] which is good fit for it. What do you mean by "for me doesn?t seem as the best way to do this?? I mean that the category will extend basically every NSMutableArray, even those that has nothing to do with AeroGear and it feels strange to me, but if you say it?s to keep the consistency with Android and JS, I understand it. > However if you want to help on the topic of Paging, we?re missing a cool recipe app (see [4]) ! > PR are always welcome. > > ++ > Corinne > [1] https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/pipeline/paging/PagedList.java > [2] https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/pipeline/AGNSMutableArray%2BPaging.h#L114 > [3] http://www.intertech.com/Blog/categories-in-objective-c/ > [4] https://issues.jboss.org/browse/AGIOS-127 > > On 03 Mar 2014, at 15:26, Tadeas Kriz wrote: > >> Hey guys, >> >> I?ve been thinking about the way how reading from pipe and I thought of a way to do it a bit differently, so there?s no need to extend the NSMutableArray using the category (which for me doesn?t seem as the best way to do this). >> >> https://gist.github.com/TadeasKriz/9325698 >> >> What do you think? >> >> ? >> Tadeas Kriz >> tkriz at redhat.com >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From corinnekrych at gmail.com Tue Mar 4 08:06:27 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 4 Mar 2014 14:06:27 +0100 Subject: [aerogear-dev] [aerogear-ios] Protocol draft for reading from pipe In-Reply-To: <39828547-0DBA-4E70-A6E2-6FBBB28CB870@redhat.com> References: <75ABD301-B4EF-48E6-BC2E-DFDBA57F218D@redhat.com> <3A7F39EE-86BA-451D-9ABC-9A4BB1DEC49E@gmail.com> <39828547-0DBA-4E70-A6E2-6FBBB28CB870@redhat.com> Message-ID: On 04 Mar 2014, at 12:34, Tadeas Kriz wrote: > > ? > Tadeas Kriz > tkriz at redhat.com > > On 04 Mar 2014, at 11:02, Corinne Krych wrote: > >> Hello Tadeas >> >> Talking a Pipe and Paging, when we were designing them we were discussing with JS and Android team, and in iOS we follow the same approach to provide a unified API. >> >> Compare Android impl [1] which extends List providing next and previous method to iOS counterpart [2] >> => It?s very similar. Instead of using Inheritance we?re using category[3] which is good fit for it. What do you mean by "for me doesn?t seem as the best way to do this?? > > I mean that the category will extend basically every NSMutableArray, even those that has nothing to do with AeroGear and it feels strange to me, but if you say it?s to keep the consistency with Android and JS, I understand it. I guess it?s a matter of design preferences here. Both will fit the bill. Composition over inheritance. Use categories as you would use ?mixins?, if you just wanto to add a extra flavor to your class (here NSMutableArray), it?s a good fit to do it with category. To have the category available you need to have the import "AGNSMutableArray+Paging.h" Besides, if you send a next/previous message on a NSMutableArray without Pipe, nothing happen. > >> However if you want to help on the topic of Paging, we?re missing a cool recipe app (see [4]) ! >> PR are always welcome. >> >> ++ >> Corinne >> [1] https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/pipeline/paging/PagedList.java >> [2] https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/pipeline/AGNSMutableArray%2BPaging.h#L114 >> [3] http://www.intertech.com/Blog/categories-in-objective-c/ >> [4] https://issues.jboss.org/browse/AGIOS-127 >> >> On 03 Mar 2014, at 15:26, Tadeas Kriz wrote: >> >>> Hey guys, >>> >>> I?ve been thinking about the way how reading from pipe and I thought of a way to do it a bit differently, so there?s no need to extend the NSMutableArray using the category (which for me doesn?t seem as the best way to do this). >>> >>> https://gist.github.com/TadeasKriz/9325698 >>> >>> What do you think? >>> >>> ? >>> Tadeas Kriz >>> tkriz at redhat.com >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From tkriz at redhat.com Tue Mar 4 08:18:42 2014 From: tkriz at redhat.com (Tadeas Kriz) Date: Tue, 4 Mar 2014 14:18:42 +0100 Subject: [aerogear-dev] [aerogear-ios] Protocol draft for reading from pipe In-Reply-To: References: <75ABD301-B4EF-48E6-BC2E-DFDBA57F218D@redhat.com> <3A7F39EE-86BA-451D-9ABC-9A4BB1DEC49E@gmail.com> <39828547-0DBA-4E70-A6E2-6FBBB28CB870@redhat.com> Message-ID: ? Tadeas Kriz tkriz at redhat.com On 04 Mar 2014, at 14:06, Corinne Krych wrote: > > On 04 Mar 2014, at 12:34, Tadeas Kriz wrote: > >> >> ? >> Tadeas Kriz >> tkriz at redhat.com >> >> On 04 Mar 2014, at 11:02, Corinne Krych wrote: >> >>> Hello Tadeas >>> >>> Talking a Pipe and Paging, when we were designing them we were discussing with JS and Android team, and in iOS we follow the same approach to provide a unified API. >>> >>> Compare Android impl [1] which extends List providing next and previous method to iOS counterpart [2] >>> => It?s very similar. Instead of using Inheritance we?re using category[3] which is good fit for it. What do you mean by "for me doesn?t seem as the best way to do this?? >> >> I mean that the category will extend basically every NSMutableArray, even those that has nothing to do with AeroGear and it feels strange to me, but if you say it?s to keep the consistency with Android and JS, I understand it. > > I guess it?s a matter of design preferences here. Both will fit the bill. Composition over inheritance. You?re right. > Use categories as you would use ?mixins?, if you just wanto to add a extra flavor to your class (here NSMutableArray), it?s a good fit to do it with category. To have the category available you need to have the import "AGNSMutableArray+Paging.h? The category's .m code is still present in the class, only the API isn?t visible, isn?t that right? But that?s just off topic question of mine. > Besides, if you send a next/previous message on a NSMutableArray without Pipe, nothing happen. +1 >> >>> However if you want to help on the topic of Paging, we?re missing a cool recipe app (see [4]) ! >>> PR are always welcome. >>> >>> ++ >>> Corinne >>> [1] https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/pipeline/paging/PagedList.java >>> [2] https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/pipeline/AGNSMutableArray%2BPaging.h#L114 >>> [3] http://www.intertech.com/Blog/categories-in-objective-c/ >>> [4] https://issues.jboss.org/browse/AGIOS-127 >>> >>> On 03 Mar 2014, at 15:26, Tadeas Kriz wrote: >>> >>>> Hey guys, >>>> >>>> I?ve been thinking about the way how reading from pipe and I thought of a way to do it a bit differently, so there?s no need to extend the NSMutableArray using the category (which for me doesn?t seem as the best way to do this). >>>> >>>> https://gist.github.com/TadeasKriz/9325698 >>>> >>>> What do you think? >>>> >>>> ? >>>> Tadeas Kriz >>>> tkriz at redhat.com >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 Mar 4 08:55:13 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 4 Mar 2014 14:55:13 +0100 Subject: [aerogear-dev] [aerogear-ios] Protocol draft for reading from pipe In-Reply-To: References: <75ABD301-B4EF-48E6-BC2E-DFDBA57F218D@redhat.com> <3A7F39EE-86BA-451D-9ABC-9A4BB1DEC49E@gmail.com> <39828547-0DBA-4E70-A6E2-6FBBB28CB870@redhat.com> Message-ID: On 04 Mar 2014, at 14:18, Tadeas Kriz wrote: > > ? > Tadeas Kriz > tkriz at redhat.com > > On 04 Mar 2014, at 14:06, Corinne Krych wrote: > >> >> On 04 Mar 2014, at 12:34, Tadeas Kriz wrote: >> >>> >>> ? >>> Tadeas Kriz >>> tkriz at redhat.com >>> >>> On 04 Mar 2014, at 11:02, Corinne Krych wrote: >>> >>>> Hello Tadeas >>>> >>>> Talking a Pipe and Paging, when we were designing them we were discussing with JS and Android team, and in iOS we follow the same approach to provide a unified API. >>>> >>>> Compare Android impl [1] which extends List providing next and previous method to iOS counterpart [2] >>>> => It?s very similar. Instead of using Inheritance we?re using category[3] which is good fit for it. What do you mean by "for me doesn?t seem as the best way to do this?? >>> >>> I mean that the category will extend basically every NSMutableArray, even those that has nothing to do with AeroGear and it feels strange to me, but if you say it?s to keep the consistency with Android and JS, I understand it. >> >> I guess it?s a matter of design preferences here. Both will fit the bill. Composition over inheritance. > > You?re right. > >> Use categories as you would use ?mixins?, if you just wanto to add a extra flavor to your class (here NSMutableArray), it?s a good fit to do it with category. To have the category available you need to have the import "AGNSMutableArray+Paging.h? > > The category's .m code is still present in the class, only the API isn?t visible, isn?t that right? Yep indeed. > But that?s just off topic question of mine. > >> Besides, if you send a next/previous message on a NSMutableArray without Pipe, nothing happen. > > +1 > >>> >>>> However if you want to help on the topic of Paging, we?re missing a cool recipe app (see [4]) ! >>>> PR are always welcome. >>>> >>>> ++ >>>> Corinne >>>> [1] https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/pipeline/paging/PagedList.java >>>> [2] https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/pipeline/AGNSMutableArray%2BPaging.h#L114 >>>> [3] http://www.intertech.com/Blog/categories-in-objective-c/ >>>> [4] https://issues.jboss.org/browse/AGIOS-127 >>>> >>>> On 03 Mar 2014, at 15:26, Tadeas Kriz wrote: >>>> >>>>> Hey guys, >>>>> >>>>> I?ve been thinking about the way how reading from pipe and I thought of a way to do it a bit differently, so there?s no need to extend the NSMutableArray using the category (which for me doesn?t seem as the best way to do this). >>>>> >>>>> https://gist.github.com/TadeasKriz/9325698 >>>>> >>>>> What do you think? >>>>> >>>>> ? >>>>> Tadeas Kriz >>>>> tkriz at redhat.com >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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 lgraham at redhat.com Tue Mar 4 10:29:24 2014 From: lgraham at redhat.com (Lee Graham) Date: Tue, 4 Mar 2014 10:29:24 -0500 (EST) Subject: [aerogear-dev] AeroGear project structure and the website In-Reply-To: <530CD63F.9060300@redhat.com> References: <53060BE2.6030803@redhat.com> <80A6BAD7-8EBD-4D55-9FE8-267BF3474603@gmail.com> <309198315.8064032.1393253413875.JavaMail.zimbra@redhat.com> <530CD63F.9060300@redhat.com> Message-ID: <2034169871.13133471.1393946964631.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Hylke Bons" > To: aerogear-dev at lists.jboss.org > Sent: Tuesday, February 25, 2014 12:43:27 PM > Subject: Re: [aerogear-dev] AeroGear project structure and the website > On 24/02/2014 14:50, Lee Graham wrote: > > So If I'm a Cordova developer and I want to learn how-to setup > > UnifiedPush Server and integrate Push within my hybrid app I don't > > care about the native Android & iOS libraries, guides, etc.. I just > > want everything that is relevant to hybrid apps. I actually ran into > > this exact issue this last weekend when I created my first push > > notification app. Its hard to keep track of what guides and sample > > code I needed. This may solve that. I kind of like the way > > http://devcenter.kinvey.com/ does this. When I first go there it > > allows me to select my dev platform and it sets a cookie so when I > > come back its still on that platform. I can swap at any time, but as a > > developer I really liked the Kinvey experience because I could find > > what I needed. Nothing more nothing less. > Cordova is a bit of a special case. Apart from a mention that Cordova is > a supported platform on the front page, I'm not quite if we should have > it as a mention for every feature, as we already have Javascript there. > We need to find out how Corodova developers normally go about picking > libraries that they want to use. I assume they can use any Javascript > library? Perhaps we just add a note to the download page that for use > with Cordova you case use the Javascript library and download a native > plugin if needed. Makes sense to me. I think the current site does confuse me a bit... what's the difference between Web/JavaScript and Hybrid/Cordova. If we are using the same exact code (aerogear.js) then my first thought is just to combine that under JavaScript (which I think is your suggestion?). If the code is similar, but different between Web and Hybrid then it may be useful to clearly define the differences. As a Cordova developer, I'm not a hardcore Java or Objective-C developer. So my first thought is to find a plugin. If that doesn't exist, I'm looking for JavaScript. I want the fastest route (aka the least amount of coding) to integrating 3rd party tools and making it work for both Android and iOS apps. Example 1: AeroGear push notification, I used the plugin. Example 2: Count.ly mobile analytics, I use the community Countly SDK JS because there is no plugin: https://github.com/Countly/countly-sdk-js I hope this helps. I do really love the new look and feel of the mockups. Very clean! > Hylke > _______________________________________________ > 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/20140304/80b932bb/attachment-0001.html From edewit at redhat.com Tue Mar 4 10:47:12 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 4 Mar 2014 16:47:12 +0100 Subject: [aerogear-dev] AeroGear project structure and the website In-Reply-To: <2034169871.13133471.1393946964631.JavaMail.zimbra@redhat.com> References: <53060BE2.6030803@redhat.com> <80A6BAD7-8EBD-4D55-9FE8-267BF3474603@gmail.com> <309198315.8064032.1393253413875.JavaMail.zimbra@redhat.com> <530CD63F.9060300@redhat.com> <2034169871.13133471.1393946964631.JavaMail.zimbra@redhat.com> Message-ID: <742DA952-5AC1-49A6-9B56-2C5E389DA323@redhat.com> > Makes sense to me. I think the current site does confuse me a bit... what's the difference between Web/JavaScript and Hybrid/Cordova. If we are using the same exact code (aerogear.js) then my first thought is just to combine that under JavaScript (which I think is your suggestion?). If the code is similar, but different between Web and Hybrid then it may be useful to clearly define the differences. > It?s a bit complex to explain and on the current site it?s not clear I agree. Not all functionality that is in the Javascript project is available in Cordova and the functionality that is has a different api. So a developer that will target Cordova will probably end up using both. The reason that only some parts of the Javascript have been put into Cordova is that for those parts it makes sense to use native hardware because of security, speed or integration, in other cases it doesn?t bring enough benefit. Because of the way Cordova plugins work it has not always been possible to have the same API although they are close most of the time. Hope this helps explain things a bit more. Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/34b91a86/attachment.html From lgraham at redhat.com Tue Mar 4 10:56:10 2014 From: lgraham at redhat.com (Lee Graham) Date: Tue, 4 Mar 2014 10:56:10 -0500 (EST) Subject: [aerogear-dev] AeroGear project structure and the website In-Reply-To: <742DA952-5AC1-49A6-9B56-2C5E389DA323@redhat.com> References: <53060BE2.6030803@redhat.com> <80A6BAD7-8EBD-4D55-9FE8-267BF3474603@gmail.com> <309198315.8064032.1393253413875.JavaMail.zimbra@redhat.com> <530CD63F.9060300@redhat.com> <2034169871.13133471.1393946964631.JavaMail.zimbra@redhat.com> <742DA952-5AC1-49A6-9B56-2C5E389DA323@redhat.com> Message-ID: <1523346370.13146391.1393948570395.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Erik Jan de Wit" > To: "AeroGear Developer Mailing List" > Sent: Tuesday, March 4, 2014 10:47:12 AM > Subject: Re: [aerogear-dev] AeroGear project structure and the website > > Makes sense to me. I think the current site does confuse me a bit... what's > > the difference between Web/JavaScript and Hybrid/Cordova. If we are using > > the same exact code (aerogear.js) then my first thought is just to combine > > that under JavaScript (which I think is your suggestion?). If the code is > > similar, but different between Web and Hybrid then it may be useful to > > clearly define the differences. > > It?s a bit complex to explain and on the current site it?s not clear I agree. > Not all functionality that is in the Javascript project is available in > Cordova and the functionality that is has a different api. So a developer > that will target Cordova will probably end up using both. > The reason that only some parts of the Javascript have been put into Cordova > is that for those parts it makes sense to use native hardware because of > security, speed or integration, in other cases it doesn?t bring enough > benefit. > Because of the way Cordova plugins work it has not always been possible to > have the same API although they are close most of the time. > Hope this helps explain things a bit more. Thanks. This does help alot > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/adb37f99/attachment.html From scm.blanc at gmail.com Tue Mar 4 12:09:16 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 4 Mar 2014 18:09:16 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets Message-ID: Hi, I've started to work on AGPUSH-550 where the idea is to generate Device Registration code Snippets that the user can copy/paste into his client application. The flow is quite simple : he chooses a Variant, then click a link on the right that brings you to the Snippets page. Since the console knows the type of the selected variant, the appropriate snippet is generated ... Yes "generated" , that means it's not a static code snippet but it's actually filled with the needed info : UPS Server URL, Variant ID, Variant Secret, SenderId (for Android). For each code snippet, there also the Cordova version for it. So, if you choose an Android variant for instance you will have : [image: Inline image 1] And as you can see, there is also a link to cordova : [image: Inline image 2] This is still work in progress, needs polishing etc ... But once we got this, it will be really easy for a new user to get started. All the variants type are covered : iOS, Android and SPS Oh, want to test it live ? Give it a try here : https://newpush-sblanc.rhcloud.com/ (admin / 123) I will probably PR that very soon, in the same time you can check this branch https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if you want to play with it locally. See you ! Sebi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/b15d09ba/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/b15d09ba/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/b15d09ba/attachment-0003.png From edewit at redhat.com Tue Mar 4 14:19:13 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 4 Mar 2014 20:19:13 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: <33067105-A30C-4777-83B4-B7F309A8F241@redhat.com> Works like a charm, like how much smaller the cordova code is. On 4 Mar,2014, at 18:09 , Sebastien Blanc wrote: > Hi, > > I've started to work on AGPUSH-550 where the idea is to generate Device Registration code Snippets that the user can copy/paste into his client application. > > The flow is quite simple : he chooses a Variant, then click a link on the right that brings you to the Snippets page. > Since the console knows the type of the selected variant, the appropriate snippet is generated ... Yes "generated" , that means it's not a static code snippet but it's actually filled with the needed info : UPS Server URL, Variant ID, Variant Secret, SenderId (for Android). > > For each code snippet, there also the Cordova version for it. So, if you choose an Android variant for instance you will have : > > > > And as you can see, there is also a link to cordova : > > > > This is still work in progress, needs polishing etc ... But once we got this, it will be really easy for a new user to get started. All the variants type are covered : iOS, Android and SPS > > Oh, want to test it live ? Give it a try here : https://newpush-sblanc.rhcloud.com/ (admin / 123) > > I will probably PR that very soon, in the same time you can check this branch https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if you want to play with it locally. > > See you ! > 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/20140304/d7a77db7/attachment.html From matzew at apache.org Tue Mar 4 15:42:29 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 4 Mar 2014 21:42:29 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: I like it! for the native iOS code I think some CSS for the background is missing. Cheers! Matthias On Tue, Mar 4, 2014 at 6:09 PM, Sebastien Blanc wrote: > Hi, > > I've started to work on AGPUSH-550 where > the idea is to generate Device Registration code Snippets that the user can > copy/paste into his client application. > > The flow is quite simple : he chooses a Variant, then click a link on the > right that brings you to the Snippets page. > Since the console knows the type of the selected variant, the appropriate > snippet is generated ... Yes "generated" , that means it's not a static > code snippet but it's actually filled with the needed info : UPS Server > URL, Variant ID, Variant Secret, SenderId (for Android). > > For each code snippet, there also the Cordova version for it. So, if you > choose an Android variant for instance you will have : > > [image: Inline image 1] > > And as you can see, there is also a link to cordova : > > [image: Inline image 2] > > This is still work in progress, needs polishing etc ... But once we got > this, it will be really easy for a new user to get started. All the > variants type are covered : iOS, Android and SPS > > Oh, want to test it live ? Give it a try here : > https://newpush-sblanc.rhcloud.com/ (admin / 123) > > I will probably PR that very soon, in the same time you can check this > branch > https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if > you want to play with it locally. > > See you ! > Sebi > > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/e6951300/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/e6951300/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/e6951300/attachment-0003.png From matzew at apache.org Tue Mar 4 15:47:00 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 4 Mar 2014 21:47:00 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: When I am on the "snippets" page, and I want to click back (to the actual variant), I get this URL (smells like JS error): https://newpush-sblanc.rhcloud.com/#/mobileApps/variant/undefined/undefined/undefined (link for the variant in "Applications > Variants > Variant") Clicking the incorrect link makes the actual page go wild On Tue, Mar 4, 2014 at 9:42 PM, Matthias Wessendorf wrote: > I like it! > > for the native iOS code I think some CSS for the background is missing. > > Cheers! > Matthias > > > On Tue, Mar 4, 2014 at 6:09 PM, Sebastien Blanc wrote: > >> Hi, >> >> I've started to work on AGPUSH-550 where >> the idea is to generate Device Registration code Snippets that the user can >> copy/paste into his client application. >> >> The flow is quite simple : he chooses a Variant, then click a link on the >> right that brings you to the Snippets page. >> Since the console knows the type of the selected variant, the >> appropriate snippet is generated ... Yes "generated" , that means it's not >> a static code snippet but it's actually filled with the needed info : UPS >> Server URL, Variant ID, Variant Secret, SenderId (for Android). >> >> For each code snippet, there also the Cordova version for it. So, if you >> choose an Android variant for instance you will have : >> >> [image: Inline image 1] >> >> And as you can see, there is also a link to cordova : >> >> [image: Inline image 2] >> >> This is still work in progress, needs polishing etc ... But once we got >> this, it will be really easy for a new user to get started. All the >> variants type are covered : iOS, Android and SPS >> >> Oh, want to test it live ? Give it a try here : >> https://newpush-sblanc.rhcloud.com/ (admin / 123) >> >> I will probably PR that very soon, in the same time you can check this >> branch >> https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if >> you want to play with it locally. >> >> See you ! >> Sebi >> >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- 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/20140304/d3851435/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/d3851435/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/d3851435/attachment-0003.png From scm.blanc at gmail.com Tue Mar 4 16:19:38 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 4 Mar 2014 22:19:38 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: On Tue, Mar 4, 2014 at 9:42 PM, Matthias Wessendorf wrote: > I like it! > > for the native iOS code I think some CSS for the background is missing. > This should be fixed now in the deployed version (forgot to checkin the latest ios template) , beware of the cache. > > Cheers! > Matthias > > > On Tue, Mar 4, 2014 at 6:09 PM, Sebastien Blanc wrote: > >> Hi, >> >> I've started to work on AGPUSH-550 where >> the idea is to generate Device Registration code Snippets that the user can >> copy/paste into his client application. >> >> The flow is quite simple : he chooses a Variant, then click a link on the >> right that brings you to the Snippets page. >> Since the console knows the type of the selected variant, the >> appropriate snippet is generated ... Yes "generated" , that means it's not >> a static code snippet but it's actually filled with the needed info : UPS >> Server URL, Variant ID, Variant Secret, SenderId (for Android). >> >> For each code snippet, there also the Cordova version for it. So, if you >> choose an Android variant for instance you will have : >> >> [image: Inline image 1] >> >> And as you can see, there is also a link to cordova : >> >> [image: Inline image 2] >> >> This is still work in progress, needs polishing etc ... But once we got >> this, it will be really easy for a new user to get started. All the >> variants type are covered : iOS, Android and SPS >> >> Oh, want to test it live ? Give it a try here : >> https://newpush-sblanc.rhcloud.com/ (admin / 123) >> >> I will probably PR that very soon, in the same time you can check this >> branch >> https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if >> you want to play with it locally. >> >> See you ! >> Sebi >> >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/75d2c5de/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/75d2c5de/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/75d2c5de/attachment-0003.png From scm.blanc at gmail.com Tue Mar 4 16:20:38 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 4 Mar 2014 22:20:38 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: On Tue, Mar 4, 2014 at 9:47 PM, Matthias Wessendorf wrote: > When I am on the "snippets" page, and I want to click back (to the actual > variant), I get this URL (smells like JS error): > > > https://newpush-sblanc.rhcloud.com/#/mobileApps/variant/undefined/undefined/undefined > (link for the variant in "Applications > Variants > Variant") > > Clicking the incorrect link makes the actual page go wild > Yeah I saw that :) , pretty scary. I must be messing something up in the routing. Will take a look tomorrow. > > > On Tue, Mar 4, 2014 at 9:42 PM, Matthias Wessendorf wrote: > >> I like it! >> >> for the native iOS code I think some CSS for the background is missing. >> >> Cheers! >> Matthias >> >> >> On Tue, Mar 4, 2014 at 6:09 PM, Sebastien Blanc wrote: >> >>> Hi, >>> >>> I've started to work on AGPUSH-550 where >>> the idea is to generate Device Registration code Snippets that the user can >>> copy/paste into his client application. >>> >>> The flow is quite simple : he chooses a Variant, then click a link on >>> the right that brings you to the Snippets page. >>> Since the console knows the type of the selected variant, the >>> appropriate snippet is generated ... Yes "generated" , that means it's not >>> a static code snippet but it's actually filled with the needed info : UPS >>> Server URL, Variant ID, Variant Secret, SenderId (for Android). >>> >>> For each code snippet, there also the Cordova version for it. So, if you >>> choose an Android variant for instance you will have : >>> >>> [image: Inline image 1] >>> >>> And as you can see, there is also a link to cordova : >>> >>> [image: Inline image 2] >>> >>> This is still work in progress, needs polishing etc ... But once we got >>> this, it will be really easy for a new user to get started. All the >>> variants type are covered : iOS, Android and SPS >>> >>> Oh, want to test it live ? Give it a try here : >>> https://newpush-sblanc.rhcloud.com/ (admin / 123) >>> >>> I will probably PR that very soon, in the same time you can check this >>> branch >>> https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if >>> you want to play with it locally. >>> >>> See you ! >>> Sebi >>> >>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20140304/7e72ca2f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/7e72ca2f/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140304/7e72ca2f/attachment-0003.png From cvasilak at gmail.com Wed Mar 5 04:39:07 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Wed, 5 Mar 2014 11:39:07 +0200 Subject: [aerogear-dev] Comparing sync in Android vs other platforms In-Reply-To: <53149CEF.5090509@redhat.com> References: <53149CEF.5090509@redhat.com> Message-ID: Hi Summers, thanks for writing this up. Had a dive on ContentProvider and SyncAdapter trying to understand the concepts and how they work together. As you mentioned, ContentProvider helps on CRUD which can be backed up by an SQLStore[1] (and can be extended to REST endpoint[2]) , which in turn provides automatically notification for every interesting client (UI support for ContentProvider) upon store updates. Further helps with caching, since records are served by the local store if network is unavailable. I think this abstraction its very interesting. Same goes with SyncAdapter where the user provides onPerformSync() and the system automatically (or manually) can be scheduled to call it up. It doesn?t provide sync per se, but a hook to user to plug in his algorithm. And works beautifully with ContentProvider. And that?s clever. In iOS, AFAIK these two abstractions do not exist, but I can imagine building them with a combination of Core Data (backed by SQLStore) and an IncrementalStore[3] abstraction that kicks in to fetch from remote REST endpoints and update local store. The system, as in Android provides build-in support for UI components update when the underlying store changes (using an NSFetchedResultsController). For SyncAdapter, a combination of Local Notification, Background Fetch and Remote Notification can be used to provide this functionality. For ContentProvider if you rely on Core Data, I would say somehow ?similar? but need the user to build upon existing techs. For SyncAdapter, I imagine the end-result is calling sync() which again needs to be build upon existing techs. The ?sophistication? of SyncAdapter when calling sync() (which relies on network availability, app usage patterns), I imagine is encompassed on the effective usage of techs mentioned earlier. Short answer, not out of the box as in Android but can be build upon existing iOS technologies. Thanks, Christos [1] https://github.com/bmeike/ProgrammingAndroid2Examples/blob/master/FinchVideo/src/com/oreilly/demo/android/pa/finchvideo/provider/FinchVideoContentProvider.java [2] https://github.com/bmeike/ProgrammingAndroid2Examples/blob/master/FinchFramework/src/com/finchframework/finch/rest/RESTfulContentProvider.java [3] https://developer.apple.com/library/ios/documentation/DataManagement/Conceptual/IncrementalStorePG/Introduction/Introduction.html On Mar 3, 2014, at 5:17 PM, Summers Pittman wrote: > For the DevNexus Android app[1] I used Android native sync APIs[2] + the > sync strawman[3] I put out back in December. It worked surprisingly > well with a few caveats. > > First a background on how Android sync works. > > Android sync is handled by three components: a SyncAdapter, a > ContentProvider, and a Authenticator. > > The Sync Adapter performs as sync and returns a status object. The > SyncAdapter is called from, managed by, etc the Android platform. It > provides an onPerformSync that the developer implements. In the > application the developer sends signals to Android which control > scheduling sync (periodic, immediate, event based etc). Also Android > will put in the "Account" settings page a control for the SyncAdapter. > In this case the SQLSynchronizer I proposed was used to implement this > method. > > The ContentProvider is responsible for CRUD operations on your data, > exposing your data to other apps on the device, and notifying the system > if data changes. This is managed by Android as well. In this case the > CP was backed by a SQLStore. > > Finally the Android Authenticator is responsible for establishing and > maintaining authentication with remote services. If the user is not > signed in, or if fetching an auth token fails, the Authenticator will be > called by Android to provide a Activity which can be used to refresh the > users account. In this case I used two custom AuthenticationModules. > One handled SSO with Google and the other handled keeping the cookie up > to date. Both communicated with the DevNexus server to keep all of the > tokens fresh. > > Overall, Android provides a very VERY slick (but very very complicated) > way of managing sync AND keeping the sync state visible to the user. If > you use Androids APIs then the OS handles things like Authentication > errors, intermittent connectivity, etc while providing configuration for > a variety of sync use cases (UI event based, polling, data listening, etc). > > I tried looking up what options are available in JS land but the closest > I came to was a FFOS blurb about it is a TODO item and isn't a W3C > proposal or anything yet. > > I tried looking at iOS but the docs made my eyes cross. > > So what does the PLATFORM support look like in these environments? > > ---- > [1]https://github.com/secondsun/devnexusAndroid > [2]http://developer.android.com/training/sync-adapters/index.html > [3]https://github.com/secondsun/aerogear-android/tree/sync_strawman/src/org/jboss/aerogear/android/sync > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From scm.blanc at gmail.com Wed Mar 5 05:18:59 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 5 Mar 2014 11:18:59 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: On Tue, Mar 4, 2014 at 10:20 PM, Sebastien Blanc wrote: > > > > On Tue, Mar 4, 2014 at 9:47 PM, Matthias Wessendorf wrote: > >> When I am on the "snippets" page, and I want to click back (to the actual >> variant), I get this URL (smells like JS error): >> >> >> https://newpush-sblanc.rhcloud.com/#/mobileApps/variant/undefined/undefined/undefined >> (link for the variant in "Applications > Variants > Variant") >> >> Clicking the incorrect link makes the actual page go wild >> > Yeah I saw that :) , pretty scary. > I must be messing something up in the routing. Will take a look tomorrow. > Well, that is fixed as well now on the deployed version ! > > >> >> >> On Tue, Mar 4, 2014 at 9:42 PM, Matthias Wessendorf wrote: >> >>> I like it! >>> >>> for the native iOS code I think some CSS for the background is missing. >>> >>> Cheers! >>> Matthias >>> >>> >>> On Tue, Mar 4, 2014 at 6:09 PM, Sebastien Blanc wrote: >>> >>>> Hi, >>>> >>>> I've started to work on AGPUSH-550 where >>>> the idea is to generate Device Registration code Snippets that the user can >>>> copy/paste into his client application. >>>> >>>> The flow is quite simple : he chooses a Variant, then click a link on >>>> the right that brings you to the Snippets page. >>>> Since the console knows the type of the selected variant, the >>>> appropriate snippet is generated ... Yes "generated" , that means it's not >>>> a static code snippet but it's actually filled with the needed info : UPS >>>> Server URL, Variant ID, Variant Secret, SenderId (for Android). >>>> >>>> For each code snippet, there also the Cordova version for it. So, if >>>> you choose an Android variant for instance you will have : >>>> >>>> [image: Inline image 1] >>>> >>>> And as you can see, there is also a link to cordova : >>>> >>>> [image: Inline image 2] >>>> >>>> This is still work in progress, needs polishing etc ... But once we got >>>> this, it will be really easy for a new user to get started. All the >>>> variants type are covered : iOS, Android and SPS >>>> >>>> Oh, want to test it live ? Give it a try here : >>>> https://newpush-sblanc.rhcloud.com/ (admin / 123) >>>> >>>> I will probably PR that very soon, in the same time you can check this >>>> branch >>>> https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if >>>> you want to play with it locally. >>>> >>>> See you ! >>>> Sebi >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/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/20140305/9bb780c2/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/9bb780c2/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/9bb780c2/attachment-0003.png From matzew at apache.org Wed Mar 5 05:40:05 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 5 Mar 2014 11:40:05 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: On Wed, Mar 5, 2014 at 11:18 AM, Sebastien Blanc wrote: > > > > On Tue, Mar 4, 2014 at 10:20 PM, Sebastien Blanc wrote: > >> >> >> >> On Tue, Mar 4, 2014 at 9:47 PM, Matthias Wessendorf wrote: >> >>> When I am on the "snippets" page, and I want to click back (to the >>> actual variant), I get this URL (smells like JS error): >>> >>> >>> https://newpush-sblanc.rhcloud.com/#/mobileApps/variant/undefined/undefined/undefined >>> (link for the variant in "Applications > Variants > Variant") >>> >>> Clicking the incorrect link makes the actual page go wild >>> >> Yeah I saw that :) , pretty scary. >> I must be messing something up in the routing. Will take a look tomorrow. >> > > Well, that is fixed as well now on the deployed version ! > awesome, works great! Ship it l;-) > >> >>> >>> >>> On Tue, Mar 4, 2014 at 9:42 PM, Matthias Wessendorf wrote: >>> >>>> I like it! >>>> >>>> for the native iOS code I think some CSS for the background is missing. >>>> >>>> Cheers! >>>> Matthias >>>> >>>> >>>> On Tue, Mar 4, 2014 at 6:09 PM, Sebastien Blanc wrote: >>>> >>>>> Hi, >>>>> >>>>> I've started to work on AGPUSH-550 where >>>>> the idea is to generate Device Registration code Snippets that the user can >>>>> copy/paste into his client application. >>>>> >>>>> The flow is quite simple : he chooses a Variant, then click a link on >>>>> the right that brings you to the Snippets page. >>>>> Since the console knows the type of the selected variant, the >>>>> appropriate snippet is generated ... Yes "generated" , that means it's not >>>>> a static code snippet but it's actually filled with the needed info : UPS >>>>> Server URL, Variant ID, Variant Secret, SenderId (for Android). >>>>> >>>>> For each code snippet, there also the Cordova version for it. So, if >>>>> you choose an Android variant for instance you will have : >>>>> >>>>> [image: Inline image 1] >>>>> >>>>> And as you can see, there is also a link to cordova : >>>>> >>>>> [image: Inline image 2] >>>>> >>>>> This is still work in progress, needs polishing etc ... But once we >>>>> got this, it will be really easy for a new user to get started. All the >>>>> variants type are covered : iOS, Android and SPS >>>>> >>>>> Oh, want to test it live ? Give it a try here : >>>>> https://newpush-sblanc.rhcloud.com/ (admin / 123) >>>>> >>>>> I will probably PR that very soon, in the same time you can check this >>>>> branch >>>>> https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if >>>>> you want to play with it locally. >>>>> >>>>> See you ! >>>>> Sebi >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/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/20140305/7e91394e/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/7e91394e/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/7e91394e/attachment-0003.png From corinnekrych at gmail.com Wed Mar 5 06:43:55 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 5 Mar 2014 12:43:55 +0100 Subject: [aerogear-dev] Comparing sync in Android vs other platforms In-Reply-To: References: <53149CEF.5090509@redhat.com> Message-ID: On 05 Mar 2014, at 10:39, Christos Vasilakis wrote: > Hi Summers, > > thanks for writing this up. > > Had a dive on ContentProvider and SyncAdapter trying to understand the concepts and how they work together. As you mentioned, ContentProvider helps on CRUD which can be backed up by an SQLStore[1] (and can be extended to REST endpoint[2]) , which in turn provides automatically notification for every interesting client (UI support for ContentProvider) upon store updates. Further helps with caching, since records are served by the local store if network is unavailable. I think this abstraction its very interesting. > > Same goes with SyncAdapter where the user provides onPerformSync() and the system automatically (or manually) can be scheduled to call it up. It doesn?t provide sync per se, but a hook to user to plug in his algorithm. And works beautifully with ContentProvider. And that?s clever. > > In iOS, AFAIK these two abstractions do not exist, but I can imagine building them with a combination of Core Data (backed by SQLStore) and an IncrementalStore[3] abstraction that kicks in to fetch from remote REST endpoints and update local store. The system, as in Android provides build-in support for UI components update when the underlying store changes (using an NSFetchedResultsController). > > For SyncAdapter, a combination of Local Notification, Background Fetch and Remote Notification can be used to provide this functionality. > > For ContentProvider if you rely on Core Data, I would say somehow ?similar? but need the user to build upon existing techs. > For SyncAdapter, I imagine the end-result is calling sync() which again needs to be build upon existing techs. The ?sophistication? of SyncAdapter when calling sync() (which relies on network availability, app usage patterns), I imagine is encompassed on the effective usage of techs mentioned earlier. > > Short answer, not out of the box as in Android but can be build upon existing iOS technologies. I guess Apple has a different strategy than Android when it somes to sync support. As I can see with Chrsitos link, Android provides hook to implement your own sync solution when iCloud/CoreData is a complete out-of-the box solution (Black box lacking flexibility [1]) Interesting alternative solutions TICDS[2] (prior to CoreData) and Ensembles[3] (using iCloud file sync) are worth looking closer at. ++ Corinne [1] http://www.theverge.com/2013/3/26/4148628/why-doesnt-icloud-just-work [2] https://github.com/nothirst/TICoreDataSync [3] https://github.com/drewmccormack/ensembles > > Thanks, > Christos > > > [1] https://github.com/bmeike/ProgrammingAndroid2Examples/blob/master/FinchVideo/src/com/oreilly/demo/android/pa/finchvideo/provider/FinchVideoContentProvider.java > > [2] https://github.com/bmeike/ProgrammingAndroid2Examples/blob/master/FinchFramework/src/com/finchframework/finch/rest/RESTfulContentProvider.java > > [3] https://developer.apple.com/library/ios/documentation/DataManagement/Conceptual/IncrementalStorePG/Introduction/Introduction.html > > On Mar 3, 2014, at 5:17 PM, Summers Pittman wrote: > >> For the DevNexus Android app[1] I used Android native sync APIs[2] + the >> sync strawman[3] I put out back in December. It worked surprisingly >> well with a few caveats. >> >> First a background on how Android sync works. >> >> Android sync is handled by three components: a SyncAdapter, a >> ContentProvider, and a Authenticator. >> >> The Sync Adapter performs as sync and returns a status object. The >> SyncAdapter is called from, managed by, etc the Android platform. It >> provides an onPerformSync that the developer implements. In the >> application the developer sends signals to Android which control >> scheduling sync (periodic, immediate, event based etc). Also Android >> will put in the "Account" settings page a control for the SyncAdapter. >> In this case the SQLSynchronizer I proposed was used to implement this >> method. >> >> The ContentProvider is responsible for CRUD operations on your data, >> exposing your data to other apps on the device, and notifying the system >> if data changes. This is managed by Android as well. In this case the >> CP was backed by a SQLStore. >> >> Finally the Android Authenticator is responsible for establishing and >> maintaining authentication with remote services. If the user is not >> signed in, or if fetching an auth token fails, the Authenticator will be >> called by Android to provide a Activity which can be used to refresh the >> users account. In this case I used two custom AuthenticationModules. >> One handled SSO with Google and the other handled keeping the cookie up >> to date. Both communicated with the DevNexus server to keep all of the >> tokens fresh. >> >> Overall, Android provides a very VERY slick (but very very complicated) >> way of managing sync AND keeping the sync state visible to the user. If >> you use Androids APIs then the OS handles things like Authentication >> errors, intermittent connectivity, etc while providing configuration for >> a variety of sync use cases (UI event based, polling, data listening, etc). >> >> I tried looking up what options are available in JS land but the closest >> I came to was a FFOS blurb about it is a TODO item and isn't a W3C >> proposal or anything yet. >> >> I tried looking at iOS but the docs made my eyes cross. >> >> So what does the PLATFORM support look like in these environments? >> >> ---- >> [1]https://github.com/secondsun/devnexusAndroid >> [2]http://developer.android.com/training/sync-adapters/index.html >> [3]https://github.com/secondsun/aerogear-android/tree/sync_strawman/src/org/jboss/aerogear/android/sync >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 supittma at redhat.com Wed Mar 5 09:15:27 2014 From: supittma at redhat.com (Summers Pittman) Date: Wed, 05 Mar 2014 09:15:27 -0500 Subject: [aerogear-dev] Modularizing the Android Library Message-ID: <5317317F.1010209@redhat.com> Earlier in development (pre passos) making the Android SDK into modules was not a concern (in fact it was an anti-concern). Now, however, we have a much more complete project and it is time to have that discussion. Right now we have two BIG questions: 1) Do we want to break out interfaces and implementation? If we do this then we could reuse a lot of code to make a aerogear-java as well. 2) How granular do we want our modules? IE If we break out push into aerogear-android-push would that include GCM, SimplePush, MQTT, etc in one package or would it look like aerogear-android-push-core, aerogear-android-push-mqtt etc. Thoughts? -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From lholmqui at redhat.com Wed Mar 5 09:18:37 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Wed, 5 Mar 2014 09:18:37 -0500 Subject: [aerogear-dev] Comparing sync in Android vs other platforms In-Reply-To: <53149CEF.5090509@redhat.com> References: <53149CEF.5090509@redhat.com> Message-ID: For JS, there isn't really anything except for maybe leveraging indexedDB upgrades, but IndexedDB isn't supported everywhere. Once Object.observe comes in, then we are closer to comparing objects super easy JS is very much DIY at this point On Mar 3, 2014, at 10:17 AM, Summers Pittman wrote: > For the DevNexus Android app[1] I used Android native sync APIs[2] + the > sync strawman[3] I put out back in December. It worked surprisingly > well with a few caveats. > > First a background on how Android sync works. > > Android sync is handled by three components: a SyncAdapter, a > ContentProvider, and a Authenticator. > > The Sync Adapter performs as sync and returns a status object. The > SyncAdapter is called from, managed by, etc the Android platform. It > provides an onPerformSync that the developer implements. In the > application the developer sends signals to Android which control > scheduling sync (periodic, immediate, event based etc). Also Android > will put in the "Account" settings page a control for the SyncAdapter. > In this case the SQLSynchronizer I proposed was used to implement this > method. > > The ContentProvider is responsible for CRUD operations on your data, > exposing your data to other apps on the device, and notifying the system > if data changes. This is managed by Android as well. In this case the > CP was backed by a SQLStore. > > Finally the Android Authenticator is responsible for establishing and > maintaining authentication with remote services. If the user is not > signed in, or if fetching an auth token fails, the Authenticator will be > called by Android to provide a Activity which can be used to refresh the > users account. In this case I used two custom AuthenticationModules. > One handled SSO with Google and the other handled keeping the cookie up > to date. Both communicated with the DevNexus server to keep all of the > tokens fresh. > > Overall, Android provides a very VERY slick (but very very complicated) > way of managing sync AND keeping the sync state visible to the user. If > you use Androids APIs then the OS handles things like Authentication > errors, intermittent connectivity, etc while providing configuration for > a variety of sync use cases (UI event based, polling, data listening, etc). > > I tried looking up what options are available in JS land but the closest > I came to was a FFOS blurb about it is a TODO item and isn't a W3C > proposal or anything yet. > > I tried looking at iOS but the docs made my eyes cross. > > So what does the PLATFORM support look like in these environments? > > ---- > [1]https://github.com/secondsun/devnexusAndroid > [2]http://developer.android.com/training/sync-adapters/index.html > [3]https://github.com/secondsun/aerogear-android/tree/sync_strawman/src/org/jboss/aerogear/android/sync > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From corinnekrych at gmail.com Wed Mar 5 09:27:55 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 5 Mar 2014 15:27:55 +0100 Subject: [aerogear-dev] Comparing sync in Android vs other platforms In-Reply-To: References: <53149CEF.5090509@redhat.com> Message-ID: Hi All, Json patch with HTTP patch method [1] are interesting to look at when it comes to send diff/patch. ++ Corinne [1] https://tools.ietf.org/html/rfc6902 On 05 Mar 2014, at 15:18, Lucas Holmquist wrote: > For JS, there isn't really anything except for maybe leveraging indexedDB upgrades, but IndexedDB isn't supported everywhere. > > Once Object.observe comes in, then we are closer to comparing objects super easy > > JS is very much DIY at this point > > > On Mar 3, 2014, at 10:17 AM, Summers Pittman wrote: > >> For the DevNexus Android app[1] I used Android native sync APIs[2] + the >> sync strawman[3] I put out back in December. It worked surprisingly >> well with a few caveats. >> >> First a background on how Android sync works. >> >> Android sync is handled by three components: a SyncAdapter, a >> ContentProvider, and a Authenticator. >> >> The Sync Adapter performs as sync and returns a status object. The >> SyncAdapter is called from, managed by, etc the Android platform. It >> provides an onPerformSync that the developer implements. In the >> application the developer sends signals to Android which control >> scheduling sync (periodic, immediate, event based etc). Also Android >> will put in the "Account" settings page a control for the SyncAdapter. >> In this case the SQLSynchronizer I proposed was used to implement this >> method. >> >> The ContentProvider is responsible for CRUD operations on your data, >> exposing your data to other apps on the device, and notifying the system >> if data changes. This is managed by Android as well. In this case the >> CP was backed by a SQLStore. >> >> Finally the Android Authenticator is responsible for establishing and >> maintaining authentication with remote services. If the user is not >> signed in, or if fetching an auth token fails, the Authenticator will be >> called by Android to provide a Activity which can be used to refresh the >> users account. In this case I used two custom AuthenticationModules. >> One handled SSO with Google and the other handled keeping the cookie up >> to date. Both communicated with the DevNexus server to keep all of the >> tokens fresh. >> >> Overall, Android provides a very VERY slick (but very very complicated) >> way of managing sync AND keeping the sync state visible to the user. If >> you use Androids APIs then the OS handles things like Authentication >> errors, intermittent connectivity, etc while providing configuration for >> a variety of sync use cases (UI event based, polling, data listening, etc). >> >> I tried looking up what options are available in JS land but the closest >> I came to was a FFOS blurb about it is a TODO item and isn't a W3C >> proposal or anything yet. >> >> I tried looking at iOS but the docs made my eyes cross. >> >> So what does the PLATFORM support look like in these environments? >> >> ---- >> [1]https://github.com/secondsun/devnexusAndroid >> [2]http://developer.android.com/training/sync-adapters/index.html >> [3]https://github.com/secondsun/aerogear-android/tree/sync_strawman/src/org/jboss/aerogear/android/sync >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 Mar 5 09:33:49 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 5 Mar 2014 15:33:49 +0100 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: <5317317F.1010209@redhat.com> References: <5317317F.1010209@redhat.com> Message-ID: On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman wrote: > Earlier in development (pre passos) making the Android SDK into modules > was not a concern (in fact it was an anti-concern). > > Now, however, we have a much more complete project and it is time to > have that discussion. > > Right now we have two BIG questions: > > 1) Do we want to break out interfaces and implementation? > > If we do this then we could reuse a lot of code to make a aerogear-java > as well. > > 2) How granular do we want our modules? > > IE If we break out push into aerogear-android-push would that include > GCM, SimplePush, MQTT, etc in one package or would it look like > android-gcm android-simplepush android-mqtt > aerogear-android-push-core, aerogear-android-push-mqtt etc. > > Thoughts? > > -- > 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/20140305/debd65b4/attachment.html From lholmqui at redhat.com Wed Mar 5 09:41:04 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Wed, 5 Mar 2014 09:41:04 -0500 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: References: <5317317F.1010209@redhat.com> Message-ID: <9E278109-FC07-45E5-85C3-CA49C87B7F23@redhat.com> On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf wrote: > > > > On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman wrote: > Earlier in development (pre passos) making the Android SDK into modules > was not a concern (in fact it was an anti-concern). > > Now, however, we have a much more complete project and it is time to > have that discussion. > > Right now we have two BIG questions: > > 1) Do we want to break out interfaces and implementation? > > If we do this then we could reuse a lot of code to make a aerogear-java > as well. > > 2) How granular do we want our modules? > > IE If we break out push into aerogear-android-push would that include > GCM, SimplePush, MQTT, etc in one package or would it look like > > android-gcm > android-simplepush > android-mqtt +1 to those names, and i'm sure you mean aerogear-* :) > > > > > aerogear-android-push-core, aerogear-android-push-mqtt etc. > > Thoughts? > > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/5164fc9c/attachment-0001.html From matzew at apache.org Wed Mar 5 09:42:55 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 5 Mar 2014 15:42:55 +0100 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: <9E278109-FC07-45E5-85C3-CA49C87B7F23@redhat.com> References: <5317317F.1010209@redhat.com> <9E278109-FC07-45E5-85C3-CA49C87B7F23@redhat.com> Message-ID: On Wed, Mar 5, 2014 at 3:41 PM, Lucas Holmquist wrote: > > On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf wrote: > > > > > On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman wrote: > >> Earlier in development (pre passos) making the Android SDK into modules >> was not a concern (in fact it was an anti-concern). >> >> Now, however, we have a much more complete project and it is time to >> have that discussion. >> >> Right now we have two BIG questions: >> >> 1) Do we want to break out interfaces and implementation? >> >> If we do this then we could reuse a lot of code to make a aerogear-java >> as well. >> >> 2) How granular do we want our modules? >> >> IE If we break out push into aerogear-android-push would that include >> GCM, SimplePush, MQTT, etc in one package or would it look like >> > > android-gcm > android-simplepush > android-mqtt > > > +1 to those names, and i'm sure you mean aerogear-* :) > yep ;-) > > > > > > >> aerogear-android-push-core, aerogear-android-push-mqtt etc. >> >> Thoughts? >> >> -- >> 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 > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140305/05fa26a1/attachment.html From daniel at passos.me Wed Mar 5 09:55:32 2014 From: daniel at passos.me (Daniel Passos) Date: Wed, 5 Mar 2014 11:55:32 -0300 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: Hi Sebi, I not sure if we really need this, because we already have an example very close of it on ag.org, btw on Android snippet you are using MainActity, but your class is an Application and missed "Category" Gist fixed => https://gist.github.com/danielpassos/f7e6e4b723d71c4c56e9 On Tue, Mar 4, 2014 at 2:09 PM, Sebastien Blanc wrote: > Hi, > > I've started to work on AGPUSH-550 where > the idea is to generate Device Registration code Snippets that the user can > copy/paste into his client application. > > The flow is quite simple : he chooses a Variant, then click a link on the > right that brings you to the Snippets page. > Since the console knows the type of the selected variant, the appropriate > snippet is generated ... Yes "generated" , that means it's not a static > code snippet but it's actually filled with the needed info : UPS Server > URL, Variant ID, Variant Secret, SenderId (for Android). > > For each code snippet, there also the Cordova version for it. So, if you > choose an Android variant for instance you will have : > > [image: Inline image 1] > > And as you can see, there is also a link to cordova : > > [image: Inline image 2] > > This is still work in progress, needs polishing etc ... But once we got > this, it will be really easy for a new user to get started. All the > variants type are covered : iOS, Android and SPS > > Oh, want to test it live ? Give it a try here : > https://newpush-sblanc.rhcloud.com/ (admin / 123) > > I will probably PR that very soon, in the same time you can check this > branch > https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if > you want to play with it locally. > > See you ! > 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/20140305/739d5612/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/739d5612/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/739d5612/attachment-0003.png From matzew at apache.org Wed Mar 5 10:04:25 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 5 Mar 2014 16:04:25 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: On Wed, Mar 5, 2014 at 3:55 PM, Daniel Passos wrote: > Hi Sebi, > > I not sure if we really need this, > having example code snippets in the UI is a nice add-on; especially since it is integrated in the Admin-UI. Pointing to website/doc/gist works too, but I feel that the closer the integration is, the better the usage. For iOS and Cordova the bits were completely working, with copy/paste. So it was very simple to get things going. I think that's the main idea behind this -M > because we already have an example very close of it on ag.org, btw on > Android snippet you are using MainActity, but your class is an Application > and missed "Category" Gist fixed => > https://gist.github.com/danielpassos/f7e6e4b723d71c4c56e9 > > > On Tue, Mar 4, 2014 at 2:09 PM, Sebastien Blanc wrote: > >> Hi, >> >> I've started to work on AGPUSH-550 where >> the idea is to generate Device Registration code Snippets that the user can >> copy/paste into his client application. >> >> The flow is quite simple : he chooses a Variant, then click a link on the >> right that brings you to the Snippets page. >> Since the console knows the type of the selected variant, the >> appropriate snippet is generated ... Yes "generated" , that means it's not >> a static code snippet but it's actually filled with the needed info : UPS >> Server URL, Variant ID, Variant Secret, SenderId (for Android). >> >> For each code snippet, there also the Cordova version for it. So, if you >> choose an Android variant for instance you will have : >> >> [image: Inline image 1] >> >> And as you can see, there is also a link to cordova : >> >> [image: Inline image 2] >> >> This is still work in progress, needs polishing etc ... But once we got >> this, it will be really easy for a new user to get started. All the >> variants type are covered : iOS, Android and SPS >> >> Oh, want to test it live ? Give it a try here : >> https://newpush-sblanc.rhcloud.com/ (admin / 123) >> >> I will probably PR that very soon, in the same time you can check this >> branch >> https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if >> you want to play with it locally. >> >> See you ! >> Sebi >> >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140305/74e6d684/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/74e6d684/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/74e6d684/attachment-0003.png From scm.blanc at gmail.com Wed Mar 5 10:11:39 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 5 Mar 2014 16:11:39 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: On Wed, Mar 5, 2014 at 3:55 PM, Daniel Passos wrote: > Hi Sebi, > > I not sure if we really need this, because we already have an example very > close of it on ag.org, > If think it can not hurt to have these snippets integrated in the UPS Console pre-filled with the "in context" values and in both time having our classic documentation. What I can do is add a link to our doc under the snippet. > btw on Android snippet you are using MainActity, but your class is an > Application and missed "Category" Gist fixed => > https://gist.github.com/danielpassos/f7e6e4b723d71c4c56e9 > Thx for the MainActivity, (bad copy paste ;) ) and I did not add Category and alias since they are optional , I just want the mandatory data for the snippets > > > On Tue, Mar 4, 2014 at 2:09 PM, Sebastien Blanc wrote: > >> Hi, >> >> I've started to work on AGPUSH-550 where >> the idea is to generate Device Registration code Snippets that the user can >> copy/paste into his client application. >> >> The flow is quite simple : he chooses a Variant, then click a link on the >> right that brings you to the Snippets page. >> Since the console knows the type of the selected variant, the >> appropriate snippet is generated ... Yes "generated" , that means it's not >> a static code snippet but it's actually filled with the needed info : UPS >> Server URL, Variant ID, Variant Secret, SenderId (for Android). >> >> For each code snippet, there also the Cordova version for it. So, if you >> choose an Android variant for instance you will have : >> >> [image: Inline image 1] >> >> And as you can see, there is also a link to cordova : >> >> [image: Inline image 2] >> >> This is still work in progress, needs polishing etc ... But once we got >> this, it will be really easy for a new user to get started. All the >> variants type are covered : iOS, Android and SPS >> >> Oh, want to test it live ? Give it a try here : >> https://newpush-sblanc.rhcloud.com/ (admin / 123) >> >> I will probably PR that very soon, in the same time you can check this >> branch >> https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 if >> you want to play with it locally. >> >> See you ! >> Sebi >> >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140305/3dfc1394/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: android.png Type: image/png Size: 91550 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/3dfc1394/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: cordova.png Type: image/png Size: 69117 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/3dfc1394/attachment-0003.png From daniel at passos.me Wed Mar 5 10:29:36 2014 From: daniel at passos.me (Daniel Passos) Date: Wed, 5 Mar 2014 12:29:36 -0300 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: References: <5317317F.1010209@redhat.com> <9E278109-FC07-45E5-85C3-CA49C87B7F23@redhat.com> Message-ID: I'd like add push in lib name aerogear-android-push (for core) aerogear-android-push-gcm aerogear-android-push-mqtt -- Passos On Wed, Mar 5, 2014 at 11:42 AM, Matthias Wessendorf wrote: > > > > On Wed, Mar 5, 2014 at 3:41 PM, Lucas Holmquist wrote: > >> >> On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf >> wrote: >> >> >> >> >> On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman wrote: >> >>> Earlier in development (pre passos) making the Android SDK into modules >>> was not a concern (in fact it was an anti-concern). >>> >>> Now, however, we have a much more complete project and it is time to >>> have that discussion. >>> >>> Right now we have two BIG questions: >>> >>> 1) Do we want to break out interfaces and implementation? >>> >>> If we do this then we could reuse a lot of code to make a aerogear-java >>> as well. >>> >>> 2) How granular do we want our modules? >>> >>> IE If we break out push into aerogear-android-push would that include >>> GCM, SimplePush, MQTT, etc in one package or would it look like >>> >> >> android-gcm >> android-simplepush >> android-mqtt >> >> >> +1 to those names, and i'm sure you mean aerogear-* :) >> > > yep ;-) > > >> >> >> >> >> >> >>> aerogear-android-push-core, aerogear-android-push-mqtt etc. >>> >>> Thoughts? >>> >>> -- >>> 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 >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140305/1083e26a/attachment.html From matzew at apache.org Wed Mar 5 10:32:49 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 5 Mar 2014 16:32:49 +0100 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: References: <5317317F.1010209@redhat.com> <9E278109-FC07-45E5-85C3-CA49C87B7F23@redhat.com> Message-ID: On Wed, Mar 5, 2014 at 4:29 PM, Daniel Passos wrote: > I'd like add push in lib name > > aerogear-android-push (for core) > aerogear-android-push-gcm > aerogear-android-push-mqtt > I still think that mqtt is more messaging, instead of push :-) > > > -- Passos > > > > On Wed, Mar 5, 2014 at 11:42 AM, Matthias Wessendorf wrote: > >> >> >> >> On Wed, Mar 5, 2014 at 3:41 PM, Lucas Holmquist wrote: >> >>> >>> On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf >>> wrote: >>> >>> >>> >>> >>> On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman wrote: >>> >>>> Earlier in development (pre passos) making the Android SDK into modules >>>> was not a concern (in fact it was an anti-concern). >>>> >>>> Now, however, we have a much more complete project and it is time to >>>> have that discussion. >>>> >>>> Right now we have two BIG questions: >>>> >>>> 1) Do we want to break out interfaces and implementation? >>>> >>>> If we do this then we could reuse a lot of code to make a aerogear-java >>>> as well. >>>> >>>> 2) How granular do we want our modules? >>>> >>>> IE If we break out push into aerogear-android-push would that include >>>> GCM, SimplePush, MQTT, etc in one package or would it look like >>>> >>> >>> android-gcm >>> android-simplepush >>> android-mqtt >>> >>> >>> +1 to those names, and i'm sure you mean aerogear-* :) >>> >> >> yep ;-) >> >> >>> >>> >>> >>> >>> >>> >>>> aerogear-android-push-core, aerogear-android-push-mqtt etc. >>>> >>>> Thoughts? >>>> >>>> -- >>>> 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 >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140305/7b47f153/attachment.html From supittma at redhat.com Wed Mar 5 10:35:35 2014 From: supittma at redhat.com (Summers Pittman) Date: Wed, 05 Mar 2014 10:35:35 -0500 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: References: <5317317F.1010209@redhat.com> <9E278109-FC07-45E5-85C3-CA49C87B7F23@redhat.com> Message-ID: <53174447.2050407@redhat.com> On Wed 05 Mar 2014 10:32:49 AM EST, Matthias Wessendorf wrote: > > > > On Wed, Mar 5, 2014 at 4:29 PM, Daniel Passos > wrote: > > I'd like add push in lib name > > aerogear-android-push (for core) > aerogear-android-push-gcm > aerogear-android-push-mqtt > > > I still think that mqtt is more messaging, instead of push :-) Well right now it would be "push" because we don't support bidirectional communication. MQTT is just the transport. We SHOULD investigate messaging soon since GCM supports it. > > > > -- Passos > > > > On Wed, Mar 5, 2014 at 11:42 AM, Matthias Wessendorf > > wrote: > > > > > On Wed, Mar 5, 2014 at 3:41 PM, Lucas Holmquist > > wrote: > > > On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf > > wrote: > >> >> >> >> On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman >> > wrote: >> >> Earlier in development (pre passos) making the >> Android SDK into modules >> was not a concern (in fact it was an anti-concern). >> >> Now, however, we have a much more complete project >> and it is time to >> have that discussion. >> >> Right now we have two BIG questions: >> >> 1) Do we want to break out interfaces and implementation? >> >> If we do this then we could reuse a lot of code to >> make a aerogear-java >> as well. >> >> 2) How granular do we want our modules? >> >> IE If we break out push into aerogear-android-push >> would that include >> GCM, SimplePush, MQTT, etc in one package or would it >> look like >> >> >> android-gcm >> android-simplepush >> android-mqtt > > +1 to those names, and i'm sure you mean aerogear-* :) > > > yep ;-) > > >> >> >> >> aerogear-android-push-core, >> aerogear-android-push-mqtt etc. >> >> Thoughts? >> >> -- >> 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > > https://lists.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. From bam at tretau.net Wed Mar 5 10:43:09 2014 From: bam at tretau.net (ttretau) Date: Wed, 5 Mar 2014 07:43:09 -0800 (PST) Subject: [aerogear-dev] Android Push: 3G /WiFi In-Reply-To: References: <1393511406719-6569.post@n5.nabble.com> <20140227200942.Horde.hCrH6HoeByhh7Uq1SNrdew1@webmail.df.eu> Message-ID: <20140305161750.Horde.vj1sxDSye5MCjmQsHnxWPw6@webmail.df.eu> Okay, to sum up this problem: The reason was firewall / router configuration and GCM. In other environments aerogear performs well and messages reach the client.. Kind regards, Torben Quoting "Matthias Wessendorf [via aerogear-dev]" : > On Thu, Feb 27, 2014 at 8:09 PM, Torben wrote: > >> >> Hello Matthias, >> Hello Erik, >> >> thanks for your fast reply! >> >> > That's weird :) Your device is listed on the unifiedpush admin console, >> > right ? >> > I guess, otherwise you would also not receive messages, when on 3G :) >> > >> > Kinda odd, but not sure... You phone should be able to receive messages >> on >> > local wifi as well. >> > All it needs: a working internet connection (internally Google's GCM has >> a >> > persistent connection to your phone) >> >> Yes, all devices are listed in the admin console. >> >> It's really wired, I have read about difficulties with some routers >> cutting network connections on the GCM Google group - and I noticed a >> difference between office and home network connection right now. >> I will debug more into this on monday when I am back in the office.. >> > > damn routers/proxies :) > > >> >> > >> > The exception below is no harm at all - it's an open issue at the APNs >> lib >> > we use internally: >> > >> >> Thanks for the info! So I don't have to go into this.. >> >> Great work, excited to get more into aerogear and the openshift cartridge! >> This is a nice alternative to other proprietary Push Service Providers.. >> > > Thanks for the kind words! We are happy to answer any question around > AeroGear, not just push ;-) > > BTW. I'd recommend updating/patching your existing OpenShift installation: > http://lists.jboss.org/pipermail/aerogear-dev/2014-February/006495.html > > -Matthias > > >> >> Kind regards, >> >> Torben >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 > > > > _______________________________________________ > If you reply to this email, your message will be added to the > discussion below: > http://aerogear-dev.1069024.n5.nabble.com/Android-Push-3G-WiFi-tp6569p6587.html > > To unsubscribe from Android Push: 3G /WiFi, visit > http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=6569&code=YmFtQHRyZXRhdS5uZXR8NjU2OXwtNjYxNjI4NjE0 -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Push-3G-WiFi-tp6569p6645.html Sent from the aerogear-dev mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140305/96abba30/attachment.html From supittma at redhat.com Wed Mar 5 11:01:04 2014 From: supittma at redhat.com (Summers Pittman) Date: Wed, 05 Mar 2014 11:01:04 -0500 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: References: <5317317F.1010209@redhat.com> <9E278109-FC07-45E5-85C3-CA49C87B7F23@redhat.com> <53174447.2050407@redhat.com> Message-ID: <53174A40.6030702@redhat.com> On Wed 05 Mar 2014 10:58:45 AM EST, Matthias Wessendorf wrote: > > > > On Wed, Mar 5, 2014 at 4:35 PM, Summers Pittman > wrote: > > On Wed 05 Mar 2014 10:32:49 AM EST, Matthias Wessendorf wrote: > > > > > On Wed, Mar 5, 2014 at 4:29 PM, Daniel Passos > > >> wrote: > > I'd like add push in lib name > > aerogear-android-push (for core) > aerogear-android-push-gcm > aerogear-android-push-mqtt > > > I still think that mqtt is more messaging, instead of push :-) > > Well right now it would be "push" because we don't support > bidirectional communication. MQTT is just the transport. > > We SHOULD investigate messaging soon since GCM supports it. > > > and that's different from push (think APNs / SimplePush), which is > what we support on the UnifiedPush Server. > Right. mqtt and friends were just examples of things we had talked about. However messaging for the project may be something we look at one day. > > doing messaging, via GCM, is fine but something different. There the > underlying technology (e.g. MQTT vs. GCM) is really just a transport, > like: > > -messaging-gcm > -messaging-mqtt > -messaging-stomp > > > -M > > > > > > -- Passos > > > > On Wed, Mar 5, 2014 at 11:42 AM, Matthias Wessendorf > > >> wrote: > > > > > On Wed, Mar 5, 2014 at 3:41 PM, Lucas Holmquist > > >> wrote: > > > On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf > > >> wrote: > > > > > On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman > >> wrote: > > Earlier in development (pre passos) making the > Android SDK into modules > was not a concern (in fact it was an > anti-concern). > > Now, however, we have a much more complete > project > and it is time to > have that discussion. > > Right now we have two BIG questions: > > 1) Do we want to break out interfaces and > implementation? > > If we do this then we could reuse a lot of > code to > make a aerogear-java > as well. > > 2) How granular do we want our modules? > > IE If we break out push into > aerogear-android-push > would that include > GCM, SimplePush, MQTT, etc in one package > or would it > look like > > > android-gcm > android-simplepush > android-mqtt > > > +1 to those names, and i'm sure you mean > aerogear-* :) > > > yep ;-) > > > > > > aerogear-android-push-core, > aerogear-android-push-mqtt etc. > > Thoughts? > > -- > 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 > > > > > _________________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > > > > https://lists.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. > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From matzew at apache.org Wed Mar 5 11:27:59 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 5 Mar 2014 17:27:59 +0100 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: <53174A40.6030702@redhat.com> References: <5317317F.1010209@redhat.com> <9E278109-FC07-45E5-85C3-CA49C87B7F23@redhat.com> <53174447.2050407@redhat.com> <53174A40.6030702@redhat.com> Message-ID: On Wed, Mar 5, 2014 at 5:01 PM, Summers Pittman wrote: > On Wed 05 Mar 2014 10:58:45 AM EST, Matthias Wessendorf wrote: > >> >> >> >> On Wed, Mar 5, 2014 at 4:35 PM, Summers Pittman > > wrote: >> >> On Wed 05 Mar 2014 10:32:49 AM EST, Matthias Wessendorf wrote: >> >> >> >> >> On Wed, Mar 5, 2014 at 4:29 PM, Daniel Passos >> >> >> wrote: >> >> I'd like add push in lib name >> >> aerogear-android-push (for core) >> aerogear-android-push-gcm >> aerogear-android-push-mqtt >> >> >> I still think that mqtt is more messaging, instead of push :-) >> >> Well right now it would be "push" because we don't support >> bidirectional communication. MQTT is just the transport. >> >> We SHOULD investigate messaging soon since GCM supports it. >> >> >> and that's different from push (think APNs / SimplePush), which is >> what we support on the UnifiedPush Server. >> >> > Right. mqtt and friends were just examples of things we had talked about. > > However messaging for the project may be something we look at one day. > agreed > > >> doing messaging, via GCM, is fine but something different. There the >> underlying technology (e.g. MQTT vs. GCM) is really just a transport, >> like: >> >> -messaging-gcm >> -messaging-mqtt >> -messaging-stomp >> >> >> -M >> >> >> >> >> >> -- Passos >> >> >> >> On Wed, Mar 5, 2014 at 11:42 AM, Matthias Wessendorf >> >> >> wrote: >> >> >> >> >> On Wed, Mar 5, 2014 at 3:41 PM, Lucas Holmquist >> >> >> wrote: >> >> >> On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf >> >> >> wrote: >> >> >> >> >> On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman >> > > >> >> wrote: >> >> Earlier in development (pre passos) making the >> Android SDK into modules >> was not a concern (in fact it was an >> anti-concern). >> >> Now, however, we have a much more complete >> project >> and it is time to >> have that discussion. >> >> Right now we have two BIG questions: >> >> 1) Do we want to break out interfaces and >> implementation? >> >> If we do this then we could reuse a lot of >> code to >> make a aerogear-java >> as well. >> >> 2) How granular do we want our modules? >> >> IE If we break out push into >> aerogear-android-push >> would that include >> GCM, SimplePush, MQTT, etc in one package >> or would it >> look like >> >> >> android-gcm >> android-simplepush >> android-mqtt >> >> >> +1 to those names, and i'm sure you mean >> aerogear-* :) >> >> >> yep ;-) >> >> >> >> >> >> aerogear-android-push-core, >> aerogear-android-push-mqtt etc. >> >> Thoughts? >> >> -- >> 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 >> >> >> >> >> _________________________________________________ >> >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org > > >> > > >> >> https://lists.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. >> >> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > 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/20140305/c0c011c3/attachment-0001.html From tech4j at gmail.com Wed Mar 5 15:34:04 2014 From: tech4j at gmail.com (Jay Balunas) Date: Wed, 5 Mar 2014 15:34:04 -0500 Subject: [aerogear-dev] Let's change the AeroGear Twitter account handle In-Reply-To: References: <52EA3687.2050601@redhat.com> <52EA39C6.8020607@redhat.com> <52EF9D46.6000306@redhat.com> <953401D5-1AA2-44BB-8240-859183299450@redhat.com> <79297C6E-D46C-468B-97E3-F3F8C3396F76@redhat.com> <20140220210758.GW51006@rohan.local> Message-ID: On Feb 21, 2014, at 12:59 AM, Matthias Wessendorf wrote: > > > > On Thu, Feb 20, 2014 at 11:17 PM, Bruno Oliveira wrote: > I still can't see what the real value added on it. Everyone knows that there's a team behind it, so I can't see why "_team", also do we plan to create handles for "AeroGearPush", "AeroGearSecurity"...if yes, > > not sure on all these twitter handles. I'd vote -1 on all these accounts +1 on the -1 for additional handles. > > > that makes sense. And "_project", well we know, > > _project or _team - I think both is fine. I never really thought too much about it (team vs. project). I would go with _team as it is shorter, although #aerogear_org I also like and is 1 character less than team. We'll need to take a vote here, or come to some conclusion - I think it can be debated forever ;-) > > > it's a project, the "s" on @aerogears always gave to me the sense of a bunch of people behind this to make it happen. > > I think the "real problem" is folks think "AeroGears" is the name of the project > > Wednesday I gave an AeroGear presentation. Due to the twitter handle of @AeroGears, two of those that asked questions, actually called the project AeroGears :)))) > And that's what I have noticed before, which is, I think, the reason why Hylke brought it up. > > Unfortunately @AeroGear is taken, but I do think that @AeroGears is misleading - in terms of the name. > > However, your "@aerogears always gave to me the sense of a bunch of people behind this to make it happen." is a good thought! Which is believe leads towards _team, right? > > Again I never really interpreted too much into the meaning of the twitter handle, besides the fact that folks do not really get our name. > > > Greetings, > Matthias > > > > > > > > > On Thu, Feb 20, 2014 at 6:54 PM, Matthias Wessendorf wrote: > Actually, @aerogear_project makes sense (see @netty_project) > > > On Thu, Feb 20, 2014 at 10:35 PM, Matthias Wessendorf wrote: > @__aerogear or @_aerogear ? > > > > > On Thu, Feb 20, 2014 at 10:07 PM, Douglas Campos wrote: > **If** we're really forced to change, I'd go with @aerogear_project > > -- > 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 > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > > -- > "The measure of a man is what he does with power" - Plato > - > @abstractj > - > Volenti Nihil Difficile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20140305/d2e990e7/attachment.html From jbalunas at redhat.com Wed Mar 5 15:53:16 2014 From: jbalunas at redhat.com (Jay Balunas) Date: Wed, 5 Mar 2014 15:53:16 -0500 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: References: <5317317F.1010209@redhat.com> <9E278109-FC07-45E5-85C3-CA49C87B7F23@redhat.com> <53174447.2050407@redhat.com> <53174A40.6030702@redhat.com> Message-ID: <89AC2AF7-0A37-428B-B1ED-A5E3F7D79B44@redhat.com> On Mar 5, 2014, at 11:27 AM, Matthias Wessendorf wrote: > > > > On Wed, Mar 5, 2014 at 5:01 PM, Summers Pittman wrote: > On Wed 05 Mar 2014 10:58:45 AM EST, Matthias Wessendorf wrote: > > > > On Wed, Mar 5, 2014 at 4:35 PM, Summers Pittman > wrote: > > On Wed 05 Mar 2014 10:32:49 AM EST, Matthias Wessendorf wrote: > > > > > On Wed, Mar 5, 2014 at 4:29 PM, Daniel Passos > > >> wrote: > > I'd like add push in lib name > > aerogear-android-push (for core) > aerogear-android-push-gcm > aerogear-android-push-mqtt > > > I still think that mqtt is more messaging, instead of push :-) > > Well right now it would be "push" because we don't support > bidirectional communication. MQTT is just the transport. > > We SHOULD investigate messaging soon since GCM supports it. > > > and that's different from push (think APNs / SimplePush), which is > what we support on the UnifiedPush Server. > > > Right. mqtt and friends were just examples of things we had talked about. > > However messaging for the project may be something we look at one day. > > > agreed +1 and I like the names given as well :-) > > > > doing messaging, via GCM, is fine but something different. There the > underlying technology (e.g. MQTT vs. GCM) is really just a transport, > like: > > -messaging-gcm > -messaging-mqtt > -messaging-stomp > > > -M > > > > > > -- Passos > > > > On Wed, Mar 5, 2014 at 11:42 AM, Matthias Wessendorf > > >> wrote: > > > > > On Wed, Mar 5, 2014 at 3:41 PM, Lucas Holmquist > > >> wrote: > > > On Mar 5, 2014, at 9:33 AM, Matthias Wessendorf > > >> wrote: > > > > > On Wed, Mar 5, 2014 at 3:15 PM, Summers Pittman > > >> wrote: > > Earlier in development (pre passos) making the > Android SDK into modules > was not a concern (in fact it was an > anti-concern). > > Now, however, we have a much more complete > project > and it is time to > have that discussion. > > Right now we have two BIG questions: > > 1) Do we want to break out interfaces and > implementation? > > If we do this then we could reuse a lot of > code to > make a aerogear-java > as well. > > 2) How granular do we want our modules? > > IE If we break out push into > aerogear-android-push > would that include > GCM, SimplePush, MQTT, etc in one package > or would it > look like > > > android-gcm > android-simplepush > android-mqtt > > > +1 to those names, and i'm sure you mean > aerogear-* :) > > > yep ;-) > > > > > > aerogear-android-push-core, > aerogear-android-push-mqtt etc. > > Thoughts? > > -- > 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 > > > > > _________________________________________________ > > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > > > > https://lists.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. > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > > -- > 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/20140305/d442452c/attachment-0001.html From bruno at abstractj.org Wed Mar 5 17:34:34 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 05 Mar 2014 14:34:34 -0800 (PST) Subject: [aerogear-dev] Let's change the AeroGear Twitter account handle In-Reply-To: References: Message-ID: <1394058874126.3cd644d4@Nodemailer> So let's just name it @aerogear_forever!? abstractj On Wed, Mar 5, 2014 at 5:34 PM, Jay Balunas wrote: > On Feb 21, 2014, at 12:59 AM, Matthias Wessendorf wrote: >> >> >> >> On Thu, Feb 20, 2014 at 11:17 PM, Bruno Oliveira wrote: >> I still can't see what the real value added on it. Everyone knows that there's a team behind it, so I can't see why "_team", also do we plan to create handles for "AeroGearPush", "AeroGearSecurity"...if yes, >> >> not sure on all these twitter handles. I'd vote -1 on all these accounts > +1 on the -1 for additional handles. >> >> >> that makes sense. And "_project", well we know, >> >> _project or _team - I think both is fine. I never really thought too much about it (team vs. project). > I would go with _team as it is shorter, although #aerogear_org I also like and is 1 character less than team. > We'll need to take a vote here, or come to some conclusion - I think it can be debated forever ;-) >> >> >> it's a project, the "s" on @aerogears always gave to me the sense of a bunch of people behind this to make it happen. >> >> I think the "real problem" is folks think "AeroGears" is the name of the project >> >> Wednesday I gave an AeroGear presentation. Due to the twitter handle of @AeroGears, two of those that asked questions, actually called the project AeroGears :)))) >> And that's what I have noticed before, which is, I think, the reason why Hylke brought it up. >> >> Unfortunately @AeroGear is taken, but I do think that @AeroGears is misleading - in terms of the name. >> >> However, your "@aerogears always gave to me the sense of a bunch of people behind this to make it happen." is a good thought! Which is believe leads towards _team, right? >> >> Again I never really interpreted too much into the meaning of the twitter handle, besides the fact that folks do not really get our name. >> >> >> Greetings, >> Matthias >> >> >> >> >> >> >> >> >> On Thu, Feb 20, 2014 at 6:54 PM, Matthias Wessendorf wrote: >> Actually, @aerogear_project makes sense (see @netty_project) >> >> >> On Thu, Feb 20, 2014 at 10:35 PM, Matthias Wessendorf wrote: >> @__aerogear or @_aerogear ? >> >> >> >> >> On Thu, Feb 20, 2014 at 10:07 PM, Douglas Campos wrote: >> **If** we're really forced to change, I'd go with @aerogear_project >> >> -- >> 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 >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> >> -- >> "The measure of a man is what he does with power" - Plato >> - >> @abstractj >> - >> Volenti Nihil Difficile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/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/20140305/eeb68b9b/attachment.html From bam at tretau.net Thu Mar 6 05:08:19 2014 From: bam at tretau.net (ttretau) Date: Thu, 6 Mar 2014 02:08:19 -0800 (PST) Subject: [aerogear-dev] aerogear-pushplugin-cordova / categories Message-ID: <1394100499280-6655.post@n5.nabble.com> Hello all, just to make sure that I am not finding it: Could it be that the current cordova plugin does not reflect the categories feature? I am looking to register a device with the cordova plugin and categories in the pushConfig. Kind regards, Torben -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-pushplugin-cordova-categories-tp6655.html Sent from the aerogear-dev mailing list archive at Nabble.com. From edewit at redhat.com Thu Mar 6 05:25:43 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 6 Mar 2014 11:25:43 +0100 Subject: [aerogear-dev] aerogear-pushplugin-cordova / categories In-Reply-To: <1394100499280-6655.post@n5.nabble.com> References: <1394100499280-6655.post@n5.nabble.com> Message-ID: Hi Torben, You are right it?s a bug I?ve create an issue for it AEROGEAR-1453 I?ll fix it today Thanks, Erik Jan On 6 Mar,2014, at 11:08 , ttretau wrote: > Hello all, > > just to make sure that I am not finding it: > Could it be that the current cordova plugin does not reflect the categories > feature? > > I am looking to register a device with the cordova plugin and categories in > the pushConfig. > > Kind regards, > > Torben > > > > -- > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-pushplugin-cordova-categories-tp6655.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140306/c05af0e8/attachment.html From miguel21op at gmail.com Thu Mar 6 05:29:00 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Thu, 6 Mar 2014 10:29:00 +0000 Subject: [aerogear-dev] aerogear-pushplugin-cordova / categories In-Reply-To: References: <1394100499280-6655.post@n5.nabble.com> Message-ID: <712428F4-725A-4BAE-82B3-B62CDC7B37C0@gmail.com> Yes. I noticed that too some days ago... I thought it was a deprecated feature. Enviado do meu iPhone No dia 06/03/2014, ?s 10:25, Erik Jan de Wit escreveu: > Hi Torben, > > You are right it?s a bug I?ve create an issue for it AEROGEAR-1453 I?ll fix it today > > Thanks, > Erik Jan > >> On 6 Mar,2014, at 11:08 , ttretau wrote: >> >> Hello all, >> >> just to make sure that I am not finding it: >> Could it be that the current cordova plugin does not reflect the categories >> feature? >> >> I am looking to register a device with the cordova plugin and categories in >> the pushConfig. >> >> Kind regards, >> >> Torben >> >> >> >> -- >> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-pushplugin-cordova-categories-tp6655.html >> Sent from the aerogear-dev mailing list archive at Nabble.com. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140306/6413d286/attachment.html From scm.blanc at gmail.com Thu Mar 6 06:05:25 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 6 Mar 2014 12:05:25 +0100 Subject: [aerogear-dev] FirefoxOS support in aerogear-pushplugin-cordova Message-ID: Hi Folks, As you may know, Firefox OS is now a supported platform in Cordova [1] , that's cool ! And since Firefox OS has also a Push feature, that we all know very well - SimplePush- , I think it would be cool that we update our plugin to support that. I start looking at this and it won't be too complicated. The idea is to wrap the FFOS Push interface inside our Plugin interface. Since FFOS is "all" web, no Native stuff is involved, just some additional JavaScript. wdyt ? The Jira to track : https://issues.jboss.org/browse/AEROGEAR-1454 Sebi [1] https://hacks.mozilla.org/2014/02/building-cordova-apps-for-firefox-os/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140306/51f00b00/attachment-0001.html From matzew at apache.org Thu Mar 6 06:12:57 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 6 Mar 2014 12:12:57 +0100 Subject: [aerogear-dev] FirefoxOS support in aerogear-pushplugin-cordova In-Reply-To: References: Message-ID: On Thu, Mar 6, 2014 at 12:05 PM, Sebastien Blanc wrote: > Hi Folks, > As you may know, Firefox OS is now a supported platform in Cordova [1] , > that's cool ! > > And since Firefox OS has also a Push feature, that we all know very well - > SimplePush- , I think it would be cool that we update our plugin to support > that. > > I start looking at this and it won't be too complicated. The idea is to > wrap the FFOS Push interface inside our Plugin interface. Since FFOS is > "all" web, no Native stuff is involved, just some additional JavaScript. > > wdyt ? > it sounds like a great plan! -M > > The Jira to track : https://issues.jboss.org/browse/AEROGEAR-1454 > > Sebi > > > > [1] > https://hacks.mozilla.org/2014/02/building-cordova-apps-for-firefox-os/ > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140306/5c2921fb/attachment.html From corinnekrych at gmail.com Thu Mar 6 07:21:16 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 6 Mar 2014 13:21:16 +0100 Subject: [aerogear-dev] FirefoxOS support in aerogear-pushplugin-cordova In-Reply-To: References: Message-ID: <7F0BD288-7B54-4D92-99DB-0B82BBF353E8@gmail.com> +1 Great idea On 06 Mar 2014, at 12:12, Matthias Wessendorf wrote: > > > > On Thu, Mar 6, 2014 at 12:05 PM, Sebastien Blanc wrote: > Hi Folks, > As you may know, Firefox OS is now a supported platform in Cordova [1] , that's cool ! > > And since Firefox OS has also a Push feature, that we all know very well - SimplePush- , I think it would be cool that we update our plugin to support that. > > I start looking at this and it won't be too complicated. The idea is to wrap the FFOS Push interface inside our Plugin interface. Since FFOS is "all" web, no Native stuff is involved, just some additional JavaScript. > > wdyt ? > > it sounds like a great plan! > > -M > > > > The Jira to track : https://issues.jboss.org/browse/AEROGEAR-1454 > > Sebi > > > > [1] https://hacks.mozilla.org/2014/02/building-cordova-apps-for-firefox-os/ > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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 bam at tretau.net Thu Mar 6 07:23:26 2014 From: bam at tretau.net (ttretau) Date: Thu, 6 Mar 2014 04:23:26 -0800 (PST) Subject: [aerogear-dev] aerogear-pushplugin-cordova / categories In-Reply-To: References: <1394100499280-6655.post@n5.nabble.com> Message-ID: <1394108606824-6661.post@n5.nabble.com> Hello Erik Jan, that's great! Thank you, I will test it then.. Kind regards, Torben -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-pushplugin-cordova-categories-tp6655p6661.html Sent from the aerogear-dev mailing list archive at Nabble.com. From kpiwko at redhat.com Thu Mar 6 08:35:14 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 6 Mar 2014 14:35:14 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: References: Message-ID: <20140306143514.576e6e47@kapy-ntb-x220> For Chrome Variant, chrome tab snippet is empty - http://imgur.com/cK8Tas2 Also, Download Client SDK image does not work. Otherwise, great stuff! As need a single source for snippets across aerogear.org, documentation, UPS and example. I believe this makes UPS an authoritative source of registration snippets. Karel On Tue, 4 Mar 2014 18:09:16 +0100 Sebastien Blanc wrote: > Hi, > > I've started to work on AGPUSH-550 > where > the idea is to generate Device Registration code Snippets that the user can > copy/paste into his client application. > > The flow is quite simple : he chooses a Variant, then click a link on the > right that brings you to the Snippets page. > Since the console knows the type of the selected variant, the appropriate > snippet is generated ... Yes "generated" , that means it's not a static > code snippet but it's actually filled with the needed info : UPS Server > URL, Variant ID, Variant Secret, SenderId (for Android). > > For each code snippet, there also the Cordova version for it. So, if you > choose an Android variant for instance you will have : > > [image: Inline image 1] > > And as you can see, there is also a link to cordova : > > [image: Inline image 2] > > This is still work in progress, needs polishing etc ... But once we got > this, it will be really easy for a new user to get started. All the > variants type are covered : iOS, Android and SPS > > Oh, want to test it live ? Give it a try here : > https://newpush-sblanc.rhcloud.com/ (admin / 123) > > I will probably PR that very soon, in the same time you can check this > branch > https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 > if > you want to play with it locally. > > See you ! > Sebi From kpiwko at redhat.com Thu Mar 6 08:38:29 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 6 Mar 2014 14:38:29 +0100 Subject: [aerogear-dev] Modularizing the Android Library In-Reply-To: <5317317F.1010209@redhat.com> References: <5317317F.1010209@redhat.com> Message-ID: <20140306143829.65e1e4aa@kapy-ntb-x220> I believe there should be a POM depchain for users that are willing just to use aerogear-android and modular dependencies are for more experienced users. Similarly to *Adding ShrinkWrap Resolvers to your project* at https://github.com/shrinkwrap/resolver/blob/master/README.asciidoc I'm not sure how nicely that would play with Gradle though. Karel On Wed, 05 Mar 2014 09:15:27 -0500 Summers Pittman wrote: > Earlier in development (pre passos) making the Android SDK into modules > was not a concern (in fact it was an anti-concern). > > Now, however, we have a much more complete project and it is time to > have that discussion. > > Right now we have two BIG questions: > > 1) Do we want to break out interfaces and implementation? > > If we do this then we could reuse a lot of code to make a aerogear-java > as well. > > 2) How granular do we want our modules? > > IE If we break out push into aerogear-android-push would that include > GCM, SimplePush, MQTT, etc in one package or would it look like > aerogear-android-push-core, aerogear-android-push-mqtt etc. > > Thoughts? > From scm.blanc at gmail.com Thu Mar 6 09:09:26 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 6 Mar 2014 15:09:26 +0100 Subject: [aerogear-dev] [UPS-Console] Showing Registration Code Snippets In-Reply-To: <20140306143514.576e6e47@kapy-ntb-x220> References: <20140306143514.576e6e47@kapy-ntb-x220> Message-ID: On Thu, Mar 6, 2014 at 2:35 PM, Karel Piwko wrote: > For Chrome Variant, chrome tab snippet is empty - http://imgur.com/cK8Tas2 Ah right I forgot to test on our newborn ! > > > Also, Download Client SDK image does not work. > Yeah, that was just part of the fork, before merging I should remove it or put a real link if people think it might be useful > > Otherwise, great stuff! As need a single source for snippets across > aerogear.org, documentation, UPS and example. I believe this makes UPS an > authoritative source of registration snippets. > > Karel > > On Tue, 4 Mar 2014 18:09:16 +0100 > Sebastien Blanc wrote: > > > Hi, > > > > I've started to work on AGPUSH-550 > > where > > the idea is to generate Device Registration code Snippets that the user > can > > copy/paste into his client application. > > > > The flow is quite simple : he chooses a Variant, then click a link on the > > right that brings you to the Snippets page. > > Since the console knows the type of the selected variant, the > appropriate > > snippet is generated ... Yes "generated" , that means it's not a static > > code snippet but it's actually filled with the needed info : UPS Server > > URL, Variant ID, Variant Secret, SenderId (for Android). > > > > For each code snippet, there also the Cordova version for it. So, if you > > choose an Android variant for instance you will have : > > > > [image: Inline image 1] > > > > And as you can see, there is also a link to cordova : > > > > [image: Inline image 2] > > > > This is still work in progress, needs polishing etc ... But once we got > > this, it will be really easy for a new user to get started. All the > > variants type are covered : iOS, Android and SPS > > > > Oh, want to test it live ? Give it a try here : > > https://newpush-sblanc.rhcloud.com/ (admin / 123) > > > > I will probably PR that very soon, in the same time you can check this > > branch > > > https://github.com/sebastienblanc/aerogear-unified-push-server-admin-ui/tree/AGPUSH-550 > > if > > you want to play with it locally. > > > > See you ! > > 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/20140306/f883cea8/attachment.html From tiagor87 at gmail.com Thu Mar 6 11:37:02 2014 From: tiagor87 at gmail.com (Tiago Resende) Date: Thu, 6 Mar 2014 13:37:02 -0300 Subject: [aerogear-dev] [Pipe] Wrapped Response Message-ID: Hi guys, My name is Tiago, I am an old Daniel Passos's student from Brazil. I'm new here and have a lot of noob questions, so, take it easy and forgive my english. I am trying to integrate AG for Android to a WCF Service on .Net C#, but all service responses are configured as Wrapped, so AG isn't working properly. I just wanna know... Should I create Wrapped objects for every endpoint, or is there another method to do it, some work around? Thanks everyone. -- *Tiago de Carvalho Resende* Desenvolvedor "O importante n?o ? saber fazer, ? saber de onde copiar." por Bernardo Esb?rard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140306/c22a42ae/attachment-0001.html From torben at tretau.net Thu Mar 6 11:45:37 2014 From: torben at tretau.net (Torben Tretau) Date: Thu, 06 Mar 2014 17:45:37 +0100 Subject: [aerogear-dev] aerogear-pushplugin-cordova / categories In-Reply-To: References: <1394100499280-6655.post@n5.nabble.com> Message-ID: <20140306174537.Horde.B1OYG9dIxsx1b1DnavQWug7@webmail.df.eu> Hi Erik Jan, fine, I tested it and it works now.. Thank you again, great work! Torben Quoting Erik Jan de Wit : > Hi Torben, > > You are right it?s a bug I?ve create an issue for it AEROGEAR-1453 > I?ll fix it today > > Thanks, > Erik Jan > > On 6 Mar,2014, at 11:08 , ttretau wrote: > >> Hello all, >> >> just to make sure that I am not finding it: >> Could it be that the current cordova plugin does not reflect the categories >> feature? >> >> I am looking to register a device with the cordova plugin and categories in >> the pushConfig. >> >> Kind regards, >> >> Torben >> >> >> >> -- >> View this message in context: >> http://aerogear-dev.1069024.n5.nabble.com/aerogear-pushplugin-cordova-categories-tp6655.html >> Sent from the aerogear-dev mailing list archive at Nabble.com. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev From supittma at redhat.com Thu Mar 6 12:08:49 2014 From: supittma at redhat.com (Summers Pittman) Date: Thu, 06 Mar 2014 12:08:49 -0500 Subject: [aerogear-dev] [Pipe] Wrapped Response In-Reply-To: References: Message-ID: <5318ABA1.1070902@redhat.com> On Thu 06 Mar 2014 11:37:02 AM EST, Tiago Resende wrote: > Hi guys, My name is Tiago, I am an old Daniel Passos's student from > Brazil. > > I'm new here and have a lot of noob questions, so, take it easy and > forgive my english. > > I am trying to integrate AG for Android to a WCF Service on .Net C#, > but all service responses are configured as Wrapped, so AG isn't > working properly. > > I just wanna know... Should I create Wrapped objects for every > endpoint, or is there another method to do it, some work around? > I'm not familiar with .Net, but if your response is JSON and you have a nested object you wish to fetch, you can use the DataRoot property in PipeConfig (In AeroGear 1.3.1, in the master branch this will be changed to a property on a MarshallingConfig object) > Thanks everyone. > > -- > *Tiago de Carvalho Resende* > Desenvolvedor > > "O importante n?o ? saber fazer, > > ? saber de onde copiar." > > por Bernardo Esb?rard > > > > _______________________________________________ > 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 daniel at passos.me Thu Mar 6 12:22:19 2014 From: daniel at passos.me (Daniel Passos) Date: Thu, 6 Mar 2014 14:22:19 -0300 Subject: [aerogear-dev] [Pipe] Wrapped Response In-Reply-To: References: Message-ID: Hi Tiago, I not sure what you mean about wrapper. But, if you JSON is not equals to your model you can annotate your model using @SerializedName("name_of_your_json_property") Please, gist[1] your Android model and your JSON [1] https://gist.github.com/ -- Passos On Thu, Mar 6, 2014 at 1:37 PM, Tiago Resende wrote: > Hi guys, My name is Tiago, I am an old Daniel Passos's student from > Brazil. > > I'm new here and have a lot of noob questions, so, take it easy and > forgive my english. > > I am trying to integrate AG for Android to a WCF Service on .Net C#, but > all service responses are configured as Wrapped, so AG isn't working > properly. > > I just wanna know... Should I create Wrapped objects for every endpoint, > or is there another method to do it, some work around? > > Thanks everyone. > > -- > *Tiago de Carvalho Resende* > Desenvolvedor > > "O importante n?o ? saber fazer, > > ? saber de onde copiar." > > por Bernardo Esb?rard > > > > _______________________________________________ > 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/20140306/d74493a2/attachment.html From tiagor87 at gmail.com Thu Mar 6 12:57:58 2014 From: tiagor87 at gmail.com (Tiago Resende) Date: Thu, 6 Mar 2014 14:57:58 -0300 Subject: [aerogear-dev] [Pipe] Wrapped Response In-Reply-To: References: Message-ID: When a response is wrapped, it comes encapsulated, just like this: - Response On Thursday, March 6, 2014, Daniel Passos wrote: > Hi Tiago, > > I not sure what you mean about wrapper. But, if you JSON is not equals to > your model you can annotate your model using > @SerializedName("name_of_your_json_property") > > Please, gist[1] your Android model and your JSON > > [1] https://gist.github.com/ > > -- Passos > > > On Thu, Mar 6, 2014 at 1:37 PM, Tiago Resende > > wrote: > >> Hi guys, My name is Tiago, I am an old Daniel Passos's student from >> Brazil. >> >> I'm new here and have a lot of noob questions, so, take it easy and >> forgive my english. >> >> I am trying to integrate AG for Android to a WCF Service on .Net C#, but >> all service responses are configured as Wrapped, so AG isn't working >> properly. >> >> I just wanna know... Should I create Wrapped objects for every endpoint, >> or is there another method to do it, some work around? >> >> Thanks everyone. >> >> -- >> *Tiago de Carvalho Resende* >> Desenvolvedor >> >> "O importante n?o ? saber fazer, >> >> ? saber de onde copiar." >> >> por Bernardo Esb?rard >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -- *Tiago de Carvalho Resende* Desenvolvedor "O importante n?o ? saber fazer, ? saber de onde copiar." por Bernardo Esb?rard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140306/f91f582d/attachment.html From daniel at passos.me Thu Mar 6 13:14:53 2014 From: daniel at passos.me (Daniel Passos) Date: Thu, 6 Mar 2014 15:14:53 -0300 Subject: [aerogear-dev] [Pipe] Wrapped Response In-Reply-To: References: Message-ID: Well, It's not a valid JSON -- Passos On Thu, Mar 6, 2014 at 2:57 PM, Tiago Resende wrote: > When a response is wrapped, it comes encapsulated, just like this: > > - Response > > > > > On Thursday, March 6, 2014, Daniel Passos wrote: > >> Hi Tiago, >> >> I not sure what you mean about wrapper. But, if you JSON is not equals to >> your model you can annotate your model using >> @SerializedName("name_of_your_json_property") >> >> Please, gist[1] your Android model and your JSON >> >> [1] https://gist.github.com/ >> >> -- Passos >> >> >> On Thu, Mar 6, 2014 at 1:37 PM, Tiago Resende wrote: >> >>> Hi guys, My name is Tiago, I am an old Daniel Passos's student from >>> Brazil. >>> >>> I'm new here and have a lot of noob questions, so, take it easy and >>> forgive my english. >>> >>> I am trying to integrate AG for Android to a WCF Service on .Net C#, but >>> all service responses are configured as Wrapped, so AG isn't working >>> properly. >>> >>> I just wanna know... Should I create Wrapped objects for every endpoint, >>> or is there another method to do it, some work around? >>> >>> Thanks everyone. >>> >>> -- >>> *Tiago de Carvalho Resende* >>> Desenvolvedor >>> >>> "O importante n?o ? saber fazer, >>> >>> ? saber de onde copiar." >>> >>> por Bernardo Esb?rard >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > > -- > *Tiago de Carvalho Resende* > Desenvolvedor > > "O importante n?o ? saber fazer, > > ? saber de onde copiar." > > por Bernardo Esb?rard > > > > > _______________________________________________ > 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/20140306/9a7f4f1a/attachment-0001.html From tiagor87 at gmail.com Thu Mar 6 13:21:03 2014 From: tiagor87 at gmail.com (Tiago Resende) Date: Thu, 6 Mar 2014 15:21:03 -0300 Subject: [aerogear-dev] [Pipe] Wrapped Response In-Reply-To: References: Message-ID: I will write it in JSON. I gave a bad example. Imagine my method in WS is called "GetUserById", so my response for this method, would be: { GetUserByIdResponse: { Login: 'Tiago', Email: 'tiagor87 at gmail.com' } }; 2014-03-06 15:14 GMT-03:00 Daniel Passos : > Well, It's not a valid JSON > > -- Passos > > > On Thu, Mar 6, 2014 at 2:57 PM, Tiago Resende wrote: > >> When a response is wrapped, it comes encapsulated, just like this: >> >> - Response >> >> >> >> >> On Thursday, March 6, 2014, Daniel Passos wrote: >> >>> Hi Tiago, >>> >>> I not sure what you mean about wrapper. But, if you JSON is not equals >>> to your model you can annotate your model using >>> @SerializedName("name_of_your_json_property") >>> >>> Please, gist[1] your Android model and your JSON >>> >>> [1] https://gist.github.com/ >>> >>> -- Passos >>> >>> >>> On Thu, Mar 6, 2014 at 1:37 PM, Tiago Resende wrote: >>> >>>> Hi guys, My name is Tiago, I am an old Daniel Passos's student from >>>> Brazil. >>>> >>>> I'm new here and have a lot of noob questions, so, take it easy and >>>> forgive my english. >>>> >>>> I am trying to integrate AG for Android to a WCF Service on .Net C#, >>>> but all service responses are configured as Wrapped, so AG isn't working >>>> properly. >>>> >>>> I just wanna know... Should I create Wrapped objects for every >>>> endpoint, or is there another method to do it, some work around? >>>> >>>> Thanks everyone. >>>> >>>> -- >>>> *Tiago de Carvalho Resende* >>>> Desenvolvedor >>>> >>>> "O importante n?o ? saber fazer, >>>> >>>> ? saber de onde copiar." >>>> >>>> por Bernardo Esb?rard >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> >> -- >> *Tiago de Carvalho Resende* >> Desenvolvedor >> >> "O importante n?o ? saber fazer, >> >> ? saber de onde copiar." >> >> por Bernardo Esb?rard >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- *Tiago de Carvalho Resende* Desenvolvedor "O importante n?o ? saber fazer, ? saber de onde copiar." por Bernardo Esb?rard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140306/1689840d/attachment.html From daniel at passos.me Thu Mar 6 13:32:39 2014 From: daniel at passos.me (Daniel Passos) Date: Thu, 6 Mar 2014 15:32:39 -0300 Subject: [aerogear-dev] [Pipe] Wrapped Response In-Reply-To: References: Message-ID: Hi Tiago, In this case as Summers said you need use DataRoot. See "Nested Data in Result" section in Pipe document[1] [1] http://aerogear.org/docs/guides/aerogear-android/pipe/ -- Passos On Thu, Mar 6, 2014 at 3:21 PM, Tiago Resende wrote: > I will write it in JSON. I gave a bad example. > > Imagine my method in WS is called "GetUserById", so my response for this > method, would be: > > { GetUserByIdResponse: { Login: 'Tiago', Email: 'tiagor87 at gmail.com' } }; > > > > 2014-03-06 15:14 GMT-03:00 Daniel Passos : > > Well, It's not a valid JSON >> >> -- Passos >> >> >> On Thu, Mar 6, 2014 at 2:57 PM, Tiago Resende wrote: >> >>> When a response is wrapped, it comes encapsulated, just like this: >>> >>> - Response >>> >>> >>> >>> >>> On Thursday, March 6, 2014, Daniel Passos wrote: >>> >>>> Hi Tiago, >>>> >>>> I not sure what you mean about wrapper. But, if you JSON is not equals >>>> to your model you can annotate your model using >>>> @SerializedName("name_of_your_json_property") >>>> >>>> Please, gist[1] your Android model and your JSON >>>> >>>> [1] https://gist.github.com/ >>>> >>>> -- Passos >>>> >>>> >>>> On Thu, Mar 6, 2014 at 1:37 PM, Tiago Resende wrote: >>>> >>>>> Hi guys, My name is Tiago, I am an old Daniel Passos's student from >>>>> Brazil. >>>>> >>>>> I'm new here and have a lot of noob questions, so, take it easy and >>>>> forgive my english. >>>>> >>>>> I am trying to integrate AG for Android to a WCF Service on .Net C#, >>>>> but all service responses are configured as Wrapped, so AG isn't working >>>>> properly. >>>>> >>>>> I just wanna know... Should I create Wrapped objects for every >>>>> endpoint, or is there another method to do it, some work around? >>>>> >>>>> Thanks everyone. >>>>> >>>>> -- >>>>> *Tiago de Carvalho Resende* >>>>> Desenvolvedor >>>>> >>>>> "O importante n?o ? saber fazer, >>>>> >>>>> ? saber de onde copiar." >>>>> >>>>> por Bernardo Esb?rard >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >>> -- >>> *Tiago de Carvalho Resende* >>> Desenvolvedor >>> >>> "O importante n?o ? saber fazer, >>> >>> ? saber de onde copiar." >>> >>> por Bernardo Esb?rard >>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > *Tiago de Carvalho Resende* > Desenvolvedor > > "O importante n?o ? saber fazer, > > ? saber de onde copiar." > > por Bernardo Esb?rard > > > > _______________________________________________ > 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/20140306/0375cde6/attachment.html From hbons at redhat.com Fri Mar 7 08:34:30 2014 From: hbons at redhat.com (Hylke Bons) Date: Fri, 07 Mar 2014 14:34:30 +0100 Subject: [aerogear-dev] AeroGear project structure and the website In-Reply-To: <2034169871.13133471.1393946964631.JavaMail.zimbra@redhat.com> References: <53060BE2.6030803@redhat.com> <80A6BAD7-8EBD-4D55-9FE8-267BF3474603@gmail.com> <309198315.8064032.1393253413875.JavaMail.zimbra@redhat.com> <530CD63F.9060300@redhat.com> <2034169871.13133471.1393946964631.JavaMail.zimbra@redhat.com> Message-ID: <5319CAE6.3070306@redhat.com> On 04/03/2014 16:29, Lee Graham wrote: > > > ------------------------------------------------------------------------ > > *From: *"Hylke Bons" > *To: *aerogear-dev at lists.jboss.org > *Sent: *Tuesday, February 25, 2014 12:43:27 PM > *Subject: *Re: [aerogear-dev] AeroGear project structure and the > website > > On 24/02/2014 14:50, Lee Graham wrote: > > So If I'm a Cordova developer and I want to learn how-to setup > > UnifiedPush Server and integrate Push within my hybrid app I don't > > care about the native Android & iOS libraries, guides, etc.. I just > > want everything that is relevant to hybrid apps. I actually ran > into > > this exact issue this last weekend when I created my first push > > notification app. Its hard to keep track of what guides and sample > > code I needed. This may solve that. I kind of like the way > > http://devcenter.kinvey.com/ does this. When I first go there it > > allows me to select my dev platform and it sets a cookie so when I > > come back its still on that platform. I can swap at any time, > but as a > > developer I really liked the Kinvey experience because I could find > > what I needed. Nothing more nothing less. > > Cordova is a bit of a special case. Apart from a mention that > Cordova is > a supported platform on the front page, I'm not quite if we should > have > it as a mention for every feature, as we already have Javascript > there. > > We need to find out how Corodova developers normally go about picking > libraries that they want to use. I assume they can use any Javascript > library? Perhaps we just add a note to the download page that for use > with Cordova you case use the Javascript library and download a > native > plugin if needed. > > Makes sense to me. I think the current site does confuse me a bit... > what's the difference between Web/JavaScript and Hybrid/Cordova. If we > are using the same exact code (aerogear.js) then my first thought is > just to combine that under JavaScript (which I think is your > suggestion?). If the code is similar, but different between Web and > Hybrid then it may be useful to clearly define the differences. > > As a Cordova developer, I'm not a hardcore Java or Objective-C > developer. So my first thought is to find a plugin. If that doesn't > exist, I'm looking for JavaScript. I want the fastest route (aka the > least amount of coding) to integrating 3rd party tools and making it > work for both Android and iOS apps. > > Example 1: AeroGear push notification, I used the plugin. > > Example 2: Count.ly mobile analytics, I use the community Countly SDK > JS because there is no plugin: https://github.com/Countly/countly-sdk-js > > I hope this helps. I do really love the new look and feel of the > mockups. Very clean! Thanks Lee, that's a useful feedback. I'll have a look at more sites that have a Cordova offering. Hylke > > Hylke > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140307/71893997/attachment-0001.html From smikloso at redhat.com Fri Mar 7 11:11:40 2014 From: smikloso at redhat.com (Stefan Miklosovic) Date: Fri, 7 Mar 2014 11:11:40 -0500 (EST) Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: <2132437836.8006806.1394204804491.JavaMail.zimbra@redhat.com> Message-ID: <2042059273.8024848.1394208700188.JavaMail.zimbra@redhat.com> Hi, we are doing HTTPS tests on UPS integration tests where UPS Java client is used to send some payload to UPS, it seems it is not sufficient to have only plain HTTP sender when we are sending it to HTTPS endpoint. When JBoss AS is set up with keystore and truststore in https connector for web subsystem like this: and UPS Java client sends some payload (with HttpUrlConnection, not secure connection), this exception is thown from it: SEVERE: Send did not succeed: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target This basically means that server was not able to mark that connection as trusted. In order to use custom trustStore and trustStorePassword, they are propagated to test like system properties System.setProperty("javax.net.ssl.trustStore", "aerogear.truststore"); System.setProperty("javax.net.ssl.trustStorePassword", "aerogear"); however any attempt to set them in test itself like that is not successful since it is "too late". When they are set like -D properties with maven, it is executed without any problems. This does not work as well https://github.com/aerogear/aerogear-unifiedpush-java-client#known-issues since we are not using jsse (and can not) because of this issue https://issues.jboss.org/browse/JBPAPP6-711 which was repaired in 7.1.2 and that release is not community release anymore so we can not base tests on EAP and we are running them on 7.1.1. (we can not run them on WF as well since it is not compatible with EAP but 7.1.1 is). So this is chicken-egg problem. When verify-client is "none" plain http from UPS Java client is not validated. When we do want client authentication (verify-client=want/true), UPS sender is not https aware. Additionally, we can not use "jsse" due to JBPAPP6-711. Ideas? Stefan Miklosovic Red Hat Brno - JBoss Mobile Platform e-mail: smikloso at redhat.com irc: smikloso From matzew at apache.org Fri Mar 7 11:21:01 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 7 Mar 2014 17:21:01 +0100 Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: <2042059273.8024848.1394208700188.JavaMail.zimbra@redhat.com> References: <2132437836.8006806.1394204804491.JavaMail.zimbra@redhat.com> <2042059273.8024848.1394208700188.JavaMail.zimbra@redhat.com> Message-ID: On Fri, Mar 7, 2014 at 5:11 PM, Stefan Miklosovic wrote: > Hi, > > we are doing HTTPS tests on UPS integration tests where UPS Java client is > used to send some payload to UPS, it seems it is not sufficient to have > only plain HTTP sender when we are sending it to HTTPS endpoint. > > When JBoss AS is set up with keystore and truststore in https connector > for web subsystem like this: > > socket-binding="https" secure="true"> > password="aerogear" > certificate-key-file="${jboss.server.config.dir}/aerogear.keystore" > protocol="ALL" > verify-client="none" > certificate-file="${jboss.server.config.dir}/aerogear.keystore" > > ca-certificate-file="${jboss.server.config.dir}/aerogear.truststore"/> > > > and UPS Java client sends some payload (with HttpUrlConnection, not secure > connection), this exception is thown from it: > I guess we can use, for https, the HttpsUrlConnection - that;s what you are basically asking, right ? Mind to create PR for that ? Thanks! Matthias > > SEVERE: Send did not succeed: sun.security.validator.ValidatorException: > PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target > > This basically means that server was not able to mark that connection as > trusted. > > In order to use custom trustStore and trustStorePassword, they are > propagated to test like system properties > > System.setProperty("javax.net.ssl.trustStore", "aerogear.truststore"); > System.setProperty("javax.net.ssl.trustStorePassword", "aerogear"); > > however any attempt to set them in test itself like that is not successful > since it is "too late". When they are set like -D properties with maven, it > is executed without any problems. > > This does not work as well > https://github.com/aerogear/aerogear-unifiedpush-java-client#known-issuessince we are not using jsse (and can not) because of this issue > https://issues.jboss.org/browse/JBPAPP6-711 which was repaired in 7.1.2 > and that release is not community release anymore so we can not base tests > on EAP and we are running them on 7.1.1. (we can not run them on WF as well > since it is not compatible with EAP but 7.1.1 is). > > So this is chicken-egg problem. When verify-client is "none" plain http > from UPS Java client is not validated. When we do want client > authentication (verify-client=want/true), UPS sender is not https aware. > Additionally, we can not use "jsse" due to JBPAPP6-711. > > Ideas? > > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: smikloso at redhat.com > irc: smikloso > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140307/e7c99e4e/attachment.html From io.christod at gmail.com Fri Mar 7 11:39:07 2014 From: io.christod at gmail.com (JChrist) Date: Fri, 7 Mar 2014 08:39:07 -0800 (PST) Subject: [aerogear-dev] Unified Push Server in Wildfly 8 final installation registration issue Message-ID: <1394210347601-6676.post@n5.nabble.com> Hello everyone, I have deployed the Unified push server (latest version, from master branch) on wildfly 8 final. Everything seems to be normal, except than when an app makes a registration (an android app installation), there is the following exception thrown: WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) Failed executing POST /registry/device: org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: application/octet-stream Is this something known, or should I report it to JIRA? Thanks! -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-in-Wildfly-8-final-installation-registration-issue-tp6676.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Fri Mar 7 11:53:17 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 7 Mar 2014 17:53:17 +0100 Subject: [aerogear-dev] Unified Push Server in Wildfly 8 final installation registration issue In-Reply-To: <1394210347601-6676.post@n5.nabble.com> References: <1394210347601-6676.post@n5.nabble.com> Message-ID: Hello, thanks for reporting - yes a JIRA is perfect - will give it a look after the weekend. Greetings, Matthias On Fri, Mar 7, 2014 at 5:39 PM, JChrist wrote: > Hello everyone, > I have deployed the Unified push server (latest version, from master > branch) > on wildfly 8 final. Everything seems to be normal, > except than when an app makes a registration (an android app installation), > there is the following exception thrown: > > WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) Failed > executing POST /registry/device: > org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find > MessageBodyWriter for response object of type: > org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: > application/octet-stream > > Is this something known, or should I report it to JIRA? > Thanks! > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-in-Wildfly-8-final-installation-registration-issue-tp6676.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140307/5c4ee848/attachment.html From tolisemm at gmail.com Fri Mar 7 14:30:36 2014 From: tolisemm at gmail.com (tolis emmanouilidis) Date: Fri, 7 Mar 2014 21:30:36 +0200 Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: References: <2132437836.8006806.1394204804491.JavaMail.zimbra@redhat.com> <2042059273.8024848.1394208700188.JavaMail.zimbra@redhat.com> Message-ID: 2014-03-07 18:21 GMT+02:00 Matthias Wessendorf : > > > > On Fri, Mar 7, 2014 at 5:11 PM, Stefan Miklosovic wrote: > >> Hi, >> >> we are doing HTTPS tests on UPS integration tests where UPS Java client >> is used to send some payload to UPS, it seems it is not sufficient to have >> only plain HTTP sender when we are sending it to HTTPS endpoint. >> >> When JBoss AS is set up with keystore and truststore in https connector >> for web subsystem like this: >> >> > socket-binding="https" secure="true"> >> > password="aerogear" >> >> certificate-key-file="${jboss.server.config.dir}/aerogear.keystore" >> protocol="ALL" >> verify-client="none" >> certificate-file="${jboss.server.config.dir}/aerogear.keystore" >> >> ca-certificate-file="${jboss.server.config.dir}/aerogear.truststore"/> >> >> >> and UPS Java client sends some payload (with HttpUrlConnection, not >> secure connection), this exception is thown from it: >> > > I guess we can use, for https, the HttpsUrlConnection - that;s what you > are basically asking, right ? > > Mind to create PR for that ? > > Thanks! > Matthias > > The certificate used in UPS integration tests is self signed. The SSL handshake, most probably will fail even when using HttpsUrlConnection, if the custom truststore is not set. I believe that the existing UPS sender version will work when a real, valid certificate is used instead of a self signed one. This issue could be fixed if UPS sender was providing a functionality to set up and use a custom TrustManager which contains the Keystore with the self signed certificate. In my opinion, the question is whether supporting self signed certificates in UPS sender, brings value. Thanks, Tolis > > >> >> SEVERE: Send did not succeed: sun.security.validator.ValidatorException: >> PKIX path building failed: >> sun.security.provider.certpath.SunCertPathBuilderException: unable to find >> valid certification path to requested target >> > >> This basically means that server was not able to mark that connection as >> trusted. >> >> In order to use custom trustStore and trustStorePassword, they are >> propagated to test like system properties >> >> System.setProperty("javax.net.ssl.trustStore", "aerogear.truststore"); >> System.setProperty("javax.net.ssl.trustStorePassword", "aerogear"); >> >> however any attempt to set them in test itself like that is not >> successful since it is "too late". When they are set like -D properties >> with maven, it is executed without any problems. >> >> This does not work as well >> https://github.com/aerogear/aerogear-unifiedpush-java-client#known-issuessince we are not using jsse (and can not) because of this issue >> https://issues.jboss.org/browse/JBPAPP6-711 which was repaired in 7.1.2 >> and that release is not community release anymore so we can not base tests >> on EAP and we are running them on 7.1.1. (we can not run them on WF as well >> since it is not compatible with EAP but 7.1.1 is). >> >> So this is chicken-egg problem. When verify-client is "none" plain http >> from UPS Java client is not validated. When we do want client >> authentication (verify-client=want/true), UPS sender is not https aware. >> Additionally, we can not use "jsse" due to JBPAPP6-711. >> >> Ideas? >> >> Stefan Miklosovic >> Red Hat Brno - JBoss Mobile Platform >> >> e-mail: smikloso at redhat.com >> irc: smikloso >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > 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/20140307/5dc884fa/attachment-0001.html From matzew at apache.org Fri Mar 7 16:17:37 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 7 Mar 2014 22:17:37 +0100 Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: References: <2132437836.8006806.1394204804491.JavaMail.zimbra@redhat.com> <2042059273.8024848.1394208700188.JavaMail.zimbra@redhat.com> Message-ID: On Friday, March 7, 2014, tolis emmanouilidis wrote: > > > > 2014-03-07 18:21 GMT+02:00 Matthias Wessendorf > >: > >> >> >> >> On Fri, Mar 7, 2014 at 5:11 PM, Stefan Miklosovic >> > wrote: >> >>> Hi, >>> >>> we are doing HTTPS tests on UPS integration tests where UPS Java client >>> is used to send some payload to UPS, it seems it is not sufficient to have >>> only plain HTTP sender when we are sending it to HTTPS endpoint. >>> >>> When JBoss AS is set up with keystore and truststore in https connector >>> for web subsystem like this: >>> >>> >> socket-binding="https" secure="true"> >>> >> password="aerogear" >>> >>> certificate-key-file="${jboss.server.config.dir}/aerogear.keystore" >>> protocol="ALL" >>> verify-client="none" >>> certificate-file="${jboss.server.config.dir}/aerogear.keystore" >>> >>> ca-certificate-file="${jboss.server.config.dir}/aerogear.truststore"/> >>> >>> >>> and UPS Java client sends some payload (with HttpUrlConnection, not >>> secure connection), this exception is thown from it: >>> >> >> I guess we can use, for https, the HttpsUrlConnection - that;s what you >> are basically asking, right ? >> >> Mind to create PR for that ? >> >> Thanks! >> Matthias >> >> > The certificate used in UPS integration tests is self signed. The SSL > handshake, most probably will fail even when using HttpsUrlConnection, if > the custom truststore is not set. I believe that the existing UPS sender > version will work when a real, valid certificate is used instead of a self > signed one. > That's what I said on IRC: self signed certs issue > This issue could be fixed if UPS sender was providing a functionality to > set up and use a custom TrustManager which contains the Keystore with the > self signed certificate. In my opinion, the question is whether supporting > self signed certificates in UPS sender, brings value. > Tbh: not much.... > Thanks, > Tolis > > >> >> >>> >>> SEVERE: Send did not succeed: sun.security.validator.ValidatorException: >>> PKIX path building failed: >>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find >>> valid certification path to requested target >>> >> >>> This basically means that server was not able to mark that connection as >>> trusted. >>> >>> In order to use custom trustStore and trustStorePassword, they are >>> propagated to test like system properties >>> >>> System.setProperty("javax.net.ssl.trustStore", "aerogear.truststore"); >>> System.setProperty("javax.net.ssl.trustStorePassword", "aerogear"); >>> >>> however any attempt to set them in test itself like that is not >>> successful since it is "too late". When they are set like -D properties >>> with maven, it is executed without any problems. >>> >>> This does not work as well >>> https://github.com/aerogear/aerogear-unifiedpush-java-client#known-issuessince we are not using jsse (and can not) because of this issue >>> https://issues.jboss.org/browse/JBPAPP6-711 which was repaired in 7.1.2 >>> and that release is not community release anymore so we can not base tests >>> on EAP and we are running them on 7.1.1. (we can not run them on WF as well >>> since it is not compatible with EAP but 7.1.1 is). >>> >>> So this is chicken-egg problem. When verify-client is "none" plain http >>> from UPS Java client is not validated. When we do want client >>> authentication (verify-client=want/true), UPS sender is not https aware. >>> Additionally, we can not use "jsse" due to JBPAPP6-711. >>> >>> Ideas? >>> >>> Stefan Miklosovic >>> Red Hat Brno - JBoss Mobile Platform >>> >>> e-mail: smikloso at redhat.com >>> irc: smikloso >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> 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/20140307/15ea24d5/attachment.html From bruno at abstractj.org Fri Mar 7 22:06:35 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 07 Mar 2014 19:06:35 -0800 (PST) Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: References: Message-ID: <1394247994174.a05c8174@Nodemailer> IMO it should be supported on client/server side. This is exactly what I've been developing for mobile applications to establish a trustworthy relationship. I prefer self signed certificates, instead of trust on any CA? abstractj On Fri, Mar 7, 2014 at 4:30 PM, tolis emmanouilidis wrote: > 2014-03-07 18:21 GMT+02:00 Matthias Wessendorf : >> >> >> >> On Fri, Mar 7, 2014 at 5:11 PM, Stefan Miklosovic wrote: >> >>> Hi, >>> >>> we are doing HTTPS tests on UPS integration tests where UPS Java client >>> is used to send some payload to UPS, it seems it is not sufficient to have >>> only plain HTTP sender when we are sending it to HTTPS endpoint. >>> >>> When JBoss AS is set up with keystore and truststore in https connector >>> for web subsystem like this: >>> >>> >> socket-binding="https" secure="true"> >>> >> password="aerogear" >>> >>> certificate-key-file="${jboss.server.config.dir}/aerogear.keystore" >>> protocol="ALL" >>> verify-client="none" >>> certificate-file="${jboss.server.config.dir}/aerogear.keystore" >>> >>> ca-certificate-file="${jboss.server.config.dir}/aerogear.truststore"/> >>> >>> >>> and UPS Java client sends some payload (with HttpUrlConnection, not >>> secure connection), this exception is thown from it: >>> >> >> I guess we can use, for https, the HttpsUrlConnection - that;s what you >> are basically asking, right ? >> >> Mind to create PR for that ? >> >> Thanks! >> Matthias >> >> > The certificate used in UPS integration tests is self signed. The SSL > handshake, most probably will fail even when using HttpsUrlConnection, if > the custom truststore is not set. I believe that the existing UPS sender > version will work when a real, valid certificate is used instead of a self > signed one. > This issue could be fixed if UPS sender was providing a functionality to > set up and use a custom TrustManager which contains the Keystore with the > self signed certificate. In my opinion, the question is whether supporting > self signed certificates in UPS sender, brings value. > Thanks, > Tolis >> >> >>> >>> SEVERE: Send did not succeed: sun.security.validator.ValidatorException: >>> PKIX path building failed: >>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find >>> valid certification path to requested target >>> >> >>> This basically means that server was not able to mark that connection as >>> trusted. >>> >>> In order to use custom trustStore and trustStorePassword, they are >>> propagated to test like system properties >>> >>> System.setProperty("javax.net.ssl.trustStore", "aerogear.truststore"); >>> System.setProperty("javax.net.ssl.trustStorePassword", "aerogear"); >>> >>> however any attempt to set them in test itself like that is not >>> successful since it is "too late". When they are set like -D properties >>> with maven, it is executed without any problems. >>> >>> This does not work as well >>> https://github.com/aerogear/aerogear-unifiedpush-java-client#known-issuessince we are not using jsse (and can not) because of this issue >>> https://issues.jboss.org/browse/JBPAPP6-711 which was repaired in 7.1.2 >>> and that release is not community release anymore so we can not base tests >>> on EAP and we are running them on 7.1.1. (we can not run them on WF as well >>> since it is not compatible with EAP but 7.1.1 is). >>> >>> So this is chicken-egg problem. When verify-client is "none" plain http >>> from UPS Java client is not validated. When we do want client >>> authentication (verify-client=want/true), UPS sender is not https aware. >>> Additionally, we can not use "jsse" due to JBPAPP6-711. >>> >>> Ideas? >>> >>> Stefan Miklosovic >>> Red Hat Brno - JBoss Mobile Platform >>> >>> e-mail: smikloso at redhat.com >>> irc: smikloso >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> 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/20140307/aa9ebfaa/attachment-0001.html From edewit at redhat.com Sun Mar 9 15:38:16 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Sun, 9 Mar 2014 19:38:16 +0000 Subject: [aerogear-dev] toc Message-ID: <20AE80A5-0E15-4B9F-8B96-EA0E1E351115@redhat.com> Hi, As you may know I?ve created a example of how the toc could look like on our new site, the problem is with mobile we don?t have enough room to have a toc there as well. We could just remove the toc or we could have something like this: This is a drop down that shows the same information as the original toc and also behaves that way. I?m not a designer, but I think this would make a very nice solution. Here is a screen shot of how the toc would look on a desktop: What do you think? Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140309/3290781b/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: mobile.png Type: image/png Size: 12081 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140309/3290781b/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: toc-desktop.png Type: image/png Size: 24487 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140309/3290781b/attachment-0003.png From edewit at redhat.com Sun Mar 9 16:10:31 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Sun, 9 Mar 2014 20:10:31 +0000 Subject: [aerogear-dev] toc In-Reply-To: <20AE80A5-0E15-4B9F-8B96-EA0E1E351115@redhat.com> References: <20AE80A5-0E15-4B9F-8B96-EA0E1E351115@redhat.com> Message-ID: Also have a look at http://aerogear-edewit.rhcloud.com/docs/guides/new/index/ for a desktop version of the toc On 9 Mar,2014, at 19:38 , Erik Jan de Wit wrote: > Hi, > > As you may know I?ve created a example of how the toc could look like on our new site, the problem is with mobile we don?t have enough room to have a toc there as well. We could just remove the toc or we could have something like this: > > > > This is a drop down that shows the same information as the original toc and also behaves that way. I?m not a designer, but I think this would make a very nice solution. > > Here is a screen shot of how the toc would look on a desktop: > > > > What do you think? > > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140309/daf2470b/attachment.html From daniel at passos.me Sun Mar 9 20:12:46 2014 From: daniel at passos.me (Daniel Passos) Date: Sun, 9 Mar 2014 21:12:46 -0300 Subject: [aerogear-dev] Team meeting agenda Message-ID: http://oksoclap.com/p/aerogear-team-mgt-20140310 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140309/f72e35e4/attachment.html From bruno at abstractj.org Sun Mar 9 21:56:50 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Sun, 9 Mar 2014 22:56:50 -0300 Subject: [aerogear-dev] toc In-Reply-To: References: <20AE80A5-0E15-4B9F-8B96-EA0E1E351115@redhat.com> Message-ID: I vote for just remove the toc on mobile devices. On Sun, Mar 9, 2014 at 5:10 PM, Erik Jan de Wit wrote: > Also have a look at > http://aerogear-edewit.rhcloud.com/docs/guides/new/index/ for a desktop > version of the toc > > > On 9 Mar,2014, at 19:38 , Erik Jan de Wit wrote: > > Hi, > > As you may know I've created a example of how the toc could look like on > our new site, the problem is with mobile we don't have enough room to have > a toc there as well. We could just remove the toc or we could have > something like this: > > > > This is a drop down that shows the same information as the original toc > and also behaves that way. I'm not a designer, but I think this would make > a very nice solution. > > Here is a screen shot of how the toc would look on a desktop: > > > > What do you think? > > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- "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/20140309/e327a882/attachment.html From corinnekrych at gmail.com Mon Mar 10 03:17:05 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 10 Mar 2014 08:17:05 +0100 Subject: [aerogear-dev] toc In-Reply-To: References: <20AE80A5-0E15-4B9F-8B96-EA0E1E351115@redhat.com> Message-ID: @edewit i think your deployed solution is not working in small resolution The menu is still displeyed on the right hand side ++ Corinne On 10 Mar 2014, at 02:56, Bruno Oliveira wrote: > I vote for just remove the toc on mobile devices. > > > On Sun, Mar 9, 2014 at 5:10 PM, Erik Jan de Wit wrote: > Also have a look at http://aerogear-edewit.rhcloud.com/docs/guides/new/index/ for a desktop version of the toc > > > On 9 Mar,2014, at 19:38 , Erik Jan de Wit wrote: > >> Hi, >> >> As you may know I?ve created a example of how the toc could look like on our new site, the problem is with mobile we don?t have enough room to have a toc there as well. We could just remove the toc or we could have something like this: >> >> >> >> This is a drop down that shows the same information as the original toc and also behaves that way. I?m not a designer, but I think this would make a very nice solution. >> >> Here is a screen shot of how the toc would look on a desktop: >> >> >> >> What do you think? >> >> Cheers, >> Erik Jan >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > > -- > "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 From daniel.bevenius at gmail.com Mon Mar 10 05:33:54 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 10 Mar 2014 10:33:54 +0100 Subject: [aerogear-dev] SimplePush Server 0.10.0 Message-ID: Hi, we have staged AeroGear SimplePush Server 0.10.0 to Nexus: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2791/ An instance if available on OpenShift: https://sps010-dbevenius.rhcloud.com:8443/simplepush If you prefer to deploy to your own OpenShift account: rhc create-app sps010 " https://cartreflect-claytondev.rhcloud.com/reflect?github=danbev/openshift-origin-cartridge-aerogear-push&commit=bfff89f3e40e62a842dbe207bdc2fa7ff4089db9" mysql-5.1 This release contains the following JIRA tickets: https://issues.jboss.org/browse/AGSMPLPUSH-48?jql=fixVersion%20%3D%20%220.10.0%22%20AND%20project%20%3D%20AGSMPLPUSH Please take it for a spin and let us know if you have any issues. Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140310/7e37350a/attachment.html From matzew at apache.org Mon Mar 10 06:14:14 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 10 Mar 2014 11:14:14 +0100 Subject: [aerogear-dev] Unified Push Server in Wildfly 8 final installation registration issue In-Reply-To: References: <1394210347601-6676.post@n5.nabble.com> Message-ID: Hello Ioannis! thanks for filing AEROGEAR-1455. I just did a quick check w/ a CURL based (dummy) registration - that one worked fine. Are you using the native Android library for the actual registration ? Or are you using our Cordova bits? Thanks! Matthias On Fri, Mar 7, 2014 at 5:53 PM, Matthias Wessendorf wrote: > Hello, > > thanks for reporting - yes a JIRA is perfect - will give it a look after > the weekend. > > Greetings, > Matthias > > > On Fri, Mar 7, 2014 at 5:39 PM, JChrist wrote: > >> Hello everyone, >> I have deployed the Unified push server (latest version, from master >> branch) >> on wildfly 8 final. Everything seems to be normal, >> except than when an app makes a registration (an android app >> installation), >> there is the following exception thrown: >> >> WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) Failed >> executing POST /registry/device: >> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find >> MessageBodyWriter for response object of type: >> org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: >> application/octet-stream >> >> Is this something known, or should I report it to JIRA? >> Thanks! >> >> >> >> -- >> View this message in context: >> http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-in-Wildfly-8-final-installation-registration-issue-tp6676.html >> Sent from the aerogear-dev mailing list archive at Nabble.com. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- 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/20140310/e28015fa/attachment-0001.html From edewit at redhat.com Mon Mar 10 06:42:00 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 10 Mar 2014 10:42:00 +0000 Subject: [aerogear-dev] toc In-Reply-To: References: <20AE80A5-0E15-4B9F-8B96-EA0E1E351115@redhat.com> Message-ID: <0184D107-BCBA-43D7-9FF8-CD31ACD159F4@redhat.com> That is why I?m asking here how we should solve it! Removing it completely is an option the most simplest one. On 10 Mar,2014, at 7:17 , Corinne Krych wrote: > @edewit i think your deployed solution is not working in small resolution > The menu is still displeyed on the right hand side > ++ > Corinne > On 10 Mar 2014, at 02:56, Bruno Oliveira wrote: > >> I vote for just remove the toc on mobile devices. >> >> >> On Sun, Mar 9, 2014 at 5:10 PM, Erik Jan de Wit wrote: >> Also have a look at http://aerogear-edewit.rhcloud.com/docs/guides/new/index/ for a desktop version of the toc >> >> >> On 9 Mar,2014, at 19:38 , Erik Jan de Wit wrote: >> >>> Hi, >>> >>> As you may know I?ve created a example of how the toc could look like on our new site, the problem is with mobile we don?t have enough room to have a toc there as well. We could just remove the toc or we could have something like this: >>> >>> >>> >>> This is a drop down that shows the same information as the original toc and also behaves that way. I?m not a designer, but I think this would make a very nice solution. >>> >>> Here is a screen shot of how the toc would look on a desktop: >>> >>> >>> >>> What do you think? >>> >>> Cheers, >>> Erik Jan >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> >> -- >> "The measure of a man is what he does with power" - Plato >> - >> @abstractj >> - >> Volenti Nihil Difficile >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From corinnekrych at gmail.com Mon Mar 10 07:02:07 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 10 Mar 2014 12:02:07 +0100 Subject: [aerogear-dev] toc In-Reply-To: <0184D107-BCBA-43D7-9FF8-CD31ACD159F4@redhat.com> References: <20AE80A5-0E15-4B9F-8B96-EA0E1E351115@redhat.com> <0184D107-BCBA-43D7-9FF8-CD31ACD159F4@redhat.com> Message-ID: <09127D3E-1C5E-4CA5-BEE7-1156F03B36F8@gmail.com> Oops sorry disn?t read " for a desktop version of the toc? Let's choose the easiest solution. Go for for nothing for mobile. ++ Corinne On 10 Mar 2014, at 11:42, Erik Jan de Wit wrote: > That is why I?m asking here how we should solve it! Removing it completely is an option the most simplest one. > > On 10 Mar,2014, at 7:17 , Corinne Krych wrote: > >> @edewit i think your deployed solution is not working in small resolution >> The menu is still displeyed on the right hand side >> ++ >> Corinne >> On 10 Mar 2014, at 02:56, Bruno Oliveira wrote: >> >>> I vote for just remove the toc on mobile devices. >>> >>> >>> On Sun, Mar 9, 2014 at 5:10 PM, Erik Jan de Wit wrote: >>> Also have a look at http://aerogear-edewit.rhcloud.com/docs/guides/new/index/ for a desktop version of the toc >>> >>> >>> On 9 Mar,2014, at 19:38 , Erik Jan de Wit wrote: >>> >>>> Hi, >>>> >>>> As you may know I?ve created a example of how the toc could look like on our new site, the problem is with mobile we don?t have enough room to have a toc there as well. We could just remove the toc or we could have something like this: >>>> >>>> >>>> >>>> This is a drop down that shows the same information as the original toc and also behaves that way. I?m not a designer, but I think this would make a very nice solution. >>>> >>>> Here is a screen shot of how the toc would look on a desktop: >>>> >>>> >>>> >>>> What do you think? >>>> >>>> Cheers, >>>> Erik Jan >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> -- >>> >>> -- >>> "The measure of a man is what he does with power" - Plato >>> - >>> @abstractj >>> - >>> Volenti Nihil Difficile >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From cvasilak at gmail.com Mon Mar 10 08:08:24 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 10 Mar 2014 14:08:24 +0200 Subject: [aerogear-dev] iOS Push registration lib / iOS 7 Message-ID: Hi all, currently the push-ios registration lib relies on AFNetworking branch 1.x for its networking stack. In the process of updating to iOS 7, the plan was to update it also to use the AFNetworking 2.x series that is optimised for iOS 7. I am thinking though if it makes sense, at this point, to remove the AFNet dependency and go with just plain iOS 7 NSURLSession API for the networking. I think, It will make easier for developers to integrate it in their own projects, without having to another dependency which may or may not use as their networking stack. Wdyth? - Christos From matzew at apache.org Mon Mar 10 08:22:44 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 10 Mar 2014 13:22:44 +0100 Subject: [aerogear-dev] iOS Push registration lib / iOS 7 In-Reply-To: References: Message-ID: I am fine in getting rid of AFN here for the next release (e.g. 0.9.0 of the SDK) On Mon, Mar 10, 2014 at 1:08 PM, Christos Vasilakis wrote: > Hi all, > > currently the push-ios registration lib relies on AFNetworking branch 1.x > for its networking stack. In the process of updating to iOS 7, the plan was > to update it also to use the AFNetworking 2.x series that is optimised for > iOS 7. > > I am thinking though if it makes sense, at this point, to remove the AFNet > dependency and go with just plain iOS 7 NSURLSession API for the > networking. I think, It will make easier for developers to integrate it in > their own projects, without having to another dependency which may or may > not use as their networking stack. > > Wdyth? > > - > Christos > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140310/6de2a400/attachment.html From corinnekrych at gmail.com Mon Mar 10 08:30:19 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 10 Mar 2014 13:30:19 +0100 Subject: [aerogear-dev] iOS Push registration lib / iOS 7 In-Reply-To: References: Message-ID: <7162FBB3-7B45-42D9-B824-3BFF1C3572A6@gmail.com> +1 the less dependencies the better Corinne On 10 Mar 2014, at 13:22, Matthias Wessendorf wrote: > I am fine in getting rid of AFN here for the next release (e.g. 0.9.0 of the SDK) > > > > > On Mon, Mar 10, 2014 at 1:08 PM, Christos Vasilakis wrote: > Hi all, > > currently the push-ios registration lib relies on AFNetworking branch 1.x for its networking stack. In the process of updating to iOS 7, the plan was to update it also to use the AFNetworking 2.x series that is optimised for iOS 7. > > I am thinking though if it makes sense, at this point, to remove the AFNet dependency and go with just plain iOS 7 NSURLSession API for the networking. I think, It will make easier for developers to integrate it in their own projects, without having to another dependency which may or may not use as their networking stack. > > Wdyth? > > - > Christos > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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 scm.blanc at gmail.com Mon Mar 10 08:34:50 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 10 Mar 2014 13:34:50 +0100 Subject: [aerogear-dev] Unified Push Server in Wildfly 8 final installation registration issue In-Reply-To: References: <1394210347601-6676.post@n5.nabble.com> Message-ID: Hi ! I've done some testing and deployed a UPS on OpenShift using the Wildfly cartdridge : http://wildflyups-sblanc.rhcloud.com (admin / aerogear) I tested 2 android apps : 1 using Cordova and 1 using Native Android. For both it did not get the error. Could you maybe share the code that you are using to register your device ? Was this code working on previous version (like JBoss AS7) ? Thx, On Mon, Mar 10, 2014 at 11:14 AM, Matthias Wessendorf wrote: > Hello Ioannis! > > thanks for filing AEROGEAR-1455. I just did a quick check w/ a CURL based > (dummy) registration - that one worked fine. > > Are you using the native Android library for the actual registration ? Or > are you using our Cordova bits? > > Thanks! > Matthias > > > On Fri, Mar 7, 2014 at 5:53 PM, Matthias Wessendorf wrote: > >> Hello, >> >> thanks for reporting - yes a JIRA is perfect - will give it a look after >> the weekend. >> >> Greetings, >> Matthias >> >> >> On Fri, Mar 7, 2014 at 5:39 PM, JChrist wrote: >> >>> Hello everyone, >>> I have deployed the Unified push server (latest version, from master >>> branch) >>> on wildfly 8 final. Everything seems to be normal, >>> except than when an app makes a registration (an android app >>> installation), >>> there is the following exception thrown: >>> >>> WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) Failed >>> executing POST /registry/device: >>> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find >>> MessageBodyWriter for response object of type: >>> org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: >>> application/octet-stream >>> >>> Is this something known, or should I report it to JIRA? >>> Thanks! >>> >>> >>> >>> -- >>> View this message in context: >>> http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-in-Wildfly-8-final-installation-registration-issue-tp6676.html >>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20140310/d6333031/attachment-0001.html From cvasilak at gmail.com Mon Mar 10 08:59:23 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 10 Mar 2014 14:59:23 +0200 Subject: [aerogear-dev] iOS Push registration lib / iOS 7 In-Reply-To: <7162FBB3-7B45-42D9-B824-3BFF1C3572A6@gmail.com> References: <7162FBB3-7B45-42D9-B824-3BFF1C3572A6@gmail.com> Message-ID: fyi, opened https://issues.jboss.org/browse/AGPUSH-558 to track it. On Mar 10, 2014, at 2:30 PM, Corinne Krych wrote: > +1 > the less dependencies the better > Corinne > On 10 Mar 2014, at 13:22, Matthias Wessendorf wrote: > >> I am fine in getting rid of AFN here for the next release (e.g. 0.9.0 of the SDK) >> >> >> >> >> On Mon, Mar 10, 2014 at 1:08 PM, Christos Vasilakis wrote: >> Hi all, >> >> currently the push-ios registration lib relies on AFNetworking branch 1.x for its networking stack. In the process of updating to iOS 7, the plan was to update it also to use the AFNetworking 2.x series that is optimised for iOS 7. >> >> I am thinking though if it makes sense, at this point, to remove the AFNet dependency and go with just plain iOS 7 NSURLSession API for the networking. I think, It will make easier for developers to integrate it in their own projects, without having to another dependency which may or may not use as their networking stack. >> >> Wdyth? >> >> - >> Christos >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 Mon Mar 10 09:03:59 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 10 Mar 2014 14:03:59 +0100 Subject: [aerogear-dev] iOS Push registration lib / iOS 7 In-Reply-To: References: <7162FBB3-7B45-42D9-B824-3BFF1C3572A6@gmail.com> Message-ID: +1 less deps sounds like a good thing. On 10 March 2014 13:59, Christos Vasilakis wrote: > fyi, opened https://issues.jboss.org/browse/AGPUSH-558 to track it. > > > On Mar 10, 2014, at 2:30 PM, Corinne Krych wrote: > > > +1 > > the less dependencies the better > > Corinne > > On 10 Mar 2014, at 13:22, Matthias Wessendorf wrote: > > > >> I am fine in getting rid of AFN here for the next release (e.g. 0.9.0 > of the SDK) > >> > >> > >> > >> > >> On Mon, Mar 10, 2014 at 1:08 PM, Christos Vasilakis > wrote: > >> Hi all, > >> > >> currently the push-ios registration lib relies on AFNetworking branch > 1.x for its networking stack. In the process of updating to iOS 7, the plan > was to update it also to use the AFNetworking 2.x series that is optimised > for iOS 7. > >> > >> I am thinking though if it makes sense, at this point, to remove the > AFNet dependency and go with just plain iOS 7 NSURLSession API for the > networking. I think, It will make easier for developers to integrate it in > their own projects, without having to another dependency which may or may > not use as their networking stack. > >> > >> Wdyth? > >> > >> - > >> Christos > >> > >> > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.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/20140310/06f8434c/attachment.html From bruno at abstractj.org Mon Mar 10 09:41:14 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 10 Mar 2014 10:41:14 -0300 Subject: [aerogear-dev] iOS Push registration lib / iOS 7 In-Reply-To: References: Message-ID: +1 -- abstractj On March 10, 2014 at 9:08:39 AM, Christos Vasilakis (cvasilak at gmail.com) wrote: > Hi all, > > currently the push-ios registration lib relies on AFNetworking branch 1.x for its networking > stack. In the process of updating to iOS 7, the plan was to update it also to use the AFNetworking > 2.x series that is optimised for iOS 7. > > I am thinking though if it makes sense, at this point, to remove the AFNet dependency and > go with just plain iOS 7 NSURLSession API for the networking. I think, It will make easier > for developers to integrate it in their own projects, without having to another dependency > which may or may not use as their networking stack. > > Wdyth? > > - > Christos > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > From kpiwko at redhat.com Mon Mar 10 09:41:17 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Mon, 10 Mar 2014 14:41:17 +0100 Subject: [aerogear-dev] iOS Push registration lib / iOS 7 In-Reply-To: References: Message-ID: <20140310144117.067d27a3@kapy-ntb-x220> I like the change as well. Less dependencies means less things that can blow up and hence less testing. As least in the most of the cases ;-) Karel On Mon, 10 Mar 2014 14:08:24 +0200 Christos Vasilakis wrote: > Hi all, > > currently the push-ios registration lib relies on AFNetworking branch 1.x for > its networking stack. In the process of updating to iOS 7, the plan was to > update it also to use the AFNetworking 2.x series that is optimised for iOS > 7. > > I am thinking though if it makes sense, at this point, to remove the AFNet > dependency and go with just plain iOS 7 NSURLSession API for the networking. > I think, It will make easier for developers to integrate it in their own > projects, without having to another dependency which may or may not use as > their networking stack. > > Wdyth? > > - > Christos > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From bruno at abstractj.org Mon Mar 10 09:42:16 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 10 Mar 2014 10:42:16 -0300 Subject: [aerogear-dev] SimplePush Server 0.10.0 In-Reply-To: References: Message-ID: Hi Dan, when do you plan to release it? -- abstractj On March 10, 2014 at 6:34:02 AM, Daniel Bevenius (daniel.bevenius at gmail.com) wrote: > > Hi, > > we have staged AeroGear SimplePush Server 0.10.0 to Nexus: > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2791/ > > An instance if available on OpenShift: > https://sps010-dbevenius.rhcloud.com:8443/simplepush > > If you prefer to deploy to your own OpenShift account: > rhc create-app sps010 "https://cartreflect-claytondev.rhcloud.com/reflect?github=danbev/openshift-origin-cartridge-aerogear-push&commit=bfff89f3e40e62a842dbe207bdc2fa7ff4089db9" > mysql-5.1 > > This release contains the following JIRA tickets: > https://issues.jboss.org/browse/AGSMPLPUSH-48?jql=fixVersion%20%3D%20%220.10.0%22%20AND%20project%20%3D%20AGSMPLPUSH > > Please take it for a spin and let us know if you have any issues. From scm.blanc at gmail.com Mon Mar 10 10:16:51 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 10 Mar 2014 15:16:51 +0100 Subject: [aerogear-dev] Team meeting agenda In-Reply-To: References: Message-ID: Here we go ! (03:16:25 PM) jbott: Meeting ended Mon Mar 10 14:04:02 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) (03:16:25 PM) jbott: Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-10-13.51.html (03:16:25 PM) jbott: Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-10-13.51.txt (03:16:25 PM) jbott: Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-10-13.51.log.html On Mon, Mar 10, 2014 at 1:12 AM, Daniel Passos wrote: > http://oksoclap.com/p/aerogear-team-mgt-20140310 > > _______________________________________________ > 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/20140310/e86e4f5d/attachment.html From smikloso at redhat.com Mon Mar 10 10:53:49 2014 From: smikloso at redhat.com (Stefan Miklosovic) Date: Mon, 10 Mar 2014 10:53:49 -0400 (EDT) Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: <1394247994174.a05c8174@Nodemailer> References: <1394247994174.a05c8174@Nodemailer> Message-ID: <1389062401.8617179.1394463229081.JavaMail.zimbra@redhat.com> Hi, so whats the "conclusion" for this? I would like to move forward with other things. Is JIRA to track this sufficient? Stefan Miklosovic Red Hat Brno - JBoss Mobile Platform e-mail: smikloso at redhat.com irc: smikloso ----- Original Message ----- > IMO it should be supported on client/server side. This is exactly what I've > been developing for mobile applications to establish a trustworthy > relationship. I prefer self signed certificates, instead of trust on any CA > ? > abstractj > On Fri, Mar 7, 2014 at 4:30 PM, tolis emmanouilidis < tolisemm at gmail.com > > wrote: > > 2014-03-07 18:21 GMT+02:00 Matthias Wessendorf < matzew at apache.org > : > > > > On Fri, Mar 7, 2014 at 5:11 PM, Stefan Miklosovic < smikloso at redhat.com > > > > wrote: > > > > > > > Hi, > > > > > > > > > > we are doing HTTPS tests on UPS integration tests where UPS Java client > > > > is > > > > used to send some payload to UPS, it seems it is not sufficient to have > > > > only > > > > plain HTTP sender when we are sending it to HTTPS endpoint. > > > > > > > > > > When JBoss AS is set up with keystore and truststore in https connector > > > > for > > > > web subsystem like this: > > > > > > > > > > > > > socket-binding="https" secure="true"> > > > > > > > > > > > > > > > > > > > password="aerogear" > > > > > > > > > > certificate-key-file="${jboss.server.config.dir}/aerogear.keystore" > > > > > > > > > > protocol="ALL" > > > > > > > > > > verify-client="none" > > > > > > > > > > certificate-file="${jboss.server.config.dir}/aerogear.keystore" > > > > > > > > > > ca-certificate-file="${jboss.server.config.dir}/aerogear.truststore"/> > > > > > > > > > > > > > > > > > > > > and UPS Java client sends some payload (with HttpUrlConnection, not > > > > secure > > > > connection), this exception is thown from it: > > > > > > > > > I guess we can use, for https, the HttpsUrlConnection - that;s what you > > > are > > > basically asking, right ? > > > > > > Mind to create PR for that ? > > > > > > Thanks! > > > > > > Matthias > > > > > T he certificate used in UPS integration tests is self signed. The SSL > > handshake, most probably will fail even when using HttpsUrlConnection, if > > the custom truststore is not set. I believe that the existing UPS sender > > version will work when a real, valid certificate is used instead of a self > > signed one. > > > This issue could be fixed if UPS sender was providing a functionality to > > set > > up and use a custom TrustManager which contains the Keystore with the self > > signed certificate. In my opinion, the question is whether supporting self > > signed certificates in UPS sender, brings value. > > > Thanks, > > > Tolis > > > > > SEVERE: Send did not succeed: > > > > sun.security.validator.ValidatorException: > > > > PKIX > > > > path building failed: > > > > sun.security.provider.certpath.SunCertPathBuilderException: unable to > > > > find > > > > valid certification path to requested target > > > > > > > > > > This basically means that server was not able to mark that connection > > > > as > > > > trusted. > > > > > > > > > > In order to use custom trustStore and trustStorePassword, they are > > > > propagated > > > > to test like system properties > > > > > > > > > > System.setProperty("javax.net.ssl.trustStore", "aerogear.truststore"); > > > > > > > > > > System.setProperty("javax.net.ssl.trustStorePassword", "aerogear"); > > > > > > > > > > however any attempt to set them in test itself like that is not > > > > successful > > > > since it is "too late". When they are set like -D properties with > > > > maven, > > > > it > > > > is executed without any problems. > > > > > > > > > > This does not work as well > > > > https://github.com/aerogear/aerogear-unifiedpush-java-client#known-issues > > > > since we are not using jsse (and can not) because of this issue > > > > https://issues.jboss.org/browse/JBPAPP6-711 which was repaired in 7.1.2 > > > > and > > > > that release is not community release anymore so we can not base tests > > > > on > > > > EAP and we are running them on 7.1.1. (we can not run them on WF as > > > > well > > > > since it is not compatible with EAP but 7.1.1 is). > > > > > > > > > > So this is chicken-egg problem. When verify-client is "none" plain http > > > > from > > > > UPS Java client is not validated. When we do want client authentication > > > > (verify-client=want/true), UPS sender is not https aware. Additionally, > > > > we > > > > can not use "jsse" due to JBPAPP6-711. > > > > > > > > > > Ideas? > > > > > > > > > > Stefan Miklosovic > > > > > > > > > > Red Hat Brno - JBoss Mobile Platform > > > > > > > > > > e-mail: smikloso at redhat.com > > > > > > > > > > irc: smikloso > > > > > > > > > > _______________________________________________ > > > > > > > > > > aerogear-dev mailing list > > > > > > > > > > aerogear-dev at lists.jboss.org > > > > > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > -- > > > > > > Matthias Wessendorf > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > > sessions: http://www.slideshare.net/mwessendorf > > > > > > twitter: http://twitter.com/mwessendorf > > > > > > _______________________________________________ > > > > > > aerogear-dev mailing list > > > > > > aerogear-dev at lists.jboss.org > > > > > > https://lists.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/20140310/b3d40ae5/attachment-0001.html From edewit at redhat.com Mon Mar 10 11:43:03 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 10 Mar 2014 16:43:03 +0100 Subject: [aerogear-dev] security updates Message-ID: Hi, Bruno has created some PR?s to update our cordova plugins to no longer support 3.0.0 but update it to 3.4.0, because of a number of security issues that have been solved. Now of course we should encourage that people use the latest version, but this PR enforces it. Also Gorkem that invested quite some time to support different versions. So what should we pick enforce or encourage? Cheers, Erik Jan From matzew at apache.org Mon Mar 10 11:47:28 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 10 Mar 2014 16:47:28 +0100 Subject: [aerogear-dev] security updates In-Reply-To: References: Message-ID: for reference, here is the related doc on the Cordova update: http://cordova.apache.org/announcements/2014/02/20/cordova-340.html ("Removing addJavascriptInterface support from all Android versions lower than 4.2 due to security vulnerability") On Mon, Mar 10, 2014 at 4:43 PM, Erik Jan de Wit wrote: > Hi, > > Bruno has created some PR's to update our cordova plugins to no longer > support 3.0.0 but update it to 3.4.0, because of a number of security > issues that have been solved. Now of course we should encourage that people > use the latest version, but this PR enforces it. Also Gorkem that invested > quite some time to support different versions. So what should we pick > enforce or encourage? > > 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/20140310/b616eeea/attachment.html From io.christod at gmail.com Mon Mar 10 12:10:49 2014 From: io.christod at gmail.com (Ioannis Christodoulou) Date: Mon, 10 Mar 2014 18:10:49 +0200 Subject: [aerogear-dev] Unified Push Server in Wildfly 8 final installation registration issue In-Reply-To: References: <1394210347601-6676.post@n5.nabble.com> Message-ID: Hello! I've not tested JBoss AS7, I will try and report back. I did not use either cordova or native android but I created an http request using the android http client (and chrome's postman to replicate the issue). The request I created using Postman in Google Chrome is shown in the attached screenshot: [image: Inline image 1] the full exception stack trace from wildfly is: 18:03:45,295 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-9) Failed executing POST /registry/device: org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: application/octet-stream at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:67) [resteasy-jaxrs-3.0.6.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:427) [resteasy-jaxrs-3.0.6.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:376) [resteasy-jaxrs-3.0.6.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.6.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.6.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.6.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.6.Final.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] Thanks! On Mon, Mar 10, 2014 at 2:34 PM, Sebastien Blanc wrote: > Hi ! > I've done some testing and deployed a UPS on OpenShift using the Wildfly > cartdridge : http://wildflyups-sblanc.rhcloud.com (admin / aerogear) > I tested 2 android apps : 1 using Cordova and 1 using Native Android. > For both it did not get the error. > > Could you maybe share the code that you are using to register your device ? > Was this code working on previous version (like JBoss AS7) ? > > Thx, > > > > On Mon, Mar 10, 2014 at 11:14 AM, Matthias Wessendorf wrote: > >> Hello Ioannis! >> >> thanks for filing AEROGEAR-1455. I just did a quick check w/ a CURL based >> (dummy) registration - that one worked fine. >> >> Are you using the native Android library for the actual registration ? Or >> are you using our Cordova bits? >> >> Thanks! >> Matthias >> >> >> On Fri, Mar 7, 2014 at 5:53 PM, Matthias Wessendorf wrote: >> >>> Hello, >>> >>> thanks for reporting - yes a JIRA is perfect - will give it a look after >>> the weekend. >>> >>> Greetings, >>> Matthias >>> >>> >>> On Fri, Mar 7, 2014 at 5:39 PM, JChrist wrote: >>> >>>> Hello everyone, >>>> I have deployed the Unified push server (latest version, from master >>>> branch) >>>> on wildfly 8 final. Everything seems to be normal, >>>> except than when an app makes a registration (an android app >>>> installation), >>>> there is the following exception thrown: >>>> >>>> WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) Failed >>>> executing POST /registry/device: >>>> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find >>>> MessageBodyWriter for response object of type: >>>> org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: >>>> application/octet-stream >>>> >>>> Is this something known, or should I report it to JIRA? >>>> Thanks! >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-in-Wildfly-8-final-installation-registration-issue-tp6676.html >>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/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/20140310/5ddc2802/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ss.png Type: image/png Size: 62343 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140310/5ddc2802/attachment-0001.png From matzew at apache.org Mon Mar 10 12:24:10 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 10 Mar 2014 17:24:10 +0100 Subject: [aerogear-dev] Unified Push Server in Wildfly 8 final installation registration issue In-Reply-To: References: <1394210347601-6676.post@n5.nabble.com> Message-ID: application/octet-stream.. hrm that's def. something w/ your request. Can you make sure the following headers are on the request? -H "Accept: application/json" -H "Content-type: application/json" Thanks! Matthias On Mon, Mar 10, 2014 at 5:10 PM, Ioannis Christodoulou < io.christod at gmail.com> wrote: > Hello! > I've not tested JBoss AS7, I will try and report back. > > I did not use either cordova or native android but I created an http > request using the android http client (and chrome's postman to replicate > the issue). > The request I created using Postman in Google Chrome is shown in the > attached screenshot: > [image: Inline image 1] > the full exception stack trace from wildfly is: > [0m [33m18:03:45,295 WARN [org.jboss.resteasy.core.ExceptionHandler] > (default task-9) Failed executing POST /registry/device: > org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find > MessageBodyWriter for response object of type: > org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: > application/octet-stream > at > org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:67) > [resteasy-jaxrs-3.0.6.Final.jar:] > at > org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:427) > [resteasy-jaxrs-3.0.6.Final.jar:] > at > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:376) > [resteasy-jaxrs-3.0.6.Final.jar:] > at > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) > [resteasy-jaxrs-3.0.6.Final.jar:] > at > org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) > [resteasy-jaxrs-3.0.6.Final.jar:] > at > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > [resteasy-jaxrs-3.0.6.Final.jar:] > at > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > [resteasy-jaxrs-3.0.6.Final.jar:] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at > org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) > [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) > [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at > org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) > [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) > [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) > [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at > io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) > [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > [rt.jar:1.7.0_51] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > > Thanks! > > On Mon, Mar 10, 2014 at 2:34 PM, Sebastien Blanc wrote: > >> Hi ! >> I've done some testing and deployed a UPS on OpenShift using the Wildfly >> cartdridge : http://wildflyups-sblanc.rhcloud.com (admin / aerogear) >> I tested 2 android apps : 1 using Cordova and 1 using Native Android. >> For both it did not get the error. >> >> Could you maybe share the code that you are using to register your device >> ? >> Was this code working on previous version (like JBoss AS7) ? >> >> Thx, >> >> >> >> On Mon, Mar 10, 2014 at 11:14 AM, Matthias Wessendorf wrote: >> >>> Hello Ioannis! >>> >>> thanks for filing AEROGEAR-1455. I just did a quick check w/ a CURL >>> based (dummy) registration - that one worked fine. >>> >>> Are you using the native Android library for the actual registration ? >>> Or are you using our Cordova bits? >>> >>> Thanks! >>> Matthias >>> >>> >>> On Fri, Mar 7, 2014 at 5:53 PM, Matthias Wessendorf wrote: >>> >>>> Hello, >>>> >>>> thanks for reporting - yes a JIRA is perfect - will give it a look >>>> after the weekend. >>>> >>>> Greetings, >>>> Matthias >>>> >>>> >>>> On Fri, Mar 7, 2014 at 5:39 PM, JChrist wrote: >>>> >>>>> Hello everyone, >>>>> I have deployed the Unified push server (latest version, from master >>>>> branch) >>>>> on wildfly 8 final. Everything seems to be normal, >>>>> except than when an app makes a registration (an android app >>>>> installation), >>>>> there is the following exception thrown: >>>>> >>>>> WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) >>>>> Failed >>>>> executing POST /registry/device: >>>>> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find >>>>> MessageBodyWriter for response object of type: >>>>> org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: >>>>> application/octet-stream >>>>> >>>>> Is this something known, or should I report it to JIRA? >>>>> Thanks! >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-in-Wildfly-8-final-installation-registration-issue-tp6676.html >>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/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/20140310/06b40e0f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ss.png Type: image/png Size: 62343 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140310/06b40e0f/attachment-0001.png From io.christod at gmail.com Mon Mar 10 12:27:32 2014 From: io.christod at gmail.com (Ioannis Christodoulou) Date: Mon, 10 Mar 2014 18:27:32 +0200 Subject: [aerogear-dev] Unified Push Server in Wildfly 8 final installation registration issue In-Reply-To: References: <1394210347601-6676.post@n5.nabble.com> Message-ID: Wow, that was it, my request was missing the "Accept: application/json" header. thanks a lot guys! ????????? ????, ??????? ???????????? On Mon, Mar 10, 2014 at 6:24 PM, Matthias Wessendorf wrote: > application/octet-stream.. hrm > > > that's def. something w/ your request. > > Can you make sure the following headers are on the request? > > -H "Accept: application/json" > -H "Content-type: application/json" > > Thanks! > Matthias > > > > On Mon, Mar 10, 2014 at 5:10 PM, Ioannis Christodoulou < > io.christod at gmail.com> wrote: > >> Hello! >> I've not tested JBoss AS7, I will try and report back. >> >> I did not use either cordova or native android but I created an http >> request using the android http client (and chrome's postman to replicate >> the issue). >> The request I created using Postman in Google Chrome is shown in the >> attached screenshot: >> [image: Inline image 1] >> the full exception stack trace from wildfly is: >> [0m [33m18:03:45,295 WARN [org.jboss.resteasy.core.ExceptionHandler] >> (default task-9) Failed executing POST /registry/device: >> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find >> MessageBodyWriter for response object of type: >> org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: >> application/octet-stream >> at >> org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:67) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> at >> org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:427) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> at >> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:376) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> at >> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> at >> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> at >> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> at >> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) >> [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) >> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) >> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) >> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) >> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >> at >> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) >> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) >> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) >> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) >> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >> at >> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) >> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> [rt.jar:1.7.0_51] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> [rt.jar:1.7.0_51] >> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] >> >> Thanks! >> >> On Mon, Mar 10, 2014 at 2:34 PM, Sebastien Blanc wrote: >> >>> Hi ! >>> I've done some testing and deployed a UPS on OpenShift using the Wildfly >>> cartdridge : http://wildflyups-sblanc.rhcloud.com (admin / aerogear) >>> I tested 2 android apps : 1 using Cordova and 1 using Native Android. >>> For both it did not get the error. >>> >>> Could you maybe share the code that you are using to register your >>> device ? >>> Was this code working on previous version (like JBoss AS7) ? >>> >>> Thx, >>> >>> >>> >>> On Mon, Mar 10, 2014 at 11:14 AM, Matthias Wessendorf >> > wrote: >>> >>>> Hello Ioannis! >>>> >>>> thanks for filing AEROGEAR-1455. I just did a quick check w/ a CURL >>>> based (dummy) registration - that one worked fine. >>>> >>>> Are you using the native Android library for the actual registration ? >>>> Or are you using our Cordova bits? >>>> >>>> Thanks! >>>> Matthias >>>> >>>> >>>> On Fri, Mar 7, 2014 at 5:53 PM, Matthias Wessendorf wrote: >>>> >>>>> Hello, >>>>> >>>>> thanks for reporting - yes a JIRA is perfect - will give it a look >>>>> after the weekend. >>>>> >>>>> Greetings, >>>>> Matthias >>>>> >>>>> >>>>> On Fri, Mar 7, 2014 at 5:39 PM, JChrist wrote: >>>>> >>>>>> Hello everyone, >>>>>> I have deployed the Unified push server (latest version, from master >>>>>> branch) >>>>>> on wildfly 8 final. Everything seems to be normal, >>>>>> except than when an app makes a registration (an android app >>>>>> installation), >>>>>> there is the following exception thrown: >>>>>> >>>>>> WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) >>>>>> Failed >>>>>> executing POST /registry/device: >>>>>> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not >>>>>> find >>>>>> MessageBodyWriter for response object of type: >>>>>> org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: >>>>>> application/octet-stream >>>>>> >>>>>> Is this something known, or should I report it to JIRA? >>>>>> Thanks! >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-in-Wildfly-8-final-installation-registration-issue-tp6676.html >>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/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/20140310/d9128cd5/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ss.png Type: image/png Size: 62343 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140310/d9128cd5/attachment-0001.png From marceloheck at gmail.com Mon Mar 10 12:09:03 2014 From: marceloheck at gmail.com (marceloheck) Date: Mon, 10 Mar 2014 09:09:03 -0700 (PDT) Subject: [aerogear-dev] aerogear security and android Message-ID: <1394467743631-6703.post@n5.nabble.com> Hello I search a sample with aerogear and security server in client private AuthenticationModule authModule; private String baseURL = "http://localhost:8080/servicos/service/auth"; private TextView status; private Button login; private Button logout; private static final String LOG_TAG = login.class.getName(); @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); Authenticator authenticator = new Authenticator(baseURL); AuthenticationConfig authenticationConfig = new AuthenticationConfig(); // authenticationConfig.setAuthType(AuthTypes.HTTP_BASIC); authenticationConfig.setLoginEndpoint("/login"); authenticationConfig.setLogoutEndpoint("/logout"); authModule = authenticator.auth("login", authenticationConfig); status = (TextView) findViewById(R.id.editText1); login = (Button) findViewById(R.id.button1); logout = (Button) findViewById(R.id.Button01); button = (Button) findViewById(R.id.button1); /* // Capture button clicks button.setOnClickListener(new OnClickListener() { public void onClick(View arg0) { // Start NewActivity.class Intent myIntent = new Intent(MainActivity.this, login.class); startActivity(myIntent); } });*/ login.setOnClickListener(new View.OnClickListener() { @Override public void onClick(View view) { authModule.login("nome", "senha", new AbstractActivityCallback() { @Override public void onSuccess(HeaderAndBody data) { Log.d(LOG_TAG, "Received ID: " + data.toString() ); logged(true); // Start NewActivity.class Intent myIntent = new Intent(MainActivity.this, br.gov.pr.dc.sisdc.activities.MapActivity.class); startActivity(myIntent); // Toast.makeText(getActivity(), "logado", Toast.LENGTH_SHORT).show(); } @Override public void onFailure(Exception e) { displayError(e.getMessage()); // Toast.makeText(getActivity(), "erro", Toast.LENGTH_SHORT).show(); Log.d(LOG_TAG, "error: " + e ); Intent myIntent = new Intent(MainActivity.this, br.gov.pr.dc.sisdc.activities.MapActivity.class); startActivity(myIntent); } }); } }); is ok but how to use the rest in android is authenticate and authorize cripty token push etc... in other REST service? is session? is value how? ... URL BASE_URL = new URL("http://localhost:8080/servicos/service/"); PageConfig pageConfig = new PageConfig(); pageConfig.setLimitValue(5); pageConfig.setMetadataLocation(PageConfig.MetadataLocations.WEB_LINKING); PipeConfig pipeConfig = new PipeConfig(BASE_URL, AbrigoVO.class); pipeConfig.setEndpoint("pessoa"); pipeConfig.setPageConfig(pageConfig); pipeline = new Pipeline(BASE_URL); pipeline.pipe(pessoaVO.class, pipeConfig); LoaderPipe pipes = pipeline.get("pessoavo", mContext); //LoaderPipe pipes = this.pipeline.get("pessoavo", fragment, mContext); //TODO https://github.com/aerogear/aerogear-aerodoc-android/blob/master/src/org/jboss/aerogear/android/unifiedpush/aerodoc/fragments/AeroDocLeadsAvailableFragments.java pipes.read(readCallback); Log.d(LOG_TAG, "Received ID: " ); return null; } catch (Exception e) { // TODO Need error handling Log.e(LOG_TAG, e.getLocalizedMessage(), e); Log.e(LOG_TAG, "sem servi?o", e); e.printStackTrace(); return null; } ... and security server jboss 7 ?? @Path("/pessoa/") public interface pessoaResource { @Produces(MediaType.APPLICATION_JSON) public Response listar(); @GET @Path("/{codigo}") @Produces(MediaType.APPLICATION_JSON) public Response obter(@PathParam("codigo") Long idpessoa); } i add @Inject private IdentityManagement configuration; @Inject private AuthenticationManager authenticationManager; and org.jboss.aerogear.security.interceptor.SecurityInterceptor and @Secure("admin") but error injection WELD-001408 Unsatisfied dependencies for type [EntityManager] with qualifiers [@Default] at injection point [[field] @Inject private org.jboss.aerogear.security.shiro.authz.GrantConfiguration.entityManager] examples JaxRS and shiro and demo not funcional of soluction server and client android i connect database login password e groups for login how to keep the connected User? have database or saved in the session? can someone give me a practical example for using rest client server? -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-security-and-android-tp6703.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Mon Mar 10 12:35:48 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 10 Mar 2014 17:35:48 +0100 Subject: [aerogear-dev] Unified Push Server in Wildfly 8 final installation registration issue In-Reply-To: References: <1394210347601-6676.post@n5.nabble.com> Message-ID: perfect! On Mon, Mar 10, 2014 at 5:27 PM, Ioannis Christodoulou < io.christod at gmail.com> wrote: > Wow, that was it, my request was missing the "Accept: application/json" > header. > thanks a lot guys! > > ????????? ????, > ??????? ???????????? > > > On Mon, Mar 10, 2014 at 6:24 PM, Matthias Wessendorf wrote: > >> application/octet-stream.. hrm >> >> >> that's def. something w/ your request. >> >> Can you make sure the following headers are on the request? >> >> -H "Accept: application/json" >> -H "Content-type: application/json" >> >> Thanks! >> Matthias >> >> >> >> On Mon, Mar 10, 2014 at 5:10 PM, Ioannis Christodoulou < >> io.christod at gmail.com> wrote: >> >>> Hello! >>> I've not tested JBoss AS7, I will try and report back. >>> >>> I did not use either cordova or native android but I created an http >>> request using the android http client (and chrome's postman to replicate >>> the issue). >>> The request I created using Postman in Google Chrome is shown in the >>> attached screenshot: >>> [image: Inline image 1] >>> the full exception stack trace from wildfly is: >>> [0m [33m18:03:45,295 WARN [org.jboss.resteasy.core.ExceptionHandler] >>> (default task-9) Failed executing POST /registry/device: >>> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find >>> MessageBodyWriter for response object of type: >>> org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: >>> application/octet-stream >>> at >>> org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:67) >>> [resteasy-jaxrs-3.0.6.Final.jar:] >>> at >>> org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:427) >>> [resteasy-jaxrs-3.0.6.Final.jar:] >>> at >>> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:376) >>> [resteasy-jaxrs-3.0.6.Final.jar:] >>> at >>> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) >>> [resteasy-jaxrs-3.0.6.Final.jar:] >>> at >>> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) >>> [resteasy-jaxrs-3.0.6.Final.jar:] >>> at >>> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) >>> [resteasy-jaxrs-3.0.6.Final.jar:] >>> at >>> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) >>> [resteasy-jaxrs-3.0.6.Final.jar:] >>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) >>> [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) >>> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) >>> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) >>> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) >>> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >>> at >>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) >>> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) >>> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) >>> [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) >>> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >>> at >>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) >>> [undertow-core-1.0.0.Final.jar:1.0.0.Final] >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>> [rt.jar:1.7.0_51] >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>> [rt.jar:1.7.0_51] >>> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] >>> >>> Thanks! >>> >>> On Mon, Mar 10, 2014 at 2:34 PM, Sebastien Blanc wrote: >>> >>>> Hi ! >>>> I've done some testing and deployed a UPS on OpenShift using the >>>> Wildfly cartdridge : http://wildflyups-sblanc.rhcloud.com (admin / >>>> aerogear) >>>> I tested 2 android apps : 1 using Cordova and 1 using Native Android. >>>> For both it did not get the error. >>>> >>>> Could you maybe share the code that you are using to register your >>>> device ? >>>> Was this code working on previous version (like JBoss AS7) ? >>>> >>>> Thx, >>>> >>>> >>>> >>>> On Mon, Mar 10, 2014 at 11:14 AM, Matthias Wessendorf < >>>> matzew at apache.org> wrote: >>>> >>>>> Hello Ioannis! >>>>> >>>>> thanks for filing AEROGEAR-1455. I just did a quick check w/ a CURL >>>>> based (dummy) registration - that one worked fine. >>>>> >>>>> Are you using the native Android library for the actual registration ? >>>>> Or are you using our Cordova bits? >>>>> >>>>> Thanks! >>>>> Matthias >>>>> >>>>> >>>>> On Fri, Mar 7, 2014 at 5:53 PM, Matthias Wessendorf >>>> > wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> thanks for reporting - yes a JIRA is perfect - will give it a look >>>>>> after the weekend. >>>>>> >>>>>> Greetings, >>>>>> Matthias >>>>>> >>>>>> >>>>>> On Fri, Mar 7, 2014 at 5:39 PM, JChrist wrote: >>>>>> >>>>>>> Hello everyone, >>>>>>> I have deployed the Unified push server (latest version, from master >>>>>>> branch) >>>>>>> on wildfly 8 final. Everything seems to be normal, >>>>>>> except than when an app makes a registration (an android app >>>>>>> installation), >>>>>>> there is the following exception thrown: >>>>>>> >>>>>>> WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-3) >>>>>>> Failed >>>>>>> executing POST /registry/device: >>>>>>> org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not >>>>>>> find >>>>>>> MessageBodyWriter for response object of type: >>>>>>> org.jboss.aerogear.unifiedpush.model.InstallationImpl of media type: >>>>>>> application/octet-stream >>>>>>> >>>>>>> Is this something known, or should I report it to JIRA? >>>>>>> Thanks! >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> View this message in context: >>>>>>> http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-in-Wildfly-8-final-installation-registration-issue-tp6676.html >>>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/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/20140310/5240b68b/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: ss.png Type: image/png Size: 62343 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140310/5240b68b/attachment-0001.png From bruno at abstractj.org Mon Mar 10 13:44:15 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 10 Mar 2014 14:44:15 -0300 Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: <1389062401.8617179.1394463229081.JavaMail.zimbra@redhat.com> References: <1394247994174.a05c8174@Nodemailer> <1389062401.8617179.1394463229081.JavaMail.zimbra@redhat.com> Message-ID: JIRA is enough as far as I can tell. -- abstractj On March 10, 2014 at 11:53:53 AM, Stefan Miklosovic (smikloso at redhat.com) wrote: > > Hi, > > so whats the "conclusion" for this? I would like to move forward > with other things. Is JIRA to track this sufficient? > > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform From matzew at apache.org Mon Mar 10 14:50:34 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 10 Mar 2014 19:50:34 +0100 Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: References: <1394247994174.a05c8174@Nodemailer> <1389062401.8617179.1394463229081.JavaMail.zimbra@redhat.com> Message-ID: On Monday, March 10, 2014, Bruno Oliveira wrote: > JIRA is enough as far as I can tell. +1 on JIRA for tracking feel free to send PR as well Greetings, Matthias > > -- > abstractj > > On March 10, 2014 at 11:53:53 AM, Stefan Miklosovic (smikloso at redhat.com) > wrote: > > > Hi, > > > > so whats the "conclusion" for this? I would like to move forward > > with other things. Is JIRA to track this sufficient? > > > > Stefan Miklosovic > > Red Hat Brno - JBoss Mobile Platform > > _______________________________________________ > 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/20140310/e7ea07a4/attachment.html From abstractj at redhat.com Mon Mar 10 16:49:15 2014 From: abstractj at redhat.com (Bruno Oliveira) Date: Mon, 10 Mar 2014 17:49:15 -0300 Subject: [aerogear-dev] iOS Passphrases for UPS Message-ID: Good morning guys, for this issue?https://issues.jboss.org/browse/AGPUSH-358. I was revisiting the whole UPS code and thinking about include two fields for iOSVariant class: skey (secret key) and pKey (public key). What?s the idea? 1. Each application has its own key pair 2. Before the addition of the iOS variant, the client sends a request asking for the public keys 3. The server sends an HTTP response with the public key for encryption 4. The client make use of the public key to encrypt the certificate + the passphrase 5. Server stores it encrypted 6. When necessary to send push messages, the server make use of the private key to decrypt that data and send fancy messages. Does it make sense to you? -- abstractj JBoss, a division of Red Hat From matzew at apache.org Mon Mar 10 17:01:24 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 10 Mar 2014 22:01:24 +0100 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: Ahoy! On Mon, Mar 10, 2014 at 9:49 PM, Bruno Oliveira wrote: > Good morning guys, for this issue > https://issues.jboss.org/browse/AGPUSH-358. I was revisiting the whole > UPS code and thinking about include two fields for iOSVariant class: skey > (secret key) and pKey (public key). What's the idea? > > 1. Each application has its own key pair > each of the PushApplication constructs/objects on the UPS ? > 2. Before the addition of the iOS variant, the client sends a request > asking for the public keys > "the client" ? Is that the AdminUI (or the relevant HTTP Rest code), when someone clicks "Add new Variant" ? > 3. The server sends an HTTP response with the public key for encryption > 4. The client make use of the public key to encrypt the certificate + the > passphrase > 5. Server stores it encrypted > 6. When necessary to send push messages, the server make use of the > private key to decrypt that data and send fancy messages. > Now, when a (JavaEE) application is sending a request for push messages to the UPS (which than internally makes use of the private key to decrypt that data and send fancy messages to Apple), the HTTP RestEndpoint requires a new argument (the public key) to be allowed to submit these "requests" ? > > Does it make sense to you? > Somewhat - not sure I fully understood :) > > -- > abstractj > > JBoss, a division of Red Hat > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140310/e30bffa3/attachment.html From scm.blanc at gmail.com Mon Mar 10 17:12:39 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 10 Mar 2014 22:12:39 +0100 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: Let me try to answer your questions so I can see if I have understand it well and then Abstractj can confirm (or not ) :) On Mon, Mar 10, 2014 at 10:01 PM, Matthias Wessendorf wrote: > Ahoy! > > > On Mon, Mar 10, 2014 at 9:49 PM, Bruno Oliveira wrote: > >> Good morning guys, for this issue >> https://issues.jboss.org/browse/AGPUSH-358. I was revisiting the whole >> UPS code and thinking about include two fields for iOSVariant class: skey >> (secret key) and pKey (public key). What's the idea? >> >> 1. Each application has its own key pair >> > > each of the PushApplication constructs/objects on the UPS ? > Yes, What I understand : each PushAPP has his own pair > > >> 2. Before the addition of the iOS variant, the client sends a request >> asking for the public keys >> > > "the client" ? Is that the AdminUI (or the relevant HTTP Rest code), when > someone clicks "Add new Variant" ? > I understand the AdminUI/Rest Service. And this mean there will be an extra REST service to retrieve the public key. Idea : maybe the public key could be already in the response of the GET of the "Parent" PushApplication. > > > >> 3. The server sends an HTTP response with the public key for encryption >> 4. The client make use of the public key to encrypt the certificate + the >> passphrase >> 5. Server stores it encrypted >> 6. When necessary to send push messages, the server make use of the >> private key to decrypt that data and send fancy messages. >> > > Now, when a (JavaEE) application is sending a request for push messages to > the UPS (which than internally makes use of the private key to decrypt that > data and send fancy messages to Apple), the HTTP RestEndpoint requires a > new argument (the public key) to be allowed to submit these "requests" ? > I don't think so since it will use only the private key to decrypt, so the API stays unchanged. > > >> >> Does it make sense to you? >> > > Somewhat - not sure I fully understood :) > > >> >> -- >> abstractj >> >> JBoss, a division of Red Hat >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140310/fff2c588/attachment.html From bruno at abstractj.org Mon Mar 10 18:38:30 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 10 Mar 2014 19:38:30 -0300 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: Ahoy, answers inline. -- abstractj On March 10, 2014 at 6:01:33 PM, Matthias Wessendorf (matzew at apache.org) wrote: > Ahoy! > > > On Mon, Mar 10, 2014 at 9:49 PM, Bruno Oliveira wrote: > > > Good morning guys, for this issue > > https://issues.jboss.org/browse/AGPUSH-358. I was revisiting the whole > > UPS code and thinking about include two fields for iOSVariant class: skey > > (secret key) and pKey (public key). What's the idea? > > > > 1. Each application has its own key pair > > > > each of the PushApplication constructs/objects on the UPS ? Yes if that makes sense to the others like Android variants. And no if we just want to use it with iOSVariant, into this case that would apply only for iOS applications. > > > > 2. Before the addition of the iOS variant, the client sends a request > > asking for the public keys > > > > "the client" ? Is that the AdminUI (or the relevant HTTP Rest code), when > someone clicks "Add new Variant? ? Whatever REST consumer we have or the service. > > > > > 3. The server sends an HTTP response with the public key for encryption > > 4. The client make use of the public key to encrypt the certificate + the > > passphrase > > 5. Server stores it encrypted > > 6. When necessary to send push messages, the server make use of the > > private key to decrypt that data and send fancy messages. > > > > Now, when a (JavaEE) application is sending a request for push messages to > the UPS (which than internally makes use of the private key to decrypt that > data and send fancy messages to Apple), the HTTP RestEndpoint requires a > new argument (the public key) to be allowed to submit these "requests? ? On the client side, after the public key retrieval you don?t need to add new parameters. As Sebastien mentioned it would remain unchanged. Currently: curl -3 -v -b cookies.txt -c cookies.txt ? -i -H "Accept: application/json" -H "Content-type: multipart/form-data" ? -F "certificate=@/Users/matzew/Desktop/MyProdCert.p12" ? -F "passphrase=TopSecret" ? -F "production=true" ?// make sure you have Production certificate and Provisioning Profile ? -X POST https://SERVER:PORT/CONTEXT/rest/applications/{pushApplicationID}/iOS Proposed: curl -3 -v -b cookies.txt -c cookies.txt ? -i -H "Accept: application/json" -H "Content-type: multipart/form-data" ? -F "certificate=@/Users/matzew/Desktop/encrypted-cert.blah" ? -F ?passphrase=schwarzenegger" ? -F "production=true" ?// make sure you have Production certificate and Provisioning Profile ? -X POST https://SERVER:PORT/CONTEXT/rest/applications/{pushApplicationID}/iOS Where encrypted-cert.blah and ?Schwarzenegger? are encrypted data. Makes sense? > > > > > > Does it make sense to you? > > > > Somewhat - not sure I fully understood :) > > > > > > -- > > abstractj > > > > JBoss, a division of Red Hat > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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 bruno at abstractj.org Mon Mar 10 18:39:30 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 10 Mar 2014 19:39:30 -0300 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: Nailed it, Sebastien. -- abstractj On March 10, 2014 at 6:12:46 PM, Sebastien Blanc (scm.blanc at gmail.com) wrote: > Let me try to answer your questions so I can see if I have understand it > well and then Abstractj can confirm (or not ) :) > > > On Mon, Mar 10, 2014 at 10:01 PM, Matthias Wessendorf wrote: > > > Ahoy! > > > > > > On Mon, Mar 10, 2014 at 9:49 PM, Bruno Oliveira wrote: > > > >> Good morning guys, for this issue > >> https://issues.jboss.org/browse/AGPUSH-358. I was revisiting the whole > >> UPS code and thinking about include two fields for iOSVariant class: skey > >> (secret key) and pKey (public key). What's the idea? > >> > >> 1. Each application has its own key pair > >> > > > > each of the PushApplication constructs/objects on the UPS ? > > > Yes, What I understand : each PushAPP has his own pair > > > > > > >> 2. Before the addition of the iOS variant, the client sends a request > >> asking for the public keys > >> > > > > "the client" ? Is that the AdminUI (or the relevant HTTP Rest code), when > > someone clicks "Add new Variant" ? > > > I understand the AdminUI/Rest Service. And this mean there will be an extra > REST service to retrieve the public key. Idea : maybe the public key could > be already in the response of the GET of the "Parent" PushApplication. > > > > > > > > >> 3. The server sends an HTTP response with the public key for encryption > >> 4. The client make use of the public key to encrypt the certificate + the > >> passphrase > >> 5. Server stores it encrypted > >> 6. When necessary to send push messages, the server make use of the > >> private key to decrypt that data and send fancy messages. > >> > > > > Now, when a (JavaEE) application is sending a request for push messages to > > the UPS (which than internally makes use of the private key to decrypt that > > data and send fancy messages to Apple), the HTTP RestEndpoint requires a > > new argument (the public key) to be allowed to submit these "requests" ? > > > I don't think so since it will use only the private key to decrypt, so the > API stays unchanged. > > > > > > >> > >> Does it make sense to you? > >> > > > > Somewhat - not sure I fully understood :) > > > > > >> > >> -- > >> abstractj > >> > >> JBoss, a division of Red Hat > >> > >> > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.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 Tue Mar 11 02:16:59 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 07:16:59 +0100 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: On Mon, Mar 10, 2014 at 11:38 PM, Bruno Oliveira wrote: > Ahoy, answers inline. > > -- > abstractj > > On March 10, 2014 at 6:01:33 PM, Matthias Wessendorf (matzew at apache.org) > wrote: > > Ahoy! > > > > > > On Mon, Mar 10, 2014 at 9:49 PM, Bruno Oliveira wrote: > > > > > Good morning guys, for this issue > > > https://issues.jboss.org/browse/AGPUSH-358. I was revisiting the whole > > > UPS code and thinking about include two fields for iOSVariant class: > skey > > > (secret key) and pKey (public key). What's the idea? > > > > > > 1. Each application has its own key pair > > > > > > > each of the PushApplication constructs/objects on the UPS ? > > Yes if that makes sense to the others like Android variants. And no if we > just want to use it with iOSVariant, into this case that would apply only > for iOS applications. > Perfect! It does make sense on the 'root' PushApplication. That way other variant types can benefit from it as well. I think we can(should?) also encrypt the Google API-Key value. And future variants (other networks) will benefit in this case as well > > > > > > > > 2. Before the addition of the iOS variant, the client sends a request > > > asking for the public keys > > > > > > > "the client" ? Is that the AdminUI (or the relevant HTTP Rest code), when > > someone clicks "Add new Variant" ? > > Whatever REST consumer we have or the service. > > > > > > > > > > 3. The server sends an HTTP response with the public key for encryption > > > 4. The client make use of the public key to encrypt the certificate + > the > > > passphrase > > > 5. Server stores it encrypted > > > 6. When necessary to send push messages, the server make use of the > > > private key to decrypt that data and send fancy messages. > > > > > > > Now, when a (JavaEE) application is sending a request for push messages > to > > the UPS (which than internally makes use of the private key to decrypt > that > > data and send fancy messages to Apple), the HTTP RestEndpoint requires a > > new argument (the public key) to be allowed to submit these "requests" ? > > On the client side, after the public key retrieval you don't need to add > new parameters. As Sebastien mentioned it would remain unchanged. > perfect! > > Currently: > > curl -3 -v -b cookies.txt -c cookies.txt > -i -H "Accept: application/json" -H "Content-type: multipart/form-data" > -F "certificate=@/Users/matzew/Desktop/MyProdCert.p12" > -F "passphrase=TopSecret" > -F "production=true" // make sure you have Production certificate and > Provisioning Profile > > -X POST https://SERVER:PORT > /CONTEXT/rest/applications/{pushApplicationID}/iOS > > > Proposed: > > > curl -3 -v -b cookies.txt -c cookies.txt > -i -H "Accept: application/json" -H "Content-type: multipart/form-data" > -F "certificate=@/Users/matzew/Desktop/encrypted-cert.blah" > -F "passphrase=schwarzenegger" > -F "production=true" // make sure you have Production certificate and > Provisioning Profile > > -X POST https://SERVER:PORT > /CONTEXT/rest/applications/{pushApplicationID}/iOS > > Where encrypted-cert.blah and "Schwarzenegger" are encrypted data. > Ok, so the encrypted data is being uploaded by the user of the UPS, right ? and hence, no more a direct upload of the plain certificate and the plain passphrase. That means there is an extra step for the user, if I see it correct. having an extra step for the API to create the (iOS) variant is fine, let's make sure it's a somewhat simple step for our users, which hopefully than does not need too much extra steps in the documentation :-) > Makes sense? > Yes, I think :-) Thanks! -Matthias > > > > > > > > > > > Does it make sense to you? > > > > > > > Somewhat - not sure I fully understood :) > > > > > > > > > > -- > > > abstractj > > > > > > JBoss, a division of Red Hat > > > > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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 > > -- 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/20140311/2869728e/attachment.html From matzew at apache.org Tue Mar 11 05:00:14 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 10:00:14 +0100 Subject: [aerogear-dev] Release process Message-ID: Hello, for the Java bits we do have a solid release process ([1]). The main benefit is we stage the artifacts on a repo and give the community a heads-up for testing. Based on this vote we release (or may not release). This is a great way to engage the entire community to double check and give feedback. The release process is a shared thing inside of the community. For the other bits we currently do not have a similar process (my feeling). I'd actually prefer if we establish something like that on all the other platforms as well. This gives the community a chance to test the bits before we push them to the repos. IMO, if we start 'silently' release bits to the actual repositories it's kinda bypassing the community's feedback on a particular release candiate. Sure all the projects have tests, but manual testing, by the community is IMO a very positive thing -Matthias [1] https://github.com/aerogear/collateral/wiki/Release-Process-(Java) -- 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/20140311/1815d6b1/attachment.html From scm.blanc at gmail.com Tue Mar 11 05:13:21 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 11 Mar 2014 10:13:21 +0100 Subject: [aerogear-dev] Release process In-Reply-To: References: Message-ID: +1 Like you said for the java bits, the process is quite clear and having a maven staging repo helps, let's use this thread to check what we could do for the other bits : * JavaScript : We could maybe share a zip (somewhere doh) containing the release and give the link in a email on the ML "please test blabla, in 48hours this will be pushed on bower and ag.org ... + JIRA changelog" * Cordova : We could point to the branch containing the release and again share this on the ML "please test blabla, in 48hours this will be pushed to master and cordova plugin repo will be updated ... + JIRA changelog" * iOS : Anything to "stage" the pods ? Once we have this, we should create a wiki page for each platform, like we did for Java. On Tue, Mar 11, 2014 at 10:00 AM, Matthias Wessendorf wrote: > Hello, > > for the Java bits we do have a solid release process ([1]). The main > benefit is we stage the artifacts on a repo and give the community a > heads-up for testing. Based on this vote we release (or may not release). > This is a great way to engage the entire community to double check and give > feedback. The release process is a shared thing inside of the community. > > > For the other bits we currently do not have a similar process (my > feeling). I'd actually prefer if we establish something like that on all > the other platforms as well. This gives the community a chance to test the > bits before we push them to the repos. > > IMO, if we start 'silently' release bits to the actual repositories it's > kinda bypassing the community's feedback on a particular release candiate. > Sure all the projects have tests, but manual testing, by the community is > IMO a very positive thing > > -Matthias > > [1] https://github.com/aerogear/collateral/wiki/Release-Process-(Java) > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20140311/347ec6b2/attachment-0001.html From daniel.bevenius at gmail.com Tue Mar 11 05:19:19 2014 From: daniel.bevenius at gmail.com (danielbevenius) Date: Tue, 11 Mar 2014 02:19:19 -0700 (PDT) Subject: [aerogear-dev] SimplePush Server 0.10.0 In-Reply-To: References: Message-ID: <1394529559439-6718.post@n5.nabble.com> Hey Bruno, sorry about the late reply. I thought I sent a response yesterday but can't see it here. I was planning on releasing tomorrow but just discovered a bug [1]. Will fix it and post back with staging details. So the release will be delayed a little. Perhaps Thursday. [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-SimplePush-Server-0-10-0-tp6686p6718.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Tue Mar 11 05:21:48 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 10:21:48 +0100 Subject: [aerogear-dev] SimplePush Server 0.10.0 In-Reply-To: <1394529559439-6718.post@n5.nabble.com> References: <1394529559439-6718.post@n5.nabble.com> Message-ID: On Tue, Mar 11, 2014 at 10:19 AM, danielbevenius wrote: > Hey Bruno, > > sorry about the late reply. I thought I sent a response yesterday but can't > see it here. > > I was planning on releasing tomorrow but just discovered a bug [1]. Will > fix > it and post back with staging details. So the release will be delayed a > little. Perhaps Thursday. > sounds good to me > > [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-SimplePush-Server-0-10-0-tp6686p6718.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140311/e7de7f2b/attachment.html From matzew at apache.org Tue Mar 11 05:41:34 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 10:41:34 +0100 Subject: [aerogear-dev] cordova push plugin simplification In-Reply-To: <659AC7C3-D8CF-4AA5-BA47-5B0A2C554873@redhat.com> References: <89288199-8AF0-4EE2-B2A8-3013401B7F7E@redhat.com> <96125410-EF33-48B8-B08A-DD4906135785@redhat.com> <659AC7C3-D8CF-4AA5-BA47-5B0A2C554873@redhat.com> Message-ID: On Fri, Feb 28, 2014 at 2:59 PM, Erik Jan de Wit wrote: Of course we still can make it look like that, this is the same example but > then without everything inlined still our average user will have to get > used that we are referencing function 'pointers' here > > var pushConfig = { > pushServerURL: "", > alias: "", > android: { > senderID: "", > variantID: "", > variantSecret: "" > }, > ios: { > variantID: "", > variantSecret: "" > } > }; > > push.register(onNotification, errorHandler, pushConfig); > > function onNotification(event) { > alert(event.alert); > } > > function errorHandler(error) { > throw error; > } > > > This is the last version of the API ? > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140311/46a0cbf1/attachment.html From edewit at redhat.com Tue Mar 11 05:47:40 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 11 Mar 2014 10:47:40 +0100 Subject: [aerogear-dev] Release process In-Reply-To: References: Message-ID: <561FAFEA-DDAE-47BA-BCD5-4503CAACB472@redhat.com> Good idea to have a good release process for all bits, one remark though is 48 or 72 hours not very little time? Users will have to make time to test things and have time to provide us with feedback. If we are going to say if we haven?t heard from you in 48 hours we going to release automatically, this will discourage people from trying. On 11 Mar,2014, at 10:13 , Sebastien Blanc wrote: > * Cordova : We could point to the branch containing the release and again share this on the ML "please test blabla, in 48hours this will be pushed to master and cordova plugin repo will be updated ... + JIRA change log? +1 for Cordova we can easily create a branch that contains the release maybe even something like Lucas suggested that we have a development branch and leave master for the last stable release. And one more thing why do we have this on a github wiki page and not on the site? Wouldn?t it be better to keep information centralised? Cheers, Erik Jan From edewit at redhat.com Tue Mar 11 05:54:22 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 11 Mar 2014 10:54:22 +0100 Subject: [aerogear-dev] Release process In-Reply-To: <561FAFEA-DDAE-47BA-BCD5-4503CAACB472@redhat.com> References: <561FAFEA-DDAE-47BA-BCD5-4503CAACB472@redhat.com> Message-ID: One more thing that I miss in this process is how do we handle updating the documentation? Right now I make to PR?s and then we have to merge them one after the other but as we stage the release of the site as well we?ll have to coordinate this even more? From edewit at redhat.com Tue Mar 11 05:59:14 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 11 Mar 2014 10:59:14 +0100 Subject: [aerogear-dev] cordova push plugin simplification In-Reply-To: References: <89288199-8AF0-4EE2-B2A8-3013401B7F7E@redhat.com> <96125410-EF33-48B8-B08A-DD4906135785@redhat.com> <659AC7C3-D8CF-4AA5-BA47-5B0A2C554873@redhat.com> Message-ID: <9B9D1250-D8F0-47A6-AFE8-534EB59C1B65@redhat.com> > > This is the last version of the API ? Yes see https://github.com/aerogear/aerogear-pushplugin-cordova/pull/17 for more details > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140311/c0d499e5/attachment-0001.html From scm.blanc at gmail.com Tue Mar 11 06:06:57 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 11 Mar 2014 11:06:57 +0100 Subject: [aerogear-dev] Release process In-Reply-To: References: <561FAFEA-DDAE-47BA-BCD5-4503CAACB472@redhat.com> Message-ID: On Tue, Mar 11, 2014 at 10:54 AM, Erik Jan de Wit wrote: > One more thing that I miss in this process is how do we handle updating > the documentation? Right now I make to PR's and then we have to merge them > one after the other but as we stage the release of the site as well we'll > have to coordinate this even more? > Good point. Along with the "core" bits, a release should also have in its "package" a Doc PR for the site. Releasing the stuff should then be a trigger to merge the doc PR and push it to production. > > > _______________________________________________ > 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/20140311/948cea66/attachment.html From bruno at abstractj.org Tue Mar 11 07:17:24 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 11 Mar 2014 08:17:24 -0300 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: I will start to file Jiras, but answers inline. -- abstractj On March 11, 2014 at 3:17:01 AM, Matthias Wessendorf (matzew at apache.org) wrote: > > > > Yes if that makes sense to the others like Android variants. And no if we > > just want to use it with iOSVariant, into this case that would apply only > > for iOS applications. > > > > Perfect! > > It does make sense on the 'root' PushApplication. That way other variant > types can benefit from it as well. I think we can(should?) also encrypt the > Google API-Key value. And future variants (other networks) will benefit in > this case as well +1 > > > > > > Currently: > > > > curl -3 -v -b cookies.txt -c cookies.txt > > -i -H "Accept: application/json" -H "Content-type: multipart/form-data" > > -F "certificate=@/Users/matzew/Desktop/MyProdCert.p12" > > -F "passphrase=TopSecret" > > -F "production=true" // make sure you have Production certificate and > > Provisioning Profile > > > > -X POST https://SERVER:PORT > > /CONTEXT/rest/applications/{pushApplicationID}/iOS > > > > > > Proposed: > > > > > > curl -3 -v -b cookies.txt -c cookies.txt > > -i -H "Accept: application/json" -H "Content-type: multipart/form-data" > > -F "certificate=@/Users/matzew/Desktop/encrypted-cert.blah" > > -F "passphrase=schwarzenegger" > > -F "production=true" // make sure you have Production certificate and > > Provisioning Profile > > > > -X POST https://SERVER:PORT > > /CONTEXT/rest/applications/{pushApplicationID}/iOS > > > > Where encrypted-cert.blah and "Schwarzenegger" are encrypted data. > > > > Ok, so the encrypted data is being uploaded by the user of the UPS, right ? > and hence, no more a direct upload of the plain certificate and the plain > passphrase. > That means there is an extra step for the user, if I see it correct. > > having an extra step for the API to create the (iOS) variant is fine, let's > make sure it's a somewhat simple step for our users, which hopefully than > does not need too much extra steps in the documentation :-) I will think about how to make it less painful to our devs > > > > > Makes sense? > > > > Yes, I think :-) > Thanks! > > -Matthias > > > > > > > > > > > > > > > > > > Does it make sense to you? > > > > > > > > > > Somewhat - not sure I fully understood :) > > > > > > > > > > > > > > -- > > > > abstractj > > > > > > > > JBoss, a division of Red Hat > > > > > > > > > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.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 > > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > From bruno at abstractj.org Tue Mar 11 07:30:25 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 11 Mar 2014 08:30:25 -0300 Subject: [aerogear-dev] Release process In-Reply-To: References: Message-ID: Speaking from my side, security. I don?t have a formal process, I think it?s up to each tech lead: Android, iOs, JS and Security. Currently what I do is: - Announce the release date via roadmaps - If something went wrong, give a heads up on the ML and update the roadmaps & Jira with a new date. - During the release process I often send an e-mail to the ML and wait 2 business days.? - If someone shows up willing to test, I coordinate and wait (I don?t want people wasting their time for nothing) - If I don?t hear anything, ship it I think each community or technology has its own release cycle and in my opinion any attempt to push formality defeats the purpose. -- abstractj On March 11, 2014 at 6:00:35 AM, Matthias Wessendorf (matzew at apache.org) wrote: > > Hello, > > for the Java bits we do have a solid release process ([1]). The > main benefit is we stage the artifacts on a repo and give the community > a heads-up for testing. Based on this vote we release (or may not > release). This is a great way to engage the entire community to > double check and give feedback. The release process is a shared > thing inside of the community. > > > For the other bits we currently do not have a similar process (my > feeling). I'd actually prefer if we establish something like > that on all the other platforms as well. This gives the community > a chance to test the bits before we push them to the repos. > > IMO, if we start 'silently' release bits to the actual repositories > it's kinda bypassing the community's feedback on a particular > release candiate. Sure all the projects have tests, but manual > testing, by the community is IMO a very positive thing > > -Matthias > > [1] https://github.com/aerogear/collateral/wiki/Release-Process-(Java) From matzew at apache.org Tue Mar 11 07:32:11 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 12:32:11 +0100 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: On Tue, Mar 11, 2014 at 12:17 PM, Bruno Oliveira wrote: > I will start to file Jiras, but answers inline. > great > > -- > abstractj > > On March 11, 2014 at 3:17:01 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > > > > > > > Yes if that makes sense to the others like Android variants. And no if > we > > > just want to use it with iOSVariant, into this case that would apply > only > > > for iOS applications. > > > > > > > Perfect! > > > > It does make sense on the 'root' PushApplication. That way other variant > > types can benefit from it as well. I think we can(should?) also encrypt > the > > Google API-Key value. And future variants (other networks) will benefit > in > > this case as well > > +1 > > > > > > > > > > Currently: > > > > > > curl -3 -v -b cookies.txt -c cookies.txt > > > -i -H "Accept: application/json" -H "Content-type: multipart/form-data" > > > -F "certificate=@/Users/matzew/Desktop/MyProdCert.p12" > > > -F "passphrase=TopSecret" > > > -F "production=true" // make sure you have Production certificate and > > > Provisioning Profile > > > > > > -X POST https://SERVER:PORT > > > /CONTEXT/rest/applications/{pushApplicationID}/iOS > > > > > > > > > Proposed: > > > > > > > > > curl -3 -v -b cookies.txt -c cookies.txt > > > -i -H "Accept: application/json" -H "Content-type: multipart/form-data" > > > -F "certificate=@/Users/matzew/Desktop/encrypted-cert.blah" > > > -F "passphrase=schwarzenegger" > > > -F "production=true" // make sure you have Production certificate and > > > Provisioning Profile > > > > > > -X POST https://SERVER:PORT > > > /CONTEXT/rest/applications/{pushApplicationID}/iOS > > > > > > Where encrypted-cert.blah and "Schwarzenegger" are encrypted data. > > > > > > > Ok, so the encrypted data is being uploaded by the user of the UPS, > right ? > > and hence, no more a direct upload of the plain certificate and the plain > > passphrase. > > That means there is an extra step for the user, if I see it correct. > > > > having an extra step for the API to create the (iOS) variant is fine, > let's > > make sure it's a somewhat simple step for our users, which hopefully than > > does not need too much extra steps in the documentation :-) > > I will think about how to make it less painful to our devs > awesome! > > > > > > > > > > Makes sense? > > > > > > > Yes, I think :-) > > Thanks! > > > > -Matthias > > > > > > > > > > > > > > > > > > > > > > > > > Does it make sense to you? > > > > > > > > > > > > > Somewhat - not sure I fully understood :) > > > > > > > > > > > > > > > > > > -- > > > > > abstractj > > > > > > > > > > JBoss, a division of Red Hat > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev at lists.jboss.org > > > > > https://lists.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 > > > > > > > > > > > > -- > > 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/20140311/84f5f80f/attachment.html From matzew at apache.org Tue Mar 11 07:34:36 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 12:34:36 +0100 Subject: [aerogear-dev] Release process In-Reply-To: References: Message-ID: On Tue, Mar 11, 2014 at 12:30 PM, Bruno Oliveira wrote: > Speaking from my side, security. I don't have a formal process, I think > it's up to each tech lead: Android, iOs, JS and Security. > > Currently what I do is: > > - Announce the release date via roadmaps > - If something went wrong, give a heads up on the ML and update the > roadmaps & Jira with a new date. > - During the release process I often send an e-mail to the ML and wait 2 > business days. > - If someone shows up willing to test, I coordinate and wait (I don't want > people wasting their time for nothing) > - If I don't hear anything, ship it > > I think each community or technology has its own release cycle and in my > opinion any attempt to push formality defeats the purpose. > yeah - I agree w/ these, the main point is really that before we ship a particular release (regardless of the platform), the dev-list should be given a heads-up for testing (similar to what you laid out). That way we don't 'silently' release a piece of software > > > -- > abstractj > > On March 11, 2014 at 6:00:35 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > > > Hello, > > > > for the Java bits we do have a solid release process ([1]). The > > main benefit is we stage the artifacts on a repo and give the community > > a heads-up for testing. Based on this vote we release (or may not > > release). This is a great way to engage the entire community to > > double check and give feedback. The release process is a shared > > thing inside of the community. > > > > > > For the other bits we currently do not have a similar process (my > > feeling). I'd actually prefer if we establish something like > > that on all the other platforms as well. This gives the community > > a chance to test the bits before we push them to the repos. > > > > IMO, if we start 'silently' release bits to the actual repositories > > it's kinda bypassing the community's feedback on a particular > > release candiate. Sure all the projects have tests, but manual > > testing, by the community is IMO a very positive thing > > > > -Matthias > > > > [1] https://github.com/aerogear/collateral/wiki/Release-Process-(Java) > > -- 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/20140311/bab1a37a/attachment-0001.html From scm.blanc at gmail.com Tue Mar 11 07:37:27 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 11 Mar 2014 12:37:27 +0100 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: On Tue, Mar 11, 2014 at 12:32 PM, Matthias Wessendorf wrote: > > > > On Tue, Mar 11, 2014 at 12:17 PM, Bruno Oliveira wrote: > >> I will start to file Jiras, but answers inline. >> > > great > > >> >> -- >> abstractj >> >> On March 11, 2014 at 3:17:01 AM, Matthias Wessendorf (matzew at apache.org) >> wrote: >> >> > > >> > > Yes if that makes sense to the others like Android variants. And no >> if we >> > > just want to use it with iOSVariant, into this case that would apply >> only >> > > for iOS applications. >> > > >> > >> > Perfect! >> > >> > It does make sense on the 'root' PushApplication. That way other variant >> > types can benefit from it as well. I think we can(should?) also encrypt >> the >> > Google API-Key value. And future variants (other networks) will benefit >> in >> > this case as well >> >> +1 >> > >> > >> > > >> > > Currently: >> > > >> > > curl -3 -v -b cookies.txt -c cookies.txt >> > > -i -H "Accept: application/json" -H "Content-type: >> multipart/form-data" >> > > -F "certificate=@/Users/matzew/Desktop/MyProdCert.p12" >> > > -F "passphrase=TopSecret" >> > > -F "production=true" // make sure you have Production certificate and >> > > Provisioning Profile >> > > >> > > -X POST https://SERVER:PORT >> > > /CONTEXT/rest/applications/{pushApplicationID}/iOS >> > > >> > > >> > > Proposed: >> > > >> > > >> > > curl -3 -v -b cookies.txt -c cookies.txt >> > > -i -H "Accept: application/json" -H "Content-type: >> multipart/form-data" >> > > -F "certificate=@/Users/matzew/Desktop/encrypted-cert.blah" >> > > -F "passphrase=schwarzenegger" >> > > -F "production=true" // make sure you have Production certificate and >> > > Provisioning Profile >> > > >> > > -X POST https://SERVER:PORT >> > > /CONTEXT/rest/applications/{pushApplicationID}/iOS >> > > >> > > Where encrypted-cert.blah and "Schwarzenegger" are encrypted data. >> > > >> > >> > Ok, so the encrypted data is being uploaded by the user of the UPS, >> right ? >> > and hence, no more a direct upload of the plain certificate and the >> plain >> > passphrase. >> > That means there is an extra step for the user, if I see it correct. >> > >> > having an extra step for the API to create the (iOS) variant is fine, >> let's >> > make sure it's a somewhat simple step for our users, which hopefully >> than >> > does not need too much extra steps in the documentation :-) >> >> I will think about how to make it less painful to our devs >> > > > awesome! > I think it can be completly transparent for the user no (at least in the admin console) ? Retrieving the PK and encrypting can be done "under the hood" while keeping the same UI Flow , no ? > > >> >> > >> > >> > >> > > Makes sense? >> > > >> > >> > Yes, I think :-) >> > Thanks! >> > >> > -Matthias >> > >> > >> > > >> > > > >> > > > >> > > > > >> > > > > Does it make sense to you? >> > > > > >> > > > >> > > > Somewhat - not sure I fully understood :) >> > > > >> > > > >> > > > > >> > > > > -- >> > > > > abstractj >> > > > > >> > > > > JBoss, a division of Red Hat >> > > > > >> > > > > >> > > > > >> > > > > _______________________________________________ >> > > > > aerogear-dev mailing list >> > > > > aerogear-dev at lists.jboss.org >> > > > > https://lists.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 >> > > >> > > >> > >> > >> > -- >> > 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/20140311/a6d9df93/attachment.html From malliq9 at yahoo.com Tue Mar 11 06:26:04 2014 From: malliq9 at yahoo.com (malliq9) Date: Tue, 11 Mar 2014 03:26:04 -0700 (PDT) Subject: [aerogear-dev] Do AeroGear UnifiedPushServer can be installed on JBOSS 5/6 ? Message-ID: <1394533564857-6725.post@n5.nabble.com> Hi, I am installed the AeroGear UnifiedPushServer version 0.80 on JBOSS 7.1 Final, it is working fine. But as I want to use JBOSS 5.1 GA for cluster setup and want AeroGear UFPS to be installed on JBOSS 5.1 GA, where I am getting below error. I am thinking this is due to incompatability with the JBOSS Server. Appreciate any answer/work around for my query Showing below trace in log ------------------------------------------------------------------------ vfszip:/D:/SNG/Softwares/jboss-5.1.0.GA_ORIGINAL/server/default/deploy/aerogear-unifiedpush-server.war/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:662) Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI=http://java.sun.com/xml/ns/javaee location=http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189) at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137) at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348) ... 33 more Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI=http://java.sun.com/xml/ns/javaee location=http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:281) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) ... 41 more -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Do-AeroGear-UnifiedPushServer-can-be-installed-on-JBOSS-5-6-tp6725.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Tue Mar 11 07:43:38 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 12:43:38 +0100 Subject: [aerogear-dev] Do AeroGear UnifiedPushServer can be installed on JBOSS 5/6 ? In-Reply-To: <1394533564857-6725.post@n5.nabble.com> References: <1394533564857-6725.post@n5.nabble.com> Message-ID: Hello and thanks for the interest on the UnifiedPush Server We have not tested to deploy on JBoss AS 5 or 6; Currently we (internally) use some newer features of JavaEE (async EJB, CDI etc), hence our main targets right now are JBoss 7.1.x and WildFly-8 Greetings, Matthias On Tue, Mar 11, 2014 at 11:26 AM, malliq9 wrote: > Hi, > > I am installed the AeroGear UnifiedPushServer version 0.80 on JBOSS 7.1 > Final, it is working fine. But as I want to use JBOSS 5.1 GA for cluster > setup and want AeroGear UFPS to be installed on JBOSS 5.1 GA, where I am > getting below error. I am thinking this is due to incompatability with the > JBOSS Server. > > Appreciate any answer/work around for my query > > Showing below trace in log > ------------------------------------------------------------------------ > > vfszip:/D:/SNG/Softwares/jboss-5.1.0.GA_ORIGINAL/server/default/deploy/aerogear-unifiedpush-server.war/ > at > > org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) > at > > org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362) > at > > org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322) > at > > org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294) > at > > org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234) > at > > org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) > at > > org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) > at > > org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) > at > > org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) > at > > org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) > at > > org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) > at > > org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) > at > > org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) > at > > org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) > at > > org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at > > org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at > > org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) > at > > org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) > at > > org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) > at > > org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) > at > > org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) > at > > org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) > at > > org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) > at > > org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) > at > > org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) > at > > org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) > at > > org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) > at > > org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) > at > > org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) > at > > org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306) > at > > org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271) > at > org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) > at org.jboss.Main.boot(Main.java:221) > at org.jboss.Main$1.run(Main.java:556) > at java.lang.Thread.run(Thread.java:662) > Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: > Failed to resolve schema nsURI=http://java.sun.com/xml/ns/javaee > location=http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd > at > > org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) > at > org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) > at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189) > at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166) > at > > org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137) > at > > org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121) > at > > org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256) > at > > org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188) > at > > org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348) > ... 33 more > Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve > schema nsURI=http://java.sun.com/xml/ns/javaee > location=http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd > at > > org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:281) > at > > org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) > at > org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) > at > org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown > Source) > at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown > Source) > at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown > Source) > at > > org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown > Source) > at > > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown > Source) > at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > at > > org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) > ... 41 more > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Do-AeroGear-UnifiedPushServer-can-be-installed-on-JBOSS-5-6-tp6725.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140311/e73791e2/attachment-0001.html From bruno at abstractj.org Tue Mar 11 07:52:46 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 11 Mar 2014 08:52:46 -0300 Subject: [aerogear-dev] aerogear security and android In-Reply-To: <1394467743631-6703.post@n5.nabble.com> References: <1394467743631-6703.post@n5.nabble.com> Message-ID: Good morning Marcelo, I?m not an Android specialist or anything, but speaking about AeroGear. The team worked to keep the symmetry between the APIs, so it doesn?t matter which backend do you have. I couldn?t understand what do you mean by "authorize cripty token push?. To make use of REST, take a look at the Android cookbook (https://github.com/aerogear/aerogear-android-cookbook), more specifically?https://github.com/aerogear/aerogear-android-cookbook/tree/5c0aa9d1434a239a2e184573b338b73732e7cea1/src/org/jboss/aerogear/cookbook/authentication. In addition check our documentation at https://aerogear.org Regarding which server should you use. The answer is whatever you want, our clients are not tied to JBoss. Speaking about the server not be functional, we are open for suggestions or send patches. Currently the following projects are running the authentication bits with no problems: -?https://github.com/aerogear/aerogear-jaxrs-demo -?https://github.com/aerogear/aerogear-integration-tests-server -?https://github.com/aerogear/aerogear-unifiedpush-server But if something is missing or not working, I?m open for suggestions. -- abstractj On March 10, 2014 at 1:28:33 PM, marceloheck (marceloheck at gmail.com) wrote: > Hello > > I search a sample with aerogear and security server > > in client > > private AuthenticationModule authModule; > private String baseURL = "http://localhost:8080/servicos/service/auth"; > > private TextView status; > private Button login; > private Button logout; > private static final String LOG_TAG = login.class.getName(); > > @Override > protected void onCreate(Bundle savedInstanceState) { > super.onCreate(savedInstanceState); > setContentView(R.layout.activity_main); > > Authenticator authenticator = new Authenticator(baseURL); > AuthenticationConfig authenticationConfig = new > AuthenticationConfig(); > // authenticationConfig.setAuthType(AuthTypes.HTTP_BASIC); > authenticationConfig.setLoginEndpoint("/login"); > authenticationConfig.setLogoutEndpoint("/logout"); > authModule = authenticator.auth("login", authenticationConfig); > > status = (TextView) findViewById(R.id.editText1); > login = (Button) findViewById(R.id.button1); > logout = (Button) findViewById(R.id.Button01); > > button = (Button) findViewById(R.id.button1); > > /* // Capture button clicks > button.setOnClickListener(new OnClickListener() { > public void onClick(View arg0) { > > // Start NewActivity.class > Intent myIntent = new Intent(MainActivity.this, > login.class); > startActivity(myIntent); > } > });*/ > > login.setOnClickListener(new View.OnClickListener() { > @Override > public void onClick(View view) { > authModule.login("nome", "senha", new > AbstractActivityCallback() { > > > @Override > public void onSuccess(HeaderAndBody data) { > Log.d(LOG_TAG, "Received ID: " + data.toString() ); > logged(true); > // Start NewActivity.class > Intent myIntent = new Intent(MainActivity.this, > > br.gov.pr.dc.sisdc.activities.MapActivity.class); > startActivity(myIntent); > > // Toast.makeText(getActivity(), "logado", > Toast.LENGTH_SHORT).show(); > } > > @Override > public void onFailure(Exception e) { > displayError(e.getMessage()); > // Toast.makeText(getActivity(), "erro", > Toast.LENGTH_SHORT).show(); > Log.d(LOG_TAG, "error: " + e ); > Intent myIntent = new Intent(MainActivity.this, > > br.gov.pr.dc.sisdc.activities.MapActivity.class); > startActivity(myIntent); > } > }); > } > }); > > > is ok > > but how to use the rest in android is authenticate and authorize cripty > token push etc... in other REST service? > is session? is value how? > > ... > > URL BASE_URL = new URL("http://localhost:8080/servicos/service/"); > > PageConfig pageConfig = new PageConfig(); > pageConfig.setLimitValue(5); > pageConfig.setMetadataLocation(PageConfig.MetadataLocations.WEB_LINKING); > > PipeConfig pipeConfig = new PipeConfig(BASE_URL, AbrigoVO.class); > pipeConfig.setEndpoint("pessoa"); > pipeConfig.setPageConfig(pageConfig); > pipeline = new Pipeline(BASE_URL); > pipeline.pipe(pessoaVO.class, pipeConfig); > > LoaderPipe pipes = pipeline.get("pessoavo", mContext); > //LoaderPipe pipes = this.pipeline.get("pessoavo", fragment, > mContext); > > //TODO > https://github.com/aerogear/aerogear-aerodoc-android/blob/master/src/org/jboss/aerogear/android/unifiedpush/aerodoc/fragments/AeroDocLeadsAvailableFragments.java > pipes.read(readCallback); > > Log.d(LOG_TAG, "Received ID: " ); > return null; > } catch (Exception e) { > // TODO Need error handling > Log.e(LOG_TAG, e.getLocalizedMessage(), e); > Log.e(LOG_TAG, "sem servi?o", e); > e.printStackTrace(); > return null; > } > ... > > > > > > and security server jboss 7 ?? > > > > > @Path("/pessoa/") > public interface pessoaResource { > > @Produces(MediaType.APPLICATION_JSON) > public Response listar(); > > > @GET > @Path("/{codigo}") > @Produces(MediaType.APPLICATION_JSON) > public Response obter(@PathParam("codigo") Long idpessoa); > > } > > > i add > > @Inject > private IdentityManagement configuration; > > @Inject > private AuthenticationManager authenticationManager; > > and > > > org.jboss.aerogear.security.interceptor.SecurityInterceptor > > > and > > @Secure("admin") > > but error injection > > WELD-001408 Unsatisfied dependencies for type [EntityManager] with > qualifiers [@Default] at injection point [[field] @Inject private > org.jboss.aerogear.security.shiro.authz.GrantConfiguration.entityManager] > > examples JaxRS and shiro and demo not funcional of soluction server and > client android > > i connect database login password e groups for login > > how to keep the connected User? have database or saved in the session? > > can someone give me a practical example for using rest client server? > > > > > > > > > > > > > > > > > > -- > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-security-and-android-tp6703.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From bruno at abstractj.org Tue Mar 11 07:53:20 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 11 Mar 2014 08:53:20 -0300 Subject: [aerogear-dev] Release process In-Reply-To: References: Message-ID: Makes sense. -- abstractj On March 11, 2014 at 8:34:36 AM, Matthias Wessendorf (matzew at apache.org) wrote: > > yeah - I agree w/ these, the main point is really that before we > ship a particular release (regardless of the platform), the > dev-list should be given a heads-up for testing (similar to what > you laid out). > > That way we don't 'silently' release a piece of software From bruno at abstractj.org Tue Mar 11 07:56:18 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 11 Mar 2014 08:56:18 -0300 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: There are thousands of solutions for it. For example: - copy and paste the public key from the admin console to use it on the client side - verify if the client already has the public key and don?t send a new request, just the data encrypted - request the public key every time I think we can start simple and improve it. -- abstractj On March 11, 2014 at 8:37:34 AM, Sebastien Blanc (scm.blanc at gmail.com) wrote: > > I think it can be completly transparent for the user no (at least > in the admin console) ? Retrieving the PK and encrypting can be > done "under the hood" while keeping the same UI Flow , no ? From matzew at apache.org Tue Mar 11 07:58:21 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 12:58:21 +0100 Subject: [aerogear-dev] iOS Passphrases for UPS In-Reply-To: References: Message-ID: On Tue, Mar 11, 2014 at 12:56 PM, Bruno Oliveira wrote: > There are thousands of solutions for it. For example: > > - copy and paste the public key from the admin console to use it on the > client side > - verify if the client already has the public key and don't send a new > request, just the data encrypted > - request the public key every time > > I think we can start simple and improve it. > +1 > > -- > abstractj > > On March 11, 2014 at 8:37:34 AM, Sebastien Blanc (scm.blanc at gmail.com) > wrote: > > > I think it can be completly transparent for the user no (at least > > in the admin console) ? Retrieving the PK and encrypting can be > > done "under the hood" while keeping the same UI Flow , no ? > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140311/5d198214/attachment.html From supittma at redhat.com Tue Mar 11 08:31:02 2014 From: supittma at redhat.com (Summers Pittman) Date: Tue, 11 Mar 2014 08:31:02 -0400 Subject: [aerogear-dev] security updates In-Reply-To: References: Message-ID: <531F0206.70007@redhat.com> On 03/10/2014 11:43 AM, Erik Jan de Wit wrote: > Hi, > > Bruno has created some PR?s to update our cordova plugins to no longer support 3.0.0 but update it to 3.4.0, because of a number of security issues that have been solved. Now of course we should encourage that people use the latest version, but this PR enforces it. Also Gorkem that invested quite some time to support different versions. So what should we pick enforce or encourage? Do we know if people are using the older version of Cordova with our libs? > > Cheers, > Erik Jan > _______________________________________________ > 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 Tue Mar 11 08:49:19 2014 From: lholmqui at redhat.com (Luke Holmquist) Date: Tue, 11 Mar 2014 08:49:19 -0400 (EDT) Subject: [aerogear-dev] Release process In-Reply-To: References: Message-ID: <9498467F-B43C-4C4A-835D-4B41DA4F6BA3@redhat.com> Makes sense. For the 1.4.0 js release coming out there will be a blog post announcing it. But next time we will do the heads up on the list. It wasn't on my index card ? Sent from my iPhone > On Mar 11, 2014, at 7:53 AM, Bruno Oliveira wrote: > > Makes sense. > > -- > abstractj > > On March 11, 2014 at 8:34:36 AM, Matthias Wessendorf (matzew at apache.org) wrote: >>> yeah - I agree w/ these, the main point is really that before we >> ship a particular release (regardless of the platform), the >> dev-list should be given a heads-up for testing (similar to what >> you laid out). >> >> That way we don't 'silently' release a piece of software > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Tue Mar 11 10:36:02 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 15:36:02 +0100 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 Message-ID: Hello, for the upcoming release we have a few, but important, tickets solved: https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 Before finishing the release, let's see if there are issues w/ the server, hence I have staged the WAR file on my private webspace: http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ If they aren't any objections or remarks I will release the bits to bintray on Friday morning Greetings, 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/20140311/f9319b4c/attachment-0001.html From bruno at abstractj.org Tue Mar 11 10:38:16 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 11 Mar 2014 11:38:16 -0300 Subject: [aerogear-dev] security updates In-Reply-To: <531F0206.70007@redhat.com> References: <531F0206.70007@redhat.com> Message-ID: No clue, but even with someone using it, I think is just the matter of communicate and explain ?why?. -- abstractj On March 11, 2014 at 9:31:16 AM, Summers Pittman (supittma at redhat.com) wrote: > > Do we know if people are using the older version of Cordova with > our libs? From edewit at redhat.com Tue Mar 11 10:41:16 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 11 Mar 2014 15:41:16 +0100 Subject: [aerogear-dev] security updates In-Reply-To: References: <531F0206.70007@redhat.com> Message-ID: I still feel like it?s saying our application won?t run on Java 1.6, because it has security issues. On 11 Mar,2014, at 15:38 , Bruno Oliveira wrote: > No clue, but even with someone using it, I think is just the matter of communicate and explain ?why?. > > -- > abstractj > > On March 11, 2014 at 9:31:16 AM, Summers Pittman (supittma at redhat.com) wrote: >>> Do we know if people are using the older version of Cordova with >> our libs? > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From bruno at abstractj.org Tue Mar 11 10:43:30 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 11 Mar 2014 11:43:30 -0300 Subject: [aerogear-dev] security updates In-Reply-To: References: <531F0206.70007@redhat.com> Message-ID: How many users do we have running Cordova projects? -- abstractj On March 11, 2014 at 11:41:26 AM, Erik Jan de Wit (edewit at redhat.com) wrote: > > I still feel like it?s saying our application won?t run on Java > 1.6, because it has security issues. > > On 11 Mar,2014, at 15:38 , Bruno Oliveira > wrote: > > > No clue, but even with someone using it, I think is just the matter > of communicate and explain ?why?. > > > > -- > > abstractj > > > > On March 11, 2014 at 9:31:16 AM(http://airmail.calendar/2014-03-11%2009:31:16%20GMT-3), > Summers Pittman (supittma at redhat.com(mailto:supittma at redhat.com)) > wrote: > >>> Do we know if people are using the older version of Cordova > with > >> our libs? > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org(mailto:aerogear-dev at lists.jboss.org) > > https://lists.jboss.org/mailman/listinfo/aerogear-dev From corinnekrych at gmail.com Tue Mar 11 11:36:47 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 11 Mar 2014 16:36:47 +0100 Subject: [aerogear-dev] Release process In-Reply-To: <9498467F-B43C-4C4A-835D-4B41DA4F6BA3@redhat.com> References: <9498467F-B43C-4C4A-835D-4B41DA4F6BA3@redhat.com> Message-ID: Ok, for iOS we're going to release 1.5.0 planned early next week. We'll do ML announcements. ++ Corinne On 11 March 2014 13:49, Luke Holmquist wrote: > Makes sense. For the 1.4.0 js release coming out there will be a blog > post announcing it. But next time we will do the heads up on the list. > It wasn't on my index card ? > > Sent from my iPhone > > > On Mar 11, 2014, at 7:53 AM, Bruno Oliveira wrote: > > > > Makes sense. > > > > -- > > abstractj > > > > On March 11, 2014 at 8:34:36 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > >>> yeah - I agree w/ these, the main point is really that before we > >> ship a particular release (regardless of the platform), the > >> dev-list should be given a heads-up for testing (similar to what > >> you laid out). > >> > >> That way we don't 'silently' release a piece of software > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20140311/eac3b278/attachment.html From matzew at apache.org Tue Mar 11 11:42:45 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Mar 2014 16:42:45 +0100 Subject: [aerogear-dev] Release process In-Reply-To: References: <9498467F-B43C-4C4A-835D-4B41DA4F6BA3@redhat.com> Message-ID: On Tuesday, March 11, 2014, Corinne Krych wrote: > Ok, for iOS we're going to release 1.5.0 planned early next week. We'll do > ML announcements. > > ++ > Corinne > Not only announcements of the actual release being done IMO a mail w/ heads up here is the branch/tag we will release to CocoaPods soon engages the community in being part of the actual release process; -Matthias > > > On 11 March 2014 13:49, Luke Holmquist > > wrote: > >> Makes sense. For the 1.4.0 js release coming out there will be a blog >> post announcing it. But next time we will do the heads up on the list. >> It wasn't on my index card ? >> >> Sent from my iPhone >> >> > On Mar 11, 2014, at 7:53 AM, Bruno Oliveira > >> wrote: >> > >> > Makes sense. >> > >> > -- >> > abstractj >> > >> > On March 11, 2014 at 8:34:36 AM, Matthias Wessendorf (matzew at apache.org) >> wrote: >> >>> yeah - I agree w/ these, the main point is really that before we >> >> ship a particular release (regardless of the platform), the >> >> dev-list should be given a heads-up for testing (similar to what >> >> you laid out). >> >> >> >> That way we don't 'silently' release a piece of software >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.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/20140311/01f318d1/attachment.html From tolisemm at gmail.com Tue Mar 11 12:18:57 2014 From: tolisemm at gmail.com (tolis emmanouilidis) Date: Tue, 11 Mar 2014 18:18:57 +0200 Subject: [aerogear-dev] security updates In-Reply-To: References: Message-ID: I'd vote for encourage even if security should always be priority 1. I feel that if the supported Cordova Lib versions of the AeroGear plugins are changed every time a security vulnerability is discovered and a new Cordova Lib version is released, then our plugins will always support only the latest Cordova Lib version. Thanks, Tolis 2014-03-10 17:43 GMT+02:00 Erik Jan de Wit : > Hi, > > Bruno has created some PR's to update our cordova plugins to no longer > support 3.0.0 but update it to 3.4.0, because of a number of security > issues that have been solved. Now of course we should encourage that people > use the latest version, but this PR enforces it. Also Gorkem that invested > quite some time to support different versions. So what should we pick > enforce or encourage? > > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140311/2038bc18/attachment.html From bsutter at redhat.com Tue Mar 11 13:12:09 2014 From: bsutter at redhat.com (Burr Sutter) Date: Tue, 11 Mar 2014 13:12:09 -0400 Subject: [aerogear-dev] security updates In-Reply-To: References: Message-ID: <7ED42B41-92DC-468A-8923-636B5334EEB3@redhat.com> We are going to have to support a range of Cordova versions for the following reasons: 1) Sync'ing with JBDS 2) Sync'ing with what is supported at any given moment - where the supported version may only update 2 times a year 3) Addressing the fact that customers are slow to upgrade unless there is a very real problem exposed in their specific application - for example, if they don't use a particular Cordova plugin then they might ignore a particular vulnerability that is tied to a specific plugin. Another example, if their apps are only used on 25 corporate executives phones, then they might determine the vulnerability is less important (small, fixed audience). We will need to pick a specific time window for all parties to "catch up" like 12 months. On Mar 11, 2014, at 12:18 PM, tolis emmanouilidis wrote: > I'd vote for encourage even if security should always be priority 1. > > I feel that if the supported Cordova Lib versions of the AeroGear plugins are changed every time a security vulnerability is discovered and a new Cordova Lib version is released, then our plugins will always support only the latest Cordova Lib version. > > Thanks, > Tolis > > > 2014-03-10 17:43 GMT+02:00 Erik Jan de Wit : > Hi, > > Bruno has created some PR?s to update our cordova plugins to no longer support 3.0.0 but update it to 3.4.0, because of a number of security issues that have been solved. Now of course we should encourage that people use the latest version, but this PR enforces it. Also Gorkem that invested quite some time to support different versions. So what should we pick enforce or encourage? > > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140311/b2cbd067/attachment-0001.html From kpiwko at redhat.com Tue Mar 11 13:15:49 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Tue, 11 Mar 2014 18:15:49 +0100 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: References: Message-ID: <20140311181549.020b7003@kapy-ntb-x220> Sounds good. I'll schedule testing to start Wed afternoon. Karel On Tue, 11 Mar 2014 15:36:02 +0100 Matthias Wessendorf wrote: > Hello, > > for the upcoming release we have a few, but important, tickets solved: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 > > > Before finishing the release, let's see if there are issues w/ the server, > hence I have staged the WAR file on my private webspace: > > > http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ > > > If they aren't any objections or remarks I will release the bits to bintray > on Friday morning > > > Greetings, > Matthias > From marceloheck at gmail.com Tue Mar 11 13:25:29 2014 From: marceloheck at gmail.com (marceloheck) Date: Tue, 11 Mar 2014 10:25:29 -0700 (PDT) Subject: [aerogear-dev] aerogear security and android In-Reply-To: References: <1394467743631-6703.post@n5.nabble.com> Message-ID: <1394558729969-6747.post@n5.nabble.com> Ola bruno , vou te escrever assim mesmo fizemos o lado do android e faz login em um rest tudo ok, o lado do servidor ? que esta complicado , usamos jboss 7 e temos suporte contratado da redhat , n?o sei se vcs s?o contratados deles e podem prestar esse suporte podemos conversar melhor... O aerogear no lado do servidor ligando com o android com seguran?a esta nosso problema, como n?o usamos barramento, precisamos usar token ,criptografia, push, ou todas pra proteger esse rest entre o android e o server. Como o aerogear ( pode ser com shiro) pode ser usado nesse conjunto, fizemos segundo o modelo com o exemplo e colocando o interceptors, fazendo inject ou n?o e temos um problema, fazemos o login , retorna ok e como o android e o servidor ficam se comunicando depois disso? na pr?xima chamada rest de dados .... e se o grupo de seguran?a trava acesso no ejb , pelos exemplos fica muito superficial n?o conseguimos ver isso funcionando com android n?o sei se consegui explicar direito , parece que em vers?es anteriores do aerogear passava token e agora isso ? feito por baixo ou n?o , estamos trabalhando a um tempo e quase desistindo porque n?o conseguimos integrar e n?o achamos um exemplo que fa?a e tem pouca coisa na web sobre o aerogear -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-security-and-android-tp6703p6747.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Wed Mar 12 03:21:36 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 12 Mar 2014 08:21:36 +0100 Subject: [aerogear-dev] OpenShift cartridge: UPS Part (was Re: Staging of UnifiedPush Server 0.10.1) Message-ID: Hello, after staging the release bits, I also updated our OpenShift cartridge: https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/commit/07367f1f96ce4b0bf88b58604f4322830b5104a7 I created a fork and merged the bits into my master (for an easier testing): https://github.com/matzew/openshift-origin-cartridge-aerogear-push For testing the 0.10.1 version our our cartridge, simply execute the following command: rhc app create --no-git https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.1 Greetings, Matthias On Tue, Mar 11, 2014 at 3:36 PM, Matthias Wessendorf wrote: > Hello, > > for the upcoming release we have a few, but important, tickets solved: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 > > > Before finishing the release, let's see if there are issues w/ the server, > hence I have staged the WAR file on my private webspace: > > > > http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ > > > If they aren't any objections or remarks I will release the bits to > bintray on Friday morning > > > Greetings, > Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140312/e6b63367/attachment.html From matzew at apache.org Wed Mar 12 04:19:55 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 12 Mar 2014 09:19:55 +0100 Subject: [aerogear-dev] aerogear security and android In-Reply-To: <1394558729969-6747.post@n5.nabble.com> References: <1394467743631-6703.post@n5.nabble.com> <1394558729969-6747.post@n5.nabble.com> Message-ID: Hello Marcelo, thanks for the interest on AeroGear. This mailing list is an English one; Please state your questions in English. This simply allows the entire community to benefit from your questions and potential answers. Thanks! Matthias 2014-03-11 18:25 GMT+01:00 marceloheck : > Ola bruno , vou te escrever assim mesmo > > fizemos o lado do android e faz login em um rest tudo ok, > > o lado do servidor ? que esta complicado , usamos jboss 7 e temos suporte > contratado da redhat , n?o sei se vcs s?o contratados deles e podem prestar > esse suporte podemos conversar melhor... > > O aerogear no lado do servidor ligando com o android com seguran?a esta > nosso problema, como n?o usamos barramento, precisamos usar token > ,criptografia, push, ou todas pra proteger esse rest entre o android e o > server. > > Como o aerogear ( pode ser com shiro) pode ser usado nesse conjunto, > fizemos > segundo o modelo com o exemplo e colocando o interceptors, fazendo inject > ou > n?o e temos um problema, fazemos o login , retorna ok e como o android e o > servidor ficam se comunicando depois disso? na pr?xima chamada rest de > dados > .... e se o grupo de seguran?a trava acesso no ejb , pelos exemplos fica > muito superficial n?o conseguimos ver isso funcionando com android > > n?o sei se consegui explicar direito , parece que em vers?es anteriores do > aerogear passava token e agora isso ? feito por baixo ou n?o , estamos > trabalhando a um tempo e quase desistindo porque n?o conseguimos integrar e > n?o achamos um exemplo que fa?a e tem pouca coisa na web sobre o aerogear > > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-security-and-android-tp6703p6747.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140312/f8a17b95/attachment.html From marceloheck at gmail.com Wed Mar 12 07:42:02 2014 From: marceloheck at gmail.com (marceloheck) Date: Wed, 12 Mar 2014 04:42:02 -0700 (PDT) Subject: [aerogear-dev] aerogear security and android In-Reply-To: References: <1394467743631-6703.post@n5.nabble.com> <1394558729969-6747.post@n5.nabble.com> Message-ID: <1394624522273-6750.post@n5.nabble.com> sorry Matthias! thanks for you response, I replied in Portuguese to answer doubts bruno because we really need to solve, or we abandon aerogear The AEROGEAR on the server side calling with android safely this our problem , as we do not use the bus, we need to use token , encryption , push , or all to protect that rest between the android and the server . As the AEROGEAR ( can be with Shiro ) can be used in this set , we modeled the example and putting the interceptors , inject or not doing and we have a problem , do the login, and returns ok as android and server are left communicating after that? the next call .... rest data and the security group access hangs in ejb , by the examples gets very shallow can not see it working with android do not know if I could explain it , it seems that in earlier versions of AEROGEAR token passed and now it is done underneath or not , we are working at a time and almost gave up because I could not integrate and could not find an example that does and has little in aerogear -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-security-and-android-tp6703p6750.html Sent from the aerogear-dev mailing list archive at Nabble.com. From bruno at abstractj.org Wed Mar 12 10:18:40 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 12 Mar 2014 11:18:40 -0300 Subject: [aerogear-dev] aerogear security and android In-Reply-To: <1394624522273-6750.post@n5.nabble.com> References: <1394467743631-6703.post@n5.nabble.com> <1394558729969-6747.post@n5.nabble.com> <1394624522273-6750.post@n5.nabble.com> Message-ID: Hi Marcelo, answers inline. -- abstractj On March 12, 2014 at 8:42:10 AM, marceloheck (marceloheck at gmail.com) wrote: > > sorry Matthias! thanks for you response, > > I replied in Portuguese to answer doubts bruno As Matthias said ML is not a one to one conversation, otherwise people won?t benefit of this discussion. > > because we really need to solve, or we abandon aerogear That would be bad, but at the same time is hard to guess what?s happening if you do not provide details. > > > The AEROGEAR on the server side calling with android safely this > our problem > , as we do not use the bus, we need to use token , encryption , push > , or > all to protect that rest between the android and the server . It seems to me too generic. Please make sure to provide more details like:? - What are you trying to do on the server side? - Which version of JBoss, AG are you running on the server? Which modules? - What are you trying to do on the client side? - Do you have stacktraces? That would help - Our documentation is clear? What?s missing? What kind of example do you want? - Have you tried the cookbooks? Are they enough? > > As the AEROGEAR ( can be with Shiro ) can be used in this set , we modeled AeroGear can be used with any thing as I mentioned before. We are not tied to a single server solution.? ? > the example and putting the interceptors , inject or not doing > and we have a > problem , do the login, and returns ok as android and server are > left Have you managed to login using Shiro *only* and send cURL HTTP requests? How your endpoint looks like? > communicating after that? the next call .... rest data and the > security > group access hangs in ejb , by the examples gets very shallow can? How does it work with cURL, wget? > not see it > working with android > > do not know if I could explain it , it seems that in earlier versions? I could barely understand due to the lack of details about what?s going on the server. Maybe stacktraces, code snippets, gists would be nice. > of > AEROGEAR token passed and now it is done underneath or not , we > are working > at a time and almost gave up because I could not integrate and could > not > find an example that does and has little in aerogear The authorization token was provided by PicketBox, I guess 1 year and a half ago, but removed once we moved to PicketLink. Keep in mind that you don?t need: AeroGear Security, AeroGear Security Picketlink or AeroGear Security Shiro on the server ? They are just a dozen of class wrappers to make the bare minimum simple, if you want to go advance, you must use the plain APIs from Shiro. I strongly recommend you to use plain Shiro on the server and integrate it with AeroGear Android. From bruno at abstractj.org Wed Mar 12 10:30:19 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 12 Mar 2014 11:30:19 -0300 Subject: [aerogear-dev] AeroGear.org Message-ID: Good morning peeps, I?m planning to push to production the latest changes on aerogear.org tomorrow. Any problems? -- abstractj From supittma at redhat.com Wed Mar 12 10:31:50 2014 From: supittma at redhat.com (Summers Pittman) Date: Wed, 12 Mar 2014 10:31:50 -0400 Subject: [aerogear-dev] AeroGear.org In-Reply-To: References: Message-ID: <53206FD6.5080606@redhat.com> On Wed 12 Mar 2014 10:30:19 AM EDT, Bruno Oliveira wrote: > Good morning peeps, I?m planning to push to production the latest changes on aerogear.org tomorrow. Any problems? > > -- > abstractj > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev +1 -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From daniel.bevenius at gmail.com Wed Mar 12 10:35:57 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Wed, 12 Mar 2014 15:35:57 +0100 Subject: [aerogear-dev] AeroGear.org In-Reply-To: <53206FD6.5080606@redhat.com> References: <53206FD6.5080606@redhat.com> Message-ID: +1 On 12 March 2014 15:31, Summers Pittman wrote: > On Wed 12 Mar 2014 10:30:19 AM EDT, Bruno Oliveira wrote: > > Good morning peeps, I'm planning to push to production the latest > changes on aerogear.org tomorrow. Any problems? > > > > -- > > abstractj > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > +1 > > -- > 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/20140312/048ef572/attachment.html From matzew at apache.org Wed Mar 12 10:37:03 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 12 Mar 2014 15:37:03 +0100 Subject: [aerogear-dev] AeroGear.org In-Reply-To: References: <53206FD6.5080606@redhat.com> Message-ID: +1 On Wed, Mar 12, 2014 at 3:35 PM, Daniel Bevenius wrote: > +1 > > > On 12 March 2014 15:31, Summers Pittman wrote: > >> On Wed 12 Mar 2014 10:30:19 AM EDT, Bruno Oliveira wrote: >> > Good morning peeps, I'm planning to push to production the latest >> changes on aerogear.org tomorrow. Any problems? >> > >> > -- >> > abstractj >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> +1 >> >> -- >> 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/20140312/35769f54/attachment.html From qmx at qmx.me Wed Mar 12 10:40:42 2014 From: qmx at qmx.me (Douglas Campos) Date: Wed, 12 Mar 2014 11:40:42 -0300 Subject: [aerogear-dev] AeroGear.org In-Reply-To: References: Message-ID: <20140312144042.GJ678@rohan.local> ship it -- qmx From smikloso at redhat.com Wed Mar 12 10:48:21 2014 From: smikloso at redhat.com (Stefan Miklosovic) Date: Wed, 12 Mar 2014 10:48:21 -0400 (EDT) Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: References: Message-ID: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> Hello Matthias, we executed UPS integration tests on the latest commit in 0.10.x brach (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. Since you talked about Bintray, we could move this little bit further and test staged bits directly from there - meaning wars which are not on Maven Central yet but they are already on Bintray would be downloaded from there dynamically and our intergration test suite would be run directly against built (but yet unreleased) wars. In other words, Bintray could be used as a staging facility for UPS. WDYT? Stefan Miklosovic Red Hat Brno - JBoss Mobile Platform e-mail: smikloso at redhat.com irc: smikloso ----- Original Message ----- > Hello, > for the upcoming release we have a few, but important, tickets solved: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 > Before finishing the release, let's see if there are issues w/ the server, > hence I have staged the WAR file on my private webspace: > http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ > If they aren't any objections or remarks I will release the bits to bintray > on Friday morning > Greetings, > 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/20140312/8fc6eb58/attachment.html From matzew at apache.org Wed Mar 12 11:12:33 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 12 Mar 2014 16:12:33 +0100 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> References: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic wrote: > Hello Matthias, > > we executed UPS integration tests on the latest commit in 0.10.x brach > (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. > awesome! > > Since you talked about Bintray, we could move this little bit further and > test > staged bits directly from there - meaning wars which are not on Maven > Central > yet but they are already on Bintray would be downloaded from there > dynamically > and our intergration test suite would be run directly against built (but > yet unreleased) wars. > the WAR files from my private staging repo will be exactly those that I upload to bintray; I use the private repo, to avoid an early publish (before the release is really done) -Matthias > > In other words, Bintray could be used as a staging facility for UPS. > > WDYT? > > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: smikloso at redhat.com > irc: smikloso > > ------------------------------ > > Hello, > > for the upcoming release we have a few, but important, tickets solved: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 > > > Before finishing the release, let's see if there are issues w/ the server, > hence I have staged the WAR file on my private webspace: > > > > http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ > > > If they aren't any objections or remarks I will release the bits to > bintray on Friday morning > > > Greetings, > 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/20140312/538fec8b/attachment-0001.html From cvasilak at gmail.com Wed Mar 12 11:19:32 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Wed, 12 Mar 2014 17:19:32 +0200 Subject: [aerogear-dev] AeroGear.org In-Reply-To: References: Message-ID: <29CE33E3-C109-4B6D-BB68-9A1DC1D0686A@gmail.com> +1 On Mar 12, 2014, at 4:30 PM, Bruno Oliveira wrote: > Good morning peeps, I?m planning to push to production the latest changes on aerogear.org tomorrow. Any problems? > > -- > abstractj > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140312/2f45e5b9/attachment.bin From smikloso at redhat.com Wed Mar 12 11:35:06 2014 From: smikloso at redhat.com (Stefan Miklosovic) Date: Wed, 12 Mar 2014 11:35:06 -0400 (EDT) Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: References: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> Message-ID: <161652535.9283579.1394638506889.JavaMail.zimbra@redhat.com> ----- Original Message ----- > On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic < smikloso at redhat.com > > wrote: > > Hello Matthias, > > > we executed UPS integration tests on the latest commit in 0.10.x brach > > > (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. > > awesome! > > Since you talked about Bintray, we could move this little bit further and > > test > > > staged bits directly from there - meaning wars which are not on Maven > > Central > > > yet but they are already on Bintray would be downloaded from there > > dynamically > > > and our intergration test suite would be run directly against built (but > > yet > > unreleased) wars. > > the WAR files from my private staging repo will be exactly those that I > upload to bintray; > I use the private repo, to avoid an early publish (before the release is > really done) Ah, right. The discussion I had with Karel was that it would be nice to test these built wars before they finally reach Maven Central and Bintray would act as a staging place just as your private repo right now. I am not sure if Bintray supports this but if it is possible, Bintray could be exactly what your "private repo" is right now, we would just make it more robust / official moving from your private repo somewhere (no offence) to Bintray. By doing this, we kind of abuse Bintray, I guess it is not primarily used for staging bits but for announcing them to the world, however it is technically possible. However feel free to cancel this idea. We are planning to test these unreleased wars anyway so instead of Bintray we try to download them from your private repo but I am just saying that having it from Bintray seems to be better. - Stefan > -Matthias > > In other words, Bintray could be used as a staging facility for UPS. > > > WDYT? > > > Stefan Miklosovic > > > Red Hat Brno - JBoss Mobile Platform > > > e-mail: smikloso at redhat.com > > > irc: smikloso > > > > Hello, > > > > > > for the upcoming release we have a few, but important, tickets solved: > > > > > > https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 > > > > > > Before finishing the release, let's see if there are issues w/ the > > > server, > > > hence I have staged the WAR file on my private webspace: > > > > > > http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ > > > > > > If they aren't any objections or remarks I will release the bits to > > > bintray > > > on Friday morning > > > > > > Greetings, > > > > > > 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 > _______________________________________________ > 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/20140312/e1d2fa3b/attachment.html From matzew at apache.org Wed Mar 12 11:39:50 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 12 Mar 2014 16:39:50 +0100 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: <161652535.9283579.1394638506889.JavaMail.zimbra@redhat.com> References: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> <161652535.9283579.1394638506889.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Mar 12, 2014 at 4:35 PM, Stefan Miklosovic wrote: > > ------------------------------ > > > > > On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic wrote: > >> Hello Matthias, >> >> we executed UPS integration tests on the latest commit in 0.10.x brach >> (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. >> > > > awesome! > >> >> Since you talked about Bintray, we could move this little bit further and >> test >> staged bits directly from there - meaning wars which are not on Maven >> Central >> yet but they are already on Bintray would be downloaded from there >> dynamically >> and our intergration test suite would be run directly against built (but >> yet unreleased) wars. >> > > > the WAR files from my private staging repo will be exactly those that I > upload to bintray; > > I use the private repo, to avoid an early publish (before the release is > really done) > > Ah, right. The discussion I had with Karel was that it would be nice to > test these built wars before they > finally reach Maven Central and Bintray would act as a staging place just > as your private repo right now. > feel free to use my private staging repo as your repo (it's a valid maven repo URL) http://people.apache.org/~matzew/aerogear-staging/ > > I am not sure if Bintray supports this but if it is possible, Bintray > could be exactly what your > "private repo" is right now, we would just make it more robust / official > moving from > your private repo somewhere (no offence) to Bintray. > > By doing this, we kind of abuse Bintray, I guess it is not primarily used > for staging bits but for announcing them to the world, > however it is technically possible. > yes, but I am more interested in keep my current process: * staging: my Apache account * release: bintray (there we have all the good stats etc) > > However feel free to cancel this idea. We are planning to test these > unreleased wars anyway so instead of Bintray > we try to download them from your private repo but I am just saying that > having it from Bintray seems to be better. > And again, these files from my private repo are exactly the same that I than upload to bintray (assuming the release tests are passing) -M > > - Stefan > > -Matthias > >> >> In other words, Bintray could be used as a staging facility for UPS. >> >> WDYT? >> >> Stefan Miklosovic >> Red Hat Brno - JBoss Mobile Platform >> >> e-mail: smikloso at redhat.com >> irc: smikloso >> >> ------------------------------ >> >> Hello, >> >> for the upcoming release we have a few, but important, tickets solved: >> https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 >> >> >> Before finishing the release, let's see if there are issues w/ the >> server, hence I have staged the WAR file on my private webspace: >> >> >> >> http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ >> >> >> If they aren't any objections or remarks I will release the bits to >> bintray on Friday morning >> >> >> Greetings, >> 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140312/c1775023/attachment-0001.html From marceloheck at gmail.com Wed Mar 12 12:47:37 2014 From: marceloheck at gmail.com (marceloheck) Date: Wed, 12 Mar 2014 09:47:37 -0700 (PDT) Subject: [aerogear-dev] aerogear security and android In-Reply-To: References: <1394467743631-6703.post@n5.nabble.com> <1394558729969-6747.post@n5.nabble.com> <1394624522273-6750.post@n5.nabble.com> Message-ID: <1394642857598-6762.post@n5.nabble.com> hi bruno thank you! In android I used the example of the cookbook and it worked the server try to use the example of jaxrs and I could not try using aerogear-security-shiro and could not, have an equal jaxrs example but using shiro? infos: i use android native in client and jboss7.1(ejb jpa resteasy jdk6 jee6) in server database of users and profile and data, I seek a REST/JSON in a tomcat 5 (legacy system) sample sequence: >>>>>>>>>>android native send aerogear login <<<<<<<< private AuthenticationModule authModule; private String baseURL = "http://localhost:8080/servicos/service/auth"; private TextView status; private Button login; private Button logout; private static final String LOG_TAG = login.class.getName(); @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); Authenticator authenticator = new Authenticator(baseURL); AuthenticationConfig authenticationConfig = new AuthenticationConfig(); authenticationConfig.setLoginEndpoint("/login"); authenticationConfig.setLogoutEndpoint("/logout"); authModule = authenticator.auth("login", authenticationConfig); status = (TextView) findViewById(R.id.editText1); login = (Button) findViewById(R.id.button1); logout = (Button) findViewById(R.id.Button01); button = (Button) findViewById(R.id.button1); login.setOnClickListener(new View.OnClickListener() { @Override public void onClick(View view) { authModule.login("jhon", "123", new AbstractActivityCallback() { } >>>>>>>>>server receive <<<<<<<<<<< (is my problem ) (wanted an example here )(queria um exemplo disso aqui no shiro ) @Path("/auth") public class LoginEndpoint { private static final Logger LOGGER = Logger.getLogger(LoginEndpoint.class.getSimpleName()); // @Inject private AuthenticationManager authenticationManager; @POST @Path("/login") @Produces(MediaType.APPLICATION_JSON) @Consumes(MediaType.APPLICATION_JSON) public Response login(User simpleUser) { User user = new User(simpleUser.getUsername(), simpleUser.getPassword()); authenticationManager.login(user, simpleUser.getPassword()); //return simpleUser; return Response.status(Status.OK).entity(user).build(); } >>>>>>>>>>>>>>> android receive <<<<<<<<<<<<<<<<<< @Override public void onSuccess(HeaderAndBody data) { Log.d(LOG_TAG, "Received ID: " + data.toString() ); logged(true); Toast.makeText(getActivity(), "logado", Toast.LENGTH_SHORT).show(); } ---------(as the android saves login, as he knows that this logged? need sample) ------- >>>>>>>>>>>>>>>> android send next requisition <<<<<<<<<< URL BASE_URL = new URL("http://localhost:8080/servicos/service/"); PageConfig pageConfig = new PageConfig(); pageConfig.setLimitValue(5); pageConfig.setMetadataLocation(PageConfig.MetadataLocations.WEB_LINKING); PipeConfig pipeConfig = new PipeConfig(BASE_URL, AbrigoVO.class); pipeConfig.setEndpoint("pessoa"); pipeConfig.setPageConfig(pageConfig); pipeline = new Pipeline(BASE_URL); pipeline.pipe(pessoaVO.class, pipeConfig); LoaderPipe pipes = pipeline.get("pessoavo", mContext); pipes.read(readCallback); return null; } catch (Exception e) { // TODO Need error handling Log.e(LOG_TAG, e.getLocalizedMessage(), e); Log.e(LOG_TAG, "sem servi?o", e); e.printStackTrace(); return null; } ---------next pipe in login? how call security rest? necessary is send login again? ------- >>>>>>>>>>>>>>>server received and response<<<<<<<<<< @GET @Produces(MediaType.APPLICATION_JSON) public Response listar(); --------how use @secure("admin)? -------- is necessary a sample ----- >>>>>>>>>>>>>>>>the end<<<<<<<<<<<<<<<<<< -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-security-and-android-tp6703p6762.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Wed Mar 12 13:19:20 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 12 Mar 2014 18:19:20 +0100 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: References: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> <161652535.9283579.1394638506889.JavaMail.zimbra@redhat.com> Message-ID: FYI: On IRC Stefan reported the WAR from my staging repo also passes the tests. On Wed, Mar 12, 2014 at 4:39 PM, Matthias Wessendorf wrote: > > > > On Wed, Mar 12, 2014 at 4:35 PM, Stefan Miklosovic wrote: > >> >> ------------------------------ >> >> >> >> >> On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic wrote: >> >>> Hello Matthias, >>> >>> we executed UPS integration tests on the latest commit in 0.10.x brach >>> (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. >>> >> >> >> awesome! >> >>> >>> Since you talked about Bintray, we could move this little bit further >>> and test >>> staged bits directly from there - meaning wars which are not on Maven >>> Central >>> yet but they are already on Bintray would be downloaded from there >>> dynamically >>> and our intergration test suite would be run directly against built >>> (but yet unreleased) wars. >>> >> >> >> the WAR files from my private staging repo will be exactly those that I >> upload to bintray; >> >> I use the private repo, to avoid an early publish (before the release is >> really done) >> >> Ah, right. The discussion I had with Karel was that it would be nice to >> test these built wars before they >> finally reach Maven Central and Bintray would act as a staging place just >> as your private repo right now. >> > > > feel free to use my private staging repo as your repo (it's a valid maven > repo URL) > http://people.apache.org/~matzew/aerogear-staging/ > > > >> >> I am not sure if Bintray supports this but if it is possible, Bintray >> could be exactly what your >> "private repo" is right now, we would just make it more robust / >> official moving from >> your private repo somewhere (no offence) to Bintray. >> >> By doing this, we kind of abuse Bintray, I guess it is not primarily used >> for staging bits but for announcing them to the world, >> however it is technically possible. >> > > yes, but I am more interested in keep my current process: > > * staging: my Apache account > * release: bintray (there we have all the good stats etc) > > >> >> However feel free to cancel this idea. We are planning to test these >> unreleased wars anyway so instead of Bintray >> we try to download them from your private repo but I am just saying that >> having it from Bintray seems to be better. >> > > And again, these files from my private repo are exactly the same that I > than upload to bintray (assuming the release tests are passing) > > -M > > >> >> - Stefan >> >> -Matthias >> >>> >>> In other words, Bintray could be used as a staging facility for UPS. >>> >>> WDYT? >>> >>> Stefan Miklosovic >>> Red Hat Brno - JBoss Mobile Platform >>> >>> e-mail: smikloso at redhat.com >>> irc: smikloso >>> >>> ------------------------------ >>> >>> Hello, >>> >>> for the upcoming release we have a few, but important, tickets solved: >>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 >>> >>> >>> Before finishing the release, let's see if there are issues w/ the >>> server, hence I have staged the WAR file on my private webspace: >>> >>> >>> >>> http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ >>> >>> >>> If they aren't any objections or remarks I will release the bits to >>> bintray on Friday morning >>> >>> >>> Greetings, >>> 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140312/56da4d53/attachment.html From bruno at abstractj.org Wed Mar 12 15:57:51 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 12 Mar 2014 16:57:51 -0300 Subject: [aerogear-dev] AeroGear Crypto Java 0.1.3 Staged Message-ID: Good morning everyone, AG Crypto Java was staged under the following maven profile:?https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2816 I?m planning to release it on Friday morning (14/03) Changelog: * 17b9787 (upstream-abstractj/keypair-encoding, keypair-encoding) Explicit imports, instead of wildcards * 7e595da Accept a raw key pair. For scenarios where the public key is transmitted over the wire a34b746 Test refactoring * 880be04 Add support on cryptobox to accept a public key for encryption * a2c39ff Testing vectors for public key encryption * 4421bc3 (upstream-abstractj/pom, pom) Change the scope for bouncycastle * f190d64 (upstream-abstractj/refactor, refactor) Accept KeyPair as argument * 832127a (AGSEC-147) Hashing support for SHA-256 and SHA-512 -- abstractj From bruno at abstractj.org Wed Mar 12 17:04:00 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 12 Mar 2014 18:04:00 -0300 Subject: [aerogear-dev] AeroGear Crypto Java 0.1.3 Staged In-Reply-To: <> References: <> Message-ID: New staging URL?https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2817. The latest change was to benefit Android and write less code: -?ae454bf Expose method to generate secret for scenarios where it must be saved into the key store -- abstractj On March 12, 2014 at 4:57:51 PM, Bruno Oliveira (bruno at abstractj.org) wrote: > Good morning everyone, AG Crypto Java was staged under the following maven profile: > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2816 > I?m planning to release it on Friday morning (14/03) Changelog: * 17b9787 (upstream-abstractj/keypair-encoding, > keypair-encoding) Explicit imports, instead of wildcards * 7e595da Accept a raw key > pair. For scenarios where the public key is transmitted over the wire a34b746 Test refactoring > * 880be04 Add support on cryptobox to accept a public key for encryption * a2c39ff Testing > vectors for public key encryption * 4421bc3 (upstream-abstractj/pom, pom) Change > the scope for bouncycastle * f190d64 (upstream-abstractj/refactor, refactor) Accept > KeyPair as argument * 832127a (AGSEC-147) Hashing support for SHA-256 and SHA-512 -- > abstractj From keith at kdmooreconsulting.com Wed Mar 12 23:02:08 2014 From: keith at kdmooreconsulting.com (keithdmoore94) Date: Wed, 12 Mar 2014 20:02:08 -0700 (PDT) Subject: [aerogear-dev] cordova push plugin simplification In-Reply-To: <89288199-8AF0-4EE2-B2A8-3013401B7F7E@redhat.com> References: <89288199-8AF0-4EE2-B2A8-3013401B7F7E@redhat.com> Message-ID: <1394679728604-6766.post@n5.nabble.com> The only catch that I see with breaking out the attributes is that for new device types (aka Windows, Amazon, some new xyz), a code change here will be needed. I like not having to check the device type in my code in order to populate the config. I guess depending on the added device, you might have to add unique attributes anyway. -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-cordova-push-plugin-simplification-tp6523p6766.html Sent from the aerogear-dev mailing list archive at Nabble.com. From daniel.bevenius at gmail.com Thu Mar 13 00:47:09 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Thu, 13 Mar 2014 05:47:09 +0100 Subject: [aerogear-dev] SimplePush Server 0.10.0 In-Reply-To: References: <1394529559439-6718.post@n5.nabble.com> Message-ID: We have staged an updated version containing fixes for [1] and [2] which can be found here: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2814/ The OpenShift instance has been updated and now also contains UnifiedPush Server 0.10.1: https://sps010-dbevenius.rhcloud.com:8443/simplepush And if you'd like create an instance using your own OpenShift account: rhc create-app appName " https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push&commit=d009198e5b71a4335f02b0fff47cb809a30c2c6e" mysql-5.1 [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 "Greeting message is only returned once." [2] https://issues.jboss.org/browse/AGSMPLPUSH-42"xhr_streaming/xhr_polling protocols are not working" On 11 March 2014 10:21, Matthias Wessendorf wrote: > > > > On Tue, Mar 11, 2014 at 10:19 AM, danielbevenius < > daniel.bevenius at gmail.com> wrote: > >> Hey Bruno, >> >> sorry about the late reply. I thought I sent a response yesterday but >> can't >> see it here. >> >> I was planning on releasing tomorrow but just discovered a bug [1]. Will >> fix >> it and post back with staging details. So the release will be delayed a >> little. Perhaps Thursday. >> > > sounds good to me > > >> >> [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 >> >> >> >> -- >> View this message in context: >> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-SimplePush-Server-0-10-0-tp6686p6718.html >> Sent from the aerogear-dev mailing list archive at Nabble.com. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > 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/20140313/f24e3559/attachment.html From edewit at redhat.com Thu Mar 13 03:45:50 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 13 Mar 2014 08:45:50 +0100 Subject: [aerogear-dev] cordova push plugin simplification In-Reply-To: <1394679728604-6766.post@n5.nabble.com> References: <89288199-8AF0-4EE2-B2A8-3013401B7F7E@redhat.com> <1394679728604-6766.post@n5.nabble.com> Message-ID: <049010E3-0C36-49E8-9F9E-422F9CD919F9@redhat.com> Hi, Currently the plugin supports only one set of varaintId and secret and if you want to create an application for android and iOS you would have logic like if (device.platform == ?android?) { variantId = ""; } else { variantId = ""; } so with this grouping you don?t have to have this if else logic anymore as you can just add them in the config like so: var pushConfig = { pushServerURL: "", alias: "", android: { senderID: "", variantID: "", variantSecret: "" }, ios: { variantID: "", variantSecret: "" } }; And when a windows phone is added you?ll still have to change the code to add the variantId for windows. As we don?t have a way to register for the application only for the variant this is the compromise. Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/b022d72b/attachment.html From edewit at redhat.com Thu Mar 13 06:19:57 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 13 Mar 2014 11:19:57 +0100 Subject: [aerogear-dev] Cordova Plugin Release 0.0.3 Message-ID: <86621CFB-E147-4706-B7DE-FF448D88A20F@redhat.com> Hi Folks, This is a heads up for the release of the Cordova Push Plugin 0.0.3, this release solves a number of minor issues. https://github.com/aerogear/aerogear-pushplugin-cordova/pull/16 For testing clone the project and switch to the release branch and install git clone https://github.com/aerogear/aerogear-pushplugin-cordova.git git checkout -b release cordova plugin install If they aren't any objections or remarks I will release the bits to bintray on Friday afternoon Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/5dc73d35/attachment.html From kpiwko at redhat.com Thu Mar 13 06:22:37 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 13 Mar 2014 11:22:37 +0100 Subject: [aerogear-dev] SimplePush Server 0.10.0 In-Reply-To: References: <1394529559439-6718.post@n5.nabble.com> Message-ID: <20140313112237.5de0105f@kapy-ntb-x220> Sweet, I'll have a look on that. Karel On Thu, 13 Mar 2014 05:47:09 +0100 Daniel Bevenius wrote: > We have staged an updated version containing fixes for [1] and [2] which > can be found here: > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2814/ > > The OpenShift instance has been updated and now also contains UnifiedPush > Server 0.10.1: > https://sps010-dbevenius.rhcloud.com:8443/simplepush > > And if you'd like create an instance using your own ARQ-OpenShift account: > rhc create-app appName " > https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push&commit=d009198e5b71a4335f02b0fff47cb809a30c2c6e" > mysql-5.1 > > [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 "Greeting message is only > returned once." > [2] https://issues.jboss.org/browse/AGSMPLPUSH-42"xhr_streaming/xhr_polling > protocols are not working" > > > > > On 11 March 2014 10:21, Matthias Wessendorf wrote: > > > > > > > > > On Tue, Mar 11, 2014 at 10:19 AM, danielbevenius < > > daniel.bevenius at gmail.com> wrote: > > > >> Hey Bruno, > >> > >> sorry about the late reply. I thought I sent a response yesterday but > >> can't > >> see it here. > >> > >> I was planning on releasing tomorrow but just discovered a bug [1]. Will > >> fix > >> it and post back with staging details. So the release will be delayed a > >> little. Perhaps Thursday. > >> > > > > sounds good to me > > > > > >> > >> [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 > >> > >>ARQ- > >> > >> -- > >> View this message in context: > >> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-SimplePush-Server-0-10-0-tp6686p6718.html > >> Sent from the aerogear-dev mailing list archive at Nabble.com. > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > From keith at kdmooreconsulting.com Thu Mar 13 06:39:24 2014 From: keith at kdmooreconsulting.com (keithdmoore94) Date: Thu, 13 Mar 2014 03:39:24 -0700 (PDT) Subject: [aerogear-dev] cordova push plugin simplification In-Reply-To: <049010E3-0C36-49E8-9F9E-422F9CD919F9@redhat.com> References: <89288199-8AF0-4EE2-B2A8-3013401B7F7E@redhat.com> <1394679728604-6766.post@n5.nabble.com> <049010E3-0C36-49E8-9F9E-422F9CD919F9@redhat.com> Message-ID: <503E2220-A145-43C1-8164-45F60D5D7DAF@kdmooreconsulting.com> Good point. I hate having to do device checks. > On Mar 13, 2014, at 2:46 AM, "Erik Jan de Wit [via aerogear-dev]" wrote: > > Hi, > > Currently the plugin supports only one set of varaintId and secret and if you want to create an application for android and iOS you would have logic like > if (device.platform == ?android?) { > variantId = ""; > } else { > variantId = ""; > } > so with this grouping you don?t have to have this if else logic anymore as you can just add them in the config like so: > var pushConfig = { > > pushServerURL: "", > > alias: "", > android: { > > senderID: "", > variantID: "", > > variantSecret: "" > }, > ios: { > > variantID: "", > variantSecret: "" > > } > }; > And when a windows phone is added you?ll still have to change the code to add the variantId for windows. As we don?t have a way to register for the application only for the variant this is the compromise. > > Cheers, > Erik Jan > > > _______________________________________________ > aerogear-dev mailing list > [hidden email] > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > If you reply to this email, your message will be added to the discussion below: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-cordova-push-plugin-simplification-tp6523p6769.html > To unsubscribe from [aerogear-dev] cordova push plugin simplification, click here. > NAML -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-cordova-push-plugin-simplification-tp6523p6772.html Sent from the aerogear-dev mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/3a56af2b/attachment.html From bruno at abstractj.org Thu Mar 13 07:59:23 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 13 Mar 2014 08:59:23 -0300 Subject: [aerogear-dev] Passphrase encryption - REST API discussion Message-ID: Good morning slackers, moving forward with my attempt to put pants on passphrases. I would like to discuss how the REST API would be with the change, because is better to have feedback instead of work for days and waste some time. Register push app: - HTTP request ? Remain unchanged - HTTP response {"id":"2095ab1a-a569-4ae2-a43c-a86b83041592?, "name":"MyApp?, "description":"awesome app?, "pushApplicationID":"ca99487d-6387-41bd-b393-0ce480977efe?, "masterSecret":"b315d524-e9f9-4d04-946c-b73278ff29be?, "developer":"admin?, "androidVariants":[], "simplePushVariants":[], ?chromePackagedAppVariants":[], "publicKey":"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEpsPA31qRWrtiAhnpGBzgwoE435c18gD42y13urb0JSdx4AHQRthhAUFVnu+RqUU8NTp9tGnEEhyBZfbV67arVw==?, ?nonce?:?6KbYGZKvTusU+IL3sdY9g==" "iosvariants":[]} publicKey: Is the public key created per application and will be optional for developers who do care about security. If for some reason they don?t want to encrypt their passphrase or certificate, that?s ok. nonce:?16 bytes non-deterministic used to encrypt the data on the server Note: Both would be stored into UPS database (not perfect, but a good start) Keep in mind that this is just the initial idea, for example, masterSecret should never return in clear. To the further interactions it will be fixed establishing a key agreement between client and server and encrypt the whole response (only for sensitive data). Yeah, I know, we are protected by SSL, but we shouldn?t trust on it. iOS Variant: - HTTP request ? Remain unchanged, but now certificate and passphrase can be send encrypted and the server will store it. - HTTP response ? Remain unchaged Sender: - HTTP request ? Remain unchanged, but now the server will search for the application ID and retrieve the public key to decrypt application's passphrase - HTTP response ? Remain unchanged AeroGear Clients - cURL Yesterday I had the amusing experience of dig into the sources of OpenSSL and their documentation, to see how people could encrypt it from the command line. If I recommend that people would remember my name for the eternity in a bad way. Another insane idea was to provide encoders for GPG. The simplest idea, I think, would be provide code for people encrypt their passphrase and certificate, instead of trust in some software. - aerogear-unifiedpush-java-client No problem to implement it. - aerogear-simplepush-java-client No problem to implement it. - aerogear-simplepush-node-client Not so easy, but they do OpenSSL behind the scenes - aerogear-unifiedpush-nodejs-client Not so easy, but they do OpenSSL behind the scenes So, what do you think? Yay/Nay? I would never use that? The goal is to provide secure alternatives to developers, but if the whole process will turn into a pain, I won?t move forward. ? -- abstractj From scm.blanc at gmail.com Thu Mar 13 08:32:59 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 13 Mar 2014 13:32:59 +0100 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: Sounds goods ! Just one small question inline On Thu, Mar 13, 2014 at 12:59 PM, Bruno Oliveira wrote: > Good morning slackers, moving forward with my attempt to put pants on > passphrases. I would like to discuss how the REST API would be with the > change, because is better to have feedback instead of work for days and > waste some time. > > Register push app: > > - HTTP request > > Remain unchanged > > - HTTP response > > {"id":"2095ab1a-a569-4ae2-a43c-a86b83041592", > "name":"MyApp", > "description":"awesome app", > "pushApplicationID":"ca99487d-6387-41bd-b393-0ce480977efe", > "masterSecret":"b315d524-e9f9-4d04-946c-b73278ff29be", > "developer":"admin", > "androidVariants":[], > "simplePushVariants":[], > "chromePackagedAppVariants":[], > > "publicKey":"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEpsPA31qRWrtiAhnpGBzgwoE435c18gD42y13urb0JSdx4AHQRthhAUFVnu+RqUU8NTp9tGnEEhyBZfbV67arVw==", > "nonce":"6KbYGZKvTusU+IL3sdY9g==" > "iosvariants":[]} > > > publicKey: Is the public key created per application and will be optional > for developers who do care about security. If for some reason they don't > want to encrypt their passphrase or certificate, that's ok. > > nonce: 16 bytes non-deterministic used to encrypt the data on the server > > Note: Both would be stored into UPS database (not perfect, but a good > start) > > Keep in mind that this is just the initial idea, for example, masterSecret > should never return in clear. To the further interactions it will be fixed > establishing a key agreement between client and server and encrypt the > whole response (only for sensitive data). Yeah, I know, we are protected by > SSL, but we shouldn't trust on it. > > > iOS Variant: > > - HTTP request > > Remain unchanged, but now certificate and passphrase can be send > encrypted and the server will store it. > Shouldn't there be a flag in the request telling the cert and passphrase are encrypted or not ? Or maybe the server can detect by itself if it's encrypted or not . > > - HTTP response > > Remain unchaged > > Sender: > > - HTTP request > > Remain unchanged, but now the server will search for the application ID > and retrieve the public key to decrypt application's passphrase > > - HTTP response > > Remain unchanged > > > AeroGear Clients > > - cURL > > Yesterday I had the amusing experience of dig into the sources of OpenSSL > and their documentation, to see how people could encrypt it from the > command line. If I recommend that people would remember my name for the > eternity in a bad way. Another insane idea was to provide encoders for GPG. > The simplest idea, I think, would be provide code for people encrypt their > passphrase and certificate, instead of trust in some software. > > - aerogear-unifiedpush-java-client > > No problem to implement it. > > - aerogear-simplepush-java-client > > No problem to implement it. > > - aerogear-simplepush-node-client > > Not so easy, but they do OpenSSL behind the scenes > > - aerogear-unifiedpush-nodejs-client > > Not so easy, but they do OpenSSL behind the scenes > > > So, what do you think? Yay/Nay? I would never use that? > > The goal is to provide secure alternatives to developers, but if the whole > process will turn into a pain, I won't move forward. > > > > > > -- > abstractj > > _______________________________________________ > 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/20140313/37d39ffe/attachment.html From bsutter at redhat.com Thu Mar 13 08:43:35 2014 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 13 Mar 2014 08:43:35 -0400 Subject: [aerogear-dev] Skins Message-ID: <63FCBBA8-B575-4138-B04D-B538A7E7B140@redhat.com> It is time to get our simulator skins upgraded Will iPhone3 or 4 still run iOS7? Please comment here: https://issues.jboss.org/browse/JBDS-2960 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/d4727569/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot 2014-03-13 08.37.41.png Type: image/png Size: 106494 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/d4727569/attachment-0001.png From bruno at abstractj.org Thu Mar 13 08:45:28 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 13 Mar 2014 09:45:28 -0300 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: That would make sense into the Sender request, once we don?t have ways to identify if the data was encrypted or not, something like "--header ?protected: true? (always optional). For example: curl -3 -u "{PushApplicationID}:{MasterSecret}" ? ?-v -H "Accept: application/json" -H "Content-type: application/json? ? ?--header ?protected: true" ? ?-X POST ? ?-d '{ ? ? ? "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", "444939cd-ae63-4ce1-96a4-de74b77e3737" ....], ? ? ? "categories" : ["someCategory"], ? ? ? "alias" : ["user at account.com", "jay at redhat.org", ....], ? ? ? "deviceType" : ["iPad", "AndroidTablet", "web"], ? ? ? "message": {"key":"value", "key2":"other value", "alert":"HELLO!"}, ? ? ? "simple-push": "version=123" ? ?}' https://SERVER:PORT/CONTEXT/rest/sender Does it make sense to you? In the future with the key agreement, that might not be necessary. -- abstractj On March 13, 2014 at 9:33:07 AM, Sebastien Blanc (scm.blanc at gmail.com) wrote: > > Shouldn't there be a flag in the request telling the cert and > passphrase are encrypted or not ? Or maybe the server can detect > by itself if it's encrypted or not . From matzew at apache.org Thu Mar 13 08:51:32 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 13:51:32 +0100 Subject: [aerogear-dev] Skins In-Reply-To: <63FCBBA8-B575-4138-B04D-B538A7E7B140@redhat.com> References: <63FCBBA8-B575-4138-B04D-B538A7E7B140@redhat.com> Message-ID: Was this post supposed to be posted to a different list ? Anyways, iPhone3 zero iOS7 Check here: http://www.apple.com/ios/features/ "OS 7 is compatible with" On Thu, Mar 13, 2014 at 1:43 PM, Burr Sutter wrote: > It is time to get our simulator skins upgraded > > Will iPhone3 or 4 still run iOS7? > > Please comment here: > https://issues.jboss.org/browse/JBDS-2960 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140313/980d5399/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot 2014-03-13 08.37.41.png Type: image/png Size: 106494 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/980d5399/attachment-0001.png From bsutter at redhat.com Thu Mar 13 09:00:19 2014 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 13 Mar 2014 09:00:19 -0400 Subject: [aerogear-dev] Skins In-Reply-To: References: <63FCBBA8-B575-4138-B04D-B538A7E7B140@redhat.com> Message-ID: <96E9D6CC-C5A6-4F6E-82A8-1A88B52FDDDA@redhat.com> On Mar 13, 2014, at 8:51 AM, Matthias Wessendorf wrote: > Was this post supposed to be posted to a different list ? No - these skins are a subset of the devices the Aerogear aims to support. :-) > > > Anyways, iPhone3 zero iOS7 OK - I think we should drop iPhone 3 from the list - it is getting cluttered and we need to add in more Android devices, as they have a higher variety of screen dimensions. > > Check here: > http://www.apple.com/ios/features/ > > "OS 7 is compatible with" > > > > On Thu, Mar 13, 2014 at 1:43 PM, Burr Sutter wrote: > It is time to get our simulator skins upgraded > > Will iPhone3 or 4 still run iOS7? > > Please comment here: > https://issues.jboss.org/browse/JBDS-2960 > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140313/25a9bcb7/attachment.html From matzew at apache.org Thu Mar 13 09:01:57 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 14:01:57 +0100 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: On Thu, Mar 13, 2014 at 12:59 PM, Bruno Oliveira wrote: > Good morning slackers, moving forward with my attempt to put pants on > passphrases. I would like to discuss how the REST API would be with the > change, because is better to have feedback instead of work for days and > waste some time. > > Register push app: > > - HTTP request > > Remain unchanged > > - HTTP response > > {"id":"2095ab1a-a569-4ae2-a43c-a86b83041592", > "name":"MyApp", > "description":"awesome app", > "pushApplicationID":"ca99487d-6387-41bd-b393-0ce480977efe", > "masterSecret":"b315d524-e9f9-4d04-946c-b73278ff29be", > "developer":"admin", > "androidVariants":[], > "simplePushVariants":[], > "chromePackagedAppVariants":[], > > "publicKey":"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEpsPA31qRWrtiAhnpGBzgwoE435c18gD42y13urb0JSdx4AHQRthhAUFVnu+RqUU8NTp9tGnEEhyBZfbV67arVw==", > "nonce":"6KbYGZKvTusU+IL3sdY9g==" > "iosvariants":[]} > > > publicKey: Is the public key created per application and will be optional > for developers who do care about security. If for some reason they don't > want to encrypt their passphrase or certificate, that's ok. > > nonce: 16 bytes non-deterministic used to encrypt the data on the server > > Note: Both would be stored into UPS database (not perfect, but a good > start) > storing both on the server (initially) is fine > > Keep in mind that this is just the initial idea, for example, masterSecret > should never return in clear. To the further interactions it will be fixed > establishing a key agreement between client and server and encrypt the > whole response (only for sensitive data). Yeah, I know, we are protected by > SSL, but we shouldn't trust on it. > > > iOS Variant: > > - HTTP request > > Remain unchanged, but now certificate and passphrase can be send > encrypted and the server will store it. > encrptyed w/ the help of the public-key ? > > - HTTP response > > Remain unchaged > > Sender: > > - HTTP request > > Remain unchanged, w/ "unchanged" you basically mean the payload of the "Send request" is the same as it is today, right ? > but now the server will search for the application ID and retrieve the > public key to decrypt application's passphrase > Ok, that's internal details. So the server basically deprcypts both: cert and its passphrase, in order to establish the connection to APNs > > - HTTP response > > Remain unchanged > > > AeroGear Clients > > - cURL > > Yesterday I had the amusing experience of dig into the sources of OpenSSL > and their documentation, to see how people could encrypt it from the > command line. If I recommend that people would remember my name for the > eternity in a bad way. Another insane idea was to provide encoders for GPG. > The simplest idea, I think, would be provide code for people encrypt their > passphrase and certificate, instead of trust in some software. > but that's really just for the "registration part", right ? I don't care that much about a cumbersome API there :-) Because in 99% of all cases the actual registration (and cert/passphrase upload) is done via the sexy Admin UI. The CURL for the send stays the same as it is today, right ? > > - aerogear-unifiedpush-java-client > > No problem to implement it. > > - aerogear-simplepush-java-client > > No problem to implement it. > > - aerogear-simplepush-node-client > > Not so easy, but they do OpenSSL behind the scenes > > - aerogear-unifiedpush-nodejs-client > > Not so easy, but they do OpenSSL behind the scenes > > > So, what do you think? Yay/Nay? I would never use that? > > The goal is to provide secure alternatives to developers, but if the whole > process will turn into a pain, I won't move forward. > It looks like it goes towards the right direction! Thanks for looking into it > > > > > > -- > abstractj > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140313/ff864f03/attachment.html From matzew at apache.org Thu Mar 13 09:03:23 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 14:03:23 +0100 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: On Thu, Mar 13, 2014 at 1:45 PM, Bruno Oliveira wrote: > That would make sense into the Sender request, once we don't have ways to > identify if the data was encrypted or not, something like "--header > "protected: true" (always optional). For example: > hrm - not sure I like that 'protected' header on the SEND > > > curl -3 -u "{PushApplicationID}:{MasterSecret}" > -v -H "Accept: application/json" -H "Content-type: application/json" > --header "protected: true" > -X POST > > -d '{ > "variants" : ["c3f0a94f-48de-4b77-a08e-68114460857e", > "444939cd-ae63-4ce1-96a4-de74b77e3737" ....], > "categories" : ["someCategory"], > "alias" : ["user at account.com", "jay at redhat.org", ....], > "deviceType" : ["iPad", "AndroidTablet", "web"], > > "message": {"key":"value", "key2":"other value", "alert":"HELLO!"}, > "simple-push": "version=123" > }' > > https://SERVER:PORT/CONTEXT/rest/sender > > Does it make sense to you? In the future with the key agreement, that > might not be necessary. > > -- > abstractj > > On March 13, 2014 at 9:33:07 AM, Sebastien Blanc (scm.blanc at gmail.com) > wrote: > > > Shouldn't there be a flag in the request telling the cert and > > passphrase are encrypted or not ? Or maybe the server can detect > > by itself if it's encrypted or not . > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140313/a0296bb4/attachment.html From matzew at apache.org Thu Mar 13 09:04:30 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 14:04:30 +0100 Subject: [aerogear-dev] Skins In-Reply-To: <96E9D6CC-C5A6-4F6E-82A8-1A88B52FDDDA@redhat.com> References: <63FCBBA8-B575-4138-B04D-B538A7E7B140@redhat.com> <96E9D6CC-C5A6-4F6E-82A8-1A88B52FDDDA@redhat.com> Message-ID: On Thu, Mar 13, 2014 at 2:00 PM, Burr Sutter wrote: > > On Mar 13, 2014, at 8:51 AM, Matthias Wessendorf > wrote: > > Was this post supposed to be posted to a different list ? > > No - these skins are a subset of the devices the Aerogear aims to support. > :-) > Ah! *check* :-) > > > > Anyways, iPhone3 zero iOS7 > > OK - I think we should drop iPhone 3 from the list - it is getting > cluttered and we need to add in more Android devices, as they have a higher > variety of screen dimensions. > If that's OK for the JBDS team, sure let's say "adios iPhone 3" > > > > Check here: > http://www.apple.com/ios/features/ > > "OS 7 is compatible with" > > > > On Thu, Mar 13, 2014 at 1:43 PM, Burr Sutter wrote: > >> It is time to get our simulator skins upgraded >> >> Will iPhone3 or 4 still run iOS7? >> >> Please comment here: >> https://issues.jboss.org/browse/JBDS-2960 >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140313/7fe70e52/attachment-0001.html From bruno at abstractj.org Thu Mar 13 09:16:59 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 13 Mar 2014 10:16:59 -0300 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: Ahoy, regarding the HTTP header we can move it to the body. What would you suggest? Other answers inline. -- abstractj On March 13, 2014 at 10:02:04 AM, Matthias Wessendorf (matzew at apache.org) wrote: > On Thu, Mar 13, 2014 at 12:59 PM, Bruno Oliveira wrote: > > iOS Variant: > > > > - HTTP request > > > > Remain unchanged, but now certificate and passphrase can be send > > encrypted and the server will store it. > > > > > encrptyed w/ the help of the public-key ? Totally correct > > > > > > > > - HTTP response > > > > Remain unchaged > > > > Sender: > > > > - HTTP request > > > > Remain unchanged, > > > > w/ "unchanged" you basically mean the payload of the "Send request" is the > same as it is today, right ? Correct. But with we agree on the flag, might be necessary to include something like ?protected: true? as optional argument. Or any other thing to let the server know. > > > > > but now the server will search for the application ID and retrieve the > > public key to decrypt application's passphrase > > > > > Ok, that's internal details. So the server basically deprcypts both: cert > and its passphrase, in order to establish the connection to APNs Correct > > > > > > AeroGear Clients > > > > - cURL > > > > Yesterday I had the amusing experience of dig into the sources of OpenSSL > > and their documentation, to see how people could encrypt it from the > > command line. If I recommend that people would remember my name for the > > eternity in a bad way. Another insane idea was to provide encoders for GPG. > > The simplest idea, I think, would be provide code for people encrypt their > > passphrase and certificate, instead of trust in some software. > > > > but that's really just for the "registration part", right ? I don't care > that much about a cumbersome API there :-) Because in 99% of all cases the > actual registration (and cert/passphrase upload) is done via the sexy Admin > UI. > > > The CURL for the send stays the same as it is today, right ? Correct. The sexy admin UI is not really a concern to me, but the clients external to it. The goal is mostly provide options for people encrypt their thing. > > > > > It looks like it goes towards the right direction! > > Thanks for looking into it > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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 Thu Mar 13 09:18:54 2014 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 13 Mar 2014 09:18:54 -0400 (EDT) Subject: [aerogear-dev] Skins In-Reply-To: <96E9D6CC-C5A6-4F6E-82A8-1A88B52FDDDA@redhat.com> References: <63FCBBA8-B575-4138-B04D-B538A7E7B140@redhat.com> <96E9D6CC-C5A6-4F6E-82A8-1A88B52FDDDA@redhat.com> Message-ID: Sent from my iPhone > On Mar 13, 2014, at 9:01 AM, Burr Sutter wrote: > > >> On Mar 13, 2014, at 8:51 AM, Matthias Wessendorf wrote: >> >> Was this post supposed to be posted to a different list ? > No - these skins are a subset of the devices the Aerogear aims to support. :-) Aren't we supporting OS's not devices > >> >> >> Anyways, iPhone3 zero iOS7 > OK - I think we should drop iPhone 3 from the list - it is getting cluttered and we need to add in more Android devices, as they have a higher variety of screen dimensions. > > >> >> Check here: >> http://www.apple.com/ios/features/ >> >> "OS 7 is compatible with" >> >> >> >>> On Thu, Mar 13, 2014 at 1:43 PM, Burr Sutter wrote: >>> It is time to get our simulator skins upgraded >>> >>> Will iPhone3 or 4 still run iOS7? >>> >>> Please comment here: >>> https://issues.jboss.org/browse/JBDS-2960 >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140313/c7eeef3f/attachment.html From bsutter at redhat.com Thu Mar 13 09:25:17 2014 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 13 Mar 2014 09:25:17 -0400 Subject: [aerogear-dev] Skins In-Reply-To: References: <63FCBBA8-B575-4138-B04D-B538A7E7B140@redhat.com> <96E9D6CC-C5A6-4F6E-82A8-1A88B52FDDDA@redhat.com> Message-ID: On Mar 13, 2014, at 9:18 AM, Luke Holmquist wrote: > > > Sent from my iPhone > > On Mar 13, 2014, at 9:01 AM, Burr Sutter wrote: > >> >> On Mar 13, 2014, at 8:51 AM, Matthias Wessendorf wrote: >> >>> Was this post supposed to be posted to a different list ? >> No - these skins are a subset of the devices the Aerogear aims to support. :-) > > Aren't we supporting OS's not devices Yes - hence my question around iPhone 3 - I think it has 'aged out' But our tooling has targets a combo of OS + Device to help with testing. We won't have a skin for every combo but I do like proper coverage of the Apple & Samsung devices as they tend to have marketshare leadership. Plus, the end-user can always build their own skin. > > >> >>> >>> >>> Anyways, iPhone3 zero iOS7 >> OK - I think we should drop iPhone 3 from the list - it is getting cluttered and we need to add in more Android devices, as they have a higher variety of screen dimensions. >> >> >>> >>> Check here: >>> http://www.apple.com/ios/features/ >>> >>> "OS 7 is compatible with" >>> >>> >>> >>> On Thu, Mar 13, 2014 at 1:43 PM, Burr Sutter wrote: >>> It is time to get our simulator skins upgraded >>> >>> Will iPhone3 or 4 still run iOS7? >>> >>> Please comment here: >>> https://issues.jboss.org/browse/JBDS-2960 >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140313/48d93f65/attachment.html From corinnekrych at gmail.com Thu Mar 13 10:07:37 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 13 Mar 2014 15:07:37 +0100 Subject: [aerogear-dev] Cordova Plugin Release 0.0.3 In-Reply-To: <86621CFB-E147-4706-B7DE-FF448D88A20F@redhat.com> References: <86621CFB-E147-4706-B7DE-FF448D88A20F@redhat.com> Message-ID: <38441E2A-206C-45A1-9539-B40A4FB46C5A@gmail.com> Hello Erik I think you forgot to push release brancg to aerogear repo. I?ve tested using edewit release branch. I?m on iOS7.0.6 with Xcode 5.0.2. I?ve uninstall previous version of plugin on my codova app and reinstall latest. but when doing cordova build I run into this compilation warning and link error: /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push/PushPlugin.m:92:80: warning: incompatible pointer types sending 'NSUserDefaults *' to parameter of type 'NSDictionary *' [-Wincompatible-pointer-types] [registration registerWithClientInfo:[self pushConfig:deviceToken withDict:userDefaults] success:^() { ^~~~~~~~~~~~ /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push/PushPlugin.m:179:103: note: passing argument to parameter 'options' here - (void (^)(id ))pushConfig:(NSData *)deviceToken withDict:(NSDictionary *)options { ^ 1 warning generated. d build/emulator/Greach.app/Greach normal i386 cd /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios setenv IPHONEOS_DEPLOYMENT_TARGET 5.0 setenv PATH "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/corinne/.rvm/gems/ruby-2.0.0-p247/bin:/Users/corinne/.rvm/gems/ruby-2.0.0-p247 at global/bin:/Users/corinne/.rvm/rubies/ruby-2.0.0-p247/bin:/Users/corinne/.rvm/bin:/opt/local/bin:/opt/local/sbin:/Users/corinne/.gvm/groovy/current/bin:/Users/corinne/.gvm/grails/current/bin:/Users/corinne/.gvm/griffon/current/bin:/Users/corinne/.gvm/gradle/current/bin:/Users/corinne/.gvm/vertx/current/bin:/Users/corinne/.gvm/bin:/Users/corinne/.gvm/ext:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Users/corinne/bin/apache-maven-3.1.1/bin:/usr/local/heroku/bin:/Users/corinne/bin/scala-2.11.0-M4/bin:/Users/corinne/bin/forge-distribution-1.4.1.Final/bin:/Library/Java/JavaVirtualMachines/jdk1.7.0_15.jdk/Contents/Home/bin:.:/Users/corinne/bin/mongodb-osx-x86_64-2.2.3/bin:/Users/corinne/bin/adt/sdk/tools:/Users/corinne/bin/adt/sdk/platform-tools:/Users/corinne/aerogear/vert.x/build/vert.x-2.0.0-beta4-SNAPSHOT/bin" /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk -L/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator -L/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push -F/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator -filelist /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/Greach.build/Debug-iphonesimulator/Greach.build/Objects-normal/i386/Greach.LinkFileList -Xlinker -objc_abi_version -Xlinker 2 -weak_framework CoreFoundation -weak_framework UIKit -weak_framework AVFoundation -weak_framework CoreMedia -weak-lSystem -force_load /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/libCordova.a -ObjC -fobjc-arc -fobjc-link-runtime -Xlinker -no_implicit_dylibs -mios-simulator-version-min=5.0 -framework AssetsLibrary /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/libCordova.a -framework CoreGraphics -framework MobileCoreServices -framework CoreLocation -lpush-sdk -lpush-sdk-0.8.1 -framework Security -framework Foundation -framework SystemConfiguration -Xlinker -dependency_info -Xlinker /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/Greach.build/Debug-iphonesimulator/Greach.build/Objects-normal/i386/Greach_dependency_info.dat -o /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/Greach.app/Greach ld: library not found for -lpush-sdk clang: error: linker command failed with exit code 1 (use -v to see invocation) ** BUILD FAILED ** ++ Corinne On 13 Mar 2014, at 11:19, Erik Jan de Wit wrote: > Hi Folks, > > This is a heads up for the release of the Cordova Push Plugin 0.0.3, this release solves a number of minor issues. > https://github.com/aerogear/aerogear-pushplugin-cordova/pull/16 > > For testing clone the project and switch to the release branch and install > > git clone https://github.com/aerogear/aerogear-pushplugin-cordova.git > git checkout -b release > cordova plugin install > If they aren't any objections or remarks I will release the bits to bintray on Friday afternoon > > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From corinnekrych at gmail.com Thu Mar 13 10:15:10 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 13 Mar 2014 15:15:10 +0100 Subject: [aerogear-dev] Cordova Plugin Release 0.0.3 In-Reply-To: <38441E2A-206C-45A1-9539-B40A4FB46C5A@gmail.com> References: <86621CFB-E147-4706-B7DE-FF448D88A20F@redhat.com> <38441E2A-206C-45A1-9539-B40A4FB46C5A@gmail.com> Message-ID: Hello again Erik Actually doing : cordova platform remove iOS and then adding it again from fresh, sorted out my issue. It works just fine. ++ Corinne On 13 Mar 2014, at 15:07, Corinne Krych wrote: > Hello Erik > > I think you forgot to push release brancg to aerogear repo. I?ve tested using edewit release branch. I?m on iOS7.0.6 with Xcode 5.0.2. > I?ve uninstall previous version of plugin on my codova app and reinstall latest. but when doing cordova build I run into this compilation warning and link error: > > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push/PushPlugin.m:92:80: warning: > incompatible pointer types sending 'NSUserDefaults *' to parameter of type 'NSDictionary *' [-Wincompatible-pointer-types] > [registration registerWithClientInfo:[self pushConfig:deviceToken withDict:userDefaults] success:^() { > ^~~~~~~~~~~~ > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push/PushPlugin.m:179:103: note: > passing argument to parameter 'options' here > - (void (^)(id ))pushConfig:(NSData *)deviceToken withDict:(NSDictionary *)options { > ^ > 1 warning generated. > > d build/emulator/Greach.app/Greach normal i386 > cd /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios > setenv IPHONEOS_DEPLOYMENT_TARGET 5.0 > setenv PATH "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/corinne/.rvm/gems/ruby-2.0.0-p247/bin:/Users/corinne/.rvm/gems/ruby-2.0.0-p247 at global/bin:/Users/corinne/.rvm/rubies/ruby-2.0.0-p247/bin:/Users/corinne/.rvm/bin:/opt/local/bin:/opt/local/sbin:/Users/corinne/.gvm/groovy/current/bin:/Users/corinne/.gvm/grails/current/bin:/Users/corinne/.gvm/griffon/current/bin:/Users/corinne/.gvm/gradle/current/bin:/Users/corinne/.gvm/vertx/current/bin:/Users/corinne/.gvm/bin:/Users/corinne/.gvm/ext:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Users/corinne/bin/apache-maven-3.1.1/bin:/usr/local/heroku/bin:/Users/corinne/bin/scala-2.11.0-M4/bin:/Users/corinne/bin/forge-distribution-1.4.1.Final/bin:/Library/Java/JavaVirtualMachines/jdk1.7.0_15.jdk/Contents/Home/bin:.:/Users/corinne/bin/mongodb-osx-x86_64-2.2.3/bin:/Users/corinne/bin/adt/sdk/tools:/Users/corinne/bin/adt/sdk/platform-tools:/Users/corinne/aerogear/vert.x/build/vert.x-2.0.0-beta4-SNAPSHOT/bin" > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk -L/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator -L/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push -F/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator -filelist /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/Greach.build/Debug-iphonesimulator/Greach.build/Objects-normal/i386/Greach.LinkFileList -Xlinker -objc_abi_version -Xlinker 2 -weak_framework CoreFoundation -weak_framework UIKit -weak_framework AVFoundation -weak_framework CoreMedia -weak-lSystem -force_load /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/libCordova.a -ObjC -fobjc-arc -fobjc-link-runtime -Xlinker -no_implicit_dylibs -mios-simulator-version-min=5.0 -framework AssetsLibrary /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/libCordova.a -framework CoreGraphics -framework MobileCoreServices -framework CoreLocation -lpush-sdk -lpush-sdk-0.8.1 -framework Security -framework Foundation -framework SystemConfiguration -Xlinker -dependency_info -Xlinker /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/Greach.build/Debug-iphonesimulator/Greach.build/Objects-normal/i386/Greach_dependency_info.dat -o /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/Greach.app/Greach > ld: library not found for -lpush-sdk > clang: error: linker command failed with exit code 1 (use -v to see invocation) > > ** BUILD FAILED ** > > ++ > Corinne > > On 13 Mar 2014, at 11:19, Erik Jan de Wit wrote: > >> Hi Folks, >> >> This is a heads up for the release of the Cordova Push Plugin 0.0.3, this release solves a number of minor issues. >> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/16 >> >> For testing clone the project and switch to the release branch and install >> >> git clone https://github.com/aerogear/aerogear-pushplugin-cordova.git >> git checkout -b release >> cordova plugin install >> If they aren't any objections or remarks I will release the bits to bintray on Friday afternoon >> >> Cheers, >> Erik Jan >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > From scm.blanc at gmail.com Thu Mar 13 10:16:54 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 13 Mar 2014 15:16:54 +0100 Subject: [aerogear-dev] Cordova Plugin Release 0.0.3 In-Reply-To: References: <86621CFB-E147-4706-B7DE-FF448D88A20F@redhat.com> <38441E2A-206C-45A1-9539-B40A4FB46C5A@gmail.com> Message-ID: Is that something related to the plugin or cordova itself that we need to remove/add again the platform when updating the plugin ? On Thu, Mar 13, 2014 at 3:15 PM, Corinne Krych wrote: > Hello again Erik > > Actually doing : > cordova platform remove iOS > and then adding it again from fresh, sorted out my issue. > > It works just fine. > > ++ > Corinne > > On 13 Mar 2014, at 15:07, Corinne Krych wrote: > > > Hello Erik > > > > I think you forgot to push release brancg to aerogear repo. I've tested > using edewit release branch. I'm on iOS7.0.6 with Xcode 5.0.2. > > I've uninstall previous version of plugin on my codova app and reinstall > latest. but when doing cordova build I run into this compilation warning > and link error: > > > > > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push/PushPlugin.m:92:80: > warning: > > incompatible pointer types sending 'NSUserDefaults *' to parameter > of type 'NSDictionary *' [-Wincompatible-pointer-types] > > [registration registerWithClientInfo:[self pushConfig:deviceToken > withDict:userDefaults] success:^() { > > > ^~~~~~~~~~~~ > > > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push/PushPlugin.m:179:103: > note: > > passing argument to parameter 'options' here > > - (void (^)(id ))pushConfig:(NSData > *)deviceToken withDict:(NSDictionary *)options { > > > ^ > > 1 warning generated. > > > > d build/emulator/Greach.app/Greach normal i386 > > cd > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios > > setenv IPHONEOS_DEPLOYMENT_TARGET 5.0 > > setenv PATH > "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/corinne/.rvm/gems/ruby-2.0.0-p247/bin:/Users/corinne/.rvm/gems/ruby-2.0.0-p247 at global > /bin:/Users/corinne/.rvm/rubies/ruby-2.0.0-p247/bin:/Users/corinne/.rvm/bin:/opt/local/bin:/opt/local/sbin:/Users/corinne/.gvm/groovy/current/bin:/Users/corinne/.gvm/grails/current/bin:/Users/corinne/.gvm/griffon/current/bin:/Users/corinne/.gvm/gradle/current/bin:/Users/corinne/.gvm/vertx/current/bin:/Users/corinne/.gvm/bin:/Users/corinne/.gvm/ext:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Users/corinne/bin/apache-maven-3.1.1/bin:/usr/local/heroku/bin:/Users/corinne/bin/scala-2.11.0-M4/bin:/Users/corinne/bin/forge-distribution-1.4.1.Final/bin:/Library/Java/JavaVirtualMachines/jdk1.7.0_15.jdk/Contents/Home/bin:.:/Users/corinne/bin/mongodb-osx-x86_64-2.2.3/bin:/Users/corinne/bin/adt/sdk/tools:/Users/corinne/bin/adt/sdk/platform-tools:/Users/corinne/aerogear/vert.x/build/vert.x-2.0.0-beta4-SNAPSHOT/bin" > > > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang > -arch i386 -isysroot > /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk > -L/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator > -L/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push > -F/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator > -filelist > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/Greach.build/Debug-iphonesimulator/Greach.build/Objects-normal/i386/Greach.LinkFileList > -Xlinker -objc_abi_version -Xlinker 2 -weak_framework CoreFoundation > -weak_framework UIKit -weak_framework AVFoundation -weak_framework > CoreMedia -weak-lSystem -force_load > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/libCordova.a > -ObjC -fobjc-arc -fobjc-link-runtime -Xlinker -no_implicit_dylibs > -mios-simulator-version-min=5.0 -framework AssetsLibrary > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/libCordova.a > -framework CoreGraphics -framework MobileCoreServices -framework > CoreLocation -lpush-sdk -lpush-sdk-0.8.1 -framework Security -framework > Foundation -framework SystemConfiguration -Xlinker -dependency_info > -Xlinker > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/Greach.build/Debug-iphonesimulator/Greach.build/Objects-normal/i386/Greach_dependency_info.dat > -o > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/Greach.app/Greach > > ld: library not found for -lpush-sdk > > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > > > > ** BUILD FAILED ** > > > > ++ > > Corinne > > > > On 13 Mar 2014, at 11:19, Erik Jan de Wit wrote: > > > >> Hi Folks, > >> > >> This is a heads up for the release of the Cordova Push Plugin 0.0.3, > this release solves a number of minor issues. > >> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/16 > >> > >> For testing clone the project and switch to the release branch and > install > >> > >> git clone https://github.com/aerogear/aerogear-pushplugin-cordova.git > >> git checkout -b release > >> cordova plugin install > >> If they aren't any objections or remarks I will release the bits to > bintray on Friday afternoon > >> > >> Cheers, > >> Erik Jan > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/cb659042/attachment.html From matzew at apache.org Thu Mar 13 10:17:24 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 15:17:24 +0100 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: On Thu, Mar 13, 2014 at 2:16 PM, Bruno Oliveira wrote: > Ahoy, regarding the HTTP header we can move it to the body. What would you > suggest? > No, I'd like to avoid that protected header/body at all :-) But... if the server really can not figure out if cert. and its passphrase are encrypted, I guess I can live w/ it - for now. Ideally the SEND API stays unchanged > > Other answers inline. > > -- > abstractj > > On March 13, 2014 at 10:02:04 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > > On Thu, Mar 13, 2014 at 12:59 PM, Bruno Oliveira wrote: > > > iOS Variant: > > > > > > - HTTP request > > > > > > Remain unchanged, but now certificate and passphrase can be send > > > encrypted and the server will store it. > > > > > > > > > encrptyed w/ the help of the public-key ? > > Totally correct > Ok, good. Oh, question: do we provide a tool for the encryption? > > > > > > > > > > > > > > > - HTTP response > > > > > > Remain unchaged > > > > > > Sender: > > > > > > - HTTP request > > > > > > Remain unchanged, > > > > > > > > w/ "unchanged" you basically mean the payload of the "Send request" is > the > > same as it is today, right ? > > Correct. But with we agree on the flag, might be necessary to include > something like "protected: true" as optional argument. Or any other thing > to let the server know. > yeah, I see. Hrm - not sure I like the flag :-) Perhaps there is a way (at least for the "long run") that the server gets: Ah, it is encrypted (or not). As said the flag is not the end of the world - I just try to make the "SEND" as simple as possible :) > > > > > > > > > > but now the server will search for the application ID and retrieve the > > > public key to decrypt application's passphrase > > > > > > > > > Ok, that's internal details. So the server basically deprcypts both: cert > > and its passphrase, in order to establish the connection to APNs > > Correct > cool > > > > > > > > > > AeroGear Clients > > > > > > - cURL > > > > > > Yesterday I had the amusing experience of dig into the sources of > OpenSSL > > > and their documentation, to see how people could encrypt it from the > > > command line. If I recommend that people would remember my name for the > > > eternity in a bad way. Another insane idea was to provide encoders for > GPG. > > > The simplest idea, I think, would be provide code for people encrypt > their > > > passphrase and certificate, instead of trust in some software. > > > > > > > but that's really just for the "registration part", right ? I don't care > > that much about a cumbersome API there :-) Because in 99% of all cases > the > > actual registration (and cert/passphrase upload) is done via the sexy > Admin > > UI. > > > > > > The CURL for the send stays the same as it is today, right ? > > Correct. The sexy admin UI is not really a concern to me, but the clients > external to it. and external clients are in 99% of the cases just using SEND - not the Registration bits > The goal is mostly provide options for people encrypt their thing. > yep!! And that is great! > > > > > > > > > > It looks like it goes towards the right direction! > > > > Thanks for looking into it > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/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/20140313/ecfd97fc/attachment-0001.html From edewit at redhat.com Thu Mar 13 10:18:12 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 13 Mar 2014 15:18:12 +0100 Subject: [aerogear-dev] Cordova Plugin Release 0.0.3 In-Reply-To: References: <86621CFB-E147-4706-B7DE-FF448D88A20F@redhat.com> <38441E2A-206C-45A1-9539-B40A4FB46C5A@gmail.com> Message-ID: <48662A45-6776-47BF-947F-A3D88738149F@redhat.com> This is a cordova related issue On 13 Mar,2014, at 15:16 , Sebastien Blanc wrote: > Is that something related to the plugin or cordova itself that we need to remove/add again the platform when updating the plugin ? > > > On Thu, Mar 13, 2014 at 3:15 PM, Corinne Krych wrote: > Hello again Erik > > Actually doing : > cordova platform remove iOS > and then adding it again from fresh, sorted out my issue. > > It works just fine. > > ++ > Corinne > > On 13 Mar 2014, at 15:07, Corinne Krych wrote: > > > Hello Erik > > > > I think you forgot to push release brancg to aerogear repo. I?ve tested using edewit release branch. I?m on iOS7.0.6 with Xcode 5.0.2. > > I?ve uninstall previous version of plugin on my codova app and reinstall latest. but when doing cordova build I run into this compilation warning and link error: > > > > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push/PushPlugin.m:92:80: warning: > > incompatible pointer types sending 'NSUserDefaults *' to parameter of type 'NSDictionary *' [-Wincompatible-pointer-types] > > [registration registerWithClientInfo:[self pushConfig:deviceToken withDict:userDefaults] success:^() { > > ^~~~~~~~~~~~ > > /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push/PushPlugin.m:179:103: note: > > passing argument to parameter 'options' here > > - (void (^)(id ))pushConfig:(NSData *)deviceToken withDict:(NSDictionary *)options { > > ^ > > 1 warning generated. > > > > d build/emulator/Greach.app/Greach normal i386 > > cd /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios > > setenv IPHONEOS_DEPLOYMENT_TARGET 5.0 > > setenv PATH "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/corinne/.rvm/gems/ruby-2.0.0-p247/bin:/Users/corinne/.rvm/gems/ruby-2.0.0-p247 at global/bin:/Users/corinne/.rvm/rubies/ruby-2.0.0-p247/bin:/Users/corinne/.rvm/bin:/opt/local/bin:/opt/local/sbin:/Users/corinne/.gvm/groovy/current/bin:/Users/corinne/.gvm/grails/current/bin:/Users/corinne/.gvm/griffon/current/bin:/Users/corinne/.gvm/gradle/current/bin:/Users/corinne/.gvm/vertx/current/bin:/Users/corinne/.gvm/bin:/Users/corinne/.gvm/ext:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Users/corinne/bin/apache-maven-3.1.1/bin:/usr/local/heroku/bin:/Users/corinne/bin/scala-2.11.0-M4/bin:/Users/corinne/bin/forge-distribution-1.4.1.Final/bin:/Library/Java/JavaVirtualMachines/jdk1.7.0_15.jdk/Contents/Home/bin:.:/Users/corinne/bin/mongodb-osx-x86_64-2.2.3/bin:/Users/corinne/bin/adt/sdk/tools:/Users/corinne/bin/adt/sdk/platform-tools:/Users/corinne/aerogear/vert.x/build/vert.x-2.0.0-beta4-SNAPSHOT/bin" > > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk -L/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator -L/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/Greach/Plugins/org.jboss.aerogear.cordova.push -F/Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator -filelist /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/Greach.build/Debug-iphonesimulator/Greach.build/Objects-normal/i386/Greach.LinkFileList -Xlinker -objc_abi_version -Xlinker 2 -weak_framework CoreFoundation -weak_framework UIKit -weak_framework AVFoundation -weak_framework CoreMedia -weak-lSystem -force_load /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/libCordova.a -ObjC -fobjc-arc -fobjc-link-runtime -Xlinker -no_implicit_dylibs -mios-simulator-version-min=5.0 -framework AssetsLibrary /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/libCordova.a -framework CoreGraphics -framework MobileCoreServices -framework CoreLocation -lpush-sdk -lpush-sdk-0.8.1 -framework Security -framework Foundation -framework SystemConfiguration -Xlinker -dependency_info -Xlinker /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/Greach.build/Debug-iphonesimulator/Greach.build/Objects-normal/i386/Greach_dependency_info.dat -o /Users/corinne/aerogear/grails/totoAeroGear/greachCordova/platforms/ios/build/emulator/Greach.app/Greach > > ld: library not found for -lpush-sdk > > clang: error: linker command failed with exit code 1 (use -v to see invocation) > > > > ** BUILD FAILED ** > > > > ++ > > Corinne > > > > On 13 Mar 2014, at 11:19, Erik Jan de Wit wrote: > > > >> Hi Folks, > >> > >> This is a heads up for the release of the Cordova Push Plugin 0.0.3, this release solves a number of minor issues. > >> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/16 > >> > >> For testing clone the project and switch to the release branch and install > >> > >> git clone https://github.com/aerogear/aerogear-pushplugin-cordova.git > >> git checkout -b release > >> cordova plugin install > >> If they aren't any objections or remarks I will release the bits to bintray on Friday afternoon > >> > >> Cheers, > >> Erik Jan > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/0a2c0eb8/attachment.html From bruno at abstractj.org Thu Mar 13 10:18:38 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 13 Mar 2014 11:18:38 -0300 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: nswers inline. --? abstractj On March 13, 2014 at 10:29:48 AM, Matthias Wessendorf (matzew at apache.org) wrote: > On Thu, Mar 13, 2014 at 2:16 PM, Bruno Oliveira wrote: >? > > Ahoy, regarding the HTTP header we can move it to the body. What would you > > suggest? > > >? > No, I'd like to avoid that protected header/body at all :-) >? > But... if the server really can not figure out if cert. and its passphrase > are encrypted, I guess I can live w/ it - for now. > Ideally the SEND API stays unchanged We can if we add one step further. Let me put the new idea in a gist (https://gist.github.com/abstractj/55905ed53fce2ca22388).? If developer requested a key pair, we create a new one for that PushApplicationID and check it on Sender if exists a key pair for that application. Into this way we make encryption totally optional. Does it make sense? ? > > > > > > encrptyed w/ the help of the public-key ? > > > > Totally correct > > >? > Ok, good. Oh, question: do we provide a tool for the encryption? Sure thing, I?m all for make it easy. > > Correct. But with we agree on the flag, might be necessary to include > > something like "protected: true" as optional argument. Or any other thing > > to let the server know. > > >? > yeah, I see. Hrm - not sure I like the flag :-) > Perhaps there is a way (at least for the "long run") that the server gets: > Ah, it is encrypted (or not). >? > As said the flag is not the end of the world - I just try to make the > "SEND" as simple as possible :) If we agree on that gist, we don?t need this flag anymore. Let me know what do you guys think about the idea. From matzew at apache.org Thu Mar 13 10:53:49 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 15:53:49 +0100 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: On Thu, Mar 13, 2014 at 3:18 PM, Bruno Oliveira wrote: > nswers inline. > > -- > abstractj > > On March 13, 2014 at 10:29:48 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > > On Thu, Mar 13, 2014 at 2:16 PM, Bruno Oliveira wrote: > > > > > Ahoy, regarding the HTTP header we can move it to the body. What would > you > > > suggest? > > > > > > > No, I'd like to avoid that protected header/body at all :-) > > > > But... if the server really can not figure out if cert. and its > passphrase > > are encrypted, I guess I can live w/ it - for now. > > Ideally the SEND API stays unchanged > > We can if we add one step further. Let me put the new idea in a gist ( > https://gist.github.com/abstractj/55905ed53fce2ca22388). > > If developer requested a key pair, we create a new one for that > PushApplicationID and check it on Sender if exists a key pair for that > application. Into this way we make encryption totally optional. > > Does it make sense? > Not sure I fully understand - let's see :) Steps (the encryption case): 1) create/register Push Application 2) request the optional publicKey 3) use the public key (w/ some tool) to encrtypt the certificate together with its passphrase 4) on iOS variant, I provide the encrypted certificate and the encrypted passphrase 5) For sending: use the same CURL as today - internally it checks: Does pushApp contain publicKey - if YES, do the decryption dance; So that basically means: if I execute 2) (request the publicKey), submitting encrypted certificate/passphrase is now required So, yeah that sounds good to me > > > > > > > > > encrptyed w/ the help of the public-key ? > > > > > > Totally correct > > > > > > > Ok, good. Oh, question: do we provide a tool for the encryption? > > Sure thing, I'm all for make it easy. > yay! > > > > Correct. But with we agree on the flag, might be necessary to include > > > something like "protected: true" as optional argument. Or any other > thing > > > to let the server know. > > > > > > > yeah, I see. Hrm - not sure I like the flag :-) > > Perhaps there is a way (at least for the "long run") that the server > gets: > > Ah, it is encrypted (or not). > > > > As said the flag is not the end of the world - I just try to make the > > "SEND" as simple as possible :) > > If we agree on that gist, we don't need this flag anymore. > > Let me know what do you guys think about the idea. > I *think* it sounds good ;-) -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/20140313/2011e13b/attachment-0001.html From matzew at apache.org Thu Mar 13 11:26:34 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 16:26:34 +0100 Subject: [aerogear-dev] Keycloak Alpha-4 (was: Re: [keycloak-dev] Alpha-3 issues) Message-ID: On Thu, Mar 13, 2014 at 4:12 PM, Bill Burke wrote: > I was able to reproduce and fix it. alpha 4 release incoming. > > Besides the previous NPE on user creation: I can confirm the alpha-4 works also fine w/ the UPS branch that aims to integrate Keycloak! Thanks for the quick reply! Cheers! Matthias > > On 3/13/2014 11:00 AM, Matthias Wessendorf wrote: > >> just saw >> >> https://github.com/keycloak/keycloak/pull/294 >> >> >> let me build it locally and give it a quick run here >> >> >> -M >> >> >> On Thu, Mar 13, 2014 at 3:56 PM, Matthias Wessendorf > > wrote: >> >> damn! email - how does it work? >> >> Sorry, but by accident I did not reply to the list :) >> >> * cache clearing did help; >> >> * Regarding the NPE Bill replied "Ok, I'll take a look and push >> another release. Probably just need a null check." >> >> >> -M >> >> On Thu, Mar 13, 2014 at 2:43 PM, Matthias Wessendorf >> > wrote: >> >> >> >> >> On Thu, Mar 13, 2014 at 2:21 PM, Bill Burke > > wrote: >> >> >> >> On 3/13/2014 5:15 AM, Matthias Wessendorf wrote: >> > Hello, >> > >> > when deploying the |deployments| folder of the >> > /keycloak-war-dist-all-1.0-alpha-3/ I noticed the >> following/WARN/: >> > >> > |10:02:18,449 WARN [org.jboss.as.ee >> ] (MSC >> >> service thread 1-9) JBAS011006: Not installing optional >> component >> org.jboss.resteasy.plugins.server.servlet. >> Servlet3AsyncHttpRequest$Servlet3ExecutionContext$ >> Servle3AsychronousResponse >> due to exception: >> org.jboss.as.server.deployment.DeploymentUnitProcessingExcept >> ion: >> JBAS011054: Could not find default constructor for class >> org.jboss.resteasy.plugins.server.servlet. >> Servlet3AsyncHttpRequest$Servlet3ExecutionContext$ >> Servle3AsychronousResponse >> > at >> org.jboss.as.ee.component.ComponentDescription$ >> DefaultComponentConfigurator.configure(ComponentDescription.java:606) >> > at >> org.jboss.as.ee.component.deployers. >> EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor >> .java:81) >> > at >> org.jboss.as.server.deployment.DeploymentUnitPhaseService. >> start(DeploymentUnitPhaseService.java:113) >> [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] >> > at >> org.jboss.msc.service.ServiceControllerImpl$ >> StartTask.startService(ServiceControllerImpl.java:1811) >> [jboss-msc-1.0.2.GA.jar:1.0.2.GA >> ] >> > at >> org.jboss.msc.service.ServiceControllerImpl$StartTask.run( >> ServiceControllerImpl.java:1746) >> [jboss-msc-1.0.2.GA.jar:1.0.2.GA >> ] >> > at >> java.util.concurrent.ThreadPoolExecutor.runWorker( >> ThreadPoolExecutor.java:1110) >> [rt.jar:1.7.0_09] >> > at >> java.util.concurrent.ThreadPoolExecutor$Worker.run( >> ThreadPoolExecutor.java:603) >> [rt.jar:1.7.0_09] >> > at java.lang.Thread.run(Thread.java:722) >> [rt.jar:1.7.0_09] >> > >> >> Haven't figured out the above ^. I assume you are running >> on EAP/AS7? >> >> >> >> Correct - JBoss AS 7.1.1-Final >> >> >> | >> > >> > Now, login (admin:admin) and the reset flow works fine. >> After creating a >> > REALM, I am on the Tab (of the new realm), but there I >> notice a few >> > "Page not found..." messages for these links: >> > >> >> Try clearing your browser cache and trying everything again. >> >> >> >> great! now I could create some roles and set default roles. >> >> >> However, the NPE on user creation is still present: >> >> >> >> Caused by: java.lang.NullPointerException >> >> at >> org.keycloak.services.resources.admin.UsersResource. >> updateUserFromRep(UsersResource.java:123) >> [keycloak-services-1.0-alpha-3.jar:] >> >> at >> org.keycloak.services.resources.admin.UsersResource. >> createUser(UsersResource.java:106) >> [keycloak-services-1.0-alpha-3.jar:] >> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> [rt.jar:1.7.0_09] >> >> at >> sun.reflect.NativeMethodAccessorImpl.invoke( >> NativeMethodAccessorImpl.java:57) >> [rt.jar:1.7.0_09] >> >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke( >> DelegatingMethodAccessorImpl.java:43) >> [rt.jar:1.7.0_09] >> >> at java.lang.reflect.Method.invoke(Method.java:601) >> [rt.jar:1.7.0_09] >> >> at >> org.jboss.resteasy.core.MethodInjectorImpl.invoke( >> MethodInjectorImpl.java:137) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> at >> org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget( >> ResourceMethodInvoker.java:280) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> at >> org.jboss.resteasy.core.ResourceMethodInvoker.invoke( >> ResourceMethodInvoker.java:234) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> at >> org.jboss.resteasy.core.ResourceLocatorInvoker. >> invokeOnTargetObject(ResourceLocatorInvoker.java:140) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> at >> org.jboss.resteasy.core.ResourceLocatorInvoker.invoke( >> ResourceLocatorInvoker.java:109) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> at >> org.jboss.resteasy.core.ResourceLocatorInvoker. >> invokeOnTargetObject(ResourceLocatorInvoker.java:135) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> at >> org.jboss.resteasy.core.ResourceLocatorInvoker.invoke( >> ResourceLocatorInvoker.java:109) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> at >> org.jboss.resteasy.core.ResourceLocatorInvoker. >> invokeOnTargetObject(ResourceLocatorInvoker.java:135) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> at >> org.jboss.resteasy.core.ResourceLocatorInvoker.invoke( >> ResourceLocatorInvoker.java:103) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> at >> org.jboss.resteasy.core.SynchronousDispatcher.invoke( >> SynchronousDispatcher.java:356) >> [resteasy-jaxrs-3.0.6.Final.jar:] >> >> ... 22 more >> >> >> >> >> >> >> -- >> Bill Burke >> JBoss, a division of Red Hat >> http://bill.burkecentral.com >> _______________________________________________ >> keycloak-dev mailing list >> keycloak-dev at lists.jboss.org >> >> >> https://lists.jboss.org/mailman/listinfo/keycloak-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 >> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > -- 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/20140313/38fe443b/attachment.html From bruno at abstractj.org Thu Mar 13 12:39:55 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 13 Mar 2014 09:39:55 -0700 (PDT) Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: <1394728795089.be32252b@Nodemailer> Nailed it, you understanding is correct? abstractj On Thu, Mar 13, 2014 at 11:53 AM, Matthias Wessendorf wrote: > On Thu, Mar 13, 2014 at 3:18 PM, Bruno Oliveira wrote: >> nswers inline. >> >> -- >> abstractj >> >> On March 13, 2014 at 10:29:48 AM, Matthias Wessendorf (matzew at apache.org) >> wrote: >> > On Thu, Mar 13, 2014 at 2:16 PM, Bruno Oliveira wrote: >> > >> > > Ahoy, regarding the HTTP header we can move it to the body. What would >> you >> > > suggest? >> > > >> > >> > No, I'd like to avoid that protected header/body at all :-) >> > >> > But... if the server really can not figure out if cert. and its >> passphrase >> > are encrypted, I guess I can live w/ it - for now. >> > Ideally the SEND API stays unchanged >> >> We can if we add one step further. Let me put the new idea in a gist ( >> https://gist.github.com/abstractj/55905ed53fce2ca22388). >> >> If developer requested a key pair, we create a new one for that >> PushApplicationID and check it on Sender if exists a key pair for that >> application. Into this way we make encryption totally optional. >> >> Does it make sense? >> > Not sure I fully understand - let's see :) > Steps (the encryption case): > 1) create/register Push Application > 2) request the optional publicKey > 3) use the public key (w/ some tool) to encrtypt the certificate together > with its passphrase > 4) on iOS variant, I provide the encrypted certificate and the encrypted > passphrase > 5) For sending: use the same CURL as today - internally it checks: Does > pushApp contain publicKey - if YES, do the decryption dance; > So that basically means: if I execute 2) (request the publicKey), > submitting encrypted certificate/passphrase is now required > So, yeah that sounds good to me >> >> > > > >> > > > encrptyed w/ the help of the public-key ? >> > > >> > > Totally correct >> > > >> > >> > Ok, good. Oh, question: do we provide a tool for the encryption? >> >> Sure thing, I'm all for make it easy. >> > yay! >> >> > > Correct. But with we agree on the flag, might be necessary to include >> > > something like "protected: true" as optional argument. Or any other >> thing >> > > to let the server know. >> > > >> > >> > yeah, I see. Hrm - not sure I like the flag :-) >> > Perhaps there is a way (at least for the "long run") that the server >> gets: >> > Ah, it is encrypted (or not). >> > >> > As said the flag is not the end of the world - I just try to make the >> > "SEND" as simple as possible :) >> >> If we agree on that gist, we don't need this flag anymore. >> >> Let me know what do you guys think about the idea. >> > I *think* it sounds good ;-) > -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/20140313/9c9be773/attachment-0001.html From matzew at apache.org Thu Mar 13 12:46:54 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 17:46:54 +0100 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: <1394728795089.be32252b@Nodemailer> References: <1394728795089.be32252b@Nodemailer> Message-ID: On Thu, Mar 13, 2014 at 5:39 PM, Bruno Oliveira wrote: > Nailed it, you understanding is correct +1 on the updated gist > -- > abstractj > > > On Thu, Mar 13, 2014 at 11:53 AM, Matthias Wessendorf wrote: > >> >> >> >> On Thu, Mar 13, 2014 at 3:18 PM, Bruno Oliveira wrote: >> >>> nswers inline. >>> >>> -- >>> abstractj >>> >>> On March 13, 2014 at 10:29:48 AM, Matthias Wessendorf (matzew at apache.org) >>> wrote: >>> > On Thu, Mar 13, 2014 at 2:16 PM, Bruno Oliveira wrote: >>> > >>> > > Ahoy, regarding the HTTP header we can move it to the body. What >>> would you >>> > > suggest? >>> > > >>> > >>> > No, I'd like to avoid that protected header/body at all :-) >>> > >>> > But... if the server really can not figure out if cert. and its >>> passphrase >>> > are encrypted, I guess I can live w/ it - for now. >>> > Ideally the SEND API stays unchanged >>> >>> We can if we add one step further. Let me put the new idea in a gist ( >>> https://gist.github.com/abstractj/55905ed53fce2ca22388). >>> >>> If developer requested a key pair, we create a new one for that >>> PushApplicationID and check it on Sender if exists a key pair for that >>> application. Into this way we make encryption totally optional. >>> >>> Does it make sense? >>> >> >> Not sure I fully understand - let's see :) >> >> Steps (the encryption case): >> 1) create/register Push Application >> 2) request the optional publicKey >> 3) use the public key (w/ some tool) to encrtypt the certificate together >> with its passphrase >> 4) on iOS variant, I provide the encrypted certificate and the encrypted >> passphrase >> 5) For sending: use the same CURL as today - internally it checks: Does >> pushApp contain publicKey - if YES, do the decryption dance; >> >> >> So that basically means: if I execute 2) (request the publicKey), >> submitting encrypted certificate/passphrase is now required >> >> So, yeah that sounds good to me >> >> >>> >>> > > > >>> > > > encrptyed w/ the help of the public-key ? >>> > > >>> > > Totally correct >>> > > >>> > >>> > Ok, good. Oh, question: do we provide a tool for the encryption? >>> >>> Sure thing, I'm all for make it easy. >>> >> >> >> >> yay! >> >> >> >>> >>> > > Correct. But with we agree on the flag, might be necessary to include >>> > > something like "protected: true" as optional argument. Or any other >>> thing >>> > > to let the server know. >>> > > >>> > >>> > yeah, I see. Hrm - not sure I like the flag :-) >>> > Perhaps there is a way (at least for the "long run") that the server >>> gets: >>> > Ah, it is encrypted (or not). >>> > >>> > As said the flag is not the end of the world - I just try to make the >>> > "SEND" as simple as possible :) >>> >>> If we agree on that gist, we don't need this flag anymore. >>> >>> Let me know what do you guys think about the idea. >>> >> >> I *think* it sounds good ;-) >> >> -Matthias >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/461c78a8/attachment.html From kpiwko at redhat.com Thu Mar 13 12:48:11 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 13 Mar 2014 17:48:11 +0100 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: Message-ID: <20140313174811.3dd56072@kapy-ntb-x220> I believe that command line based client is important. Either Java Sender or Node.js Sender could be enhanced with non-sending functionality and wrapped to provide CLI though via airline and nodejs libs. We already have similar stuff internally for sampling random data on OpenShift carts, it is based on RestAssured/Spacelift though. It will not be that difficult to make it available upstream if use case are clear ;-) Current functionality listed at [1] > AeroGear Clients > > - cURL > > Yesterday I had the amusing experience of dig into the sources of OpenSSL and > their documentation, to see how people could encrypt it from the command > line. If I recommend that people would remember my name for the eternity in a > bad way. Another insane idea was to provide encoders for GPG. The simplest > idea, I think, would be provide code for people encrypt their passphrase and > certificate, instead of trust in some software. > [1] usage: perf-test-env [] The most commonly used perf-test-env commands are: cart-create Create OpenShift Cartridge based on latest commit in given organization, repository and branch. Requires rhc tools installed help Display help information ups-delete Deletes data from an UPS instance ups-dump Dumps all data from UPS so they are usable by performance tests ups-generate Generates data for an UPS instance See 'perf-test-env help ' for more information on a specific command. NAME perf-test-env ups-generate - Generates data for an UPS instance SYNOPSIS perf-test-env ups-generate (-a | --app-name ) [--cert-pass ] [--cert-path ] [--google-key ] [(-n | --namespace )] [--no-https] [--old-password ] (-p | --password ) [--port ] [--production] [--project-no ] --push-app-name [--simple-push] [(-u | --username )] OPTIONS -a , --app-name Name of the application on OpenShift --cert-pass Certificate passphrase --cert-path Path to iOS certificate. If set, --cert-pass is required and iOS variant is created. --google-key Google API key for Android application variant. If set, --project-no is required and Android variant is created. -n , --namespace Namespace on OpenShift, default value: mobileqa --no-https Use HTTP protocol instead of HTTPS --old-password Previous password. Default value: 123 -p , --password Password to be used for Unified Push Server login. If old-password matches, this one replaces the old one --port Port to be used for REST calls, default value: 80 or 443, depending on --no-https --production If set, certificate is marked as production one --project-no Google Project Number for Android application variant. If present, Android variant is created. --push-app-name Push application name --simple-push If set, SimplePush application variant is generated -u , --username Username to be used for Unified Push Server login, default value: admin From matzew at apache.org Thu Mar 13 12:52:48 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 17:52:48 +0100 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: <20140313174811.3dd56072@kapy-ntb-x220> References: <20140313174811.3dd56072@kapy-ntb-x220> Message-ID: On Thu, Mar 13, 2014 at 5:48 PM, Karel Piwko wrote: > I believe that command line based client is important. Either Java Sender > or Node.js Sender could be enhanced with non-sending functionality and > wrapped > to provide CLI though via airline :-))))) I totally agree - let's create a JIRA for a Java-based CLI via airline > and nodejs libs. > > We already have similar stuff internally for sampling random data on > OpenShift > carts, it is based on RestAssured/Spacelift though. It will not be that > difficult to make it available upstream if use case are clear ;-) > > Current functionality listed at [1] > > > AeroGear Clients > > > > - cURL > > > > Yesterday I had the amusing experience of dig into the sources of > OpenSSL and > > their documentation, to see how people could encrypt it from the command > > line. If I recommend that people would remember my name for the eternity > in a > > bad way. Another insane idea was to provide encoders for GPG. The > simplest > > idea, I think, would be provide code for people encrypt their passphrase > and > > certificate, instead of trust in some software. > > > [1] > usage: perf-test-env [] > > The most commonly used perf-test-env commands are: > cart-create Create OpenShift Cartridge based on latest commit in > given > organization, repository and branch. Requires rhc tools installed > help Display help information ups-delete Deletes data from > an UPS > instance ups-dump Dumps all data from UPS so they are usable by > performance tests ups-generate Generates data for an UPS instance > > See 'perf-test-env help ' for more information on a specific > command. > > NAME > perf-test-env ups-generate - Generates data for an UPS instance > > SYNOPSIS > perf-test-env ups-generate (-a | --app-name ) > [--cert-pass ] [--cert-path > ] [--google-key ] [(-n | > --namespace > )] [--no-https] [--old-password ] > (-p | --password ) [--port ] > [--production] [--project-no ] --push-app-name > > [--simple-push] [(-u | --username )] > > OPTIONS > -a , --app-name > Name of the application on OpenShift > > --cert-pass > Certificate passphrase > > --cert-path > Path to iOS certificate. If set, --cert-pass is required and > iOS > variant is created. > > --google-key > Google API key for Android application variant. If set, > --project-no > is required and Android variant is created. > > -n , --namespace > Namespace on OpenShift, default value: mobileqa > > --no-https > Use HTTP protocol instead of HTTPS > > --old-password > Previous password. Default value: 123 > > -p , --password > Password to be used for Unified Push Server login. If > old-password > matches, this one replaces the old one > > --port > Port to be used for REST calls, default value: 80 or 443, > depending > on --no-https > > --production > If set, certificate is marked as production one > > --project-no > Google Project Number for Android application variant. If > present, > Android variant is created. > > --push-app-name > Push application name > > --simple-push > If set, SimplePush application variant is generated > > -u , --username > Username to be used for Unified Push Server login, default > value: > admin > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140313/258aa08b/attachment.html From scm.blanc at gmail.com Thu Mar 13 12:59:24 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 13 Mar 2014 17:59:24 +0100 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: References: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> <161652535.9283579.1394638506889.JavaMail.zimbra@redhat.com> Message-ID: Deployed and tested with success !! +1 On Wed, Mar 12, 2014 at 6:19 PM, Matthias Wessendorf wrote: > FYI: On IRC Stefan reported the WAR from my staging repo also passes the > tests. > > > > > > > On Wed, Mar 12, 2014 at 4:39 PM, Matthias Wessendorf wrote: > >> >> >> >> On Wed, Mar 12, 2014 at 4:35 PM, Stefan Miklosovic wrote: >> >>> >>> ------------------------------ >>> >>> >>> >>> >>> On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic wrote: >>> >>>> Hello Matthias, >>>> >>>> we executed UPS integration tests on the latest commit in 0.10.x brach >>>> (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. >>>> >>> >>> >>> awesome! >>> >>>> >>>> Since you talked about Bintray, we could move this little bit further >>>> and test >>>> staged bits directly from there - meaning wars which are not on Maven >>>> Central >>>> yet but they are already on Bintray would be downloaded from there >>>> dynamically >>>> and our intergration test suite would be run directly against built >>>> (but yet unreleased) wars. >>>> >>> >>> >>> the WAR files from my private staging repo will be exactly those that I >>> upload to bintray; >>> >>> I use the private repo, to avoid an early publish (before the release is >>> really done) >>> >>> Ah, right. The discussion I had with Karel was that it would be nice to >>> test these built wars before they >>> finally reach Maven Central and Bintray would act as a staging place >>> just as your private repo right now. >>> >> >> >> feel free to use my private staging repo as your repo (it's a valid maven >> repo URL) >> http://people.apache.org/~matzew/aerogear-staging/ >> >> >> >>> >>> I am not sure if Bintray supports this but if it is possible, Bintray >>> could be exactly what your >>> "private repo" is right now, we would just make it more robust / >>> official moving from >>> your private repo somewhere (no offence) to Bintray. >>> >>> By doing this, we kind of abuse Bintray, I guess it is not primarily >>> used for staging bits but for announcing them to the world, >>> however it is technically possible. >>> >> >> yes, but I am more interested in keep my current process: >> >> * staging: my Apache account >> * release: bintray (there we have all the good stats etc) >> >> >>> >>> However feel free to cancel this idea. We are planning to test these >>> unreleased wars anyway so instead of Bintray >>> we try to download them from your private repo but I am just saying that >>> having it from Bintray seems to be better. >>> >> >> And again, these files from my private repo are exactly the same that I >> than upload to bintray (assuming the release tests are passing) >> >> -M >> >> >>> >>> - Stefan >>> >>> -Matthias >>> >>>> >>>> In other words, Bintray could be used as a staging facility for UPS. >>>> >>>> WDYT? >>>> >>>> Stefan Miklosovic >>>> Red Hat Brno - JBoss Mobile Platform >>>> >>>> e-mail: smikloso at redhat.com >>>> irc: smikloso >>>> >>>> ------------------------------ >>>> >>>> Hello, >>>> >>>> for the upcoming release we have a few, but important, tickets solved: >>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 >>>> >>>> >>>> Before finishing the release, let's see if there are issues w/ the >>>> server, hence I have staged the WAR file on my private webspace: >>>> >>>> >>>> >>>> http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ >>>> >>>> >>>> If they aren't any objections or remarks I will release the bits to >>>> bintray on Friday morning >>>> >>>> >>>> Greetings, >>>> 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140313/5ae652ae/attachment-0001.html From bsutter at redhat.com Thu Mar 13 13:09:14 2014 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 13 Mar 2014 13:09:14 -0400 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: References: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> <161652535.9283579.1394638506889.JavaMail.zimbra@redhat.com> Message-ID: <1745AA9B-5CEE-454F-A5BB-FFB836887173@redhat.com> By the way, I am really enjoying the new Test Message feature :-) curl is a pain and becomes problematic for our Windows userbase anyway. On Mar 13, 2014, at 12:59 PM, Sebastien Blanc wrote: > Deployed and tested with success !! > +1 > > > > On Wed, Mar 12, 2014 at 6:19 PM, Matthias Wessendorf wrote: > FYI: On IRC Stefan reported the WAR from my staging repo also passes the tests. > > > > > > > On Wed, Mar 12, 2014 at 4:39 PM, Matthias Wessendorf wrote: > > > > On Wed, Mar 12, 2014 at 4:35 PM, Stefan Miklosovic wrote: > > > > > On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic wrote: > Hello Matthias, > > we executed UPS integration tests on the latest commit in 0.10.x brach > (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. > > > awesome! > > Since you talked about Bintray, we could move this little bit further and test > staged bits directly from there - meaning wars which are not on Maven Central > yet but they are already on Bintray would be downloaded from there dynamically > and our intergration test suite would be run directly against built (but yet unreleased) wars. > > > the WAR files from my private staging repo will be exactly those that I upload to bintray; > > I use the private repo, to avoid an early publish (before the release is really done) > Ah, right. The discussion I had with Karel was that it would be nice to test these built wars before they > finally reach Maven Central and Bintray would act as a staging place just as your private repo right now. > > > feel free to use my private staging repo as your repo (it's a valid maven repo URL) > http://people.apache.org/~matzew/aerogear-staging/ > > > > I am not sure if Bintray supports this but if it is possible, Bintray could be exactly what your > "private repo" is right now, we would just make it more robust / official moving from > your private repo somewhere (no offence) to Bintray. > > By doing this, we kind of abuse Bintray, I guess it is not primarily used for staging bits but for announcing them to the world, > however it is technically possible. > > yes, but I am more interested in keep my current process: > > * staging: my Apache account > * release: bintray (there we have all the good stats etc) > > > However feel free to cancel this idea. We are planning to test these unreleased wars anyway so instead of Bintray > we try to download them from your private repo but I am just saying that having it from Bintray seems to be better. > > And again, these files from my private repo are exactly the same that I than upload to bintray (assuming the release tests are passing) > > -M > > > - Stefan > > -Matthias > > In other words, Bintray could be used as a staging facility for UPS. > > WDYT? > > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: smikloso at redhat.com > irc: smikloso > > Hello, > > for the upcoming release we have a few, but important, tickets solved: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 > > > Before finishing the release, let's see if there are issues w/ the server, hence I have staged the WAR file on my private webspace: > > > http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ > > > If they aren't any objections or remarks I will release the bits to bintray on Friday morning > > > Greetings, > 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/0444fc4b/attachment.html From matzew at apache.org Thu Mar 13 13:11:51 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 18:11:51 +0100 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: <1745AA9B-5CEE-454F-A5BB-FFB836887173@redhat.com> References: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> <161652535.9283579.1394638506889.JavaMail.zimbra@redhat.com> <1745AA9B-5CEE-454F-A5BB-FFB836887173@redhat.com> Message-ID: On Thu, Mar 13, 2014 at 6:09 PM, Burr Sutter wrote: > By the way, I am really enjoying the new Test Message feature :-) > IT's not only a test message :) you can use that to just reach out to users :) (think marketing apps :) ) > > curl is a pain and becomes problematic for our Windows userbase anyway. > > > On Mar 13, 2014, at 12:59 PM, Sebastien Blanc wrote: > > Deployed and tested with success !! > +1 > > > > On Wed, Mar 12, 2014 at 6:19 PM, Matthias Wessendorf wrote: > >> FYI: On IRC Stefan reported the WAR from my staging repo also passes >> the tests. >> >> >> >> >> >> >> On Wed, Mar 12, 2014 at 4:39 PM, Matthias Wessendorf wrote: >> >>> >>> >>> >>> On Wed, Mar 12, 2014 at 4:35 PM, Stefan Miklosovic wrote: >>> >>>> >>>> ------------------------------ >>>> >>>> >>>> >>>> >>>> On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic >>> > wrote: >>>> >>>>> Hello Matthias, >>>>> >>>>> we executed UPS integration tests on the latest commit in 0.10.x brach >>>>> (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. >>>>> >>>> >>>> >>>> awesome! >>>> >>>>> >>>>> Since you talked about Bintray, we could move this little bit further >>>>> and test >>>>> staged bits directly from there - meaning wars which are not on Maven >>>>> Central >>>>> yet but they are already on Bintray would be downloaded from there >>>>> dynamically >>>>> and our intergration test suite would be run directly against built >>>>> (but yet unreleased) wars. >>>>> >>>> >>>> >>>> the WAR files from my private staging repo will be exactly those that I >>>> upload to bintray; >>>> >>>> I use the private repo, to avoid an early publish (before the release >>>> is really done) >>>> >>>> Ah, right. The discussion I had with Karel was that it would be nice to >>>> test these built wars before they >>>> finally reach Maven Central and Bintray would act as a staging place >>>> just as your private repo right now. >>>> >>> >>> >>> feel free to use my private staging repo as your repo (it's a valid >>> maven repo URL) >>> http://people.apache.org/~matzew/aerogear-staging/ >>> >>> >>> >>>> >>>> I am not sure if Bintray supports this but if it is possible, Bintray >>>> could be exactly what your >>>> "private repo" is right now, we would just make it more robust / >>>> official moving from >>>> your private repo somewhere (no offence) to Bintray. >>>> >>>> By doing this, we kind of abuse Bintray, I guess it is not primarily >>>> used for staging bits but for announcing them to the world, >>>> however it is technically possible. >>>> >>> >>> yes, but I am more interested in keep my current process: >>> >>> * staging: my Apache account >>> * release: bintray (there we have all the good stats etc) >>> >>> >>>> >>>> However feel free to cancel this idea. We are planning to test these >>>> unreleased wars anyway so instead of Bintray >>>> we try to download them from your private repo but I am just saying >>>> that having it from Bintray seems to be better. >>>> >>> >>> And again, these files from my private repo are exactly the same that I >>> than upload to bintray (assuming the release tests are passing) >>> >>> -M >>> >>> >>>> >>>> - Stefan >>>> >>>> -Matthias >>>> >>>>> >>>>> In other words, Bintray could be used as a staging facility for UPS. >>>>> >>>>> WDYT? >>>>> >>>>> Stefan Miklosovic >>>>> Red Hat Brno - JBoss Mobile Platform >>>>> >>>>> e-mail: smikloso at redhat.com >>>>> irc: smikloso >>>>> >>>>> ------------------------------ >>>>> >>>>> Hello, >>>>> >>>>> for the upcoming release we have a few, but important, tickets solved: >>>>> https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 >>>>> >>>>> >>>>> Before finishing the release, let's see if there are issues w/ the >>>>> server, hence I have staged the WAR file on my private webspace: >>>>> >>>>> >>>>> >>>>> http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ >>>>> >>>>> >>>>> If they aren't any objections or remarks I will release the bits to >>>>> bintray on Friday morning >>>>> >>>>> >>>>> Greetings, >>>>> 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- 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/20140313/51577704/attachment-0001.html From bsutter at redhat.com Thu Mar 13 13:25:44 2014 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 13 Mar 2014 13:25:44 -0400 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: References: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> <161652535.9283579.1394638506889.JavaMail.zimbra@redhat.com> <1745AA9B-5CEE-454F-A5BB-FFB836887173@redhat.com> Message-ID: On Mar 13, 2014, at 1:11 PM, Matthias Wessendorf wrote: > > > > On Thu, Mar 13, 2014 at 6:09 PM, Burr Sutter wrote: > By the way, I am really enjoying the new Test Message feature :-) > > IT's not only a test message :) > you can use that to just reach out to users :) (think marketing apps :) ) Well, I do not yet consider it ready for marketing users. Mostly because of the security model - everybody is an admin - it would be bad if the marketing folks messed up the iOS cert for example. I believe we should have some form of read-only user role as well as a "message sending" only role - therefore the admin can protect all the other settings. This can wait until after 1.0, for now, just "push administrators" can send messages - useful for testing, sometimes in the case of emergency, however, I would not recommend giving all that power to the average marketing person. > > > curl is a pain and becomes problematic for our Windows userbase anyway. > > > On Mar 13, 2014, at 12:59 PM, Sebastien Blanc wrote: > >> Deployed and tested with success !! >> +1 >> >> >> >> On Wed, Mar 12, 2014 at 6:19 PM, Matthias Wessendorf wrote: >> FYI: On IRC Stefan reported the WAR from my staging repo also passes the tests. >> >> >> >> >> >> >> On Wed, Mar 12, 2014 at 4:39 PM, Matthias Wessendorf wrote: >> >> >> >> On Wed, Mar 12, 2014 at 4:35 PM, Stefan Miklosovic wrote: >> >> >> >> >> On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic wrote: >> Hello Matthias, >> >> we executed UPS integration tests on the latest commit in 0.10.x brach >> (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. >> >> >> awesome! >> >> Since you talked about Bintray, we could move this little bit further and test >> staged bits directly from there - meaning wars which are not on Maven Central >> yet but they are already on Bintray would be downloaded from there dynamically >> and our intergration test suite would be run directly against built (but yet unreleased) wars. >> >> >> the WAR files from my private staging repo will be exactly those that I upload to bintray; >> >> I use the private repo, to avoid an early publish (before the release is really done) >> Ah, right. The discussion I had with Karel was that it would be nice to test these built wars before they >> finally reach Maven Central and Bintray would act as a staging place just as your private repo right now. >> >> >> feel free to use my private staging repo as your repo (it's a valid maven repo URL) >> http://people.apache.org/~matzew/aerogear-staging/ >> >> >> >> I am not sure if Bintray supports this but if it is possible, Bintray could be exactly what your >> "private repo" is right now, we would just make it more robust / official moving from >> your private repo somewhere (no offence) to Bintray. >> >> By doing this, we kind of abuse Bintray, I guess it is not primarily used for staging bits but for announcing them to the world, >> however it is technically possible. >> >> yes, but I am more interested in keep my current process: >> >> * staging: my Apache account >> * release: bintray (there we have all the good stats etc) >> >> >> However feel free to cancel this idea. We are planning to test these unreleased wars anyway so instead of Bintray >> we try to download them from your private repo but I am just saying that having it from Bintray seems to be better. >> >> And again, these files from my private repo are exactly the same that I than upload to bintray (assuming the release tests are passing) >> >> -M >> >> >> - Stefan >> >> -Matthias >> >> In other words, Bintray could be used as a staging facility for UPS. >> >> WDYT? >> >> Stefan Miklosovic >> Red Hat Brno - JBoss Mobile Platform >> >> e-mail: smikloso at redhat.com >> irc: smikloso >> >> Hello, >> >> for the upcoming release we have a few, but important, tickets solved: >> https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 >> >> >> Before finishing the release, let's see if there are issues w/ the server, hence I have staged the WAR file on my private webspace: >> >> >> http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ >> >> >> If they aren't any objections or remarks I will release the bits to bintray on Friday morning >> >> >> Greetings, >> 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20140313/9b7e1b68/attachment-0001.html From matzew at apache.org Thu Mar 13 14:07:38 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 13 Mar 2014 19:07:38 +0100 Subject: [aerogear-dev] Staging of UnifiedPush Server 0.10.1 In-Reply-To: References: <565862382.9264834.1394635701055.JavaMail.zimbra@redhat.com> <161652535.9283579.1394638506889.JavaMail.zimbra@redhat.com> <1745AA9B-5CEE-454F-A5BB-FFB836887173@redhat.com> Message-ID: On Thursday, March 13, 2014, Burr Sutter wrote: > > On Mar 13, 2014, at 1:11 PM, Matthias Wessendorf > > wrote: > > > > > On Thu, Mar 13, 2014 at 6:09 PM, Burr Sutter > > wrote: > >> By the way, I am really enjoying the new Test Message feature :-) >> > > IT's not only a test message :) > you can use that to just reach out to users :) (think marketing apps :) ) > > > Well, I do not yet consider it ready for marketing users. Mostly because > of the security model - everybody is an admin - it would be bad if the > marketing folks messed up the iOS cert for example. > > I believe we should have some form of read-only user role as well as a > "message sending" only role - therefore the admin can protect all the other > settings. > Was part of our user mgmt thread in nov/dec/jan > > This can wait until after 1.0, for now, just "push administrators" can > send messages - useful for testing, sometimes in the case of emergency, > however, I would not recommend giving all that power to the average > marketing person. > Well, think small shops/agencies: IMO pretty much all they need I agree we need improvements after 1.0 (e.g. Keycloak user roles etc). But I'd also not "recommend" to _not_ use the UI for real pushes :-) BUT yeah, not yet 100% enterprise > > > > > curl is a pain and becomes problematic for our Windows userbase anyway. > > > On Mar 13, 2014, at 12:59 PM, Sebastien Blanc wrote: > > Deployed and tested with success !! > +1 > > > > On Wed, Mar 12, 2014 at 6:19 PM, Matthias Wessendorf > wrote: > > FYI: On IRC Stefan reported the WAR from my staging repo also passes the > tests. > > > > > > > On Wed, Mar 12, 2014 at 4:39 PM, Matthias Wessendorf > wrote: > > > > > On Wed, Mar 12, 2014 at 4:35 PM, Stefan Miklosovic > wrote: > > > ------------------------------ > > > > > On Wed, Mar 12, 2014 at 3:48 PM, Stefan Miklosovic > wrote: > > Hello Matthias, > > we executed UPS integration tests on the latest commit in 0.10.x brach > (35d15c91b7b4f01902e2fdb6a61d60506439a67c) and tests passed ok. > > > > awesome! > > > Since you talked about Bintray, we could move this little bit further and > test > staged bits directly from there - meaning wars which are not on Maven > Central > yet but they are already on Bintray would be downloaded from there > dynamically > and our intergration test suite would be run directly against built (but > yet unreleased) wars. > > > > the WAR files from my private staging repo will be exactly those that I > upload to bintray; > > I use the private repo, to avoid an early publish (before the release is > really done) > > Ah, right. The discussion I had with Karel was that it would be nice to > test these built wars before they > finally reach Maven Central and Bintray would act as a staging place just > as your private repo right now. > > > > feel free to use my private staging repo as your repo (it's a valid maven > repo > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/40c1ce78/attachment.html From fjuma at redhat.com Thu Mar 13 15:23:42 2014 From: fjuma at redhat.com (Farah Juma) Date: Thu, 13 Mar 2014 15:23:42 -0400 (EDT) Subject: [aerogear-dev] SimplePush Server 0.10.0 In-Reply-To: References: <1394529559439-6718.post@n5.nabble.com> Message-ID: <1623218245.29493438.1394738622544.JavaMail.zimbra@redhat.com> > From: "Daniel Bevenius" > To: "AeroGear Developer Mailing List" > Sent: Thursday, March 13, 2014 12:47:09 AM > Subject: Re: [aerogear-dev] SimplePush Server 0.10.0 > > We have staged an updated version containing fixes for [1] and [2] which can > be found here: > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2814/ > > The OpenShift instance has been updated and now also contains UnifiedPush > Server 0.10.1: > https://sps010-dbevenius.rhcloud.com:8443/simplepush I've also created a branch that contains updated snapshot/restore action hooks: https://github.com/fjuma/openshift-origin-cartridge-aerogear-push/commits/upgrade To test upgrading from an existing 0.9.0 cartridge instance to an 0.10.0 instance, the following steps can be used: 1) ssh into an existing 0.9.0 test instance and perform the following commands: echo "$OPENSHIFT_AEROGEAR_PUSH_TOKEN_KEY" > $OPENSHIFT_DATA_DIR/aerogear_push_token_key cp $OPENSHIFT_AEROGEAR_PUSH_DIR/standalone/configuration/standalone.xml $OPENSHIFT_DATA_DIR/standalone.snapshot.xml 2) rhc snapshot save 3) rhc app delete 4) rhc create-app --no-git "https://cartreflect-claytondev.rhcloud.com/reflect?github=fjuma/openshift-origin-cartridge-aerogear-push&commit=9f8941ca095e07e36d0ee20e29f69f249c865390" mysql-5.1 5) rhc snapshot restore -f /PATH/TO/APP.tar.gz If you're using FireFox, you'll need to restart your browser to avoid an issue with caching. You should then be able to log into the admin console with the same password you previously set, see existing push applications and variants, and send push notifications. Farah > And if you'd like create an instance using your own OpenShift account: > rhc create-app appName " > https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push&commit=d009198e5b71a4335f02b0fff47cb809a30c2c6e > " mysql-5.1 > > [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 "Greeting message is only > returned once." > [2] https://issues.jboss.org/browse/AGSMPLPUSH-42 "xhr_streaming/xhr_polling > protocols are not working" > > > > > On 11 March 2014 10:21, Matthias Wessendorf < matzew at apache.org > wrote: > > > > > > > On Tue, Mar 11, 2014 at 10:19 AM, danielbevenius < daniel.bevenius at gmail.com > > wrote: > > > Hey Bruno, > > sorry about the late reply. I thought I sent a response yesterday but can't > see it here. > > I was planning on releasing tomorrow but just discovered a bug [1]. Will fix > it and post back with staging details. So the release will be delayed a > little. Perhaps Thursday. > > sounds good to me > > > > [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-SimplePush-Server-0-10-0-tp6686p6718.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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 Mar 13 15:47:59 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 13 Mar 2014 20:47:59 +0100 Subject: [aerogear-dev] SimplePush Server 0.10.0 In-Reply-To: <1623218245.29493438.1394738622544.JavaMail.zimbra@redhat.com> References: <1394529559439-6718.post@n5.nabble.com> <1623218245.29493438.1394738622544.JavaMail.zimbra@redhat.com> Message-ID: <20140313204759.29251a18@kapy-ntb-x220> On Thu, 13 Mar 2014 15:23:42 -0400 (EDT) Farah Juma wrote: > > > From: "Daniel Bevenius" > > To: "AeroGear Developer Mailing List" > > Sent: Thursday, March 13, 2014 12:47:09 AM > > Subject: Re: [aerogear-dev] SimplePush Server 0.10.0 > > > > We have staged an updated version containing fixes for [1] and [2] which can > > be found here: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2814/ > > > > The OpenShift instance has been updated and now also contains UnifiedPush > > Server 0.10.1: > > https://sps010-dbevenius.rhcloud.com:8443/simplepush > > > I've also created a branch that contains updated snapshot/restore action > hooks: > https://github.com/fjuma/openshift-origin-cartridge-aerogear-push/commits/upgrade > > To test upgrading from an existing 0.9.0 cartridge instance to an 0.10.0 > instance, the following steps can be used: > > 1) ssh into an existing 0.9.0 test instance and perform the following > commands: echo "$OPENSHIFT_AEROGEAR_PUSH_TOKEN_KEY" > > $OPENSHIFT_DATA_DIR/aerogear_push_token_key cp > $OPENSHIFT_AEROGEAR_PUSH_DIR/standalone/configuration/standalone.xml > $OPENSHIFT_DATA_DIR/standalone.snapshot.xml Farah, do I understand correctly that 1) will be done automagically starting by 0.10.0 version of UPS cartridge? > > 2) rhc snapshot save > > 3) rhc app delete > > 4) rhc create-app --no-git > "https://cartreflect-claytondev.rhcloud.com/reflect?github=fjuma/openshift-origin-cartridge-aerogear-push&commit=9f8941ca095e07e36d0ee20e29f69f249c865390" > mysql-5.1 > > 5) rhc snapshot restore -f /PATH/TO/APP.tar.gz > > If you're using FireFox, you'll need to restart your browser to avoid an > issue with caching. You should then be able to log into the admin console > with the same password you previously set, see existing push applications and > variants, and send push notifications. > > > Farah > > > > > And if you'd like create an instance using your own OpenShift account: > > rhc create-app appName " > > https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push&commit=d009198e5b71a4335f02b0fff47cb809a30c2c6e > > " mysql-5.1 > > > > [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 "Greeting message is only > > returned once." > > [2] https://issues.jboss.org/browse/AGSMPLPUSH-42 "xhr_streaming/xhr_polling > > protocols are not working" > > > > > > > > > > On 11 March 2014 10:21, Matthias Wessendorf < matzew at apache.org > wrote: > > > > > > > > > > > > > > On Tue, Mar 11, 2014 at 10:19 AM, danielbevenius < daniel.bevenius at gmail.com > > > wrote: > > > > > > Hey Bruno, > > > > sorry about the late reply. I thought I sent a response yesterday but can't > > see it here. > > > > I was planning on releasing tomorrow but just discovered a bug [1]. Will fix > > it and post back with staging details. So the release will be delayed a > > little. Perhaps Thursday. > > > > sounds good to me > > > > > > > > [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 > > > > > > > > -- > > View this message in context: > > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-SimplePush-Server-0-10-0-tp6686p6718.html > > Sent from the aerogear-dev mailing list archive at Nabble.com. > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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 fjuma at redhat.com Thu Mar 13 15:59:41 2014 From: fjuma at redhat.com (Farah Juma) Date: Thu, 13 Mar 2014 15:59:41 -0400 (EDT) Subject: [aerogear-dev] SimplePush Server 0.10.0 In-Reply-To: <20140313204759.29251a18@kapy-ntb-x220> References: <1394529559439-6718.post@n5.nabble.com> <1623218245.29493438.1394738622544.JavaMail.zimbra@redhat.com> <20140313204759.29251a18@kapy-ntb-x220> Message-ID: <1319669351.29517786.1394740781882.JavaMail.zimbra@redhat.com> > From: "Karel Piwko" > To: "Farah Juma" > Cc: "AeroGear Developer Mailing List" > Sent: Thursday, March 13, 2014 3:47:59 PM > Subject: Re: [aerogear-dev] SimplePush Server 0.10.0 > > On Thu, 13 Mar 2014 15:23:42 -0400 (EDT) > Farah Juma wrote: > > > > > > From: "Daniel Bevenius" > > > To: "AeroGear Developer Mailing List" > > > Sent: Thursday, March 13, 2014 12:47:09 AM > > > Subject: Re: [aerogear-dev] SimplePush Server 0.10.0 > > > > > > We have staged an updated version containing fixes for [1] and [2] which > > > can > > > be found here: > > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2814/ > > > > > > The OpenShift instance has been updated and now also contains UnifiedPush > > > Server 0.10.1: > > > https://sps010-dbevenius.rhcloud.com:8443/simplepush > > > > > > I've also created a branch that contains updated snapshot/restore action > > hooks: > > https://github.com/fjuma/openshift-origin-cartridge-aerogear-push/commits/upgrade > > > > To test upgrading from an existing 0.9.0 cartridge instance to an 0.10.0 > > instance, the following steps can be used: > > > > 1) ssh into an existing 0.9.0 test instance and perform the following > > commands: echo "$OPENSHIFT_AEROGEAR_PUSH_TOKEN_KEY" > > > $OPENSHIFT_DATA_DIR/aerogear_push_token_key cp > > $OPENSHIFT_AEROGEAR_PUSH_DIR/standalone/configuration/standalone.xml > > $OPENSHIFT_DATA_DIR/standalone.snapshot.xml > > Farah, do I understand correctly that 1) will be done automagically starting > by 0.10.0 version of UPS cartridge? Correct. Because an 0.9.0 instance won't already have the necessary snapshot hook, step 1) needs to be done manually right now. Once the action hooks are committed to the cartridge repo for the 0.10.0 cartridge release, this step will be done automatically for future upgrades (e.g., upgrading from 0.10.0 to 0.11.0). > > > > 2) rhc snapshot save > > > > 3) rhc app delete > > > > 4) rhc create-app --no-git > > "https://cartreflect-claytondev.rhcloud.com/reflect?github=fjuma/openshift-origin-cartridge-aerogear-push&commit=9f8941ca095e07e36d0ee20e29f69f249c865390" > > mysql-5.1 > > > > 5) rhc snapshot restore -f /PATH/TO/APP.tar.gz > > > > If you're using FireFox, you'll need to restart your browser to avoid an > > issue with caching. You should then be able to log into the admin console > > with the same password you previously set, see existing push applications > > and > > variants, and send push notifications. > > > > > > Farah > > > > > > > > > And if you'd like create an instance using your own OpenShift account: > > > rhc create-app appName " > > > https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push&commit=d009198e5b71a4335f02b0fff47cb809a30c2c6e > > > " mysql-5.1 > > > > > > [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 "Greeting message is > > > only > > > returned once." > > > [2] https://issues.jboss.org/browse/AGSMPLPUSH-42 > > > "xhr_streaming/xhr_polling > > > protocols are not working" > > > > > > > > > > > > > > > On 11 March 2014 10:21, Matthias Wessendorf < matzew at apache.org > wrote: > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 11, 2014 at 10:19 AM, danielbevenius < > > > daniel.bevenius at gmail.com > > > > wrote: > > > > > > > > > Hey Bruno, > > > > > > sorry about the late reply. I thought I sent a response yesterday but > > > can't > > > see it here. > > > > > > I was planning on releasing tomorrow but just discovered a bug [1]. Will > > > fix > > > it and post back with staging details. So the release will be delayed a > > > little. Perhaps Thursday. > > > > > > sounds good to me > > > > > > > > > > > > [1] https://issues.jboss.org/browse/AGSMPLPUSH-49 > > > > > > > > > > > > -- > > > View this message in context: > > > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-SimplePush-Server-0-10-0-tp6686p6718.html > > > Sent from the aerogear-dev mailing list archive at Nabble.com. > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > sessions: http://www.slideshare.net/mwessendorf > > > twitter: http://twitter.com/mwessendorf > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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 gorkem.ercan at gmail.com Thu Mar 13 22:51:14 2014 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Thu, 13 Mar 2014 22:51:14 -0400 Subject: [aerogear-dev] Skins In-Reply-To: References: <63FCBBA8-B575-4138-B04D-B538A7E7B140@redhat.com> <96E9D6CC-C5A6-4F6E-82A8-1A88B52FDDDA@redhat.com> Message-ID: Our tools do not support XCode versions older than 4.6 (cordova-ios supports 4.5 but I suspect that will change soon). So the minimum iOS version that we can support with the tools is iOS 4.3. This means that iPhone 3G is out of reach but iPhone 3GS is still in range. -- Gorkem On Thu, Mar 13, 2014 at 9:25 AM, Burr Sutter wrote: > > On Mar 13, 2014, at 9:18 AM, Luke Holmquist wrote: > > > > Sent from my iPhone > > On Mar 13, 2014, at 9:01 AM, Burr Sutter wrote: > > > On Mar 13, 2014, at 8:51 AM, Matthias Wessendorf > wrote: > > Was this post supposed to be posted to a different list ? > > No - these skins are a subset of the devices the Aerogear aims to support. > :-) > > > Aren't we supporting OS's not devices > > Yes - hence my question around iPhone 3 - I think it has 'aged out' > > But our tooling has targets a combo of OS + Device to help with testing. > We won't have a skin for every combo but I do like proper coverage of the > Apple & Samsung devices as they tend to have marketshare leadership. > > Plus, the end-user can always build their own skin. > > > > > > > Anyways, iPhone3 zero iOS7 > > OK - I think we should drop iPhone 3 from the list - it is getting > cluttered and we need to add in more Android devices, as they have a higher > variety of screen dimensions. > > > > Check here: > http://www.apple.com/ios/features/ > > "OS 7 is compatible with" > > > > On Thu, Mar 13, 2014 at 1:43 PM, Burr Sutter wrote: > >> It is time to get our simulator skins upgraded >> >> Will iPhone3 or 4 still run iOS7? >> >> Please comment here: >> https://issues.jboss.org/browse/JBDS-2960 >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140313/c13448b6/attachment.html From bruno at abstractj.org Fri Mar 14 04:20:35 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 14 Mar 2014 05:20:35 -0300 Subject: [aerogear-dev] AeroGear Crypto Java 0.1.3 Staged In-Reply-To: References: Message-ID: Aloha, our release will be postponed for the next week. I?m solving the issues between BouncyCastle and SpongyCastle for Android. Kisses. -- abstractj On March 12, 2014 at 6:04:04 PM, Bruno Oliveira (bruno at abstractj.org) wrote: > New staging URL https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2817. > The latest change was to benefit Android and write less code: > > - ae454bf Expose method to generate secret for scenarios where it must be saved into the > key store > > > > -- > abstractj > > On March 12, 2014 at 4:57:51 PM, Bruno Oliveira (bruno at abstractj.org) wrote: > > Good morning everyone, AG Crypto Java was staged under the following maven profile: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2816 > > I?m planning to release it on Friday morning (14/03) Changelog: * 17b9787 (upstream-abstractj/keypair-encoding, > > keypair-encoding) Explicit imports, instead of wildcards * 7e595da Accept a raw key > > pair. For scenarios where the public key is transmitted over the wire a34b746 Test refactoring > > * 880be04 Add support on cryptobox to accept a public key for encryption * a2c39ff Testing > > vectors for public key encryption * 4421bc3 (upstream-abstractj/pom, pom) Change > > the scope for bouncycastle * f190d64 (upstream-abstractj/refactor, refactor) Accept > > KeyPair as argument * 832127a (AGSEC-147) Hashing support for SHA-256 and SHA-512 > -- > > abstractj > > From bruno at abstractj.org Fri Mar 14 04:25:26 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 14 Mar 2014 05:25:26 -0300 Subject: [aerogear-dev] security updates In-Reply-To: <7ED42B41-92DC-468A-8923-636B5334EEB3@redhat.com> References: <7ED42B41-92DC-468A-8923-636B5334EEB3@redhat.com> Message-ID: I think we need to discuss in a meeting. I also would like to hear from Gorkem the implications on it. Other than that, we can?t wait 12 months to apply security updates. -- abstractj On March 11, 2014 at 2:12:15 PM, Burr Sutter (bsutter at redhat.com) wrote: > > We are going to have to support a range of Cordova versions for > the following reasons: > 1) Sync'ing with JBDS > 2) Sync'ing with what is supported at any given moment - where > the supported version may only update 2 times a year > 3) Addressing the fact that customers are slow to upgrade unless > there is a very real problem exposed in their specific application > - for example, if they don't use a particular Cordova plugin then > they might ignore a particular vulnerability that is tied to > a specific plugin. Another example, if their apps are only used > on 25 corporate executives phones, then they might determine > the vulnerability is less important (small, fixed audience). > > We will need to pick a specific time window for all parties to "catch > up" like 12 months. From kpiwko at redhat.com Fri Mar 14 04:30:42 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Fri, 14 Mar 2014 09:30:42 +0100 Subject: [aerogear-dev] Passphrase encryption - REST API discussion In-Reply-To: References: <20140313174811.3dd56072@kapy-ntb-x220> Message-ID: <20140314093042.6850cd7b@kapy-ntb-x220> On Thu, 13 Mar 2014 17:52:48 +0100 Matthias Wessendorf wrote: > On Thu, Mar 13, 2014 at 5:48 PM, Karel Piwko wrote: > > > I believe that command line based client is important. Either Java Sender > > or Node.js Sender could be enhanced with non-sending functionality and > > wrapped > > to provide CLI though via airline > > > :-))))) I totally agree - let's create a JIRA for a Java-based CLI via > airline https://issues.jboss.org/browse/AGPUSH-561 > > > > > and nodejs libs. > > > > We already have similar stuff internally for sampling random data on > > OpenShift > > carts, it is based on RestAssured/Spacelift though. It will not be that > > difficult to make it available upstream if use case are clear ;-) > > > > Current functionality listed at [1] > > > > > AeroGear Clients > > > > > > - cURL > > > > > > Yesterday I had the amusing experience of dig into the sources of > > OpenSSL and > > > their documentation, to see how people could encrypt it from the command > > > line. If I recommend that people would remember my name for the eternity > > in a > > > bad way. Another insane idea was to provide encoders for GPG. The > > simplest > > > idea, I think, would be provide code for people encrypt their passphrase > > and > > > certificate, instead of trust in some software. > > > > > [1] > > usage: perf-test-env [] > > > > The most commonly used perf-test-env commands are: > > cart-create Create OpenShift Cartridge based on latest commit in > > given > > organization, repository and branch. Requires rhc tools installed > > help Display help information ups-delete Deletes data from > > an UPS > > instance ups-dump Dumps all data from UPS so they are usable by > > performance tests ups-generate Generates data for an UPS instance > > > > See 'perf-test-env help ' for more information on a specific > > command. > > > > NAME > > perf-test-env ups-generate - Generates data for an UPS instance > > > > SYNOPSIS > > perf-test-env ups-generate (-a | --app-name ) > > [--cert-pass ] [--cert-path > > ] [--google-key ] [(-n | > > --namespace > > )] [--no-https] [--old-password ] > > (-p | --password ) [--port ] > > [--production] [--project-no ] --push-app-name > > > > [--simple-push] [(-u | --username )] > > > > OPTIONS > > -a , --app-name > > Name of the application on OpenShift > > > > --cert-pass > > Certificate passphrase > > > > --cert-path > > Path to iOS certificate. If set, --cert-pass is required and > > iOS > > variant is created. > > > > --google-key > > Google API key for Android application variant. If set, > > --project-no > > is required and Android variant is created. > > > > -n , --namespace > > Namespace on OpenShift, default value: mobileqa > > > > --no-https > > Use HTTP protocol instead of HTTPS > > > > --old-password > > Previous password. Default value: 123 > > > > -p , --password > > Password to be used for Unified Push Server login. If > > old-password > > matches, this one replaces the old one > > > > --port > > Port to be used for REST calls, default value: 80 or 443, > > depending > > on --no-https > > > > --production > > If set, certificate is marked as production one > > > > --project-no > > Google Project Number for Android application variant. If > > present, > > Android variant is created. > > > > --push-app-name > > Push application name > > > > --simple-push > > If set, SimplePush application variant is generated > > > > -u , --username > > Username to be used for Unified Push Server login, default > > value: > > admin > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > From edewit at redhat.com Fri Mar 14 04:29:57 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 14 Mar 2014 09:29:57 +0100 Subject: [aerogear-dev] security updates In-Reply-To: References: <7ED42B41-92DC-468A-8923-636B5334EEB3@redhat.com> Message-ID: But, this doesn?t address a security fix in our products, we can?t be held responsible for the platform our plugin runs on.Like Tolis said if we take this route we might as well only support the latest cordova version. On 14 Mar,2014, at 9:25 , Bruno Oliveira wrote: > I think we need to discuss in a meeting. I also would like to hear from Gorkem the implications on it. Other than that, we can?t wait 12 months to apply security updates. > From bruno at abstractj.org Fri Mar 14 04:58:53 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 14 Mar 2014 05:58:53 -0300 Subject: [aerogear-dev] security updates In-Reply-To: References: <7ED42B41-92DC-468A-8923-636B5334EEB3@redhat.com> Message-ID: Apples and oranges my friend. Let?s schedule a meeting for it. -- abstractj On March 14, 2014 at 5:56:42 AM, Erik Jan de Wit (edewit at redhat.com) wrote: > > But, this doesn?t address a security fix in our products, we > can?t be held responsible for the platform our plugin runs on.Like > Tolis said if we take this route we might as well only support the > latest cordova version. From matzew at apache.org Fri Mar 14 05:21:09 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 14 Mar 2014 10:21:09 +0100 Subject: [aerogear-dev] security updates In-Reply-To: References: <7ED42B41-92DC-468A-8923-636B5334EEB3@redhat.com> Message-ID: +1 meeting to discuss this sounds good On Fri, Mar 14, 2014 at 9:58 AM, Bruno Oliveira wrote: > Apples and oranges my friend. Let's schedule a meeting for it. > > -- > abstractj > > On March 14, 2014 at 5:56:42 AM, Erik Jan de Wit (edewit at redhat.com) > wrote: > > > But, this doesn't address a security fix in our products, we > > can't be held responsible for the platform our plugin runs on.Like > > Tolis said if we take this route we might as well only support the > > latest cordova version. > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140314/8185f21f/attachment.html From matzew at apache.org Fri Mar 14 05:27:56 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 14 Mar 2014 10:27:56 +0100 Subject: [aerogear-dev] AeroGear Crypto Java 0.1.3 Staged In-Reply-To: References: Message-ID: thanks for the heads-up! On Fri, Mar 14, 2014 at 9:20 AM, Bruno Oliveira wrote: > Aloha, our release will be postponed for the next week. I'm solving the > issues between BouncyCastle and SpongyCastle for Android. > > Kisses. > > -- > abstractj > > On March 12, 2014 at 6:04:04 PM, Bruno Oliveira (bruno at abstractj.org) > wrote: > > New staging URL > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2817 > . > > The latest change was to benefit Android and write less code: > > > > - ae454bf Expose method to generate secret for scenarios where it must > be saved into the > > key store > > > > > > > > -- > > abstractj > > > > On March 12, 2014 at 4:57:51 PM, Bruno Oliveira (bruno at abstractj.org) > wrote: > > > Good morning everyone, AG Crypto Java was staged under the following > maven profile: > > > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2816 > > > I'm planning to release it on Friday morning (14/03) Changelog: * > 17b9787 (upstream-abstractj/keypair-encoding, > > > keypair-encoding) Explicit imports, instead of wildcards * 7e595da > Accept a raw key > > > pair. For scenarios where the public key is transmitted over the wire > a34b746 Test refactoring > > > * 880be04 Add support on cryptobox to accept a public key for > encryption * a2c39ff Testing > > > vectors for public key encryption * 4421bc3 (upstream-abstractj/pom, > pom) Change > > > the scope for bouncycastle * f190d64 (upstream-abstractj/refactor, > refactor) Accept > > > KeyPair as argument * 832127a (AGSEC-147) Hashing support for SHA-256 > and SHA-512 > > -- > > > abstractj > > > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140314/78d253d9/attachment.html From scm.blanc at gmail.com Fri Mar 14 05:36:05 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 14 Mar 2014 10:36:05 +0100 Subject: [aerogear-dev] AeroGear Crypto Java 0.1.3 Staged In-Reply-To: References: Message-ID: If you need help to test just scream ! On Fri, Mar 14, 2014 at 9:20 AM, Bruno Oliveira wrote: > Aloha, our release will be postponed for the next week. I'm solving the > issues between BouncyCastle and SpongyCastle for Android. > > Kisses. > > -- > abstractj > > On March 12, 2014 at 6:04:04 PM, Bruno Oliveira (bruno at abstractj.org) > wrote: > > New staging URL > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2817 > . > > The latest change was to benefit Android and write less code: > > > > - ae454bf Expose method to generate secret for scenarios where it must > be saved into the > > key store > > > > > > > > -- > > abstractj > > > > On March 12, 2014 at 4:57:51 PM, Bruno Oliveira (bruno at abstractj.org) > wrote: > > > Good morning everyone, AG Crypto Java was staged under the following > maven profile: > > > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2816 > > > I'm planning to release it on Friday morning (14/03) Changelog: * > 17b9787 (upstream-abstractj/keypair-encoding, > > > keypair-encoding) Explicit imports, instead of wildcards * 7e595da > Accept a raw key > > > pair. For scenarios where the public key is transmitted over the wire > a34b746 Test refactoring > > > * 880be04 Add support on cryptobox to accept a public key for > encryption * a2c39ff Testing > > > vectors for public key encryption * 4421bc3 (upstream-abstractj/pom, > pom) Change > > > the scope for bouncycastle * f190d64 (upstream-abstractj/refactor, > refactor) Accept > > > KeyPair as argument * 832127a (AGSEC-147) Hashing support for SHA-256 > and SHA-512 > > -- > > > abstractj > > > > > > > _______________________________________________ > 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/20140314/b551d153/attachment.html From bruno at abstractj.org Fri Mar 14 09:23:40 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 14 Mar 2014 10:23:40 -0300 Subject: [aerogear-dev] AG Crypto, BouncyCastle...SpongyCastle...Android. Oh my! Message-ID: Good morning everyone, Yesterday we found an issue on AG Crypto, it just doesn't work with AG Android when you make use of the CryptoBox or try to generate a key pair. I would like to thank Sebastien, Passos and Summers for reporting and testing it. The reason why it din't work is because AG Crypto make use of the APIs for GCM and Elliptic curves and has explicit calls to BouncyCastle. For example: - BouncyCastle: import org.bouncycastle.crypto.InvalidCipherTextException; import org.bouncycastle.crypto.modes.AEADBlockCipher; import org.bouncycastle.crypto.params.AEADParameters; import org.bouncycastle.crypto.params.KeyParameter; - SpongyCastle (on Android): import org.spongycastle.crypto.InvalidCipherTextException; import org.spongycastle.crypto.modes.AEADBlockCipher; import org.spongycastle.crypto.params.AEADParameters; import org.spongycastle.crypto.params.KeyParameter; This is all because Google made us a favor (https://code.google.com/p/android/issues/detail?id=3280). More details about SpongyCastle here: http://rtyley.github.io/spongycastle/ To understand the issue and reproduce the following stacktrace (https://gist.github.com/secondsun/225a3698ab83f4d077bc). Follow these steps: - Get the staging url https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2817 - Get the following PR https://github.com/aerogear/aerogear-android/pull/140 - Run the integration tests (https://github.com/aerogear/aerogear-android-integration-tests) with AG Crypto 0.1.3 Why that never happened before? The key pair and CryptoBox was not being used on Android. Possible solution: Since yesterday I was thinking about a possible solution, a dirty idea of factory to providers came to my mind but the number of wrappers would make the whole API impractical. Chatting with qmx, he suggested to me http://maven.apache.org/plugins/maven-shade-plugin/ (Thanks bro). The whole idea is to have a profile specific for Android, please see my PR (https://github.com/aerogear/aerogear-crypto-java/pull/22) into this way we will have a jar being generated specifically for mobile devices. What will change for Android? - You don't need to specify a gazillion of dependencies anymore (https://github.com/aerogear/aerogear-android/pull/141/files#diff-600376dffeb79835ede4a0b285078036R136) - Is necessary to specify the classifier (https://github.com/aerogear/aerogear-android/pull/141/files#diff-600376dffeb79835ede4a0b285078036R135) - The code duplication was removed (https://github.com/aerogear/aerogear-android/pull/141/files#diff-55ea76a676297e3a3ea9cd7e0f5d7e34R113) If you want to test it, run the integration tests (https://github.com/aerogear/aerogear-android-integration-tests/pull/26). One test was intentionally skipped (https://github.com/abstractj/aerogear-android-integration-tests/commit/f114b46e5f518d912176f6746ec914e13f565c22). I'm still investigating. Arms are welcome. -- abstractj From vmfamaral at gmail.com Fri Mar 14 12:26:59 2014 From: vmfamaral at gmail.com (Vasco Amaral) Date: Fri, 14 Mar 2014 16:26:59 +0000 Subject: [aerogear-dev] E-mail Message-ID: vmfamaral at gmail.com -- Vasco Amaral -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140314/a0337593/attachment.html From matzew at apache.org Fri Mar 14 12:32:57 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 14 Mar 2014 17:32:57 +0100 Subject: [aerogear-dev] E-mail In-Reply-To: References: Message-ID: hello, looks like you are subscribed :-) 2014-03-14 17:26 GMT+01:00 Vasco Amaral : > vmfamaral at gmail.com > > -- > Vasco Amaral > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140314/a5d52caf/attachment-0001.html From vmfamaral at gmail.com Fri Mar 14 12:41:08 2014 From: vmfamaral at gmail.com (Vasco Amaral) Date: Fri, 14 Mar 2014 16:41:08 +0000 Subject: [aerogear-dev] Problem with Push notification chrome-app Message-ID: Hello, I'm trying to follow this tutorial: https://github.com/lholmquist/aerogear.org/tree/AGPUSH-549/docs/guides/aerogear-push-chrome Because I want to do an app that is able to receive push notifications. But I'm having problems and seems that are coming from the AeroGear.js. But I'm not sure. I was debugging my application and it's returning this: Error in response to pushMessaging.getChannelId: TypeError: Object # has no method 'UnifiedPushClient' anyone at anytime got this error? and know how to solve it? this error comes from the "main.js" file on line 14 -> https://github.com/lholmquist/aerogear.org/blob/AGPUSH-549/docs/guides/aerogear-push-chrome/chrome-app.asciidoc Thank you :) -- Vasco Amaral -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140314/6cc5815b/attachment.html From scm.blanc at gmail.com Fri Mar 14 13:08:41 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 14 Mar 2014 18:08:41 +0100 Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: References: Message-ID: Hey ! Are you sure you aerogear.js is loaded ? In the guide I see a slight difference (and error that we should fix) between the screenshot of the app structure showing aerogear.js is in scripts/vendor folder and the manifest.json where it's in scripts/ (one level higher). Seb On Fri, Mar 14, 2014 at 5:41 PM, Vasco Amaral wrote: > Hello, > > I'm trying to follow this tutorial: > > https://github.com/lholmquist/aerogear.org/tree/AGPUSH-549/docs/guides/aerogear-push-chrome > > Because I want to do an app that is able to receive push notifications. > But I'm having problems and seems that are coming from the AeroGear.js. But > I'm not sure. > > I was debugging my application and it's returning this: > Error in response to pushMessaging.getChannelId: TypeError: Object > # has no method 'UnifiedPushClient' > anyone at anytime got this error? and know how to solve it? > > > this error comes from the "main.js" file on line 14 -> > https://github.com/lholmquist/aerogear.org/blob/AGPUSH-549/docs/guides/aerogear-push-chrome/chrome-app.asciidoc > > Thank you :) > -- > Vasco Amaral > > _______________________________________________ > 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/20140314/389927bf/attachment.html From kpiwko at redhat.com Fri Mar 14 16:53:10 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Fri, 14 Mar 2014 21:53:10 +0100 Subject: [aerogear-dev] Releasing test artifacts in org.aerogear.arquillian groupId Message-ID: <20140314215310.2af4b7e5@kapy-ntb-x220> Greetings, we have a bunch of Arquillian extensions to help test Aerogear spread across Aerogear test repos, for instance: * smart url - allows tests to switch in between http and https URLs for deployment * rules - allows test to defines sample data for UPS via JUnit @Rule * openshift-non-deploying-container - allows test to pretend Arquillian done some deployment to OpenShift cartridge It would be handy for us to release these extensions to Maven Central so we don't have to compile them prior running tests and also reuse them across tests. I was thinking about moving them into single repository in aerogear GH and releasing them in org.aerogear.arquillian groupId. Thoughts? Thanks, Karel From matzew at apache.org Sat Mar 15 02:08:12 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Sat, 15 Mar 2014 07:08:12 +0100 Subject: [aerogear-dev] Releasing test artifacts in org.aerogear.arquillian groupId In-Reply-To: <20140314215310.2af4b7e5@kapy-ntb-x220> References: <20140314215310.2af4b7e5@kapy-ntb-x220> Message-ID: On Friday, March 14, 2014, Karel Piwko wrote: > Greetings, > > we have a bunch of Arquillian extensions to help test Aerogear spread > across > Aerogear test repos, for instance: > > * smart url - allows tests to switch in between http and https URLs for > deployment > * rules - allows test to defines sample data for UPS via JUnit @Rule > * openshift-non-deploying-container - allows test to pretend Arquillian > done > some deployment to OpenShift cartridge > > It would be handy for us to release these extensions to Maven Central so we > don't have to compile them prior running tests and also reuse them across > tests. > > I was thinking about moving them into single repository in aerogear GH > and releasing them in org.aerogear.arquillian groupId. > > Thoughts? Sure, why not? > > Thanks, > > Karel > _______________________________________________ > 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/20140315/38803626/attachment.html From miguel21op at gmail.com Sun Mar 16 12:02:46 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Sun, 16 Mar 2014 16:02:46 +0000 Subject: [aerogear-dev] Cordova and iOS Message-ID: Hi all! As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: a) I created my development profile at Apple; b) I uploaded the Certificates.p12 to the AeroGear Server; c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): if(device.platform=='iOS'){ varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; } else if (device.platform=='Android'){ varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; } var pushConfig = { senderID: "278695547260", // not relevant for Android anyway pushServerURL: "https://aerogear-metalpush.rhcloud.com", variantID: varID, variantSecret: varSec, alias: userid } But nevertheless I can't register the device. I get this error: no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") What can be wrong? Thanks Miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140316/68b447cf/attachment.html From scm.blanc at gmail.com Sun Mar 16 12:11:59 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Sun, 16 Mar 2014 17:11:59 +0100 Subject: [aerogear-dev] Cordova and iOS In-Reply-To: References: Message-ID: Hi Miguel :) I will dig more into it tomorrow but first thing that comes in mind (because I did this error in the beginning) is to be sure that the bundle you created in the apple portal is exactly the same as the one in your cordova app Seb On Sun, Mar 16, 2014 at 5:02 PM, Miguel Lemos wrote: > Hi all! > > As you know I managed - with a little help from my friends ;-) -to have > the push notifications working on Android. But with iOS, not the same luck > so far. What I've done: > > a) I created my development profile at Apple; > b) I uploaded the Certificates.p12 to the AeroGear Server; > c) I installed the devprof profile (the mobile provision file) in Xcode > (which says it's valid); > d) I inserted the variant ID and Secret on my phone code, like this (keys > are not real): > > if(device.platform=='iOS'){ > varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; > varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; > } else if (device.platform=='Android'){ > varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; > varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; > } > var pushConfig = { > senderID: "278695547260", // not relevant for Android anyway > pushServerURL: "https://aerogear-metalpush.rhcloud.com", > variantID: varID, > variantSecret: varSec, > alias: userid > } > > But nevertheless I can't register the device. I get this error: > > no valid aps-environment (the message is not in English, so I translate > it freely:"It was not found a valid aps-environment for the app") > > What can be wrong? > > Thanks > > Miguel > > _______________________________________________ > 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/20140316/fab4d9b6/attachment.html From miguel21op at gmail.com Sun Mar 16 12:22:45 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Sun, 16 Mar 2014 16:22:45 +0000 Subject: [aerogear-dev] Cordova and iOS In-Reply-To: References: Message-ID: Hi Seb, thanks for answering in a so short notice :-) Yes, I payed attention to that: com.redebiz.smartdrifter both places M On Sun, Mar 16, 2014 at 4:11 PM, Sebastien Blanc wrote: > Hi Miguel :) > I will dig more into it tomorrow but first thing that comes in mind > (because I did this error in the beginning) is to be sure that the bundle > you created in the apple portal is exactly the same as the one in your > cordova app > Seb > > > > On Sun, Mar 16, 2014 at 5:02 PM, Miguel Lemos wrote: > >> Hi all! >> >> As you know I managed - with a little help from my friends ;-) -to have >> the push notifications working on Android. But with iOS, not the same luck >> so far. What I've done: >> >> a) I created my development profile at Apple; >> b) I uploaded the Certificates.p12 to the AeroGear Server; >> c) I installed the devprof profile (the mobile provision file) in Xcode >> (which says it's valid); >> d) I inserted the variant ID and Secret on my phone code, like this (keys >> are not real): >> >> if(device.platform=='iOS'){ >> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >> } else if (device.platform=='Android'){ >> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >> } >> var pushConfig = { >> senderID: "278695547260", // not relevant for Android anyway >> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >> variantID: varID, >> variantSecret: varSec, >> alias: userid >> } >> >> But nevertheless I can't register the device. I get this error: >> >> no valid aps-environment (the message is not in English, so I translate >> it freely:"It was not found a valid aps-environment for the app") >> >> What can be wrong? >> >> Thanks >> >> Miguel >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140316/e186337d/attachment-0001.html From miguel21op at gmail.com Sun Mar 16 12:25:03 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Sun, 16 Mar 2014 16:25:03 +0000 Subject: [aerogear-dev] Cordova and iOS In-Reply-To: References: Message-ID: Oops! A typo :-( I missed a "t": i wrote smardrifter :-( Once again, you got it!!! On Sun, Mar 16, 2014 at 4:22 PM, Miguel Lemos wrote: > Hi Seb, thanks for answering in a so short notice :-) > > Yes, I payed attention to that: com.redebiz.smartdrifter both places > > M > > > On Sun, Mar 16, 2014 at 4:11 PM, Sebastien Blanc wrote: > >> Hi Miguel :) >> I will dig more into it tomorrow but first thing that comes in mind >> (because I did this error in the beginning) is to be sure that the bundle >> you created in the apple portal is exactly the same as the one in your >> cordova app >> Seb >> >> >> >> On Sun, Mar 16, 2014 at 5:02 PM, Miguel Lemos wrote: >> >>> Hi all! >>> >>> As you know I managed - with a little help from my friends ;-) -to have >>> the push notifications working on Android. But with iOS, not the same luck >>> so far. What I've done: >>> >>> a) I created my development profile at Apple; >>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>> c) I installed the devprof profile (the mobile provision file) in Xcode >>> (which says it's valid); >>> d) I inserted the variant ID and Secret on my phone code, like this >>> (keys are not real): >>> >>> if(device.platform=='iOS'){ >>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>> } else if (device.platform=='Android'){ >>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>> } >>> var pushConfig = { >>> senderID: "278695547260", // not relevant for Android anyway >>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>> variantID: varID, >>> variantSecret: varSec, >>> alias: userid >>> } >>> >>> But nevertheless I can't register the device. I get this error: >>> >>> no valid aps-environment (the message is not in English, so I translate >>> it freely:"It was not found a valid aps-environment for the app") >>> >>> What can be wrong? >>> >>> Thanks >>> >>> Miguel >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140316/d46537c5/attachment.html From scm.blanc at gmail.com Sun Mar 16 12:53:32 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Sun, 16 Mar 2014 17:53:32 +0100 Subject: [aerogear-dev] Cordova and iOS In-Reply-To: References: Message-ID: Glad I could help on this nice sunny sunday :) On Sun, Mar 16, 2014 at 5:25 PM, Miguel Lemos wrote: > Oops! A typo :-( > > I missed a "t": i wrote smardrifter :-( > > Once again, you got it!!! > > > > On Sun, Mar 16, 2014 at 4:22 PM, Miguel Lemos wrote: > >> Hi Seb, thanks for answering in a so short notice :-) >> >> Yes, I payed attention to that: com.redebiz.smartdrifter both places >> >> M >> >> >> On Sun, Mar 16, 2014 at 4:11 PM, Sebastien Blanc wrote: >> >>> Hi Miguel :) >>> I will dig more into it tomorrow but first thing that comes in mind >>> (because I did this error in the beginning) is to be sure that the bundle >>> you created in the apple portal is exactly the same as the one in your >>> cordova app >>> Seb >>> >>> >>> >>> On Sun, Mar 16, 2014 at 5:02 PM, Miguel Lemos wrote: >>> >>>> Hi all! >>>> >>>> As you know I managed - with a little help from my friends ;-) -to >>>> have the push notifications working on Android. But with iOS, not the same >>>> luck so far. What I've done: >>>> >>>> a) I created my development profile at Apple; >>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>> c) I installed the devprof profile (the mobile provision file) in Xcode >>>> (which says it's valid); >>>> d) I inserted the variant ID and Secret on my phone code, like this >>>> (keys are not real): >>>> >>>> if(device.platform=='iOS'){ >>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>> } else if (device.platform=='Android'){ >>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>> } >>>> var pushConfig = { >>>> senderID: "278695547260", // not relevant for Android anyway >>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>> variantID: varID, >>>> variantSecret: varSec, >>>> alias: userid >>>> } >>>> >>>> But nevertheless I can't register the device. I get this error: >>>> >>>> no valid aps-environment (the message is not in English, so I >>>> translate it freely:"It was not found a valid aps-environment for the app") >>>> >>>> What can be wrong? >>>> >>>> Thanks >>>> >>>> Miguel >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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/20140316/1d0de4eb/attachment.html From miguel21op at gmail.com Sun Mar 16 13:02:03 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Sun, 16 Mar 2014 17:02:03 +0000 Subject: [aerogear-dev] Cordova and iOS In-Reply-To: References: Message-ID: Yes it is! I don't know where you live but here is indeed a sunny / gorgeous and hot (24 celsius) day. Unfortunately only in the morning I could enjoy it. In the afternoon I returned to my unpleasant chores :-( On Sun, Mar 16, 2014 at 4:53 PM, Sebastien Blanc wrote: > Glad I could help on this nice sunny sunday :) > > > > On Sun, Mar 16, 2014 at 5:25 PM, Miguel Lemos wrote: > >> Oops! A typo :-( >> >> I missed a "t": i wrote smardrifter :-( >> >> Once again, you got it!!! >> >> >> >> On Sun, Mar 16, 2014 at 4:22 PM, Miguel Lemos wrote: >> >>> Hi Seb, thanks for answering in a so short notice :-) >>> >>> Yes, I payed attention to that: com.redebiz.smartdrifter both places >>> >>> M >>> >>> >>> On Sun, Mar 16, 2014 at 4:11 PM, Sebastien Blanc wrote: >>> >>>> Hi Miguel :) >>>> I will dig more into it tomorrow but first thing that comes in mind >>>> (because I did this error in the beginning) is to be sure that the bundle >>>> you created in the apple portal is exactly the same as the one in your >>>> cordova app >>>> Seb >>>> >>>> >>>> >>>> On Sun, Mar 16, 2014 at 5:02 PM, Miguel Lemos wrote: >>>> >>>>> Hi all! >>>>> >>>>> As you know I managed - with a little help from my friends ;-) -to >>>>> have the push notifications working on Android. But with iOS, not the same >>>>> luck so far. What I've done: >>>>> >>>>> a) I created my development profile at Apple; >>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>> c) I installed the devprof profile (the mobile provision file) in >>>>> Xcode (which says it's valid); >>>>> d) I inserted the variant ID and Secret on my phone code, like this >>>>> (keys are not real): >>>>> >>>>> if(device.platform=='iOS'){ >>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>> } else if (device.platform=='Android'){ >>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>> } >>>>> var pushConfig = { >>>>> senderID: "278695547260", // not relevant for Android anyway >>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>> variantID: varID, >>>>> variantSecret: varSec, >>>>> alias: userid >>>>> } >>>>> >>>>> But nevertheless I can't register the device. I get this error: >>>>> >>>>> no valid aps-environment (the message is not in English, so I >>>>> translate it freely:"It was not found a valid aps-environment for the app") >>>>> >>>>> What can be wrong? >>>>> >>>>> Thanks >>>>> >>>>> Miguel >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.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/20140316/5b8cc89e/attachment-0001.html From miguel21op at gmail.com Sun Mar 16 13:54:51 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Sun, 16 Mar 2014 17:54:51 +0000 Subject: [aerogear-dev] Cordova and iOS In-Reply-To: References: Message-ID: Yes, it's working now :-) It was easy; the problem was caused because there was a "small" typo on the Bundle ID I created in the Apple service (a letter was missing...). By the way: the in-depth explanation about setting up the service on Apple - made by Mathias, I think - is very clear. Kudos to you all :-) M On Sun, Mar 16, 2014 at 5:02 PM, Miguel Lemos wrote: > Yes it is! I don't know where you live but here is indeed a sunny / > gorgeous and hot (24 celsius) day. Unfortunately only in the morning I > could enjoy it. In the afternoon I returned to my unpleasant chores :-( > > > On Sun, Mar 16, 2014 at 4:53 PM, Sebastien Blanc wrote: > >> Glad I could help on this nice sunny sunday :) >> >> >> >> On Sun, Mar 16, 2014 at 5:25 PM, Miguel Lemos wrote: >> >>> Oops! A typo :-( >>> >>> I missed a "t": i wrote smardrifter :-( >>> >>> Once again, you got it!!! >>> >>> >>> >>> On Sun, Mar 16, 2014 at 4:22 PM, Miguel Lemos wrote: >>> >>>> Hi Seb, thanks for answering in a so short notice :-) >>>> >>>> Yes, I payed attention to that: com.redebiz.smartdrifter both places >>>> >>>> M >>>> >>>> >>>> On Sun, Mar 16, 2014 at 4:11 PM, Sebastien Blanc wrote: >>>> >>>>> Hi Miguel :) >>>>> I will dig more into it tomorrow but first thing that comes in mind >>>>> (because I did this error in the beginning) is to be sure that the bundle >>>>> you created in the apple portal is exactly the same as the one in your >>>>> cordova app >>>>> Seb >>>>> >>>>> >>>>> >>>>> On Sun, Mar 16, 2014 at 5:02 PM, Miguel Lemos wrote: >>>>> >>>>>> Hi all! >>>>>> >>>>>> As you know I managed - with a little help from my friends ;-) -to >>>>>> have the push notifications working on Android. But with iOS, not the same >>>>>> luck so far. What I've done: >>>>>> >>>>>> a) I created my development profile at Apple; >>>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>>> c) I installed the devprof profile (the mobile provision file) in >>>>>> Xcode (which says it's valid); >>>>>> d) I inserted the variant ID and Secret on my phone code, like this >>>>>> (keys are not real): >>>>>> >>>>>> if(device.platform=='iOS'){ >>>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>>> } else if (device.platform=='Android'){ >>>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>>> } >>>>>> var pushConfig = { >>>>>> senderID: "278695547260", // not relevant for Android anyway >>>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>>> variantID: varID, >>>>>> variantSecret: varSec, >>>>>> alias: userid >>>>>> } >>>>>> >>>>>> But nevertheless I can't register the device. I get this error: >>>>>> >>>>>> no valid aps-environment (the message is not in English, so I >>>>>> translate it freely:"It was not found a valid aps-environment for the app") >>>>>> >>>>>> What can be wrong? >>>>>> >>>>>> Thanks >>>>>> >>>>>> Miguel >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.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/20140316/e11c0ba4/attachment.html From matzew at apache.org Sun Mar 16 14:43:16 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Sun, 16 Mar 2014 19:43:16 +0100 Subject: [aerogear-dev] Cordova and iOS In-Reply-To: References: Message-ID: Does the app-id (bundle identifier) match the one which you created the SSL certificate for? Otherwise it is not valid to Apple -Matthias On Sunday, March 16, 2014, Miguel Lemos wrote: > Hi all! > > As you know I managed - with a little help from my friends ;-) -to have > the push notifications working on Android. But with iOS, not the same luck > so far. What I've done: > > a) I created my development profile at Apple; > b) I uploaded the Certificates.p12 to the AeroGear Server; > c) I installed the devprof profile (the mobile provision file) in Xcode > (which says it's valid); > d) I inserted the variant ID and Secret on my phone code, like this (keys > are not real): > > if(device.platform=='iOS'){ > varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; > varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; > } else if (device.platform=='Android'){ > varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; > varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; > } > var pushConfig = { > senderID: "278695547260", // not relevant for Android anyway > pushServerURL: "https://aerogear-metalpush.rhcloud.com", > variantID: varID, > variantSecret: varSec, > alias: userid > } > > But nevertheless I can't register the device. I get this error: > > no valid aps-environment (the message is not in English, so I translate > it freely:"It was not found a valid aps-environment for the app") > > What can be wrong? > > Thanks > > Miguel > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140316/5c76dfd4/attachment.html From matzew at apache.org Sun Mar 16 14:45:27 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Sun, 16 Mar 2014 19:45:27 +0100 Subject: [aerogear-dev] Cordova and iOS In-Reply-To: References: Message-ID: Just saw the rest of the thread :-) Glad it works! -Matthias On Sunday, March 16, 2014, Matthias Wessendorf wrote: > Does the app-id (bundle identifier) match the one which you created the > SSL certificate for? > > Otherwise it is not valid to Apple > > -Matthias > > On Sunday, March 16, 2014, Miguel Lemos > > wrote: > >> Hi all! >> >> As you know I managed - with a little help from my friends ;-) -to have >> the push notifications working on Android. But with iOS, not the same luck >> so far. What I've done: >> >> a) I created my development profile at Apple; >> b) I uploaded the Certificates.p12 to the AeroGear Server; >> c) I installed the devprof profile (the mobile provision file) in Xcode >> (which says it's valid); >> d) I inserted the variant ID and Secret on my phone code, like this (keys >> are not real): >> >> if(device.platform=='iOS'){ >> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >> } else if (device.platform=='Android'){ >> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >> } >> var pushConfig = { >> senderID: "278695547260", // not relevant for Android anyway >> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >> variantID: varID, >> variantSecret: varSec, >> alias: userid >> } >> >> But nevertheless I can't register the device. I get this error: >> >> no valid aps-environment (the message is not in English, so I translate >> it freely:"It was not found a valid aps-environment for the app") >> >> What can be wrong? >> >> Thanks >> >> Miguel >> > > > -- > Sent from Gmail Mobile > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140316/8f7330ac/attachment.html From daniel.bevenius at gmail.com Sun Mar 16 14:57:40 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Sun, 16 Mar 2014 19:57:40 +0100 Subject: [aerogear-dev] Team meeting agenda Message-ID: http://oksoclap.com/p/aerogear-team-mgt-20140317 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140316/b8e72b9c/attachment.html From miguel21op at gmail.com Sun Mar 16 15:09:37 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Sun, 16 Mar 2014 19:09:37 +0000 Subject: [aerogear-dev] Cordova and iOS In-Reply-To: References: Message-ID: [?] On Sun, Mar 16, 2014 at 6:45 PM, Matthias Wessendorf wrote: > Just saw the rest of the thread :-) > > Glad it works! > > -Matthias > > > On Sunday, March 16, 2014, Matthias Wessendorf wrote: > >> Does the app-id (bundle identifier) match the one which you created the >> SSL certificate for? >> >> Otherwise it is not valid to Apple >> >> -Matthias >> >> On Sunday, March 16, 2014, Miguel Lemos wrote: >> >>> Hi all! >>> >>> As you know I managed - with a little help from my friends ;-) -to have >>> the push notifications working on Android. But with iOS, not the same luck >>> so far. What I've done: >>> >>> a) I created my development profile at Apple; >>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>> c) I installed the devprof profile (the mobile provision file) in Xcode >>> (which says it's valid); >>> d) I inserted the variant ID and Secret on my phone code, like this >>> (keys are not real): >>> >>> if(device.platform=='iOS'){ >>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>> } else if (device.platform=='Android'){ >>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>> } >>> var pushConfig = { >>> senderID: "278695547260", // not relevant for Android anyway >>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>> variantID: varID, >>> variantSecret: varSec, >>> alias: userid >>> } >>> >>> But nevertheless I can't register the device. I get this error: >>> >>> no valid aps-environment (the message is not in English, so I translate >>> it freely:"It was not found a valid aps-environment for the app") >>> >>> What can be wrong? >>> >>> Thanks >>> >>> Miguel >>> >> >> >> -- >> Sent from Gmail Mobile >> > > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140316/2da1754e/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 116 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140316/2da1754e/attachment-0001.gif From tiagor87 at gmail.com Sun Mar 16 17:20:29 2014 From: tiagor87 at gmail.com (Tiago Resende) Date: Sun, 16 Mar 2014 18:20:29 -0300 Subject: [aerogear-dev] SQLite Store Order By and Auto Increment ID Message-ID: Hi guys, thanks for the other day, you really helped me. I have two questions today. How can I perform a query using "order by" statement in SQLStore? I did a readAll, then I ordered in memory using Ordering. The second question is how can I indicate to AeroGear that it should use an auto increment primary key for a table. I created an AutoGeneratorId Class, but it's not working beautifully for SQLStore. I had to create an update method and call it for every object, I didn't like it, but I couldn't find a better solution reading the documentation. I really appreciate your help. Thanks. -- *Tiago de Carvalho Resende* -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140316/728c5879/attachment.html From miguel21op at gmail.com Mon Mar 17 05:53:39 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 09:53:39 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: Message-ID: I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. As I told you, the same code works just fine in Android. Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... Thanks M Enviado do meu iPhone No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: > Just saw the rest of the thread :-) > > Glad it works! > > -Matthias > >> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >> >> Otherwise it is not valid to Apple >> >> -Matthias >> >>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>> Hi all! >>> >>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>> >>> a) I created my development profile at Apple; >>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>> >>> if(device.platform=='iOS'){ >>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>> } else if (device.platform=='Android'){ >>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>> } >>> >>> var pushConfig = { >>> senderID: "278695547260", // not relevant for Android anyway >>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>> variantID: varID, >>> variantSecret: varSec, >>> alias: userid >>> } >>> >>> But nevertheless I can't register the device. I get this error: >>> >>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>> >>> What can be wrong? >>> >>> Thanks >>> >>> Miguel >> >> >> -- >> Sent from Gmail Mobile > > > -- > Sent from Gmail Mobile > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/58586bef/attachment.html From vmfamaral at gmail.com Mon Mar 17 06:06:02 2014 From: vmfamaral at gmail.com (oxsav) Date: Mon, 17 Mar 2014 03:06:02 -0700 (PDT) Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: References: Message-ID: <1395050762975-6834.post@n5.nabble.com> Hi. yes I'm sure, I print the aerogo (object) in the console and it appears with a few methods, but not includes the "UnifiedPushClient". I saw the source code of aerogo.js and some of the methods exist in the code. so I think it's loaded correctly. I changed it in the manifest.json file to be loaded in the scripts/vendor folder, so that is not the problem. (sorry for my bad english.) Thanks again, -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6834.html Sent from the aerogear-dev mailing list archive at Nabble.com. From edewit at redhat.com Mon Mar 17 06:13:02 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 17 Mar 2014 11:13:02 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: Message-ID: Hi Miguel, Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. Hope this helps, Erik Jan On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: > I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. > > If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. > > As I told you, the same code works just fine in Android. > > Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... > > Thanks > > M > > Enviado do meu iPhone > > No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: > >> Just saw the rest of the thread :-) >> >> Glad it works! >> >> -Matthias >> >> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >> >> Otherwise it is not valid to Apple >> >> -Matthias >> >> On Sunday, March 16, 2014, Miguel Lemos wrote: >> Hi all! >> >> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >> >> a) I created my development profile at Apple; >> b) I uploaded the Certificates.p12 to the AeroGear Server; >> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >> >> if(device.platform=='iOS'){ >> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >> } else if (device.platform=='Android'){ >> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >> } >> >> var pushConfig = { >> senderID: "278695547260", // not relevant for Android anyway >> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >> variantID: varID, >> variantSecret: varSec, >> alias: userid >> } >> >> But nevertheless I can't register the device. I get this error: >> >> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >> >> What can be wrong? >> >> Thanks >> >> Miguel >> >> >> -- >> Sent from Gmail Mobile >> >> >> -- >> Sent from Gmail Mobile >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/94fd93ac/attachment.html From miguel21op at gmail.com Mon Mar 17 06:24:10 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 10:24:10 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: Message-ID: <512ECD71-2B55-4552-B294-4A66AA2E0E66@gmail.com> Hi Erik! I already use the Safari debugger too and no problem (error) is shown there. Neither in the Xcode, besides that odd thing I told before. Anyway, as I told before the same code works just fine with Android. About the new version of the plugin: do I have to make any changes to the Javascript code? Enviado do meu iPhone No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: > Hi Miguel, > > Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. > > Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. > > Hope this helps, > Erik Jan > >> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >> >> I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. >> >> If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. >> >> As I told you, the same code works just fine in Android. >> >> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... >> >> Thanks >> >> M >> >> Enviado do meu iPhone >> >> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: >> >>> Just saw the rest of the thread :-) >>> >>> Glad it works! >>> >>> -Matthias >>> >>>> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >>>> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >>>> >>>> Otherwise it is not valid to Apple >>>> >>>> -Matthias >>>> >>>>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>>>> Hi all! >>>>> >>>>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>>>> >>>>> a) I created my development profile at Apple; >>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>>>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>>>> >>>>> if(device.platform=='iOS'){ >>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>> } else if (device.platform=='Android'){ >>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>> } >>>>> >>>>> var pushConfig = { >>>>> senderID: "278695547260", // not relevant for Android anyway >>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>> variantID: varID, >>>>> variantSecret: varSec, >>>>> alias: userid >>>>> } >>>>> >>>>> But nevertheless I can't register the device. I get this error: >>>>> >>>>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>>>> >>>>> What can be wrong? >>>>> >>>>> Thanks >>>>> >>>>> Miguel >>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>> >>> >>> -- >>> Sent from Gmail Mobile >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/29ef5899/attachment-0001.html From miguel21op at gmail.com Mon Mar 17 06:30:05 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 10:30:05 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: Message-ID: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 M Enviado do meu iPhone No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: > Hi Miguel, > > Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. > > Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. > > Hope this helps, > Erik Jan > >> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >> >> I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. >> >> If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. >> >> As I told you, the same code works just fine in Android. >> >> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... >> >> Thanks >> >> M >> >> Enviado do meu iPhone >> >> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: >> >>> Just saw the rest of the thread :-) >>> >>> Glad it works! >>> >>> -Matthias >>> >>>> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >>>> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >>>> >>>> Otherwise it is not valid to Apple >>>> >>>> -Matthias >>>> >>>>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>>>> Hi all! >>>>> >>>>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>>>> >>>>> a) I created my development profile at Apple; >>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>>>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>>>> >>>>> if(device.platform=='iOS'){ >>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>> } else if (device.platform=='Android'){ >>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>> } >>>>> >>>>> var pushConfig = { >>>>> senderID: "278695547260", // not relevant for Android anyway >>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>> variantID: varID, >>>>> variantSecret: varSec, >>>>> alias: userid >>>>> } >>>>> >>>>> But nevertheless I can't register the device. I get this error: >>>>> >>>>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>>>> >>>>> What can be wrong? >>>>> >>>>> Thanks >>>>> >>>>> Miguel >>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>> >>> >>> -- >>> Sent from Gmail Mobile >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/8eb21111/attachment.html From miguel21op at gmail.com Mon Mar 17 06:35:25 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 10:35:25 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: Message-ID: <514A0D5A-6BC7-4E86-9967-567178E8783B@gmail.com> I forget to mention, but for sure you already know it, that Xcode throws some warning messages about the Aerogear libraries (deprecated instructions). Enviado do meu iPhone No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: > Hi Miguel, > > Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. > > Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. > > Hope this helps, > Erik Jan > >> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >> >> I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. >> >> If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. >> >> As I told you, the same code works just fine in Android. >> >> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... >> >> Thanks >> >> M >> >> Enviado do meu iPhone >> >> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: >> >>> Just saw the rest of the thread :-) >>> >>> Glad it works! >>> >>> -Matthias >>> >>>> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >>>> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >>>> >>>> Otherwise it is not valid to Apple >>>> >>>> -Matthias >>>> >>>>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>>>> Hi all! >>>>> >>>>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>>>> >>>>> a) I created my development profile at Apple; >>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>>>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>>>> >>>>> if(device.platform=='iOS'){ >>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>> } else if (device.platform=='Android'){ >>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>> } >>>>> >>>>> var pushConfig = { >>>>> senderID: "278695547260", // not relevant for Android anyway >>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>> variantID: varID, >>>>> variantSecret: varSec, >>>>> alias: userid >>>>> } >>>>> >>>>> But nevertheless I can't register the device. I get this error: >>>>> >>>>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>>>> >>>>> What can be wrong? >>>>> >>>>> Thanks >>>>> >>>>> Miguel >>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>> >>> >>> -- >>> Sent from Gmail Mobile >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/3efcc944/attachment.html From edewit at redhat.com Mon Mar 17 07:09:31 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 17 Mar 2014 12:09:31 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> Message-ID: Hi, That could be a problem, I think Xcode 5.1 doesn?t work with Cordova, there are some issue that will be fixed in 3.5 you might have to revert this update. As for the plugin update the javascript API has not change yet, but it will when we merge the simplification branch. Cheers, Erik Jan On 17 Mar,2014, at 11:30 , Miguel Lemos wrote: > Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 > > M > > > Enviado do meu iPhone > > No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: > >> Hi Miguel, >> >> Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. >> >> Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. >> >> Hope this helps, >> Erik Jan >> >> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >> >>> I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. >>> >>> If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. >>> >>> As I told you, the same code works just fine in Android. >>> >>> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... >>> >>> Thanks >>> >>> M >>> >>> Enviado do meu iPhone >>> >>> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: >>> >>>> Just saw the rest of the thread :-) >>>> >>>> Glad it works! >>>> >>>> -Matthias >>>> >>>> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >>>> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >>>> >>>> Otherwise it is not valid to Apple >>>> >>>> -Matthias >>>> >>>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>>> Hi all! >>>> >>>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>>> >>>> a) I created my development profile at Apple; >>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>>> >>>> if(device.platform=='iOS'){ >>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>> } else if (device.platform=='Android'){ >>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>> } >>>> >>>> var pushConfig = { >>>> senderID: "278695547260", // not relevant for Android anyway >>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>> variantID: varID, >>>> variantSecret: varSec, >>>> alias: userid >>>> } >>>> >>>> But nevertheless I can't register the device. I get this error: >>>> >>>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>>> >>>> What can be wrong? >>>> >>>> Thanks >>>> >>>> Miguel >>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>>> >>>> >>>> -- >>>> Sent from Gmail Mobile >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ > 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/20140317/5a7eb28b/attachment-0001.html From miguel21op at gmail.com Mon Mar 17 07:18:27 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 11:18:27 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> Message-ID: <1799F44B-5D68-46E6-828C-10B638E9CE21@gmail.com> No, it works with Cordova perfectly! There's no problem. It's only needed to manually update the compilation definitions. But if you're starting a new project, not even that problem exists. And those Aerogear warning messages already were present in XCode 5. Besides, if you update the phone to iOS 7.1, you must update Xcode accordingly. No way back possible. Enviado do meu iPhone No dia 17/03/2014, ?s 11:09, Erik Jan de Wit escreveu: > Hi, > > That could be a problem, I think Xcode 5.1 doesn?t work with Cordova, there are some issue that will be fixed in 3.5 you might have to revert this update. As for the plugin update the javascript API has not change yet, but it will when we merge the simplification branch. > > Cheers, > Erik Jan > >> On 17 Mar,2014, at 11:30 , Miguel Lemos wrote: >> >> Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 >> >> M >> >> >> Enviado do meu iPhone >> >> No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: >> >>> Hi Miguel, >>> >>> Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. >>> >>> Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. >>> >>> Hope this helps, >>> Erik Jan >>> >>>> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >>>> >>>> I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. >>>> >>>> If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. >>>> >>>> As I told you, the same code works just fine in Android. >>>> >>>> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... >>>> >>>> Thanks >>>> >>>> M >>>> >>>> Enviado do meu iPhone >>>> >>>> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: >>>> >>>>> Just saw the rest of the thread :-) >>>>> >>>>> Glad it works! >>>>> >>>>> -Matthias >>>>> >>>>>> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >>>>>> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >>>>>> >>>>>> Otherwise it is not valid to Apple >>>>>> >>>>>> -Matthias >>>>>> >>>>>>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>>>>>> Hi all! >>>>>>> >>>>>>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>>>>>> >>>>>>> a) I created my development profile at Apple; >>>>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>>>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>>>>>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>>>>>> >>>>>>> if(device.platform=='iOS'){ >>>>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>>>> } else if (device.platform=='Android'){ >>>>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>>>> } >>>>>>> >>>>>>> var pushConfig = { >>>>>>> senderID: "278695547260", // not relevant for Android anyway >>>>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>>>> variantID: varID, >>>>>>> variantSecret: varSec, >>>>>>> alias: userid >>>>>>> } >>>>>>> >>>>>>> But nevertheless I can't register the device. I get this error: >>>>>>> >>>>>>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>>>>>> >>>>>>> What can be wrong? >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Miguel >>>>>> >>>>>> >>>>>> -- >>>>>> Sent from Gmail Mobile >>>>> >>>>> >>>>> -- >>>>> Sent from Gmail Mobile >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140317/d317d575/attachment.html From vmfamaral at gmail.com Mon Mar 17 07:45:11 2014 From: vmfamaral at gmail.com (oxsav) Date: Mon, 17 Mar 2014 04:45:11 -0700 (PDT) Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: References: Message-ID: <1395056711933-6841.post@n5.nabble.com> Ok I did a little change. Loading the "aerogear.unifiedpush.js" file and it recognized the "UnifiedPushClient" . But now I have another problem when I try to execute this command: */curl -3 -u "{pushApplicationID}:{masterSecret}" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"message": {"alert":"Push Notification"}}' https://SERVER:PORT/CONTEXT/rest/sender/* with all fields full filled correctly it returns me in the response: /* upload completely sent off: 42out of 42 bytes < HTTP/1.1 401 Unauthorized < Connection: keep-alive * Authentication problem. Ignoring this. < WWW-Authenticate: Basic realm="AeroGear UnifiedPush Server" < X-Powered-By: Undertow 1 < Server: Wildfly 8 < Content-Type: application/json < Content-Length: 20 < Date: Mon, 17 Mar 2014 11:28:33 GMT* / any idea what can be? -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6841.html Sent from the aerogear-dev mailing list archive at Nabble.com. From miguel21op at gmail.com Mon Mar 17 07:53:33 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 11:53:33 +0000 Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: <1395056711933-6841.post@n5.nabble.com> References: <1395056711933-6841.post@n5.nabble.com> Message-ID: <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> What url are you using? Did you change the "context", etc. to your own / platform specific parameters? Sorry for asking ;-) Enviado do meu iPhone No dia 17/03/2014, ?s 11:45, oxsav escreveu: > Ok I did a little change. Loading the "aerogear.unifiedpush.js" file and it > recognized the "UnifiedPushClient" . But now I have another problem when I > try to execute this command: > > */curl -3 -u "{pushApplicationID}:{masterSecret}" > -v -H "Accept: application/json" -H "Content-type: application/json" > -X POST -d '{"message": {"alert":"Push Notification"}}' > https://SERVER:PORT/CONTEXT/rest/sender/* > > with all fields full filled correctly it returns me in the response: > /* upload completely sent off: 42out of 42 bytes > < HTTP/1.1 401 Unauthorized > < Connection: keep-alive > * Authentication problem. Ignoring this. > < WWW-Authenticate: Basic realm="AeroGear UnifiedPush Server" > < X-Powered-By: Undertow 1 > < Server: Wildfly 8 > < Content-Type: application/json > < Content-Length: 20 > < Date: Mon, 17 Mar 2014 11:28:33 GMT* > / > > > any idea what can be? > > > > > -- > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6841.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From vmfamaral at gmail.com Mon Mar 17 07:57:13 2014 From: vmfamaral at gmail.com (oxsav) Date: Mon, 17 Mar 2014 04:57:13 -0700 (PDT) Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> Message-ID: <1395057433543-6843.post@n5.nabble.com> Hello I'm using http://:/unifiedpush-server-0.10.0/rest/sender I'm using http because if I use https returns me an error of sslv3: */error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number/ * tks -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6843.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Mon Mar 17 08:24:36 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 17 Mar 2014 13:24:36 +0100 Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: <1395057433543-6843.post@n5.nabble.com> References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> Message-ID: For http (no TLS), please skip the -3 part (that is for SSLv3) On Mon, Mar 17, 2014 at 12:57 PM, oxsav wrote: > Hello I'm using > > http://:/unifiedpush-server-0.10.0/rest/sender > > I'm using http because if I use https returns me an error of sslv3: > */error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number/ > * > > tks > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6843.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/0432afe8/attachment-0001.html From vmfamaral at gmail.com Mon Mar 17 08:28:50 2014 From: vmfamaral at gmail.com (oxsav) Date: Mon, 17 Mar 2014 05:28:50 -0700 (PDT) Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> Message-ID: <1395059330201-6845.post@n5.nabble.com> Skipped it same thing "Unauthorized". this only works for packaged chrome applications? or it works for unpackaged chrome applications too? Because w8ting about an hour for an package application being accepted, is not good at all.. -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6845.html Sent from the aerogear-dev mailing list archive at Nabble.com. From bsutter at redhat.com Mon Mar 17 08:32:42 2014 From: bsutter at redhat.com (Burr Sutter) Date: Mon, 17 Mar 2014 08:32:42 -0400 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <1799F44B-5D68-46E6-828C-10B638E9CE21@gmail.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <1799F44B-5D68-46E6-828C-10B638E9CE21@gmail.com> Message-ID: Was this same set of code working well on iOS 7.0? Here is a listing of the issues associated with Cordova & XCode 5.1 http://shazronatadobe.wordpress.com/2014/03/12/xcode-5-1-and-cordova-ios/ I had to uninstall XCode 5.1 and reinstall 5.0 just to get the iOS Simulator working again. On Mar 17, 2014, at 7:18 AM, Miguel Lemos wrote: > No, it works with Cordova perfectly! There's no problem. It's only needed to manually update the compilation definitions. But if you're starting a new project, not even that problem exists. > > And those Aerogear warning messages already were present in XCode 5. > > Besides, if you update the phone to iOS 7.1, you must update Xcode accordingly. No way back possible. > > Enviado do meu iPhone > > No dia 17/03/2014, ?s 11:09, Erik Jan de Wit escreveu: > >> Hi, >> >> That could be a problem, I think Xcode 5.1 doesn?t work with Cordova, there are some issue that will be fixed in 3.5 you might have to revert this update. As for the plugin update the javascript API has not change yet, but it will when we merge the simplification branch. >> >> Cheers, >> Erik Jan >> >> On 17 Mar,2014, at 11:30 , Miguel Lemos wrote: >> >>> Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 >>> >>> M >>> >>> >>> Enviado do meu iPhone >>> >>> No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: >>> >>>> Hi Miguel, >>>> >>>> Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. >>>> >>>> Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. >>>> >>>> Hope this helps, >>>> Erik Jan >>>> >>>> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >>>> >>>>> I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. >>>>> >>>>> If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. >>>>> >>>>> As I told you, the same code works just fine in Android. >>>>> >>>>> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... >>>>> >>>>> Thanks >>>>> >>>>> M >>>>> >>>>> Enviado do meu iPhone >>>>> >>>>> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: >>>>> >>>>>> Just saw the rest of the thread :-) >>>>>> >>>>>> Glad it works! >>>>>> >>>>>> -Matthias >>>>>> >>>>>> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >>>>>> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >>>>>> >>>>>> Otherwise it is not valid to Apple >>>>>> >>>>>> -Matthias >>>>>> >>>>>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>>>>> Hi all! >>>>>> >>>>>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>>>>> >>>>>> a) I created my development profile at Apple; >>>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>>>>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>>>>> >>>>>> if(device.platform=='iOS'){ >>>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>>> } else if (device.platform=='Android'){ >>>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>>> } >>>>>> >>>>>> var pushConfig = { >>>>>> senderID: "278695547260", // not relevant for Android anyway >>>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>>> variantID: varID, >>>>>> variantSecret: varSec, >>>>>> alias: userid >>>>>> } >>>>>> >>>>>> But nevertheless I can't register the device. I get this error: >>>>>> >>>>>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>>>>> >>>>>> What can be wrong? >>>>>> >>>>>> Thanks >>>>>> >>>>>> Miguel >>>>>> >>>>>> >>>>>> -- >>>>>> Sent from Gmail Mobile >>>>>> >>>>>> >>>>>> -- >>>>>> Sent from Gmail Mobile >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140317/39ea2dd3/attachment.html From matzew at apache.org Mon Mar 17 08:33:30 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 17 Mar 2014 13:33:30 +0100 Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: <1395059330201-6845.post@n5.nabble.com> References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> Message-ID: I never tried / tested the Chrome bits; However, regarding the "send" and getting a 401; Are you sure you are using the right PushApplicationID and the master secret ? It's NOT the credentials from your Chrome Variant - the send requires the credentials from the root Push Application (not the variant) On Mon, Mar 17, 2014 at 1:28 PM, oxsav wrote: > Skipped it same thing "Unauthorized". > > this only works for packaged chrome applications? or it works for > unpackaged > chrome applications too? > > Because w8ting about an hour for an package application being accepted, is > not good at all.. > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6845.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/417c8e82/attachment.html From miguel21op at gmail.com Mon Mar 17 08:46:09 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 12:46:09 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <1799F44B-5D68-46E6-828C-10B638E9CE21@gmail.com> Message-ID: <811D8776-C723-4039-ACF8-580EDA776993@gmail.com> Yes, it was. And no: I'm telling you that Cordova 3.4 works fine for me with Xcode 5.1 My app and the installed plugins work the same way as before. I only had to change the compilation parameters. Do you want I send a video? ;) Enviado do meu iPhone No dia 17/03/2014, ?s 12:32, Burr Sutter escreveu: > Was this same set of code working well on iOS 7.0? > > Here is a listing of the issues associated with Cordova & XCode 5.1 > http://shazronatadobe.wordpress.com/2014/03/12/xcode-5-1-and-cordova-ios/ > > I had to uninstall XCode 5.1 and reinstall 5.0 just to get the iOS Simulator working again. > >> On Mar 17, 2014, at 7:18 AM, Miguel Lemos wrote: >> >> No, it works with Cordova perfectly! There's no problem. It's only needed to manually update the compilation definitions. But if you're starting a new project, not even that problem exists. >> >> And those Aerogear warning messages already were present in XCode 5. >> >> Besides, if you update the phone to iOS 7.1, you must update Xcode accordingly. No way back possible. >> >> Enviado do meu iPhone >> >> No dia 17/03/2014, ?s 11:09, Erik Jan de Wit escreveu: >> >>> Hi, >>> >>> That could be a problem, I think Xcode 5.1 doesn?t work with Cordova, there are some issue that will be fixed in 3.5 you might have to revert this update. As for the plugin update the javascript API has not change yet, but it will when we merge the simplification branch. >>> >>> Cheers, >>> Erik Jan >>> >>>> On 17 Mar,2014, at 11:30 , Miguel Lemos wrote: >>>> >>>> Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 >>>> >>>> M >>>> >>>> >>>> Enviado do meu iPhone >>>> >>>> No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: >>>> >>>>> Hi Miguel, >>>>> >>>>> Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. >>>>> >>>>> Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. >>>>> >>>>> Hope this helps, >>>>> Erik Jan >>>>> >>>>>> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >>>>>> >>>>>> I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. >>>>>> >>>>>> If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. >>>>>> >>>>>> As I told you, the same code works just fine in Android. >>>>>> >>>>>> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... >>>>>> >>>>>> Thanks >>>>>> >>>>>> M >>>>>> >>>>>> Enviado do meu iPhone >>>>>> >>>>>> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: >>>>>> >>>>>>> Just saw the rest of the thread :-) >>>>>>> >>>>>>> Glad it works! >>>>>>> >>>>>>> -Matthias >>>>>>> >>>>>>>> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >>>>>>>> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >>>>>>>> >>>>>>>> Otherwise it is not valid to Apple >>>>>>>> >>>>>>>> -Matthias >>>>>>>> >>>>>>>>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>>>>>>>> Hi all! >>>>>>>>> >>>>>>>>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>>>>>>>> >>>>>>>>> a) I created my development profile at Apple; >>>>>>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>>>>>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>>>>>>>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>>>>>>>> >>>>>>>>> if(device.platform=='iOS'){ >>>>>>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>>>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>>>>>> } else if (device.platform=='Android'){ >>>>>>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>>>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>>>>>> } >>>>>>>>> >>>>>>>>> var pushConfig = { >>>>>>>>> senderID: "278695547260", // not relevant for Android anyway >>>>>>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>>>>>> variantID: varID, >>>>>>>>> variantSecret: varSec, >>>>>>>>> alias: userid >>>>>>>>> } >>>>>>>>> >>>>>>>>> But nevertheless I can't register the device. I get this error: >>>>>>>>> >>>>>>>>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>>>>>>>> >>>>>>>>> What can be wrong? >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> >>>>>>>>> Miguel >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Sent from Gmail Mobile >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sent from Gmail Mobile >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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/20140317/3f73fb19/attachment-0001.html From miguel21op at gmail.com Mon Mar 17 08:49:10 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 12:49:10 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <1799F44B-5D68-46E6-828C-10B638E9CE21@gmail.com> Message-ID: <830249DD-1EE2-466C-8942-84FB7CFB8DF4@gmail.com> And as the blog says I reinstalled the ios-sim ( when I compiled the app for the first time it said it was missing). Enviado do meu iPhone No dia 17/03/2014, ?s 12:32, Burr Sutter escreveu: > Was this same set of code working well on iOS 7.0? > > Here is a listing of the issues associated with Cordova & XCode 5.1 > http://shazronatadobe.wordpress.com/2014/03/12/xcode-5-1-and-cordova-ios/ > > I had to uninstall XCode 5.1 and reinstall 5.0 just to get the iOS Simulator working again. > >> On Mar 17, 2014, at 7:18 AM, Miguel Lemos wrote: >> >> No, it works with Cordova perfectly! There's no problem. It's only needed to manually update the compilation definitions. But if you're starting a new project, not even that problem exists. >> >> And those Aerogear warning messages already were present in XCode 5. >> >> Besides, if you update the phone to iOS 7.1, you must update Xcode accordingly. No way back possible. >> >> Enviado do meu iPhone >> >> No dia 17/03/2014, ?s 11:09, Erik Jan de Wit escreveu: >> >>> Hi, >>> >>> That could be a problem, I think Xcode 5.1 doesn?t work with Cordova, there are some issue that will be fixed in 3.5 you might have to revert this update. As for the plugin update the javascript API has not change yet, but it will when we merge the simplification branch. >>> >>> Cheers, >>> Erik Jan >>> >>>> On 17 Mar,2014, at 11:30 , Miguel Lemos wrote: >>>> >>>> Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 >>>> >>>> M >>>> >>>> >>>> Enviado do meu iPhone >>>> >>>> No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: >>>> >>>>> Hi Miguel, >>>>> >>>>> Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. >>>>> >>>>> Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. >>>>> >>>>> Hope this helps, >>>>> Erik Jan >>>>> >>>>>> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >>>>>> >>>>>> I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. >>>>>> >>>>>> If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. >>>>>> >>>>>> As I told you, the same code works just fine in Android. >>>>>> >>>>>> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... >>>>>> >>>>>> Thanks >>>>>> >>>>>> M >>>>>> >>>>>> Enviado do meu iPhone >>>>>> >>>>>> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: >>>>>> >>>>>>> Just saw the rest of the thread :-) >>>>>>> >>>>>>> Glad it works! >>>>>>> >>>>>>> -Matthias >>>>>>> >>>>>>>> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >>>>>>>> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >>>>>>>> >>>>>>>> Otherwise it is not valid to Apple >>>>>>>> >>>>>>>> -Matthias >>>>>>>> >>>>>>>>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>>>>>>>> Hi all! >>>>>>>>> >>>>>>>>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>>>>>>>> >>>>>>>>> a) I created my development profile at Apple; >>>>>>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>>>>>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>>>>>>>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>>>>>>>> >>>>>>>>> if(device.platform=='iOS'){ >>>>>>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>>>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>>>>>> } else if (device.platform=='Android'){ >>>>>>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>>>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>>>>>> } >>>>>>>>> >>>>>>>>> var pushConfig = { >>>>>>>>> senderID: "278695547260", // not relevant for Android anyway >>>>>>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>>>>>> variantID: varID, >>>>>>>>> variantSecret: varSec, >>>>>>>>> alias: userid >>>>>>>>> } >>>>>>>>> >>>>>>>>> But nevertheless I can't register the device. I get this error: >>>>>>>>> >>>>>>>>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>>>>>>>> >>>>>>>>> What can be wrong? >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> >>>>>>>>> Miguel >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Sent from Gmail Mobile >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sent from Gmail Mobile >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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/20140317/baf5b905/attachment.html From matzew at apache.org Mon Mar 17 08:49:42 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 17 Mar 2014 13:49:42 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <811D8776-C723-4039-ACF8-580EDA776993@gmail.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <1799F44B-5D68-46E6-828C-10B638E9CE21@gmail.com> <811D8776-C723-4039-ACF8-580EDA776993@gmail.com> Message-ID: On Mon, Mar 17, 2014 at 1:46 PM, Miguel Lemos wrote: > Yes, it was. > > And no: I'm telling you that Cordova 3.4 works fine for me with Xcode 5.1 > My app and the installed plugins work the same way as before. I only had > to change the compilation parameters. > > Do you want I send a video? ;) > sure! why not? > > > Enviado do meu iPhone > > No dia 17/03/2014, ?s 12:32, Burr Sutter escreveu: > > Was this same set of code working well on iOS 7.0? > > Here is a listing of the issues associated with Cordova & XCode 5.1 > http://shazronatadobe.wordpress.com/2014/03/12/xcode-5-1-and-cordova-ios/ > > I had to uninstall XCode 5.1 and reinstall 5.0 just to get the iOS > Simulator working again. > > On Mar 17, 2014, at 7:18 AM, Miguel Lemos wrote: > > No, it works with Cordova perfectly! There's no problem. It's only needed > to manually update the compilation definitions. But if you're starting a > new project, not even that problem exists. > > And those Aerogear warning messages already were present in XCode 5. > > Besides, if you update the phone to iOS 7.1, you must update Xcode > accordingly. No way back possible. > > Enviado do meu iPhone > > No dia 17/03/2014, ?s 11:09, Erik Jan de Wit escreveu: > > Hi, > > That could be a problem, I think Xcode 5.1 doesn't work with Cordova, > there are some issue that will be fixed in 3.5 you might have to revert > this update. As for the plugin update the javascript API has not change > yet, but it will when we merge the simplification branch. > > Cheers, > Erik Jan > > On 17 Mar,2014, at 11:30 , Miguel Lemos wrote: > > Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 > > M > > > Enviado do meu iPhone > > No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: > > Hi Miguel, > > Not sure what the problem is, but you could maybe try to debug it a bit. > The easiest way is to start safari on your machine and on your device > enable the web inspector ( Settings > Safari > Advanced ). Then in safari > you can go to develop > "device name" then you can open the javascript > console and see if there was an error of some kind. > > Also we just released a new version (0.0.3) that that fixes some bugs you > could also try to update to that version by removing and adding the plugin > in you cordova project. > > Hope this helps, > Erik Jan > > On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: > > I have this problem now: in iPhone (the same code works just fine with > Android) the event handler never triggers the alert message. > > If the app is running in the background I get the message in the status > bar, the badge shows, but when I touch on it or if the app is in the > foreground the alert box inside the app never shows. > > As I told you, the same code works just fine in Android. > > Meanwhile I noticed this odd thing in the Xcode debugger: even if the app > is running in the background, when the push notification arrives it says a > foreground message has arrived... > > Thanks > > M > > Enviado do meu iPhone > > No dia 16/03/2014, ?s 18:45, Matthias Wessendorf > escreveu: > > Just saw the rest of the thread :-) > > Glad it works! > > -Matthias > > On Sunday, March 16, 2014, Matthias Wessendorf wrote: > >> Does the app-id (bundle identifier) match the one which you created the >> SSL certificate for? >> >> Otherwise it is not valid to Apple >> >> -Matthias >> >> On Sunday, March 16, 2014, Miguel Lemos wrote: >> >>> Hi all! >>> >>> As you know I managed - with a little help from my friends ;-) -to have >>> the push notifications working on Android. But with iOS, not the same luck >>> so far. What I've done: >>> >>> a) I created my development profile at Apple; >>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>> c) I installed the devprof profile (the mobile provision file) in Xcode >>> (which says it's valid); >>> d) I inserted the variant ID and Secret on my phone code, like this >>> (keys are not real): >>> >>> if(device.platform=='iOS'){ >>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>> } else if (device.platform=='Android'){ >>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>> } >>> var pushConfig = { >>> senderID: "278695547260", // not relevant for Android anyway >>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>> variantID: varID, >>> variantSecret: varSec, >>> alias: userid >>> } >>> >>> But nevertheless I can't register the device. I get this error: >>> >>> no valid aps-environment (the message is not in English, so I translate >>> it freely:"It was not found a valid aps-environment for the app") >>> >>> What can be wrong? >>> >>> Thanks >>> >>> Miguel >>> >> >> >> -- >> Sent from Gmail Mobile >> > > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140317/63a69b4a/attachment-0001.html From vmfamaral at gmail.com Mon Mar 17 08:51:57 2014 From: vmfamaral at gmail.com (oxsav) Date: Mon, 17 Mar 2014 05:51:57 -0700 (PDT) Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> Message-ID: <1395060717930-6851.post@n5.nabble.com> Yep, I'm sure that I'm doing that. Can be a problem with the h2database? because in deployments it appears as "undeployed". thanks, -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6851.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Mon Mar 17 08:54:03 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 17 Mar 2014 13:54:03 +0100 Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: <1395060717930-6851.post@n5.nabble.com> References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> <1395060717930-6851.post@n5.nabble.com> Message-ID: hrm, weird make sure the xml file ( https://github.com/aerogear/aerogear-unifiedpush-server/blob/0.10.x/databases/unifiedpush-h2-ds.xml) is deployed into $JBOSS/standalone/deployments On Mon, Mar 17, 2014 at 1:51 PM, oxsav wrote: > Yep, I'm sure that I'm doing that. > > Can be a problem with the h2database? because in deployments it appears as > "undeployed". > > thanks, > > > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6851.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/e311b7ca/attachment.html From miguel21op at gmail.com Mon Mar 17 08:55:15 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 12:55:15 +0000 Subject: [aerogear-dev] OK :) Message-ID: Now I'm not in office, but I send to you a screenshot of my app setup info. It's in Portuguese but in the "Perfil do Equipamento" section you can see the info returned by the system (I didn't paste anything) ;-) Cheers M -------------- next part -------------- A non-text attachment was scrubbed... Name: fotografia.PNG Type: image/png Size: 132761 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/8189f084/attachment-0001.png -------------- next part -------------- Enviado do meu iPhone From vmfamaral at gmail.com Mon Mar 17 09:19:23 2014 From: vmfamaral at gmail.com (oxsav) Date: Mon, 17 Mar 2014 06:19:23 -0700 (PDT) Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> <1395060717930-6851.post@n5.nabble.com> Message-ID: <1395062363438-6854.post@n5.nabble.com> Hmm did it. And the problem persists. I analysed the log from the jboss and when I try to open the URL: http://150.140.184.246:4441/unifiedpush-server-0.10.0 , returns me the following error: /*5:07:49,969 ERROR [org.jboss.as.ejb3.invocation] (default task-1) JBAS014134: EJB Invocation failed on component Ping for method public javax.ws.rs.core.Response org.jboss.aerogear.unifiedpush.rest.util.Ping.ping(): javax.ejb.EJBException: org.jboss.aerogear.security.exception.AeroGearSecurityException: Not authorized!*/ The weird thing is, I can access that well and create my application, my variant and I already have an device registered to a variant :S .. Any idea? Tks, -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6854.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Mon Mar 17 09:28:12 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 17 Mar 2014 14:28:12 +0100 Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: <1395062363438-6854.post@n5.nabble.com> References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> <1395060717930-6851.post@n5.nabble.com> <1395062363438-6854.post@n5.nabble.com> Message-ID: On Mon, Mar 17, 2014 at 2:19 PM, oxsav wrote: > Hmm did it. And the problem persists. > > I analysed the log from the jboss and when I try to open the URL: > http://150.140.184.246:4441/unifiedpush-server-0.10.0 , returns me the > I do see the admin ui - but can not login, as I don't know your admin password > following error: > > /*5:07:49,969 ERROR [org.jboss.as.ejb3.invocation] (default task-1) > JBAS014134: EJB Invocation failed on component Ping for method public > javax.ws.rs.core.Response > org.jboss.aerogear.unifiedpush.rest.util.Ping.ping(): > javax.ejb.EJBException: > org.jboss.aerogear.security.exception.AeroGearSecurityException: Not > authorized!*/ > > The weird thing is, I can access that well and create my application, my > variant and I already have an device registered to a variant :S .. > Any idea? > > Tks, > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6854.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/263de200/attachment.html From miguel21op at gmail.com Mon Mar 17 10:34:06 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 14:34:06 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> Message-ID: Hi Erik! I could seat again in front of a Mac, and already found out what's going on. I managed to make a pop-up window appear when the notification arrives. I'll go through some more testings and afterwards I'll tell you precisely where the problem is coming from. On Mon, Mar 17, 2014 at 11:09 AM, Erik Jan de Wit wrote: > Hi, > > That could be a problem, I think Xcode 5.1 doesn?t work with Cordova, > there are some issue that will be fixed in 3.5 you might have to revert > this update. As for the plugin update the javascript API has not change > yet, but it will when we merge the simplification branch. > > Cheers, > Erik Jan > > On 17 Mar,2014, at 11:30 , Miguel Lemos wrote: > > Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 > > M > > > Enviado do meu iPhone > > No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: > > Hi Miguel, > > Not sure what the problem is, but you could maybe try to debug it a bit. > The easiest way is to start safari on your machine and on your device > enable the web inspector ( Settings > Safari > Advanced ). Then in safari > you can go to develop > ?device name? then you can open the javascript > console and see if there was an error of some kind. > > Also we just released a new version (0.0.3) that that fixes some bugs you > could also try to update to that version by removing and adding the plugin > in you cordova project. > > Hope this helps, > Erik Jan > > On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: > > I have this problem now: in iPhone (the same code works just fine with > Android) the event handler never triggers the alert message. > > If the app is running in the background I get the message in the status > bar, the badge shows, but when I touch on it or if the app is in the > foreground the alert box inside the app never shows. > > As I told you, the same code works just fine in Android. > > Meanwhile I noticed this odd thing in the Xcode debugger: even if the app > is running in the background, when the push notification arrives it says a > foreground message has arrived... > > Thanks > > M > > Enviado do meu iPhone > > No dia 16/03/2014, ?s 18:45, Matthias Wessendorf > escreveu: > > Just saw the rest of the thread :-) > > Glad it works! > > -Matthias > > On Sunday, March 16, 2014, Matthias Wessendorf wrote: > >> Does the app-id (bundle identifier) match the one which you created the >> SSL certificate for? >> >> Otherwise it is not valid to Apple >> >> -Matthias >> >> On Sunday, March 16, 2014, Miguel Lemos wrote: >> >>> Hi all! >>> >>> As you know I managed - with a little help from my friends ;-) -to have >>> the push notifications working on Android. But with iOS, not the same luck >>> so far. What I've done: >>> >>> a) I created my development profile at Apple; >>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>> c) I installed the devprof profile (the mobile provision file) in Xcode >>> (which says it's valid); >>> d) I inserted the variant ID and Secret on my phone code, like this >>> (keys are not real): >>> >>> if(device.platform=='iOS'){ >>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>> } else if (device.platform=='Android'){ >>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>> } >>> var pushConfig = { >>> senderID: "278695547260", // not relevant for Android anyway >>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>> variantID: varID, >>> variantSecret: varSec, >>> alias: userid >>> } >>> >>> But nevertheless I can't register the device. I get this error: >>> >>> no valid aps-environment (the message is not in English, so I translate >>> it freely:"It was not found a valid aps-environment for the app") >>> >>> What can be wrong? >>> >>> Thanks >>> >>> Miguel >>> >> >> >> -- >> Sent from Gmail Mobile >> > > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140317/ac80497e/attachment.html From edewit at redhat.com Mon Mar 17 10:37:33 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 17 Mar 2014 15:37:33 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> Message-ID: <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> Hi Miguel, That is good news, hope you find the cause of the problem. Cheers, Erik Jan On 17 Mar,2014, at 15:34 , Miguel Lemos wrote: > Hi Erik! > > I could seat again in front of a Mac, and already found out what's going on. I managed to make a pop-up window appear when the notification arrives. > > I'll go through some more testings and afterwards I'll tell you precisely where the problem is coming from. > > > On Mon, Mar 17, 2014 at 11:09 AM, Erik Jan de Wit wrote: > Hi, > > That could be a problem, I think Xcode 5.1 doesn?t work with Cordova, there are some issue that will be fixed in 3.5 you might have to revert this update. As for the plugin update the javascript API has not change yet, but it will when we merge the simplification branch. > > Cheers, > Erik Jan > > On 17 Mar,2014, at 11:30 , Miguel Lemos wrote: > >> Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 >> >> M >> >> >> Enviado do meu iPhone >> >> No dia 17/03/2014, ?s 10:13, Erik Jan de Wit escreveu: >> >>> Hi Miguel, >>> >>> Not sure what the problem is, but you could maybe try to debug it a bit. The easiest way is to start safari on your machine and on your device enable the web inspector ( Settings > Safari > Advanced ). Then in safari you can go to develop > ?device name? then you can open the javascript console and see if there was an error of some kind. >>> >>> Also we just released a new version (0.0.3) that that fixes some bugs you could also try to update to that version by removing and adding the plugin in you cordova project. >>> >>> Hope this helps, >>> Erik Jan >>> >>> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >>> >>>> I have this problem now: in iPhone (the same code works just fine with Android) the event handler never triggers the alert message. >>>> >>>> If the app is running in the background I get the message in the status bar, the badge shows, but when I touch on it or if the app is in the foreground the alert box inside the app never shows. >>>> >>>> As I told you, the same code works just fine in Android. >>>> >>>> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app is running in the background, when the push notification arrives it says a foreground message has arrived... >>>> >>>> Thanks >>>> >>>> M >>>> >>>> Enviado do meu iPhone >>>> >>>> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf escreveu: >>>> >>>>> Just saw the rest of the thread :-) >>>>> >>>>> Glad it works! >>>>> >>>>> -Matthias >>>>> >>>>> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >>>>> Does the app-id (bundle identifier) match the one which you created the SSL certificate for? >>>>> >>>>> Otherwise it is not valid to Apple >>>>> >>>>> -Matthias >>>>> >>>>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>>>> Hi all! >>>>> >>>>> As you know I managed - with a little help from my friends ;-) -to have the push notifications working on Android. But with iOS, not the same luck so far. What I've done: >>>>> >>>>> a) I created my development profile at Apple; >>>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>>> c) I installed the devprof profile (the mobile provision file) in Xcode (which says it's valid); >>>>> d) I inserted the variant ID and Secret on my phone code, like this (keys are not real): >>>>> >>>>> if(device.platform=='iOS'){ >>>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>>> } else if (device.platform=='Android'){ >>>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>>> } >>>>> >>>>> var pushConfig = { >>>>> senderID: "278695547260", // not relevant for Android anyway >>>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>>> variantID: varID, >>>>> variantSecret: varSec, >>>>> alias: userid >>>>> } >>>>> >>>>> But nevertheless I can't register the device. I get this error: >>>>> >>>>> no valid aps-environment (the message is not in English, so I translate it freely:"It was not found a valid aps-environment for the app") >>>>> >>>>> What can be wrong? >>>>> >>>>> Thanks >>>>> >>>>> Miguel >>>>> >>>>> >>>>> -- >>>>> Sent from Gmail Mobile >>>>> >>>>> >>>>> -- >>>>> Sent from Gmail Mobile >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140317/4d14b496/attachment-0001.html From scm.blanc at gmail.com Mon Mar 17 10:44:23 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 17 Mar 2014 15:44:23 +0100 Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: <1395062363438-6854.post@n5.nabble.com> References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> <1395060717930-6851.post@n5.nabble.com> <1395062363438-6854.post@n5.nabble.com> Message-ID: On Mon, Mar 17, 2014 at 2:19 PM, oxsav wrote: > Hmm did it. And the problem persists. > > I analysed the log from the jboss and when I try to open the URL: > http://150.140.184.246:4441/unifiedpush-server-0.10.0 , returns me the > following error: > > /*5:07:49,969 ERROR [org.jboss.as.ejb3.invocation] (default task-1) > JBAS014134: EJB Invocation failed on component Ping for method public > javax.ws.rs.core.Response > org.jboss.aerogear.unifiedpush.rest.util.Ping.ping(): > javax.ejb.EJBException: > org.jboss.aerogear.security.exception.AeroGearSecurityException: Not > authorized!*/ > The first "Ping" Rest call will always return this, the admin client uses this to check if you are connected or not. So, having this log (probably at the beginning) make sense. > > The weird thing is, I can access that well and create my application, my > variant and I already have an device registered to a variant :S .. > Any idea? > Again, sorry again for asking stupid questions but you are sure to not have left the "{" and "}" around the PushId and the masterID, check this valid example : https://github.com/sebastienblanc/chuckpush/blob/master/CURL.txt > > Tks, > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6854.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/8811ad96/attachment.html From matzew at apache.org Mon Mar 17 10:51:54 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 17 Mar 2014 15:51:54 +0100 Subject: [aerogear-dev] Releasing test artifacts in org.aerogear.arquillian groupId In-Reply-To: References: <20140314215310.2af4b7e5@kapy-ntb-x220> Message-ID: JIRA for the subject https://issues.jboss.org/browse/AEROGEAR-1457 On Sat, Mar 15, 2014 at 7:08 AM, Matthias Wessendorf wrote: > > > On Friday, March 14, 2014, Karel Piwko wrote: > >> Greetings, >> >> we have a bunch of Arquillian extensions to help test Aerogear spread >> across >> Aerogear test repos, for instance: >> >> * smart url - allows tests to switch in between http and https URLs for >> deployment >> * rules - allows test to defines sample data for UPS via JUnit @Rule >> * openshift-non-deploying-container - allows test to pretend Arquillian >> done >> some deployment to OpenShift cartridge >> >> It would be handy for us to release these extensions to Maven Central so >> we >> don't have to compile them prior running tests and also reuse them across >> tests. >> >> I was thinking about moving them into single repository in aerogear GH >> and releasing them in org.aerogear.arquillian groupId. >> >> Thoughts? > > > Sure, why not? > > >> >> Thanks, >> >> Karel >> _______________________________________________ >> 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/20140317/f3984974/attachment.html From vmfamaral at gmail.com Mon Mar 17 11:19:11 2014 From: vmfamaral at gmail.com (oxsav) Date: Mon, 17 Mar 2014 08:19:11 -0700 (PDT) Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> <1395060717930-6851.post@n5.nabble.com> <1395062363438-6854.post@n5.nabble.com> Message-ID: <1395069551329-6860.post@n5.nabble.com> Is not a stupid question. Maybe I'm a stupid guy :p Yep the problem was the {}. Thanks for all :) -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6860.html Sent from the aerogear-dev mailing list archive at Nabble.com. From scm.blanc at gmail.com Mon Mar 17 11:30:12 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 17 Mar 2014 16:30:12 +0100 Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: <1395069551329-6860.post@n5.nabble.com> References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> <1395060717930-6851.post@n5.nabble.com> <1395062363438-6854.post@n5.nabble.com> <1395069551329-6860.post@n5.nabble.com> Message-ID: On Mon, Mar 17, 2014 at 4:19 PM, oxsav wrote: > Is not a stupid question. Maybe I'm a stupid guy :p > > Yep the problem was the {}. > > Thanks for all :) > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6860.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/8991aee0/attachment.html From scm.blanc at gmail.com Mon Mar 17 11:31:32 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 17 Mar 2014 16:31:32 +0100 Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: <1395069551329-6860.post@n5.nabble.com> References: <1395056711933-6841.post@n5.nabble.com> <9529A8FA-57E0-416E-BA1C-EA0769484F28@gmail.com> <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> <1395060717930-6851.post@n5.nabble.com> <1395062363438-6854.post@n5.nabble.com> <1395069551329-6860.post@n5.nabble.com> Message-ID: On Mon, Mar 17, 2014 at 4:19 PM, oxsav wrote: > Is not a stupid question. Maybe I'm a stupid guy :p > Not at all :) you are not the first one hit by this, we should change the doc / samples to make it more obivous ! > > Yep the problem was the {}. > > Thanks for all :) > You're welcome, thanks again for you interest in the project. > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6860.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/0194951d/attachment.html From vmfamaral at gmail.com Mon Mar 17 11:36:32 2014 From: vmfamaral at gmail.com (oxsav) Date: Mon, 17 Mar 2014 08:36:32 -0700 (PDT) Subject: [aerogear-dev] Problem with Push notification chrome-app In-Reply-To: References: <1395057433543-6843.post@n5.nabble.com> <1395059330201-6845.post@n5.nabble.com> <1395060717930-6851.post@n5.nabble.com> <1395062363438-6854.post@n5.nabble.com> <1395069551329-6860.post@n5.nabble.com> Message-ID: <1395070592072-6863.post@n5.nabble.com> Yep, but if I saw the curl 's "man page", maybe I could have seen this problem earlier. Because there we can find -u, --user . ;) tks -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problem-with-Push-notification-chrome-app-tp6817p6863.html Sent from the aerogear-dev mailing list archive at Nabble.com. From kpiwko at redhat.com Mon Mar 17 13:10:03 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Mon, 17 Mar 2014 18:10:03 +0100 Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results Message-ID: <20140317181003.2e9b63c7@kapy-ntb-x220> Hey, status looks like: * Integration tests - passed * UI tests - failed - UI glitches in FF * SP tests - passed * Migration tests - failed - scheme problems. Migration is not a part of cartridge but I guess that UI should be fixed. I have filled following bugs: * https://issues.jboss.org/browse/AGPUSH-562 * https://issues.jboss.org/browse/AGPUSH-563 Note, as for Firefox DNS cache, just set network.dnsCacheExpirationGracePeriod=0 in about:config. Karel From matzew at apache.org Mon Mar 17 13:14:05 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 17 Mar 2014 18:14:05 +0100 Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: <20140317181003.2e9b63c7@kapy-ntb-x220> References: <20140317181003.2e9b63c7@kapy-ntb-x220> Message-ID: On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko wrote: > Hey, > > status looks like: > > * Integration tests - passed > * UI tests - failed - UI glitches in FF > known problem; not sure - but there might be already a ticket for it > * SP tests - passed > * Migration tests - failed - scheme problems. > possible - we might have changed the data model between 0.9.x and 0.10.x > > Migration is not a part of cartridge but I guess that UI should be fixed. > It's minor, not sure we should really stop the process; especially the UPS is now on staging/hold since one entire week > > I have filled following bugs: > * https://issues.jboss.org/browse/AGPUSH-562 > * https://issues.jboss.org/browse/AGPUSH-563 > > Note, as for Firefox DNS cache, just set > network.dnsCacheExpirationGracePeriod=0 in about:config. > > Karel > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140317/2c65ae5a/attachment-0001.html From fjuma at redhat.com Mon Mar 17 14:27:42 2014 From: fjuma at redhat.com (Farah Juma) Date: Mon, 17 Mar 2014 14:27:42 -0400 (EDT) Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: References: <20140317181003.2e9b63c7@kapy-ntb-x220> Message-ID: <1870763722.1787721.1395080862802.JavaMail.zimbra@redhat.com> > From: "Matthias Wessendorf" > To: "AeroGear Developer Mailing List" > Cc: "Farah Juma" > Sent: Monday, March 17, 2014 1:14:05 PM > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko wrote: > > > Hey, > > > > status looks like: > > > > * Integration tests - passed > > * UI tests - failed - UI glitches in FF > > > > known problem; not sure - but there might be already a ticket for it > > > > * SP tests - passed > > * Migration tests - failed - scheme problems. > > > > possible - we might have changed the data model between 0.9.x and 0.10.x Interesting, this would cause issues with modifying existing data/adding new data. As Karel noted on AGPUSH-563, it looks like we would need a migration strategy for DB schema changes. Farah > > > > Migration is not a part of cartridge but I guess that UI should be fixed. > > > > It's minor, not sure we should really stop the process; especially the UPS > is now on staging/hold since one entire week > > > > > > I have filled following bugs: > > * https://issues.jboss.org/browse/AGPUSH-562 > > * https://issues.jboss.org/browse/AGPUSH-563 > > > > Note, as for Firefox DNS cache, just set > > network.dnsCacheExpirationGracePeriod=0 in about:config. > > > > Karel > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > From matzew at apache.org Mon Mar 17 14:55:01 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 17 Mar 2014 19:55:01 +0100 Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: <1870763722.1787721.1395080862802.JavaMail.zimbra@redhat.com> References: <20140317181003.2e9b63c7@kapy-ntb-x220> <1870763722.1787721.1395080862802.JavaMail.zimbra@redhat.com> Message-ID: On Mon, Mar 17, 2014 at 7:27 PM, Farah Juma wrote: > > > From: "Matthias Wessendorf" > > To: "AeroGear Developer Mailing List" > > Cc: "Farah Juma" > > Sent: Monday, March 17, 2014 1:14:05 PM > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko wrote: > > > > > Hey, > > > > > > status looks like: > > > > > > * Integration tests - passed > > > * UI tests - failed - UI glitches in FF > > > > > > > known problem; not sure - but there might be already a ticket for it > > > > > > > * SP tests - passed > > > * Migration tests - failed - scheme problems. > > > > > > > possible - we might have changed the data model between 0.9.x and 0.10.x > > Interesting, this would cause issues with modifying existing data/adding > new data. As Karel noted on AGPUSH-563, it looks like we would need a > migration strategy for DB schema changes. > yep - I was thought that's part of the upgrade work; but we can file a ticket to explicitly cover this > > Farah > > > > > > > Migration is not a part of cartridge but I guess that UI should be > fixed. > > > > > > > It's minor, not sure we should really stop the process; especially the > UPS > > is now on staging/hold since one entire week > > > > > > > > > > I have filled following bugs: > > > * https://issues.jboss.org/browse/AGPUSH-562 > > > * https://issues.jboss.org/browse/AGPUSH-563 > > > > > > Note, as for Firefox DNS cache, just set > > > network.dnsCacheExpirationGracePeriod=0 in about:config. > > > > > > Karel > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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/20140317/429c0548/attachment.html From fjuma at redhat.com Mon Mar 17 15:56:14 2014 From: fjuma at redhat.com (Farah Juma) Date: Mon, 17 Mar 2014 15:56:14 -0400 (EDT) Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: References: <20140317181003.2e9b63c7@kapy-ntb-x220> <1870763722.1787721.1395080862802.JavaMail.zimbra@redhat.com> Message-ID: <1382681329.1846389.1395086174731.JavaMail.zimbra@redhat.com> > From: "Matthias Wessendorf" > To: "Farah Juma" > Cc: "AeroGear Developer Mailing List" > Sent: Monday, March 17, 2014 2:55:01 PM > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > On Mon, Mar 17, 2014 at 7:27 PM, Farah Juma wrote: > > > > > > From: "Matthias Wessendorf" > > > To: "AeroGear Developer Mailing List" > > > Cc: "Farah Juma" > > > Sent: Monday, March 17, 2014 1:14:05 PM > > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > > > > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko wrote: > > > > > > > Hey, > > > > > > > > status looks like: > > > > > > > > * Integration tests - passed > > > > * UI tests - failed - UI glitches in FF > > > > > > > > > > known problem; not sure - but there might be already a ticket for it > > > > > > > > > > * SP tests - passed > > > > * Migration tests - failed - scheme problems. > > > > > > > > > > possible - we might have changed the data model between 0.9.x and 0.10.x > > > > Interesting, this would cause issues with modifying existing data/adding > > new data. As Karel noted on AGPUSH-563, it looks like we would need a > > migration strategy for DB schema changes. > > > > yep - I was thought that's part of the upgrade work; but we can file a > ticket to explicitly cover this That would be good. The database part of the upgrade is currently handled by the MySQL cartridge's "post_restore" action hook - this just restores the database to whatever it was before and doesn't handle schema changes: https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-mysql/bin/control#L140 Once the necessary MySQL commands for migrating data from 0.9.x to 0.10.x are defined, we could try adding them to the AeroGear cartridge's "post_restore" action hook. > > > > > > > > > > Migration is not a part of cartridge but I guess that UI should be > > fixed. > > > > > > > > > > It's minor, not sure we should really stop the process; especially the > > UPS > > > is now on staging/hold since one entire week > > > > > > > > > > > > > > I have filled following bugs: > > > > * https://issues.jboss.org/browse/AGPUSH-562 > > > > * https://issues.jboss.org/browse/AGPUSH-563 > > > > > > > > Note, as for Firefox DNS cache, just set > > > > network.dnsCacheExpirationGracePeriod=0 in about:config. > > > > > > > > Karel > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.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 > From tolisemm at gmail.com Mon Mar 17 15:59:22 2014 From: tolisemm at gmail.com (tolis emmanouilidis) Date: Mon, 17 Mar 2014 21:59:22 +0200 Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: References: <1394247994174.a05c8174@Nodemailer> <1389062401.8617179.1394463229081.JavaMail.zimbra@redhat.com> Message-ID: To follow up, the JIRA id is AGPUSH-559 and I've sent a PR for supporting custom truststores [1]. The integration tests using SSL and the custom aerogear.truststore passed. [1]: https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/36 Thanks, Tolis 2014-03-10 20:50 GMT+02:00 Matthias Wessendorf : > > > On Monday, March 10, 2014, Bruno Oliveira wrote: > >> JIRA is enough as far as I can tell. > > > +1 on JIRA for tracking > > feel free to send PR as well > > Greetings, > Matthias > > >> >> -- >> abstractj >> >> On March 10, 2014 at 11:53:53 AM, Stefan Miklosovic (smikloso at redhat.com) >> wrote: >> > > Hi, >> > >> > so whats the "conclusion" for this? I would like to move forward >> > with other things. Is JIRA to track this sufficient? >> > >> > Stefan Miklosovic >> > Red Hat Brno - JBoss Mobile Platform >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/7d42ddd9/attachment.html From daniel at passos.me Mon Mar 17 17:11:53 2014 From: daniel at passos.me (Daniel Passos) Date: Mon, 17 Mar 2014 18:11:53 -0300 Subject: [aerogear-dev] SQLite Store Order By and Auto Increment ID In-Reply-To: References: Message-ID: Hi Thiago, Nice questions. Answers inline. On Sun, Mar 16, 2014 at 6:20 PM, Tiago Resende wrote: > Hi guys, thanks for the other day, you really helped me. > > I have two questions today. > > How can I perform a query using "order by" statement in SQLStore? > > I did a readAll, then I ordered in memory using Ordering. > Unfortunately. We don't have this option for now. > The second question is how can I indicate to AeroGear that it should use > an auto increment primary key for a table. I created an AutoGeneratorId > Class, but it's not working beautifully for SQLStore. I had to create an > update method and call it for every object, I didn't like it, but I > couldn't find a better solution reading the documentation. > No, who creates the id is always idGenerator. What's the problem? > I really appreciate your help. > > Thanks. > > -- > *Tiago de Carvalho Resende* > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/0c8aef32/attachment.html From tiagor87 at gmail.com Mon Mar 17 17:45:30 2014 From: tiagor87 at gmail.com (Tiago Resende) Date: Mon, 17 Mar 2014 18:45:30 -0300 Subject: [aerogear-dev] SQLite Store Order By and Auto Increment ID In-Reply-To: References: Message-ID: The AeroGear isn't reading the last Id saved in database, so, it starts over and over again, overwriting my old data every time a open my application. 2014-03-17 18:11 GMT-03:00 Daniel Passos : > Hi Thiago, > > Nice questions. Answers inline. > > On Sun, Mar 16, 2014 at 6:20 PM, Tiago Resende wrote: > >> Hi guys, thanks for the other day, you really helped me. >> >> I have two questions today. >> >> How can I perform a query using "order by" statement in SQLStore? >> >> I did a readAll, then I ordered in memory using Ordering. >> > > Unfortunately. We don't have this option for now. > > >> The second question is how can I indicate to AeroGear that it should use >> an auto increment primary key for a table. I created an AutoGeneratorId >> Class, but it's not working beautifully for SQLStore. I had to create an >> update method and call it for every object, I didn't like it, but I >> couldn't find a better solution reading the documentation. >> > > No, who creates the id is always idGenerator. What's the problem? > > >> I really appreciate your help. >> >> Thanks. >> >> -- >> *Tiago de Carvalho Resende* >> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- *Tiago de Carvalho Resende* Desenvolvedor "O importante n?o ? saber fazer, ? saber de onde copiar." por Bernardo Esb?rard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/1496f95a/attachment-0001.html From tiagor87 at gmail.com Mon Mar 17 17:54:20 2014 From: tiagor87 at gmail.com (Tiago Resende) Date: Mon, 17 Mar 2014 18:54:20 -0300 Subject: [aerogear-dev] SQLite Store Order By and Auto Increment ID In-Reply-To: References: Message-ID: The "order by" problem I solved implementing an extension for AG Store. 2014-03-17 18:45 GMT-03:00 Tiago Resende : > The AeroGear isn't reading the last Id saved in database, so, it starts > over and over again, overwriting my old data every time a open my > application. > > > 2014-03-17 18:11 GMT-03:00 Daniel Passos : > >> Hi Thiago, >> >> Nice questions. Answers inline. >> >> On Sun, Mar 16, 2014 at 6:20 PM, Tiago Resende wrote: >> >>> Hi guys, thanks for the other day, you really helped me. >>> >>> I have two questions today. >>> >>> How can I perform a query using "order by" statement in SQLStore? >>> >>> I did a readAll, then I ordered in memory using Ordering. >>> >> >> Unfortunately. We don't have this option for now. >> >> >>> The second question is how can I indicate to AeroGear that it should use >>> an auto increment primary key for a table. I created an AutoGeneratorId >>> Class, but it's not working beautifully for SQLStore. I had to create an >>> update method and call it for every object, I didn't like it, but I >>> couldn't find a better solution reading the documentation. >>> >> >> No, who creates the id is always idGenerator. What's the problem? >> >> >>> I really appreciate your help. >>> >>> Thanks. >>> >>> -- >>> *Tiago de Carvalho Resende* >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > *Tiago de Carvalho Resende* > Desenvolvedor > > "O importante n?o ? saber fazer, > > ? saber de onde copiar." > > por Bernardo Esb?rard > > > -- *Tiago de Carvalho Resende* Desenvolvedor "O importante n?o ? saber fazer, ? saber de onde copiar." por Bernardo Esb?rard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/2b0875c5/attachment.html From tiagor87 at gmail.com Mon Mar 17 18:44:48 2014 From: tiagor87 at gmail.com (Tiago Resende) Date: Mon, 17 Mar 2014 19:44:48 -0300 Subject: [aerogear-dev] SQLite Store Order By and Auto Increment ID In-Reply-To: References: Message-ID: It's not as much beautiful as I liked, but it works. Is there anyway to use AG implementation to read the cursor with all fields and retrieve the object? I've used "read" to do the magic, but I didn't like it. public Collection readSorted(EnumSort enumSort) { String tableName = getTableName(); String fieldName = getIdFieldName(); String sql = "SELECT %s FROM %s ORDER BY %s %s"; if (enumSort == EnumSort.ASCENDING) { sql = String.format(sql, fieldName, tableName, fieldName, "ASC"); } else { sql = String.format(sql, fieldName, tableName, fieldName, "DESC"); } Collection collection = new ArrayList(); SQLiteDatabase database = this.getReadableDatabase(); Cursor cursor = database.rawQuery(sql, new String[]{}); for (cursor.moveToFirst(); !cursor.isAfterLast(); cursor.moveToNext()) { collection.add(this.read(cursor.getInt(0))); } return collection; } 2014-03-17 18:54 GMT-03:00 Tiago Resende : > The "order by" problem I solved implementing an extension for AG Store. > > > > > > > 2014-03-17 18:45 GMT-03:00 Tiago Resende : > > The AeroGear isn't reading the last Id saved in database, so, it starts >> over and over again, overwriting my old data every time a open my >> application. >> >> >> 2014-03-17 18:11 GMT-03:00 Daniel Passos : >> >>> Hi Thiago, >>> >>> Nice questions. Answers inline. >>> >>> On Sun, Mar 16, 2014 at 6:20 PM, Tiago Resende wrote: >>> >>>> Hi guys, thanks for the other day, you really helped me. >>>> >>>> I have two questions today. >>>> >>>> How can I perform a query using "order by" statement in SQLStore? >>>> >>>> I did a readAll, then I ordered in memory using Ordering. >>>> >>> >>> Unfortunately. We don't have this option for now. >>> >>> >>>> The second question is how can I indicate to AeroGear that it should >>>> use an auto increment primary key for a table. I created an AutoGeneratorId >>>> Class, but it's not working beautifully for SQLStore. I had to create an >>>> update method and call it for every object, I didn't like it, but I >>>> couldn't find a better solution reading the documentation. >>>> >>> >>> No, who creates the id is always idGenerator. What's the problem? >>> >>> >>>> I really appreciate your help. >>>> >>>> Thanks. >>>> >>>> -- >>>> *Tiago de Carvalho Resende* >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> *Tiago de Carvalho Resende* >> Desenvolvedor >> >> "O importante n?o ? saber fazer, >> >> ? saber de onde copiar." >> >> por Bernardo Esb?rard >> >> >> > > > > -- > *Tiago de Carvalho Resende* > Desenvolvedor > > "O importante n?o ? saber fazer, > > ? saber de onde copiar." > > por Bernardo Esb?rard > > > -- *Tiago de Carvalho Resende* Desenvolvedor "O importante n?o ? saber fazer, ? saber de onde copiar." por Bernardo Esb?rard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/d16e016d/attachment.html From tiagor87 at gmail.com Mon Mar 17 21:07:11 2014 From: tiagor87 at gmail.com (Tiago Resende) Date: Mon, 17 Mar 2014 22:07:11 -0300 Subject: [aerogear-dev] SQLite Store Order By and Auto Increment ID In-Reply-To: References: Message-ID: I had to change the code I sent above, It only works without AG, I've tested in another project. ='( The AG table structure is much different that I thought. We have just one table mapping all database, right? 2014-03-17 19:44 GMT-03:00 Tiago Resende : > It's not as much beautiful as I liked, but it works. > > Is there anyway to use AG implementation to read the cursor with all > fields and retrieve the object? I've used "read" to do the magic, but I > didn't like it. > > public Collection readSorted(EnumSort enumSort) { > String tableName = getTableName(); > String fieldName = getIdFieldName(); > > String sql = "SELECT %s FROM %s ORDER BY %s %s"; > if (enumSort == EnumSort.ASCENDING) { > sql = String.format(sql, fieldName, tableName, fieldName, > "ASC"); > } else { > sql = String.format(sql, fieldName, tableName, fieldName, > "DESC"); > } > > Collection collection = new ArrayList(); > > SQLiteDatabase database = this.getReadableDatabase(); > Cursor cursor = database.rawQuery(sql, new String[]{}); > for (cursor.moveToFirst(); !cursor.isAfterLast(); > cursor.moveToNext()) { > collection.add(this.read(cursor.getInt(0))); > } > > return collection; > } > > > 2014-03-17 18:54 GMT-03:00 Tiago Resende : > > The "order by" problem I solved implementing an extension for AG Store. >> >> >> >> >> >> >> 2014-03-17 18:45 GMT-03:00 Tiago Resende : >> >> The AeroGear isn't reading the last Id saved in database, so, it starts >>> over and over again, overwriting my old data every time a open my >>> application. >>> >>> >>> 2014-03-17 18:11 GMT-03:00 Daniel Passos : >>> >>>> Hi Thiago, >>>> >>>> Nice questions. Answers inline. >>>> >>>> On Sun, Mar 16, 2014 at 6:20 PM, Tiago Resende wrote: >>>> >>>>> Hi guys, thanks for the other day, you really helped me. >>>>> >>>>> I have two questions today. >>>>> >>>>> How can I perform a query using "order by" statement in SQLStore? >>>>> >>>>> I did a readAll, then I ordered in memory using Ordering. >>>>> >>>> >>>> Unfortunately. We don't have this option for now. >>>> >>>> >>>>> The second question is how can I indicate to AeroGear that it should >>>>> use an auto increment primary key for a table. I created an AutoGeneratorId >>>>> Class, but it's not working beautifully for SQLStore. I had to create an >>>>> update method and call it for every object, I didn't like it, but I >>>>> couldn't find a better solution reading the documentation. >>>>> >>>> >>>> No, who creates the id is always idGenerator. What's the problem? >>>> >>>> >>>>> I really appreciate your help. >>>>> >>>>> Thanks. >>>>> >>>>> -- >>>>> *Tiago de Carvalho Resende* >>>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> *Tiago de Carvalho Resende* >>> Desenvolvedor >>> >>> "O importante n?o ? saber fazer, >>> >>> ? saber de onde copiar." >>> >>> por Bernardo Esb?rard >>> >>> >>> >> >> >> >> -- >> *Tiago de Carvalho Resende* >> Desenvolvedor >> >> "O importante n?o ? saber fazer, >> >> ? saber de onde copiar." >> >> por Bernardo Esb?rard >> >> >> > > > > -- > *Tiago de Carvalho Resende* > Desenvolvedor > > "O importante n?o ? saber fazer, > > ? saber de onde copiar." > > por Bernardo Esb?rard > > > -- *Tiago de Carvalho Resende* Desenvolvedor "O importante n?o ? saber fazer, ? saber de onde copiar." por Bernardo Esb?rard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/e2fee7b0/attachment-0001.html From matzew at apache.org Tue Mar 18 01:47:06 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 06:47:06 +0100 Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: <1382681329.1846389.1395086174731.JavaMail.zimbra@redhat.com> References: <20140317181003.2e9b63c7@kapy-ntb-x220> <1870763722.1787721.1395080862802.JavaMail.zimbra@redhat.com> <1382681329.1846389.1395086174731.JavaMail.zimbra@redhat.com> Message-ID: On Mon, Mar 17, 2014 at 8:56 PM, Farah Juma wrote: > > > From: "Matthias Wessendorf" > > To: "Farah Juma" > > Cc: "AeroGear Developer Mailing List" > > Sent: Monday, March 17, 2014 2:55:01 PM > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > > > On Mon, Mar 17, 2014 at 7:27 PM, Farah Juma wrote: > > > > > > > > > From: "Matthias Wessendorf" > > > > To: "AeroGear Developer Mailing List" > > > > Cc: "Farah Juma" > > > > Sent: Monday, March 17, 2014 1:14:05 PM > > > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test > results > > > > > > > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko > wrote: > > > > > > > > > Hey, > > > > > > > > > > status looks like: > > > > > > > > > > * Integration tests - passed > > > > > * UI tests - failed - UI glitches in FF > > > > > > > > > > > > > known problem; not sure - but there might be already a ticket for it > > > > > > > > > > > > > * SP tests - passed > > > > > * Migration tests - failed - scheme problems. > > > > > > > > > > > > > possible - we might have changed the data model between 0.9.x and > 0.10.x > > > > > > Interesting, this would cause issues with modifying existing > data/adding > > > new data. As Karel noted on AGPUSH-563, it looks like we would need a > > > migration strategy for DB schema changes. > > > > > > > yep - I was thought that's part of the upgrade work; but we can file a > > ticket to explicitly cover this > > That would be good. The database part of the upgrade is currently handled > by the MySQL cartridge's "post_restore" action hook - this just restores > the database to whatever it was before and doesn't handle schema changes: > > > https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-mysql/bin/control#L140 ok > > > Once the necessary MySQL commands for migrating data from 0.9.x to 0.10.x > are defined, we could try adding them to the AeroGear cartridge's > "post_restore" action hook. > With "necessary MySQL commands" you mean those that take care of the schema changes? I think generally having a migration script for the schema is a nice thing to have, regardless of OpenShift. Once we are closer to our 1.0.0 that's something we have to have. Are you planing on adding these necessary MySQL commands (assuming they are relevant for taking care of schema changes ;-)) for our cartridge? Or should we just track that requirement in a JIRA for now ? -Matthias > > > > > > > > > > > > > > Migration is not a part of cartridge but I guess that UI should be > > > fixed. > > > > > > > > > > > > > It's minor, not sure we should really stop the process; especially > the > > > UPS > > > > is now on staging/hold since one entire week > > > > > > > > > > > > > > > > > > I have filled following bugs: > > > > > * https://issues.jboss.org/browse/AGPUSH-562 > > > > > * https://issues.jboss.org/browse/AGPUSH-563 > > > > > > > > > > Note, as for Firefox DNS cache, just set > > > > > network.dnsCacheExpirationGracePeriod=0 in about:config. > > > > > > > > > > Karel > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev at lists.jboss.org > > > > > https://lists.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 > > > -- 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/20140318/256c6b1e/attachment.html From corinnekrych at gmail.com Tue Mar 18 03:37:03 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 18 Mar 2014 08:37:03 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 Message-ID: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> Hello iOS Friends, AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). To test it, open Podfile and point to the latest git branch pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' Help us make this release a success, give it a trial, and let us know how it goes for your project. ++ Corinne From corinnekrych at gmail.com Tue Mar 18 03:57:47 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 18 Mar 2014 08:57:47 +0100 Subject: [aerogear-dev] Team meeting agenda In-Reply-To: References: Message-ID: Minutes can be found here: Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-17-13.47.html jbott Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-17-13.47.txt jbott Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-17-13.47.log.html On 16 Mar 2014, at 19:57, Daniel Bevenius wrote: > http://oksoclap.com/p/aerogear-team-mgt-20140317 > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From kpiwko at redhat.com Tue Mar 18 04:17:13 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Tue, 18 Mar 2014 09:17:13 +0100 Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: References: <20140317181003.2e9b63c7@kapy-ntb-x220> Message-ID: <20140318091713.012e7f05@kapy-ntb-x220> On Mon, 17 Mar 2014 18:14:05 +0100 Matthias Wessendorf wrote: > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko wrote: > > > Hey, > > > > status looks like: > > > > * Integration tests - passed > > * UI tests - failed - UI glitches in FF > > > > known problem; not sure - but there might be already a ticket for it > > > > * SP tests - passed > > * Migration tests - failed - scheme problems. > > > > possible - we might have changed the data model between 0.9.x and 0.10.x > > > > > > Migration is not a part of cartridge but I guess that UI should be fixed. > > > > It's minor, not sure we should really stop the process; especially the UPS > is now on staging/hold since one entire week It's up to you. I believe that 0.10.1 has many improvements and if really needed 0.10.2 with fixed UI can follow. > > > > > > I have filled following bugs: > > * https://issues.jboss.org/browse/AGPUSH-562 > > * https://issues.jboss.org/browse/AGPUSH-563 > > > > Note, as for Firefox DNS cache, just set > > network.dnsCacheExpirationGracePeriod=0 in about:config. > > > > Karel > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > From scm.blanc at gmail.com Tue Mar 18 04:23:50 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 18 Mar 2014 09:23:50 +0100 Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: <20140318091713.012e7f05@kapy-ntb-x220> References: <20140317181003.2e9b63c7@kapy-ntb-x220> <20140318091713.012e7f05@kapy-ntb-x220> Message-ID: Yes, let's move on with 0.10.1 and if really needed, we can indeed do later 0.10.2 with UI fixes. Release the kraken ! On Tue, Mar 18, 2014 at 9:17 AM, Karel Piwko wrote: > On Mon, 17 Mar 2014 18:14:05 +0100 > Matthias Wessendorf wrote: > > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko wrote: > > > > > Hey, > > > > > > status looks like: > > > > > > * Integration tests - passed > > > * UI tests - failed - UI glitches in FF > > > > > > > known problem; not sure - but there might be already a ticket for it > > > > > > > * SP tests - passed > > > * Migration tests - failed - scheme problems. > > > > > > > possible - we might have changed the data model between 0.9.x and 0.10.x > > > > > > > > > > Migration is not a part of cartridge but I guess that UI should be > fixed. > > > > > > > It's minor, not sure we should really stop the process; especially the > UPS > > is now on staging/hold since one entire week > > It's up to you. I believe that 0.10.1 has many improvements and if really > needed 0.10.2 with fixed UI can follow. > > > > > > > > > > > I have filled following bugs: > > > * https://issues.jboss.org/browse/AGPUSH-562 > > > * https://issues.jboss.org/browse/AGPUSH-563 > > > > > > Note, as for Firefox DNS cache, just set > > > network.dnsCacheExpirationGracePeriod=0 in about:config. > > > > > > Karel > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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/20140318/93b08ffa/attachment.html From kpiwko at redhat.com Tue Mar 18 04:26:56 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Tue, 18 Mar 2014 09:26:56 +0100 Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: References: <1394247994174.a05c8174@Nodemailer> <1389062401.8617179.1394463229081.JavaMail.zimbra@redhat.com> Message-ID: <20140318092656.656bfef5@kapy-ntb-x220> Thanks Tolis, it looks good! We'd just need an additional test to verify previous behavior is still valid, e.g. connection test was rewritten, it should have been added next to http. Many thanks! Karel On Mon, 17 Mar 2014 21:59:22 +0200 tolis emmanouilidis wrote: > To follow up, the JIRA id is AGPUSH-559 and I've sent a PR for supporting > custom truststores [1]. The integration tests using SSL and the custom > aerogear.truststore passed. > > [1]: https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/36 > > Thanks, > Tolis > > > 2014-03-10 20:50 GMT+02:00 Matthias Wessendorf : > > > > > > > On Monday, March 10, 2014, Bruno Oliveira wrote: > > > >> JIRA is enough as far as I can tell. > > > > > > +1 on JIRA for tracking > > > > feel free to send PR as well > > > > Greetings, > > Matthias > > > > > >> > >> -- > >> abstractj > >> > >> On March 10, 2014 at 11:53:53 AM, Stefan Miklosovic (smikloso at redhat.com) > >> wrote: > >> > > Hi, > >> > > >> > so whats the "conclusion" for this? I would like to move forward > >> > with other things. Is JIRA to track this sufficient? > >> > > >> > Stefan Miklosovic > >> > Red Hat Brno - JBoss Mobile Platform > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > > > > > > -- > > Sent from Gmail Mobile > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > From matzew at apache.org Tue Mar 18 04:27:44 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 09:27:44 +0100 Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: References: <20140317181003.2e9b63c7@kapy-ntb-x220> <20140318091713.012e7f05@kapy-ntb-x220> Message-ID: On Tue, Mar 18, 2014 at 9:23 AM, Sebastien Blanc wrote: > Yes, let's move on with 0.10.1 and if really needed, we can indeed do > later 0.10.2 with UI fixes. > Release the kraken ! > +1 > > > > On Tue, Mar 18, 2014 at 9:17 AM, Karel Piwko wrote: > >> On Mon, 17 Mar 2014 18:14:05 +0100 >> Matthias Wessendorf wrote: >> >> > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko wrote: >> > >> > > Hey, >> > > >> > > status looks like: >> > > >> > > * Integration tests - passed >> > > * UI tests - failed - UI glitches in FF >> > > >> > >> > known problem; not sure - but there might be already a ticket for it >> > >> > >> > > * SP tests - passed >> > > * Migration tests - failed - scheme problems. >> > > >> > >> > possible - we might have changed the data model between 0.9.x and 0.10.x >> > >> > >> > > >> > > Migration is not a part of cartridge but I guess that UI should be >> fixed. >> > > >> > >> > It's minor, not sure we should really stop the process; especially the >> UPS >> > is now on staging/hold since one entire week >> >> It's up to you. I believe that 0.10.1 has many improvements and if really >> needed 0.10.2 with fixed UI can follow. >> >> > >> > >> > > >> > > I have filled following bugs: >> > > * https://issues.jboss.org/browse/AGPUSH-562 >> > > * https://issues.jboss.org/browse/AGPUSH-563 >> > > >> > > Note, as for Firefox DNS cache, just set >> > > network.dnsCacheExpirationGracePeriod=0 in about:config. >> > > >> > > Karel >> > > _______________________________________________ >> > > aerogear-dev mailing list >> > > aerogear-dev at lists.jboss.org >> > > https://lists.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/20140318/2a6fa4eb/attachment.html From daniel.bevenius at gmail.com Tue Mar 18 04:32:49 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Tue, 18 Mar 2014 09:32:49 +0100 Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: References: <20140317181003.2e9b63c7@kapy-ntb-x220> <20140318091713.012e7f05@kapy-ntb-x220> Message-ID: I've released AeroGear SimplePush Server 0.10.0 using Nexus, but it will take some time to get synced to Maven central. I'll post an announcement to the mailing list when the artifacts are available on Maven central. On 18 March 2014 09:27, Matthias Wessendorf wrote: > > > > On Tue, Mar 18, 2014 at 9:23 AM, Sebastien Blanc wrote: > >> Yes, let's move on with 0.10.1 and if really needed, we can indeed do >> later 0.10.2 with UI fixes. >> Release the kraken ! >> > > +1 > > >> >> >> >> On Tue, Mar 18, 2014 at 9:17 AM, Karel Piwko wrote: >> >>> On Mon, 17 Mar 2014 18:14:05 +0100 >>> Matthias Wessendorf wrote: >>> >>> > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko >>> wrote: >>> > >>> > > Hey, >>> > > >>> > > status looks like: >>> > > >>> > > * Integration tests - passed >>> > > * UI tests - failed - UI glitches in FF >>> > > >>> > >>> > known problem; not sure - but there might be already a ticket for it >>> > >>> > >>> > > * SP tests - passed >>> > > * Migration tests - failed - scheme problems. >>> > > >>> > >>> > possible - we might have changed the data model between 0.9.x and >>> 0.10.x >>> > >>> > >>> > > >>> > > Migration is not a part of cartridge but I guess that UI should be >>> fixed. >>> > > >>> > >>> > It's minor, not sure we should really stop the process; especially the >>> UPS >>> > is now on staging/hold since one entire week >>> >>> It's up to you. I believe that 0.10.1 has many improvements and if really >>> needed 0.10.2 with fixed UI can follow. >>> >>> > >>> > >>> > > >>> > > I have filled following bugs: >>> > > * https://issues.jboss.org/browse/AGPUSH-562 >>> > > * https://issues.jboss.org/browse/AGPUSH-563 >>> > > >>> > > Note, as for Firefox DNS cache, just set >>> > > network.dnsCacheExpirationGracePeriod=0 in about:config. >>> > > >>> > > Karel >>> > > _______________________________________________ >>> > > aerogear-dev mailing list >>> > > aerogear-dev at lists.jboss.org >>> > > https://lists.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/20140318/23b95fb8/attachment.html From matzew at apache.org Tue Mar 18 04:38:06 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 09:38:06 +0100 Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: References: <20140317181003.2e9b63c7@kapy-ntb-x220> <1870763722.1787721.1395080862802.JavaMail.zimbra@redhat.com> <1382681329.1846389.1395086174731.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Mar 18, 2014 at 6:47 AM, Matthias Wessendorf wrote: > > > > On Mon, Mar 17, 2014 at 8:56 PM, Farah Juma wrote: > >> >> > From: "Matthias Wessendorf" >> > To: "Farah Juma" >> > Cc: "AeroGear Developer Mailing List" >> > Sent: Monday, March 17, 2014 2:55:01 PM >> > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results >> > >> > On Mon, Mar 17, 2014 at 7:27 PM, Farah Juma wrote: >> > >> > > >> > > > From: "Matthias Wessendorf" >> > > > To: "AeroGear Developer Mailing List" > > >> > > > Cc: "Farah Juma" >> > > > Sent: Monday, March 17, 2014 1:14:05 PM >> > > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test >> results >> > > > >> > > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko >> wrote: >> > > > >> > > > > Hey, >> > > > > >> > > > > status looks like: >> > > > > >> > > > > * Integration tests - passed >> > > > > * UI tests - failed - UI glitches in FF >> > > > > >> > > > >> > > > known problem; not sure - but there might be already a ticket for it >> > > > >> > > > >> > > > > * SP tests - passed >> > > > > * Migration tests - failed - scheme problems. >> > > > > >> > > > >> > > > possible - we might have changed the data model between 0.9.x and >> 0.10.x >> > > >> > > Interesting, this would cause issues with modifying existing >> data/adding >> > > new data. As Karel noted on AGPUSH-563, it looks like we would need a >> > > migration strategy for DB schema changes. >> > > >> > >> > yep - I was thought that's part of the upgrade work; but we can file a >> > ticket to explicitly cover this >> >> That would be good. The database part of the upgrade is currently handled >> by the MySQL cartridge's "post_restore" action hook - this just restores >> the database to whatever it was before and doesn't handle schema changes: >> >> >> https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-mysql/bin/control#L140 > > > > ok > > >> >> >> Once the necessary MySQL commands for migrating data from 0.9.x to 0.10.x >> are defined, we could try adding them to the AeroGear cartridge's >> "post_restore" action hook. >> > Farah, I was just thinking: should we 'deplay' the upgrade hooks, until we do have the proper upgrade (including database schema) working? -Matthias > > With "necessary MySQL commands" you mean those that take care of the > schema changes? I think generally having a migration script for the schema > is a nice thing to have, regardless of OpenShift. Once we are closer to our > 1.0.0 that's something we have to have. > > Are you planing on adding these necessary MySQL commands (assuming they > are relevant for taking care of schema changes ;-)) for our cartridge? Or > should we just track that requirement in a JIRA for now ? > > -Matthias > > > >> >> > > >> > > > > >> > > > > Migration is not a part of cartridge but I guess that UI should be >> > > fixed. >> > > > > >> > > > >> > > > It's minor, not sure we should really stop the process; especially >> the >> > > UPS >> > > > is now on staging/hold since one entire week >> > > > >> > > > >> > > > > >> > > > > I have filled following bugs: >> > > > > * https://issues.jboss.org/browse/AGPUSH-562 >> > > > > * https://issues.jboss.org/browse/AGPUSH-563 >> > > > > >> > > > > Note, as for Firefox DNS cache, just set >> > > > > network.dnsCacheExpirationGracePeriod=0 in about:config. >> > > > > >> > > > > Karel >> > > > > _______________________________________________ >> > > > > aerogear-dev mailing list >> > > > > aerogear-dev at lists.jboss.org >> > > > > https://lists.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 >> > >> > > > > -- > 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/20140318/fef92819/attachment-0001.html From scm.blanc at gmail.com Tue Mar 18 04:44:00 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 18 Mar 2014 09:44:00 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> Message-ID: Hi, I tried to upgrade my local aerodoc-ios with the new pod : First thing I noticed was that I had to upgrade my cocoapods to 0.29 then my updated pod file : xcodeproj 'AeroDoc.xcodeproj' platform :ios, '7.1' pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' pod 'AeroGear-Push', '0.8.0' And then after typing "pod install" I'm getting : [!] Unable to satisfy the following requirements: - `AFNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking/UIKit (2.2.1)`- `AFNetworking (= 1.3.1)` required by `AeroGear-Push (0.8.0)` I'm probably missing sometinh obvious :) , any ideas ? Do I need to explicitly add AFNetworking in my pod ? Seb On Tue, Mar 18, 2014 at 8:37 AM, Corinne Krych wrote: > Hello iOS Friends, > > AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to > release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and > AFNetworking 2.x (latest 2.2.1). > > To test it, open Podfile and point to the latest git branch > pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > > Help us make this release a success, give it a trial, and let us know how > it goes for your project. > > ++ > 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/20140318/8ad2ddc9/attachment.html From corinnekrych at gmail.com Tue Mar 18 04:51:39 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 18 Mar 2014 09:51:39 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> Message-ID: <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> Hello Sebi Actually PR are on their ways (as we test it) to set proper version, what you need here https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile is to upgrade to: platform :ios, ?7.0' pod 'AFNetworking', ?2.2.1' Note that we?ll support from ios 7.0 Feel free to send the PR with Podfile update if the testing works for you. ++ Thanks for the feedback, Corinne On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) From matzew at apache.org Tue Mar 18 04:52:34 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 09:52:34 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> Message-ID: On Tue, Mar 18, 2014 at 9:44 AM, Sebastien Blanc wrote: > Hi, > I tried to upgrade my local aerodoc-ios with the new pod : > First thing I noticed was that I had to upgrade my cocoapods to 0.29 > > then my updated pod file : > > xcodeproj 'AeroDoc.xcodeproj' > > platform :ios, '7.1' > > > > pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > > pod 'AeroGear-Push', '0.8.0' > > And then after typing "pod install" I'm getting : > > [!] Unable to satisfy the following requirements: > > - `AFNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- > `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection > (2.2.1)`- `AFNetworking/Reachability` required by > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` > required by `AFNetworking/NSURLSession (2.2.1)`- > `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1)`- > `AFNetworking/NSURLSession` required by `AFNetworking/UIKit (2.2.1)`- > `AFNetworking (= 1.3.1)` required by `AeroGear-Push (0.8.0)` > > > I'm probably missing sometinh obvious :) , any ideas ? Do I need to > explicitly add AFNetworking in my pod ? > yeah - it's broken; atm; However, Christos already filed: https://issues.jboss.org/browse/AGPUSH-558 I am sure that one will come w/in the next few days > > Seb > > > > > > On Tue, Mar 18, 2014 at 8:37 AM, Corinne Krych wrote: > >> Hello iOS Friends, >> >> AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to >> release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and >> AFNetworking 2.x (latest 2.2.1). >> >> To test it, open Podfile and point to the latest git branch >> pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' >> >> Help us make this release a success, give it a trial, and let us know how >> it goes for your project. >> >> ++ >> 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 > -- 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/20140318/24f30163/attachment.html From matzew at apache.org Tue Mar 18 04:53:08 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 09:53:08 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> Message-ID: Corinne, no AFN on that project, in the future: https://issues.jboss.org/browse/AGPUSH-558 On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych wrote: > Hello Sebi > > Actually PR are on their ways (as we test it) to set proper version, what > you need here > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > is to upgrade to: > platform :ios, '7.0' > pod 'AFNetworking', '2.2.1' > > Note that we'll support from ios 7.0 > Feel free to send the PR with Podfile update if the testing works for you. > > ++ > Thanks for the feedback, > Corinne > > On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- > `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection > (2.2.1)`- `AFNetworking/Reachability` required by > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` > required by `AFNetworking/NSURLSession (2.2.1)`- > `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140318/bef61ee2/attachment.html From corinnekrych at gmail.com Tue Mar 18 05:05:00 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 18 Mar 2014 10:05:00 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> Message-ID: <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> True, eventually we will remove that dependency. What about getting 1.5 out of the way and then release AG Push registration 0.9.0 without AFNetworkin dependency? ++ Corinne On 18 Mar 2014, at 09:53, Matthias Wessendorf wrote: > Corinne, > > no AFN on that project, in the future: > https://issues.jboss.org/browse/AGPUSH-558 > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych wrote: > Hello Sebi > > Actually PR are on their ways (as we test it) to set proper version, what you need here > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > is to upgrade to: > platform :ios, ?7.0' > pod 'AFNetworking', ?2.2.1' > > Note that we?ll support from ios 7.0 > Feel free to send the PR with Podfile update if the testing works for you. > > ++ > Thanks for the feedback, > Corinne > > On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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 Mar 18 05:06:46 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 10:06:46 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> Message-ID: On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych wrote: > True, eventually we will remove that dependency. > What about getting 1.5 out of the way and then release AG Push > registration 0.9.0 without AFNetworkin dependency? > sounds good to me! > > ++ > Corinne > On 18 Mar 2014, at 09:53, Matthias Wessendorf wrote: > > > Corinne, > > > > no AFN on that project, in the future: > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych > wrote: > > Hello Sebi > > > > Actually PR are on their ways (as we test it) to set proper version, > what you need here > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > > is to upgrade to: > > platform :ios, '7.0' > > pod 'AFNetworking', '2.2.1' > > > > Note that we'll support from ios 7.0 > > Feel free to send the PR with Podfile update if the testing works for > you. > > > > ++ > > Thanks for the feedback, > > Corinne > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- > `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection > (2.2.1)`- `AFNetworking/Reachability` required by > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` > required by `AFNetworking/NSURLSession (2.2.1)`- > `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20140318/1112e5f8/attachment.html From scm.blanc at gmail.com Tue Mar 18 05:47:58 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 18 Mar 2014 10:47:58 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> Message-ID: But until AG Push registration 0.9 is released , 0.8.1 do not work with AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) Shouldn't it make sense to make a 0.8.2 release with an updated pod (what Corinne mentionned in the second message) to "fill the gap" until 0.9 is released ? On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf wrote: > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych wrote: > >> True, eventually we will remove that dependency. >> What about getting 1.5 out of the way and then release AG Push >> registration 0.9.0 without AFNetworkin dependency? >> > > > sounds good to me! > > >> >> ++ >> Corinne >> On 18 Mar 2014, at 09:53, Matthias Wessendorf wrote: >> >> > Corinne, >> > >> > no AFN on that project, in the future: >> > https://issues.jboss.org/browse/AGPUSH-558 >> > >> > >> > >> > >> > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych >> wrote: >> > Hello Sebi >> > >> > Actually PR are on their ways (as we test it) to set proper version, >> what you need here >> > >> https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile >> > is to upgrade to: >> > platform :ios, '7.0' >> > pod 'AFNetworking', '2.2.1' >> > >> > Note that we'll support from ios 7.0 >> > Feel free to send the PR with Podfile update if the testing works for >> you. >> > >> > ++ >> > Thanks for the feedback, >> > Corinne >> > >> > On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: >> > >> > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- >> `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- >> `AFNetworking/Security` required by `AFNetworking (2.2.1)`- >> `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- >> `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- >> `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- >> `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- >> `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection >> (2.2.1)`- `AFNetworking/Reachability` required by >> `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by >> `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` >> required by `AFNetworking/NSURLSession (2.2.1)`- >> `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) >> > >> > >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.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/20140318/f8d00635/attachment.html From corinnekrych at gmail.com Tue Mar 18 05:56:41 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 18 Mar 2014 10:56:41 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> Message-ID: Yep indeed coordination is needed, let?s see how we progress on removing AFNetworking dep. When releasing 1.5 we?ll go either: 0.8.2 => with AFNetworking 2.2.1 or 0.9.0 => without AFNetworking dep Keep you posted (very soon) on that. ++ Corinne On 18 Mar 2014, at 10:47, Sebastien Blanc wrote: > But until AG Push registration 0.9 is released , 0.8.1 do not work with AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) > Shouldn't it make sense to make a 0.8.2 release with an updated pod (what Corinne mentionned in the second message) to "fill the gap" until 0.9 is released ? > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf wrote: > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych wrote: > True, eventually we will remove that dependency. > What about getting 1.5 out of the way and then release AG Push registration 0.9.0 without AFNetworkin dependency? > > > sounds good to me! > > > ++ > Corinne > On 18 Mar 2014, at 09:53, Matthias Wessendorf wrote: > > > Corinne, > > > > no AFN on that project, in the future: > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych wrote: > > Hello Sebi > > > > Actually PR are on their ways (as we test it) to set proper version, what you need here > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > > is to upgrade to: > > platform :ios, ?7.0' > > pod 'AFNetworking', ?2.2.1' > > > > Note that we?ll support from ios 7.0 > > Feel free to send the PR with Podfile update if the testing works for you. > > > > ++ > > Thanks for the feedback, > > Corinne > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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 Tue Mar 18 06:07:14 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 11:07:14 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> Message-ID: On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych wrote: > Yep indeed coordination is needed, let's see how we progress on removing > AFNetworking dep. > When releasing 1.5 we'll go either: > 0.8.2 => with AFNetworking 2.2.1 > sounds like an odd thing, due to item below > or 0.9.0 => without AFNetworking dep > +1 > > Keep you posted (very soon) on that. > > ++ > Corinne > On 18 Mar 2014, at 10:47, Sebastien Blanc wrote: > > > But until AG Push registration 0.9 is released , 0.8.1 do not work with > AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) > > Shouldn't it make sense to make a 0.8.2 release with an updated pod > (what Corinne mentionned in the second message) to "fill the gap" until 0.9 > is released ? > > > > > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf > wrote: > > > > > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych > wrote: > > True, eventually we will remove that dependency. > > What about getting 1.5 out of the way and then release AG Push > registration 0.9.0 without AFNetworkin dependency? > > > > > > sounds good to me! > > > > > > ++ > > Corinne > > On 18 Mar 2014, at 09:53, Matthias Wessendorf wrote: > > > > > Corinne, > > > > > > no AFN on that project, in the future: > > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych > wrote: > > > Hello Sebi > > > > > > Actually PR are on their ways (as we test it) to set proper version, > what you need here > > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > > > is to upgrade to: > > > platform :ios, '7.0' > > > pod 'AFNetworking', '2.2.1' > > > > > > Note that we'll support from ios 7.0 > > > Feel free to send the PR with Podfile update if the testing works for > you. > > > > > > ++ > > > Thanks for the feedback, > > > Corinne > > > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: > > > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- > `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection > (2.2.1)`- `AFNetworking/Reachability` required by > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` > required by `AFNetworking/NSURLSession (2.2.1)`- > `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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/20140318/adc7bab9/attachment-0001.html From corinnekrych at gmail.com Tue Mar 18 06:09:34 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 18 Mar 2014 11:09:34 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> Message-ID: <936C2299-09C0-45BB-B4AC-D7350CE654F2@gmail.com> +1 Here's the plan. Back to testing. ++ Corinne On 18 Mar 2014, at 11:07, Matthias Wessendorf wrote: > > > > On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych wrote: > Yep indeed coordination is needed, let?s see how we progress on removing AFNetworking dep. > When releasing 1.5 we?ll go either: > 0.8.2 => with AFNetworking 2.2.1 > > sounds like an odd thing, due to item below > > > or 0.9.0 => without AFNetworking dep > > +1 > > > Keep you posted (very soon) on that. > > ++ > Corinne > On 18 Mar 2014, at 10:47, Sebastien Blanc wrote: > > > But until AG Push registration 0.9 is released , 0.8.1 do not work with AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) > > Shouldn't it make sense to make a 0.8.2 release with an updated pod (what Corinne mentionned in the second message) to "fill the gap" until 0.9 is released ? > > > > > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf wrote: > > > > > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych wrote: > > True, eventually we will remove that dependency. > > What about getting 1.5 out of the way and then release AG Push registration 0.9.0 without AFNetworkin dependency? > > > > > > sounds good to me! > > > > > > ++ > > Corinne > > On 18 Mar 2014, at 09:53, Matthias Wessendorf wrote: > > > > > Corinne, > > > > > > no AFN on that project, in the future: > > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych wrote: > > > Hello Sebi > > > > > > Actually PR are on their ways (as we test it) to set proper version, what you need here > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > > > is to upgrade to: > > > platform :ios, ?7.0' > > > pod 'AFNetworking', ?2.2.1' > > > > > > Note that we?ll support from ios 7.0 > > > Feel free to send the PR with Podfile update if the testing works for you. > > > > > > ++ > > > Thanks for the feedback, > > > Corinne > > > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: > > > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > sessions: http://www.slideshare.net/mwessendorf > > > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From stian at redhat.com Tue Mar 18 06:53:34 2014 From: stian at redhat.com (Stian Thorgersen) Date: Tue, 18 Mar 2014 06:53:34 -0400 (EDT) Subject: [aerogear-dev] Keycloak adapters for iOS and Android In-Reply-To: <805376679.1293116.1395139456827.JavaMail.zimbra@redhat.com> Message-ID: <1413826749.1296233.1395140014298.JavaMail.zimbra@redhat.com> We're aiming to release beta1 of Keycloak in beginning of May. It would be great to have basic iOS and Android examples added to our demo. With that in mind I have a couple of question: * Any chance anyone from the AeroGear team could contribute an iOS example? Something that works together with our current demo would be great, login with Keycloak and fetch/display customers list from the server is sufficient (same features as customer-portal and customer-portal-js in our demo). It would also be nice to have a small section on how to use it added to our documentation. * Do you have an ETA when Android adapter will be ready? * Same as for iOS, any chance to get some help with an Android example and documentation? Cheers, Stian From bruno at abstractj.org Tue Mar 18 07:21:02 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 18 Mar 2014 08:21:02 -0300 Subject: [aerogear-dev] Keycloak adapters for iOS and Android In-Reply-To: <1413826749.1296233.1395140014298.JavaMail.zimbra@redhat.com> References: <1413826749.1296233.1395140014298.JavaMail.zimbra@redhat.com> Message-ID: Good morning Stian. -- abstractj On March 18, 2014 at 7:53:38 AM, Stian Thorgersen (stian at redhat.com) wrote: > We're aiming to release beta1 of Keycloak in beginning of May. It would be great to have? Great news > basic iOS and Android examples added to our demo. With that in mind I have a couple of question:? You must check their respective roadmaps, each project on AeroGear has its own schedule (http://aerogear.org/docs/planning/).? That said it must be coordinated. If Keycloak adapters are not there, JIRAs to discuss is a good fit. > > * Any chance anyone from the AeroGear team could contribute an iOS example? Something > that works together with our current demo would be great, login with Keycloak and fetch/display > customers list from the server is sufficient (same features as customer-portal and > customer-portal-js in our demo). It would also be nice to have a small section on how to > use it added to our documentation. Do we have JIRAs for that? (http://aerogear.org/docs/planning/roadmaps/AeroGeariOS/) > * Do you have an ETA when Android adapter will be ready? > * Same as for iOS, any chance to get some help with an Android example and documentation?? Please, Android's roadmap (http://aerogear.org/docs/planning/roadmaps/AeroGearAndroid/) > > Cheers, > Stian > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > From daniel at passos.me Tue Mar 18 07:29:28 2014 From: daniel at passos.me (Daniel Passos) Date: Tue, 18 Mar 2014 08:29:28 -0300 Subject: [aerogear-dev] Keycloak adapters for iOS and Android In-Reply-To: <1413826749.1296233.1395140014298.JavaMail.zimbra@redhat.com> References: <805376679.1293116.1395139456827.JavaMail.zimbra@redhat.com> <1413826749.1296233.1395140014298.JavaMail.zimbra@redhat.com> Message-ID: Hi Stian, Answers inline On Tue, Mar 18, 2014 at 7:53 AM, Stian Thorgersen wrote: > We're aiming to release beta1 of Keycloak in beginning of May. It would be > great to have basic iOS and Android examples added to our demo. With that > in mind I have a couple of question: > > * Any chance anyone from the AeroGear team could contribute an iOS > example? Something that works together with our current demo would be > great, login with Keycloak and fetch/display customers list from the server > is sufficient (same features as customer-portal and customer-portal-js in > our demo). It would also be nice to have a small section on how to use it > added to our documentation. > * Do you have an ETA when Android adapter will be ready? > Yes, we have already started working on it. We'll postpone our 1.4 release (scheduled for mid March to mid April ) to include KC adapter see last meeting notes[1] > * Same as for iOS, any chance to get some help with an Android example and > documentation? > Of course. Ping me when you need. Btw, we'll add it on our cookbook app[2] > Cheers, > Stian [1] http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-17-13.47.html [2] https://github.com/aerogear/aerogear-android-cookbook -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140318/7b0bab6e/attachment.html From miguel21op at gmail.com Tue Mar 18 09:22:08 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 13:22:08 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> Message-ID: Hi Erik, Did you see my report? Are you trying to fix the issue? Thanks M From edewit at redhat.com Tue Mar 18 09:25:51 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 18 Mar 2014 14:25:51 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> Message-ID: No Miguel, I didn?t see your report where did you report it? On 18 Mar,2014, at 14:22 , Miguel Lemos wrote: > Hi Erik, > > Did you see my report? > Are you trying to fix the issue? > > Thanks > > M > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From bruno at abstractj.org Tue Mar 18 09:31:46 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 18 Mar 2014 10:31:46 -0300 Subject: [aerogear-dev] aerogear security and android In-Reply-To: <1394642857598-6762.post@n5.nabble.com> References: <1394467743631-6703.post@n5.nabble.com> <1394558729969-6747.post@n5.nabble.com> <1394624522273-6750.post@n5.nabble.com> <1394642857598-6762.post@n5.nabble.com> Message-ID: Good morning Marcelo, sorry if I didn?t get back to you sooner. As I told you, you don?t need AG Security. Thinking about it, I wrote a PoC with Apache Shiro to be tested against AeroGear Android, please take a look:?https://github.com/abstractj/example-jaxrs-shiro Passos already tested it with AG Android Cookbook.? I hope it helps. -- abstractj On March 12, 2014 at 1:47:46 PM, marceloheck (marceloheck at gmail.com) wrote: > hi bruno thank you! > > In android I used the example of the cookbook and it worked > > the server try to use the example of jaxrs and I could not > > try using aerogear-security-shiro and could not, > > have an equal jaxrs example but using shiro? > > infos: > i use android native in client and jboss7.1(ejb jpa resteasy jdk6 jee6) in > server > database of users and profile and data, I seek a REST/JSON in a tomcat 5 > (legacy system) > > > sample sequence: > > >>>>>>>>>>android native send aerogear login <<<<<<<< > private AuthenticationModule authModule; > private String baseURL = > "http://localhost:8080/servicos/service/auth"; > > private TextView status; > private Button login; > private Button logout; > private static final String LOG_TAG = login.class.getName(); > > @Override > protected void onCreate(Bundle savedInstanceState) { > super.onCreate(savedInstanceState); > setContentView(R.layout.activity_main); > > Authenticator authenticator = new Authenticator(baseURL); > AuthenticationConfig authenticationConfig = new > AuthenticationConfig(); > > authenticationConfig.setLoginEndpoint("/login"); > authenticationConfig.setLogoutEndpoint("/logout"); > authModule = authenticator.auth("login", > authenticationConfig); > > status = (TextView) findViewById(R.id.editText1); > login = (Button) findViewById(R.id.button1); > logout = (Button) findViewById(R.id.Button01); > > button = (Button) findViewById(R.id.button1); > > login.setOnClickListener(new View.OnClickListener() { > @Override > public void onClick(View view) { > authModule.login("jhon", "123", new > AbstractActivityCallback() { > } > > > > > >>>>>>>>>server receive <<<<<<<<<<< > (is my problem ) (wanted an example here )(queria um exemplo disso aqui no > shiro ) > > @Path("/auth") > public class LoginEndpoint { > > private static final Logger LOGGER = > Logger.getLogger(LoginEndpoint.class.getSimpleName()); > > // @Inject > private AuthenticationManager authenticationManager; > > @POST > @Path("/login") > @Produces(MediaType.APPLICATION_JSON) > @Consumes(MediaType.APPLICATION_JSON) > public Response login(User simpleUser) { > User user = new User(simpleUser.getUsername(), > simpleUser.getPassword()); > authenticationManager.login(user, simpleUser.getPassword()); > //return simpleUser; > return Response.status(Status.OK).entity(user).build(); > } > > > >>>>>>>>>>>>>>> android receive <<<<<<<<<<<<<<<<<< > > > @Override > public void onSuccess(HeaderAndBody data) { > Log.d(LOG_TAG, "Received ID: " + data.toString() ); > logged(true); > > Toast.makeText(getActivity(), "logado", > Toast.LENGTH_SHORT).show(); > } > ---------(as the android saves login, as he knows that this logged? need > sample) ------- > > > > >>>>>>>>>>>>>>>> android send next requisition <<<<<<<<<< > > URL BASE_URL = new URL("http://localhost:8080/servicos/service/"); > > PageConfig pageConfig = new PageConfig(); > pageConfig.setLimitValue(5); > > pageConfig.setMetadataLocation(PageConfig.MetadataLocations.WEB_LINKING); > PipeConfig pipeConfig = new PipeConfig(BASE_URL, > AbrigoVO.class); > pipeConfig.setEndpoint("pessoa"); > pipeConfig.setPageConfig(pageConfig); > pipeline = new Pipeline(BASE_URL); > pipeline.pipe(pessoaVO.class, pipeConfig); > > LoaderPipe pipes = > pipeline.get("pessoavo", mContext); > pipes.read(readCallback); > return null; > } catch (Exception e) { > // TODO Need error handling > Log.e(LOG_TAG, e.getLocalizedMessage(), e); > Log.e(LOG_TAG, "sem servi?o", e); > e.printStackTrace(); > return null; > } > ---------next pipe in login? how call security rest? necessary is send login > again? ------- > > > >>>>>>>>>>>>>>>server received and response<<<<<<<<<< > > > @GET > @Produces(MediaType.APPLICATION_JSON) > public Response listar(); > > --------how use @secure("admin)? -------- is necessary a sample ----- > > >>>>>>>>>>>>>>>>the end<<<<<<<<<<<<<<<<<< > > > > > -- > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-security-and-android-tp6703p6762.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From miguel21op at gmail.com Mon Mar 17 11:15:24 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 17 Mar 2014 15:15:24 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> Message-ID: Erik, The problem with the iPhone (not Android!) is that whatever comes under the payload parameters is not recognized, and thus they throw an undefined error, preventing the code to proceed. As I told you, this only happens with iPhone. Only the e.alert parameter is loaded. Example: A - What arrives to the phone (I get it through the Xcode debugger): Msg: {en:'598',cd:'',badge:'1',alert:'Oferta irrecus?vel',av:'Especial oferta para si. Prima o bot?o para saber mais',ul:' http://www.metal-pr.net/landingService/template10.php?i=MTAz',ln:'',at:'Oferta irrecus?vel',cp:'',rd:'',lt:'',foreground:'1',} None of the parameters above are read, except the "alert"). B- If I change the code like the way bellow, it will work ('tit', 'not', 'url', and 'ent' are commented: function onNotification(e) { /* tit = e.payload.at; notif = e.payload.av; ent = e.payload.en; */ tit = e.alert; notif = "O que quero dizer"; ent=598; if (e.foreground) { if (ent==entID){ setTimeout (function(){ navigator.notification.confirm( notif, onConfirmDo, tit, 'OK' ); function onConfirmDo(button){ // url= e.payload.ul; url ="http://metal-pr.net"; if(button == "1" && url !='' && sessionStorage.getItem('net')=='on'){ openInside(url+','+imei); } else { // n?o faz nada } } },500) } } } On Mon, Mar 17, 2014 at 2:37 PM, Erik Jan de Wit wrote: > Hi Miguel, > > That is good news, hope you find the cause of the problem. > > Cheers, > Erik Jan > > On 17 Mar,2014, at 15:34 , Miguel Lemos wrote: > > Hi Erik! > > I could seat again in front of a Mac, and already found out what's going > on. I managed to make a pop-up window appear when the notification arrives. > > I'll go through some more testings and afterwards I'll tell you precisely > where the problem is coming from. > > > On Mon, Mar 17, 2014 at 11:09 AM, Erik Jan de Wit wrote: > >> Hi, >> >> That could be a problem, I think Xcode 5.1 doesn?t work with Cordova, >> there are some issue that will be fixed in 3.5 you might have to revert >> this update. As for the plugin update the javascript API has not change >> yet, but it will when we merge the simplification branch. >> >> Cheers, >> Erik Jan >> >> On 17 Mar,2014, at 11:30 , Miguel Lemos wrote: >> >> Further info: I use Xcode 5.1, iOS 7.1 and Cordova 3.4 >> >> M >> >> >> Enviado do meu iPhone >> >> No dia 17/03/2014, ?s 10:13, Erik Jan de Wit >> escreveu: >> >> Hi Miguel, >> >> Not sure what the problem is, but you could maybe try to debug it a bit. >> The easiest way is to start safari on your machine and on your device >> enable the web inspector ( Settings > Safari > Advanced ). Then in safari >> you can go to develop > ?device name? then you can open the javascript >> console and see if there was an error of some kind. >> >> Also we just released a new version (0.0.3) that that fixes some bugs you >> could also try to update to that version by removing and adding the plugin >> in you cordova project. >> >> Hope this helps, >> Erik Jan >> >> On 17 Mar,2014, at 10:53 , Miguel Lemos wrote: >> >> I have this problem now: in iPhone (the same code works just fine with >> Android) the event handler never triggers the alert message. >> >> If the app is running in the background I get the message in the status >> bar, the badge shows, but when I touch on it or if the app is in the >> foreground the alert box inside the app never shows. >> >> As I told you, the same code works just fine in Android. >> >> Meanwhile I noticed this odd thing in the Xcode debugger: even if the app >> is running in the background, when the push notification arrives it says a >> foreground message has arrived... >> >> Thanks >> >> M >> >> Enviado do meu iPhone >> >> No dia 16/03/2014, ?s 18:45, Matthias Wessendorf >> escreveu: >> >> Just saw the rest of the thread :-) >> >> Glad it works! >> >> -Matthias >> >> On Sunday, March 16, 2014, Matthias Wessendorf wrote: >> >>> Does the app-id (bundle identifier) match the one which you created the >>> SSL certificate for? >>> >>> Otherwise it is not valid to Apple >>> >>> -Matthias >>> >>> On Sunday, March 16, 2014, Miguel Lemos wrote: >>> >>>> Hi all! >>>> >>>> As you know I managed - with a little help from my friends ;-) -to >>>> have the push notifications working on Android. But with iOS, not the same >>>> luck so far. What I've done: >>>> >>>> a) I created my development profile at Apple; >>>> b) I uploaded the Certificates.p12 to the AeroGear Server; >>>> c) I installed the devprof profile (the mobile provision file) in Xcode >>>> (which says it's valid); >>>> d) I inserted the variant ID and Secret on my phone code, like this >>>> (keys are not real): >>>> >>>> if(device.platform=='iOS'){ >>>> varID= "bb66d681-zabc-42cc-87f6-c27185c2389f"; >>>> varSec= "e66271f5-dd92-492d-bbac-83736f53e930"; >>>> } else if (device.platform=='Android'){ >>>> varID= "b438d657-5eef-4301-ba82-28c46cc3466f"; >>>> varSec= "150b5f99-z450-4edc-bdad-62dad284af2e"; >>>> } >>>> var pushConfig = { >>>> senderID: "278695547260", // not relevant for Android anyway >>>> pushServerURL: "https://aerogear-metalpush.rhcloud.com", >>>> variantID: varID, >>>> variantSecret: varSec, >>>> alias: userid >>>> } >>>> >>>> But nevertheless I can't register the device. I get this error: >>>> >>>> no valid aps-environment (the message is not in English, so I >>>> translate it freely:"It was not found a valid aps-environment for the app") >>>> >>>> What can be wrong? >>>> >>>> Thanks >>>> >>>> Miguel >>>> >>> >>> >>> -- >>> Sent from Gmail Mobile >>> >> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140317/86614d5f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: 2014-03-17 15.06.07.png Type: image/png Size: 725252 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/86614d5f/attachment-0002.png -------------- next part -------------- A non-text attachment was scrubbed... Name: 2014-03-17 15.05.33.png Type: image/png Size: 145764 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140317/86614d5f/attachment-0003.png From matzew at apache.org Tue Mar 18 09:39:48 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 14:39:48 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> Message-ID: It's in moderator queue, due to the attachement - should be here in a bit :-))) On Tue, Mar 18, 2014 at 2:25 PM, Erik Jan de Wit wrote: > No Miguel, I didn't see your report where did you report it? > > On 18 Mar,2014, at 14:22 , Miguel Lemos wrote: > > > Hi Erik, > > > > Did you see my report? > > Are you trying to fix the issue? > > > > Thanks > > > > M > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20140318/07c30e8f/attachment.html From fjuma at redhat.com Tue Mar 18 09:57:07 2014 From: fjuma at redhat.com (Farah Juma) Date: Tue, 18 Mar 2014 09:57:07 -0400 (EDT) Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: References: <20140317181003.2e9b63c7@kapy-ntb-x220> <1870763722.1787721.1395080862802.JavaMail.zimbra@redhat.com> <1382681329.1846389.1395086174731.JavaMail.zimbra@redhat.com> Message-ID: <2035767885.2375785.1395151027710.JavaMail.zimbra@redhat.com> > From: "Matthias Wessendorf" > To: "Farah Juma" > Cc: "AeroGear Developer Mailing List" > Sent: Tuesday, March 18, 2014 1:47:06 AM > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > On Mon, Mar 17, 2014 at 8:56 PM, Farah Juma wrote: > > > > > > From: "Matthias Wessendorf" > > > To: "Farah Juma" > > > Cc: "AeroGear Developer Mailing List" > > > Sent: Monday, March 17, 2014 2:55:01 PM > > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > > > > > On Mon, Mar 17, 2014 at 7:27 PM, Farah Juma wrote: > > > > > > > > > > > > From: "Matthias Wessendorf" > > > > > To: "AeroGear Developer Mailing List" > > > > > Cc: "Farah Juma" > > > > > Sent: Monday, March 17, 2014 1:14:05 PM > > > > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test > > results > > > > > > > > > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko > > wrote: > > > > > > > > > > > Hey, > > > > > > > > > > > > status looks like: > > > > > > > > > > > > * Integration tests - passed > > > > > > * UI tests - failed - UI glitches in FF > > > > > > > > > > > > > > > > known problem; not sure - but there might be already a ticket for it > > > > > > > > > > > > > > > > * SP tests - passed > > > > > > * Migration tests - failed - scheme problems. > > > > > > > > > > > > > > > > possible - we might have changed the data model between 0.9.x and > > 0.10.x > > > > > > > > Interesting, this would cause issues with modifying existing > > data/adding > > > > new data. As Karel noted on AGPUSH-563, it looks like we would need a > > > > migration strategy for DB schema changes. > > > > > > > > > > yep - I was thought that's part of the upgrade work; but we can file a > > > ticket to explicitly cover this > > > > That would be good. The database part of the upgrade is currently handled > > by the MySQL cartridge's "post_restore" action hook - this just restores > > the database to whatever it was before and doesn't handle schema changes: > > > > > > https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-mysql/bin/control#L140 > > > > ok > > > > > > > > Once the necessary MySQL commands for migrating data from 0.9.x to 0.10.x > > are defined, we could try adding them to the AeroGear cartridge's > > "post_restore" action hook. > > > > With "necessary MySQL commands" you mean those that take care of the schema > changes? Yes, exactly. > I think generally having a migration script for the schema is a > nice thing to have, regardless of OpenShift. Once we are closer to our > 1.0.0 that's something we have to have. +1 > Are you planing on adding these necessary MySQL commands (assuming they are > relevant for taking care of schema changes ;-)) for our cartridge? Or > should we just track that requirement in a JIRA for now ? Let's track this requirement in a JIRA for now. I think it'll be easier for you guys to define the necessary commands as schema changes are being made. Farah > > -Matthias > > > > > > > > > > > > > > > > > > > > > Migration is not a part of cartridge but I guess that UI should be > > > > fixed. > > > > > > > > > > > > > > > > It's minor, not sure we should really stop the process; especially > > the > > > > UPS > > > > > is now on staging/hold since one entire week > > > > > > > > > > > > > > > > > > > > > > I have filled following bugs: > > > > > > * https://issues.jboss.org/browse/AGPUSH-562 > > > > > > * https://issues.jboss.org/browse/AGPUSH-563 > > > > > > > > > > > > Note, as for Firefox DNS cache, just set > > > > > > network.dnsCacheExpirationGracePeriod=0 in about:config. > > > > > > > > > > > > Karel > > > > > > _______________________________________________ > > > > > > aerogear-dev mailing list > > > > > > aerogear-dev at lists.jboss.org > > > > > > https://lists.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 > > > > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > From fjuma at redhat.com Tue Mar 18 09:58:36 2014 From: fjuma at redhat.com (Farah Juma) Date: Tue, 18 Mar 2014 09:58:36 -0400 (EDT) Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: References: <20140317181003.2e9b63c7@kapy-ntb-x220> <1870763722.1787721.1395080862802.JavaMail.zimbra@redhat.com> <1382681329.1846389.1395086174731.JavaMail.zimbra@redhat.com> Message-ID: <644251366.2376634.1395151116716.JavaMail.zimbra@redhat.com> > From: "Matthias Wessendorf" > To: "Farah Juma" > Cc: "AeroGear Developer Mailing List" > Sent: Tuesday, March 18, 2014 4:38:06 AM > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > On Tue, Mar 18, 2014 at 6:47 AM, Matthias Wessendorf > wrote: > > > > > > > > > On Mon, Mar 17, 2014 at 8:56 PM, Farah Juma wrote: > > > >> > >> > From: "Matthias Wessendorf" > >> > To: "Farah Juma" > >> > Cc: "AeroGear Developer Mailing List" > >> > Sent: Monday, March 17, 2014 2:55:01 PM > >> > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > >> > > >> > On Mon, Mar 17, 2014 at 7:27 PM, Farah Juma wrote: > >> > > >> > > > >> > > > From: "Matthias Wessendorf" > >> > > > To: "AeroGear Developer Mailing List" >> > > >> > > > Cc: "Farah Juma" > >> > > > Sent: Monday, March 17, 2014 1:14:05 PM > >> > > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test > >> results > >> > > > > >> > > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko > >> wrote: > >> > > > > >> > > > > Hey, > >> > > > > > >> > > > > status looks like: > >> > > > > > >> > > > > * Integration tests - passed > >> > > > > * UI tests - failed - UI glitches in FF > >> > > > > > >> > > > > >> > > > known problem; not sure - but there might be already a ticket for it > >> > > > > >> > > > > >> > > > > * SP tests - passed > >> > > > > * Migration tests - failed - scheme problems. > >> > > > > > >> > > > > >> > > > possible - we might have changed the data model between 0.9.x and > >> 0.10.x > >> > > > >> > > Interesting, this would cause issues with modifying existing > >> data/adding > >> > > new data. As Karel noted on AGPUSH-563, it looks like we would need a > >> > > migration strategy for DB schema changes. > >> > > > >> > > >> > yep - I was thought that's part of the upgrade work; but we can file a > >> > ticket to explicitly cover this > >> > >> That would be good. The database part of the upgrade is currently handled > >> by the MySQL cartridge's "post_restore" action hook - this just restores > >> the database to whatever it was before and doesn't handle schema changes: > >> > >> > >> https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-mysql/bin/control#L140 > > > > > > > > ok > > > > > >> > >> > >> Once the necessary MySQL commands for migrating data from 0.9.x to 0.10.x > >> are defined, we could try adding them to the AeroGear cartridge's > >> "post_restore" action hook. > >> > > > > > Farah, I was just thinking: should we 'deplay' the upgrade hooks, until we > do have the proper upgrade (including database schema) working? Yes, "deplaying" the upgrade hooks for now sounds like a good idea to me. Farah > > -Matthias > > > > > > > > With "necessary MySQL commands" you mean those that take care of the > > schema changes? I think generally having a migration script for the schema > > is a nice thing to have, regardless of OpenShift. Once we are closer to our > > 1.0.0 that's something we have to have. > > > > Are you planing on adding these necessary MySQL commands (assuming they > > are relevant for taking care of schema changes ;-)) for our cartridge? Or > > should we just track that requirement in a JIRA for now ? > > > > -Matthias > > > > > > > >> > >> > > > >> > > > > > >> > > > > Migration is not a part of cartridge but I guess that UI should be > >> > > fixed. > >> > > > > > >> > > > > >> > > > It's minor, not sure we should really stop the process; especially > >> the > >> > > UPS > >> > > > is now on staging/hold since one entire week > >> > > > > >> > > > > >> > > > > > >> > > > > I have filled following bugs: > >> > > > > * https://issues.jboss.org/browse/AGPUSH-562 > >> > > > > * https://issues.jboss.org/browse/AGPUSH-563 > >> > > > > > >> > > > > Note, as for Firefox DNS cache, just set > >> > > > > network.dnsCacheExpirationGracePeriod=0 in about:config. > >> > > > > > >> > > > > Karel > >> > > > > _______________________________________________ > >> > > > > aerogear-dev mailing list > >> > > > > aerogear-dev at lists.jboss.org > >> > > > > https://lists.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 > >> > > >> > > > > > > > > -- > > 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 > From miguel21op at gmail.com Tue Mar 18 10:04:32 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 14:04:32 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> Message-ID: <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> I sent it yesterday in the afternoon :-( Basically the problem is caused by the fact that the Iphone version doesn't recognizes what's comming under the payload parameters (except the alert one) causing an error. Enviado do meu iPhone No dia 18/03/2014, ?s 13:25, Erik Jan de Wit escreveu: > No Miguel, I didn?t see your report where did you report it? > >> On 18 Mar,2014, at 14:22 , Miguel Lemos wrote: >> >> Hi Erik, >> >> Did you see my report? >> Are you trying to fix the issue? >> >> Thanks >> >> M >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 fjuma at redhat.com Tue Mar 18 10:26:18 2014 From: fjuma at redhat.com (Farah Juma) Date: Tue, 18 Mar 2014 10:26:18 -0400 (EDT) Subject: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results In-Reply-To: <2035767885.2375785.1395151027710.JavaMail.zimbra@redhat.com> References: <20140317181003.2e9b63c7@kapy-ntb-x220> <1870763722.1787721.1395080862802.JavaMail.zimbra@redhat.com> <1382681329.1846389.1395086174731.JavaMail.zimbra@redhat.com> <2035767885.2375785.1395151027710.JavaMail.zimbra@redhat.com> Message-ID: <110199168.2395926.1395152778250.JavaMail.zimbra@redhat.com> > From: "Farah Juma" > To: matzew at apache.org > Cc: "AeroGear Developer Mailing List" > Sent: Tuesday, March 18, 2014 9:57:07 AM > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > > > From: "Matthias Wessendorf" > > To: "Farah Juma" > > Cc: "AeroGear Developer Mailing List" > > Sent: Tuesday, March 18, 2014 1:47:06 AM > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > > > On Mon, Mar 17, 2014 at 8:56 PM, Farah Juma wrote: > > > > > > > > > From: "Matthias Wessendorf" > > > > To: "Farah Juma" > > > > Cc: "AeroGear Developer Mailing List" > > > > Sent: Monday, March 17, 2014 2:55:01 PM > > > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > > > > > > > On Mon, Mar 17, 2014 at 7:27 PM, Farah Juma wrote: > > > > > > > > > > > > > > > From: "Matthias Wessendorf" > > > > > > To: "AeroGear Developer Mailing List" > > > > > > > > > > > > Cc: "Farah Juma" > > > > > > Sent: Monday, March 17, 2014 1:14:05 PM > > > > > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test > > > results > > > > > > > > > > > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko > > > wrote: > > > > > > > > > > > > > Hey, > > > > > > > > > > > > > > status looks like: > > > > > > > > > > > > > > * Integration tests - passed > > > > > > > * UI tests - failed - UI glitches in FF > > > > > > > > > > > > > > > > > > > known problem; not sure - but there might be already a ticket for > > > > > > it > > > > > > > > > > > > > > > > > > > * SP tests - passed > > > > > > > * Migration tests - failed - scheme problems. > > > > > > > > > > > > > > > > > > > possible - we might have changed the data model between 0.9.x and > > > 0.10.x > > > > > > > > > > Interesting, this would cause issues with modifying existing > > > data/adding > > > > > new data. As Karel noted on AGPUSH-563, it looks like we would need a > > > > > migration strategy for DB schema changes. > > > > > > > > > > > > > yep - I was thought that's part of the upgrade work; but we can file a > > > > ticket to explicitly cover this > > > > > > That would be good. The database part of the upgrade is currently handled > > > by the MySQL cartridge's "post_restore" action hook - this just restores > > > the database to whatever it was before and doesn't handle schema changes: > > > > > > > > > https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-mysql/bin/control#L140 > > > > > > > > ok > > > > > > > > > > > > > Once the necessary MySQL commands for migrating data from 0.9.x to 0.10.x > > > are defined, we could try adding them to the AeroGear cartridge's > > > "post_restore" action hook. > > > > > > > With "necessary MySQL commands" you mean those that take care of the schema > > changes? > > Yes, exactly. > > > I think generally having a migration script for the schema is a > > nice thing to have, regardless of OpenShift. Once we are closer to our > > 1.0.0 that's something we have to have. > > +1 > > > Are you planing on adding these necessary MySQL commands (assuming they are > > relevant for taking care of schema changes ;-)) for our cartridge? Or > > should we just track that requirement in a JIRA for now ? > > Let's track this requirement in a JIRA for now. I think it'll be easier for > you guys to define the necessary commands as schema changes are being made. I've created the following JIRA to track this: https://issues.jboss.org/browse/AGPUSH-564 Farah > > > > > -Matthias > > > > > > > > > > > > > > > > > > > > > > > > > > > > Migration is not a part of cartridge but I guess that UI should > > > > > > > be > > > > > fixed. > > > > > > > > > > > > > > > > > > > It's minor, not sure we should really stop the process; especially > > > the > > > > > UPS > > > > > > is now on staging/hold since one entire week > > > > > > > > > > > > > > > > > > > > > > > > > > I have filled following bugs: > > > > > > > * https://issues.jboss.org/browse/AGPUSH-562 > > > > > > > * https://issues.jboss.org/browse/AGPUSH-563 > > > > > > > > > > > > > > Note, as for Firefox DNS cache, just set > > > > > > > network.dnsCacheExpirationGracePeriod=0 in about:config. > > > > > > > > > > > > > > Karel > > > > > > > _______________________________________________ > > > > > > > aerogear-dev mailing list > > > > > > > aerogear-dev at lists.jboss.org > > > > > > > https://lists.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 > > > > > > > > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/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 Tue Mar 18 10:42:04 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 18 Mar 2014 15:42:04 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> Message-ID: Hi Miguel, As you can see from the log statement on iOS the extra parameters are not in a separate payload object but direct under the root. I?ll correct this. Cheers, Erik Jan On 18 Mar,2014, at 15:04 , Miguel Lemos wrote: > I sent it yesterday in the afternoon :-( > Basically the problem is caused by the fact that the Iphone version doesn't recognizes what's comming under the payload parameters (except the alert one) causing an error. > > Enviado do meu iPhone > > No dia 18/03/2014, ?s 13:25, Erik Jan de Wit escreveu: > >> No Miguel, I didn?t see your report where did you report it? >> >>> On 18 Mar,2014, at 14:22 , Miguel Lemos wrote: >>> >>> Hi Erik, >>> >>> Did you see my report? >>> Are you trying to fix the issue? >>> >>> Thanks >>> >>> M >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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 miguel21op at gmail.com Tue Mar 18 10:49:09 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 14:49:09 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> Message-ID: Fine, Erik! Nice to know it's easy to fix. A small issue, that caused - almost - everything to fail... I'm glad I could help in the role of "bug buster" ;-) Miguel Enviado do meu iPhone No dia 18/03/2014, ?s 14:42, Erik Jan de Wit escreveu: > Hi Miguel, > > As you can see from the log statement on iOS the extra parameters are not in a separate payload object but direct under the root. I?ll correct this. > > Cheers, > Erik Jan > >> On 18 Mar,2014, at 15:04 , Miguel Lemos wrote: >> >> I sent it yesterday in the afternoon :-( >> Basically the problem is caused by the fact that the Iphone version doesn't recognizes what's comming under the payload parameters (except the alert one) causing an error. >> >> Enviado do meu iPhone >> >> No dia 18/03/2014, ?s 13:25, Erik Jan de Wit escreveu: >> >>> No Miguel, I didn?t see your report where did you report it? >>> >>>> On 18 Mar,2014, at 14:22 , Miguel Lemos wrote: >>>> >>>> Hi Erik, >>>> >>>> Did you see my report? >>>> Are you trying to fix the issue? >>>> >>>> Thanks >>>> >>>> M >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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 corinnekrych at gmail.com Tue Mar 18 10:52:14 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 18 Mar 2014 15:52:14 +0100 Subject: [aerogear-dev] Asciidoc snippet Git hook In-Reply-To: References: <20140221110318.7a47354b@kapy-ntb-x220> <99FADA47-2775-4259-BF07-15F5567781DC@gmail.com> <20140226121801.369ac045@kapy-ntb-x220> Message-ID: Hello folks, On the inlude snippet topic, I?ve just proposed a PR: https://github.com/aerogear/aerogear.org/pull/275 Here it?s to avoid duplicate documentation, but we can reuse same mechanism for code snippet as discussed below. ++ Corinne On 26 Feb 2014, at 14:02, Corinne Krych wrote: > Cool, I'll stay tune then ;) > > > On 26 February 2014 12:18, Karel Piwko wrote: > Makes perfect sense. > > However, we need to agree on tag format. The hook might be useful no matter > the format, for instance to check that a tag is missing in latest commit. I'll > rework it next week to reflect that. > > Karel > > On Wed, 26 Feb 2014 09:51:53 +0100 > Corinne Krych wrote: > > > Hello Karel, > > > > Yesterday, discussing with a friend who is writing his documentation using > > asciidoctor: > > http://beta.groovy-lang.org/docs/groovy-2.3.0-SNAPSHOT/html/documentation/ > > > > Instead of using line number, he uses tag in his documentation inclusion like: > > > > [source,groovy] > > -------------------------------- > > include::{projectdir}/src/spec/test/DifferencesFromJavaTest.groovy[tags=innerclass_3,indent=0] > > ???????????????? > > > > And in his code source he puts some tag like below: > > > > // tag::innerclass_3[] > > public class Y { > > public class X {} > > public X foo() { > > return new X() > > } > > public static X createX(Y y) { > > return new X(y) > > } > > } > > // end::innerclass_3[] > > > > I think it worth a trial. wdyt? > > > > ++ > > Corinne > > > > > > On 21 Feb 2014, at 11:03, Karel Piwko wrote: > > > > > I've created following Git hook - > > > https://github.com/kpiwko/asciidoc-git-hooks > > > > > > Let me know if you like it and we can start using it improving our > > > documentation kept DRY experience. > > > > > > Thanks, > > > > > > Karel > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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 marti1003 at hotmail.com Tue Mar 18 11:53:28 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Tue, 18 Mar 2014 10:53:28 -0500 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Message-ID: Hi! I made some firefox os apps and I Java dev I really interesting in https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ Could you tell me more about this project? and how to make my proposal for this project? Regards Willy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140318/0844a93e/attachment.html From scm.blanc at gmail.com Tue Mar 18 11:59:08 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 18 Mar 2014 16:59:08 +0100 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: Message-ID: Hi, I think you should post that to the RHQ mailing list since it's a RHQ related project https://fedorahosted.org/mailman/listinfo/rhq-users Seb On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez < marti1003 at hotmail.com> wrote: > Hi! > > I made some firefox os apps and I Java dev > I really interesting in > > > https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ > > Could you tell me more about this project? and how to make my proposal for > this project? > > Regards > Willy > > _______________________________________________ > 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/20140318/48beb77c/attachment.html From edewit at redhat.com Tue Mar 18 12:08:25 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 18 Mar 2014 17:08:25 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> Message-ID: <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> PR submitted https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: > Fine, Erik! > > Nice to know it's easy to fix. > > A small issue, that caused - almost - everything to fail... > > I'm glad I could help in the role of "bug buster" ;-) > > Miguel > > Enviado do meu iPhone -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140318/61916ac9/attachment.html From marti1003 at hotmail.com Tue Mar 18 12:15:35 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Tue, 18 Mar 2014 11:15:35 -0500 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: , Message-ID: ups sorry is this https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Support_new_Push_Networks_on_the_UnifiedPush_Server Date: Tue, 18 Mar 2014 16:59:08 +0100 From: scm.blanc at gmail.com To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hi,I think you should post that to the RHQ mailing list since it's a RHQ related project https://fedorahosted.org/mailman/listinfo/rhq-users Seb On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez wrote: Hi! I made some firefox os apps and I Java dev I really interesting in https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ Could you tell me more about this project? and how to make my proposal for this project? Regards Willy _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.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/20140318/c851beca/attachment-0001.html From edewit at redhat.com Tue Mar 18 12:24:12 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 18 Mar 2014 17:24:12 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> Message-ID: <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> BTW Miguel I see that you are sending a lot of extras in the message, be careful that Apple doesn?t allow the message to become to big the max is 256 bytes. On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: > > PR submitted https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 > > On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: > >> Fine, Erik! >> >> Nice to know it's easy to fix. >> >> A small issue, that caused - almost - everything to fail... >> >> I'm glad I could help in the role of "bug buster" ;-) >> >> Miguel >> >> Enviado do meu iPhone > > _______________________________________________ > 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/20140318/ef503722/attachment.html From miguel21op at gmail.com Tue Mar 18 12:34:59 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 16:34:59 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> Message-ID: Thanks Erik. I know that; the total payload never surpasses 256 byes and the av parameter (the notification itself) 107 characters. After the correction I just have the reinstall the plugin? M Enviado do meu iPhone No dia 18/03/2014, ?s 16:24, Erik Jan de Wit escreveu: > BTW Miguel I see that you are sending a lot of extras in the message, be careful that Apple doesn?t allow the message to become to big the max is 256 bytes. > >> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >> >> >> PR submitted https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >> >>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>> >>> Fine, Erik! >>> >>> Nice to know it's easy to fix. >>> >>> A small issue, that caused - almost - everything to fail... >>> >>> I'm glad I could help in the role of "bug buster" ;-) >>> >>> Miguel >>> >>> Enviado do meu iPhone >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140318/d698eace/attachment.html From scm.blanc at gmail.com Tue Mar 18 12:37:46 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 18 Mar 2014 17:37:46 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> Message-ID: On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: > Thanks Erik. I know that; the total payload never surpasses 256 byes and > the av parameter (the notification itself) 107 characters. > > After the correction I just have the reinstall the plugin? > That should be enough but it has sometime failed for me , in this case you will need to do a : cordova platform remove ios cordova platform add ios > M > > Enviado do meu iPhone > > No dia 18/03/2014, ?s 16:24, Erik Jan de Wit escreveu: > > BTW Miguel I see that you are sending a lot of extras in the message, be > careful that Apple doesn't allow the message to become to big the max is > 256 bytes. > > On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: > > > PR submitted > https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 > > On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: > > Fine, Erik! > > Nice to know it's easy to fix. > > A small issue, that caused - almost - everything to fail... > > I'm glad I could help in the role of "bug buster" ;-) > > Miguel > > Enviado do meu iPhone > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140318/8e208d97/attachment.html From miguel21op at gmail.com Tue Mar 18 12:41:53 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 16:41:53 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> Message-ID: <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Yes. That "trick" has to be used sometimes. That's a very annoying Cordova issue. Thanks. Enviado do meu iPhone No dia 18/03/2014, ?s 16:37, Sebastien Blanc escreveu: > > > >> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >> Thanks Erik. I know that; the total payload never surpasses 256 byes and the av parameter (the notification itself) 107 characters. >> >> After the correction I just have the reinstall the plugin? > That should be enough but it has sometime failed for me , in this case you will need to do a : > > cordova platform remove ios > cordova platform add ios > >> >> M >> >> Enviado do meu iPhone >> >> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit escreveu: >> >>> BTW Miguel I see that you are sending a lot of extras in the message, be careful that Apple doesn?t allow the message to become to big the max is 256 bytes. >>> >>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >>>> >>>> >>>> PR submitted https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>> >>>>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>>>> >>>>> Fine, Erik! >>>>> >>>>> Nice to know it's easy to fix. >>>>> >>>>> A small issue, that caused - almost - everything to fail... >>>>> >>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>> >>>>> Miguel >>>>> >>>>> Enviado do meu iPhone >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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/20140318/f55f2e83/attachment-0001.html From matzew at apache.org Tue Mar 18 12:48:11 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 17:48:11 +0100 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: Message-ID: Hello Willy, the AeroGear UnifiedPush server supports push notifications over a unified API for the following platforms: * Google Cloud Messaging (Android and Chrome) * APNs (iOS) ==> Safari is on the works (by Luke) * SimplePush (Firefox OS and polyfil for any browser) The goal of the suggested project would be adding support for other push networks: * Amazon Push * Windows Phone/Mobile * Black Berry Besides that we are happy to get support for other push networks as well. The main work would be the integration of those networks (server-side, admin UI, documentation and examples) Does that sound interesting to you ? Greetings, Matthias On Tue, Mar 18, 2014 at 5:15 PM, Willy Martin Aguirre Rodriguez < marti1003 at hotmail.com> wrote: > ups sorry is this > > https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Support_new_Push_Networks_on_the_UnifiedPush_Server > > ------------------------------ > Date: Tue, 18 Mar 2014 16:59:08 +0100 > From: scm.blanc at gmail.com > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > > Hi, > I think you should post that to the RHQ mailing list since it's a RHQ > related project > https://fedorahosted.org/mailman/listinfo/rhq-users > > Seb > > > > On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > Hi! > > I made some firefox os apps and I Java dev > I really interesting in > > > https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ > > Could you tell me more about this project? and how to make my proposal for > this project? > > Regards > Willy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140318/7c5a0472/attachment.html From marti1003 at hotmail.com Tue Mar 18 13:16:08 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Tue, 18 Mar 2014 12:16:08 -0500 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: , , , Message-ID: Yes! I really like to work with mobile technology Date: Tue, 18 Mar 2014 17:48:11 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hello Willy, the AeroGear UnifiedPush server supports push notifications over a unified API for the following platforms:* Google Cloud Messaging (Android and Chrome)* APNs (iOS) ==> Safari is on the works (by Luke) * SimplePush (Firefox OS and polyfil for any browser) The goal of the suggested project would be adding support for other push networks:* Amazon Push* Windows Phone/Mobile * Black Berry Besides that we are happy to get support for other push networks as well. The main work would be the integration of those networks (server-side, admin UI, documentation and examples) Does that sound interesting to you ? Greetings,Matthias On Tue, Mar 18, 2014 at 5:15 PM, Willy Martin Aguirre Rodriguez wrote: ups sorry is this https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Support_new_Push_Networks_on_the_UnifiedPush_Server Date: Tue, 18 Mar 2014 16:59:08 +0100 From: scm.blanc at gmail.com To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hi,I think you should post that to the RHQ mailing list since it's a RHQ related project https://fedorahosted.org/mailman/listinfo/rhq-users Seb On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez wrote: Hi! I made some firefox os apps and I Java dev I really interesting in https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ Could you tell me more about this project? and how to make my proposal for this project? Regards Willy _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.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/20140318/dc332870/attachment.html From matzew at apache.org Tue Mar 18 13:27:28 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 18 Mar 2014 18:27:28 +0100 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: Message-ID: On Tue, Mar 18, 2014 at 6:16 PM, Willy Martin Aguirre Rodriguez < marti1003 at hotmail.com> wrote: > Yes! > > I really like to work with mobile technology > awesome! Regarding the requested technologies (e.g. Amazon Push, BlackBerry or Windows), do you have experience in that area (e.g. development of apps and/or push APIs for them) ? Greetings, Matthias > > > ------------------------------ > Date: Tue, 18 Mar 2014 17:48:11 +0100 > From: matzew at apache.org > > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > Hello Willy, > > the AeroGear UnifiedPush server supports push notifications over a unified > API for the following platforms: > * Google Cloud Messaging (Android and Chrome) > * APNs (iOS) ==> Safari is on the works (by Luke) > * SimplePush (Firefox OS and polyfil for any browser) > > > The goal of the suggested project would be adding support for other push > networks: > * Amazon Push > * Windows Phone/Mobile > * Black Berry > > Besides that we are happy to get support for other push networks as well. > > > The main work would be the integration of those networks (server-side, > admin UI, documentation and examples) > > > Does that sound interesting to you ? > > > Greetings, > Matthias > > > > > On Tue, Mar 18, 2014 at 5:15 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > ups sorry is this > > https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Support_new_Push_Networks_on_the_UnifiedPush_Server > > ------------------------------ > Date: Tue, 18 Mar 2014 16:59:08 +0100 > From: scm.blanc at gmail.com > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > > Hi, > I think you should post that to the RHQ mailing list since it's a RHQ > related project > https://fedorahosted.org/mailman/listinfo/rhq-users > > Seb > > > > On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > Hi! > > I made some firefox os apps and I Java dev > I really interesting in > > > https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ > > Could you tell me more about this project? and how to make my proposal for > this project? > > Regards > Willy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140318/27d02236/attachment-0001.html From marti1003 at hotmail.com Tue Mar 18 15:26:01 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Tue, 18 Mar 2014 14:26:01 -0500 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: , , , , , Message-ID: About my experience: for mobile I am using cordova(phonegap) for android this include Jquery mobile and dev firerfox apps with backbonejs backend java play framework http://www.playframework.com/ (hibernate) and dynamic jasper I remember was made an app with j2me and servlets communication via sockets I will finish a project where connects two systems one of then is Oracle PeopleSoft and and Adryan Cosapi Data(http://www.cosapidata.com.pe/Adryan.asp) via webservices. here you are my github account https://github.com/marti1125 Regards Willy Date: Tue, 18 Mar 2014 18:27:28 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server On Tue, Mar 18, 2014 at 6:16 PM, Willy Martin Aguirre Rodriguez wrote: Yes! I really like to work with mobile technology awesome! Regarding the requested technologies (e.g. Amazon Push, BlackBerry or Windows), do you have experience in that area (e.g. development of apps and/or push APIs for them) ? Greetings,Matthias Date: Tue, 18 Mar 2014 17:48:11 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hello Willy, the AeroGear UnifiedPush server supports push notifications over a unified API for the following platforms: * Google Cloud Messaging (Android and Chrome)* APNs (iOS) ==> Safari is on the works (by Luke) * SimplePush (Firefox OS and polyfil for any browser) The goal of the suggested project would be adding support for other push networks:* Amazon Push* Windows Phone/Mobile * Black Berry Besides that we are happy to get support for other push networks as well. The main work would be the integration of those networks (server-side, admin UI, documentation and examples) Does that sound interesting to you ? Greetings,Matthias On Tue, Mar 18, 2014 at 5:15 PM, Willy Martin Aguirre Rodriguez wrote: ups sorry is this https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Support_new_Push_Networks_on_the_UnifiedPush_Server Date: Tue, 18 Mar 2014 16:59:08 +0100 From: scm.blanc at gmail.com To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hi,I think you should post that to the RHQ mailing list since it's a RHQ related project https://fedorahosted.org/mailman/listinfo/rhq-users Seb On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez wrote: Hi! I made some firefox os apps and I Java dev I really interesting in https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ Could you tell me more about this project? and how to make my proposal for this project? Regards Willy _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140318/dd07bf54/attachment.html From miguel21op at gmail.com Tue Mar 18 17:30:15 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 21:30:15 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Message-ID: Erik, I just uninstalled and installed again the Aerogear plugin, removed and installed again the Ios platform, I compiled the program, but the result didn't change: XCode debugger: *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',}* cordova plugin add org.jboss.aerogear.cordova.push Maybe you didn't uploaded it yet? Thanks M On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: > Yes. That "trick" has to be used sometimes. That's a very annoying Cordova > issue. Thanks. > > Enviado do meu iPhone > > No dia 18/03/2014, ?s 16:37, Sebastien Blanc > escreveu: > > > > > On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: > >> Thanks Erik. I know that; the total payload never surpasses 256 byes and >> the av parameter (the notification itself) 107 characters. >> >> After the correction I just have the reinstall the plugin? >> > That should be enough but it has sometime failed for me , in this case you > will need to do a : > > cordova platform remove ios > cordova platform add ios > > >> M >> >> Enviado do meu iPhone >> >> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >> escreveu: >> >> BTW Miguel I see that you are sending a lot of extras in the message, be >> careful that Apple doesn?t allow the message to become to big the max is >> 256 bytes. >> >> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >> >> >> PR submitted >> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >> >> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >> >> Fine, Erik! >> >> Nice to know it's easy to fix. >> >> A small issue, that caused - almost - everything to fail... >> >> I'm glad I could help in the role of "bug buster" ;-) >> >> Miguel >> >> Enviado do meu iPhone >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140318/2ad8181a/attachment.html From scm.blanc at gmail.com Tue Mar 18 17:43:40 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 18 Mar 2014 22:43:40 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Message-ID: Hi, Erik's fix isn't merged yet on our master repo. If you can't wait :) You could clone Erik's branch containing the fix : git clone https://github.com/edewit/aerogear-pushplugin-cordova/ cd aerogear-pushplugin-cordova git checkout payload-missing And then install the plugin from your local folder cordova plugin add /Home/whereeveryouputtheplugin/aerogear-pushplugin-cordova Hope it helps On Tue, Mar 18, 2014 at 10:30 PM, Miguel Lemos wrote: > Erik, > > I just uninstalled and installed again the Aerogear plugin, removed and > installed again the Ios platform, I compiled the program, but the result > didn't change: > > > XCode debugger: > > > > > *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: > {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} > * > > cordova plugin add org.jboss.aerogear.cordova.push > > Maybe you didn't uploaded it yet? > > Thanks > > M > > > On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: > >> Yes. That "trick" has to be used sometimes. That's a very annoying >> Cordova issue. Thanks. >> >> Enviado do meu iPhone >> >> No dia 18/03/2014, ?s 16:37, Sebastien Blanc >> escreveu: >> >> >> >> >> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >> >>> Thanks Erik. I know that; the total payload never surpasses 256 byes and >>> the av parameter (the notification itself) 107 characters. >>> >>> After the correction I just have the reinstall the plugin? >>> >> That should be enough but it has sometime failed for me , in this case >> you will need to do a : >> >> cordova platform remove ios >> cordova platform add ios >> >> >>> M >>> >>> Enviado do meu iPhone >>> >>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >>> escreveu: >>> >>> BTW Miguel I see that you are sending a lot of extras in the message, be >>> careful that Apple doesn't allow the message to become to big the max is >>> 256 bytes. >>> >>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >>> >>> >>> PR submitted >>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>> >>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>> >>> Fine, Erik! >>> >>> Nice to know it's easy to fix. >>> >>> A small issue, that caused - almost - everything to fail... >>> >>> I'm glad I could help in the role of "bug buster" ;-) >>> >>> Miguel >>> >>> Enviado do meu iPhone >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140318/82e1245b/attachment-0001.html From miguel21op at gmail.com Tue Mar 18 17:45:07 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 21:45:07 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Message-ID: Forget my previous post! Done ;-) I uploaded and installed directly the PushPugin.m to its location. I didn't pay attention to what you wrote... It's working OK now and there's no error. On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: > Erik, > > I just uninstalled and installed again the Aerogear plugin, removed and > installed again the Ios platform, I compiled the program, but the result > didn't change: > > > XCode debugger: > > > > > *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: > {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} > * > > cordova plugin add org.jboss.aerogear.cordova.push > > Maybe you didn't uploaded it yet? > > Thanks > > M > > > On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: > >> Yes. That "trick" has to be used sometimes. That's a very annoying >> Cordova issue. Thanks. >> >> Enviado do meu iPhone >> >> No dia 18/03/2014, ?s 16:37, Sebastien Blanc >> escreveu: >> >> >> >> >> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >> >>> Thanks Erik. I know that; the total payload never surpasses 256 byes and >>> the av parameter (the notification itself) 107 characters. >>> >>> After the correction I just have the reinstall the plugin? >>> >> That should be enough but it has sometime failed for me , in this case >> you will need to do a : >> >> cordova platform remove ios >> cordova platform add ios >> >> >>> M >>> >>> Enviado do meu iPhone >>> >>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >>> escreveu: >>> >>> BTW Miguel I see that you are sending a lot of extras in the message, be >>> careful that Apple doesn?t allow the message to become to big the max is >>> 256 bytes. >>> >>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >>> >>> >>> PR submitted >>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>> >>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>> >>> Fine, Erik! >>> >>> Nice to know it's easy to fix. >>> >>> A small issue, that caused - almost - everything to fail... >>> >>> I'm glad I could help in the role of "bug buster" ;-) >>> >>> Miguel >>> >>> Enviado do meu iPhone >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140318/796b4316/attachment.html From miguel21op at gmail.com Tue Mar 18 17:46:33 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 21:46:33 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Message-ID: Thanks Seb :-) I had already notice that and installed the new file "? la main". I't working ! On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: > Forget my previous post! Done ;-) > > I uploaded and installed directly the PushPugin.m to its location. I > didn't pay attention to what you wrote... > It's working OK now and there's no error. > > > > > On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: > >> Erik, >> >> I just uninstalled and installed again the Aerogear plugin, removed and >> installed again the Ios platform, I compiled the program, but the result >> didn't change: >> >> >> XCode debugger: >> >> >> >> >> *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: >> {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} >> * >> >> cordova plugin add org.jboss.aerogear.cordova.push >> >> Maybe you didn't uploaded it yet? >> >> Thanks >> >> M >> >> >> On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: >> >>> Yes. That "trick" has to be used sometimes. That's a very annoying >>> Cordova issue. Thanks. >>> >>> Enviado do meu iPhone >>> >>> No dia 18/03/2014, ?s 16:37, Sebastien Blanc >>> escreveu: >>> >>> >>> >>> >>> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >>> >>>> Thanks Erik. I know that; the total payload never surpasses 256 byes >>>> and the av parameter (the notification itself) 107 characters. >>>> >>>> After the correction I just have the reinstall the plugin? >>>> >>> That should be enough but it has sometime failed for me , in this case >>> you will need to do a : >>> >>> cordova platform remove ios >>> cordova platform add ios >>> >>> >>>> M >>>> >>>> Enviado do meu iPhone >>>> >>>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >>>> escreveu: >>>> >>>> BTW Miguel I see that you are sending a lot of extras in the message, >>>> be careful that Apple doesn?t allow the message to become to big the max is >>>> 256 bytes. >>>> >>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >>>> >>>> >>>> PR submitted >>>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>> >>>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>>> >>>> Fine, Erik! >>>> >>>> Nice to know it's easy to fix. >>>> >>>> A small issue, that caused - almost - everything to fail... >>>> >>>> I'm glad I could help in the role of "bug buster" ;-) >>>> >>>> Miguel >>>> >>>> Enviado do meu iPhone >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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/20140318/af05a737/attachment.html From scm.blanc at gmail.com Tue Mar 18 17:50:21 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 18 Mar 2014 22:50:21 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Message-ID: Cool ! Would be nice if you could add a comment here https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 like "+1 it's working" , assuming you have a github account. On Tue, Mar 18, 2014 at 10:46 PM, Miguel Lemos wrote: > Thanks Seb :-) > > I had already notice that and installed the new file "? la main". I't > working ! > > > On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: > >> Forget my previous post! Done ;-) >> >> I uploaded and installed directly the PushPugin.m to its location. I >> didn't pay attention to what you wrote... >> It's working OK now and there's no error. >> >> >> >> >> On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: >> >>> Erik, >>> >>> I just uninstalled and installed again the Aerogear plugin, removed and >>> installed again the Ios platform, I compiled the program, but the result >>> didn't change: >>> >>> >>> XCode debugger: >>> >>> >>> >>> >>> *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: >>> {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} >>> * >>> >>> cordova plugin add org.jboss.aerogear.cordova.push >>> >>> Maybe you didn't uploaded it yet? >>> >>> Thanks >>> >>> M >>> >>> >>> On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: >>> >>>> Yes. That "trick" has to be used sometimes. That's a very annoying >>>> Cordova issue. Thanks. >>>> >>>> Enviado do meu iPhone >>>> >>>> No dia 18/03/2014, ?s 16:37, Sebastien Blanc >>>> escreveu: >>>> >>>> >>>> >>>> >>>> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >>>> >>>>> Thanks Erik. I know that; the total payload never surpasses 256 byes >>>>> and the av parameter (the notification itself) 107 characters. >>>>> >>>>> After the correction I just have the reinstall the plugin? >>>>> >>>> That should be enough but it has sometime failed for me , in this case >>>> you will need to do a : >>>> >>>> cordova platform remove ios >>>> cordova platform add ios >>>> >>>> >>>>> M >>>>> >>>>> Enviado do meu iPhone >>>>> >>>>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >>>>> escreveu: >>>>> >>>>> BTW Miguel I see that you are sending a lot of extras in the message, >>>>> be careful that Apple doesn't allow the message to become to big the max is >>>>> 256 bytes. >>>>> >>>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >>>>> >>>>> >>>>> PR submitted >>>>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>>> >>>>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>>>> >>>>> Fine, Erik! >>>>> >>>>> Nice to know it's easy to fix. >>>>> >>>>> A small issue, that caused - almost - everything to fail... >>>>> >>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>> >>>>> Miguel >>>>> >>>>> Enviado do meu iPhone >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.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/20140318/7a1cecbb/attachment-0001.html From miguel21op at gmail.com Tue Mar 18 17:56:06 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 21:56:06 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Message-ID: Too soon, unfortunately ! Isn't yet 100% perfect. There's still a problem if the app is running in the background. I must dig further to understand why it happens :-( On Tue, Mar 18, 2014 at 9:50 PM, Sebastien Blanc wrote: > Cool ! > Would be nice if you could add a comment here > https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 like "+1 > it's working" , assuming you have a github account. > > > > On Tue, Mar 18, 2014 at 10:46 PM, Miguel Lemos wrote: > >> Thanks Seb :-) >> >> I had already notice that and installed the new file "? la main". I't >> working ! >> >> >> On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: >> >>> Forget my previous post! Done ;-) >>> >>> I uploaded and installed directly the PushPugin.m to its location. I >>> didn't pay attention to what you wrote... >>> It's working OK now and there's no error. >>> >>> >>> >>> >>> On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: >>> >>>> Erik, >>>> >>>> I just uninstalled and installed again the Aerogear plugin, removed and >>>> installed again the Ios platform, I compiled the program, but the result >>>> didn't change: >>>> >>>> >>>> XCode debugger: >>>> >>>> >>>> >>>> >>>> *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: >>>> {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} >>>> * >>>> >>>> cordova plugin add org.jboss.aerogear.cordova.push >>>> >>>> Maybe you didn't uploaded it yet? >>>> >>>> Thanks >>>> >>>> M >>>> >>>> >>>> On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: >>>> >>>>> Yes. That "trick" has to be used sometimes. That's a very annoying >>>>> Cordova issue. Thanks. >>>>> >>>>> Enviado do meu iPhone >>>>> >>>>> No dia 18/03/2014, ?s 16:37, Sebastien Blanc >>>>> escreveu: >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >>>>> >>>>>> Thanks Erik. I know that; the total payload never surpasses 256 byes >>>>>> and the av parameter (the notification itself) 107 characters. >>>>>> >>>>>> After the correction I just have the reinstall the plugin? >>>>>> >>>>> That should be enough but it has sometime failed for me , in this case >>>>> you will need to do a : >>>>> >>>>> cordova platform remove ios >>>>> cordova platform add ios >>>>> >>>>> >>>>>> M >>>>>> >>>>>> Enviado do meu iPhone >>>>>> >>>>>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >>>>>> escreveu: >>>>>> >>>>>> BTW Miguel I see that you are sending a lot of extras in the message, >>>>>> be careful that Apple doesn?t allow the message to become to big the max is >>>>>> 256 bytes. >>>>>> >>>>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >>>>>> >>>>>> >>>>>> PR submitted >>>>>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>>>> >>>>>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>>>>> >>>>>> Fine, Erik! >>>>>> >>>>>> Nice to know it's easy to fix. >>>>>> >>>>>> A small issue, that caused - almost - everything to fail... >>>>>> >>>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>>> >>>>>> Miguel >>>>>> >>>>>> Enviado do meu iPhone >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>> >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140318/63d7e200/attachment.html From miguel21op at gmail.com Tue Mar 18 18:23:51 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 22:23:51 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Message-ID: Not 100% yet. If the app is running in the foreground, now the Json array is formed in a different way, and the alert window shows correctly and loads all the paramaters: *2014-03-18 22:00:12.980 SmartDrifter[4011:60b] Msg: {"alert":"Ol?! Benvindo aos Armaz?ns do Chiado","badge":"1","payload": {"lt":"0.00000000000","cd":"","av":"Ol?! Benvindo aos Armaz?ns do Chiado","ul":"http://metal-pr.net/c/?79 ","ln":"0.00000000000","en":"598","at":"Aviso","cp":"79","rd":"0",},"foreground":"1"}*But if the message arrives first to the status bar (meaning: the app is not available), then nothing happens when I press the notification: the app opens indeed, but no alert window shows. Unfortunately I could not trace any errors, neither through the Safari debugger (the problem happens too soon, maybe before the index.html is fully available), nor through Xcode. But the problem has nothing to do with the previously faulty parameters because an alert(e.alert) doesn't trigger nothing either... On Tue, Mar 18, 2014 at 9:56 PM, Miguel Lemos wrote: > Too soon, unfortunately ! > > Isn't yet 100% perfect. There's still a problem if the app is running in > the background. I must dig further to understand why it happens :-( > > > On Tue, Mar 18, 2014 at 9:50 PM, Sebastien Blanc wrote: > >> Cool ! >> Would be nice if you could add a comment here >> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 like "+1 >> it's working" , assuming you have a github account. >> >> >> >> On Tue, Mar 18, 2014 at 10:46 PM, Miguel Lemos wrote: >> >>> Thanks Seb :-) >>> >>> I had already notice that and installed the new file "? la main". I't >>> working ! >>> >>> >>> On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: >>> >>>> Forget my previous post! Done ;-) >>>> >>>> I uploaded and installed directly the PushPugin.m to its location. I >>>> didn't pay attention to what you wrote... >>>> It's working OK now and there's no error. >>>> >>>> >>>> >>>> >>>> On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: >>>> >>>>> Erik, >>>>> >>>>> I just uninstalled and installed again the Aerogear plugin, removed >>>>> and installed again the Ios platform, I compiled the program, but the >>>>> result didn't change: >>>>> >>>>> >>>>> XCode debugger: >>>>> >>>>> >>>>> >>>>> >>>>> *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: >>>>> {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} >>>>> * >>>>> >>>>> cordova plugin add org.jboss.aerogear.cordova.push >>>>> >>>>> Maybe you didn't uploaded it yet? >>>>> >>>>> Thanks >>>>> >>>>> M >>>>> >>>>> >>>>> On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: >>>>> >>>>>> Yes. That "trick" has to be used sometimes. That's a very annoying >>>>>> Cordova issue. Thanks. >>>>>> >>>>>> Enviado do meu iPhone >>>>>> >>>>>> No dia 18/03/2014, ?s 16:37, Sebastien Blanc >>>>>> escreveu: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >>>>>> >>>>>>> Thanks Erik. I know that; the total payload never surpasses 256 byes >>>>>>> and the av parameter (the notification itself) 107 characters. >>>>>>> >>>>>>> After the correction I just have the reinstall the plugin? >>>>>>> >>>>>> That should be enough but it has sometime failed for me , in this >>>>>> case you will need to do a : >>>>>> >>>>>> cordova platform remove ios >>>>>> cordova platform add ios >>>>>> >>>>>> >>>>>>> M >>>>>>> >>>>>>> Enviado do meu iPhone >>>>>>> >>>>>>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >>>>>>> escreveu: >>>>>>> >>>>>>> BTW Miguel I see that you are sending a lot of extras in the >>>>>>> message, be careful that Apple doesn?t allow the message to become to big >>>>>>> the max is 256 bytes. >>>>>>> >>>>>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit >>>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> PR submitted >>>>>>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>>>>> >>>>>>> On 18 Mar,2014, at 15:49 , Miguel Lemos >>>>>>> wrote: >>>>>>> >>>>>>> Fine, Erik! >>>>>>> >>>>>>> Nice to know it's easy to fix. >>>>>>> >>>>>>> A small issue, that caused - almost - everything to fail... >>>>>>> >>>>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>>>> >>>>>>> Miguel >>>>>>> >>>>>>> Enviado do meu iPhone >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140318/7955293f/attachment-0001.html From miguel21op at gmail.com Tue Mar 18 19:08:19 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Tue, 18 Mar 2014 23:08:19 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Message-ID: Now: if the app is not in the foreground, but it was not removed (still running), when a notification is sent and I press the status bar, the Safari debugger throws this error: SyntaxError: Unexpected number '0' and no window is opened. All I have in my code is: alert(e.alert); The string that arrives to the device is like this: *Msg: {"badge":"1","alert":"hlhlkhkl","payload": {"cp":"","cd":"","av":"hlhlkhkl","ul":"","ln":"","en":"598","at":"Aviso","rd":"","lt":"",},"foreground:"0"}* Hope it helps. On Tue, Mar 18, 2014 at 10:23 PM, Miguel Lemos wrote: > Not 100% yet. > > If the app is running in the foreground, now the Json array is formed in > a different way, and the alert window shows correctly and loads all the > paramaters: > > > > *2014-03-18 22:00:12.980 SmartDrifter[4011:60b] Msg: {"alert":"Ol?! > Benvindo aos Armaz?ns do Chiado","badge":"1","payload": > {"lt":"0.00000000000","cd":"","av":"Ol?! Benvindo aos Armaz?ns do > Chiado","ul":"http://metal-pr.net/c/?79 > ","ln":"0.00000000000","en":"598","at":"Aviso","cp":"79","rd":"0",},"foreground":"1"} > *But if the message arrives first to the status bar (meaning: the app is > not available), then nothing happens when I press the notification: the app > opens indeed, but no alert window shows. Unfortunately I could not trace > any errors, neither through the Safari debugger (the problem happens too > soon, maybe before the index.html is fully available), nor through Xcode. > But the problem has nothing to do with the previously faulty parameters > because an alert(e.alert) doesn't trigger nothing either... > > > On Tue, Mar 18, 2014 at 9:56 PM, Miguel Lemos wrote: > >> Too soon, unfortunately ! >> >> Isn't yet 100% perfect. There's still a problem if the app is running in >> the background. I must dig further to understand why it happens :-( >> >> >> On Tue, Mar 18, 2014 at 9:50 PM, Sebastien Blanc wrote: >> >>> Cool ! >>> Would be nice if you could add a comment here >>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 like >>> "+1 it's working" , assuming you have a github account. >>> >>> >>> >>> On Tue, Mar 18, 2014 at 10:46 PM, Miguel Lemos wrote: >>> >>>> Thanks Seb :-) >>>> >>>> I had already notice that and installed the new file "? la main". I't >>>> working ! >>>> >>>> >>>> On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: >>>> >>>>> Forget my previous post! Done ;-) >>>>> >>>>> I uploaded and installed directly the PushPugin.m to its location. I >>>>> didn't pay attention to what you wrote... >>>>> It's working OK now and there's no error. >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: >>>>> >>>>>> Erik, >>>>>> >>>>>> I just uninstalled and installed again the Aerogear plugin, removed >>>>>> and installed again the Ios platform, I compiled the program, but the >>>>>> result didn't change: >>>>>> >>>>>> >>>>>> XCode debugger: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: >>>>>> {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} >>>>>> * >>>>>> >>>>>> cordova plugin add org.jboss.aerogear.cordova.push >>>>>> >>>>>> Maybe you didn't uploaded it yet? >>>>>> >>>>>> Thanks >>>>>> >>>>>> M >>>>>> >>>>>> >>>>>> On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: >>>>>> >>>>>>> Yes. That "trick" has to be used sometimes. That's a very annoying >>>>>>> Cordova issue. Thanks. >>>>>>> >>>>>>> Enviado do meu iPhone >>>>>>> >>>>>>> No dia 18/03/2014, ?s 16:37, Sebastien Blanc >>>>>>> escreveu: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >>>>>>> >>>>>>>> Thanks Erik. I know that; the total payload never surpasses 256 >>>>>>>> byes and the av parameter (the notification itself) 107 characters. >>>>>>>> >>>>>>>> After the correction I just have the reinstall the plugin? >>>>>>>> >>>>>>> That should be enough but it has sometime failed for me , in this >>>>>>> case you will need to do a : >>>>>>> >>>>>>> cordova platform remove ios >>>>>>> cordova platform add ios >>>>>>> >>>>>>> >>>>>>>> M >>>>>>>> >>>>>>>> Enviado do meu iPhone >>>>>>>> >>>>>>>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >>>>>>>> escreveu: >>>>>>>> >>>>>>>> BTW Miguel I see that you are sending a lot of extras in the >>>>>>>> message, be careful that Apple doesn?t allow the message to become to big >>>>>>>> the max is 256 bytes. >>>>>>>> >>>>>>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> PR submitted >>>>>>>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>>>>>> >>>>>>>> On 18 Mar,2014, at 15:49 , Miguel Lemos >>>>>>>> wrote: >>>>>>>> >>>>>>>> Fine, Erik! >>>>>>>> >>>>>>>> Nice to know it's easy to fix. >>>>>>>> >>>>>>>> A small issue, that caused - almost - everything to fail... >>>>>>>> >>>>>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>>>>> >>>>>>>> Miguel >>>>>>>> >>>>>>>> Enviado do meu iPhone >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140318/b7af9b36/attachment.html From edewit at redhat.com Wed Mar 19 03:47:27 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 19 Mar 2014 08:47:27 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> Message-ID: <6AF0AA50-52D3-473C-BAFA-8F2D28D25F64@redhat.com> Yeah didn?t test all possibilities apparently, there is a ? missing on the foreground property. Fixed now. On 19 Mar,2014, at 0:08 , Miguel Lemos wrote: > Now: if the app is not in the foreground, but it was not removed (still running), when a notification is sent and I press the status bar, the Safari debugger throws this error: SyntaxError: Unexpected number '0' > and no window is opened. > > All I have in my code is: > > alert(e.alert); > > The string that arrives to the device is like this: > > Msg: {"badge":"1","alert":"hlhlkhkl","payload": {"cp":"","cd":"","av":"hlhlkhkl","ul":"","ln":"","en":"598","at":"Aviso","rd":"","lt":"",},"foreground:"0"} > > > > Hope it helps. > > > > On Tue, Mar 18, 2014 at 10:23 PM, Miguel Lemos wrote: > Not 100% yet. > > If the app is running in the foreground, now the Json array is formed in a different way, and the alert window shows correctly and loads all the paramaters: > > 2014-03-18 22:00:12.980 SmartDrifter[4011:60b] Msg: {"alert":"Ol?! Benvindo aos Armaz?ns do Chiado","badge":"1","payload": {"lt":"0.00000000000","cd":"","av":"Ol?! Benvindo aos Armaz?ns do Chiado","ul":"http://metal-pr.net/c/?79","ln":"0.00000000000","en":"598","at":"Aviso","cp":"79","rd":"0",},"foreground":"1"} > > But if the message arrives first to the status bar (meaning: the app is not available), then nothing happens when I press the notification: the app opens indeed, but no alert window shows. Unfortunately I could not trace any errors, neither through the Safari debugger (the problem happens too soon, maybe before the index.html is fully available), nor through Xcode. But the problem has nothing to do with the previously faulty parameters because an alert(e.alert) doesn't trigger nothing either... > > > > On Tue, Mar 18, 2014 at 9:56 PM, Miguel Lemos wrote: > Too soon, unfortunately ! > > Isn't yet 100% perfect. There's still a problem if the app is running in the background. I must dig further to understand why it happens :-( > > > On Tue, Mar 18, 2014 at 9:50 PM, Sebastien Blanc wrote: > Cool ! > Would be nice if you could add a comment here https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 like "+1 it's working" , assuming you have a github account. > > > > On Tue, Mar 18, 2014 at 10:46 PM, Miguel Lemos wrote: > Thanks Seb :-) > > I had already notice that and installed the new file "? la main". I't working ! > > > On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: > Forget my previous post! Done ;-) > > I uploaded and installed directly the PushPugin.m to its location. I didn't pay attention to what you wrote... > It's working OK now and there's no error. > > > > > On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: > Erik, > > I just uninstalled and installed again the Aerogear plugin, removed and installed again the Ios platform, I compiled the program, but the result didn't change: > > > XCode debugger: > > > 2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} > > > cordova plugin add org.jboss.aerogear.cordova.push > > Maybe you didn't uploaded it yet? > > Thanks > > M > > > > On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: > Yes. That "trick" has to be used sometimes. That's a very annoying Cordova issue. Thanks. > > Enviado do meu iPhone > > No dia 18/03/2014, ?s 16:37, Sebastien Blanc escreveu: > >> >> >> >> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >> Thanks Erik. I know that; the total payload never surpasses 256 byes and the av parameter (the notification itself) 107 characters. >> >> After the correction I just have the reinstall the plugin? >> That should be enough but it has sometime failed for me , in this case you will need to do a : >> >> cordova platform remove ios >> cordova platform add ios >> >> >> M >> >> Enviado do meu iPhone >> >> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit escreveu: >> >>> BTW Miguel I see that you are sending a lot of extras in the message, be careful that Apple doesn?t allow the message to become to big the max is 256 bytes. >>> >>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >>> >>>> >>>> PR submitted https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>> >>>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>>> >>>>> Fine, Erik! >>>>> >>>>> Nice to know it's easy to fix. >>>>> >>>>> A small issue, that caused - almost - everything to fail... >>>>> >>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>> >>>>> Miguel >>>>> >>>>> Enviado do meu iPhone >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/9538aed3/attachment-0001.html From miguel21op at gmail.com Wed Mar 19 05:28:20 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 09:28:20 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: <6AF0AA50-52D3-473C-BAFA-8F2D28D25F64@redhat.com> References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> <6AF0AA50-52D3-473C-BAFA-8F2D28D25F64@redhat.com> Message-ID: Yes, I see it now. I'll test it as soon as I can again. M Enviado do meu iPhone No dia 19/03/2014, ?s 07:47, Erik Jan de Wit escreveu: > Yeah didn?t test all possibilities apparently, there is a ? missing on the foreground property. Fixed now. > >> On 19 Mar,2014, at 0:08 , Miguel Lemos wrote: >> >> Now: if the app is not in the foreground, but it was not removed (still running), when a notification is sent and I press the status bar, the Safari debugger throws this error: SyntaxError: Unexpected number '0' >> and no window is opened. >> >> All I have in my code is: >> >> alert(e.alert); >> >> The string that arrives to the device is like this: >> >> Msg: {"badge":"1","alert":"hlhlkhkl","payload": {"cp":"","cd":"","av":"hlhlkhkl","ul":"","ln":"","en":"598","at":"Aviso","rd":"","lt":"",},"foreground:"0"} >> >> >> >> Hope it helps. >> >> >> >>> On Tue, Mar 18, 2014 at 10:23 PM, Miguel Lemos wrote: >>> Not 100% yet. >>> >>> If the app is running in the foreground, now the Json array is formed in a different way, and the alert window shows correctly and loads all the paramaters: >>> >>> 2014-03-18 22:00:12.980 SmartDrifter[4011:60b] Msg: {"alert":"Ol?! Benvindo aos Armaz?ns do Chiado","badge":"1","payload": {"lt":"0.00000000000","cd":"","av":"Ol?! Benvindo aos Armaz?ns do Chiado","ul":"http://metal-pr.net/c/?79","ln":"0.00000000000","en":"598","at":"Aviso","cp":"79","rd":"0",},"foreground":"1"} >>> >>> But if the message arrives first to the status bar (meaning: the app is not available), then nothing happens when I press the notification: the app opens indeed, but no alert window shows. Unfortunately I could not trace any errors, neither through the Safari debugger (the problem happens too soon, maybe before the index.html is fully available), nor through Xcode. But the problem has nothing to do with the previously faulty parameters because an alert(e.alert) doesn't trigger nothing either... >>> >>> >>> >>>> On Tue, Mar 18, 2014 at 9:56 PM, Miguel Lemos wrote: >>>> Too soon, unfortunately ! >>>> >>>> Isn't yet 100% perfect. There's still a problem if the app is running in the background. I must dig further to understand why it happens :-( >>>> >>>> >>>>> On Tue, Mar 18, 2014 at 9:50 PM, Sebastien Blanc wrote: >>>>> Cool ! >>>>> Would be nice if you could add a comment here https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 like "+1 it's working" , assuming you have a github account. >>>>> >>>>> >>>>> >>>>>> On Tue, Mar 18, 2014 at 10:46 PM, Miguel Lemos wrote: >>>>>> Thanks Seb :-) >>>>>> >>>>>> I had already notice that and installed the new file "? la main". I't working ! >>>>>> >>>>>> >>>>>>> On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: >>>>>>> Forget my previous post! Done ;-) >>>>>>> >>>>>>> I uploaded and installed directly the PushPugin.m to its location. I didn't pay attention to what you wrote... >>>>>>> It's working OK now and there's no error. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: >>>>>>>> Erik, >>>>>>>> >>>>>>>> I just uninstalled and installed again the Aerogear plugin, removed and installed again the Ios platform, I compiled the program, but the result didn't change: >>>>>>>> >>>>>>>> >>>>>>>> XCode debugger: >>>>>>>> >>>>>>>> >>>>>>>> 2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} >>>>>>>> >>>>>>>> >>>>>>>> cordova plugin add org.jboss.aerogear.cordova.push >>>>>>>> >>>>>>>> Maybe you didn't uploaded it yet? >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> M >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: >>>>>>>>> Yes. That "trick" has to be used sometimes. That's a very annoying Cordova issue. Thanks. >>>>>>>>> >>>>>>>>> Enviado do meu iPhone >>>>>>>>> >>>>>>>>> No dia 18/03/2014, ?s 16:37, Sebastien Blanc escreveu: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >>>>>>>>>>> Thanks Erik. I know that; the total payload never surpasses 256 byes and the av parameter (the notification itself) 107 characters. >>>>>>>>>>> >>>>>>>>>>> After the correction I just have the reinstall the plugin? >>>>>>>>>> That should be enough but it has sometime failed for me , in this case you will need to do a : >>>>>>>>>> >>>>>>>>>> cordova platform remove ios >>>>>>>>>> cordova platform add ios >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> M >>>>>>>>>>> >>>>>>>>>>> Enviado do meu iPhone >>>>>>>>>>> >>>>>>>>>>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit escreveu: >>>>>>>>>>> >>>>>>>>>>>> BTW Miguel I see that you are sending a lot of extras in the message, be careful that Apple doesn?t allow the message to become to big the max is 256 bytes. >>>>>>>>>>>> >>>>>>>>>>>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> PR submitted https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>>>>>>>>>>> >>>>>>>>>>>>>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Fine, Erik! >>>>>>>>>>>>>> >>>>>>>>>>>>>> Nice to know it's easy to fix. >>>>>>>>>>>>>> >>>>>>>>>>>>>> A small issue, that caused - almost - everything to fail... >>>>>>>>>>>>>> >>>>>>>>>>>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>>>>>>>>>>> >>>>>>>>>>>>>> Miguel >>>>>>>>>>>>>> >>>>>>>>>>>>>> Enviado do meu iPhone >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > 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/20140319/a75bb7c2/attachment.html From corinnekrych at gmail.com Wed Mar 19 06:05:29 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 19 Mar 2014 11:05:29 +0100 Subject: [aerogear-dev] Keycloak adapters for iOS and Android In-Reply-To: References: <805376679.1293116.1395139456827.JavaMail.zimbra@redhat.com> <1413826749.1296233.1395140014298.JavaMail.zimbra@redhat.com> Message-ID: Hello Stian KC adapter is planned for our iOS 1.6 release (end of June) as pointed out by abstract, it?s in our roadmap. Once 1.5 is out (end of this week), we?ll start 1.6 and work this adapter. As for Android, we have our ios-cookbook[1], we can find a sample that fit close to your sample app. No worries. We also have a JIRA ticket to track progress[2]. ++ Corinne [1] https://github.com/aerogear/aerogear-ios-cookbook [2] https://issues.jboss.org/browse/AGIOS-178 On 18 Mar 2014, at 12:29, Daniel Passos wrote: > Hi Stian, > > Answers inline > > On Tue, Mar 18, 2014 at 7:53 AM, Stian Thorgersen wrote: > We're aiming to release beta1 of Keycloak in beginning of May. It would be great to have basic iOS and Android examples added to our demo. With that in mind I have a couple of question: > > * Any chance anyone from the AeroGear team could contribute an iOS example? Something that works together with our current demo would be great, login with Keycloak and fetch/display customers list from the server is sufficient (same features as customer-portal and customer-portal-js in our demo). It would also be nice to have a small section on how to use it added to our documentation. > * Do you have an ETA when Android adapter will be ready? > > Yes, we have already started working on it. We'll postpone our 1.4 release (scheduled for mid March to mid April ) to include KC adapter see last meeting notes[1] > > * Same as for iOS, any chance to get some help with an Android example and documentation? > > Of course. Ping me when you need. Btw, we'll add it on our cookbook app[2] > > Cheers, > Stian > > [1] http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-17-13.47.html > [2] https://github.com/aerogear/aerogear-android-cookbook > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Wed Mar 19 06:30:50 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 19 Mar 2014 11:30:50 +0100 Subject: [aerogear-dev] It is out (was: Re: Staging of UnifiedPush Server 0.10.1) Message-ID: Done! Get it from http://aerogear.org/push/ Also, Sebi wrote a nice blog on the UI related improvements: http://blog-sblanc.rhcloud.com/?p=49 (OpenShift cartridge has been updated; when you create a new app, you will get this version of UPS) -Matthias On Tue, Mar 11, 2014 at 3:36 PM, Matthias Wessendorf wrote: > Hello, > > for the upcoming release we have a few, but important, tickets solved: > https://issues.jboss.org/browse/AGPUSH/fixforversion/12324188 > > > Before finishing the release, let's see if there are issues w/ the server, > hence I have staged the WAR file on my private webspace: > > > > http://people.apache.org/~matzew/aerogear-staging/org/jboss/aerogear/unifiedpush/unifiedpush-server/0.10.1/ > > > If they aren't any objections or remarks I will release the bits to > bintray on Friday morning > > > Greetings, > Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/03806ae6/attachment-0001.html From daniel.bevenius at gmail.com Wed Mar 19 06:35:02 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Wed, 19 Mar 2014 11:35:02 +0100 Subject: [aerogear-dev] SimplePush Server 0.10.0 released Message-ID: Hi! We have just release AeroGear SimplePush Server 0.10.0. While there are no really exciting new features in this release [1], it is the first one we have release to Maven Central [2]. SimplePush Server version 0.10.0 is also available on OpenShift [3] in combination with AeroGear UnifiedPush Server. More information about the servers can be found at http://aerogear.org. [1] https://issues.jboss.org/browse/AGSMPLPUSH-42?filter=12319749 [2] http://search.maven.org/#search%7Cga%7C1%7Csimplepush [3] https://www.openshift.com/quickstarts/aerogear-push-0x -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/1d8a0607/attachment.html From matzew at apache.org Wed Mar 19 06:44:29 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 19 Mar 2014 11:44:29 +0100 Subject: [aerogear-dev] AeroGear Push releases Message-ID: Today we are releasing a few push related artifacts - SimplePush Server 0.10.0 - UnifiedPush Server 0.10.1 - AeroGear's Push Cartridge for OpenShift 0.10.0 While the SimplePush Server mainly contains small fixes and improvements (see Dan Bevenius' email), the UnifiedPush Server comes with great updates to the Admin UI: - composing and sending push messages is now possible from within the AdminUI - code snippets for device registrations are generated on the different variant overviews In his blog, Sebi Blanc is talking about the improvements. OpenShift Last but not least, we have also updated our OpenShift cartridge! When you now create a new AeroGear Push instance you are getting the above server releases automatically: - AeroGear SimplePush Server 0.10.0 - AeroGear UnifiedPush Server 0.10.1 Have fun and let us know what you think, or how and where we can improve! -- 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/20140319/ff251dc4/attachment.html From bruno at abstractj.org Wed Mar 19 09:01:10 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 19 Mar 2014 10:01:10 -0300 Subject: [aerogear-dev] aerogear.org revamp: team work In-Reply-To: <5CEC844E-310B-4DB7-AC89-43E5CC57EA18@gmail.com> References: <5CEC844E-310B-4DB7-AC89-43E5CC57EA18@gmail.com> Message-ID: Hi Corinne, I was giving a look at sass branch and I?m really concerned due to the number of conflicts with ?master?. I think for the sanity of everyone, is healthy to regularly rebase that branch against master like Corinne mentioned before. I tried rebase, but due to my poor sass skills, I?m afraid of mess it up. What I did? git checkout sass git rebase origin/master -- abstractj On February 24, 2014 at 11:09:59 AM, Corinne Krych (corinnekrych at gmail.com) wrote: > Hello All, > > With aerogear web site roadmap [1] proposal we can start working together toward a new > website. We already have a common branch (named sass - maybe not the best name) [2] where > we can work together. It?s important to rebase/keep this branch up to date. > > Here is how we could work together efficiently: > - take JIRA for 0.1.0 release, > - branch from sass branch, do you work > - send PR againt sass. > - usual PR review > - then PR can be merged into sass. > > If a ticket requires changes in page documentation like splitting a markdown page into > several pages or move to asciidoc format etc? we should do this JIRA initial in master > branch, send a PRL, get the PR merged and get the changes in sass branch. This way we can > keep history and let the documentation evolves without fear for merging it into new site > revamp branch. > > Thought? #agreed? > > ++ > Corinne > [1] http://aerogear.org/docs/planning/roadmaps/AeroGearWebSite/ > [2 https://github.com/aerogear/aerogear.org/tree/sass > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > From daniel at passos.me Wed Mar 19 09:12:34 2014 From: daniel at passos.me (Daniel Passos) Date: Wed, 19 Mar 2014 10:12:34 -0300 Subject: [aerogear-dev] Postpone agdroid 1.4 Message-ID: Hi folks, Summers and I were thinking about postponing AeroGear Android 1.4 release schedule from mid March to mid April to include oAuth and KC integration. Last months we were focused on sync, updating/reviewing docs and example apps. We have fixed some bugs, but have no new features. So, wdyt? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/eeccb2cb/attachment.html From matzew at apache.org Wed Mar 19 09:17:16 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 19 Mar 2014 14:17:16 +0100 Subject: [aerogear-dev] Postpone agdroid 1.4 In-Reply-To: References: Message-ID: sure, why not. If you feel no need to release now, that's perfectly valid On Wed, Mar 19, 2014 at 2:12 PM, Daniel Passos wrote: > Hi folks, > > Summers and I were thinking about postponing AeroGear Android 1.4 release > schedule from mid March to mid April to include oAuth and KC integration. > > Last months we were focused on sync, updating/reviewing docs and example > apps. We have fixed some bugs, but have no new features. > > So, wdyt? > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140319/de4c9076/attachment.html From daniel at passos.me Wed Mar 19 09:18:37 2014 From: daniel at passos.me (Daniel Passos) Date: Wed, 19 Mar 2014 10:18:37 -0300 Subject: [aerogear-dev] Still supporting pagination? Message-ID: Hi all After ag-controller was deprecated, are we still supporting pipe pagination? Do we have some alternative(s) to use it in the server side? -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/ac24895a/attachment.html From bruno at abstractj.org Wed Mar 19 09:19:16 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 19 Mar 2014 10:19:16 -0300 Subject: [aerogear-dev] Postpone agdroid 1.4 In-Reply-To: References: Message-ID: I trust your judgment, so +1 -- abstractj On March 19, 2014 at 10:13:04 AM, Daniel Passos (daniel at passos.me) wrote: > > Hi folks, > > Summers and I were thinking about postponing AeroGear Android > 1.4 release schedule from mid March to mid April to include oAuth > and KC integration. > > Last months we were focused on sync, updating/reviewing docs > and example apps. We have fixed some bugs, but have no new features. > > So, wdyt? From qmx at qmx.me Wed Mar 19 09:22:10 2014 From: qmx at qmx.me (Douglas Campos) Date: Wed, 19 Mar 2014 10:22:10 -0300 Subject: [aerogear-dev] Postpone agdroid 1.4 In-Reply-To: References: Message-ID: <20140319132210.GO13960@rohan.local> On Wed, Mar 19, 2014 at 10:12:34AM -0300, Daniel Passos wrote: > Hi folks, > > Summers and I were thinking about postponing AeroGear Android 1.4 release > schedule from mid March to mid April to include oAuth and KC integration. > > Last months we were focused on sync, updating/reviewing docs and example > apps. We have fixed some bugs, but have no new features. > > So, wdyt? +1 -- qmx From daniel.bevenius at gmail.com Wed Mar 19 09:26:22 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Wed, 19 Mar 2014 14:26:22 +0100 Subject: [aerogear-dev] Postpone agdroid 1.4 In-Reply-To: <20140319132210.GO13960@rohan.local> References: <20140319132210.GO13960@rohan.local> Message-ID: Sounds good to me On 19 March 2014 14:22, Douglas Campos wrote: > On Wed, Mar 19, 2014 at 10:12:34AM -0300, Daniel Passos wrote: > > Hi folks, > > > > Summers and I were thinking about postponing AeroGear Android 1.4 release > > schedule from mid March to mid April to include oAuth and KC integration. > > > > Last months we were focused on sync, updating/reviewing docs and example > > apps. We have fixed some bugs, but have no new features. > > > > So, wdyt? > > +1 > > > -- > 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/20140319/9deb9724/attachment.html From matzew at apache.org Wed Mar 19 09:28:36 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 19 Mar 2014 14:28:36 +0100 Subject: [aerogear-dev] Still supporting pagination? In-Reply-To: References: Message-ID: that's a good question; client-side pagination pretty much relies on whatever the server offers; that said, on iOS, I know the current pagination works with different server APIs, like Github's GIST APIs: https://github.com/aerogear/aerogear-ios-integration/blob/master/AeroGear-iOS-Integration/AeroGear-iOS-IntegrationTests/AGPagingWebLinking_GitHubSpec.m (they neatly support the Web-Linking RFC (http://tools.ietf.org/html/rfc5988 )) So, in theory, it should work w/ any server-side impl. that also follows this particular standard On Wed, Mar 19, 2014 at 2:18 PM, Daniel Passos wrote: > Hi all > > After ag-controller was deprecated, are we still supporting pipe > pagination? Do we have some alternative(s) to use it in the server side? > > -- 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/20140319/44d47af8/attachment.html From bruno at abstractj.org Wed Mar 19 09:28:47 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 19 Mar 2014 10:28:47 -0300 Subject: [aerogear-dev] Still supporting pagination? In-Reply-To: References: Message-ID: Hi Passos, it can be done with JAX-RS as far as I can tell. Probably is just the matter of file Jiras -- abstractj On March 19, 2014 at 10:19:08 AM, Daniel Passos (daniel at passos.me) wrote: > > Hi all > > After ag-controller was deprecated, are we still supporting > pipe pagination? Do we have some alternative(s) to use it in the > server side? > > -- Passos From matzew at apache.org Wed Mar 19 09:29:00 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 19 Mar 2014 14:29:00 +0100 Subject: [aerogear-dev] Still supporting pagination? In-Reply-To: References: Message-ID: On Wed, Mar 19, 2014 at 2:28 PM, Matthias Wessendorf wrote: > that's a good question; > > client-side pagination pretty much relies on whatever the server offers; > > that said, on iOS, I know the current pagination works with different > server APIs, like Github's GIST APIs: > > https://github.com/aerogear/aerogear-ios-integration/blob/master/AeroGear-iOS-Integration/AeroGear-iOS-IntegrationTests/AGPagingWebLinking_GitHubSpec.m > > (they neatly support the Web-Linking RFC ( > http://tools.ietf.org/html/rfc5988)) > > > So, in theory, it should work w/ any server-side impl. that also follows > this particular standard > so, yes, I think we are still having interest in supporting pagination > > > > > On Wed, Mar 19, 2014 at 2:18 PM, Daniel Passos wrote: > >> Hi all >> >> After ag-controller was deprecated, are we still supporting pipe >> pagination? Do we have some alternative(s) to use it in the server side? >> >> -- 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 > -- 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/20140319/792d4b87/attachment.html From daniel at passos.me Wed Mar 19 09:29:52 2014 From: daniel at passos.me (Daniel Passos) Date: Wed, 19 Mar 2014 10:29:52 -0300 Subject: [aerogear-dev] Kill getting started docs Message-ID: Hi folks, For android we have some docs called 'Getting Started Guides' to help community to import ag in your favorite IDE. I never agreed to these documents and I don't want to keep updating it. If the developer will work with our libraries and already uses her favorite IDE, she probably already knows how to do that. So, I'd like to kill these docs. wdyt? -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/c462a7f7/attachment.html From lholmqui at redhat.com Wed Mar 19 09:31:23 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Wed, 19 Mar 2014 09:31:23 -0400 Subject: [aerogear-dev] Still supporting pagination? In-Reply-To: References: Message-ID: On Mar 19, 2014, at 9:28 AM, Matthias Wessendorf wrote: > that's a good question; > > client-side pagination pretty much relies on whatever the server offers; > > that said, on iOS, I know the current pagination works with different server APIs, like Github's GIST APIs: > https://github.com/aerogear/aerogear-ios-integration/blob/master/AeroGear-iOS-Integration/AeroGear-iOS-IntegrationTests/AGPagingWebLinking_GitHubSpec.m > > (they neatly support the Web-Linking RFC (http://tools.ietf.org/html/rfc5988)) > > > So, in theory, it should work w/ any server-side impl. that also follows this particular standard same theory for the js lib > > > > > On Wed, Mar 19, 2014 at 2:18 PM, Daniel Passos wrote: > Hi all > > After ag-controller was deprecated, are we still supporting pipe pagination? Do we have some alternative(s) to use it in the server side? > > -- 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/20140319/f1ddb9c8/attachment-0001.html From matzew at apache.org Wed Mar 19 09:35:02 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 19 Mar 2014 14:35:02 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > Hi folks, > > For android we have some docs called 'Getting Started Guides' to help > community to import ag in your favorite IDE. I never agreed to these > documents and I don't want to keep updating it. > > If the developer will work with our libraries and already uses her > favorite IDE, she probably already knows how to do that. > > So, I'd like to kill these docs. wdyt? > +1000 > > -- 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/20140319/dcbcc225/attachment.html From matzew at apache.org Wed Mar 19 09:35:59 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 19 Mar 2014 14:35:59 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: too fast :-) +1000 from a Android developer view; Not sure if that's really true for our targetted customers. Java EE guys, new to android, might appreciate that kind of getting started help On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > >> Hi folks, >> >> For android we have some docs called 'Getting Started Guides' to help >> community to import ag in your favorite IDE. I never agreed to these >> documents and I don't want to keep updating it. >> >> If the developer will work with our libraries and already uses her >> favorite IDE, she probably already knows how to do that. >> >> So, I'd like to kill these docs. wdyt? >> > > +1000 > > >> >> -- 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 > -- 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/20140319/ee4c3fb1/attachment.html From scm.blanc at gmail.com Wed Mar 19 09:36:04 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 19 Mar 2014 14:36:04 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: Finish them !! On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > >> Hi folks, >> >> For android we have some docs called 'Getting Started Guides' to help >> community to import ag in your favorite IDE. I never agreed to these >> documents and I don't want to keep updating it. >> >> If the developer will work with our libraries and already uses her >> favorite IDE, she probably already knows how to do that. >> >> So, I'd like to kill these docs. wdyt? >> > > +1000 > > >> >> -- 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/20140319/d58b2153/attachment.html From miguel21op at gmail.com Wed Mar 19 09:43:24 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 13:43:24 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> <6AF0AA50-52D3-473C-BAFA-8F2D28D25F64@redhat.com> Message-ID: Erik, I think you didn't update the code... On Wed, Mar 19, 2014 at 9:28 AM, Miguel Lemos wrote: > Yes, I see it now. I'll test it as soon as I can again. > > M > > Enviado do meu iPhone > > No dia 19/03/2014, ?s 07:47, Erik Jan de Wit escreveu: > > Yeah didn?t test all possibilities apparently, there is a ? missing on the > foreground property. Fixed now. > > On 19 Mar,2014, at 0:08 , Miguel Lemos wrote: > > Now: if the app is not in the foreground, but it was not removed (still > running), when a notification is sent and I press the status bar, the > Safari debugger throws this error: SyntaxError: Unexpected number '0' > and no window is opened. > > All I have in my code is: > > alert(e.alert); > > The string that arrives to the device is like this: > > > > *Msg: {"badge":"1","alert":"hlhlkhkl","payload": > {"cp":"","cd":"","av":"hlhlkhkl","ul":"","ln":"","en":"598","at":"Aviso","rd":"","lt":"",},"foreground:"0"} > * > > Hope it helps. > > > On Tue, Mar 18, 2014 at 10:23 PM, Miguel Lemos wrote: > >> Not 100% yet. >> >> If the app is running in the foreground, now the Json array is formed in >> a different way, and the alert window shows correctly and loads all the >> paramaters: >> >> >> >> *2014-03-18 22:00:12.980 SmartDrifter[4011:60b] Msg: {"alert":"Ol?! >> Benvindo aos Armaz?ns do Chiado","badge":"1","payload": >> {"lt":"0.00000000000","cd":"","av":"Ol?! Benvindo aos Armaz?ns do >> Chiado","ul":"http://metal-pr.net/c/?79 >> ","ln":"0.00000000000","en":"598","at":"Aviso","cp":"79","rd":"0",},"foreground":"1"} >> *But if the message arrives first to the status bar (meaning: the app is >> not available), then nothing happens when I press the notification: the app >> opens indeed, but no alert window shows. Unfortunately I could not trace >> any errors, neither through the Safari debugger (the problem happens too >> soon, maybe before the index.html is fully available), nor through Xcode. >> But the problem has nothing to do with the previously faulty parameters >> because an alert(e.alert) doesn't trigger nothing either... >> >> >> On Tue, Mar 18, 2014 at 9:56 PM, Miguel Lemos wrote: >> >>> Too soon, unfortunately ! >>> >>> Isn't yet 100% perfect. There's still a problem if the app is running in >>> the background. I must dig further to understand why it happens :-( >>> >>> >>> On Tue, Mar 18, 2014 at 9:50 PM, Sebastien Blanc wrote: >>> >>>> Cool ! >>>> Would be nice if you could add a comment here >>>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 like >>>> "+1 it's working" , assuming you have a github account. >>>> >>>> >>>> >>>> On Tue, Mar 18, 2014 at 10:46 PM, Miguel Lemos wrote: >>>> >>>>> Thanks Seb :-) >>>>> >>>>> I had already notice that and installed the new file "? la main". I't >>>>> working ! >>>>> >>>>> >>>>> On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: >>>>> >>>>>> Forget my previous post! Done ;-) >>>>>> >>>>>> I uploaded and installed directly the PushPugin.m to its location. I >>>>>> didn't pay attention to what you wrote... >>>>>> It's working OK now and there's no error. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: >>>>>> >>>>>>> Erik, >>>>>>> >>>>>>> I just uninstalled and installed again the Aerogear plugin, removed >>>>>>> and installed again the Ios platform, I compiled the program, but the >>>>>>> result didn't change: >>>>>>> >>>>>>> >>>>>>> XCode debugger: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: >>>>>>> {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} >>>>>>> * >>>>>>> >>>>>>> cordova plugin add org.jboss.aerogear.cordova.push >>>>>>> >>>>>>> Maybe you didn't uploaded it yet? >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> M >>>>>>> >>>>>>> >>>>>>> On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: >>>>>>> >>>>>>>> Yes. That "trick" has to be used sometimes. That's a very annoying >>>>>>>> Cordova issue. Thanks. >>>>>>>> >>>>>>>> Enviado do meu iPhone >>>>>>>> >>>>>>>> No dia 18/03/2014, ?s 16:37, Sebastien Blanc >>>>>>>> escreveu: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos >>>>>>> > wrote: >>>>>>>> >>>>>>>>> Thanks Erik. I know that; the total payload never surpasses 256 >>>>>>>>> byes and the av parameter (the notification itself) 107 characters. >>>>>>>>> >>>>>>>>> After the correction I just have the reinstall the plugin? >>>>>>>>> >>>>>>>> That should be enough but it has sometime failed for me , in this >>>>>>>> case you will need to do a : >>>>>>>> >>>>>>>> cordova platform remove ios >>>>>>>> cordova platform add ios >>>>>>>> >>>>>>>> >>>>>>>>> M >>>>>>>>> >>>>>>>>> Enviado do meu iPhone >>>>>>>>> >>>>>>>>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >>>>>>>>> escreveu: >>>>>>>>> >>>>>>>>> BTW Miguel I see that you are sending a lot of extras in the >>>>>>>>> message, be careful that Apple doesn?t allow the message to become to big >>>>>>>>> the max is 256 bytes. >>>>>>>>> >>>>>>>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> PR submitted >>>>>>>>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>>>>>>> >>>>>>>>> On 18 Mar,2014, at 15:49 , Miguel Lemos >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Fine, Erik! >>>>>>>>> >>>>>>>>> Nice to know it's easy to fix. >>>>>>>>> >>>>>>>>> A small issue, that caused - almost - everything to fail... >>>>>>>>> >>>>>>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>>>>>> >>>>>>>>> Miguel >>>>>>>>> >>>>>>>>> Enviado do meu iPhone >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >> > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > 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/20140319/c6816540/attachment-0001.html From bsutter at redhat.com Wed Mar 19 09:45:09 2014 From: bsutter at redhat.com (Burr Sutter) Date: Wed, 19 Mar 2014 09:45:09 -0400 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: Do you mean: http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ and to some degree http://aerogear.org/docs/guides/GetStartedAndroid/ The only one that aligns with our efforts is the Eclipse one - as in JBDS (or eclipse + JBoss Tools). On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > Finish them !! > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > Hi folks, > > For android we have some docs called 'Getting Started Guides' to help community to import ag in your favorite IDE. I never agreed to these documents and I don't want to keep updating it. > > If the developer will work with our libraries and already uses her favorite IDE, she probably already knows how to do that. > > So, I'd like to kill these docs. wdyt? > > +1000 > > > -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/2eca4c9b/attachment.html From edewit at redhat.com Wed Mar 19 09:47:35 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 19 Mar 2014 14:47:35 +0100 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> <6AF0AA50-52D3-473C-BAFA-8F2D28D25F64@redhat.com> Message-ID: I did https://github.com/edewit/aerogear-pushplugin-cordova/commit/1df1adcaa76aa0a740d6e9c02ec2b02b3b0b990a checkout my branch: git checkout -b edewit-payload-missing master git pull git at github.com:edewit/aerogear-pushplugin-cordova.git payload-missing On 19 Mar,2014, at 14:43 , Miguel Lemos wrote: > Erik, > > I think you didn't update the code... > > > On Wed, Mar 19, 2014 at 9:28 AM, Miguel Lemos wrote: > Yes, I see it now. I'll test it as soon as I can again. > > M > > Enviado do meu iPhone > > No dia 19/03/2014, ?s 07:47, Erik Jan de Wit escreveu: > >> Yeah didn?t test all possibilities apparently, there is a ? missing on the foreground property. Fixed now. >> >> On 19 Mar,2014, at 0:08 , Miguel Lemos wrote: >> >>> Now: if the app is not in the foreground, but it was not removed (still running), when a notification is sent and I press the status bar, the Safari debugger throws this error: SyntaxError: Unexpected number '0' >>> and no window is opened. >>> >>> All I have in my code is: >>> >>> alert(e.alert); >>> >>> The string that arrives to the device is like this: >>> >>> Msg: {"badge":"1","alert":"hlhlkhkl","payload": {"cp":"","cd":"","av":"hlhlkhkl","ul":"","ln":"","en":"598","at":"Aviso","rd":"","lt":"",},"foreground:"0"} >>> >>> >>> >>> Hope it helps. >>> >>> >>> >>> On Tue, Mar 18, 2014 at 10:23 PM, Miguel Lemos wrote: >>> Not 100% yet. >>> >>> If the app is running in the foreground, now the Json array is formed in a different way, and the alert window shows correctly and loads all the paramaters: >>> >>> 2014-03-18 22:00:12.980 SmartDrifter[4011:60b] Msg: {"alert":"Ol?! Benvindo aos Armaz?ns do Chiado","badge":"1","payload": {"lt":"0.00000000000","cd":"","av":"Ol?! Benvindo aos Armaz?ns do Chiado","ul":"http://metal-pr.net/c/?79","ln":"0.00000000000","en":"598","at":"Aviso","cp":"79","rd":"0",},"foreground":"1"} >>> >>> But if the message arrives first to the status bar (meaning: the app is not available), then nothing happens when I press the notification: the app opens indeed, but no alert window shows. Unfortunately I could not trace any errors, neither through the Safari debugger (the problem happens too soon, maybe before the index.html is fully available), nor through Xcode. But the problem has nothing to do with the previously faulty parameters because an alert(e.alert) doesn't trigger nothing either... >>> >>> >>> >>> On Tue, Mar 18, 2014 at 9:56 PM, Miguel Lemos wrote: >>> Too soon, unfortunately ! >>> >>> Isn't yet 100% perfect. There's still a problem if the app is running in the background. I must dig further to understand why it happens :-( >>> >>> >>> On Tue, Mar 18, 2014 at 9:50 PM, Sebastien Blanc wrote: >>> Cool ! >>> Would be nice if you could add a comment here https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 like "+1 it's working" , assuming you have a github account. >>> >>> >>> >>> On Tue, Mar 18, 2014 at 10:46 PM, Miguel Lemos wrote: >>> Thanks Seb :-) >>> >>> I had already notice that and installed the new file "? la main". I't working ! >>> >>> >>> On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: >>> Forget my previous post! Done ;-) >>> >>> I uploaded and installed directly the PushPugin.m to its location. I didn't pay attention to what you wrote... >>> It's working OK now and there's no error. >>> >>> >>> >>> >>> On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: >>> Erik, >>> >>> I just uninstalled and installed again the Aerogear plugin, removed and installed again the Ios platform, I compiled the program, but the result didn't change: >>> >>> >>> XCode debugger: >>> >>> >>> 2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} >>> >>> >>> cordova plugin add org.jboss.aerogear.cordova.push >>> >>> Maybe you didn't uploaded it yet? >>> >>> Thanks >>> >>> M >>> >>> >>> >>> On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos wrote: >>> Yes. That "trick" has to be used sometimes. That's a very annoying Cordova issue. Thanks. >>> >>> Enviado do meu iPhone >>> >>> No dia 18/03/2014, ?s 16:37, Sebastien Blanc escreveu: >>> >>>> >>>> >>>> >>>> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos wrote: >>>> Thanks Erik. I know that; the total payload never surpasses 256 byes and the av parameter (the notification itself) 107 characters. >>>> >>>> After the correction I just have the reinstall the plugin? >>>> That should be enough but it has sometime failed for me , in this case you will need to do a : >>>> >>>> cordova platform remove ios >>>> cordova platform add ios >>>> >>>> >>>> M >>>> >>>> Enviado do meu iPhone >>>> >>>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit escreveu: >>>> >>>>> BTW Miguel I see that you are sending a lot of extras in the message, be careful that Apple doesn?t allow the message to become to big the max is 256 bytes. >>>>> >>>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit wrote: >>>>> >>>>>> >>>>>> PR submitted https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>>>> >>>>>> On 18 Mar,2014, at 15:49 , Miguel Lemos wrote: >>>>>> >>>>>>> Fine, Erik! >>>>>>> >>>>>>> Nice to know it's easy to fix. >>>>>>> >>>>>>> A small issue, that caused - almost - everything to fail... >>>>>>> >>>>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>>>> >>>>>>> Miguel >>>>>>> >>>>>>> Enviado do meu iPhone >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140319/6033e7c6/attachment-0001.html From corinnekrych at gmail.com Wed Mar 19 10:01:21 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Wed, 19 Mar 2014 15:01:21 +0100 Subject: [aerogear-dev] aerogear.org revamp: team work In-Reply-To: References: <5CEC844E-310B-4DB7-AC89-43E5CC57EA18@gmail.com> Message-ID: Let me rebase. ++ Corinne On 19 Mar 2014, at 14:01, Bruno Oliveira wrote: > Hi Corinne, I was giving a look at sass branch and I?m really concerned due to the number of conflicts with ?master?. > > I think for the sanity of everyone, is healthy to regularly rebase that branch against master like Corinne mentioned before. I tried rebase, but due to my poor sass skills, I?m afraid of mess it up. > > What I did? > > git checkout sass > git rebase origin/master > > > -- > abstractj > > On February 24, 2014 at 11:09:59 AM, Corinne Krych (corinnekrych at gmail.com) wrote: >> Hello All, >> >> With aerogear web site roadmap [1] proposal we can start working together toward a new >> website. We already have a common branch (named sass - maybe not the best name) [2] where >> we can work together. It?s important to rebase/keep this branch up to date. >> >> Here is how we could work together efficiently: >> - take JIRA for 0.1.0 release, >> - branch from sass branch, do you work >> - send PR againt sass. >> - usual PR review >> - then PR can be merged into sass. >> >> If a ticket requires changes in page documentation like splitting a markdown page into >> several pages or move to asciidoc format etc? we should do this JIRA initial in master >> branch, send a PRL, get the PR merged and get the changes in sass branch. This way we can >> keep history and let the documentation evolves without fear for merging it into new site >> revamp branch. >> >> Thought? #agreed? >> >> ++ >> Corinne >> [1] http://aerogear.org/docs/planning/roadmaps/AeroGearWebSite/ >> [2 https://github.com/aerogear/aerogear.org/tree/sass >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > From miguel21op at gmail.com Wed Mar 19 10:08:56 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 14:08:56 +0000 Subject: [aerogear-dev] Cordova and iOS new issue In-Reply-To: References: <724639B0-7694-4A63-AD7E-30C8BBC7F056@gmail.com> <51630639-2215-4A00-9655-A0DBC03AB851@redhat.com> <900F8FF6-1025-4BCB-8EC9-6EDD1D5952B3@gmail.com> <2074AB33-EC61-4B28-A1CD-0ADAD5785296@redhat.com> <8F6FEB68-6D1E-405B-85B8-9F0F46BC703C@redhat.com> <554D7D8B-7730-4C35-BB3D-45027CFE952A@gmail.com> <6AF0AA50-52D3-473C-BAFA-8F2D28D25F64@redhat.com> Message-ID: OK. I just pasted the PushPlugin.m but I picked the yesterday's version. I already tested it and now it's working correctly, thanks. Thanks On Wed, Mar 19, 2014 at 1:47 PM, Erik Jan de Wit wrote: > I did > https://github.com/edewit/aerogear-pushplugin-cordova/commit/1df1adcaa76aa0a740d6e9c02ec2b02b3b0b990a > > > checkout my branch: > > git checkout -b edewit-payload-missing master > git pull git at github.com:edewit/aerogear-pushplugin-cordova.git payload-missing > > > > On 19 Mar,2014, at 14:43 , Miguel Lemos wrote: > > Erik, > > I think you didn't update the code... > > > On Wed, Mar 19, 2014 at 9:28 AM, Miguel Lemos wrote: > >> Yes, I see it now. I'll test it as soon as I can again. >> >> M >> >> Enviado do meu iPhone >> >> No dia 19/03/2014, ?s 07:47, Erik Jan de Wit >> escreveu: >> >> Yeah didn?t test all possibilities apparently, there is a ? missing on >> the foreground property. Fixed now. >> >> On 19 Mar,2014, at 0:08 , Miguel Lemos wrote: >> >> Now: if the app is not in the foreground, but it was not removed (still >> running), when a notification is sent and I press the status bar, the >> Safari debugger throws this error: SyntaxError: Unexpected number '0' >> and no window is opened. >> >> All I have in my code is: >> >> alert(e.alert); >> >> The string that arrives to the device is like this: >> >> >> >> *Msg: {"badge":"1","alert":"hlhlkhkl","payload": >> {"cp":"","cd":"","av":"hlhlkhkl","ul":"","ln":"","en":"598","at":"Aviso","rd":"","lt":"",},"foreground:"0"} >> * >> >> Hope it helps. >> >> >> On Tue, Mar 18, 2014 at 10:23 PM, Miguel Lemos wrote: >> >>> Not 100% yet. >>> >>> If the app is running in the foreground, now the Json array is formed >>> in a different way, and the alert window shows correctly and loads all the >>> paramaters: >>> >>> >>> >>> *2014-03-18 22:00:12.980 SmartDrifter[4011:60b] Msg: {"alert":"Ol?! >>> Benvindo aos Armaz?ns do Chiado","badge":"1","payload": >>> {"lt":"0.00000000000","cd":"","av":"Ol?! Benvindo aos Armaz?ns do >>> Chiado","ul":"http://metal-pr.net/c/?79 >>> ","ln":"0.00000000000","en":"598","at":"Aviso","cp":"79","rd":"0",},"foreground":"1"} >>> *But if the message arrives first to the status bar (meaning: the app >>> is not available), then nothing happens when I press the notification: the >>> app opens indeed, but no alert window shows. Unfortunately I could not >>> trace any errors, neither through the Safari debugger (the problem happens >>> too soon, maybe before the index.html is fully available), nor through >>> Xcode. But the problem has nothing to do with the previously faulty >>> parameters because an alert(e.alert) doesn't trigger nothing either... >>> >>> >>> On Tue, Mar 18, 2014 at 9:56 PM, Miguel Lemos wrote: >>> >>>> Too soon, unfortunately ! >>>> >>>> Isn't yet 100% perfect. There's still a problem if the app is running >>>> in the background. I must dig further to understand why it happens :-( >>>> >>>> >>>> On Tue, Mar 18, 2014 at 9:50 PM, Sebastien Blanc wrote: >>>> >>>>> Cool ! >>>>> Would be nice if you could add a comment here >>>>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 like >>>>> "+1 it's working" , assuming you have a github account. >>>>> >>>>> >>>>> >>>>> On Tue, Mar 18, 2014 at 10:46 PM, Miguel Lemos wrote: >>>>> >>>>>> Thanks Seb :-) >>>>>> >>>>>> I had already notice that and installed the new file "? la main". I't >>>>>> working ! >>>>>> >>>>>> >>>>>> On Tue, Mar 18, 2014 at 9:45 PM, Miguel Lemos wrote: >>>>>> >>>>>>> Forget my previous post! Done ;-) >>>>>>> >>>>>>> I uploaded and installed directly the PushPugin.m to its location. I >>>>>>> didn't pay attention to what you wrote... >>>>>>> It's working OK now and there's no error. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Mar 18, 2014 at 9:30 PM, Miguel Lemos wrote: >>>>>>> >>>>>>>> Erik, >>>>>>>> >>>>>>>> I just uninstalled and installed again the Aerogear plugin, removed >>>>>>>> and installed again the Ios platform, I compiled the program, but the >>>>>>>> result didn't change: >>>>>>>> >>>>>>>> >>>>>>>> XCode debugger: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> *2014-03-18 21:24:11.983 SmartDrifter[3892:60b] Msg: >>>>>>>> {en:'598',cd:'',badge:'1',alert:'Teste',av:'Teste',ul:'',ln:'',at:'Aviso',cp:'',rd:'',lt:'',foreground:'1',} >>>>>>>> * >>>>>>>> >>>>>>>> cordova plugin add org.jboss.aerogear.cordova.push >>>>>>>> >>>>>>>> Maybe you didn't uploaded it yet? >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> M >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Mar 18, 2014 at 4:41 PM, Miguel Lemos >>>>>>> > wrote: >>>>>>>> >>>>>>>>> Yes. That "trick" has to be used sometimes. That's a very annoying >>>>>>>>> Cordova issue. Thanks. >>>>>>>>> >>>>>>>>> Enviado do meu iPhone >>>>>>>>> >>>>>>>>> No dia 18/03/2014, ?s 16:37, Sebastien Blanc >>>>>>>>> escreveu: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Tue, Mar 18, 2014 at 5:34 PM, Miguel Lemos < >>>>>>>>> miguel21op at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Thanks Erik. I know that; the total payload never surpasses 256 >>>>>>>>>> byes and the av parameter (the notification itself) 107 characters. >>>>>>>>>> >>>>>>>>>> After the correction I just have the reinstall the plugin? >>>>>>>>>> >>>>>>>>> That should be enough but it has sometime failed for me , in this >>>>>>>>> case you will need to do a : >>>>>>>>> >>>>>>>>> cordova platform remove ios >>>>>>>>> cordova platform add ios >>>>>>>>> >>>>>>>>> >>>>>>>>>> M >>>>>>>>>> >>>>>>>>>> Enviado do meu iPhone >>>>>>>>>> >>>>>>>>>> No dia 18/03/2014, ?s 16:24, Erik Jan de Wit >>>>>>>>>> escreveu: >>>>>>>>>> >>>>>>>>>> BTW Miguel I see that you are sending a lot of extras in the >>>>>>>>>> message, be careful that Apple doesn?t allow the message to become to big >>>>>>>>>> the max is 256 bytes. >>>>>>>>>> >>>>>>>>>> On 18 Mar,2014, at 17:08 , Erik Jan de Wit >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> PR submitted >>>>>>>>>> https://github.com/aerogear/aerogear-pushplugin-cordova/pull/20 >>>>>>>>>> >>>>>>>>>> On 18 Mar,2014, at 15:49 , Miguel Lemos >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Fine, Erik! >>>>>>>>>> >>>>>>>>>> Nice to know it's easy to fix. >>>>>>>>>> >>>>>>>>>> A small issue, that caused - almost - everything to fail... >>>>>>>>>> >>>>>>>>>> I'm glad I could help in the role of "bug buster" ;-) >>>>>>>>>> >>>>>>>>>> Miguel >>>>>>>>>> >>>>>>>>>> Enviado do meu iPhone >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140319/d98e564d/attachment-0001.html From miguel21op at gmail.com Wed Mar 19 11:00:53 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 15:00:53 +0000 Subject: [aerogear-dev] Cordova push notifications enhancement request Message-ID: It would be very useful that, besides a sound, we could have a vibrate option when the notification arrives to the tray. Many people have the phone in their pockets or simply don't want to listen a sound. A vibrate function could be very handy. Thanks Miguel PS - Meanwhile I still don't understand what's this for: if (e.coldstart) { } else { } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/87877d59/attachment.html From daniel at passos.me Wed Mar 19 12:27:22 2014 From: daniel at passos.me (Daniel Passos) Date: Wed, 19 Mar 2014 13:27:22 -0300 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: I mean http://aerogear.org/docs/guides/GetStartedAndroid/ http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ -- Passos On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > Do you mean: > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > and to some degree > http://aerogear.org/docs/guides/GetStartedAndroid/ > > The only one that aligns with our efforts is the Eclipse one - as in JBDS > (or eclipse + JBoss Tools). > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > Finish them !! > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > >> >> >> >> On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: >> >>> Hi folks, >>> >>> For android we have some docs called 'Getting Started Guides' to help >>> community to import ag in your favorite IDE. I never agreed to these >>> documents and I don't want to keep updating it. >>> >>> If the developer will work with our libraries and already uses her >>> favorite IDE, she probably already knows how to do that. >>> >>> So, I'd like to kill these docs. wdyt? >>> >> >> +1000 >> >> >>> >>> -- 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 > > > > _______________________________________________ > 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/20140319/a20c49aa/attachment.html From edewit at redhat.com Wed Mar 19 12:43:07 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 19 Mar 2014 17:43:07 +0100 Subject: [aerogear-dev] Cordova push notifications enhancement request In-Reply-To: References: Message-ID: Hi Miguel, You could install a cordova plugin for that https://github.com/apache/cordova-plugin-vibration or org.apache.cordova.vibration then put this in the onNotification handler: navigator.notification.vibrate(time) > > if (e.coldstart) { > > } else { > > } This is android specific, it?s set to true when the application was not active not even in the background and the system started the app to respond to the notification. Hope that helps, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/37a14432/attachment.html From miguel21op at gmail.com Wed Mar 19 12:50:26 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 16:50:26 +0000 Subject: [aerogear-dev] Sound issue Cordova iOS and notation Message-ID: Hi The sound event when the notification arrives doesn't seem to work (at least on iPhone; Android not tested yet). And yes: the sound plugin is installed and working just fine. Besides, I don't understand quite well the way you build the event. Example given by you for Android: var my_media = new Media("/android_asset/www/" + e.sound); ..What sound? I can have several sounds on a given folder... I think a better - and more trivial - approach would be something like this (just an opinion...): if (e.sound) { if (device.platform == "Android") { media = new Media("/android_asset/www/beep.wav"); } else if (device.platform == "iOS") { media = new Media("beep.wav"); // root directory } media.play(); } Thanks guys :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/97224bb7/attachment.html From miguel21op at gmail.com Wed Mar 19 12:55:35 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 16:55:35 +0000 Subject: [aerogear-dev] Cordova push notifications enhancement request In-Reply-To: References: Message-ID: Hi Erik, how are you? I already use that plugin (vibration) but it doesn't seem to work under the onNotification handler (I had already tested it before I send the previous message). Anyway: it should be triggered only when the notification arrives at the device, otherwise it's useless I think. Thank you On Wed, Mar 19, 2014 at 4:43 PM, Erik Jan de Wit wrote: > Hi Miguel, > > You could install a cordova plugin for that > https://github.com/apache/cordova-plugin-vibration or > org.apache.cordova.vibration then put this in the onNotification handler: > > navigator.notification.vibrate(time) > > > if (e.coldstart) { > > } else { > > } > > > This is android specific, it?s set to true when the application was not > active not even in the background and the system started the app to respond > to the notification. > > Hope that helps, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/690275e3/attachment-0001.html From stian at redhat.com Wed Mar 19 12:59:30 2014 From: stian at redhat.com (Stian Thorgersen) Date: Wed, 19 Mar 2014 12:59:30 -0400 (EDT) Subject: [aerogear-dev] Keycloak adapters for iOS and Android In-Reply-To: References: <805376679.1293116.1395139456827.JavaMail.zimbra@redhat.com> <1413826749.1296233.1395140014298.JavaMail.zimbra@redhat.com> Message-ID: <290003441.2331181.1395248370528.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Daniel Passos" > To: "AeroGear Developer Mailing List" > Sent: Tuesday, 18 March, 2014 11:29:28 AM > Subject: Re: [aerogear-dev] Keycloak adapters for iOS and Android > > Hi Stian, > > Answers inline > > On Tue, Mar 18, 2014 at 7:53 AM, Stian Thorgersen < stian at redhat.com > wrote: > > > We're aiming to release beta1 of Keycloak in beginning of May. It would be > great to have basic iOS and Android examples added to our demo. With that in > mind I have a couple of question: > > * Any chance anyone from the AeroGear team could contribute an iOS example? > Something that works together with our current demo would be great, login > with Keycloak and fetch/display customers list from the server is sufficient > (same features as customer-portal and customer-portal-js in our demo). It > would also be nice to have a small section on how to use it added to our > documentation. > * Do you have an ETA when Android adapter will be ready? > > Yes, we have already started working on it. We'll postpone our 1.4 release > (scheduled for mid March to mid April ) to include KC adapter see last > meeting notes[1] That's great news, please let me know when you have something working :) > > > * Same as for iOS, any chance to get some help with an Android example and > documentation? > > Of course. Ping me when you need. Btw, we'll add it on our cookbook app[2] We can talk about this when you have it in your cookbook app. Not sure if we should just direct to AeroGear docs and examples, or include something in our own. > > > Cheers, > Stian > > [1] > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-17-13.47.html > [2] https://github.com/aerogear/aerogear-android-cookbook > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From stian at redhat.com Wed Mar 19 13:01:24 2014 From: stian at redhat.com (Stian Thorgersen) Date: Wed, 19 Mar 2014 13:01:24 -0400 (EDT) Subject: [aerogear-dev] [keycloak-dev] Keycloak adapters for iOS and Android In-Reply-To: References: <805376679.1293116.1395139456827.JavaMail.zimbra@redhat.com> <1413826749.1296233.1395140014298.JavaMail.zimbra@redhat.com> Message-ID: <299704101.2334992.1395248484319.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Corinne Krych" > To: "AeroGear Developer Mailing List" , keycloak-dev at lists.jboss.org > Sent: Wednesday, 19 March, 2014 10:05:29 AM > Subject: Re: [keycloak-dev] [aerogear-dev] Keycloak adapters for iOS and Android > > Hello Stian > > KC adapter is planned for our iOS 1.6 release (end of June) as pointed out by > abstract, it?s in our roadmap. Once 1.5 is out (end of this week), we?ll > start 1.6 and work this adapter. Great, please keep me updated on the progress and if there's any issues you have with Keycloak :) > > As for Android, we have our ios-cookbook[1], we can find a sample that fit > close to your sample app. No worries. We also have a JIRA ticket to track > progress[2]. > ++ > Corinne > [1] https://github.com/aerogear/aerogear-ios-cookbook > [2] https://issues.jboss.org/browse/AGIOS-178 > > On 18 Mar 2014, at 12:29, Daniel Passos wrote: > > > Hi Stian, > > > > Answers inline > > > > On Tue, Mar 18, 2014 at 7:53 AM, Stian Thorgersen wrote: > > We're aiming to release beta1 of Keycloak in beginning of May. It would be > > great to have basic iOS and Android examples added to our demo. With that > > in mind I have a couple of question: > > > > * Any chance anyone from the AeroGear team could contribute an iOS example? > > Something that works together with our current demo would be great, login > > with Keycloak and fetch/display customers list from the server is > > sufficient (same features as customer-portal and customer-portal-js in our > > demo). It would also be nice to have a small section on how to use it > > added to our documentation. > > * Do you have an ETA when Android adapter will be ready? > > > > Yes, we have already started working on it. We'll postpone our 1.4 release > > (scheduled for mid March to mid April ) to include KC adapter see last > > meeting notes[1] > > > > * Same as for iOS, any chance to get some help with an Android example and > > documentation? > > > > Of course. Ping me when you need. Btw, we'll add it on our cookbook app[2] > > > > Cheers, > > Stian > > > > [1] > > http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-17-13.47.html > > [2] https://github.com/aerogear/aerogear-android-cookbook > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev > From miguel21op at gmail.com Wed Mar 19 13:09:04 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 17:09:04 +0000 Subject: [aerogear-dev] Cordova push notifications enhancement request In-Reply-To: References: Message-ID: Wait! The damn plugin (vibrate) used to work; now I tested it outside the notification routine and I noticed it just stopped working. I'll try to reinstall it... On Wed, Mar 19, 2014 at 4:55 PM, Miguel Lemos wrote: > Hi Erik, how are you? > > I already use that plugin (vibration) but it doesn't seem to work under > the onNotification handler (I had already tested it before I send the > previous message). > > Anyway: it should be triggered only when the notification arrives at the > device, otherwise it's useless I think. > > Thank you > > > On Wed, Mar 19, 2014 at 4:43 PM, Erik Jan de Wit wrote: > >> Hi Miguel, >> >> You could install a cordova plugin for that >> https://github.com/apache/cordova-plugin-vibration or >> org.apache.cordova.vibration then put this in the onNotification handler: >> >> navigator.notification.vibrate(time) >> >> >> if (e.coldstart) { >> >> } else { >> >> } >> >> >> This is android specific, it?s set to true when the application was not >> active not even in the background and the system started the app to respond >> to the notification. >> >> Hope that helps, >> Erik Jan >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/6a0f2403/attachment.html From edewit at redhat.com Wed Mar 19 13:00:29 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 19 Mar 2014 18:00:29 +0100 Subject: [aerogear-dev] Cordova push notifications enhancement request In-Reply-To: References: Message-ID: <2DBC25CD-33E3-4863-B9D3-255F15119A4D@redhat.com> On 19 Mar,2014, at 17:55 , Miguel Lemos wrote: > Hi Erik, how are you? > > I already use that plugin (vibration) but it doesn't seem to work under the onNotification handler (I had already tested it before I send the previous message). Strange, anyway this might be something a user can enable as well. My android phone vibrates and plays a sound on any notification. From marti1003 at hotmail.com Wed Mar 19 13:30:46 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Wed, 19 Mar 2014 12:30:46 -0500 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: , , , , , , , , , , , Message-ID: Hi http://aerogear.org/docs/specs/aerogear-server-push/ http://aerogear.org/push/ the idea is to implement Amazon Push, BlackBerry or Windows for aerogear-server-push From: marti1003 at hotmail.com To: aerogear-dev at lists.jboss.org Date: Tue, 18 Mar 2014 14:26:01 -0500 Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server About my experience: for mobile I am using cordova(phonegap) for android this include Jquery mobile and dev firerfox apps with backbonejs backend java play framework http://www.playframework.com/ (hibernate) and dynamic jasper I remember was made an app with j2me and servlets communication via sockets I will finish a project where connects two systems one of then is Oracle PeopleSoft and and Adryan Cosapi Data(http://www.cosapidata.com.pe/Adryan.asp) via webservices. here you are my github account https://github.com/marti1125 Regards Willy Date: Tue, 18 Mar 2014 18:27:28 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server On Tue, Mar 18, 2014 at 6:16 PM, Willy Martin Aguirre Rodriguez wrote: Yes! I really like to work with mobile technology awesome! Regarding the requested technologies (e.g. Amazon Push, BlackBerry or Windows), do you have experience in that area (e.g. development of apps and/or push APIs for them) ? Greetings,Matthias Date: Tue, 18 Mar 2014 17:48:11 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hello Willy, the AeroGear UnifiedPush server supports push notifications over a unified API for the following platforms: * Google Cloud Messaging (Android and Chrome)* APNs (iOS) ==> Safari is on the works (by Luke) * SimplePush (Firefox OS and polyfil for any browser) The goal of the suggested project would be adding support for other push networks:* Amazon Push* Windows Phone/Mobile * Black Berry Besides that we are happy to get support for other push networks as well. The main work would be the integration of those networks (server-side, admin UI, documentation and examples) Does that sound interesting to you ? Greetings,Matthias On Tue, Mar 18, 2014 at 5:15 PM, Willy Martin Aguirre Rodriguez wrote: ups sorry is this https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Support_new_Push_Networks_on_the_UnifiedPush_Server Date: Tue, 18 Mar 2014 16:59:08 +0100 From: scm.blanc at gmail.com To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hi,I think you should post that to the RHQ mailing list since it's a RHQ related project https://fedorahosted.org/mailman/listinfo/rhq-users Seb On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez wrote: Hi! I made some firefox os apps and I Java dev I really interesting in https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ Could you tell me more about this project? and how to make my proposal for this project? Regards Willy _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/f51e1532/attachment-0001.html From miguel21op at gmail.com Wed Mar 19 13:36:56 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 17:36:56 +0000 Subject: [aerogear-dev] Cordova push notifications enhancement request In-Reply-To: <2DBC25CD-33E3-4863-B9D3-255F15119A4D@redhat.com> References: <2DBC25CD-33E3-4863-B9D3-255F15119A4D@redhat.com> Message-ID: I don't know why but the vibrate all of a sudden stop functioning (iOS). I'll try to find out what's up... Anyway: the only interest on vibrating and / or playing a sound is when the notification arrives to the phone, not after the user has already seen it. On Wed, Mar 19, 2014 at 5:00 PM, Erik Jan de Wit wrote: > > On 19 Mar,2014, at 17:55 , Miguel Lemos wrote: > > > Hi Erik, how are you? > > > > I already use that plugin (vibration) but it doesn't seem to work under > the onNotification handler (I had already tested it before I send the > previous message). > > Strange, anyway this might be something a user can enable as well. My > android phone vibrates and plays a sound on any notification. > > > _______________________________________________ > 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/20140319/1904ef69/attachment.html From scm.blanc at gmail.com Wed Mar 19 13:40:51 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 19 Mar 2014 18:40:51 +0100 Subject: [aerogear-dev] Sound issue Cordova iOS and notation In-Reply-To: References: Message-ID: On Wed, Mar 19, 2014 at 5:50 PM, Miguel Lemos wrote: > Hi > > The sound event when the notification arrives doesn't seem to work (at > least on iPhone; Android not tested yet). > > And yes: the sound plugin is installed and working just fine. > > Besides, I don't understand quite well the way you build the event. > Example given by you for Android: > > var my_media = new Media("/android_asset/www/" + e.sound); > > ..What sound? I can have several sounds on a given folder... > I haven't play too much with sound but e.sound is supposed to contain the filename of your sound file (like beep.wav / sirene.wav ...) > > I think a better - and more trivial - approach would be something like > this (just an opinion...): > > if (e.sound) { > if (device.platform == "Android") { > media = new Media("/android_asset/www/beep.wav"); > } else if (device.platform == "iOS") { > media = new Media("beep.wav"); // root directory > } > media.play(); > } > > > Thanks guys :-) > > _______________________________________________ > 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/20140319/820ddb02/attachment.html From bsutter at redhat.com Wed Mar 19 13:44:39 2014 From: bsutter at redhat.com (Burr Sutter) Date: Wed, 19 Mar 2014 13:44:39 -0400 Subject: [aerogear-dev] Sound issue Cordova iOS and notation In-Reply-To: References: Message-ID: Are there no "out-of-the-box" sounds for Android? I thought the iOS sounds were not driven by the indiviual app. On Mar 19, 2014, at 1:40 PM, Sebastien Blanc wrote: > > > > On Wed, Mar 19, 2014 at 5:50 PM, Miguel Lemos wrote: > Hi > > The sound event when the notification arrives doesn't seem to work (at least on iPhone; Android not tested yet). > > And yes: the sound plugin is installed and working just fine. > > Besides, I don't understand quite well the way you build the event. Example given by you for Android: > > var my_media = new Media("/android_asset/www/" + e.sound); > > ..What sound? I can have several sounds on a given folder... > I haven't play too much with sound but e.sound is supposed to contain the filename of your sound file (like beep.wav / sirene.wav ...) > > I think a better - and more trivial - approach would be something like this (just an opinion...): > > if (e.sound) { > if (device.platform == "Android") { > media = new Media("/android_asset/www/beep.wav"); > } else if (device.platform == "iOS") { > media = new Media("beep.wav"); // root directory > } > media.play(); > } > > > Thanks guys :-) > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140319/010cae1f/attachment.html From miguel21op at gmail.com Wed Mar 19 13:58:25 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 17:58:25 +0000 Subject: [aerogear-dev] Sound issue Cordova iOS and notation In-Reply-To: References: Message-ID: Yes, the sounds can be defined by the app. > In the iOS case (with Cordova) the only way to make the sound play that I know is to put the file in the project's root and pointing to it. I tested and it works. Not that i use it very much, but sometimes it's needed... > The function you use to play a sound along with the notification is: if (e.sound) { var media = new Media("/android_asset/www/" + e.sound); media.play(); } I didn't manage to make it work. Anyway I think it would be more "normal" a function like the one I sent. But, as I told before, the vibration and / or sound play only makes sense when the notification arrives in the notification area, not before I pressed on it. Mind for instance a geofenced notification:the user must see it at the moment it arrives, and not 30 minutes later. In this case the vibration or sound are very important. On Wed, Mar 19, 2014 at 5:44 PM, Burr Sutter wrote: > Are there no "out-of-the-box" sounds for Android? > > I thought the iOS sounds were not driven by the indiviual app. > > > On Mar 19, 2014, at 1:40 PM, Sebastien Blanc wrote: > > > > > On Wed, Mar 19, 2014 at 5:50 PM, Miguel Lemos > wrote: > >> Hi >> >> The sound event when the notification arrives doesn't seem to work (at >> least on iPhone; Android not tested yet). >> >> And yes: the sound plugin is installed and working just fine. >> >> Besides, I don't understand quite well the way you build the event. >> Example given by you for Android: >> >> var my_media = new Media("/android_asset/www/" + e.sound); >> >> ..What sound? I can have several sounds on a given folder... >> > I haven't play too much with sound but e.sound is supposed to contain the > filename of your sound file (like beep.wav / sirene.wav ...) > >> >> I think a better - and more trivial - approach would be something like >> this (just an opinion...): >> >> if (e.sound) { >> if (device.platform == "Android") { >> media = new Media("/android_asset/www/beep.wav"); >> } else if (device.platform == "iOS") { >> media = new Media("beep.wav"); // root directory >> } >> media.play(); >> } >> >> >> Thanks guys :-) >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140319/ac696167/attachment-0001.html From miguel21op at gmail.com Wed Mar 19 13:59:36 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 17:59:36 +0000 Subject: [aerogear-dev] Sound issue Cordova iOS and notation In-Reply-To: References: Message-ID: * not after I pressed... On Wed, Mar 19, 2014 at 5:58 PM, Miguel Lemos wrote: > Yes, the sounds can be defined by the app. > > > In the iOS case (with Cordova) the only way to make the sound play that > I know is to put the file in the project's root and pointing to it. I > tested and it works. Not that i use it very much, but sometimes it's > needed... > > > The function you use to play a sound along with the notification is: > > if (e.sound) { var media = new Media("/android_asset/www/" + e.sound); > media.play(); } > > I didn't manage to make it work. Anyway I think it would be more "normal" > a function like the one I sent. But, as I told before, the vibration and / > or sound play only makes sense when the notification arrives in the > notification area, not before I pressed on it. > > Mind for instance a geofenced notification:the user must see it at the > moment it arrives, and not 30 minutes later. In this case the vibration or > sound are very important. > > > On Wed, Mar 19, 2014 at 5:44 PM, Burr Sutter wrote: > >> Are there no "out-of-the-box" sounds for Android? >> >> I thought the iOS sounds were not driven by the indiviual app. >> >> >> On Mar 19, 2014, at 1:40 PM, Sebastien Blanc wrote: >> >> >> >> >> On Wed, Mar 19, 2014 at 5:50 PM, Miguel Lemos >> wrote: >> >>> Hi >>> >>> The sound event when the notification arrives doesn't seem to work (at >>> least on iPhone; Android not tested yet). >>> >>> And yes: the sound plugin is installed and working just fine. >>> >>> Besides, I don't understand quite well the way you build the event. >>> Example given by you for Android: >>> >>> var my_media = new Media("/android_asset/www/" + e.sound); >>> >>> ..What sound? I can have several sounds on a given folder... >>> >> I haven't play too much with sound but e.sound is supposed to contain the >> filename of your sound file (like beep.wav / sirene.wav ...) >> >>> >>> I think a better - and more trivial - approach would be something like >>> this (just an opinion...): >>> >>> if (e.sound) { >>> if (device.platform == "Android") { >>> media = new Media("/android_asset/www/beep.wav"); >>> } else if (device.platform == "iOS") { >>> media = new Media("beep.wav"); // root directory >>> } >>> media.play(); >>> } >>> >>> >>> Thanks guys :-) >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140319/5284d7db/attachment.html From lholmqui at redhat.com Wed Mar 19 15:32:45 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Wed, 19 Mar 2014 15:32:45 -0400 Subject: [aerogear-dev] AeroGear.JS 1.4.0 release Message-ID: Hello Devs, we recently released the 1.4.0 version of the AeroGear.js lib. Checkout the blog post for more info http://blog.lholmquist.org/aerogear-js-1-4-0-release/ a big shout out to Tolis for his work on the tests and stuff Keep it real, -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/f74e30dd/attachment.html From miguel21op at gmail.com Wed Mar 19 17:45:13 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Wed, 19 Mar 2014 21:45:13 +0000 Subject: [aerogear-dev] Sound issue Cordova iOS and notation In-Reply-To: References: Message-ID: In Android the notification triggers the sound, vibrate, etc. But indeed the problem is that this should happen (or not...), as I said, when it arrives at the notification tray. On Wed, Mar 19, 2014 at 5:59 PM, Miguel Lemos wrote: > * not after I pressed... > > > On Wed, Mar 19, 2014 at 5:58 PM, Miguel Lemos wrote: > >> Yes, the sounds can be defined by the app. >> >> > In the iOS case (with Cordova) the only way to make the sound play that >> I know is to put the file in the project's root and pointing to it. I >> tested and it works. Not that i use it very much, but sometimes it's >> needed... >> >> > The function you use to play a sound along with the notification is: >> >> if (e.sound) { var media = new Media("/android_asset/www/" + e.sound); >> media.play(); } >> >> I didn't manage to make it work. Anyway I think it would be more "normal" >> a function like the one I sent. But, as I told before, the vibration and / >> or sound play only makes sense when the notification arrives in the >> notification area, not before I pressed on it. >> >> Mind for instance a geofenced notification:the user must see it at the >> moment it arrives, and not 30 minutes later. In this case the vibration or >> sound are very important. >> >> >> On Wed, Mar 19, 2014 at 5:44 PM, Burr Sutter wrote: >> >>> Are there no "out-of-the-box" sounds for Android? >>> >>> I thought the iOS sounds were not driven by the indiviual app. >>> >>> >>> On Mar 19, 2014, at 1:40 PM, Sebastien Blanc >>> wrote: >>> >>> >>> >>> >>> On Wed, Mar 19, 2014 at 5:50 PM, Miguel Lemos >>> wrote: >>> >>>> Hi >>>> >>>> The sound event when the notification arrives doesn't seem to work (at >>>> least on iPhone; Android not tested yet). >>>> >>>> And yes: the sound plugin is installed and working just fine. >>>> >>>> Besides, I don't understand quite well the way you build the event. >>>> Example given by you for Android: >>>> >>>> var my_media = new Media("/android_asset/www/" + e.sound); >>>> >>>> ..What sound? I can have several sounds on a given folder... >>>> >>> I haven't play too much with sound but e.sound is supposed to contain >>> the filename of your sound file (like beep.wav / sirene.wav ...) >>> >>>> >>>> I think a better - and more trivial - approach would be something like >>>> this (just an opinion...): >>>> >>>> if (e.sound) { >>>> if (device.platform == "Android") { >>>> media = new Media("/android_asset/www/beep.wav"); >>>> } else if (device.platform == "iOS") { >>>> media = new Media("beep.wav"); // root directory >>>> } >>>> media.play(); >>>> } >>>> >>>> >>>> Thanks guys :-) >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.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/20140319/0bd04e7d/attachment-0001.html From matzew at apache.org Wed Mar 19 18:51:19 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 19 Mar 2014 23:51:19 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: If we don't want to offer help for those that are new (to Android), let's get rid of it. Perhaps, we can link to better, more up-to-date, introductions; if really needed -Matthias On Wednesday, March 19, 2014, Daniel Passos wrote: > I mean > > http://aerogear.org/docs/guides/GetStartedAndroid/ > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > -- Passos > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > Do you mean: > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > and to some degree > http://aerogear.org/docs/guides/GetStartedAndroid/ > > The only one that aligns with our efforts is the Eclipse one - as in JBDS > (or eclipse + JBoss Tools). > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > Finish them !! > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > Hi folks, > > For android we have some docs called 'Getting Started Guides' to help > community to import ag in your favorite IDE. I never agreed to these > documents and I don't want to keep updating it. > > If the developer will work with our libraries and already uses her > favorite IDE, she probably already knows how to do that. > > So, I'd like to kill these docs. wdyt? > > > +1000 > > > > -- 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 > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lis > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/6df3ffea/attachment.html From bruno at abstractj.org Wed Mar 19 19:25:38 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Wed, 19 Mar 2014 16:25:38 -0700 (PDT) Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: <1395271538172.ae4b66c7@Nodemailer> I guess that was a bad sentence, we are here to help anyone interested in OSS. My understanding about Passos' suggestion, is because there are several resources on the internet to newcomers learn about Android. Duplicate it would be too much. ? abstractj On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > If we don't want to offer help for those that are new (to Android), let's > get rid of it. > Perhaps, we can link to better, more up-to-date, introductions; if really > needed > -Matthias > On Wednesday, March 19, 2014, Daniel Passos wrote: >> I mean >> >> http://aerogear.org/docs/guides/GetStartedAndroid/ >> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >> >> -- Passos >> >> >> On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: >> >> Do you mean: >> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >> >> and to some degree >> http://aerogear.org/docs/guides/GetStartedAndroid/ >> >> The only one that aligns with our efforts is the Eclipse one - as in JBDS >> (or eclipse + JBoss Tools). >> >> On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: >> >> Finish them !! >> >> >> On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: >> >> >> >> >> On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: >> >> Hi folks, >> >> For android we have some docs called 'Getting Started Guides' to help >> community to import ag in your favorite IDE. I never agreed to these >> documents and I don't want to keep updating it. >> >> If the developer will work with our libraries and already uses her >> favorite IDE, she probably already knows how to do that. >> >> So, I'd like to kill these docs. wdyt? >> >> >> +1000 >> >> >> >> -- 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 >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lis >> >> > -- > Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/e3268851/attachment.html From lholmqui at redhat.com Wed Mar 19 22:26:16 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Wed, 19 Mar 2014 22:26:16 -0400 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: <1395271538172.ae4b66c7@Nodemailer> References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: <7D0E990D-561E-432F-B4C5-5E5809B5AFE1@redhat.com> i know as a JS dev, i have no clue how to setup IntelliJ or other IDE's, so that walkthrough was nice with the pictures On Mar 19, 2014, at 7:25 PM, Bruno Oliveira wrote: > I guess that was a bad sentence, we are here to help anyone interested in OSS. My understanding about Passos' suggestion, is because there are several resources on the internet to newcomers learn about Android. > > Duplicate it would be too much. > ? > abstractj > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > If we don't want to offer help for those that are new (to Android), let's get rid of it. > > > Perhaps, we can link to better, more up-to-date, introductions; if really needed > > -Matthias > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > I mean > > http://aerogear.org/docs/guides/GetStartedAndroid/ > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > -- Passos > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > Do you mean: > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > and to some degree > http://aerogear.org/docs/guides/GetStartedAndroid/ > > The only one that aligns with our efforts is the Eclipse one - as in JBDS (or eclipse + JBoss Tools). > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > >> Finish them !! >> >> >> On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: >> >> >> >> On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: >> Hi folks, >> >> For android we have some docs called 'Getting Started Guides' to help community to import ag in your favorite IDE. I never agreed to these documents and I don't want to keep updating it. >> >> If the developer will work with our libraries and already uses her favorite IDE, she probably already knows how to do that. >> >> So, I'd like to kill these docs. wdyt? >> >> +1000 >> >> >> -- 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lis > > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140319/ea34a667/attachment-0001.html From bruno at abstractj.org Thu Mar 20 00:14:48 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 20 Mar 2014 01:14:48 -0300 Subject: [aerogear-dev] AeroGear Crypto 0.1.3 Staged Message-ID: Good morning peeps, the project was staged under the following profile:?https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2889/ It has fixes for Android platform. If you want to test it, try: -?https://github.com/aerogear/aerogear-android/pull/141 -?https://github.com/aerogear/aerogear-android-integration-tests/pull/26 I?m planning to release it on Friday, so if you find any critical issues, let me know. -- abstractj From matzew at apache.org Thu Mar 20 01:43:26 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 06:43:26 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: <7D0E990D-561E-432F-B4C5-5E5809B5AFE1@redhat.com> References: <1395271538172.ae4b66c7@Nodemailer> <7D0E990D-561E-432F-B4C5-5E5809B5AFE1@redhat.com> Message-ID: Even as a Java weenie, I struggled w/ setup of Android (see our ml archive). I found our Eclipse guide helpful; But yeah, we can point/link to "better" resources, if that works. Perhaps, we just need to show the piece whats missing for our own library support (e.g Google Play libs, etc). That way we don't need to help on "here is Eclipse/IDEA; here is how you install it;..." -Matthias On Thursday, March 20, 2014, Lucas Holmquist wrote: > i know as a JS dev, i have no clue how to setup IntelliJ or other IDE's, > so that walkthrough was nice with the pictures > On Mar 19, 2014, at 7:25 PM, Bruno Oliveira wrote: > > I guess that was a bad sentence, we are here to help anyone interested in > OSS. My understanding about Passos' suggestion, is because there are > several resources on the internet to newcomers learn about Android. > > Duplicate it would be too much. > -- > abstractj > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > If we don't want to offer help for those that are new (to Android), let's > get rid of it. > > Perhaps, we can link to better, more up-to-date, introductions; if really > needed > > -Matthias > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > I mean > > http://aerogear.org/docs/guides/GetStartedAndroid/ > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > -- Passos > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > Do you mean: > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > and to some degree > http://aerogear.org/docs/guides/GetStartedAndroid/ > > The only one that aligns with our efforts is the Eclipse one - as in JBDS > (or eclipse + JBoss Tools). > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > Finish them !! > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > Hi folks, > > For android we have some docs called 'Getting Started Guides' to help > community to import ag in your favorite IDE. I never agreed to these > documents and I don't want to keep updating it. > > If the developer will work with our libraries and already uses her > favorite IDE, she probably already knows how to do that. > > So, I'd like to kill these docs. wdyt? > > > +1000 > > > > -- Passos > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/25590684/attachment.html From matzew at apache.org Thu Mar 20 01:46:51 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 06:46:51 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: <1395271538172.ae4b66c7@Nodemailer> References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: On Thursday, March 20, 2014, Bruno Oliveira wrote: > I guess that was a bad sentence, Perhaps a bit of an unfortunate expression. If so: sorry for that > we are here to help anyone interested in OSS. Yeah :-) > My understanding about Passos' suggestion, is because there are several > resources on the internet to newcomers learn about Android. > > Duplicate it would be too much. > +1 > -- > abstractj > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > If we don't want to offer help for those that are new (to Android), let's > get rid of it. > > Perhaps, we can link to better, more up-to-date, introductions; if really > needed > > -Matthias > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > I mean > > http://aerogear.org/docs/guides/GetStartedAndroid/ > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > -- Passos > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > Do you mean: > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > and to some degree > http://aerogear.org/docs/guides/GetStartedAndroid/ > > The only one that aligns with our efforts is the Eclipse one - as in JBDS > (or eclipse + JBoss Tools). > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > Finish them !! > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > Hi folks, > > For android we have some docs called 'Getting Started Guides' to help > community to import ag in your favorite IDE. I never agreed to these > documents and I don't want to keep updating it. > > If the developer will work with our libraries and already uses her > favorite IDE, she probably already knows how to do that. > > So, I'd like to kill these docs. wdyt? > > > +1000 > > > > -- Passos > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/c3ddadd6/attachment.html From bruno at abstractj.org Thu Mar 20 02:03:58 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 20 Mar 2014 03:03:58 -0300 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: My opinion is to get rid of IDE setup, and keep:?http://aerogear.org/docs/guides/GetStartedAndroid/ The number of gotchas to get the environment working is a PITA. In addition I would rename to ?Contributing for Android" -- abstractj On March 20, 2014 at 2:46:59 AM, Matthias Wessendorf (matzew at apache.org) wrote: > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > > I guess that was a bad sentence, > > > Perhaps a bit of an unfortunate expression. If so: sorry for that > > > > we are here to help anyone interested in OSS. > > > Yeah :-) > > > > My understanding about Passos' suggestion, is because there are several > > resources on the internet to newcomers learn about Android. > > > > Duplicate it would be too much. > > > > +1 > > > > -- > > abstractj > > > > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > > > If we don't want to offer help for those that are new (to Android), let's > > get rid of it. > > > > Perhaps, we can link to better, more up-to-date, introductions; if really > > needed > > > > -Matthias > > > > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > > > I mean > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > -- Passos > > > > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > > > Do you mean: > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > and to some degree > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > The only one that aligns with our efforts is the Eclipse one - as in JBDS > > (or eclipse + JBoss Tools). > > > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > > > Finish them !! > > > > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > > > Hi folks, > > > > For android we have some docs called 'Getting Started Guides' to help > > community to import ag in your favorite IDE. I never agreed to these > > documents and I don't want to keep updating it. > > > > If the developer will work with our libraries and already uses her > > favorite IDE, she probably already knows how to do that. > > > > So, I'd like to kill these docs. wdyt? > > > > > > +1000 > > > > > > > > -- Passos > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > -- > > Matthias Wessendorf > > > > blog: > > > > > > -- > Sent from Gmail Mobile > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Thu Mar 20 02:16:22 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 07:16:22 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: On Thursday, March 20, 2014, Bruno Oliveira wrote: > My opinion is to get rid of IDE setup, and keep: > http://aerogear.org/docs/guides/GetStartedAndroid/ Yes! Good call > > The number of gotchas to get the environment working is a PITA. In > addition I would rename to "Contributing for Android" > > -- > abstractj > > On March 20, 2014 at 2:46:59 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > > > > I guess that was a bad sentence, > > > > > > Perhaps a bit of an unfortunate expression. If so: sorry for that > > > > > > > we are here to help anyone interested in OSS. > > > > > > Yeah :-) > > > > > > > My understanding about Passos' suggestion, is because there are several > > > resources on the internet to newcomers learn about Android. > > > > > > Duplicate it would be too much. > > > > > > > +1 > > > > > > > -- > > > abstractj > > > > > > > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > > > > > If we don't want to offer help for those that are new (to Android), > let's > > > get rid of it. > > > > > > Perhaps, we can link to better, more up-to-date, introductions; if > really > > > needed > > > > > > -Matthias > > > > > > > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > > > > > I mean > > > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > -- Passos > > > > > > > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > > > > > Do you mean: > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > and to some degree > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > > > The only one that aligns with our efforts is the Eclipse one - as in > JBDS > > > (or eclipse + JBoss Tools). > > > > > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > > > > > Finish them !! > > > > > > > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > > > > > Hi folks, > > > > > > For android we have some docs called 'Getting Started Guides' to help > > > community to import ag in your favorite IDE. I never agreed to these > > > documents and I don't want to keep updating it. > > > > > > If the developer will work with our libraries and already uses her > > > favorite IDE, she probably already knows how to do that. > > > > > > So, I'd like to kill these docs. wdyt? > > > > > > > > > +1000 > > > > > > > > > > > > -- Passos > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: > > > > > > > > > > -- > > Sent from Gmail Mobile > > _______________________________________________ > > 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/20140320/162871f5/attachment.html From corinnekrych at gmail.com Thu Mar 20 03:29:49 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 20 Mar 2014 08:29:49 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: <3F2737AD-1BCF-4399-9BC8-8B8CC392F846@gmail.com> For iOS we have this doc: http://aerogear.org/docs/guides/GetStartedwithAeroGearandXcode/ We don?t cover ?Getting started with AppCode? Indeed providing documentation for each IDE is a bit fastidious. My point is if we get rid of getting started with Eclipse, we shall remove our getting started with Xcode? ++ Corinne On 20 Mar 2014, at 07:16, Matthias Wessendorf wrote: > > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > My opinion is to get rid of IDE setup, and keep: http://aerogear.org/docs/guides/GetStartedAndroid/ > > > Yes! Good call > > > > The number of gotchas to get the environment working is a PITA. In addition I would rename to ?Contributing for Android" > > -- > abstractj > > On March 20, 2014 at 2:46:59 AM, Matthias Wessendorf (matzew at apache.org) wrote: > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > > > > I guess that was a bad sentence, > > > > > > Perhaps a bit of an unfortunate expression. If so: sorry for that > > > > > > > we are here to help anyone interested in OSS. > > > > > > Yeah :-) > > > > > > > My understanding about Passos' suggestion, is because there are several > > > resources on the internet to newcomers learn about Android. > > > > > > Duplicate it would be too much. > > > > > > > +1 > > > > > > > -- > > > abstractj > > > > > > > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > > > > > If we don't want to offer help for those that are new (to Android), let's > > > get rid of it. > > > > > > Perhaps, we can link to better, more up-to-date, introductions; if really > > > needed > > > > > > -Matthias > > > > > > > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > > > > > I mean > > > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > -- Passos > > > > > > > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > > > > > Do you mean: > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > and to some degree > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > > > The only one that aligns with our efforts is the Eclipse one - as in JBDS > > > (or eclipse + JBoss Tools). > > > > > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > > > > > Finish them !! > > > > > > > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > > > > > Hi folks, > > > > > > For android we have some docs called 'Getting Started Guides' to help > > > community to import ag in your favorite IDE. I never agreed to these > > > documents and I don't want to keep updating it. > > > > > > If the developer will work with our libraries and already uses her > > > favorite IDE, she probably already knows how to do that. > > > > > > So, I'd like to kill these docs. wdyt? > > > > > > > > > +1000 > > > > > > > > > > > > -- Passos > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: > > > > > > > > > > -- > > Sent from Gmail Mobile > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Sent from Gmail Mobile > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Thu Mar 20 03:43:27 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 08:43:27 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: <3F2737AD-1BCF-4399-9BC8-8B8CC392F846@gmail.com> References: <1395271538172.ae4b66c7@Nodemailer> <3F2737AD-1BCF-4399-9BC8-8B8CC392F846@gmail.com> Message-ID: On Thu, Mar 20, 2014 at 8:29 AM, Corinne Krych wrote: > For iOS we have this doc: > http://aerogear.org/docs/guides/GetStartedwithAeroGearandXcode/ > We don't cover "Getting started with AppCode" > Indeed providing documentation for each IDE is a bit fastidious. > > My point is if we get rid of getting started with Eclipse, we shall remove > our getting started with Xcode? > I am not really sure; I do like that doc and it seems to be a good intro. Having in my that our target is (IMO) not the really experienced iOS/ObjC hacker. It's most-likely a Java Enterprise/Web guy, in a need to do some sort of (native) mobile development. > > ++ > Corinne > > On 20 Mar 2014, at 07:16, Matthias Wessendorf wrote: > > > > > > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > My opinion is to get rid of IDE setup, and keep: > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > > > Yes! Good call > > > > > > > > The number of gotchas to get the environment working is a PITA. In > addition I would rename to "Contributing for Android" > > > > -- > > abstractj > > > > On March 20, 2014 at 2:46:59 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > > > > > > I guess that was a bad sentence, > > > > > > > > > Perhaps a bit of an unfortunate expression. If so: sorry for that > > > > > > > > > > we are here to help anyone interested in OSS. > > > > > > > > > Yeah :-) > > > > > > > > > > My understanding about Passos' suggestion, is because there are > several > > > > resources on the internet to newcomers learn about Android. > > > > > > > > Duplicate it would be too much. > > > > > > > > > > +1 > > > > > > > > > > -- > > > > abstractj > > > > > > > > > > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > > > > > > > If we don't want to offer help for those that are new (to Android), > let's > > > > get rid of it. > > > > > > > > Perhaps, we can link to better, more up-to-date, introductions; if > really > > > > needed > > > > > > > > -Matthias > > > > > > > > > > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > > > > > > > I mean > > > > > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > > > -- Passos > > > > > > > > > > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > > > > > > > Do you mean: > > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > > > and to some degree > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > > > > > The only one that aligns with our efforts is the Eclipse one - as in > JBDS > > > > (or eclipse + JBoss Tools). > > > > > > > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > > > > > > > Finish them !! > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > > > > > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > > > > > > > Hi folks, > > > > > > > > For android we have some docs called 'Getting Started Guides' to help > > > > community to import ag in your favorite IDE. I never agreed to these > > > > documents and I don't want to keep updating it. > > > > > > > > If the developer will work with our libraries and already uses her > > > > favorite IDE, she probably already knows how to do that. > > > > > > > > So, I'd like to kill these docs. wdyt? > > > > > > > > > > > > +1000 > > > > > > > > > > > > > > > > -- Passos > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > -- > > > > Matthias Wessendorf > > > > > > > > blog: > > > > > > > > > > > > > > -- > > > Sent from Gmail Mobile > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > -- > > Sent from Gmail Mobile > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/8f27d11a/attachment-0001.html From corinnekrych at gmail.com Thu Mar 20 04:31:29 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 20 Mar 2014 09:31:29 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> <3F2737AD-1BCF-4399-9BC8-8B8CC392F846@gmail.com> Message-ID: On 20 Mar 2014, at 08:43, Matthias Wessendorf wrote: > > > > On Thu, Mar 20, 2014 at 8:29 AM, Corinne Krych wrote: > For iOS we have this doc: > http://aerogear.org/docs/guides/GetStartedwithAeroGearandXcode/ > We don?t cover ?Getting started with AppCode? > Indeed providing documentation for each IDE is a bit fastidious. > > My point is if we get rid of getting started with Eclipse, we shall remove our getting started with Xcode? > > I am not really sure; I do like that doc and it seems to be a good intro. Having in my that our target is (IMO) not the really experienced iOS/ObjC hacker. > It's most-likely a Java Enterprise/Web guy, in a need to do some sort of (native) mobile development. #agreed then we should keep Getting started with Eclipse and Android, as Burr suggested. We should also find a place where to fit this general purpose documentation in our new ag.org revamp. > > > > > ++ > Corinne > > On 20 Mar 2014, at 07:16, Matthias Wessendorf wrote: > > > > > > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > My opinion is to get rid of IDE setup, and keep: http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > > > Yes! Good call > > > > > > > > The number of gotchas to get the environment working is a PITA. In addition I would rename to ?Contributing for Android" > > > > -- > > abstractj > > > > On March 20, 2014 at 2:46:59 AM, Matthias Wessendorf (matzew at apache.org) wrote: > > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > > > > > > I guess that was a bad sentence, > > > > > > > > > Perhaps a bit of an unfortunate expression. If so: sorry for that > > > > > > > > > > we are here to help anyone interested in OSS. > > > > > > > > > Yeah :-) > > > > > > > > > > My understanding about Passos' suggestion, is because there are several > > > > resources on the internet to newcomers learn about Android. > > > > > > > > Duplicate it would be too much. > > > > > > > > > > +1 > > > > > > > > > > -- > > > > abstractj > > > > > > > > > > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > > > > > > > If we don't want to offer help for those that are new (to Android), let's > > > > get rid of it. > > > > > > > > Perhaps, we can link to better, more up-to-date, introductions; if really > > > > needed > > > > > > > > -Matthias > > > > > > > > > > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > > > > > > > I mean > > > > > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > > > -- Passos > > > > > > > > > > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > > > > > > > Do you mean: > > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > > > and to some degree > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > > > > > The only one that aligns with our efforts is the Eclipse one - as in JBDS > > > > (or eclipse + JBoss Tools). > > > > > > > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > > > > > > > Finish them !! > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > > > > > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > > > > > > > Hi folks, > > > > > > > > For android we have some docs called 'Getting Started Guides' to help > > > > community to import ag in your favorite IDE. I never agreed to these > > > > documents and I don't want to keep updating it. > > > > > > > > If the developer will work with our libraries and already uses her > > > > favorite IDE, she probably already knows how to do that. > > > > > > > > So, I'd like to kill these docs. wdyt? > > > > > > > > > > > > +1000 > > > > > > > > > > > > > > > > -- Passos > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > -- > > > > Matthias Wessendorf > > > > > > > > blog: > > > > > > > > > > > > > > -- > > > Sent from Gmail Mobile > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > -- > > Sent from Gmail Mobile > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From bruno at abstractj.org Thu Mar 20 06:11:01 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 20 Mar 2014 07:11:01 -0300 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: <3F2737AD-1BCF-4399-9BC8-8B8CC392F846@gmail.com> References: <1395271538172.ae4b66c7@Nodemailer> <3F2737AD-1BCF-4399-9BC8-8B8CC392F846@gmail.com> Message-ID: Well is just my opinion, but we already have several websites outside there to educate and teach into their own respective platforms.? -- abstractj On March 20, 2014 at 4:30:01 AM, Corinne Krych (corinnekrych at gmail.com) wrote: > > For iOS we have this doc: > http://aerogear.org/docs/guides/GetStartedwithAeroGearandXcode/ > We don?t cover ?Getting started with AppCode? > Indeed providing documentation for each IDE is a bit fastidious. > > My point is if we get rid of getting started with Eclipse, we shall > remove our getting started with Xcode? > > ++ > Corinne From matzew at apache.org Thu Mar 20 06:43:03 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 11:43:03 +0100 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: Message-ID: Hello Willy On Wed, Mar 19, 2014 at 6:30 PM, Willy Martin Aguirre Rodriguez < marti1003 at hotmail.com> wrote: > Hi > > http://aerogear.org/docs/specs/aerogear-server-push/ > > http://aerogear.org/push/ > > the idea is to implement Amazon Push, BlackBerry or Windows for > aerogear-server-push > I'd say the idea would be to implement at least two of them; e.g. Amazon and Windows; if time allows adding more would be even better. (the work is on the server, the ui, the documentation and examples) Does that sound good ? Greetings, Matthias > > ------------------------------ > From: marti1003 at hotmail.com > To: aerogear-dev at lists.jboss.org > Date: Tue, 18 Mar 2014 14:26:01 -0500 > > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > > About my experience: > > for mobile I am using cordova(phonegap) for android this include Jquery > mobile and dev firerfox apps with backbonejs > backend java play framework http://www.playframework.com/ (hibernate) and > dynamic jasper > > I remember was made an app with j2me and servlets communication via > sockets > > I will finish a project where connects two systems one of then is Oracle > PeopleSoft and and Adryan Cosapi Data( > http://www.cosapidata.com.pe/Adryan.asp) via webservices. > > here you are my github account > > https://github.com/marti1125 > > Regards > Willy > > > ------------------------------ > Date: Tue, 18 Mar 2014 18:27:28 +0100 > From: matzew at apache.org > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > > > > On Tue, Mar 18, 2014 at 6:16 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > Yes! > > I really like to work with mobile technology > > > awesome! > > Regarding the requested technologies (e.g. Amazon Push, BlackBerry or > Windows), do you have experience in that area (e.g. development of apps > and/or push APIs for them) ? > > > Greetings, > Matthias > > > > > > ------------------------------ > Date: Tue, 18 Mar 2014 17:48:11 +0100 > From: matzew at apache.org > > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > Hello Willy, > > the AeroGear UnifiedPush server supports push notifications over a unified > API for the following platforms: > * Google Cloud Messaging (Android and Chrome) > * APNs (iOS) ==> Safari is on the works (by Luke) > * SimplePush (Firefox OS and polyfil for any browser) > > > The goal of the suggested project would be adding support for other push > networks: > * Amazon Push > * Windows Phone/Mobile > * Black Berry > > Besides that we are happy to get support for other push networks as well. > > > The main work would be the integration of those networks (server-side, > admin UI, documentation and examples) > > > Does that sound interesting to you ? > > > Greetings, > Matthias > > > > > On Tue, Mar 18, 2014 at 5:15 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > ups sorry is this > > https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Support_new_Push_Networks_on_the_UnifiedPush_Server > > ------------------------------ > Date: Tue, 18 Mar 2014 16:59:08 +0100 > From: scm.blanc at gmail.com > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > > Hi, > I think you should post that to the RHQ mailing list since it's a RHQ > related project > https://fedorahosted.org/mailman/listinfo/rhq-users > > Seb > > > > On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > Hi! > > I made some firefox os apps and I Java dev > I really interesting in > > > https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ > > Could you tell me more about this project? and how to make my proposal for > this project? > > Regards > Willy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140320/ac84bbfd/attachment-0001.html From daniel at passos.me Thu Mar 20 07:07:47 2014 From: daniel at passos.me (Daniel Passos) Date: Thu, 20 Mar 2014 08:07:47 -0300 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: My point is. For use agdroid, a pre-req is android skill, and for programming in android a pre-req is a Java skill. So, if you are java programming or android programming you already use some idea and we not need teach you how to use it For use oor lib Google (I'm not talking about google.com but of developer.google.com) help you to use an external library in your project, for Eclipse (ADT) or Intellij (Android Studio) IMO we need support only how to build adgroid library, because it's not trivial and you need a lot of things to make it. -- Passos On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > If we don't want to offer help for those that are new (to Android), let's > get rid of it. > > Perhaps, we can link to better, more up-to-date, introductions; if really > needed > > -Matthias > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > >> I mean >> >> http://aerogear.org/docs/guides/GetStartedAndroid/ >> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >> >> -- Passos >> >> >> On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: >> >> Do you mean: >> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >> >> and to some degree >> http://aerogear.org/docs/guides/GetStartedAndroid/ >> >> The only one that aligns with our efforts is the Eclipse one - as in JBDS >> (or eclipse + JBoss Tools). >> >> On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: >> >> Finish them !! >> >> >> On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: >> >> >> >> >> On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: >> >> Hi folks, >> >> For android we have some docs called 'Getting Started Guides' to help >> community to import ag in your favorite IDE. I never agreed to these >> documents and I don't want to keep updating it. >> >> If the developer will work with our libraries and already uses her >> favorite IDE, she probably already knows how to do that. >> >> So, I'd like to kill these docs. wdyt? >> >> >> +1000 >> >> >> >> -- 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 >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lis >> >> > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/9065a175/attachment.html From bruno at abstractj.org Thu Mar 20 07:09:09 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 20 Mar 2014 08:09:09 -0300 Subject: [aerogear-dev] aerogear.org revamp: team work In-Reply-To: References: <5CEC844E-310B-4DB7-AC89-43E5CC57EA18@gmail.com> Message-ID: Ahoy, I did the rebase?https://github.com/aerogear/aerogear.org/tree/sass-rebased. But due to my great skills on sass, something is wrong. Any takers? -- abstractj On March 19, 2014 at 11:01:25 AM, Corinne Krych (corinnekrych at gmail.com) wrote: > Let me rebase. > ++ > Corinne > On 19 Mar 2014, at 14:01, Bruno Oliveira wrote: > > > Hi Corinne, I was giving a look at sass branch and I?m really concerned due to the number > of conflicts with ?master?. > > > > I think for the sanity of everyone, is healthy to regularly rebase that branch against > master like Corinne mentioned before. I tried rebase, but due to my poor sass skills, > I?m afraid of mess it up. > > > > What I did? > > > > git checkout sass > > git rebase origin/master > > > > > > -- > > abstractj > > > > On February 24, 2014 at 11:09:59 AM, Corinne Krych (corinnekrych at gmail.com) wrote: > >> Hello All, > >> > >> With aerogear web site roadmap [1] proposal we can start working together toward a > new > >> website. We already have a common branch (named sass - maybe not the best name) [2] where > >> we can work together. It?s important to rebase/keep this branch up to date. > >> > >> Here is how we could work together efficiently: > >> - take JIRA for 0.1.0 release, > >> - branch from sass branch, do you work > >> - send PR againt sass. > >> - usual PR review > >> - then PR can be merged into sass. > >> > >> If a ticket requires changes in page documentation like splitting a markdown page > into > >> several pages or move to asciidoc format etc? we should do this JIRA initial in master > >> branch, send a PRL, get the PR merged and get the changes in sass branch. This way we can > >> keep history and let the documentation evolves without fear for merging it into new > site > >> revamp branch. > >> > >> Thought? #agreed? > >> > >> ++ > >> Corinne > >> [1] http://aerogear.org/docs/planning/roadmaps/AeroGearWebSite/ > >> [2 https://github.com/aerogear/aerogear.org/tree/sass > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > > > > From daniel at passos.me Thu Mar 20 07:10:21 2014 From: daniel at passos.me (Daniel Passos) Date: Thu, 20 Mar 2014 08:10:21 -0300 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: On Thu, Mar 20, 2014 at 3:03 AM, Bruno Oliveira wrote: > My opinion is to get rid of IDE setup, and keep: > http://aerogear.org/docs/guides/GetStartedAndroid/ > > The number of gotchas to get the environment working is a PITA. In > addition I would rename to "Contributing for Android" > It was replaced by How to build agdroid library[1]. It will be kept ;) [1] http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/ > -- > abstractj > > On March 20, 2014 at 2:46:59 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > > > > I guess that was a bad sentence, > > > > > > Perhaps a bit of an unfortunate expression. If so: sorry for that > > > > > > > we are here to help anyone interested in OSS. > > > > > > Yeah :-) > > > > > > > My understanding about Passos' suggestion, is because there are several > > > resources on the internet to newcomers learn about Android. > > > > > > Duplicate it would be too much. > > > > > > > +1 > > > > > > > -- > > > abstractj > > > > > > > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > > > > > If we don't want to offer help for those that are new (to Android), > let's > > > get rid of it. > > > > > > Perhaps, we can link to better, more up-to-date, introductions; if > really > > > needed > > > > > > -Matthias > > > > > > > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > > > > > I mean > > > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > -- Passos > > > > > > > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > > > > > Do you mean: > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > and to some degree > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > > > The only one that aligns with our efforts is the Eclipse one - as in > JBDS > > > (or eclipse + JBoss Tools). > > > > > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > > > > > Finish them !! > > > > > > > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > > > > > Hi folks, > > > > > > For android we have some docs called 'Getting Started Guides' to help > > > community to import ag in your favorite IDE. I never agreed to these > > > documents and I don't want to keep updating it. > > > > > > If the developer will work with our libraries and already uses her > > > favorite IDE, she probably already knows how to do that. > > > > > > So, I'd like to kill these docs. wdyt? > > > > > > > > > +1000 > > > > > > > > > > > > -- Passos > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: > > > > > > > > > > -- > > Sent from Gmail Mobile > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/dc0640ff/attachment-0001.html From bruno at abstractj.org Thu Mar 20 07:14:17 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 20 Mar 2014 08:14:17 -0300 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: So to me +1 on kill any IDE related, by that I mean. Android environment configuration and IDEs. If we have something pretty much specific for AG, it makes sense to be documented. Unless someone would like to maintain that docs every time Eclipse, IntelliJ and AppCode release a new version. I can?t see volunteers. -- abstractj On March 20, 2014 at 8:10:50 AM, Daniel Passos (daniel at passos.me) wrote: > > On Thu, Mar 20, 2014 at 3:03 AM, Bruno Oliveira > wrote: > > My opinion is to get rid of IDE setup, and keep: http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > The number of gotchas to get the environment working is a PITA. > In addition I would rename to ?Contributing for Android" > > It was replaced by How to build agdroid library[1]. It will be > kept ;) > > [1] http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/ > (http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/) From corinnekrych at gmail.com Thu Mar 20 07:14:39 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 20 Mar 2014 12:14:39 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: Consistency is key, specially with the new site coming out. Either we kep IDE setup for android and iOS or we remove both. The simpliest for the new site will be to removed those getting started with IDE. Actuelly we could write a blog about Xcode and AG getting started... We will have some documentation in the GET IT / SET UP section of each fathers (let?s say core) which may include some doc or link on IDE setup. ++ Corinne On 20 Mar 2014, at 12:10, Daniel Passos wrote: > On Thu, Mar 20, 2014 at 3:03 AM, Bruno Oliveira wrote: > My opinion is to get rid of IDE setup, and keep: http://aerogear.org/docs/guides/GetStartedAndroid/ > > The number of gotchas to get the environment working is a PITA. In addition I would rename to ?Contributing for Android" > > It was replaced by How to build agdroid library[1]. It will be kept ;) > > [1] http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/ > > -- > abstractj > > On March 20, 2014 at 2:46:59 AM, Matthias Wessendorf (matzew at apache.org) wrote: > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > > > > I guess that was a bad sentence, > > > > > > Perhaps a bit of an unfortunate expression. If so: sorry for that > > > > > > > we are here to help anyone interested in OSS. > > > > > > Yeah :-) > > > > > > > My understanding about Passos' suggestion, is because there are several > > > resources on the internet to newcomers learn about Android. > > > > > > Duplicate it would be too much. > > > > > > > +1 > > > > > > > -- > > > abstractj > > > > > > > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > > > > > If we don't want to offer help for those that are new (to Android), let's > > > get rid of it. > > > > > > Perhaps, we can link to better, more up-to-date, introductions; if really > > > needed > > > > > > -Matthias > > > > > > > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > > > > > I mean > > > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > -- Passos > > > > > > > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > > > > > Do you mean: > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > and to some degree > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > > > The only one that aligns with our efforts is the Eclipse one - as in JBDS > > > (or eclipse + JBoss Tools). > > > > > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > > > > > Finish them !! > > > > > > > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > > > > > Hi folks, > > > > > > For android we have some docs called 'Getting Started Guides' to help > > > community to import ag in your favorite IDE. I never agreed to these > > > documents and I don't want to keep updating it. > > > > > > If the developer will work with our libraries and already uses her > > > favorite IDE, she probably already knows how to do that. > > > > > > So, I'd like to kill these docs. wdyt? > > > > > > > > > +1000 > > > > > > > > > > > > -- Passos > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: > > > > > > > > > > -- > > Sent from Gmail Mobile > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From miguel21op at gmail.com Thu Mar 20 07:24:21 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Thu, 20 Mar 2014 11:24:21 +0000 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: <1A80795A-9F6C-4381-8883-E94AF30B5A2D@gmail.com> A regular Java programmer needs a steep learning curve to be a good (not fair) Android programmer. No dia 20/03/2014, ?s 11:07, Daniel Passos escreveu: > My point is. For use agdroid, a pre-req is android skill, and for programming in android a pre-req is a Java skill. So, if you are java programming or android programming you already use some idea and we not need teach you how to use it > > For use oor lib Google (I'm not talking about google.com but of developer.google.com) help you to use an external library in your project, for Eclipse (ADT) or Intellij (Android Studio) > > IMO we need support only how to build adgroid library, because it's not trivial and you need a lot of things to make it. > > -- Passos > > > >> On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: >> If we don't want to offer help for those that are new (to Android), let's get rid of it. >> >> Perhaps, we can link to better, more up-to-date, introductions; if really needed >> >> -Matthias >> >> >>> On Wednesday, March 19, 2014, Daniel Passos wrote: >>> I mean >>> >>> http://aerogear.org/docs/guides/GetStartedAndroid/ >>> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >>> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >>> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >>> >>> -- Passos >>> >>> >>> On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: >>> Do you mean: >>> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >>> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >>> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >>> >>> and to some degree >>> http://aerogear.org/docs/guides/GetStartedAndroid/ >>> >>> The only one that aligns with our efforts is the Eclipse one - as in JBDS (or eclipse + JBoss Tools). >>> >>>> On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: >>>> >>>> Finish them !! >>>> >>>> >>>> On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: >>>> >>>> >>>> >>>> On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: >>>> Hi folks, >>>> >>>> For android we have some docs called 'Getting Started Guides' to help community to import ag in your favorite IDE. I never agreed to these documents and I don't want to keep updating it. >>>> >>>> If the developer will work with our libraries and already uses her favorite IDE, she probably already knows how to do that. >>>> >>>> So, I'd like to kill these docs. wdyt? >>>> >>>> +1000 >>>> >>>> >>>> -- 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 >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lis >> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/8880c304/attachment.html From matzew at apache.org Thu Mar 20 07:24:56 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 12:24:56 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: Message-ID: On Thu, Mar 20, 2014 at 12:07 PM, Daniel Passos wrote: > My point is. For use agdroid, a pre-req is android skill, and for > programming in android a pre-req is a Java skill. So, if you are java > programming or android programming you already use some idea and we not > need teach you how to use it > > For use oor lib Google (I'm not talking about google.com but of > developer.google.com) help you to use an external library in your > project, for Eclipse (ADT) or Intellij (Android Studio) > Well, if that's really good enough ("Click here (link to google) to see how to integrate our library into your project"), I guess that's the way to go. > > IMO we need support only how to build adgroid library, because it's not > trivial and you need a lot of things to make it. > yeah > > -- Passos > > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > >> If we don't want to offer help for those that are new (to Android), let's >> get rid of it. >> >> Perhaps, we can link to better, more up-to-date, introductions; if really >> needed >> >> -Matthias >> >> >> On Wednesday, March 19, 2014, Daniel Passos wrote: >> >>> I mean >>> >>> http://aerogear.org/docs/guides/GetStartedAndroid/ >>> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >>> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >>> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >>> >>> -- Passos >>> >>> >>> On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: >>> >>> Do you mean: >>> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >>> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >>> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >>> >>> and to some degree >>> http://aerogear.org/docs/guides/GetStartedAndroid/ >>> >>> The only one that aligns with our efforts is the Eclipse one - as in >>> JBDS (or eclipse + JBoss Tools). >>> >>> On Mar 19, 2014, at 9:36 AM, Sebastien Blanc >>> wrote: >>> >>> Finish them !! >>> >>> >>> On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: >>> >>> >>> >>> >>> On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: >>> >>> Hi folks, >>> >>> For android we have some docs called 'Getting Started Guides' to help >>> community to import ag in your favorite IDE. I never agreed to these >>> documents and I don't want to keep updating it. >>> >>> If the developer will work with our libraries and already uses her >>> favorite IDE, she probably already knows how to do that. >>> >>> So, I'd like to kill these docs. wdyt? >>> >>> >>> +1000 >>> >>> >>> >>> -- 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 >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lis >>> >>> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/7891d5c1/attachment-0001.html From matzew at apache.org Thu Mar 20 07:27:37 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 12:27:37 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: On Thu, Mar 20, 2014 at 12:14 PM, Corinne Krych wrote: > Consistency is key, specially with the new site coming out. > > Either we kep IDE setup for android and iOS or we remove both. > > The simpliest for the new site will be to removed those getting started > with IDE. > would make the site cleaner - less verbose > Actuelly we could write a blog about Xcode and AG getting started... > > We will have some documentation in the GET IT / SET UP section of each > fathers (let's say core) which may include some doc or link on IDE setup. > I *think* that sounds good > > ++ > Corinne > > On 20 Mar 2014, at 12:10, Daniel Passos wrote: > > > On Thu, Mar 20, 2014 at 3:03 AM, Bruno Oliveira > wrote: > > My opinion is to get rid of IDE setup, and keep: > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > The number of gotchas to get the environment working is a PITA. In > addition I would rename to "Contributing for Android" > > > > It was replaced by How to build agdroid library[1]. It will be kept ;) > > > > [1] > http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/ > > > > -- > > abstractj > > > > On March 20, 2014 at 2:46:59 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > > > On Thursday, March 20, 2014, Bruno Oliveira wrote: > > > > > > > I guess that was a bad sentence, > > > > > > > > > Perhaps a bit of an unfortunate expression. If so: sorry for that > > > > > > > > > > we are here to help anyone interested in OSS. > > > > > > > > > Yeah :-) > > > > > > > > > > My understanding about Passos' suggestion, is because there are > several > > > > resources on the internet to newcomers learn about Android. > > > > > > > > Duplicate it would be too much. > > > > > > > > > > +1 > > > > > > > > > > -- > > > > abstractj > > > > > > > > > > > > On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: > > > > > > > > If we don't want to offer help for those that are new (to Android), > let's > > > > get rid of it. > > > > > > > > Perhaps, we can link to better, more up-to-date, introductions; if > really > > > > needed > > > > > > > > -Matthias > > > > > > > > > > > > On Wednesday, March 19, 2014, Daniel Passos wrote: > > > > > > > > I mean > > > > > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > > > -- Passos > > > > > > > > > > > > On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: > > > > > > > > Do you mean: > > > > http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ > > > > http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ > > > > http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ > > > > > > > > and to some degree > > > > http://aerogear.org/docs/guides/GetStartedAndroid/ > > > > > > > > The only one that aligns with our efforts is the Eclipse one - as in > JBDS > > > > (or eclipse + JBoss Tools). > > > > > > > > On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: > > > > > > > > Finish them !! > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: > > > > > > > > > > > > > > > > > > > > On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: > > > > > > > > Hi folks, > > > > > > > > For android we have some docs called 'Getting Started Guides' to help > > > > community to import ag in your favorite IDE. I never agreed to these > > > > documents and I don't want to keep updating it. > > > > > > > > If the developer will work with our libraries and already uses her > > > > favorite IDE, she probably already knows how to do that. > > > > > > > > So, I'd like to kill these docs. wdyt? > > > > > > > > > > > > +1000 > > > > > > > > > > > > > > > > -- Passos > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > -- > > > > Matthias Wessendorf > > > > > > > > blog: > > > > > > > > > > > > > > -- > > > Sent from Gmail Mobile > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140320/4c5d2ab0/attachment.html From lholmqui at redhat.com Thu Mar 20 08:26:32 2014 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 20 Mar 2014 08:26:32 -0400 (EDT) Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: <351B2C57-7082-4023-9DDB-1FE56A17AE52@redhat.com> Sent from my iPhone > On Mar 20, 2014, at 7:14 AM, Bruno Oliveira wrote: > > So to me +1 on kill any IDE related, by that I mean. Android environment configuration and IDEs. > This makes sense. Just as long as we point to the android docs or whatever > If we have something pretty much specific for AG, it makes sense to be documented. Unless someone would like to maintain that docs every time Eclipse, IntelliJ and AppCode release a new version. > > I can?t see volunteers. > > -- > abstractj > > On March 20, 2014 at 8:10:50 AM, Daniel Passos (daniel at passos.me) wrote: >>> On Thu, Mar 20, 2014 at 3:03 AM, Bruno Oliveira >> wrote: >>> My opinion is to get rid of IDE setup, and keep: http://aerogear.org/docs/guides/GetStartedAndroid/ >>> >>> The number of gotchas to get the environment working is a PITA. >> In addition I would rename to ?Contributing for Android" >> >> It was replaced by How to build agdroid library[1]. It will be >> kept ;) >> >> [1] http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/ >> (http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/) > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From edewit at redhat.com Thu Mar 20 03:37:52 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 20 Mar 2014 08:37:52 +0100 Subject: [aerogear-dev] Sound issue Cordova iOS and notation In-Reply-To: References: Message-ID: <4B2E5C80-C1D4-4AAB-8670-1DC7EE1A1AA9@redhat.com> There is nothing we can do about that, when the notification arrives the phone will vibrate in accordance with the user preferences. iPhone Settings > Sound - Android Settings > Device > Sound > Default notification Cheers, Erik Jan On 19 Mar,2014, at 22:45 , Miguel Lemos wrote: > In Android the notification triggers the sound, vibrate, etc. But indeed the problem is that this should happen (or not...), as I said, when it arrives at the notification tray. > > > On Wed, Mar 19, 2014 at 5:59 PM, Miguel Lemos wrote: > * not after I pressed... > > > On Wed, Mar 19, 2014 at 5:58 PM, Miguel Lemos wrote: > Yes, the sounds can be defined by the app. > > > In the iOS case (with Cordova) the only way to make the sound play that I know is to put the file in the project's root and pointing to it. I tested and it works. Not that i use it very much, but sometimes it's needed... > > > The function you use to play a sound along with the notification is: > > if (e.sound) { > var media = new Media("/android_asset/www/" + e.sound); > media.play(); > } > > I didn't manage to make it work. Anyway I think it would be more "normal" a function like the one I sent. But, as I told before, the vibration and / or sound play only makes sense when the notification arrives in the notification area, not before I pressed on it. > > Mind for instance a geofenced notification:the user must see it at the moment it arrives, and not 30 minutes later. In this case the vibration or sound are very important. > > > On Wed, Mar 19, 2014 at 5:44 PM, Burr Sutter wrote: > Are there no "out-of-the-box" sounds for Android? > > I thought the iOS sounds were not driven by the indiviual app. > > > On Mar 19, 2014, at 1:40 PM, Sebastien Blanc wrote: > >> >> >> >> On Wed, Mar 19, 2014 at 5:50 PM, Miguel Lemos wrote: >> Hi >> >> The sound event when the notification arrives doesn't seem to work (at least on iPhone; Android not tested yet). >> >> And yes: the sound plugin is installed and working just fine. >> >> Besides, I don't understand quite well the way you build the event. Example given by you for Android: >> >> var my_media = new Media("/android_asset/www/" + e.sound); >> >> ..What sound? I can have several sounds on a given folder... >> I haven't play too much with sound but e.sound is supposed to contain the filename of your sound file (like beep.wav / sirene.wav ...) >> >> I think a better - and more trivial - approach would be something like this (just an opinion...): >> >> if (e.sound) { >> if (device.platform == "Android") { >> media = new Media("/android_asset/www/beep.wav"); >> } else if (device.platform == "iOS") { >> media = new Media("beep.wav"); // root directory >> } >> media.play(); >> } >> >> >> Thanks guys :-) >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140320/eda96ccb/attachment-0001.html From bsutter at redhat.com Thu Mar 20 08:55:20 2014 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 20 Mar 2014 08:55:20 -0400 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: On Mar 20, 2014, at 7:14 AM, Bruno Oliveira wrote: > So to me +1 on kill any IDE related, by that I mean. Android environment configuration and IDEs. > > If we have something pretty much specific for AG, it makes sense to be documented. Unless someone would like to maintain that docs every time Eclipse, IntelliJ and AppCode release a new version. What is "AppCode"? > > I can?t see volunteers. > > -- > abstractj > > On March 20, 2014 at 8:10:50 AM, Daniel Passos (daniel at passos.me) wrote: >>> On Thu, Mar 20, 2014 at 3:03 AM, Bruno Oliveira >> wrote: >>> My opinion is to get rid of IDE setup, and keep: http://aerogear.org/docs/guides/GetStartedAndroid/ >>> >>> The number of gotchas to get the environment working is a PITA. >> In addition I would rename to ?Contributing for Android" >> >> It was replaced by How to build agdroid library[1]. It will be >> kept ;) >> >> [1] http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/ >> (http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/) > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From bsutter at redhat.com Thu Mar 20 08:58:51 2014 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 20 Mar 2014 08:58:51 -0400 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: On Mar 20, 2014, at 7:14 AM, Corinne Krych wrote: > Consistency is key, specially with the new site coming out. +1 > > Either we kep IDE setup for android and iOS or we remove both. > > The simpliest for the new site will be to removed those getting started with IDE. > Actuelly we could write a blog about Xcode and AG getting started... > > We will have some documentation in the GET IT / SET UP section of each fathers (let?s say core) which may include some doc or link on IDE setup. I wish to focus on the hybrid developer first (he/she coming from the Java EE world) - we are offering JBDS for that developer - and that will require a tutorial of some sort - we could reuse the TiMo tutorial by working with Vineet. For the native developer, we simply need to show off how to include Aerogear into their Eclipse-based Android project or XCode project. Ideally we would also support "newbie native" developers with our docs, but that has to be a lower priority for now. > > ++ > Corinne > > On 20 Mar 2014, at 12:10, Daniel Passos wrote: > >> On Thu, Mar 20, 2014 at 3:03 AM, Bruno Oliveira wrote: >> My opinion is to get rid of IDE setup, and keep: http://aerogear.org/docs/guides/GetStartedAndroid/ >> >> The number of gotchas to get the environment working is a PITA. In addition I would rename to ?Contributing for Android" >> >> It was replaced by How to build agdroid library[1]. It will be kept ;) >> >> [1] http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/ >> >> -- >> abstractj >> >> On March 20, 2014 at 2:46:59 AM, Matthias Wessendorf (matzew at apache.org) wrote: >>> On Thursday, March 20, 2014, Bruno Oliveira wrote: >>> >>>> I guess that was a bad sentence, >>> >>> >>> Perhaps a bit of an unfortunate expression. If so: sorry for that >>> >>> >>>> we are here to help anyone interested in OSS. >>> >>> >>> Yeah :-) >>> >>> >>>> My understanding about Passos' suggestion, is because there are several >>>> resources on the internet to newcomers learn about Android. >>>> >>>> Duplicate it would be too much. >>>> >>> >>> +1 >>> >>> >>>> -- >>>> abstractj >>>> >>>> >>>> On Wed, Mar 19, 2014 at 7:51 PM, Matthias Wessendorf wrote: >>>> >>>> If we don't want to offer help for those that are new (to Android), let's >>>> get rid of it. >>>> >>>> Perhaps, we can link to better, more up-to-date, introductions; if really >>>> needed >>>> >>>> -Matthias >>>> >>>> >>>> On Wednesday, March 19, 2014, Daniel Passos wrote: >>>> >>>> I mean >>>> >>>> http://aerogear.org/docs/guides/GetStartedAndroid/ >>>> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >>>> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >>>> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >>>> >>>> -- Passos >>>> >>>> >>>> On Wed, Mar 19, 2014 at 10:45 AM, Burr Sutter wrote: >>>> >>>> Do you mean: >>>> http://aerogear.org/docs/guides/GetStartedAndroidEclipse/ >>>> http://aerogear.org/docs/guides/GetStartedAndroidIntellij/ >>>> http://aerogear.org/docs/guides/GettingStartedAndroidNetbeans/ >>>> >>>> and to some degree >>>> http://aerogear.org/docs/guides/GetStartedAndroid/ >>>> >>>> The only one that aligns with our efforts is the Eclipse one - as in JBDS >>>> (or eclipse + JBoss Tools). >>>> >>>> On Mar 19, 2014, at 9:36 AM, Sebastien Blanc wrote: >>>> >>>> Finish them !! >>>> >>>> >>>> On Wed, Mar 19, 2014 at 2:35 PM, Matthias Wessendorf wrote: >>>> >>>> >>>> >>>> >>>> On Wed, Mar 19, 2014 at 2:29 PM, Daniel Passos wrote: >>>> >>>> Hi folks, >>>> >>>> For android we have some docs called 'Getting Started Guides' to help >>>> community to import ag in your favorite IDE. I never agreed to these >>>> documents and I don't want to keep updating it. >>>> >>>> If the developer will work with our libraries and already uses her >>>> favorite IDE, she probably already knows how to do that. >>>> >>>> So, I'd like to kill these docs. wdyt? >>>> >>>> >>>> +1000 >>>> >>>> >>>> >>>> -- Passos >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: >>>> >>>> >>> >>> -- >>> Sent from Gmail Mobile >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Thu Mar 20 09:04:52 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 14:04:52 +0100 Subject: [aerogear-dev] Kill getting started docs In-Reply-To: References: <1395271538172.ae4b66c7@Nodemailer> Message-ID: On Thu, Mar 20, 2014 at 1:55 PM, Burr Sutter wrote: > > > On Mar 20, 2014, at 7:14 AM, Bruno Oliveira wrote: > > > So to me +1 on kill any IDE related, by that I mean. Android environment > configuration and IDEs. > > > > If we have something pretty much specific for AG, it makes sense to be > documented. Unless someone would like to maintain that docs every time > Eclipse, IntelliJ and AppCode release a new version. > > What is "AppCode"? > http://www.jetbrains.com/objc/ > > > > > I can't see volunteers. > > > > -- > > abstractj > > > > On March 20, 2014 at 8:10:50 AM, Daniel Passos (daniel at passos.me) wrote: > >>> On Thu, Mar 20, 2014 at 3:03 AM, Bruno Oliveira > >> wrote: > >>> My opinion is to get rid of IDE setup, and keep: > http://aerogear.org/docs/guides/GetStartedAndroid/ > >>> > >>> The number of gotchas to get the environment working is a PITA. > >> In addition I would rename to "Contributing for Android" > >> > >> It was replaced by How to build agdroid library[1]. It will be > >> kept ;) > >> > >> [1] > http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/ > >> ( > http://aerogear.org/docs/guides/aerogear-android/HowToBuildAeroGearAndroidLibrary/ > ) > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20140320/716fd236/attachment.html From miguel21op at gmail.com Thu Mar 20 10:02:48 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Thu, 20 Mar 2014 14:02:48 +0000 Subject: [aerogear-dev] Sound issue Cordova iOS and notation In-Reply-To: <4B2E5C80-C1D4-4AAB-8670-1DC7EE1A1AA9@redhat.com> References: <4B2E5C80-C1D4-4AAB-8670-1DC7EE1A1AA9@redhat.com> Message-ID: Well, for Android I know we can define programmatically how the app behaves when the notification arrives to the notification tray. For iPhone I don't know, but I read this (among other things): "I just figured out one way to do this [vibrate without sound]: if you want to phone to *only* vibrate on receipt of a push notification, you need to have a silent sound file in your application bundle, for example "silence.aif" ... if you specify that sound file in the APS notification, the iOS device will "play" the silence.aif from your application bundle, but since the sound is silence, there is nothing to hear. However the notification vibration is still triggered" And also this about push notifications on Facebook: For any of you's who have been frustrated with no sounds for notifications on Facebook, and to those who despises them! There is now a fix for both worlds..Yes Facebook finally fixed their facebook notification sounds on iPhone. This post is for the people who enjoy getting facebook notifications, like me! -Go to the facebook app on phone -Go to Account Settings -Go to Notifications -Go to Mobile Push -Look at the top of the screen, go to where it says "Sound for push notifications" -Edit it to ON for all notifications Enjoy guys. And for those who don't want sound than don't edit this and leave at default!! On Thu, Mar 20, 2014 at 7:37 AM, Erik Jan de Wit wrote: > There is nothing we can do about that, when the notification arrives the > phone will vibrate in accordance with the user preferences. iPhone Settings > > Sound - Android Settings > Device > Sound > Default notification > > Cheers, > Erik Jan > > On 19 Mar,2014, at 22:45 , Miguel Lemos wrote: > > In Android the notification triggers the sound, vibrate, etc. But indeed > the problem is that this should happen (or not...), as I said, when it > arrives at the notification tray. > > > On Wed, Mar 19, 2014 at 5:59 PM, Miguel Lemos wrote: > >> * not after I pressed... >> >> >> On Wed, Mar 19, 2014 at 5:58 PM, Miguel Lemos wrote: >> >>> Yes, the sounds can be defined by the app. >>> >>> > In the iOS case (with Cordova) the only way to make the sound play >>> that I know is to put the file in the project's root and pointing to it. I >>> tested and it works. Not that i use it very much, but sometimes it's >>> needed... >>> >>> > The function you use to play a sound along with the notification is: >>> >>> if (e.sound) { var media = new Media("/android_asset/www/" + e.sound); >>> media.play(); } >>> >>> I didn't manage to make it work. Anyway I think it would be more >>> "normal" a function like the one I sent. But, as I told before, the >>> vibration and / or sound play only makes sense when the notification >>> arrives in the notification area, not before I pressed on it. >>> >>> Mind for instance a geofenced notification:the user must see it at the >>> moment it arrives, and not 30 minutes later. In this case the vibration or >>> sound are very important. >>> >>> >>> On Wed, Mar 19, 2014 at 5:44 PM, Burr Sutter wrote: >>> >>>> Are there no "out-of-the-box" sounds for Android? >>>> >>>> I thought the iOS sounds were not driven by the indiviual app. >>>> >>>> >>>> On Mar 19, 2014, at 1:40 PM, Sebastien Blanc >>>> wrote: >>>> >>>> >>>> >>>> >>>> On Wed, Mar 19, 2014 at 5:50 PM, Miguel Lemos >>>> wrote: >>>> >>>>> Hi >>>>> >>>>> The sound event when the notification arrives doesn't seem to work (at >>>>> least on iPhone; Android not tested yet). >>>>> >>>>> And yes: the sound plugin is installed and working just fine. >>>>> >>>>> Besides, I don't understand quite well the way you build the event. >>>>> Example given by you for Android: >>>>> >>>>> var my_media = new Media("/android_asset/www/" + e.sound); >>>>> >>>>> ..What sound? I can have several sounds on a given folder... >>>>> >>>> I haven't play too much with sound but e.sound is supposed to contain >>>> the filename of your sound file (like beep.wav / sirene.wav ...) >>>> >>>>> >>>>> I think a better - and more trivial - approach would be something like >>>>> this (just an opinion...): >>>>> >>>>> if (e.sound) { >>>>> if (device.platform == "Android") { >>>>> media = new Media("/android_asset/www/beep.wav"); >>>>> } else if (device.platform == "iOS") { >>>>> media = new Media("beep.wav"); // root directory >>>>> } >>>>> media.play(); >>>>> } >>>>> >>>>> >>>>> Thanks guys :-) >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.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/20140320/e4bf15c6/attachment-0001.html From lholmqui at redhat.com Thu Mar 20 10:31:11 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Thu, 20 Mar 2014 10:31:11 -0400 Subject: [aerogear-dev] AeroGear.js + ES6 Message-ID: Hey peeps, I've been seeing libraries such and Angular and Ember starting to author in ES6( the next iteration of javascript ) and then transpiling back to ES5( the current iteration of javascript ). So i've created a new branch called "get_to_tha_choppa" that will be tracking these changes to see if we can benefit from this. this could also help us in the quest for AMD/Browser Modules/New Fancy Term some related JIRA https://issues.jboss.org/browse/AGJS-149 incase people don't get the "get_to_tha_choppa" reference https://www.youtube.com/watch?v=Xs_OacEq2Sk -Luke -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/1f22fe28/attachment.html From bruno at abstractj.org Thu Mar 20 10:50:39 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Thu, 20 Mar 2014 11:50:39 -0300 Subject: [aerogear-dev] AeroGear.js + ES6 In-Reply-To: References: Message-ID: go for it, can?t wait for ES7 and have a branch named ?LEGEN?WAIT FOR IT?DARY!" -- abstractj On March 20, 2014 at 11:31:23 AM, Lucas Holmquist (lholmqui at redhat.com) wrote: > > Hey peeps, > > I've been seeing libraries such and Angular and Ember starting > to author in ES6( the next iteration of javascript ) and then transpiling > back to ES5( the current iteration of javascript ). > > So i've created a new branch called "get_to_tha_choppa" that > will be tracking these changes to see if we can benefit from this. > > this could also help us in the quest for AMD/Browser Modules/New > Fancy Term > > some related JIRA > > https://issues.jboss.org/browse/AGJS-149 > > incase people don't get the "get_to_tha_choppa" reference > > https://www.youtube.com/watch?v=Xs_OacEq2Sk > > > -Luke From kpiwko at redhat.com Thu Mar 20 11:39:39 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 20 Mar 2014 16:39:39 +0100 Subject: [aerogear-dev] AeroGear Crypto 0.1.3 Staged In-Reply-To: References: Message-ID: <20140320163939.43826ce8@kapy-ntb-x220> We'll give it a try and let you know tomorrow late afternoon CET about the results. Karel On Thu, 20 Mar 2014 01:14:48 -0300 Bruno Oliveira wrote: > Good morning peeps, the project was staged under the following > profile:?https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2889/ > > It has fixes for Android platform. If you want to test it, try: > > -?https://github.com/aerogear/aerogear-android/pull/141 > -?https://github.com/aerogear/aerogear-android-integration-tests/pull/26 > > I?m planning to release it on Friday, so if you find any critical issues, let > me know. > > -- > abstractj > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From kpiwko at redhat.com Thu Mar 20 11:55:33 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 20 Mar 2014 16:55:33 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <936C2299-09C0-45BB-B4AC-D7350CE654F2@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> <936C2299-09C0-45BB-B4AC-D7350CE654F2@gmail.com> Message-ID: <20140320165533.0a8104b1@kapy-ntb-x220> So, how long will there be AG iOS 1.5 without any available support for AG Push Registration? It would make sense to me to stage&test 1.5 now and then wait for AG Push Registration 0.9.0 to happen, stage&test. Then push both into the wild simultaneously. Karel On Tue, 18 Mar 2014 11:09:34 +0100 Corinne Krych wrote: > +1 > Here's the plan. > Back to testing. > ++ > Corinne > On 18 Mar 2014, at 11:07, Matthias Wessendorf wrote: > > > > > > > > > On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych > > wrote: Yep indeed coordination is needed, let?s see how we progress on > > removing AFNetworking dep. When releasing 1.5 we?ll go either: > > 0.8.2 => with AFNetworking 2.2.1 > > > > sounds like an odd thing, due to item below > > > > > > or 0.9.0 => without AFNetworking dep > > > > +1 > > > > > > Keep you posted (very soon) on that. > > > > ++ > > Corinne > > On 18 Mar 2014, at 10:47, Sebastien Blanc wrote: > > > > > But until AG Push registration 0.9 is released , 0.8.1 do not work with > > > AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) Shouldn't it make > > > sense to make a 0.8.2 release with an updated pod (what Corinne > > > mentionned in the second message) to "fill the gap" until 0.9 is > > > released ? > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf > > > wrote: > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych > > > wrote: True, eventually we will remove that dependency. > > > What about getting 1.5 out of the way and then release AG Push > > > registration 0.9.0 without AFNetworkin dependency? > > > > > > > > > sounds good to me! > > > > > > > > > ++ > > > Corinne > > > On 18 Mar 2014, at 09:53, Matthias Wessendorf wrote: > > > > > > > Corinne, > > > > > > > > no AFN on that project, in the future: > > > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych > > > > wrote: Hello Sebi > > > > > > > > Actually PR are on their ways (as we test it) to set proper version, > > > > what you need here > > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > > > > is to upgrade to: platform :ios, ?7.0' > > > > pod 'AFNetworking', ?2.2.1' > > > > > > > > Note that we?ll support from ios 7.0 > > > > Feel free to send the PR with Podfile update if the testing works for > > > > you. > > > > > > > > ++ > > > > Thanks for the feedback, > > > > Corinne > > > > > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: > > > > > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > > > > > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > > > > > `AFNetworking/Serialization` required by > > > > > `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` > > > > > required by `AFNetworking/NSURLConnection (2.2.1)`- > > > > > `AFNetworking/Security` required by `AFNetworking/NSURLConnection > > > > > (2.2.1)`- `AFNetworking/NSURLConnection` required by > > > > > `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` > > > > > required by `AFNetworking/UIKit (2.2.1) > > > > > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > -- > > > > Matthias Wessendorf > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > sessions: http://www.slideshare.net/mwessendorf > > > > twitter: http://twitter.com/mwessendorf > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > sessions: http://www.slideshare.net/mwessendorf > > > twitter: http://twitter.com/mwessendorf > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Thu Mar 20 11:59:42 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 16:59:42 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <20140320165533.0a8104b1@kapy-ntb-x220> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> <936C2299-09C0-45BB-B4AC-D7350CE654F2@gmail.com> <20140320165533.0a8104b1@kapy-ntb-x220> Message-ID: On Thu, Mar 20, 2014 at 4:55 PM, Karel Piwko wrote: > So, how long will there be AG iOS 1.5 without any available support for AG > Push > Registration? > zero days http://cocoapods.org/?q=AeroGear 0.9.0 is already 'out' > > It would make sense to me to stage&test 1.5 now and then wait for AG Push > Registration 0.9.0 to happen, stage&test. Then push both into the wild > simultaneously. > > Karel > > On Tue, 18 Mar 2014 11:09:34 +0100 > Corinne Krych wrote: > > > +1 > > Here's the plan. > > Back to testing. > > ++ > > Corinne > > On 18 Mar 2014, at 11:07, Matthias Wessendorf wrote: > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych < > corinnekrych at gmail.com> > > > wrote: Yep indeed coordination is needed, let's see how we progress on > > > removing AFNetworking dep. When releasing 1.5 we'll go either: > > > 0.8.2 => with AFNetworking 2.2.1 > > > > > > sounds like an odd thing, due to item below > > > > > > > > > or 0.9.0 => without AFNetworking dep > > > > > > +1 > > > > > > > > > Keep you posted (very soon) on that. > > > > > > ++ > > > Corinne > > > On 18 Mar 2014, at 10:47, Sebastien Blanc wrote: > > > > > > > But until AG Push registration 0.9 is released , 0.8.1 do not work > with > > > > AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) Shouldn't it > make > > > > sense to make a 0.8.2 release with an updated pod (what Corinne > > > > mentionned in the second message) to "fill the gap" until 0.9 is > > > > released ? > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf < > matzew at apache.org> > > > > wrote: > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych < > corinnekrych at gmail.com> > > > > wrote: True, eventually we will remove that dependency. > > > > What about getting 1.5 out of the way and then release AG Push > > > > registration 0.9.0 without AFNetworkin dependency? > > > > > > > > > > > > sounds good to me! > > > > > > > > > > > > ++ > > > > Corinne > > > > On 18 Mar 2014, at 09:53, Matthias Wessendorf > wrote: > > > > > > > > > Corinne, > > > > > > > > > > no AFN on that project, in the future: > > > > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych < > corinnekrych at gmail.com> > > > > > wrote: Hello Sebi > > > > > > > > > > Actually PR are on their ways (as we test it) to set proper > version, > > > > > what you need here > > > > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > > > > > is to upgrade to: platform :ios, '7.0' > > > > > pod 'AFNetworking', '2.2.1' > > > > > > > > > > Note that we'll support from ios 7.0 > > > > > Feel free to send the PR with Podfile update if the testing works > for > > > > > you. > > > > > > > > > > ++ > > > > > Thanks for the feedback, > > > > > Corinne > > > > > > > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc > wrote: > > > > > > > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > > > > > > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- > > > > > > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > > > > > > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- > > > > > > `AFNetworking/NSURLConnection` required by `AFNetworking > (2.2.1)`- > > > > > > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- > > > > > > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > > > > > > `AFNetworking/Serialization` required by > > > > > > `AFNetworking/NSURLConnection (2.2.1)`- > `AFNetworking/Reachability` > > > > > > required by `AFNetworking/NSURLConnection (2.2.1)`- > > > > > > `AFNetworking/Security` required by `AFNetworking/NSURLConnection > > > > > > (2.2.1)`- `AFNetworking/NSURLConnection` required by > > > > > > `AFNetworking/NSURLSession (2.2.1)`- > `AFNetworking/NSURLConnection` > > > > > > required by `AFNetworking/UIKit (2.2.1) > > > > > > > > > > > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev at lists.jboss.org > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > -- > > > > > Matthias Wessendorf > > > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > sessions: http://www.slideshare.net/mwessendorf > > > > > twitter: http://twitter.com/mwessendorf > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev at lists.jboss.org > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > -- > > > > Matthias Wessendorf > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > sessions: http://www.slideshare.net/mwessendorf > > > > twitter: http://twitter.com/mwessendorf > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > sessions: http://www.slideshare.net/mwessendorf > > > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140320/36b89c2f/attachment-0001.html From edewit at redhat.com Thu Mar 20 12:12:05 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 20 Mar 2014 17:12:05 +0100 Subject: [aerogear-dev] Released 0.0.3 Cordova Push Plugin Message-ID: <98BB8816-A7B5-46FC-9956-E9A079D67FA5@redhat.com> Hi all, We?re happy to announce that version 0.0.3 of the Push Plugin has been released. The next release will include the new API so stay tuned. You can download it from http://plugins.cordova.io or look at our website http://aerogear.org/cordova/ Cheers, Erik Jan From kpiwko at redhat.com Thu Mar 20 12:12:22 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 20 Mar 2014 17:12:22 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> <936C2299-09C0-45BB-B4AC-D7350CE654F2@gmail.com> <20140320165533.0a8104b1@kapy-ntb-x220> Message-ID: <20140320171222.635cb6ac@kapy-ntb-x220> On Thu, 20 Mar 2014 16:59:42 +0100 Matthias Wessendorf wrote: > On Thu, Mar 20, 2014 at 4:55 PM, Karel Piwko wrote: > > > So, how long will there be AG iOS 1.5 without any available support for AG > > Push > > Registration? > > > > zero days > > http://cocoapods.org/?q=AeroGear > > 0.9.0 is already 'out' Sweet! I haven't expected that at all give the discussion above ;-) > > > > > > It would make sense to me to stage&test 1.5 now and then wait for AG Push > > Registration 0.9.0 to happen, stage&test. Then push both into the wild > > simultaneously. > > > > Karel > > > > On Tue, 18 Mar 2014 11:09:34 +0100 > > Corinne Krych wrote: > > > > > +1 > > > Here's the plan. > > > Back to testing. > > > ++ > > > Corinne > > > On 18 Mar 2014, at 11:07, Matthias Wessendorf wrote: > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych < > > corinnekrych at gmail.com> > > > > wrote: Yep indeed coordination is needed, let's see how we progress on > > > > removing AFNetworking dep. When releasing 1.5 we'll go either: > > > > 0.8.2 => with AFNetworking 2.2.1 > > > > > > > > sounds like an odd thing, due to item below > > > > > > > > > > > > or 0.9.0 => without AFNetworking dep > > > > > > > > +1 > > > > > > > > > > > > Keep you posted (very soon) on that. > > > > > > > > ++ > > > > Corinne > > > > On 18 Mar 2014, at 10:47, Sebastien Blanc wrote: > > > > > > > > > But until AG Push registration 0.9 is released , 0.8.1 do not work > > with > > > > > AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) Shouldn't it > > make > > > > > sense to make a 0.8.2 release with an updated pod (what Corinne > > > > > mentionned in the second message) to "fill the gap" until 0.9 is > > > > > released ? > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf < > > matzew at apache.org> > > > > > wrote: > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych < > > corinnekrych at gmail.com> > > > > > wrote: True, eventually we will remove that dependency. > > > > > What about getting 1.5 out of the way and then release AG Push > > > > > registration 0.9.0 without AFNetworkin dependency? > > > > > > > > > > > > > > > sounds good to me! > > > > > > > > > > > > > > > ++ > > > > > Corinne > > > > > On 18 Mar 2014, at 09:53, Matthias Wessendorf > > wrote: > > > > > > > > > > > Corinne, > > > > > > > > > > > > no AFN on that project, in the future: > > > > > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych < > > corinnekrych at gmail.com> > > > > > > wrote: Hello Sebi > > > > > > > > > > > > Actually PR are on their ways (as we test it) to set proper > > version, > > > > > > what you need here > > > > > > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > > > > > > is to upgrade to: platform :ios, '7.0' > > > > > > pod 'AFNetworking', '2.2.1' > > > > > > > > > > > > Note that we'll support from ios 7.0 > > > > > > Feel free to send the PR with Podfile update if the testing works > > for > > > > > > you. > > > > > > > > > > > > ++ > > > > > > Thanks for the feedback, > > > > > > Corinne > > > > > > > > > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc > > wrote: > > > > > > > > > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > > > > > > > `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/NSURLConnection` required by `AFNetworking > > (2.2.1)`- > > > > > > > `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > > > > > > > `AFNetworking/Serialization` required by > > > > > > > `AFNetworking/NSURLConnection (2.2.1)`- > > `AFNetworking/Reachability` > > > > > > > required by `AFNetworking/NSURLConnection (2.2.1)`- > > > > > > > `AFNetworking/Security` required by `AFNetworking/NSURLConnection > > > > > > > (2.2.1)`- `AFNetworking/NSURLConnection` required by > > > > > > > `AFNetworking/NSURLSession (2.2.1)`- > > `AFNetworking/NSURLConnection` > > > > > > > required by `AFNetworking/UIKit (2.2.1) > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > aerogear-dev mailing list > > > > > > aerogear-dev at lists.jboss.org > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Matthias Wessendorf > > > > > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > > sessions: http://www.slideshare.net/mwessendorf > > > > > > twitter: http://twitter.com/mwessendorf > > > > > > _______________________________________________ > > > > > > aerogear-dev mailing list > > > > > > aerogear-dev at lists.jboss.org > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev at lists.jboss.org > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > -- > > > > > Matthias Wessendorf > > > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > sessions: http://www.slideshare.net/mwessendorf > > > > > twitter: http://twitter.com/mwessendorf > > > > > > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev at lists.jboss.org > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev at lists.jboss.org > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > -- > > > > Matthias Wessendorf > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > sessions: http://www.slideshare.net/mwessendorf > > > > twitter: http://twitter.com/mwessendorf > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > From matzew at apache.org Thu Mar 20 12:14:25 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 17:14:25 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <20140320171222.635cb6ac@kapy-ntb-x220> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> <936C2299-09C0-45BB-B4AC-D7350CE654F2@gmail.com> <20140320165533.0a8104b1@kapy-ntb-x220> <20140320171222.635cb6ac@kapy-ntb-x220> Message-ID: On Thu, Mar 20, 2014 at 5:12 PM, Karel Piwko wrote: > On Thu, 20 Mar 2014 16:59:42 +0100 > Matthias Wessendorf wrote: > > > On Thu, Mar 20, 2014 at 4:55 PM, Karel Piwko wrote: > > > > > So, how long will there be AG iOS 1.5 without any available support > for AG > > > Push > > > Registration? > > > > > > > zero days > > > > http://cocoapods.org/?q=AeroGear > > > > 0.9.0 is already 'out' > > Sweet! I haven't expected that at all give the discussion above ;-) > Christos just did it :-) It will be 'officially' announced w/ the iOS 1.5.0 release > > > > > > > > > > > It would make sense to me to stage&test 1.5 now and then wait for AG > Push > > > Registration 0.9.0 to happen, stage&test. Then push both into the wild > > > simultaneously. > > > > > > Karel > > > > > > On Tue, 18 Mar 2014 11:09:34 +0100 > > > Corinne Krych wrote: > > > > > > > +1 > > > > Here's the plan. > > > > Back to testing. > > > > ++ > > > > Corinne > > > > On 18 Mar 2014, at 11:07, Matthias Wessendorf > wrote: > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych < > > > corinnekrych at gmail.com> > > > > > wrote: Yep indeed coordination is needed, let's see how we > progress on > > > > > removing AFNetworking dep. When releasing 1.5 we'll go either: > > > > > 0.8.2 => with AFNetworking 2.2.1 > > > > > > > > > > sounds like an odd thing, due to item below > > > > > > > > > > > > > > > or 0.9.0 => without AFNetworking dep > > > > > > > > > > +1 > > > > > > > > > > > > > > > Keep you posted (very soon) on that. > > > > > > > > > > ++ > > > > > Corinne > > > > > On 18 Mar 2014, at 10:47, Sebastien Blanc > wrote: > > > > > > > > > > > But until AG Push registration 0.9 is released , 0.8.1 do not > work > > > with > > > > > > AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) Shouldn't > it > > > make > > > > > > sense to make a 0.8.2 release with an updated pod (what Corinne > > > > > > mentionned in the second message) to "fill the gap" until 0.9 is > > > > > > released ? > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf < > > > matzew at apache.org> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych < > > > corinnekrych at gmail.com> > > > > > > wrote: True, eventually we will remove that dependency. > > > > > > What about getting 1.5 out of the way and then release AG Push > > > > > > registration 0.9.0 without AFNetworkin dependency? > > > > > > > > > > > > > > > > > > sounds good to me! > > > > > > > > > > > > > > > > > > ++ > > > > > > Corinne > > > > > > On 18 Mar 2014, at 09:53, Matthias Wessendorf > > > > wrote: > > > > > > > > > > > > > Corinne, > > > > > > > > > > > > > > no AFN on that project, in the future: > > > > > > > https://issues.jboss.org/browse/AGPUSH-558 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych < > > > corinnekrych at gmail.com> > > > > > > > wrote: Hello Sebi > > > > > > > > > > > > > > Actually PR are on their ways (as we test it) to set proper > > > version, > > > > > > > what you need here > > > > > > > > > > > https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile > > > > > > > is to upgrade to: platform :ios, '7.0' > > > > > > > pod 'AFNetworking', '2.2.1' > > > > > > > > > > > > > > Note that we'll support from ios 7.0 > > > > > > > Feel free to send the PR with Podfile update if the testing > works > > > for > > > > > > > you. > > > > > > > > > > > > > > ++ > > > > > > > Thanks for the feedback, > > > > > > > Corinne > > > > > > > > > > > > > > On 18 Mar 2014, at 09:44, Sebastien Blanc > > > > wrote: > > > > > > > > > > > > > > > FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- > > > > > > > > `AFNetworking/Serialization` required by `AFNetworking > (2.2.1)`- > > > > > > > > `AFNetworking/Security` required by `AFNetworking (2.2.1)`- > > > > > > > > `AFNetworking/Reachability` required by `AFNetworking > (2.2.1)`- > > > > > > > > `AFNetworking/NSURLConnection` required by `AFNetworking > > > (2.2.1)`- > > > > > > > > `AFNetworking/NSURLSession` required by `AFNetworking > (2.2.1)`- > > > > > > > > `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- > > > > > > > > `AFNetworking/Serialization` required by > > > > > > > > `AFNetworking/NSURLConnection (2.2.1)`- > > > `AFNetworking/Reachability` > > > > > > > > required by `AFNetworking/NSURLConnection (2.2.1)`- > > > > > > > > `AFNetworking/Security` required by > `AFNetworking/NSURLConnection > > > > > > > > (2.2.1)`- `AFNetworking/NSURLConnection` required by > > > > > > > > `AFNetworking/NSURLSession (2.2.1)`- > > > `AFNetworking/NSURLConnection` > > > > > > > > required by `AFNetworking/UIKit (2.2.1) > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > aerogear-dev mailing list > > > > > > > aerogear-dev at lists.jboss.org > > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Matthias Wessendorf > > > > > > > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > > > sessions: http://www.slideshare.net/mwessendorf > > > > > > > twitter: http://twitter.com/mwessendorf > > > > > > > _______________________________________________ > > > > > > > aerogear-dev mailing list > > > > > > > aerogear-dev at lists.jboss.org > > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > aerogear-dev mailing list > > > > > > aerogear-dev at lists.jboss.org > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Matthias Wessendorf > > > > > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > > sessions: http://www.slideshare.net/mwessendorf > > > > > > twitter: http://twitter.com/mwessendorf > > > > > > > > > > > > _______________________________________________ > > > > > > aerogear-dev mailing list > > > > > > aerogear-dev at lists.jboss.org > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > _______________________________________________ > > > > > > aerogear-dev mailing list > > > > > > aerogear-dev at lists.jboss.org > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev at lists.jboss.org > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > -- > > > > > Matthias Wessendorf > > > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > sessions: http://www.slideshare.net/mwessendorf > > > > > twitter: http://twitter.com/mwessendorf > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev at lists.jboss.org > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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/20140320/c3b93544/attachment-0001.html From tkriz at redhat.com Thu Mar 20 12:15:52 2014 From: tkriz at redhat.com (Tadeas Kriz) Date: Thu, 20 Mar 2014 17:15:52 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <936C2299-09C0-45BB-B4AC-D7350CE654F2@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5415546D-8275-4D98-A071-C4E77E15EA52@gmail.com> <3E17905A-B0B0-4062-B71A-36B61CD84C33@gmail.com> <936C2299-09C0-45BB-B4AC-D7350CE654F2@gmail.com> Message-ID: Run unit tests, two applications that use pipes (one of them also uses push, which worked when 0.9.0 was used) and also tested multipart. The only issue I found was with the multipart, which I?ve sent PR [1] for. 1 - https://github.com/aerogear/aerogear-ios/pull/122 ? Tadeas Kriz On 18 Mar 2014, at 11:09, Corinne Krych wrote: > +1 > Here's the plan. > Back to testing. > ++ > Corinne > On 18 Mar 2014, at 11:07, Matthias Wessendorf wrote: > >> >> >> >> On Tue, Mar 18, 2014 at 10:56 AM, Corinne Krych wrote: >> Yep indeed coordination is needed, let?s see how we progress on removing AFNetworking dep. >> When releasing 1.5 we?ll go either: >> 0.8.2 => with AFNetworking 2.2.1 >> >> sounds like an odd thing, due to item below >> >> >> or 0.9.0 => without AFNetworking dep >> >> +1 >> >> >> Keep you posted (very soon) on that. >> >> ++ >> Corinne >> On 18 Mar 2014, at 10:47, Sebastien Blanc wrote: >> >>> But until AG Push registration 0.9 is released , 0.8.1 do not work with AG iOS 1.5 , right ? (Sorry if I'm totally wrong :) ) >>> Shouldn't it make sense to make a 0.8.2 release with an updated pod (what Corinne mentionned in the second message) to "fill the gap" until 0.9 is released ? >>> >>> >>> >>> On Tue, Mar 18, 2014 at 10:06 AM, Matthias Wessendorf wrote: >>> >>> >>> >>> On Tue, Mar 18, 2014 at 10:05 AM, Corinne Krych wrote: >>> True, eventually we will remove that dependency. >>> What about getting 1.5 out of the way and then release AG Push registration 0.9.0 without AFNetworkin dependency? >>> >>> >>> sounds good to me! >>> >>> >>> ++ >>> Corinne >>> On 18 Mar 2014, at 09:53, Matthias Wessendorf wrote: >>> >>>> Corinne, >>>> >>>> no AFN on that project, in the future: >>>> https://issues.jboss.org/browse/AGPUSH-558 >>>> >>>> >>>> >>>> >>>> On Tue, Mar 18, 2014 at 9:51 AM, Corinne Krych wrote: >>>> Hello Sebi >>>> >>>> Actually PR are on their ways (as we test it) to set proper version, what you need here >>>> https://github.com/aerogear/aerogear-push-ios-registration/blob/master/Podfile >>>> is to upgrade to: >>>> platform :ios, ?7.0' >>>> pod 'AFNetworking', ?2.2.1' >>>> >>>> Note that we?ll support from ios 7.0 >>>> Feel free to send the PR with Podfile update if the testing works for you. >>>> >>>> ++ >>>> Thanks for the feedback, >>>> Corinne >>>> >>>> On 18 Mar 2014, at 09:44, Sebastien Blanc wrote: >>>> >>>>> FNetworking (= 2.2.1)` required by `AeroGear (1.5.0)`- `AFNetworking/Serialization` required by `AFNetworking (2.2.1)`- `AFNetworking/Security` required by `AFNetworking (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking (2.2.1)`- `AFNetworking/NSURLSession` required by `AFNetworking (2.2.1)`- `AFNetworking/UIKit` required by `AFNetworking (2.2.1)`- `AFNetworking/Serialization` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Reachability` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/Security` required by `AFNetworking/NSURLConnection (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/NSURLSession (2.2.1)`- `AFNetworking/NSURLConnection` required by `AFNetworking/UIKit (2.2.1) >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From marti1003 at hotmail.com Thu Mar 20 12:37:04 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Thu, 20 Mar 2014 11:37:04 -0500 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: , , , , , , , , Message-ID: yes :), thanks you I am going to send my proposal Date: Thu, 20 Mar 2014 11:43:03 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hello Willy On Wed, Mar 19, 2014 at 6:30 PM, Willy Martin Aguirre Rodriguez wrote: Hi http://aerogear.org/docs/specs/aerogear-server-push/ http://aerogear.org/push/ the idea is to implement Amazon Push, BlackBerry or Windows for aerogear-server-push I'd say the idea would be to implement at least two of them; e.g. Amazon and Windows; if time allows adding more would be even better. (the work is on the server, the ui, the documentation and examples) Does that sound good ? Greetings,Matthias From: marti1003 at hotmail.com To: aerogear-dev at lists.jboss.org Date: Tue, 18 Mar 2014 14:26:01 -0500 Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server About my experience: for mobile I am using cordova(phonegap) for android this include Jquery mobile and dev firerfox apps with backbonejs backend java play framework http://www.playframework.com/ (hibernate) and dynamic jasper I remember was made an app with j2me and servlets communication via sockets I will finish a project where connects two systems one of then is Oracle PeopleSoft and and Adryan Cosapi Data(http://www.cosapidata.com.pe/Adryan.asp) via webservices. here you are my github account https://github.com/marti1125 Regards Willy Date: Tue, 18 Mar 2014 18:27:28 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server On Tue, Mar 18, 2014 at 6:16 PM, Willy Martin Aguirre Rodriguez wrote: Yes! I really like to work with mobile technology awesome! Regarding the requested technologies (e.g. Amazon Push, BlackBerry or Windows), do you have experience in that area (e.g. development of apps and/or push APIs for them) ? Greetings,Matthias Date: Tue, 18 Mar 2014 17:48:11 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hello Willy, the AeroGear UnifiedPush server supports push notifications over a unified API for the following platforms: * Google Cloud Messaging (Android and Chrome)* APNs (iOS) ==> Safari is on the works (by Luke) * SimplePush (Firefox OS and polyfil for any browser) The goal of the suggested project would be adding support for other push networks:* Amazon Push* Windows Phone/Mobile * Black Berry Besides that we are happy to get support for other push networks as well. The main work would be the integration of those networks (server-side, admin UI, documentation and examples) Does that sound interesting to you ? Greetings,Matthias On Tue, Mar 18, 2014 at 5:15 PM, Willy Martin Aguirre Rodriguez wrote: ups sorry is this https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Support_new_Push_Networks_on_the_UnifiedPush_Server Date: Tue, 18 Mar 2014 16:59:08 +0100 From: scm.blanc at gmail.com To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server Hi,I think you should post that to the RHQ mailing list since it's a RHQ related project https://fedorahosted.org/mailman/listinfo/rhq-users Seb On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez wrote: Hi! I made some firefox os apps and I Java dev I really interesting in https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ Could you tell me more about this project? and how to make my proposal for this project? Regards Willy _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/102e61b1/attachment.html From matzew at apache.org Thu Mar 20 12:44:45 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Mar 2014 17:44:45 +0100 Subject: [aerogear-dev] gsoc2014 Support new Push Networks on the UnifiedPush Server In-Reply-To: References: Message-ID: Awesome! I'd really appreciate if the initial focus would be around * Windows Phone * Amazon Push :-) On Thu, Mar 20, 2014 at 5:37 PM, Willy Martin Aguirre Rodriguez < marti1003 at hotmail.com> wrote: > yes :), thanks you > > I am going to send my proposal > > ------------------------------ > Date: Thu, 20 Mar 2014 11:43:03 +0100 > > From: matzew at apache.org > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > Hello Willy > > > On Wed, Mar 19, 2014 at 6:30 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > Hi > > http://aerogear.org/docs/specs/aerogear-server-push/ > > http://aerogear.org/push/ > > the idea is to implement Amazon Push, BlackBerry or Windows for > aerogear-server-push > > > I'd say the idea would be to implement at least two of them; e.g. Amazon > and Windows; if time allows adding more would be even better. > (the work is on the server, the ui, the documentation and examples) > > Does that sound good ? > > Greetings, > Matthias > > > > > ------------------------------ > From: marti1003 at hotmail.com > To: aerogear-dev at lists.jboss.org > Date: Tue, 18 Mar 2014 14:26:01 -0500 > > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > > About my experience: > > for mobile I am using cordova(phonegap) for android this include Jquery > mobile and dev firerfox apps with backbonejs > backend java play framework http://www.playframework.com/ (hibernate) and > dynamic jasper > > I remember was made an app with j2me and servlets communication via > sockets > > I will finish a project where connects two systems one of then is Oracle > PeopleSoft and and Adryan Cosapi Data( > http://www.cosapidata.com.pe/Adryan.asp) via webservices. > > here you are my github account > > https://github.com/marti1125 > > Regards > Willy > > > ------------------------------ > Date: Tue, 18 Mar 2014 18:27:28 +0100 > From: matzew at apache.org > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > > > > On Tue, Mar 18, 2014 at 6:16 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > Yes! > > I really like to work with mobile technology > > > awesome! > > Regarding the requested technologies (e.g. Amazon Push, BlackBerry or > Windows), do you have experience in that area (e.g. development of apps > and/or push APIs for them) ? > > > Greetings, > Matthias > > > > > > ------------------------------ > Date: Tue, 18 Mar 2014 17:48:11 +0100 > From: matzew at apache.org > > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > Hello Willy, > > the AeroGear UnifiedPush server supports push notifications over a unified > API for the following platforms: > * Google Cloud Messaging (Android and Chrome) > * APNs (iOS) ==> Safari is on the works (by Luke) > * SimplePush (Firefox OS and polyfil for any browser) > > > The goal of the suggested project would be adding support for other push > networks: > * Amazon Push > * Windows Phone/Mobile > * Black Berry > > Besides that we are happy to get support for other push networks as well. > > > The main work would be the integration of those networks (server-side, > admin UI, documentation and examples) > > > Does that sound interesting to you ? > > > Greetings, > Matthias > > > > > On Tue, Mar 18, 2014 at 5:15 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > ups sorry is this > > https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Support_new_Push_Networks_on_the_UnifiedPush_Server > > ------------------------------ > Date: Tue, 18 Mar 2014 16:59:08 +0100 > From: scm.blanc at gmail.com > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] gsoc2014 Support new Push Networks on the > UnifiedPush Server > > > Hi, > I think you should post that to the RHQ mailing list since it's a RHQ > related project > https://fedorahosted.org/mailman/listinfo/rhq-users > > Seb > > > > On Tue, Mar 18, 2014 at 4:53 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > Hi! > > I made some firefox os apps and I Java dev > I really interesting in > > > https://community.jboss.org/wiki/GSOC14Ideas?_sscc=t#jive_content_id_Implement_a_big_screen_dashboard_for_RHQ > > Could you tell me more about this project? and how to make my proposal for > this project? > > Regards > Willy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- 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/20140320/f552e37c/attachment-0001.html From tolisemm at gmail.com Thu Mar 20 13:18:34 2014 From: tolisemm at gmail.com (tolis emmanouilidis) Date: Thu, 20 Mar 2014 19:18:34 +0200 Subject: [aerogear-dev] AeroGear.js + ES6 In-Reply-To: References: Message-ID: +1 for ES6 Do you think that ES6 classes will affect the way AeroGear.js library is structured? Thanks, Tolis 2014-03-20 16:50 GMT+02:00 Bruno Oliveira : > go for it, can't wait for ES7 and have a branch named "LEGEN...WAIT FOR > IT...DARY!" > > -- > abstractj > > On March 20, 2014 at 11:31:23 AM, Lucas Holmquist (lholmqui at redhat.com) > wrote: > > > Hey peeps, > > > > I've been seeing libraries such and Angular and Ember starting > > to author in ES6( the next iteration of javascript ) and then transpiling > > back to ES5( the current iteration of javascript ). > > > > So i've created a new branch called "get_to_tha_choppa" that > > will be tracking these changes to see if we can benefit from this. > > > > this could also help us in the quest for AMD/Browser Modules/New > > Fancy Term > > > > some related JIRA > > > > https://issues.jboss.org/browse/AGJS-149 > > > > incase people don't get the "get_to_tha_choppa" reference > > > > https://www.youtube.com/watch?v=Xs_OacEq2Sk > > > > > > -Luke > > > _______________________________________________ > 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/20140320/5060e9c2/attachment.html From tolisemm at gmail.com Thu Mar 20 13:21:00 2014 From: tolisemm at gmail.com (tolis emmanouilidis) Date: Thu, 20 Mar 2014 19:21:00 +0200 Subject: [aerogear-dev] UPS Java Client should support client authentication In-Reply-To: <20140318092656.656bfef5@kapy-ntb-x220> References: <1394247994174.a05c8174@Nodemailer> <1389062401.8617179.1394463229081.JavaMail.zimbra@redhat.com> <20140318092656.656bfef5@kapy-ntb-x220> Message-ID: Sure, I'll try to improve the tests after refactoring the existing code and performing some changes that Bruno recommended. Thanks, Tolis 2014-03-18 10:26 GMT+02:00 Karel Piwko : > Thanks Tolis, it looks good! We'd just need an additional test to verify > previous behavior is still valid, e.g. connection test was rewritten, it > should > have been added next to http. > > Many thanks! > > Karel > > On Mon, 17 Mar 2014 21:59:22 +0200 > tolis emmanouilidis wrote: > > > To follow up, the JIRA id is AGPUSH-559 and I've sent a PR for supporting > > custom truststores [1]. The integration tests using SSL and the custom > > aerogear.truststore passed. > > > > [1]: > https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/36 > > > > Thanks, > > Tolis > > > > > > 2014-03-10 20:50 GMT+02:00 Matthias Wessendorf : > > > > > > > > > > > On Monday, March 10, 2014, Bruno Oliveira wrote: > > > > > >> JIRA is enough as far as I can tell. > > > > > > > > > +1 on JIRA for tracking > > > > > > feel free to send PR as well > > > > > > Greetings, > > > Matthias > > > > > > > > >> > > >> -- > > >> abstractj > > >> > > >> On March 10, 2014 at 11:53:53 AM, Stefan Miklosovic ( > smikloso at redhat.com) > > >> wrote: > > >> > > Hi, > > >> > > > >> > so whats the "conclusion" for this? I would like to move forward > > >> > with other things. Is JIRA to track this sufficient? > > >> > > > >> > Stefan Miklosovic > > >> > Red Hat Brno - JBoss Mobile Platform > > >> > > >> _______________________________________________ > > >> aerogear-dev mailing list > > >> aerogear-dev at lists.jboss.org > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > >> > > > > > > > > > -- > > > Sent from Gmail Mobile > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140320/b0e348d2/attachment.html From lholmqui at redhat.com Thu Mar 20 13:27:16 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Thu, 20 Mar 2014 13:27:16 -0400 Subject: [aerogear-dev] AeroGear.js + ES6 In-Reply-To: References: Message-ID: <3DD039CA-843E-48E6-933C-C61571C89727@redhat.com> On Mar 20, 2014, at 1:18 PM, tolis emmanouilidis wrote: > +1 for ES6 > > Do you think that ES6 classes will affect the way AeroGear.js library is structured? maybe a little in the way we do inheritance. > > Thanks, > Tolis > > > 2014-03-20 16:50 GMT+02:00 Bruno Oliveira : > go for it, can?t wait for ES7 and have a branch named ?LEGEN?WAIT FOR IT?DARY!" > > -- > abstractj > > On March 20, 2014 at 11:31:23 AM, Lucas Holmquist (lholmqui at redhat.com) wrote: > > > Hey peeps, > > > > I've been seeing libraries such and Angular and Ember starting > > to author in ES6( the next iteration of javascript ) and then transpiling > > back to ES5( the current iteration of javascript ). > > > > So i've created a new branch called "get_to_tha_choppa" that > > will be tracking these changes to see if we can benefit from this. > > > > this could also help us in the quest for AMD/Browser Modules/New > > Fancy Term > > > > some related JIRA > > > > https://issues.jboss.org/browse/AGJS-149 > > > > incase people don't get the "get_to_tha_choppa" reference > > > > https://www.youtube.com/watch?v=Xs_OacEq2Sk > > > > > > -Luke > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140320/42eb1ba7/attachment.html From kontakt at neo-revolution.de Fri Mar 21 06:42:07 2014 From: kontakt at neo-revolution.de (nerevo) Date: Fri, 21 Mar 2014 03:42:07 -0700 (PDT) Subject: [aerogear-dev] How to use the plugin with phonegap remote build Message-ID: <1395398527808-7013.post@n5.nabble.com> I write sencha touch apps with phonegap plugins build with "phonegap remote build". How can I insert the push plugin? The doc says: cordova plugin add https://github.com/aerogear/aerogear-pushplugin-cordova.git But I use phonegap. I don't want to use cordova. What can I do to use this plugin and let it build remote? Thank you! -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/How-to-use-the-plugin-with-phonegap-remote-build-tp7013.html Sent from the aerogear-dev mailing list archive at Nabble.com. From kpiwko at redhat.com Fri Mar 21 07:32:17 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Fri, 21 Mar 2014 12:32:17 +0100 Subject: [aerogear-dev] Released 0.0.3 Cordova Push Plugin In-Reply-To: <98BB8816-A7B5-46FC-9956-E9A079D67FA5@redhat.com> References: <98BB8816-A7B5-46FC-9956-E9A079D67FA5@redhat.com> Message-ID: <20140321123217.5edcf5d1@kapy-ntb-x220> Thanks Erik, I've tested it on Android 2.3, 4.1, 4.2 and 4.4 yesterday and all went fine. Karel On Thu, 20 Mar 2014 17:12:05 +0100 Erik Jan de Wit wrote: > Hi all, > > We?re happy to announce that version 0.0.3 of the Push Plugin has been > released. The next release will include the new API so stay tuned. You can > download it from http://plugins.cordova.io or look at our website > http://aerogear.org/cordova/ > > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From cvasilak at gmail.com Fri Mar 21 07:43:46 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Fri, 21 Mar 2014 13:43:46 +0200 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> Message-ID: <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> Hi everyone, after discussion with Corinne, we have decided to pause the release of aerogear-ios this week, and release early next. The reason is that we would like the upcoming release to include dependency of the new aerogear-crypto changes that were incorporated this week[1], mainly the update of the symmetric encryption to use NaCI. We feel, that it makes sense to release both at the same time. For aerogear-ios, a minor ?private' API change is needed, but would like a bit of time for testing. Let us know your thoughts/concerns. Regards Christos [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 On Mar 18, 2014, at 9:37 AM, Corinne Krych wrote: > Hello iOS Friends, > > AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). > > To test it, open Podfile and point to the latest git branch > pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > > Help us make this release a success, give it a trial, and let us know how it goes for your project. > > ++ > Corinne > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From matzew at apache.org Fri Mar 21 07:55:14 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 21 Mar 2014 12:55:14 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> Message-ID: sounds good ! On Fri, Mar 21, 2014 at 12:43 PM, Christos Vasilakis wrote: > Hi everyone, > > after discussion with Corinne, we have decided to pause the release of > aerogear-ios this week, and release early next. The reason is that we would > like the upcoming release to include dependency of the new aerogear-crypto > changes that were incorporated this week[1], mainly the update of the > symmetric encryption to use NaCI. We feel, that it makes sense to release > both at the same time. > > For aerogear-ios, a minor 'private' API change is needed, but would like a > bit of time for testing. > > Let us know your thoughts/concerns. > > Regards > Christos > > [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 > > > On Mar 18, 2014, at 9:37 AM, Corinne Krych wrote: > > > Hello iOS Friends, > > > > AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to > release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and > AFNetworking 2.x (latest 2.2.1). > > > > To test it, open Podfile and point to the latest git branch > > pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > > > > Help us make this release a success, give it a trial, and let us know > how it goes for your project. > > > > ++ > > 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 > -- 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/20140321/a382568e/attachment-0001.html From daniel.bevenius at gmail.com Fri Mar 21 07:56:42 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Fri, 21 Mar 2014 12:56:42 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> Message-ID: sounds good On 21 March 2014 12:43, Christos Vasilakis wrote: > Hi everyone, > > after discussion with Corinne, we have decided to pause the release of > aerogear-ios this week, and release early next. The reason is that we would > like the upcoming release to include dependency of the new aerogear-crypto > changes that were incorporated this week[1], mainly the update of the > symmetric encryption to use NaCI. We feel, that it makes sense to release > both at the same time. > > For aerogear-ios, a minor 'private' API change is needed, but would like a > bit of time for testing. > > Let us know your thoughts/concerns. > > Regards > Christos > > [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 > > > On Mar 18, 2014, at 9:37 AM, Corinne Krych wrote: > > > Hello iOS Friends, > > > > AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to > release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and > AFNetworking 2.x (latest 2.2.1). > > > > To test it, open Podfile and point to the latest git branch > > pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > > > > Help us make this release a success, give it a trial, and let us know > how it goes for your project. > > > > ++ > > 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/20140321/a9c1dd79/attachment.html From bruno at abstractj.org Fri Mar 21 07:59:56 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 21 Mar 2014 08:59:56 -0300 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> Message-ID: Sounds good +1 On Fri, Mar 21, 2014 at 8:43 AM, Christos Vasilakis wrote: > Hi everyone, > > after discussion with Corinne, we have decided to pause the release of > aerogear-ios this week, and release early next. The reason is that we would > like the upcoming release to include dependency of the new aerogear-crypto > changes that were incorporated this week[1], mainly the update of the > symmetric encryption to use NaCI. We feel, that it makes sense to release > both at the same time. > > For aerogear-ios, a minor 'private' API change is needed, but would like a > bit of time for testing. > > Let us know your thoughts/concerns. > > Regards > Christos > > [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 > > > On Mar 18, 2014, at 9:37 AM, Corinne Krych wrote: > > > Hello iOS Friends, > > > > AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to > release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and > AFNetworking 2.x (latest 2.2.1). > > > > To test it, open Podfile and point to the latest git branch > > pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > > > > Help us make this release a success, give it a trial, and let us know > how it goes for your project. > > > > ++ > > 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 > -- -- "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/20140321/8fc70637/attachment.html From edewit at redhat.com Fri Mar 21 08:06:42 2014 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 21 Mar 2014 13:06:42 +0100 Subject: [aerogear-dev] How to use the plugin with phonegap remote build In-Reply-To: <1395398527808-7013.post@n5.nabble.com> References: <1395398527808-7013.post@n5.nabble.com> Message-ID: <2E524C1B-0CCA-4E46-B4B2-6DDEA2C64A86@redhat.com> Hi Nerevo, Unfortunately our plugins cannot be used on phonegap build. But this document http://aerogear.org/docs/guides/aerogear-push-cordova-ios/cordova-iOS-app/ describes how to use the ?standard? push plugin and how to configure it to use it with our UnifiedPush server. Use https://build.phonegap.com/plugins/324 to install the Push Plugin into your application. Hope that helps, Erik Jan On 21 Mar,2014, at 11:42 , nerevo wrote: > I write sencha touch apps with phonegap plugins build with "phonegap remote > build". > > How can I insert the push plugin? The doc says: > cordova plugin add > https://github.com/aerogear/aerogear-pushplugin-cordova.git > > But I use phonegap. I don't want to use cordova. > > What can I do to use this plugin and let it build remote? > > Thank you! > > > > -- > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/How-to-use-the-plugin-with-phonegap-remote-build-tp7013.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140321/7219e7c4/attachment.html From matzew at apache.org Fri Mar 21 10:10:00 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 21 Mar 2014 15:10:00 +0100 Subject: [aerogear-dev] Cordova: question on recent Push Plugin release Message-ID: Hello, a few days ago, the 0.0.3 version of our Cordova Push Plugin was released (see [1]). Now, on our github 'releases' folder we see the release was made available on March 17th (as of now it says "4 days ago"). Great! Looking at the Cordova Plugin Registry, I see it's there since four weeks: http://plugins.cordova.io/#/org.jboss.aerogear.cordova.push That's incorrect, as we officially released it a few days ago (see [1]). Also they are not exactly the same (in download size and content (just do a diff on the PushPlugin.m file). Anyways, I am wondering if it is possible to update the version on the Cordova Registry, so that we: a) ship the official release b) have both downloads (GH and Cordova.io) being the same Thanks! Matthias [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-March/006926.html -- 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/20140321/78953619/attachment.html From bruno at abstractj.org Fri Mar 21 12:03:42 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Fri, 21 Mar 2014 13:03:42 -0300 Subject: [aerogear-dev] AeroGear Crypto 0.1.3 Staged In-Reply-To: <20140320163939.43826ce8@kapy-ntb-x220> References: <20140320163939.43826ce8@kapy-ntb-x220> Message-ID: Ahoy, I?m planning to press ?that? button. Anyone testing? -- abstractj On March 20, 2014 at 12:39:48 PM, Karel Piwko (kpiwko at redhat.com) wrote: > > We'll give it a try and let you know tomorrow late afternoon CET > about the > results. > > Karel From kpiwko at redhat.com Fri Mar 21 12:14:20 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Fri, 21 Mar 2014 17:14:20 +0100 Subject: [aerogear-dev] AeroGear Crypto 0.1.3 Staged In-Reply-To: <20140320163939.43826ce8@kapy-ntb-x220> References: <20140320163939.43826ce8@kapy-ntb-x220> Message-ID: <20140321171420.1837b7cf@kapy-ntb-x220> On Thu, 20 Mar 2014 16:39:39 +0100 Karel Piwko wrote: > We'll give it a try and let you know tomorrow late afternoon CET about the > results. I haven't found any issues. I've tested unit test with various JDK versions (JDK6, JDK7, IBM JDK7, OpenJDK7, with or without NSS activated) and AG integration tests with Android 4.2 device and internal integration tests with Android 4.2 device and Android 4.1 emulator. That said, I believe there is some work on automation and coverage for integration tests. Press the button! > > Karel > > On Thu, 20 Mar 2014 01:14:48 -0300 > Bruno Oliveira wrote: > > > Good morning peeps, the project was staged under the following > > profile:?https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-2889/ > > > > It has fixes for Android platform. If you want to test it, try: > > > > -?https://github.com/aerogear/aerogear-android/pull/141 > > -?https://github.com/aerogear/aerogear-android-integration-tests/pull/26 > > > > I?m planning to release it on Friday, so if you find any critical issues, > > let me know. > > > > -- > > abstractj > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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 at passos.me Fri Mar 21 12:19:30 2014 From: daniel at passos.me (Daniel Passos) Date: Fri, 21 Mar 2014 13:19:30 -0300 Subject: [aerogear-dev] SQLite Store Order By and Auto Increment ID In-Reply-To: References: Message-ID: Hi Thiago, Sorry for my delay. AeroGear does not control the id value. This is delegated to IdGenerator, so it's your (developer) responsibility to control it. My sugestion is, store the last id used in a SharedPreferece or use UUID (the AeroGear DefaultIdGenator[1]). I have added an example using SharedPreference in AeroGear Android Cookbook[2] [1] https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/datamanager/DefaultIdGenerator.java [2] https://github.com/aerogear/aerogear-android-cookbook/pull/12 -- Passos On Mon, Mar 17, 2014 at 6:45 PM, Tiago Resende wrote: > The AeroGear isn't reading the last Id saved in database, so, it starts > over and over again, overwriting my old data every time a open my > application. > > > 2014-03-17 18:11 GMT-03:00 Daniel Passos : > >> Hi Thiago, >> >> Nice questions. Answers inline. >> >> On Sun, Mar 16, 2014 at 6:20 PM, Tiago Resende wrote: >> >>> Hi guys, thanks for the other day, you really helped me. >>> >>> I have two questions today. >>> >>> How can I perform a query using "order by" statement in SQLStore? >>> >>> I did a readAll, then I ordered in memory using Ordering. >>> >> >> Unfortunately. We don't have this option for now. >> >> >>> The second question is how can I indicate to AeroGear that it should use >>> an auto increment primary key for a table. I created an AutoGeneratorId >>> Class, but it's not working beautifully for SQLStore. I had to create an >>> update method and call it for every object, I didn't like it, but I >>> couldn't find a better solution reading the documentation. >>> >> >> No, who creates the id is always idGenerator. What's the problem? >> >> >>> I really appreciate your help. >>> >>> Thanks. >>> >>> -- >>> *Tiago de Carvalho Resende* >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > *Tiago de Carvalho Resende* > Desenvolvedor > > "O importante n?o ? saber fazer, > > ? saber de onde copiar." > > por Bernardo Esb?rard > > > > _______________________________________________ > 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/20140321/c54db924/attachment.html From kontakt at neo-revolution.de Fri Mar 21 13:32:13 2014 From: kontakt at neo-revolution.de (nerevo) Date: Fri, 21 Mar 2014 10:32:13 -0700 (PDT) Subject: [aerogear-dev] How to use the plugin with phonegap remote build In-Reply-To: <2E524C1B-0CCA-4E46-B4B2-6DDEA2C64A86@redhat.com> References: <1395398527808-7013.post@n5.nabble.com> <2E524C1B-0CCA-4E46-B4B2-6DDEA2C64A86@redhat.com> Message-ID: <1395423133696-7024.post@n5.nabble.com> Thank you! I tried to integrate this inside sencha touch, but aerogear.js needs jquery. Can I download an aerogear.js version without the need of jquery? Pure javascript? Thank you!!!! -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/How-to-use-the-plugin-with-phonegap-remote-build-tp7013p7024.html Sent from the aerogear-dev mailing list archive at Nabble.com. From lholmqui at redhat.com Fri Mar 21 14:48:32 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Fri, 21 Mar 2014 14:48:32 -0400 Subject: [aerogear-dev] How to use the plugin with phonegap remote build In-Reply-To: <1395423133696-7024.post@n5.nabble.com> References: <1395398527808-7013.post@n5.nabble.com> <2E524C1B-0CCA-4E46-B4B2-6DDEA2C64A86@redhat.com> <1395423133696-7024.post@n5.nabble.com> Message-ID: On Mar 21, 2014, at 1:32 PM, nerevo wrote: > Thank you! > > I tried to integrate this inside sencha touch, but aerogear.js needs jquery. > > Can I download an aerogear.js version without the need of jquery? Pure > javascript? Hello, currently aerogear.js is dependent on jQuery, but there is a JIRA to remove the jQuery requirement for the future > > > Thank you!!!! > > > > -- > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/How-to-use-the-plugin-with-phonegap-remote-build-tp7013p7024.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From miguel21op at gmail.com Fri Mar 21 15:42:30 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Fri, 21 Mar 2014 19:42:30 +0000 Subject: [aerogear-dev] How to use the plugin with phonegap remote build In-Reply-To: References: <1395398527808-7013.post@n5.nabble.com> <2E524C1B-0CCA-4E46-B4B2-6DDEA2C64A86@redhat.com> <1395423133696-7024.post@n5.nabble.com> Message-ID: On jQuery and Cordova: http://apachecordova.blogspot.pt/2012/11/who-is-murdering-phonegap-its-jquery.html On Fri, Mar 21, 2014 at 6:48 PM, Lucas Holmquist wrote: > On Mar 21, 2014, at 1:32 PM, nerevo wrote: > > > Thank you! > > > > I tried to integrate this inside sencha touch, but aerogear.js needs > jquery. > > > > Can I download an aerogear.js version without the need of jquery? Pure > > javascript? > > Hello, currently aerogear.js is dependent on jQuery, but there is a JIRA > to remove the jQuery requirement for the future > > > > > > > Thank you!!!! > > > > > > > > -- > > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/How-to-use-the-plugin-with-phonegap-remote-build-tp7013p7024.html > > Sent from the aerogear-dev mailing list archive at Nabble.com. > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140321/965ebbf7/attachment.html From mwringe at redhat.com Fri Mar 21 17:40:48 2014 From: mwringe at redhat.com (Matt Wringe) Date: Fri, 21 Mar 2014 17:40:48 -0400 Subject: [aerogear-dev] Exposing UPS Variants through the endpoints for application use Message-ID: <532CB1E0.8010802@redhat.com> I am trying to set up some integration in LiveOak with UPS so that LiveOak can send out push notifications. Currently I have the application's UPS configuration options stored in LiveOak (ie variant id, secret, gcm number, UPS url, etc) and the application fetches the options from there so that it can do the UPS registration. This is so we can manage the variants on the LiveOak side and not have to have them hard coded in a native application itself. Ideally, instead of us storing the variant options in LiveOak, it would be great if we could use the UPS endpoints to fetch the variant data directly. We could do this now using the endpoints and the admin account, but wondering if there is any option (or any planned option) to support having more read-only accounts to fetch this kind of data? Something like oauth scopes might would work really well here. Thanks, Matt Wringe From matzew at apache.org Fri Mar 21 18:02:28 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 21 Mar 2014 23:02:28 +0100 Subject: [aerogear-dev] Exposing UPS Variants through the endpoints for application use In-Reply-To: <532CB1E0.8010802@redhat.com> References: <532CB1E0.8010802@redhat.com> Message-ID: Hello Matt, On Fri, Mar 21, 2014 at 10:40 PM, Matt Wringe wrote: > I am trying to set up some integration in LiveOak with UPS so that > LiveOak can send out push notifications. > > Currently I have the application's UPS configuration options stored in > LiveOak (ie variant id, secret, gcm number, UPS url, etc) and the > application fetches the options from there so that it can do the UPS > registration. This is so we can manage the variants on the LiveOak side > and not have to have them hard coded in a native application itself. > > Ideally, instead of us storing the variant options in LiveOak, it would > be great if we could use the UPS endpoints to fetch the variant data > directly. We could do this now using the endpoints and the admin > account, yes - the account for the "push admin" would be the one to use - for now > but wondering if there is any option (or any planned option) to > support having more read-only accounts to fetch this kind of data? > Something like oauth scopes might would work really well here. > that's an interesting request. On a branch we started working on keycloak integration, so once that is complete, I guess it would be that kinda of place to add support for your request > > Thanks, > > Matt Wringe > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140321/85820fb9/attachment-0001.html From tolisemm at gmail.com Sun Mar 23 06:35:28 2014 From: tolisemm at gmail.com (tolis emmanouilidis) Date: Sun, 23 Mar 2014 12:35:28 +0200 Subject: [aerogear-dev] How to use the plugin with phonegap remote build In-Reply-To: References: <1395398527808-7013.post@n5.nabble.com> <2E524C1B-0CCA-4E46-B4B2-6DDEA2C64A86@redhat.com> <1395423133696-7024.post@n5.nabble.com> Message-ID: 2014-03-21 21:42 GMT+02:00 Miguel Lemos : > On jQuery and Cordova: > > > http://apachecordova.blogspot.pt/2012/11/who-is-murdering-phonegap-its-jquery.html > > > Afaik AeroGear.js is using jQuery.ajax in its Pipeline lib. I suppose that this decision was initially taken in order to avoid handling the different browsers syntax for AJAX. Miguel, the mentioned post talks about using jQuery Mobile in PhoneGap apps. To make it clear, there is not any dependency of AeroGear.js on jQuery Mobile. Besides that, this post is old (2012) and in my opinion most of its points are currently invalid. I agree that it would be nice to implement AGJS-70(Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. [1]: http://projects.jga.me/jquery-builder/ [2]: https://github.com/jgallen23/jquery-builder > > On Fri, Mar 21, 2014 at 6:48 PM, Lucas Holmquist wrote: > >> On Mar 21, 2014, at 1:32 PM, nerevo wrote: >> >> > Thank you! >> > >> > I tried to integrate this inside sencha touch, but aerogear.js needs >> jquery. >> > >> > Can I download an aerogear.js version without the need of jquery? Pure >> > javascript? >> >> Hello, currently aerogear.js is dependent on jQuery, but there is a JIRA >> to remove the jQuery requirement for the future >> >> > >> > >> > Thank you!!!! >> > >> > >> > >> > -- >> > View this message in context: >> http://aerogear-dev.1069024.n5.nabble.com/How-to-use-the-plugin-with-phonegap-remote-build-tp7013p7024.html >> > Sent from the aerogear-dev mailing list archive at Nabble.com. >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > 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/20140323/229f0f08/attachment.html From hrupp at redhat.com Mon Mar 24 03:32:21 2014 From: hrupp at redhat.com (Heiko W.Rupp) Date: Mon, 24 Mar 2014 08:32:21 +0100 Subject: [aerogear-dev] [android] pipeline.get() and Services? Message-ID: <75E0E576-1DE5-4139-986E-B85B73C700A8@redhat.com> Hey, [ this is with 1.3.1 ] Pipeline.get(name, ..) allows to use Fragments and Activities as "callbacks". What is the recommended way to use that inside a Service? >From looking at the code I think the logic inside LoaderAdapter could accept the AbstractCallback as sort of "fallback" for cases that are neither Activity nor Fragment. Thanks Heiko From daniel.bevenius at gmail.com Mon Mar 24 03:55:21 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 24 Mar 2014 08:55:21 +0100 Subject: [aerogear-dev] Team meeting agenda Message-ID: http://oksoclap.com/p/aerogear-team-mgt-20140324 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140324/61ad11e8/attachment.html From lholmqui at redhat.com Mon Mar 24 08:29:40 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 08:29:40 -0400 Subject: [aerogear-dev] How to use the plugin with phonegap remote build In-Reply-To: References: <1395398527808-7013.post@n5.nabble.com> <2E524C1B-0CCA-4E46-B4B2-6DDEA2C64A86@redhat.com> <1395423133696-7024.post@n5.nabble.com> Message-ID: <05615CC7-6562-4D13-886D-D637FAEB2753@redhat.com> On Mar 23, 2014, at 6:35 AM, tolis emmanouilidis wrote: > 2014-03-21 21:42 GMT+02:00 Miguel Lemos : > On jQuery and Cordova: > > http://apachecordova.blogspot.pt/2012/11/who-is-murdering-phonegap-its-jquery.html > > > > Afaik AeroGear.js is using jQuery.ajax in its Pipeline lib. I suppose that this decision was initially taken in order to avoid handling the different browsers syntax for AJAX. Miguel, the mentioned post talks about using jQuery Mobile in PhoneGap apps. To make it clear, there is not any dependency of AeroGear.js on jQuery Mobile. Besides that, this post is old (2012) and in my opinion most of its points are currently invalid. agreed, a lot has changed in 2 years > > I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. I'm going to move these thoughts to another ML thread. > > [1]: http://projects.jga.me/jquery-builder/ > [2]: https://github.com/jgallen23/jquery-builder > > > On Fri, Mar 21, 2014 at 6:48 PM, Lucas Holmquist wrote: > On Mar 21, 2014, at 1:32 PM, nerevo wrote: > > > Thank you! > > > > I tried to integrate this inside sencha touch, but aerogear.js needs jquery. > > > > Can I download an aerogear.js version without the need of jquery? Pure > > javascript? > > Hello, currently aerogear.js is dependent on jQuery, but there is a JIRA to remove the jQuery requirement for the future > > > > > > > Thank you!!!! > > > > > > > > -- > > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/How-to-use-the-plugin-with-phonegap-remote-build-tp7013p7024.html > > Sent from the aerogear-dev mailing list archive at Nabble.com. > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140324/2c2427c5/attachment.html From miguel21op at gmail.com Mon Mar 24 08:35:29 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 24 Mar 2014 12:35:29 +0000 Subject: [aerogear-dev] How to use the plugin with phonegap remote build In-Reply-To: <05615CC7-6562-4D13-886D-D637FAEB2753@redhat.com> References: <1395398527808-7013.post@n5.nabble.com> <2E524C1B-0CCA-4E46-B4B2-6DDEA2C64A86@redhat.com> <1395423133696-7024.post@n5.nabble.com> <05615CC7-6562-4D13-886D-D637FAEB2753@redhat.com> Message-ID: Anyway: jQuery (Sencha, etc.) is just another library overloading the already bloated Cordova, IMO. I think it's useless most of the times, and it would be better if we could pass without it. Enviado do meu iPhone No dia 24/03/2014, ?s 12:29, Lucas Holmquist escreveu: > >> On Mar 23, 2014, at 6:35 AM, tolis emmanouilidis wrote: >> >> 2014-03-21 21:42 GMT+02:00 Miguel Lemos : >>> On jQuery and Cordova: >>> >>> http://apachecordova.blogspot.pt/2012/11/who-is-murdering-phonegap-its-jquery.html >> >> Afaik AeroGear.js is using jQuery.ajax in its Pipeline lib. I suppose that this decision was initially taken in order to avoid handling the different browsers syntax for AJAX. Miguel, the mentioned post talks about using jQuery Mobile in PhoneGap apps. To make it clear, there is not any dependency of AeroGear.js on jQuery Mobile. Besides that, this post is old (2012) and in my opinion most of its points are currently invalid. > agreed, a lot has changed in 2 years > > >> >> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. > > I'm going to move these thoughts to another ML thread. > > >> >> [1]: http://projects.jga.me/jquery-builder/ >> [2]: https://github.com/jgallen23/jquery-builder >> >>> >>>> On Fri, Mar 21, 2014 at 6:48 PM, Lucas Holmquist wrote: >>>> On Mar 21, 2014, at 1:32 PM, nerevo wrote: >>>> >>>> > Thank you! >>>> > >>>> > I tried to integrate this inside sencha touch, but aerogear.js needs jquery. >>>> > >>>> > Can I download an aerogear.js version without the need of jquery? Pure >>>> > javascript? >>>> >>>> Hello, currently aerogear.js is dependent on jQuery, but there is a JIRA to remove the jQuery requirement for the future >>>> >>>> > >>>> > >>>> > Thank you!!!! >>>> > >>>> > >>>> > >>>> > -- >>>> > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/How-to-use-the-plugin-with-phonegap-remote-build-tp7013p7024.html >>>> > Sent from the aerogear-dev mailing list archive at Nabble.com. >>>> > _______________________________________________ >>>> > aerogear-dev mailing list >>>> > aerogear-dev at lists.jboss.org >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140324/d97626d6/attachment-0001.html From lholmqui at redhat.com Mon Mar 24 09:03:41 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 09:03:41 -0400 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion Message-ID: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> > I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140324/ba04f529/attachment.html From lholmqui at redhat.com Mon Mar 24 09:06:34 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 09:06:34 -0400 Subject: [aerogear-dev] How to use the plugin with phonegap remote build In-Reply-To: <05615CC7-6562-4D13-886D-D637FAEB2753@redhat.com> References: <1395398527808-7013.post@n5.nabble.com> <2E524C1B-0CCA-4E46-B4B2-6DDEA2C64A86@redhat.com> <1395423133696-7024.post@n5.nabble.com> <05615CC7-6562-4D13-886D-D637FAEB2753@redhat.com> Message-ID: On Mar 24, 2014, at 8:29 AM, Lucas Holmquist wrote: > > On Mar 23, 2014, at 6:35 AM, tolis emmanouilidis wrote: > >> 2014-03-21 21:42 GMT+02:00 Miguel Lemos : >> On jQuery and Cordova: >> >> http://apachecordova.blogspot.pt/2012/11/who-is-murdering-phonegap-its-jquery.html >> >> >> >> Afaik AeroGear.js is using jQuery.ajax in its Pipeline lib. I suppose that this decision was initially taken in order to avoid handling the different browsers syntax for AJAX. Miguel, the mentioned post talks about using jQuery Mobile in PhoneGap apps. To make it clear, there is not any dependency of AeroGear.js on jQuery Mobile. Besides that, this post is old (2012) and in my opinion most of its points are currently invalid. > agreed, a lot has changed in 2 years > > >> >> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. > > I'm going to move these thoughts to another ML thread. > jquery removal discussion here http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-js-without-jQuery-Discussion-td7034.html > >> >> [1]: http://projects.jga.me/jquery-builder/ >> [2]: https://github.com/jgallen23/jquery-builder >> >> >> On Fri, Mar 21, 2014 at 6:48 PM, Lucas Holmquist wrote: >> On Mar 21, 2014, at 1:32 PM, nerevo wrote: >> >> > Thank you! >> > >> > I tried to integrate this inside sencha touch, but aerogear.js needs jquery. >> > >> > Can I download an aerogear.js version without the need of jquery? Pure >> > javascript? >> >> Hello, currently aerogear.js is dependent on jQuery, but there is a JIRA to remove the jQuery requirement for the future >> >> > >> > >> > Thank you!!!! >> > >> > >> > >> > -- >> > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/How-to-use-the-plugin-with-phonegap-remote-build-tp7013p7024.html >> > Sent from the aerogear-dev mailing list archive at Nabble.com. >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev at lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140324/ce66285b/attachment.html From miguel21op at gmail.com Mon Mar 24 09:25:49 2014 From: miguel21op at gmail.com (Miguel Lemos) Date: Mon, 24 Mar 2014 13:25:49 +0000 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: Sorry, I don't understand why jQuery is needed to implement Ajax. We use Ajax to perform many tasks (both for mobile and desktop) and we NEVER use jQuery. On Mon, Mar 24, 2014 at 1:03 PM, Lucas Holmquist wrote: > I agree that it would be nice to implement AGJS-70 (Investigate > removing jQuery requirement). Meanwhile, there is an open source project on > GitHub that claims to offer a custom builder for jQuery in order to include > only the modules needed [1] [2]. I haven't tried it yet but maybe we could > create a custom jQuery build which includes only the parts currently needed > in AeroGear. This would mean a smaller size of the jQuery dependency. > > > The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax > and the promise implementation. > > i know we can make custom builds of jQuery pretty easily( building from > source ), but i don't really want to bundle it within our lib. > > and i don't think with bower we can do this easily. although they did just > add a post install hook, so perhaps that could be something to look at. > > Datamanager only uses the promise implementation of jQuery( and some > random thing for the filter method, which could probably be updated ). > Promises are starting to become available natively in browsers and jQuery > doesn't use the Promise/A+ spec, so it could be harder to fallback without > a shim of some kind > > > while i don't really want to reinvent the wheel in terms of Ajax, it > might be interesting to take a look. I think in a previous ML thread about > what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, > with exception for multipart > > > > > > > > _______________________________________________ > 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/20140324/34eb421b/attachment.html From lholmqui at redhat.com Mon Mar 24 09:29:09 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 09:29:09 -0400 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: On Mar 24, 2014, at 9:25 AM, Miguel Lemos wrote: > Sorry, I don't understand why jQuery is needed to implement Ajax. We use Ajax to perform many tasks (both for mobile and desktop) and we NEVER use jQuery. we are using the jQuery.Ajax library to our ajax calls, make sense? > > > On Mon, Mar 24, 2014 at 1:03 PM, Lucas Holmquist wrote: >> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. > > The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. > > i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. > > and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. > > Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind > > > while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart > > > > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140324/74e7f338/attachment-0001.html From matzew at apache.org Mon Mar 24 09:39:45 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 24 Mar 2014 14:39:45 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: > I agree that it would be nice to implement AGJS-70 (Investigate > removing jQuery requirement). Meanwhile, there is an open source project on > GitHub that claims to offer a custom builder for jQuery in order to include > only the modules needed [1] [2]. I haven't tried it yet but maybe we could > create a custom jQuery build which includes only the parts currently needed > in AeroGear. This would mean a smaller size of the jQuery dependency. > > > The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax > and the promise implementation. > > i know we can make custom builds of jQuery pretty easily( building from > source ), but i don't really want to bundle it within our lib. > > and i don't think with bower we can do this easily. although they did just > add a post install hook, so perhaps that could be something to look at. > > Datamanager only uses the promise implementation of jQuery( and some > random thing for the filter method, which could probably be updated ). > Promises are starting to become available natively in browsers and jQuery > doesn't use the Promise/A+ spec, so it could be harder to fallback without > a shim of some kind > sounds reasonable to 'wait' on the promise side of things, and use that bit in the datamanager > > > while i don't really want to reinvent the wheel in terms of Ajax, it > might be interesting to take a look. > Yeah, IMO worth to look there, for reducing dependencies -M > I think in a previous ML thread about what 2.0 looked like, that > Pipeline would maybe just be a JSON only thing, with exception for multipart > > > > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140324/4bc881d7/attachment.html From tolisemm at gmail.com Mon Mar 24 10:10:14 2014 From: tolisemm at gmail.com (tolis emmanouilidis) Date: Mon, 24 Mar 2014 16:10:14 +0200 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : > > > > On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: > >> I agree that it would be nice to implement AGJS-70 (Investigate >> removing jQuery requirement). Meanwhile, there is an open source project on >> GitHub that claims to offer a custom builder for jQuery in order to include >> only the modules needed [1] [2]. I haven't tried it yet but maybe we could >> create a custom jQuery build which includes only the parts currently needed >> in AeroGear. This would mean a smaller size of the jQuery dependency. >> >> >> The AG lib depends on a few parts of jQuery, the biggest being >> jQuery.Ajax and the promise implementation. >> >> i know we can make custom builds of jQuery pretty easily( building from >> source ), but i don't really want to bundle it within our lib. >> >> and i don't think with bower we can do this easily. although they did >> just add a post install hook, so perhaps that could be something to look at. >> >> Datamanager only uses the promise implementation of jQuery( and some >> random thing for the filter method, which could probably be updated ). >> > > Promises are starting to become available natively in browsers and jQuery >> doesn't use the Promise/A+ spec, so it could be harder to fallback without >> a shim of some kind >> > Good to know. Thanks for providing this info. > > sounds reasonable to 'wait' on the promise side of things, and use that > bit in the datamanager > +1 >> >> while i don't really want to reinvent the wheel in terms of Ajax, it >> might be interesting to take a look. >> > > Yeah, IMO worth to look there, for reducing dependencies > > -M > > > > > >> I think in a previous ML thread about what 2.0 looked like, that >> Pipeline would maybe just be a JSON only thing, with exception for multipart >> >> >> @Lucas Thanks for making things clear > >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140324/cb593737/attachment.html From daniel at passos.me Mon Mar 24 10:10:50 2014 From: daniel at passos.me (Daniel Passos) Date: Mon, 24 Mar 2014 11:10:50 -0300 Subject: [aerogear-dev] [android] pipeline.get() and Services? In-Reply-To: <75E0E576-1DE5-4139-986E-B85B73C700A8@redhat.com> References: <75E0E576-1DE5-4139-986E-B85B73C700A8@redhat.com> Message-ID: Hi Heiko, Pipeline.get(name, ..) is a method to return a PipeLoader (a Pipe wrapper using Loaders) instead a Pipe.? Loaders[1] were designed for activities and fragments in order to cleanly handle configuration changes that occur in Activites and Fragments. So, for service you need to use a Pipe (Pipeline.get(name)) and AbstractCallback (or Callback) [1] http://developer.android.com/guide/components/loaders.html --? Daniel Passos On March 24, 2014 at 4:32:57 AM, Heiko W.Rupp (hrupp at redhat.com) wrote: Hey, [ this is with 1.3.1 ] Pipeline.get(name, ..) allows to use Fragments and Activities as "callbacks". What is the recommended way to use that inside a Service? >From looking at the code I think the logic inside LoaderAdapter could accept the AbstractCallback as sort of "fallback" for cases that are neither Activity nor Fragment. Thanks Heiko -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140324/4df3c34d/attachment.html From cvasilak at gmail.com Mon Mar 24 10:18:09 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 24 Mar 2014 16:18:09 +0200 Subject: [aerogear-dev] Team meeting agenda In-Reply-To: References: Message-ID: <7FE3925C-8503-499B-A612-CA100BFDB4E8@gmail.com> FYI [16:16:38] Meeting ended Mon Mar 24 14:03:35 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) [16:16:38] Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-24-13.48.html [16:16:38] Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-24-13.48.txt [16:16:38] Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-24-13.48.log.html On Mar 24, 2014, at 9:55 AM, Daniel Bevenius wrote: > http://oksoclap.com/p/aerogear-team-mgt-20140324 > > > _______________________________________________ > 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/20140324/a9bafc1a/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140324/a9bafc1a/attachment-0001.bin From lholmqui at redhat.com Mon Mar 24 11:05:24 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 11:05:24 -0400 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis wrote: > 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : > > > > On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. > > The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. > > i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. > > and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. > > Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). > > > Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind > > Good to know. Thanks for providing this info. > > > sounds reasonable to 'wait' on the promise side of things, and use that bit in the datamanager > > +1 there are other promise implementations that we could use, that are to spec, such as Q and RSVP, here is the link to the HTML5 rocks article http://www.html5rocks.com/en/tutorials/es6/promises/ > > > > while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. > > Yeah, IMO worth to look there, for reducing dependencies > > -M > > > > > I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart > > > > @Lucas Thanks for making things clear > > > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140324/046e14e3/attachment.html From scm.blanc at gmail.com Mon Mar 24 11:12:46 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 24 Mar 2014 16:12:46 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: > I agree that it would be nice to implement AGJS-70 (Investigate > removing jQuery requirement). Meanwhile, there is an open source project on > GitHub that claims to offer a custom builder for jQuery in order to include > only the modules needed [1] [2]. I haven't tried it yet but maybe we could > create a custom jQuery build which includes only the parts currently needed > in AeroGear. This would mean a smaller size of the jQuery dependency. > > > The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax > and the promise implementation. > > i know we can make custom builds of jQuery pretty easily( building from > source ), but i don't really want to bundle it within our lib. > > and i don't think with bower we can do this easily. although they did just > add a post install hook, so perhaps that could be something to look at. > > Datamanager only uses the promise implementation of jQuery( and some > random thing for the filter method, which could probably be updated ). > Promises are starting to become available natively in browsers and jQuery > doesn't use the Promise/A+ spec, so it could be harder to fallback without > a shim of some kind > > > while i don't really want to reinvent the wheel in terms of Ajax, it > might be interesting to take a look. I think in a previous ML thread about > what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, > with exception for multipart > Do you mean here relying on a "lighter" Ajax lib or just refactoring it using plain old XmlHttpRequest ? > > > > > > > _______________________________________________ > 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/20140324/f95401d7/attachment.html From lholmqui at redhat.com Mon Mar 24 11:15:31 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 11:15:31 -0400 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: <7856FBD5-28C2-41AC-8D49-9C43825FF9D7@redhat.com> On Mar 24, 2014, at 11:12 AM, Sebastien Blanc wrote: > > > > On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. > > The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. > > i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. > > and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. > > Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind > > > while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart > > Do you mean here relying on a "lighter" Ajax lib or just refactoring it using plain old XmlHttpRequest ? we would have an internal AeroGear.Ajax( or something like that ) as our "lighter" ajax lib that used plain xmlhttprequests > > > > > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140324/200d147d/attachment.html From scm.blanc at gmail.com Mon Mar 24 11:14:28 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 24 Mar 2014 16:14:28 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: > > On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis > wrote: > > 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : > >> >> >> >> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >> >>> I agree that it would be nice to implement AGJS-70 (Investigate >>> removing jQuery requirement). Meanwhile, there is an open source project on >>> GitHub that claims to offer a custom builder for jQuery in order to include >>> only the modules needed [1] [2]. I haven't tried it yet but maybe we could >>> create a custom jQuery build which includes only the parts currently needed >>> in AeroGear. This would mean a smaller size of the jQuery dependency. >>> >>> >>> The AG lib depends on a few parts of jQuery, the biggest being >>> jQuery.Ajax and the promise implementation. >>> >>> i know we can make custom builds of jQuery pretty easily( building from >>> source ), but i don't really want to bundle it within our lib. >>> >>> and i don't think with bower we can do this easily. although they did >>> just add a post install hook, so perhaps that could be something to look at. >>> >>> Datamanager only uses the promise implementation of jQuery( and some >>> random thing for the filter method, which could probably be updated ). >>> >> > > >> Promises are starting to become available natively in browsers and jQuery >>> doesn't use the Promise/A+ spec, so it could be harder to fallback without >>> a shim of some kind >>> >> > Good to know. Thanks for providing this info. > > >> >> sounds reasonable to 'wait' on the promise side of things, and use that >> bit in the datamanager >> > > +1 > > > there are other promise implementations that we could use, that are to > spec, such as Q and RSVP, here is the link to the HTML5 rocks article > http://www.html5rocks.com/en/tutorials/es6/promises/ > These last days I have been playing with the library When provided by Cujo, it's maybe also worth looking https://github.com/cujojs/when > > > >>> >>> while i don't really want to reinvent the wheel in terms of Ajax, it >>> might be interesting to take a look. >>> >> >> Yeah, IMO worth to look there, for reducing dependencies >> >> -M >> >> >> > >> >> >>> I think in a previous ML thread about what 2.0 looked like, that >>> Pipeline would maybe just be a JSON only thing, with exception for multipart >>> >>> >>> > @Lucas Thanks for making things clear > > >> >>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140324/bdaed4eb/attachment-0001.html From matzew at apache.org Mon Mar 24 11:25:19 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 24 Mar 2014 16:25:19 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: <7856FBD5-28C2-41AC-8D49-9C43825FF9D7@redhat.com> References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <7856FBD5-28C2-41AC-8D49-9C43825FF9D7@redhat.com> Message-ID: On Mon, Mar 24, 2014 at 4:15 PM, Lucas Holmquist wrote: > > On Mar 24, 2014, at 11:12 AM, Sebastien Blanc wrote: > > > > > On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: > >> I agree that it would be nice to implement AGJS-70 (Investigate >> removing jQuery requirement). Meanwhile, there is an open source project on >> GitHub that claims to offer a custom builder for jQuery in order to include >> only the modules needed [1] [2]. I haven't tried it yet but maybe we could >> create a custom jQuery build which includes only the parts currently needed >> in AeroGear. This would mean a smaller size of the jQuery dependency. >> >> >> The AG lib depends on a few parts of jQuery, the biggest being >> jQuery.Ajax and the promise implementation. >> >> i know we can make custom builds of jQuery pretty easily( building from >> source ), but i don't really want to bundle it within our lib. >> >> and i don't think with bower we can do this easily. although they did >> just add a post install hook, so perhaps that could be something to look at. >> >> Datamanager only uses the promise implementation of jQuery( and some >> random thing for the filter method, which could probably be updated ). >> Promises are starting to become available natively in browsers and jQuery >> doesn't use the Promise/A+ spec, so it could be harder to fallback without >> a shim of some kind >> >> >> while i don't really want to reinvent the wheel in terms of Ajax, it >> might be interesting to take a look. I think in a previous ML thread about >> what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, >> with exception for multipart >> > > Do you mean here relying on a "lighter" Ajax lib or just refactoring it > using plain old XmlHttpRequest ? > > > we would have an internal AeroGear.Ajax( or something like that ) as our > "lighter" ajax lib that used plain xmlhttprequests > +1 on XHR usage - no other framework > > > > >> >> >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140324/0b19497c/attachment.html From matzew at apache.org Mon Mar 24 11:26:46 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 24 Mar 2014 16:26:46 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: > > > > On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: > >> >> On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis >> wrote: >> >> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >> >>> >>> >>> >>> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>> >>>> I agree that it would be nice to implement AGJS-70 (Investigate >>>> removing jQuery requirement). Meanwhile, there is an open source project on >>>> GitHub that claims to offer a custom builder for jQuery in order to include >>>> only the modules needed [1] [2]. I haven't tried it yet but maybe we could >>>> create a custom jQuery build which includes only the parts currently needed >>>> in AeroGear. This would mean a smaller size of the jQuery dependency. >>>> >>>> >>>> The AG lib depends on a few parts of jQuery, the biggest being >>>> jQuery.Ajax and the promise implementation. >>>> >>>> i know we can make custom builds of jQuery pretty easily( building from >>>> source ), but i don't really want to bundle it within our lib. >>>> >>>> and i don't think with bower we can do this easily. although they did >>>> just add a post install hook, so perhaps that could be something to look at. >>>> >>>> Datamanager only uses the promise implementation of jQuery( and some >>>> random thing for the filter method, which could probably be updated ). >>>> >>> >> >> >>> Promises are starting to become available natively in browsers and >>>> jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback >>>> without a shim of some kind >>>> >>> >> Good to know. Thanks for providing this info. >> >> >>> >>> sounds reasonable to 'wait' on the promise side of things, and use that >>> bit in the datamanager >>> >> >> +1 >> >> >> there are other promise implementations that we could use, that are to >> spec, such as Q and RSVP, here is the link to the HTML5 rocks article >> http://www.html5rocks.com/en/tutorials/es6/promises/ >> > > These last days I have been playing with the library When provided by > Cujo, it's maybe also worth looking https://github.com/cujojs/when > not sure I see value in using a different library as a temporary thing. Once the API is part of the browser platform, the need for [yet another js lib] goes away. > > >> >> >> >>>> >>>> while i don't really want to reinvent the wheel in terms of Ajax, it >>>> might be interesting to take a look. >>>> >>> >>> Yeah, IMO worth to look there, for reducing dependencies >>> >>> -M >>> >>> >>> >> >>> >>> >>>> I think in a previous ML thread about what 2.0 looked like, that >>>> Pipeline would maybe just be a JSON only thing, with exception for multipart >>>> >>>> >>>> >> @Lucas Thanks for making things clear >> >> >>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140324/8a438c00/attachment.html From scm.blanc at gmail.com Mon Mar 24 11:26:51 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 24 Mar 2014 16:26:51 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <7856FBD5-28C2-41AC-8D49-9C43825FF9D7@redhat.com> Message-ID: On Mon, Mar 24, 2014 at 4:25 PM, Matthias Wessendorf wrote: > > > > On Mon, Mar 24, 2014 at 4:15 PM, Lucas Holmquist wrote: > >> >> On Mar 24, 2014, at 11:12 AM, Sebastien Blanc >> wrote: >> >> >> >> >> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >> >>> I agree that it would be nice to implement AGJS-70 (Investigate >>> removing jQuery requirement). Meanwhile, there is an open source project on >>> GitHub that claims to offer a custom builder for jQuery in order to include >>> only the modules needed [1] [2]. I haven't tried it yet but maybe we could >>> create a custom jQuery build which includes only the parts currently needed >>> in AeroGear. This would mean a smaller size of the jQuery dependency. >>> >>> >>> The AG lib depends on a few parts of jQuery, the biggest being >>> jQuery.Ajax and the promise implementation. >>> >>> i know we can make custom builds of jQuery pretty easily( building from >>> source ), but i don't really want to bundle it within our lib. >>> >>> and i don't think with bower we can do this easily. although they did >>> just add a post install hook, so perhaps that could be something to look at. >>> >>> Datamanager only uses the promise implementation of jQuery( and some >>> random thing for the filter method, which could probably be updated ). >>> Promises are starting to become available natively in browsers and jQuery >>> doesn't use the Promise/A+ spec, so it could be harder to fallback without >>> a shim of some kind >>> >>> >>> while i don't really want to reinvent the wheel in terms of Ajax, it >>> might be interesting to take a look. I think in a previous ML thread about >>> what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, >>> with exception for multipart >>> >> >> Do you mean here relying on a "lighter" Ajax lib or just refactoring it >> using plain old XmlHttpRequest ? >> >> >> we would have an internal AeroGear.Ajax( or something like that ) as our >> "lighter" ajax lib that used plain xmlhttprequests >> > > > +1 on XHR usage - no other framework > +9001 \o/ > > >> >> >> >> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140324/9735b795/attachment-0001.html From scm.blanc at gmail.com Mon Mar 24 11:55:18 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 24 Mar 2014 16:55:18 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf wrote: > > > > On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: > >> >> >> >> On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: >> >>> >>> On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis >>> wrote: >>> >>> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >>> >>>> >>>> >>>> >>>> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>>> >>>>> I agree that it would be nice to implement AGJS-70 (Investigate >>>>> removing jQuery requirement). Meanwhile, there is an open source project on >>>>> GitHub that claims to offer a custom builder for jQuery in order to include >>>>> only the modules needed [1] [2]. I haven't tried it yet but maybe we could >>>>> create a custom jQuery build which includes only the parts currently needed >>>>> in AeroGear. This would mean a smaller size of the jQuery dependency. >>>>> >>>>> >>>>> The AG lib depends on a few parts of jQuery, the biggest being >>>>> jQuery.Ajax and the promise implementation. >>>>> >>>>> i know we can make custom builds of jQuery pretty easily( building >>>>> from source ), but i don't really want to bundle it within our lib. >>>>> >>>>> and i don't think with bower we can do this easily. although they did >>>>> just add a post install hook, so perhaps that could be something to look at. >>>>> >>>>> Datamanager only uses the promise implementation of jQuery( and some >>>>> random thing for the filter method, which could probably be updated ). >>>>> >>>> >>> >>> >>>> Promises are starting to become available natively in browsers and >>>>> jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback >>>>> without a shim of some kind >>>>> >>>> >>> Good to know. Thanks for providing this info. >>> >>> >>>> >>>> sounds reasonable to 'wait' on the promise side of things, and use that >>>> bit in the datamanager >>>> >>> >>> +1 >>> >>> >>> there are other promise implementations that we could use, that are to >>> spec, such as Q and RSVP, here is the link to the HTML5 rocks article >>> http://www.html5rocks.com/en/tutorials/es6/promises/ >>> >> >> These last days I have been playing with the library When provided by >> Cujo, it's maybe also worth looking https://github.com/cujojs/when >> > > not sure I see value in using a different library as a temporary thing. > Once the API is part of the browser platform, the need for [yet another js > lib] goes away. > I know but I'm more concerned about "Once the API is part of the browser platform" When will that happen and does it match with our roadmap ? Was also to offer a polyfill for older browser if we want to keep supporting them. > > >> >> >>> >>> >>> >>>>> >>>>> while i don't really want to reinvent the wheel in terms of Ajax, it >>>>> might be interesting to take a look. >>>>> >>>> >>>> Yeah, IMO worth to look there, for reducing dependencies >>>> >>>> -M >>>> >>>> >>>> >>> >>>> >>>> >>>>> I think in a previous ML thread about what 2.0 looked like, that >>>>> Pipeline would maybe just be a JSON only thing, with exception for multipart >>>>> >>>>> >>>>> >>> @Lucas Thanks for making things clear >>> >>> >>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > 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/20140324/06979eb3/attachment.html From lholmqui at redhat.com Mon Mar 24 12:01:38 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 12:01:38 -0400 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> Message-ID: <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: > > > > On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf wrote: > > > > On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: > > > > On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: > > On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis wrote: > >> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >> >> >> >> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. >> >> The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. >> >> i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. >> >> and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. >> >> Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). >> >> >> Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind >> >> Good to know. Thanks for providing this info. >> >> >> sounds reasonable to 'wait' on the promise side of things, and use that bit in the datamanager >> >> +1 > > there are other promise implementations that we could use, that are to spec, such as Q and RSVP, here is the link to the HTML5 rocks article > http://www.html5rocks.com/en/tutorials/es6/promises/ > > These last days I have been playing with the library When provided by Cujo, it's maybe also worth looking https://github.com/cujojs/when > > not sure I see value in using a different library as a temporary thing. Once the API is part of the browser platform, the need for [yet another js lib] goes away. > I know but I'm more concerned about "Once the API is part of the browser platform" When will that happen and does it match with our roadmap ? Was also to offer a polyfill for older browser if we want to keep supporting them. > i will have to update the roadmap. 2.0 would be a nice time to "fully" switch, but we can start experimenting now and maybe for 1.5 can have some implemenation for data manager only. Current Chrome has Promise's enable by default and it looks like FireFox 29( next version ) will too. Safari and IE are in dev i believe for fallback we can still make use of jQuery i think because of this method here "Promise.cast", although the closest lib to the spec is RSVP( maybe this could be the 2.0 fallback if we remove jQuery from the whole lib ) > > > > >> >> >> >> while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. >> >> Yeah, IMO worth to look there, for reducing dependencies >> >> -M >> >> >> >> >> I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart >> >> >> >> @Lucas Thanks for making things clear >> >> >> >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140324/43350682/attachment-0001.html From lholmqui at redhat.com Mon Mar 24 12:07:20 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 12:07:20 -0400 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> Message-ID: <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> On Mar 24, 2014, at 12:01 PM, Lucas Holmquist wrote: > > On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: > >> >> >> >> On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf wrote: >> >> >> >> On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: >> >> >> >> On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: >> >> On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis wrote: >> >>> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >>> >>> >>> >>> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>>> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. >>> >>> The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. >>> >>> i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. >>> >>> and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. >>> >>> Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). >>> >>> >>> Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind >>> >>> Good to know. Thanks for providing this info. >>> >>> >>> sounds reasonable to 'wait' on the promise side of things, and use that bit in the datamanager >>> >>> +1 >> >> there are other promise implementations that we could use, that are to spec, such as Q and RSVP, here is the link to the HTML5 rocks article >> http://www.html5rocks.com/en/tutorials/es6/promises/ >> >> These last days I have been playing with the library When provided by Cujo, it's maybe also worth looking https://github.com/cujojs/when >> >> not sure I see value in using a different library as a temporary thing. Once the API is part of the browser platform, the need for [yet another js lib] goes away. >> I know but I'm more concerned about "Once the API is part of the browser platform" When will that happen and does it match with our roadmap ? Was also to offer a polyfill for older browser if we want to keep supporting them. >> > i will have to update the roadmap. > > 2.0 would be a nice time to "fully" switch, but we can start experimenting now and maybe for 1.5 can have some implemenation for data manager only. > > Current Chrome has Promise's enable by default and it looks like FireFox 29( next version ) will too. Safari and IE are in dev i believe > > for fallback we can still make use of jQuery i think because of this method here "Promise.cast", please strike this comment from the record, i'm an idiot :) > although the closest lib to the spec is RSVP( maybe this could be the 2.0 fallback if we remove jQuery from the whole lib ) > > > >> >> >> >> >>> >>> >>> >>> while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. >>> >>> Yeah, IMO worth to look there, for reducing dependencies >>> >>> -M >>> >>> >>> >>> >>> I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart >>> >>> >>> >>> @Lucas Thanks for making things clear >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140324/1c1890ca/attachment.html From scm.blanc at gmail.com Mon Mar 24 12:11:31 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 24 Mar 2014 17:11:31 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> Message-ID: That's why I mentioned When.js for an eventual 2.0 fallback lib "When.js is a rock solid, battle-tested Promises/A+ and when() implementation, including a complete ES6 Promise shim " On Mon, Mar 24, 2014 at 5:07 PM, Lucas Holmquist wrote: > > On Mar 24, 2014, at 12:01 PM, Lucas Holmquist wrote: > > > On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: > > > > > On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf wrote: > >> >> >> >> On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: >> >>> >>> >>> >>> On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: >>> >>>> >>>> On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis >>>> wrote: >>>> >>>> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >>>> >>>>> >>>>> >>>>> >>>>> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>>>> >>>>>> I agree that it would be nice to implement AGJS-70 (Investigate >>>>>> removing jQuery requirement). Meanwhile, there is an open source project on >>>>>> GitHub that claims to offer a custom builder for jQuery in order to include >>>>>> only the modules needed [1] [2]. I haven't tried it yet but maybe we could >>>>>> create a custom jQuery build which includes only the parts currently needed >>>>>> in AeroGear. This would mean a smaller size of the jQuery dependency. >>>>>> >>>>>> >>>>>> The AG lib depends on a few parts of jQuery, the biggest being >>>>>> jQuery.Ajax and the promise implementation. >>>>>> >>>>>> i know we can make custom builds of jQuery pretty easily( building >>>>>> from source ), but i don't really want to bundle it within our lib. >>>>>> >>>>>> and i don't think with bower we can do this easily. although they did >>>>>> just add a post install hook, so perhaps that could be something to look at. >>>>>> >>>>>> Datamanager only uses the promise implementation of jQuery( and some >>>>>> random thing for the filter method, which could probably be updated ). >>>>>> >>>>> >>>> >>>> >>>>> Promises are starting to become available natively in browsers and >>>>>> jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback >>>>>> without a shim of some kind >>>>>> >>>>> >>>> Good to know. Thanks for providing this info. >>>> >>>> >>>>> >>>>> sounds reasonable to 'wait' on the promise side of things, and use >>>>> that bit in the datamanager >>>>> >>>> >>>> +1 >>>> >>>> >>>> there are other promise implementations that we could use, that are to >>>> spec, such as Q and RSVP, here is the link to the HTML5 rocks article >>>> http://www.html5rocks.com/en/tutorials/es6/promises/ >>>> >>> >>> These last days I have been playing with the library When provided by >>> Cujo, it's maybe also worth looking https://github.com/cujojs/when >>> >> >> not sure I see value in using a different library as a temporary thing. >> Once the API is part of the browser platform, the need for [yet another js >> lib] goes away. >> > I know but I'm more concerned about "Once the API is part of the browser > platform" When will that happen and does it match with our roadmap ? Was > also to offer a polyfill for older browser if we want to keep supporting > them. > > i will have to update the roadmap. > > 2.0 would be a nice time to "fully" switch, but we can start > experimenting now and maybe for 1.5 can have some implemenation for data > manager only. > > Current Chrome has Promise's enable by default and it looks like FireFox > 29( next version ) will too. Safari and IE are in dev i believe > > for fallback we can still make use of jQuery i think because of this > method here "Promise.cast", > > please strike this comment from the record, i'm an idiot :) > > although the closest lib to the spec is RSVP( maybe this could be the 2.0 > fallback if we remove jQuery from the whole lib ) > > > > >> >> >>> >>> >>>> >>>> >>>> >>>>>> >>>>>> while i don't really want to reinvent the wheel in terms of Ajax, it >>>>>> might be interesting to take a look. >>>>>> >>>>> >>>>> Yeah, IMO worth to look there, for reducing dependencies >>>>> >>>>> -M >>>>> >>>>> >>>>> >>>> >>>>> >>>>> >>>>>> I think in a previous ML thread about what 2.0 looked like, that >>>>>> Pipeline would maybe just be a JSON only thing, with exception for multipart >>>>>> >>>>>> >>>>>> >>>> @Lucas Thanks for making things clear >>>> >>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140324/09372ce8/attachment-0001.html From scm.blanc at gmail.com Mon Mar 24 12:20:29 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 24 Mar 2014 17:20:29 +0100 Subject: [aerogear-dev] Cordova: question on recent Push Plugin release In-Reply-To: References: Message-ID: In the same spirit, I think that the plugin version in our master should always be bumped in comparison to the current released version. Like we do in the other projects. So, for now master should be 0.4-dev / or 0.4-snapshot, not sure what cordova supports. Because when we will merge PRs , can be confusing for the users. On Fri, Mar 21, 2014 at 3:10 PM, Matthias Wessendorf wrote: > Hello, > > a few days ago, the 0.0.3 version of our Cordova Push Plugin was released > (see [1]). > > Now, on our github 'releases' folder we see the release was made available > on March 17th (as of now it says "4 days ago"). > > Great! > > Looking at the Cordova Plugin Registry, I see it's there since four weeks: > http://plugins.cordova.io/#/org.jboss.aerogear.cordova.push > > That's incorrect, as we officially released it a few days ago (see [1]). > > Also they are not exactly the same (in download size and content (just do > a diff on the PushPlugin.m file). > > Anyways, I am wondering if it is possible to update the version on the > Cordova Registry, so that we: > a) ship the official release > b) have both downloads (GH and Cordova.io) being the same > > Thanks! > Matthias > > > [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-March/006926.html > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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/20140324/13a5ba1e/attachment.html From tkriz at redhat.com Mon Mar 24 12:24:31 2014 From: tkriz at redhat.com (Tadeas Kriz) Date: Mon, 24 Mar 2014 17:24:31 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> Message-ID: Hey, I?m done with testing the new crypto. The only thing that I?ve already discussed with cvasilak is that if anyone updates to the new crypto and already had some data stored with the old one, it will crash when trying to read them. Other than that everything works. ? Tadeas Kriz On 21 Mar 2014, at 12:43, Christos Vasilakis wrote: > Hi everyone, > > after discussion with Corinne, we have decided to pause the release of aerogear-ios this week, and release early next. The reason is that we would like the upcoming release to include dependency of the new aerogear-crypto changes that were incorporated this week[1], mainly the update of the symmetric encryption to use NaCI. We feel, that it makes sense to release both at the same time. > > For aerogear-ios, a minor ?private' API change is needed, but would like a bit of time for testing. > > Let us know your thoughts/concerns. > > Regards > Christos > > [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 > > > On Mar 18, 2014, at 9:37 AM, Corinne Krych wrote: > >> Hello iOS Friends, >> >> AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). >> >> To test it, open Podfile and point to the latest git branch >> pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' >> >> Help us make this release a success, give it a trial, and let us know how it goes for your project. >> >> ++ >> 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 Mon Mar 24 12:36:30 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 24 Mar 2014 17:36:30 +0100 Subject: [aerogear-dev] Cordova: question on recent Push Plugin release In-Reply-To: References: Message-ID: I am fine in keeping master up-to-date w/ the latest greatst of our Android/iOS. But my question was really: Why are there two different 0.0.3 versions being released (our offical one on GH, and some four week old one on crodova.io (can we remove/update that piece)? On Mon, Mar 24, 2014 at 5:20 PM, Sebastien Blanc wrote: > In the same spirit, I think that the plugin version in our master should > always be bumped in comparison to the current released version. Like we do > in the other projects. > So, for now master should be 0.4-dev / or 0.4-snapshot, not sure what > cordova supports. Because when we will merge PRs , can be confusing for the > users. > > > > On Fri, Mar 21, 2014 at 3:10 PM, Matthias Wessendorf wrote: > >> Hello, >> >> a few days ago, the 0.0.3 version of our Cordova Push Plugin was released >> (see [1]). >> >> Now, on our github 'releases' folder we see the release was made >> available on March 17th (as of now it says "4 days ago"). >> >> Great! >> >> Looking at the Cordova Plugin Registry, I see it's there since four weeks: >> http://plugins.cordova.io/#/org.jboss.aerogear.cordova.push >> >> That's incorrect, as we officially released it a few days ago (see [1]). >> >> Also they are not exactly the same (in download size and content (just do >> a diff on the PushPlugin.m file). >> >> Anyways, I am wondering if it is possible to update the version on the >> Cordova Registry, so that we: >> a) ship the official release >> b) have both downloads (GH and Cordova.io) being the same >> >> Thanks! >> Matthias >> >> >> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-March/006926.html >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/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/20140324/71cc9952/attachment.html From matzew at apache.org Mon Mar 24 12:42:31 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 24 Mar 2014 17:42:31 +0100 Subject: [aerogear-dev] Cordova: question on recent Push Plugin release In-Reply-To: References: Message-ID: On Mon, Mar 24, 2014 at 5:36 PM, Matthias Wessendorf wrote: > I am fine in keeping master up-to-date w/ the latest greatst of our > Android/iOS. > > But my question was really: Why are there two different 0.0.3 versions > being released (our offical one on GH, and some four week old one on > crodova.io (can we remove/update that piece)? > ah! check: http://plugins.cordova.io/#/org.jboss.aerogear.cordova.push it shows the recent version. yay! > > > > On Mon, Mar 24, 2014 at 5:20 PM, Sebastien Blanc wrote: > >> In the same spirit, I think that the plugin version in our master should >> always be bumped in comparison to the current released version. Like we do >> in the other projects. >> So, for now master should be 0.4-dev / or 0.4-snapshot, not sure what >> cordova supports. Because when we will merge PRs , can be confusing for the >> users. >> >> >> >> On Fri, Mar 21, 2014 at 3:10 PM, Matthias Wessendorf wrote: >> >>> Hello, >>> >>> a few days ago, the 0.0.3 version of our Cordova Push Plugin was >>> released (see [1]). >>> >>> Now, on our github 'releases' folder we see the release was made >>> available on March 17th (as of now it says "4 days ago"). >>> >>> Great! >>> >>> Looking at the Cordova Plugin Registry, I see it's there since four >>> weeks: >>> http://plugins.cordova.io/#/org.jboss.aerogear.cordova.push >>> >>> That's incorrect, as we officially released it a few days ago (see [1]). >>> >>> Also they are not exactly the same (in download size and content (just >>> do a diff on the PushPlugin.m file). >>> >>> Anyways, I am wondering if it is possible to update the version on the >>> Cordova Registry, so that we: >>> a) ship the official release >>> b) have both downloads (GH and Cordova.io) being the same >>> >>> Thanks! >>> Matthias >>> >>> >>> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-March/006926.html >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/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/20140324/2572b554/attachment-0001.html From gorkem.ercan at gmail.com Mon Mar 24 12:48:13 2014 From: gorkem.ercan at gmail.com (Gorkem Ercan) Date: Mon, 24 Mar 2014 09:48:13 -0700 Subject: [aerogear-dev] Cordova: question on recent Push Plugin release In-Reply-To: References: Message-ID: In case your CLI or HMT does not pick up the new release. The downloaded plugins are cached in ~/.plugman/cache removing them and reinstalling on the tools should cause the later version to be downloaded. -- Gorkem On Mon, Mar 24, 2014 at 9:42 AM, Matthias Wessendorf wrote: > > > > On Mon, Mar 24, 2014 at 5:36 PM, Matthias Wessendorf wrote: > >> I am fine in keeping master up-to-date w/ the latest greatst of our >> Android/iOS. >> >> But my question was really: Why are there two different 0.0.3 versions >> being released (our offical one on GH, and some four week old one on >> crodova.io (can we remove/update that piece)? >> > > ah! check: > http://plugins.cordova.io/#/org.jboss.aerogear.cordova.push > > it shows the recent version. yay! > > > >> >> >> >> On Mon, Mar 24, 2014 at 5:20 PM, Sebastien Blanc wrote: >> >>> In the same spirit, I think that the plugin version in our master should >>> always be bumped in comparison to the current released version. Like we do >>> in the other projects. >>> So, for now master should be 0.4-dev / or 0.4-snapshot, not sure what >>> cordova supports. Because when we will merge PRs , can be confusing for the >>> users. >>> >>> >>> >>> On Fri, Mar 21, 2014 at 3:10 PM, Matthias Wessendorf wrote: >>> >>>> Hello, >>>> >>>> a few days ago, the 0.0.3 version of our Cordova Push Plugin was >>>> released (see [1]). >>>> >>>> Now, on our github 'releases' folder we see the release was made >>>> available on March 17th (as of now it says "4 days ago"). >>>> >>>> Great! >>>> >>>> Looking at the Cordova Plugin Registry, I see it's there since four >>>> weeks: >>>> http://plugins.cordova.io/#/org.jboss.aerogear.cordova.push >>>> >>>> That's incorrect, as we officially released it a few days ago (see [1]). >>>> >>>> Also they are not exactly the same (in download size and content (just >>>> do a diff on the PushPlugin.m file). >>>> >>>> Anyways, I am wondering if it is possible to update the version on the >>>> Cordova Registry, so that we: >>>> a) ship the official release >>>> b) have both downloads (GH and Cordova.io) being the same >>>> >>>> Thanks! >>>> Matthias >>>> >>>> >>>> [1] >>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-March/006926.html >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/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/20140324/d29fedd2/attachment.html From lholmqui at redhat.com Mon Mar 24 13:11:05 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 13:11:05 -0400 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> Message-ID: On Mar 24, 2014, at 12:11 PM, Sebastien Blanc wrote: > That's why I mentioned When.js for an eventual 2.0 fallback lib > "When.js is a rock solid, battle-tested Promises/A+ and when() implementation, including a complete ES6 Promise shim" if we do it right, a user could use any promise lib that is to spec > > > On Mon, Mar 24, 2014 at 5:07 PM, Lucas Holmquist wrote: > > On Mar 24, 2014, at 12:01 PM, Lucas Holmquist wrote: > >> >> On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: >> >>> >>> >>> >>> On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf wrote: >>> >>> >>> >>> On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: >>> >>> >>> >>> On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: >>> >>> On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis wrote: >>> >>>> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >>>> >>>> >>>> >>>> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>>>> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. >>>> >>>> The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. >>>> >>>> i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. >>>> >>>> and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. >>>> >>>> Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). >>>> >>>> >>>> Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind >>>> >>>> Good to know. Thanks for providing this info. >>>> >>>> >>>> sounds reasonable to 'wait' on the promise side of things, and use that bit in the datamanager >>>> >>>> +1 >>> >>> there are other promise implementations that we could use, that are to spec, such as Q and RSVP, here is the link to the HTML5 rocks article >>> http://www.html5rocks.com/en/tutorials/es6/promises/ >>> >>> These last days I have been playing with the library When provided by Cujo, it's maybe also worth looking https://github.com/cujojs/when >>> >>> not sure I see value in using a different library as a temporary thing. Once the API is part of the browser platform, the need for [yet another js lib] goes away. >>> I know but I'm more concerned about "Once the API is part of the browser platform" When will that happen and does it match with our roadmap ? Was also to offer a polyfill for older browser if we want to keep supporting them. >>> >> i will have to update the roadmap. >> >> 2.0 would be a nice time to "fully" switch, but we can start experimenting now and maybe for 1.5 can have some implemenation for data manager only. >> >> Current Chrome has Promise's enable by default and it looks like FireFox 29( next version ) will too. Safari and IE are in dev i believe >> >> for fallback we can still make use of jQuery i think because of this method here "Promise.cast", > > please strike this comment from the record, i'm an idiot :) > >> although the closest lib to the spec is RSVP( maybe this could be the 2.0 fallback if we remove jQuery from the whole lib ) >> >> >> >>> >>> >>> >>> >>>> >>>> >>>> >>>> while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. >>>> >>>> Yeah, IMO worth to look there, for reducing dependencies >>>> >>>> -M >>>> >>>> >>>> >>>> >>>> I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart >>>> >>>> >>>> >>>> @Lucas Thanks for making things clear >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140324/75e7d60c/attachment-0001.html From cvasilak at gmail.com Mon Mar 24 13:47:12 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 24 Mar 2014 19:47:12 +0200 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> Message-ID: On Mar 24, 2014, at 6:24 PM, Tadeas Kriz wrote: > Hey, > > I?m done with testing the new crypto. The only thing that I?ve already discussed with cvasilak is that if anyone updates to the new crypto and already had some data stored with the old one, it will crash when trying to read them. Other than that everything works. For the record, unfortunately due to change of symmetic crypto to use NaCl and moving away from common crypto, old encrypted data will fail to be read with the new version. But we believe relying on NaCI for both symm/asymm encryption is the way to move forward and the main motivation for pausing this release of agios to incorporate latest crypto. As sooner we switch, the better. For any user that will be affected by this, a possible dump of the old data using ?read:all?, and reload on the new version can be an option. This downside will be documented on our release notes. Regards, Christos > > ? > Tadeas Kriz > > On 21 Mar 2014, at 12:43, Christos Vasilakis wrote: > >> Hi everyone, >> >> after discussion with Corinne, we have decided to pause the release of aerogear-ios this week, and release early next. The reason is that we would like the upcoming release to include dependency of the new aerogear-crypto changes that were incorporated this week[1], mainly the update of the symmetric encryption to use NaCI. We feel, that it makes sense to release both at the same time. >> >> For aerogear-ios, a minor ?private' API change is needed, but would like a bit of time for testing. >> >> Let us know your thoughts/concerns. >> >> Regards >> Christos >> >> [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 >> >> >> On Mar 18, 2014, at 9:37 AM, Corinne Krych wrote: >> >>> Hello iOS Friends, >>> >>> AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). >>> >>> To test it, open Podfile and point to the latest git branch >>> pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' >>> >>> Help us make this release a success, give it a trial, and let us know how it goes for your project. >>> >>> ++ >>> 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 bruno at abstractj.com Mon Mar 24 14:21:42 2014 From: bruno at abstractj.com (Bruno Oliveira) Date: Mon, 24 Mar 2014 15:21:42 -0300 Subject: [aerogear-dev] AeroGear Security and friends deprecation Message-ID: Good morning everyone, today I would like to announce the deprecation of the following projects: - AeroGear Security? - AeroGear Security PicketLink? - AeroGear Security Hawk? - AeroGear Security Shiro Please see:?https://issues.jboss.org/browse/AGSEC-179. This decision didn?t come from nowhere. We just had few classes, created because we didn?t have a final solution for security on the server side. Today we have Keycloak and Picketlink to replace AeroGear Security and we are not abandoning security on the server side, just joining our efforts with Keycloak. The following projects will be immediately affected:? - https://github.com/aerogear/aerogear-jaxrs-demo? - https://github.com/aerogear/aerogear-unifiedpush-server? - https://github.com/aerogear/aerogear-integration-tests-server? - https://github.com/aerogear/aerogear-aerodoc-backend? I will be working to migrate the codebase. If you this change might affect you, please raise your hand. I?m doing it for the best. ? -- abstractj From matzew at apache.org Mon Mar 24 14:52:42 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 24 Mar 2014 19:52:42 +0100 Subject: [aerogear-dev] AeroGear Security and friends deprecation In-Reply-To: References: Message-ID: Hello there, and thanks for the heads up! On Mon, Mar 24, 2014 at 7:21 PM, Bruno Oliveira wrote: > Good morning everyone, today I would like to announce the deprecation of > the following projects: > > - AeroGear Security > - AeroGear Security PicketLink > - AeroGear Security Hawk > - AeroGear Security Shiro > > Please see: https://issues.jboss.org/browse/AGSEC-179. This decision > didn't come from nowhere. We just had few classes, created because we > didn't have a final solution for security on the server side. Today we have > Keycloak and Picketlink to replace AeroGear Security and we are not > abandoning security on the server side, just joining our efforts with > Keycloak. > > The following projects will be immediately affected: > > - https://github.com/aerogear/aerogear-jaxrs-demo > - https://github.com/aerogear/aerogear-unifiedpush-server > - https://github.com/aerogear/aerogear-integration-tests-server > - https://github.com/aerogear/aerogear-aerodoc-backend > > I will be working to migrate the codebase. awesome! One note on the UPS: We have this branch (already updated on the latest alpha-4): https://github.com/aerogear/aerogear-unifiedpush-server/tree/Keycloak_after_re_org2 I am currently looking for a slightly better integration, instead of pointing to a separate deployed WAR file: - e.g. bundle KC libs and realm-setup inside our WAR; Or providing an EAR file (UPS.war + KC.war), etc. This is currently in on 'research' :-) Hopefully, in very soon this branch will be merged down to master, celebrated w/ an 0.11.0 release :-) > If you this change might affect you, please raise your hand. > > I'm doing it for the best. > +1 great move! -M > > > -- > abstractj > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140324/70972c0a/attachment.html From matzew at apache.org Mon Mar 24 14:56:20 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 24 Mar 2014 19:56:20 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> Message-ID: On Mon, Mar 24, 2014 at 6:47 PM, Christos Vasilakis wrote: > > On Mar 24, 2014, at 6:24 PM, Tadeas Kriz wrote: > > > Hey, > > > > I'm done with testing the new crypto. The only thing that I've already > discussed with cvasilak is that if anyone updates to the new crypto and > already had some data stored with the old one, it will crash when trying to > read them. Other than that everything works. > > For the record, unfortunately due to change of symmetic crypto to use NaCl > and moving away from common crypto, old encrypted data will fail to be read > with the new version. But we believe relying on NaCI for both symm/asymm > encryption is the way to move forward and the main motivation for pausing > this release of agios to incorporate latest crypto. As sooner we switch, > the better. > +9001 :-) > > For any user that will be affected by this, a possible dump of the old > data using 'read:all', and reload on the new version can be an option. This > downside will be documented on our release notes. > yeah - I do not think it's a serious problem. This library is pretty young, and under active development. +1 on documentation/release notes for the issue. And yeah, as you said: better sooner than later to switch :-) Great job and thanks for the update! -Matthias > > Regards, > Christos > > > > > -- > > Tadeas Kriz > > > > On 21 Mar 2014, at 12:43, Christos Vasilakis wrote: > > > >> Hi everyone, > >> > >> after discussion with Corinne, we have decided to pause the release of > aerogear-ios this week, and release early next. The reason is that we would > like the upcoming release to include dependency of the new aerogear-crypto > changes that were incorporated this week[1], mainly the update of the > symmetric encryption to use NaCI. We feel, that it makes sense to release > both at the same time. > >> > >> For aerogear-ios, a minor 'private' API change is needed, but would > like a bit of time for testing. > >> > >> Let us know your thoughts/concerns. > >> > >> Regards > >> Christos > >> > >> [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 > >> > >> > >> On Mar 18, 2014, at 9:37 AM, Corinne Krych > wrote: > >> > >>> Hello iOS Friends, > >>> > >>> AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to > release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and > AFNetworking 2.x (latest 2.2.1). > >>> > >>> To test it, open Podfile and point to the latest git branch > >>> pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > >>> > >>> Help us make this release a success, give it a trial, and let us know > how it goes for your project. > >>> > >>> ++ > >>> 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 > -- 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/20140324/c925c545/attachment.html From miguel21op at gmail.com Mon Mar 24 17:09:02 2014 From: miguel21op at gmail.com (Miiguel Lemos) Date: Mon, 24 Mar 2014 21:09:02 +0000 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> Message-ID: Meanwhile: there are several possibilities to build a customized (smaller) jQuery library. For instance: http://projects.jga.me/jquery-builder/ Enviado do meu iPad No dia 24/03/2014, ?s 17:11, Lucas Holmquist escreveu: > >> On Mar 24, 2014, at 12:11 PM, Sebastien Blanc wrote: >> >> That's why I mentioned When.js for an eventual 2.0 fallback lib >> "When.js is a rock solid, battle-tested Promises/A+ and when() implementation, including a complete ES6 Promise shim" > > if we do it right, a user could use any promise lib that is to spec > >> >> >>> On Mon, Mar 24, 2014 at 5:07 PM, Lucas Holmquist wrote: >>> >>>> On Mar 24, 2014, at 12:01 PM, Lucas Holmquist wrote: >>>> >>>> >>>>> On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: >>>>> >>>>> >>>>> >>>>> >>>>>> On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf wrote: >>>>>> >>>>>> >>>>>> >>>>>>> On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: >>>>>>>> >>>>>>>>> On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis wrote: >>>>>>>>> >>>>>>>>> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>>>>>>>>>>> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. >>>>>>>>>>> >>>>>>>>>>> The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. >>>>>>>>>>> >>>>>>>>>>> i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. >>>>>>>>>>> >>>>>>>>>>> and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. >>>>>>>>>>> >>>>>>>>>>> Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). >>>>>>>>> >>>>>>>>> >>>>>>>>>>> Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind >>>>>>>>> >>>>>>>>> Good to know. Thanks for providing this info. >>>>>>>>> >>>>>>>>>> >>>>>>>>>> sounds reasonable to 'wait' on the promise side of things, and use that bit in the datamanager >>>>>>>>> >>>>>>>>> +1 >>>>>>>> >>>>>>>> there are other promise implementations that we could use, that are to spec, such as Q and RSVP, here is the link to the HTML5 rocks article >>>>>>>> http://www.html5rocks.com/en/tutorials/es6/promises/ >>>>>>> >>>>>>> These last days I have been playing with the library When provided by Cujo, it's maybe also worth looking https://github.com/cujojs/when >>>>>> >>>>>> not sure I see value in using a different library as a temporary thing. Once the API is part of the browser platform, the need for [yet another js lib] goes away. >>>>> I know but I'm more concerned about "Once the API is part of the browser platform" When will that happen and does it match with our roadmap ? Was also to offer a polyfill for older browser if we want to keep supporting them. >>>> i will have to update the roadmap. >>>> >>>> 2.0 would be a nice time to "fully" switch, but we can start experimenting now and maybe for 1.5 can have some implemenation for data manager only. >>>> >>>> Current Chrome has Promise's enable by default and it looks like FireFox 29( next version ) will too. Safari and IE are in dev i believe >>>> >>>> for fallback we can still make use of jQuery i think because of this method here "Promise.cast", >>> >>> please strike this comment from the record, i'm an idiot :) >>> >>>> although the closest lib to the spec is RSVP( maybe this could be the 2.0 fallback if we remove jQuery from the whole lib ) >>>> >>>> >>>> >>>>>> >>>>>> >>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. >>>>>>>>>> >>>>>>>>>> Yeah, IMO worth to look there, for reducing dependencies >>>>>>>>>> >>>>>>>>>> -M >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart >>>>>>>>> >>>>>>>>> @Lucas Thanks for making things clear >>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Matthias Wessendorf >>>>>>>>>> >>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140324/8aed6f8b/attachment-0001.html From miguel21op at gmail.com Mon Mar 24 17:09:02 2014 From: miguel21op at gmail.com (Miiguel Lemos) Date: Mon, 24 Mar 2014 21:09:02 +0000 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> Message-ID: Meanwhile: there are several possibilities to build a customized (smaller) jQuery library. For instance: http://projects.jga.me/jquery-builder/ Enviado do meu iPad No dia 24/03/2014, ?s 17:11, Lucas Holmquist escreveu: > >> On Mar 24, 2014, at 12:11 PM, Sebastien Blanc wrote: >> >> That's why I mentioned When.js for an eventual 2.0 fallback lib >> "When.js is a rock solid, battle-tested Promises/A+ and when() implementation, including a complete ES6 Promise shim" > > if we do it right, a user could use any promise lib that is to spec > >> >> >>> On Mon, Mar 24, 2014 at 5:07 PM, Lucas Holmquist wrote: >>> >>>> On Mar 24, 2014, at 12:01 PM, Lucas Holmquist wrote: >>>> >>>> >>>>> On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: >>>>> >>>>> >>>>> >>>>> >>>>>> On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf wrote: >>>>>> >>>>>> >>>>>> >>>>>>> On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: >>>>>>>> >>>>>>>>> On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis wrote: >>>>>>>>> >>>>>>>>> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>>>>>>>>>>> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. >>>>>>>>>>> >>>>>>>>>>> The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. >>>>>>>>>>> >>>>>>>>>>> i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. >>>>>>>>>>> >>>>>>>>>>> and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. >>>>>>>>>>> >>>>>>>>>>> Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). >>>>>>>>> >>>>>>>>> >>>>>>>>>>> Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind >>>>>>>>> >>>>>>>>> Good to know. Thanks for providing this info. >>>>>>>>> >>>>>>>>>> >>>>>>>>>> sounds reasonable to 'wait' on the promise side of things, and use that bit in the datamanager >>>>>>>>> >>>>>>>>> +1 >>>>>>>> >>>>>>>> there are other promise implementations that we could use, that are to spec, such as Q and RSVP, here is the link to the HTML5 rocks article >>>>>>>> http://www.html5rocks.com/en/tutorials/es6/promises/ >>>>>>> >>>>>>> These last days I have been playing with the library When provided by Cujo, it's maybe also worth looking https://github.com/cujojs/when >>>>>> >>>>>> not sure I see value in using a different library as a temporary thing. Once the API is part of the browser platform, the need for [yet another js lib] goes away. >>>>> I know but I'm more concerned about "Once the API is part of the browser platform" When will that happen and does it match with our roadmap ? Was also to offer a polyfill for older browser if we want to keep supporting them. >>>> i will have to update the roadmap. >>>> >>>> 2.0 would be a nice time to "fully" switch, but we can start experimenting now and maybe for 1.5 can have some implemenation for data manager only. >>>> >>>> Current Chrome has Promise's enable by default and it looks like FireFox 29( next version ) will too. Safari and IE are in dev i believe >>>> >>>> for fallback we can still make use of jQuery i think because of this method here "Promise.cast", >>> >>> please strike this comment from the record, i'm an idiot :) >>> >>>> although the closest lib to the spec is RSVP( maybe this could be the 2.0 fallback if we remove jQuery from the whole lib ) >>>> >>>> >>>> >>>>>> >>>>>> >>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. >>>>>>>>>> >>>>>>>>>> Yeah, IMO worth to look there, for reducing dependencies >>>>>>>>>> >>>>>>>>>> -M >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart >>>>>>>>> >>>>>>>>> @Lucas Thanks for making things clear >>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Matthias Wessendorf >>>>>>>>>> >>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140324/8aed6f8b/attachment-0002.html From bruno at abstractj.org Mon Mar 24 17:17:11 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 24 Mar 2014 18:17:11 -0300 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> Message-ID: <3FA5B368-7CA8-4E7C-BB45-22746E3FD1E6@abstractj.org> That would be a big win > On Mar 24, 2014, at 2:11 PM, Lucas Holmquist wrote: > > if we do it right, a user could use any promise lib that is to spec From miguel21op at gmail.com Mon Mar 24 17:50:05 2014 From: miguel21op at gmail.com (Miiguel Lemos) Date: Mon, 24 Mar 2014 21:50:05 +0000 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: <3FA5B368-7CA8-4E7C-BB45-22746E3FD1E6@abstractj.org> References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> <3FA5B368-7CA8-4E7C-BB45-22746E3FD1E6@abstractj.org> Message-ID: <6C6748E7-0B9F-4FCB-8A1F-663E894489AF@gmail.com> Assuming that are really needed (?) external libraries to execute asynchronous calls, here is a comparaison. And as you can see jQuery performs not very well... http://complexitymaze.com/2014/03/03/javascript-promises-a-comparison-of-libraries/ Enviado do meu iPad No dia 24/03/2014, ?s 21:17, Bruno Oliveira escreveu: > That would be a big win > >> On Mar 24, 2014, at 2:11 PM, Lucas Holmquist wrote: >> >> if we do it right, a user could use any promise lib that is to spec > _______________________________________________ > 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/20140324/8951a0f9/attachment.html From lholmqui at redhat.com Mon Mar 24 19:46:00 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 24 Mar 2014 19:46:00 -0400 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> Message-ID: On Mar 24, 2014, at 5:09 PM, Miiguel Lemos wrote: > Meanwhile: there are several possibilities to build a customized (smaller) jQuery library. > For instance: > > http://projects.jga.me/jquery-builder/ yup, and since we don't package jQuery with our JS libs, you could use that to build a smaller build > > Enviado do meu iPad > > No dia 24/03/2014, ?s 17:11, Lucas Holmquist escreveu: > >> >> On Mar 24, 2014, at 12:11 PM, Sebastien Blanc wrote: >> >>> That's why I mentioned When.js for an eventual 2.0 fallback lib >>> "When.js is a rock solid, battle-tested Promises/A+ and when() implementation, including a complete ES6 Promise shim" >> >> if we do it right, a user could use any promise lib that is to spec >> >>> >>> >>> On Mon, Mar 24, 2014 at 5:07 PM, Lucas Holmquist wrote: >>> >>> On Mar 24, 2014, at 12:01 PM, Lucas Holmquist wrote: >>> >>>> >>>> On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: >>>> >>>>> >>>>> >>>>> >>>>> On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf wrote: >>>>> >>>>> >>>>> >>>>> On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: >>>>> >>>>> >>>>> >>>>> On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: >>>>> >>>>> On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis wrote: >>>>> >>>>>> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>>>>>> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. >>>>>> >>>>>> The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. >>>>>> >>>>>> i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. >>>>>> >>>>>> and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. >>>>>> >>>>>> Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). >>>>>> >>>>>> >>>>>> Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind >>>>>> >>>>>> Good to know. Thanks for providing this info. >>>>>> >>>>>> >>>>>> sounds reasonable to 'wait' on the promise side of things, and use that bit in the datamanager >>>>>> >>>>>> +1 >>>>> >>>>> there are other promise implementations that we could use, that are to spec, such as Q and RSVP, here is the link to the HTML5 rocks article >>>>> http://www.html5rocks.com/en/tutorials/es6/promises/ >>>>> >>>>> These last days I have been playing with the library When provided by Cujo, it's maybe also worth looking https://github.com/cujojs/when >>>>> >>>>> not sure I see value in using a different library as a temporary thing. Once the API is part of the browser platform, the need for [yet another js lib] goes away. >>>>> I know but I'm more concerned about "Once the API is part of the browser platform" When will that happen and does it match with our roadmap ? Was also to offer a polyfill for older browser if we want to keep supporting them. >>>>> >>>> i will have to update the roadmap. >>>> >>>> 2.0 would be a nice time to "fully" switch, but we can start experimenting now and maybe for 1.5 can have some implemenation for data manager only. >>>> >>>> Current Chrome has Promise's enable by default and it looks like FireFox 29( next version ) will too. Safari and IE are in dev i believe >>>> >>>> for fallback we can still make use of jQuery i think because of this method here "Promise.cast", >>> >>> please strike this comment from the record, i'm an idiot :) >>> >>>> although the closest lib to the spec is RSVP( maybe this could be the 2.0 fallback if we remove jQuery from the whole lib ) >>>> >>>> >>>> >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>> while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. >>>>>> >>>>>> Yeah, IMO worth to look there, for reducing dependencies >>>>>> >>>>>> -M >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart >>>>>> >>>>>> >>>>>> >>>>>> @Lucas Thanks for making things clear >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> >>>>> -- >>>>> Matthias Wessendorf >>>>> >>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>> sessions: http://www.slideshare.net/mwessendorf >>>>> twitter: http://twitter.com/mwessendorf >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140324/43db995d/attachment-0001.html From miguel21op at gmail.com Mon Mar 24 20:17:21 2014 From: miguel21op at gmail.com (Miiguel Lemos) Date: Tue, 25 Mar 2014 00:17:21 +0000 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <59102FE3-B926-4E75-B5B6-4055A8CB1575@redhat.com> Message-ID: Me? No! When jQuery gets in, I get out ;-) Enviado do meu iPad No dia 24/03/2014, ?s 23:46, Lucas Holmquist escreveu: > >> On Mar 24, 2014, at 5:09 PM, Miiguel Lemos wrote: >> >> Meanwhile: there are several possibilities to build a customized (smaller) jQuery library. >> For instance: >> >> http://projects.jga.me/jquery-builder/ > > yup, and since we don't package jQuery with our JS libs, you could use that to build a smaller build > >> >> Enviado do meu iPad >> >> No dia 24/03/2014, ?s 17:11, Lucas Holmquist escreveu: >> >>> >>>> On Mar 24, 2014, at 12:11 PM, Sebastien Blanc wrote: >>>> >>>> That's why I mentioned When.js for an eventual 2.0 fallback lib >>>> "When.js is a rock solid, battle-tested Promises/A+ and when() implementation, including a complete ES6 Promise shim" >>> >>> if we do it right, a user could use any promise lib that is to spec >>> >>>> >>>> >>>>> On Mon, Mar 24, 2014 at 5:07 PM, Lucas Holmquist wrote: >>>>> >>>>>> On Mar 24, 2014, at 12:01 PM, Lucas Holmquist wrote: >>>>>> >>>>>> >>>>>>> On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist wrote: >>>>>>>>>> >>>>>>>>>>> On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis wrote: >>>>>>>>>>> >>>>>>>>>>> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist wrote: >>>>>>>>>>>>>> I agree that it would be nice to implement AGJS-70 (Investigate removing jQuery requirement). Meanwhile, there is an open source project on GitHub that claims to offer a custom builder for jQuery in order to include only the modules needed [1] [2]. I haven't tried it yet but maybe we could create a custom jQuery build which includes only the parts currently needed in AeroGear. This would mean a smaller size of the jQuery dependency. >>>>>>>>>>>>> >>>>>>>>>>>>> The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax and the promise implementation. >>>>>>>>>>>>> >>>>>>>>>>>>> i know we can make custom builds of jQuery pretty easily( building from source ), but i don't really want to bundle it within our lib. >>>>>>>>>>>>> >>>>>>>>>>>>> and i don't think with bower we can do this easily. although they did just add a post install hook, so perhaps that could be something to look at. >>>>>>>>>>>>> >>>>>>>>>>>>> Datamanager only uses the promise implementation of jQuery( and some random thing for the filter method, which could probably be updated ). >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>> Promises are starting to become available natively in browsers and jQuery doesn't use the Promise/A+ spec, so it could be harder to fallback without a shim of some kind >>>>>>>>>>> >>>>>>>>>>> Good to know. Thanks for providing this info. >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> sounds reasonable to 'wait' on the promise side of things, and use that bit in the datamanager >>>>>>>>>>> >>>>>>>>>>> +1 >>>>>>>>>> >>>>>>>>>> there are other promise implementations that we could use, that are to spec, such as Q and RSVP, here is the link to the HTML5 rocks article >>>>>>>>>> http://www.html5rocks.com/en/tutorials/es6/promises/ >>>>>>>>> >>>>>>>>> These last days I have been playing with the library When provided by Cujo, it's maybe also worth looking https://github.com/cujojs/when >>>>>>>> >>>>>>>> not sure I see value in using a different library as a temporary thing. Once the API is part of the browser platform, the need for [yet another js lib] goes away. >>>>>>> I know but I'm more concerned about "Once the API is part of the browser platform" When will that happen and does it match with our roadmap ? Was also to offer a polyfill for older browser if we want to keep supporting them. >>>>>> i will have to update the roadmap. >>>>>> >>>>>> 2.0 would be a nice time to "fully" switch, but we can start experimenting now and maybe for 1.5 can have some implemenation for data manager only. >>>>>> >>>>>> Current Chrome has Promise's enable by default and it looks like FireFox 29( next version ) will too. Safari and IE are in dev i believe >>>>>> >>>>>> for fallback we can still make use of jQuery i think because of this method here "Promise.cast", >>>>> >>>>> please strike this comment from the record, i'm an idiot :) >>>>> >>>>>> although the closest lib to the spec is RSVP( maybe this could be the 2.0 fallback if we remove jQuery from the whole lib ) >>>>>> >>>>>> >>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> while i don't really want to reinvent the wheel in terms of Ajax, it might be interesting to take a look. >>>>>>>>>>>> >>>>>>>>>>>> Yeah, IMO worth to look there, for reducing dependencies >>>>>>>>>>>> >>>>>>>>>>>> -M >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> I think in a previous ML thread about what 2.0 looked like, that Pipeline would maybe just be a JSON only thing, with exception for multipart >>>>>>>>>>> >>>>>>>>>>> @Lucas Thanks for making things clear >>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Matthias Wessendorf >>>>>>>>>>>> >>>>>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> aerogear-dev mailing list >>>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> aerogear-dev mailing list >>>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> aerogear-dev mailing list >>>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Matthias Wessendorf >>>>>>>> >>>>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>>>> sessions: http://www.slideshare.net/mwessendorf >>>>>>>> twitter: http://twitter.com/mwessendorf >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> aerogear-dev mailing list >>>>>>>> aerogear-dev at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > 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/20140325/356ffeb2/attachment-0001.html From matzew at apache.org Tue Mar 25 02:33:59 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 07:33:59 +0100 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? Message-ID: Hi, I feel a bit of the documentation might be misleading and not always that great to go over. Instead of adding more and more the README, I think we should (w/in the REPO) start to write a guide/book on HOWTO. Regarding the actual format, I think asciidoc comes to mind; 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/20140325/f26d390d/attachment.html From scm.blanc at gmail.com Tue Mar 25 03:55:16 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 25 Mar 2014 08:55:16 +0100 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? In-Reply-To: References: Message-ID: +1 We got already almost all the material in the current readme and we can split that nicely into a howto and then rewriting maybe some parts. On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf wrote: > Hi, > > I feel a bit of the documentation might be misleading and not always that > great to go over. > > Instead of adding more and more the README, I think we should (w/in the > REPO) start to write a guide/book on HOWTO. > > Regarding the actual format, I think asciidoc comes to mind; > > > 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/20140325/063bfeba/attachment.html From scm.blanc at gmail.com Tue Mar 25 04:27:06 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 25 Mar 2014 09:27:06 +0100 Subject: [aerogear-dev] AeroGear Security and friends deprecation In-Reply-To: References: Message-ID: Make sense ! I can of course help for the migration (especially for aerodoc). On Mon, Mar 24, 2014 at 7:52 PM, Matthias Wessendorf wrote: > Hello there, > > and thanks for the heads up! > > > > On Mon, Mar 24, 2014 at 7:21 PM, Bruno Oliveira wrote: > >> Good morning everyone, today I would like to announce the deprecation of >> the following projects: >> >> - AeroGear Security >> - AeroGear Security PicketLink >> - AeroGear Security Hawk >> - AeroGear Security Shiro >> >> Please see: https://issues.jboss.org/browse/AGSEC-179. This decision >> didn't come from nowhere. We just had few classes, created because we >> didn't have a final solution for security on the server side. Today we have >> Keycloak and Picketlink to replace AeroGear Security and we are not >> abandoning security on the server side, just joining our efforts with >> Keycloak. >> >> The following projects will be immediately affected: >> >> - https://github.com/aerogear/aerogear-jaxrs-demo >> - https://github.com/aerogear/aerogear-unifiedpush-server >> - https://github.com/aerogear/aerogear-integration-tests-server >> - https://github.com/aerogear/aerogear-aerodoc-backend >> >> I will be working to migrate the codebase. > > > awesome! > > One note on the UPS: > We have this branch (already updated on the latest alpha-4): > > https://github.com/aerogear/aerogear-unifiedpush-server/tree/Keycloak_after_re_org2 > > I am currently looking for a slightly better integration, instead of > pointing to a separate deployed WAR file: > - e.g. bundle KC libs and realm-setup inside our WAR; Or providing an EAR > file (UPS.war + KC.war), etc. > > This is currently in on 'research' :-) Hopefully, in very soon this branch > will be merged down to master, celebrated w/ an 0.11.0 release :-) > > > > >> If you this change might affect you, please raise your hand. >> >> I'm doing it for the best. >> > > +1 great move! > > -M > > >> >> >> -- >> abstractj >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140325/c9f3225f/attachment.html From matzew at apache.org Tue Mar 25 04:51:35 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 09:51:35 +0100 Subject: [aerogear-dev] AeroGear Security and friends deprecation In-Reply-To: References: Message-ID: Hello again! One thing that just came to mind is the implications for the clients. Today the client libs are supporting "AeroGear Security", for cases like the RESTful login. For example, taking the iOS library: https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/security/AGRestAuthentication.m This class somewhat expects an endpoint, that under the covers uses AeroGear Security-PicketLink JAR. The AGIOS-35 ticket is a good example of how client had to be changed due to updates on the used version of PicketLink. Now, I am wondering, what does the deprecation of the java libraries mean for the client offerings? For instance, once we did port the endpoints (for instance on AeroDoc) to vanilla PicketLink, should this iOS class/module just function like before? Or does it even make sense to keep that functionality? Or, instead of on the "core" module (speaking iOS), would it make sense to move it into a different/separate project ? Greetings, Matthias [AGIOS-35] https://issues.jboss.org/browse/AGIOS-35 On Mon, Mar 24, 2014 at 7:21 PM, Bruno Oliveira wrote: > Good morning everyone, today I would like to announce the deprecation of > the following projects: > > - AeroGear Security > - AeroGear Security PicketLink > - AeroGear Security Hawk > - AeroGear Security Shiro > > Please see: https://issues.jboss.org/browse/AGSEC-179. This decision > didn't come from nowhere. We just had few classes, created because we > didn't have a final solution for security on the server side. Today we have > Keycloak and Picketlink to replace AeroGear Security and we are not > abandoning security on the server side, just joining our efforts with > Keycloak. > > The following projects will be immediately affected: > > - https://github.com/aerogear/aerogear-jaxrs-demo > - https://github.com/aerogear/aerogear-unifiedpush-server > - https://github.com/aerogear/aerogear-integration-tests-server > - https://github.com/aerogear/aerogear-aerodoc-backend > > I will be working to migrate the codebase. If you this change might affect > you, please raise your hand. > > I'm doing it for the best. > > > -- > abstractj > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140325/ac7517c1/attachment.html From corinnekrych at gmail.com Tue Mar 25 04:59:09 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 25 Mar 2014 09:59:09 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> Message-ID: <29DE6245-57E0-441C-B8D2-6B8693BF9A77@gmail.com> +1 On 24 Mar 2014, at 19:56, Matthias Wessendorf wrote: > > > > On Mon, Mar 24, 2014 at 6:47 PM, Christos Vasilakis wrote: > > On Mar 24, 2014, at 6:24 PM, Tadeas Kriz wrote: > > > Hey, > > > > I?m done with testing the new crypto. The only thing that I?ve already discussed with cvasilak is that if anyone updates to the new crypto and already had some data stored with the old one, it will crash when trying to read them. Other than that everything works. > > For the record, unfortunately due to change of symmetic crypto to use NaCl and moving away from common crypto, old encrypted data will fail to be read with the new version. But we believe relying on NaCI for both symm/asymm encryption is the way to move forward and the main motivation for pausing this release of agios to incorporate latest crypto. As sooner we switch, the better. > > +9001 :-) > > > > For any user that will be affected by this, a possible dump of the old data using ?read:all?, and reload on the new version can be an option. This downside will be documented on our release notes. > > yeah - I do not think it's a serious problem. This library is pretty young, and under active development. +1 on documentation/release notes for the issue. > > And yeah, as you said: better sooner than later to switch :-) > > Great job and thanks for the update! > > -Matthias > > > > Regards, > Christos > > > > > ? > > Tadeas Kriz > > > > On 21 Mar 2014, at 12:43, Christos Vasilakis wrote: > > > >> Hi everyone, > >> > >> after discussion with Corinne, we have decided to pause the release of aerogear-ios this week, and release early next. The reason is that we would like the upcoming release to include dependency of the new aerogear-crypto changes that were incorporated this week[1], mainly the update of the symmetric encryption to use NaCI. We feel, that it makes sense to release both at the same time. > >> > >> For aerogear-ios, a minor ?private' API change is needed, but would like a bit of time for testing. > >> > >> Let us know your thoughts/concerns. > >> > >> Regards > >> Christos > >> > >> [1] https://github.com/aerogear/aerogear-crypto-ios/pull/18 > >> > >> > >> On Mar 18, 2014, at 9:37 AM, Corinne Krych wrote: > >> > >>> Hello iOS Friends, > >>> > >>> AeroGear iOS 1.5 is on his way. We plan (if no objections raised) to release it end of this week. Main focus of 1.5 is to upgrade to iOS7 and AFNetworking 2.x (latest 2.2.1). > >>> > >>> To test it, open Podfile and point to the latest git branch > >>> pod 'AeroGear', :git => 'https://github.com/aerogear/aerogear-ios.git' > >>> > >>> Help us make this release a success, give it a trial, and let us know how it goes for your project. > >>> > >>> ++ > >>> 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 > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/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 corinnekrych at gmail.com Tue Mar 25 05:11:58 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Tue, 25 Mar 2014 10:11:58 +0100 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? In-Reply-To: References: Message-ID: On 25 Mar 2014, at 08:55, Sebastien Blanc wrote: > +1 > We got already almost all the material in the current readme and we can split that nicely into a howto and then rewriting maybe some parts. > > > > On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf wrote: > Hi, > > I feel a bit of the documentation might be misleading and not always that great to go over. > > Instead of adding more and more the README, I think we should (w/in the REPO) start to write a guide/book on HOWTO. +1 to add the doc in the relevant repo We could alway inlude part of the ascidoc text in aerogear web site with the same mechanism as shown in this PR: https://github.com/aerogear/aerogear.org/pull/275 > > Regarding the actual format, I think asciidoc comes to mind; > > > 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 From lukas.fryc at gmail.com Tue Mar 25 06:39:16 2014 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 25 Mar 2014 11:39:16 +0100 Subject: [aerogear-dev] AeroGear.js + ES6 In-Reply-To: <3DD039CA-843E-48E6-933C-C61571C89727@redhat.com> References: <3DD039CA-843E-48E6-933C-C61571C89727@redhat.com> Message-ID: +10 trans-compiling ES6 to ES5 I wonder how it will affect build step, particularly in development time, The tooling around ES6 seems to be pretty decent already. ECMAScript 6 Resources For The Curious JavaScripter http://addyosmani.com/blog/ecmascript-6-resources-for-the-curious-javascripter/ On Thu, Mar 20, 2014 at 6:27 PM, Lucas Holmquist wrote: > > On Mar 20, 2014, at 1:18 PM, tolis emmanouilidis > wrote: > > +1 for ES6 > > Do you think that ES6 classes will affect the way AeroGear.js library is > structured? > > > maybe a little in the way we do inheritance. > > > Thanks, > Tolis > > > 2014-03-20 16:50 GMT+02:00 Bruno Oliveira : > >> go for it, can't wait for ES7 and have a branch named "LEGEN...WAIT FOR >> IT...DARY!" >> >> -- >> abstractj >> >> On March 20, 2014 at 11:31:23 AM, Lucas Holmquist (lholmqui at redhat.com) >> wrote: >> > > Hey peeps, >> > >> > I've been seeing libraries such and Angular and Ember starting >> > to author in ES6( the next iteration of javascript ) and then >> transpiling >> > back to ES5( the current iteration of javascript ). >> > >> > So i've created a new branch called "get_to_tha_choppa" that >> > will be tracking these changes to see if we can benefit from this. >> > >> > this could also help us in the quest for AMD/Browser Modules/New >> > Fancy Term >> > >> > some related JIRA >> > >> > https://issues.jboss.org/browse/AGJS-149 >> > >> > incase people don't get the "get_to_tha_choppa" reference >> > >> > https://www.youtube.com/watch?v=Xs_OacEq2Sk >> > >> > >> > -Luke >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140325/8a25ef07/attachment.html From bruno at abstractj.org Tue Mar 25 07:04:56 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 25 Mar 2014 08:04:56 -0300 Subject: [aerogear-dev] AeroGear Security and friends deprecation In-Reply-To: References: Message-ID: Ahoy, answers inline -- abstractj On March 25, 2014 at 5:51:46 AM, Matthias Wessendorf (matzew at apache.org) wrote: > > Hello again! > > One thing that just came to mind is the implications for the clients.? It shouldn?t exist once we are server agnostic > > Today the client libs are supporting "AeroGear Security", for > cases like the RESTful login. I would say that?s a wrong assumption. Our client libraries rely on RESTful endpoints, not AG Security. For example, I could run AG Android against https://github.com/abstractj/example-jaxrs-shiro (Plain Shiro with RESTful endpoints)? > > For example, taking the iOS library: > https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/security/AGRestAuthentication.m > > This class somewhat expects an endpoint, that under the covers > uses AeroGear Security-PicketLink JAR. The AGIOS-35 ticket > is a good example of how client had to be changed due to updates > on the used version of PicketLink. If we?ve been doing it, that?s wrong. Because you tie the client with the server. I think the correct would be the opposite or some balance. For plain database authentication, the server could adapt its endpoints for what AeroGear expects. Or, the client should allow our dev to configure parameters.?AGIOS-35 seems to be hard-coded parameters, which ties the client with the server. For basic and digest authentication, both must follow the protocol specification. > > Now, I am wondering, what does the deprecation of the java libraries > mean for the client offerings? For instance, once we did port? I can be dead wrong, but this deprecation doesn?t mean to much to me. Why? AG Security is just few classes to fill in the gaps from PicketLink in the past. Our offerings should not be tied to the server side, at least for authentication. How could I authenticate with AeroGear and Node.js? In the worst case scenario, AG Security still exists. But we will no longer support it, so people can fork, copy and whatever they want.? > the endpoints (for instance on AeroDoc) to vanilla PicketLink, > should this iOS class/module just function like before? Or does? Yes, they just need to be adapted and have AG Security removed. Today, we don?t need anymore 2 jars only for login/logout. Just stick with Apache Shiro, PicketLink or Keycloak and that?s all. > it even make sense to keep that functionality? Or, instead of > on the "core" module (speaking iOS), would it make sense to move > it into a different/separate project ? I don?t think so, our focus relies on the client side and offerings for mobile on the server side. Security on the server is Keycloak and Picketlink responsibility, and yes, we will help on it. It doesn?t matter if is iOS, Android or JS, every project was supposed to be server agnostic. (Is just my opinion) > > Greetings, > Matthias > > [AGIOS-35] https://issues.jboss.org/browse/AGIOS-35 From matzew at apache.org Tue Mar 25 07:07:47 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 12:07:47 +0100 Subject: [aerogear-dev] UnifiedPush 0.10.2 - release coming soon (WAR and OpenShift) Message-ID: Hi, in order to be consistent with the DS name changes on master, we did apply them to the 0.10.x branch as well. That's the only content of the release: updated DS name changes. I have uploaded the WAR file to my _private_ staging repository: http://people.apache.org/~matzew/aerogear-staging/ Also, I have applied the updated WAR file (including the DB configuration change) to the OpenShift cartridge. See: https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/11 If you want to test it - it's simple! Just go ahead and use my fork of the repo: rhc app create --no-git https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.1 Let me know the results of your testing; If I hear nothing bad by Thursday evening, the merges will happen on Friday Greetings, 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/20140325/2086122a/attachment.html From kpiwko at redhat.com Tue Mar 25 07:26:59 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Tue, 25 Mar 2014 12:26:59 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> Message-ID: <20140325122659.38fb4055@kapy-ntb-x220> Given number of supported browsers is quite low - http://caniuse.com/promises, I believe that polyfill will be needed even with version 2.0. On Mon, 24 Mar 2014 12:01:38 -0400 Lucas Holmquist wrote: > > On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: > > > > > > > > > On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf > > wrote: > > > > > > > > On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc > > wrote: > > > > > > > > On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist > > wrote: > > > > On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis > > wrote: > > > >> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : > >> > >> > >> > >> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist > >> wrote: > >>> I agree that it would be nice to implement AGJS-70 (Investigate removing > >>> jQuery requirement). Meanwhile, there is an open source project on GitHub > >>> that claims to offer a custom builder for jQuery in order to include only > >>> the modules needed [1] [2]. I haven't tried it yet but maybe we could > >>> create a custom jQuery build which includes only the parts currently > >>> needed in AeroGear. This would mean a smaller size of the jQuery > >>> dependency. > >> > >> The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax > >> and the promise implementation. > >> > >> i know we can make custom builds of jQuery pretty easily( building from > >> source ), but i don't really want to bundle it within our lib. > >> > >> and i don't think with bower we can do this easily. although they did just > >> add a post install hook, so perhaps that could be something to look at. > >> > >> Datamanager only uses the promise implementation of jQuery( and some > >> random thing for the filter method, which could probably be updated ). > >> > >> > >> Promises are starting to become available natively in browsers and jQuery > >> doesn't use the Promise/A+ spec, so it could be harder to fallback > >> without a shim of some kind > >> > >> Good to know. Thanks for providing this info. > >> > >> > >> sounds reasonable to 'wait' on the promise side of things, and use that > >> bit in the datamanager > >> > >> +1 > > > > there are other promise implementations that we could use, that are to > > spec, such as Q and RSVP, here is the link to the HTML5 rocks article > > http://www.html5rocks.com/en/tutorials/es6/promises/ > > > > These last days I have been playing with the library When provided by Cujo, > > it's maybe also worth looking https://github.com/cujojs/when > > > > not sure I see value in using a different library as a temporary thing. > > Once the API is part of the browser platform, the need for [yet another js > > lib] goes away. I know but I'm more concerned about "Once the API is part > > of the browser platform" When will that happen and does it match with our > > roadmap ? Was also to offer a polyfill for older browser if we want to keep > > supporting them. > > > i will have to update the roadmap. > > 2.0 would be a nice time to "fully" switch, but we can start experimenting > now and maybe for 1.5 can have some implemenation for data manager only. > > Current Chrome has Promise's enable by default and it looks like FireFox > 29( next version ) will too. Safari and IE are in dev i believe > > for fallback we can still make use of jQuery i think because of this method > here "Promise.cast", although the closest lib to the spec is RSVP( maybe > this could be the 2.0 fallback if we remove jQuery from the whole lib ) > > > > > > > > > > > > >> > >> > >> > >> while i don't really want to reinvent the wheel in terms of Ajax, it > >> might be interesting to take a look. > >> > >> Yeah, IMO worth to look there, for reducing dependencies > >> > >> -M > >> > >> > >> > >> > >> I think in a previous ML thread about what 2.0 looked like, that > >> Pipeline would maybe just be a JSON only thing, with exception for > >> multipart > >> > >> > >> > >> @Lucas Thanks for making things clear > >> > >> > >> > >> > >> > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > >> > >> > >> -- > >> Matthias Wessendorf > >> > >> blog: http://matthiaswessendorf.wordpress.com/ > >> sessions: http://www.slideshare.net/mwessendorf > >> twitter: http://twitter.com/mwessendorf > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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 lukas.fryc at gmail.com Tue Mar 25 08:15:55 2014 From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=) Date: Tue, 25 Mar 2014 13:15:55 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: <20140325122659.38fb4055@kapy-ntb-x220> References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <20140325122659.38fb4055@kapy-ntb-x220> Message-ID: Side note: getting integration with jQuery{ajax,promises} right was one of the pain points when integrating with AeroGear.js / Angular (uses q.js, and custom http service). We must be sure whatever we choose is compatible with frameworks out there (at least it should not hard-nut to make it work). In terms of promises implementation. In the end people may even end up using 2-3 promise approaches in one project that makes code pretty disgusting. So: +1 getting rid of jQuery.ajax +1 getting rid of jQuery promises (they are just wrong anyway ;-) Btw in terms of polyfilling, I would suggest: 1) use whatever standard *is* as long as supported by majority of mainstream browsers 2) use whatever standard *will be *and compile polyfill into aerogear.js (as long as it's not too bloated; not necessary for bower users) Wdyt? On Tue, Mar 25, 2014 at 12:26 PM, Karel Piwko wrote: > Given number of supported browsers is quite low - > http://caniuse.com/promises, I > believe that polyfill will be needed even with version 2.0. > > On Mon, 24 Mar 2014 12:01:38 -0400 > Lucas Holmquist wrote: > > > > > On Mar 24, 2014, at 11:55 AM, Sebastien Blanc > wrote: > > > > > > > > > > > > > > On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf < > matzew at apache.org> > > > wrote: > > > > > > > > > > > > On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc > > > wrote: > > > > > > > > > > > > On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist > > > wrote: > > > > > > On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis > > > wrote: > > > > > >> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : > > >> > > >> > > >> > > >> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist > > > >> wrote: > > >>> I agree that it would be nice to implement AGJS-70 (Investigate > removing > > >>> jQuery requirement). Meanwhile, there is an open source project on > GitHub > > >>> that claims to offer a custom builder for jQuery in order to include > only > > >>> the modules needed [1] [2]. I haven't tried it yet but maybe we could > > >>> create a custom jQuery build which includes only the parts currently > > >>> needed in AeroGear. This would mean a smaller size of the jQuery > > >>> dependency. > > >> > > >> The AG lib depends on a few parts of jQuery, the biggest being > jQuery.Ajax > > >> and the promise implementation. > > >> > > >> i know we can make custom builds of jQuery pretty easily( building > from > > >> source ), but i don't really want to bundle it within our lib. > > >> > > >> and i don't think with bower we can do this easily. although they did > just > > >> add a post install hook, so perhaps that could be something to look > at. > > >> > > >> Datamanager only uses the promise implementation of jQuery( and some > > >> random thing for the filter method, which could probably be updated > ). > > >> > > >> > > >> Promises are starting to become available natively in browsers and > jQuery > > >> doesn't use the Promise/A+ spec, so it could be harder to fallback > > >> without a shim of some kind > > >> > > >> Good to know. Thanks for providing this info. > > >> > > >> > > >> sounds reasonable to 'wait' on the promise side of things, and use > that > > >> bit in the datamanager > > >> > > >> +1 > > > > > > there are other promise implementations that we could use, that are to > > > spec, such as Q and RSVP, here is the link to the HTML5 rocks article > > > http://www.html5rocks.com/en/tutorials/es6/promises/ > > > > > > These last days I have been playing with the library When provided by > Cujo, > > > it's maybe also worth looking https://github.com/cujojs/when > > > > > > not sure I see value in using a different library as a temporary thing. > > > Once the API is part of the browser platform, the need for [yet > another js > > > lib] goes away. I know but I'm more concerned about "Once the API is > part > > > of the browser platform" When will that happen and does it match with > our > > > roadmap ? Was also to offer a polyfill for older browser if we want to > keep > > > supporting them. > > > > > i will have to update the roadmap. > > > > 2.0 would be a nice time to "fully" switch, but we can start > experimenting > > now and maybe for 1.5 can have some implemenation for data manager only. > > > > Current Chrome has Promise's enable by default and it looks like FireFox > > 29( next version ) will too. Safari and IE are in dev i believe > > > > for fallback we can still make use of jQuery i think because of this > method > > here "Promise.cast", although the closest lib to the spec is RSVP( > maybe > > this could be the 2.0 fallback if we remove jQuery from the whole lib ) > > > > > > > > > > > > > > > > > > > > >> > > >> > > >> > > >> while i don't really want to reinvent the wheel in terms of Ajax, it > > >> might be interesting to take a look. > > >> > > >> Yeah, IMO worth to look there, for reducing dependencies > > >> > > >> -M > > >> > > >> > > >> > > >> > > >> I think in a previous ML thread about what 2.0 looked like, that > > >> Pipeline would maybe just be a JSON only thing, with exception for > > >> multipart > > >> > > >> > > >> > > >> @Lucas Thanks for making things clear > > >> > > >> > > >> > > >> > > >> > > >> > > >> _______________________________________________ > > >> aerogear-dev mailing list > > >> aerogear-dev at lists.jboss.org > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > >> > > >> > > >> > > >> -- > > >> Matthias Wessendorf > > >> > > >> blog: http://matthiaswessendorf.wordpress.com/ > > >> sessions: http://www.slideshare.net/mwessendorf > > >> twitter: http://twitter.com/mwessendorf > > >> > > >> _______________________________________________ > > >> aerogear-dev mailing list > > >> aerogear-dev at lists.jboss.org > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > >> > > >> _______________________________________________ > > >> aerogear-dev mailing list > > >> aerogear-dev at lists.jboss.org > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > sessions: http://www.slideshare.net/mwessendorf > > > twitter: http://twitter.com/mwessendorf > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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/20140325/85ab2da9/attachment.html From matzew at apache.org Tue Mar 25 08:37:24 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 13:37:24 +0100 Subject: [aerogear-dev] AeroGear Security and friends deprecation In-Reply-To: References: Message-ID: On Tue, Mar 25, 2014 at 12:04 PM, Bruno Oliveira wrote: > Ahoy, answers inline > > -- > abstractj > > On March 25, 2014 at 5:51:46 AM, Matthias Wessendorf (matzew at apache.org) > wrote: > > > Hello again! > > > > One thing that just came to mind is the implications for the clients. > > It shouldn't exist once we are server agnostic > you mean no implications on the client, right ? > > > > > Today the client libs are supporting "AeroGear Security", for > > cases like the RESTful login. > > I would say that's a wrong assumption. Our client libraries rely on > RESTful endpoints, not AG Security. For example, I could run AG Android > against https://github.com/abstractj/example-jaxrs-shiro (Plain Shiro > with RESTful endpoints) > > > > > For example, taking the iOS library: > > > https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/security/AGRestAuthentication.m > > > > This class somewhat expects an endpoint, that under the covers > > uses AeroGear Security-PicketLink JAR. The AGIOS-35 ticket > > is a good example of how client had to be changed due to updates > > on the used version of PicketLink. > > If we've been doing it, that's wrong. Because you tie the client with the > server. I think the correct would be the opposite or some balance. > > For plain database authentication, the server could adapt its endpoints > for what AeroGear expects. Or, the client should allow our dev to configure > parameters. AGIOS-35 seems to be hard-coded parameters, which ties the > client with the server. > yep, it's pretty much aligned to that. I think same is true for other client offerings as well (not really sure) > > For basic and digest authentication, both must follow the protocol > specification. > right - that's way simpler, as we have an actual protocol there (similar to OAuth2) > > > > > Now, I am wondering, what does the deprecation of the java libraries > > mean for the client offerings? For instance, once we did port > > I can be dead wrong, but this deprecation doesn't mean to much to me. Why? > AG Security is just few classes to fill in the gaps from PicketLink in the > past. > > Our offerings should not be tied to the server side, at least for > authentication. yeah - I am not sure that is really the case - I can be wrong; But I think that the "AGRestAuthentication.m" is a bit tied to AG Security's PicketLink Module > How could I authenticate with AeroGear and Node.js? > I don't know. I *think* IF the endpoints would actually follow this spec, it would work: http://aerogear.org/docs/specs/aerogear-rest-api/#aerogear-security But my hope is that, in the future, we only have OAuth2 and the 'legacy' bits like BASIC/DIGEST. Great thing here: they are actually (well) defined protocols. > > In the worst case scenario, AG Security still exists. But we will no > longer support it, so people can fork, copy and whatever they want. > > > > > the endpoints (for instance on AeroDoc) to vanilla PicketLink, > > should this iOS class/module just function like before? Or does > > Yes, they just need to be adapted and have AG Security removed. Today, we > don't need anymore 2 jars only for login/logout. Just stick with Apache > Shiro, PicketLink So, yeah if the endpoints ported to plain PL/Shiro/etc they would have to follow this spec, right ? http://aerogear.org/docs/specs/aerogear-rest-api/#aerogear-security > or Keycloak and that's all. > > > it even make sense to keep that functionality? Or, instead of > > on the "core" module (speaking iOS), would it make sense to move > > it into a different/separate project ? > > I don't think so, our focus relies on the client side and offerings for > mobile on the server side. Security on the server is Keycloak and > Picketlink responsibility, and yes, we will help on it. > > It doesn't matter if is iOS, Android or JS, every project was supposed to > be server agnostic. (Is just my opinion) > yeah - I picked iOS only because I know that code a bit better than Android or JS ;-) > > > > > Greetings, > > Matthias > > > > > [AGIOS-35] https://issues.jboss.org/browse/AGIOS-35 > > -- 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/20140325/7d7d7520/attachment-0001.html From lholmqui at redhat.com Tue Mar 25 08:53:48 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 25 Mar 2014 08:53:48 -0400 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? In-Reply-To: References: Message-ID: did we discuss using the wiki, or was that for something else On Mar 25, 2014, at 5:11 AM, Corinne Krych wrote: > > On 25 Mar 2014, at 08:55, Sebastien Blanc wrote: > >> +1 >> We got already almost all the material in the current readme and we can split that nicely into a howto and then rewriting maybe some parts. >> >> >> >> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf wrote: >> Hi, >> >> I feel a bit of the documentation might be misleading and not always that great to go over. >> >> Instead of adding more and more the README, I think we should (w/in the REPO) start to write a guide/book on HOWTO. > > +1 to add the doc in the relevant repo > We could alway inlude part of the ascidoc text in aerogear web site with the same mechanism as shown in this PR: > https://github.com/aerogear/aerogear.org/pull/275 > > >> >> Regarding the actual format, I think asciidoc comes to mind; >> >> >> 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 From kpiwko at redhat.com Tue Mar 25 08:53:57 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Tue, 25 Mar 2014 13:53:57 +0100 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <20140325122659.38fb4055@kapy-ntb-x220> Message-ID: <20140325135357.6ee27042@kapy-ntb-x220> On Tue, 25 Mar 2014 13:15:55 +0100 Luk?? Fry? wrote: > Side note: getting integration with jQuery{ajax,promises} right was one of > the pain points when integrating with AeroGear.js / Angular (uses q.js, and > custom http service). > > We must be sure whatever we choose is compatible with frameworks out there > (at least it should not hard-nut to make it work). In terms of promises > implementation. In the end people may even end up using 2-3 promise > approaches in one project that makes code pretty disgusting. > > So: > > +1 getting rid of jQuery.ajax > +1 getting rid of jQuery promises (they are just wrong anyway ;-) > > > Btw in terms of polyfilling, I would suggest: > > 1) use whatever standard *is* as long as supported by majority of > mainstream browsers > > 2) use whatever standard *will be *and compile polyfill into aerogear.js > (as long as it's not too bloated; not necessary for bower users) > +1 I'd just add performance as additional criterion for polyfill selection. Especially if we want to consider AGJS being used from Cordova apps. > Wdyt? > > > > On Tue, Mar 25, 2014 at 12:26 PM, Karel Piwko wrote: > > > Given number of supported browsers is quite low - > > http://caniuse.com/promises, I > > believe that polyfill will be needed even with version 2.0. > > > > On Mon, 24 Mar 2014 12:01:38 -0400 > > Lucas Holmquist wrote: > > > > > > > > On Mar 24, 2014, at 11:55 AM, Sebastien Blanc > > wrote: > > > > > > > > > > > > > > > > > > > On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf < > > matzew at apache.org> > > > > wrote: > > > > > > > > > > > > > > > > On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc > > > > wrote: > > > > > > > > > > > > > > > > On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist > > > > wrote: > > > > > > > > On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis > > > > wrote: > > > > > > > >> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : > > > >> > > > >> > > > >> > > > >> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist > > > > > >> wrote: > > > >>> I agree that it would be nice to implement AGJS-70 (Investigate > > removing > > > >>> jQuery requirement). Meanwhile, there is an open source project on > > GitHub > > > >>> that claims to offer a custom builder for jQuery in order to include > > only > > > >>> the modules needed [1] [2]. I haven't tried it yet but maybe we could > > > >>> create a custom jQuery build which includes only the parts currently > > > >>> needed in AeroGear. This would mean a smaller size of the jQuery > > > >>> dependency. > > > >> > > > >> The AG lib depends on a few parts of jQuery, the biggest being > > jQuery.Ajax > > > >> and the promise implementation. > > > >> > > > >> i know we can make custom builds of jQuery pretty easily( building > > from > > > >> source ), but i don't really want to bundle it within our lib. > > > >> > > > >> and i don't think with bower we can do this easily. although they did > > just > > > >> add a post install hook, so perhaps that could be something to look > > at. > > > >> > > > >> Datamanager only uses the promise implementation of jQuery( and some > > > >> random thing for the filter method, which could probably be updated > > ). > > > >> > > > >> > > > >> Promises are starting to become available natively in browsers and > > jQuery > > > >> doesn't use the Promise/A+ spec, so it could be harder to fallback > > > >> without a shim of some kind > > > >> > > > >> Good to know. Thanks for providing this info. > > > >> > > > >> > > > >> sounds reasonable to 'wait' on the promise side of things, and use > > that > > > >> bit in the datamanager > > > >> > > > >> +1 > > > > > > > > there are other promise implementations that we could use, that are to > > > > spec, such as Q and RSVP, here is the link to the HTML5 rocks article > > > > http://www.html5rocks.com/en/tutorials/es6/promises/ > > > > > > > > These last days I have been playing with the library When provided by > > Cujo, > > > > it's maybe also worth looking https://github.com/cujojs/when > > > > > > > > not sure I see value in using a different library as a temporary thing. > > > > Once the API is part of the browser platform, the need for [yet > > another js > > > > lib] goes away. I know but I'm more concerned about "Once the API is > > part > > > > of the browser platform" When will that happen and does it match with > > our > > > > roadmap ? Was also to offer a polyfill for older browser if we want to > > keep > > > > supporting them. > > > > > > > i will have to update the roadmap. > > > > > > 2.0 would be a nice time to "fully" switch, but we can start > > experimenting > > > now and maybe for 1.5 can have some implemenation for data manager only. > > > > > > Current Chrome has Promise's enable by default and it looks like FireFox > > > 29( next version ) will too. Safari and IE are in dev i believe > > > > > > for fallback we can still make use of jQuery i think because of this > > method > > > here "Promise.cast", although the closest lib to the spec is RSVP( > > maybe > > > this could be the 2.0 fallback if we remove jQuery from the whole lib ) > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > > > >> > > > >> > > > >> while i don't really want to reinvent the wheel in terms of Ajax, it > > > >> might be interesting to take a look. > > > >>http://postimg.org/image/6mbqdbvkv/ > > > >> Yeah, IMO worth to look there, for reducing dependencies > > > >> > > > >> -M > > > >> > > > >> > > > >> > > > >> > > > >> I think in a previous ML thread about what 2.0 looked like, that > > > >> Pipeline would maybe just be a JSON only thing, with exception for > > > >> multipart > > > >> > > > >> > > > >> > > > >> @Lucas Thanks for making things clear > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> _______________________________________________ > > > >> aerogear-dev mailing list > > > >> aerogear-dev at lists.jboss.org > > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > >> > > > >> > > > >> > > > >> -- > > > >> Matthias Wessendorf > > > >> > > > >> blog: http://matthiaswessendorf.wordpress.com/ > > > >> sessions: http://www.slideshare.net/mwessendorf > > > >> twitter: http://twitter.com/mwessendorf > > > >> > > > >> _______________________________________________ > > > >> aerogear-dev mailing list > > > >> aerogear-dev at lists.jboss.org > > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > >> > > > >> _______________________________________________ > > > >> aerogear-dev mailing list > > > >> aerogear-dev at lists.jboss.org > > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > -- > > > > Matthias Wessendorf > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > sessions: http://www.slideshare.net/mwessendorf > > > > twitter: http://twitter.com/mwessendorf > > > > > > > > _______________________________________________ > > > > aerogear-dev mailing list > > > > aerogear-dev at lists.jboss.org > > > > https://lists.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 Tue Mar 25 08:55:43 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 13:55:43 +0100 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? In-Reply-To: References: Message-ID: On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist wrote: > did we discuss using the wiki, or was that for something else > not sure - wiki is nice, but a real guide/book is really something I prefer for the "official" documentation. wiki could be: setup up your XFVZ Database etc > On Mar 25, 2014, at 5:11 AM, Corinne Krych wrote: > > > > > On 25 Mar 2014, at 08:55, Sebastien Blanc wrote: > > > >> +1 > >> We got already almost all the material in the current readme and we can > split that nicely into a howto and then rewriting maybe some parts. > >> > >> > >> > >> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf > wrote: > >> Hi, > >> > >> I feel a bit of the documentation might be misleading and not always > that great to go over. > >> > >> Instead of adding more and more the README, I think we should (w/in the > REPO) start to write a guide/book on HOWTO. > > > > +1 to add the doc in the relevant repo > > We could alway inlude part of the ascidoc text in aerogear web site with > the same mechanism as shown in this PR: > > https://github.com/aerogear/aerogear.org/pull/275 > > > > > >> > >> Regarding the actual format, I think asciidoc comes to mind; > >> > >> > >> 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140325/c90e15dc/attachment.html From lholmqui at redhat.com Tue Mar 25 08:58:54 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 25 Mar 2014 08:58:54 -0400 Subject: [aerogear-dev] AeroGear.js without jQuery Discussion In-Reply-To: References: <6D6F35A3-BF5F-431E-A916-C5FB7966189E@redhat.com> <97A36F35-7C1C-4078-9594-ABD2A82A1D38@redhat.com> <20140325122659.38fb4055@kapy-ntb-x220> Message-ID: On Mar 25, 2014, at 8:15 AM, Luk?? Fry? wrote: > Side note: getting integration with jQuery{ajax,promises} right was one of the pain points when integrating with AeroGear.js / Angular (uses q.js, and custom http service). > i know they include their "own" version of jQuery > We must be sure whatever we choose is compatible with frameworks out there (at least it should not hard-nut to make it work). In terms of promises implementation. In the end people may even end up using 2-3 promise approaches in one project that makes code pretty disgusting. > > So: > > +1 getting rid of jQuery.ajax > +1 getting rid of jQuery promises (they are just wrong anyway ;-) > > > Btw in terms of polyfilling, I would suggest: > > 1) use whatever standard is as long as supported by majority of mainstream browsers > > 2) use whatever standard will be and compile polyfill into aerogear.js (as long as it's not too bloated; not necessary for bower users) > the polyfill i was thinking about is here https://github.com/jakearchibald/es6-promise it is just the spec and 2kb gzipped, which is nice and i think this could be an external( compiled in ) dep of the library > Wdyt? > > > > On Tue, Mar 25, 2014 at 12:26 PM, Karel Piwko wrote: > Given number of supported browsers is quite low - http://caniuse.com/promises, I > believe that polyfill will be needed even with version 2.0. > > On Mon, 24 Mar 2014 12:01:38 -0400 > Lucas Holmquist wrote: > > > > > On Mar 24, 2014, at 11:55 AM, Sebastien Blanc wrote: > > > > > > > > > > > > > > On Mon, Mar 24, 2014 at 4:26 PM, Matthias Wessendorf > > > wrote: > > > > > > > > > > > > On Mon, Mar 24, 2014 at 4:14 PM, Sebastien Blanc > > > wrote: > > > > > > > > > > > > On Mon, Mar 24, 2014 at 4:05 PM, Lucas Holmquist > > > wrote: > > > > > > On Mar 24, 2014, at 10:10 AM, tolis emmanouilidis > > > wrote: > > > > > >> 2014-03-24 15:39 GMT+02:00 Matthias Wessendorf : > > >> > > >> > > >> > > >> On Mon, Mar 24, 2014 at 2:03 PM, Lucas Holmquist > > >> wrote: > > >>> I agree that it would be nice to implement AGJS-70 (Investigate removing > > >>> jQuery requirement). Meanwhile, there is an open source project on GitHub > > >>> that claims to offer a custom builder for jQuery in order to include only > > >>> the modules needed [1] [2]. I haven't tried it yet but maybe we could > > >>> create a custom jQuery build which includes only the parts currently > > >>> needed in AeroGear. This would mean a smaller size of the jQuery > > >>> dependency. > > >> > > >> The AG lib depends on a few parts of jQuery, the biggest being jQuery.Ajax > > >> and the promise implementation. > > >> > > >> i know we can make custom builds of jQuery pretty easily( building from > > >> source ), but i don't really want to bundle it within our lib. > > >> > > >> and i don't think with bower we can do this easily. although they did just > > >> add a post install hook, so perhaps that could be something to look at. > > >> > > >> Datamanager only uses the promise implementation of jQuery( and some > > >> random thing for the filter method, which could probably be updated ). > > >> > > >> > > >> Promises are starting to become available natively in browsers and jQuery > > >> doesn't use the Promise/A+ spec, so it could be harder to fallback > > >> without a shim of some kind > > >> > > >> Good to know. Thanks for providing this info. > > >> > > >> > > >> sounds reasonable to 'wait' on the promise side of things, and use that > > >> bit in the datamanager > > >> > > >> +1 > > > > > > there are other promise implementations that we could use, that are to > > > spec, such as Q and RSVP, here is the link to the HTML5 rocks article > > > http://www.html5rocks.com/en/tutorials/es6/promises/ > > > > > > These last days I have been playing with the library When provided by Cujo, > > > it's maybe also worth looking https://github.com/cujojs/when > > > > > > not sure I see value in using a different library as a temporary thing. > > > Once the API is part of the browser platform, the need for [yet another js > > > lib] goes away. I know but I'm more concerned about "Once the API is part > > > of the browser platform" When will that happen and does it match with our > > > roadmap ? Was also to offer a polyfill for older browser if we want to keep > > > supporting them. > > > > > i will have to update the roadmap. > > > > 2.0 would be a nice time to "fully" switch, but we can start experimenting > > now and maybe for 1.5 can have some implemenation for data manager only. > > > > Current Chrome has Promise's enable by default and it looks like FireFox > > 29( next version ) will too. Safari and IE are in dev i believe > > > > for fallback we can still make use of jQuery i think because of this method > > here "Promise.cast", although the closest lib to the spec is RSVP( maybe > > this could be the 2.0 fallback if we remove jQuery from the whole lib ) > > > > > > > > > > > > > > > > > > > > >> > > >> > > >> > > >> while i don't really want to reinvent the wheel in terms of Ajax, it > > >> might be interesting to take a look. > > >> > > >> Yeah, IMO worth to look there, for reducing dependencies > > >> > > >> -M > > >> > > >> > > >> > > >> > > >> I think in a previous ML thread about what 2.0 looked like, that > > >> Pipeline would maybe just be a JSON only thing, with exception for > > >> multipart > > >> > > >> > > >> > > >> @Lucas Thanks for making things clear > > >> > > >> > > >> > > >> > > >> > > >> > > >> _______________________________________________ > > >> aerogear-dev mailing list > > >> aerogear-dev at lists.jboss.org > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > >> > > >> > > >> > > >> -- > > >> Matthias Wessendorf > > >> > > >> blog: http://matthiaswessendorf.wordpress.com/ > > >> sessions: http://www.slideshare.net/mwessendorf > > >> twitter: http://twitter.com/mwessendorf > > >> > > >> _______________________________________________ > > >> aerogear-dev mailing list > > >> aerogear-dev at lists.jboss.org > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > >> > > >> _______________________________________________ > > >> aerogear-dev mailing list > > >> aerogear-dev at lists.jboss.org > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > -- > > > Matthias Wessendorf > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > sessions: http://www.slideshare.net/mwessendorf > > > twitter: http://twitter.com/mwessendorf > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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/20140325/8a5330e5/attachment-0001.html From bruno at abstractj.org Tue Mar 25 10:36:20 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Tue, 25 Mar 2014 11:36:20 -0300 Subject: [aerogear-dev] AeroGear Security and friends deprecation In-Reply-To: References: Message-ID: > > On March 25, 2014 at 5:51:46 AM, Matthias Wessendorf (matzew at apache.org)? > > >? > > > One thing that just came to mind is the implications for the clients.? > >? > > It shouldn't exist once we are server agnostic? > >? >? >? > you mean no implications on the client, right ?? Yes!? > > >? > > > Now, I am wondering, what does the deprecation of the java libraries? > > > mean for the client offerings? For instance, once we did port? > >? > > I can be dead wrong, but this deprecation doesn't mean to much to me. Why?? > > AG Security is just few classes to fill in the gaps from PicketLink in the? > > past.? > >? > > Our offerings should not be tied to the server side, at least for? > > authentication.? >? >? > yeah - I am not sure that is really the case - I can be wrong; But I think? > that the "AGRestAuthentication.m" is a bit tied to AG Security's PicketLink? > Module? If that is happening, we must fix this.? >? > > How could I authenticate with AeroGear and Node.js?? > >? >? > I don't know. I *think* IF the endpoints would actually follow this spec,? > it would work:? > http://aerogear.org/docs/specs/aerogear-rest-api/#aerogear-security? Think about people interacting with legacies, they can?t just say ?hey, would you mind to change your endpoint??. For this reason,? we should have the flexibility to specify endpoints + parameters (https://github.com/aerogear/aerogear-android-cookbook/blob/master/src/org/jboss/aerogear/cookbook/authentication/HowToUseAuthentication.java#L70).? It shouldn't matter if the endpoint is ?login? or ?enroll?. Or parameters are ?login? or ?username?.? >? >? > But my hope is that, in the future, we only have OAuth2 and the 'legacy'? > bits like BASIC/DIGEST. Great thing here: they are actually (well) defined? > protocols.? That?s pretty much what we do today, I guess.? > > > the endpoints (for instance on AeroDoc) to vanilla PicketLink,? > > > should this iOS class/module just function like before? Or does? > >? > > Yes, they just need to be adapted and have AG Security removed. Today, we? > > don't need anymore 2 jars only for login/logout. Just stick with Apache? > > Shiro, PicketLink? >? >? > So, yeah if the endpoints ported to plain PL/Shiro/etc they would have to? > follow this spec, right ?? > http://aerogear.org/docs/specs/aerogear-rest-api/#aerogear-security? For examples, yes. But, we shouldn?t me tied to this. What would happen with the client if I want to name my endpoints with: ?/register?, ?/signin? and ?/signout? ? ? See: https://github.com/aerogear/aerogear-js/blob/master/tests/unit/authentication/authentication-rest.js#L13? > yeah - I picked iOS only because I know that code a bit better than Android? > or JS ;-)? I know, that new update for iOS 7.1 called ?drain my battery? is awesome. From matzew at apache.org Tue Mar 25 11:03:45 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 16:03:45 +0100 Subject: [aerogear-dev] AeroGear Security and friends deprecation In-Reply-To: References: Message-ID: On Tue, Mar 25, 2014 at 3:36 PM, Bruno Oliveira wrote: > > > On March 25, 2014 at 5:51:46 AM, Matthias Wessendorf ( > matzew at apache.org) > > > > > > > > One thing that just came to mind is the implications for the > clients. > > > > > > It shouldn't exist once we are server agnostic > > > > > > > > > you mean no implications on the client, right ? > > Yes! > > > > > > > > > Now, I am wondering, what does the deprecation of the java libraries > > > > mean for the client offerings? For instance, once we did port > > > > > > I can be dead wrong, but this deprecation doesn't mean to much to me. > Why? > > > AG Security is just few classes to fill in the gaps from PicketLink in > the > > > past. > > > > > > Our offerings should not be tied to the server side, at least for > > > authentication. > > > > > > yeah - I am not sure that is really the case - I can be wrong; But I > think > > that the "AGRestAuthentication.m" is a bit tied to AG Security's > PicketLink > > Module > > If that is happening, we must fix this. > > > > > > How could I authenticate with AeroGear and Node.js? > > > > > > > I don't know. I *think* IF the endpoints would actually follow this > spec, > > it would work: > > http://aerogear.org/docs/specs/aerogear-rest-api/#aerogear-security > > Think about people interacting with legacies, they can't just say "hey, > would you mind to change your endpoint?". For this reason, > we should have the flexibility to specify endpoints + parameters ( > https://github.com/aerogear/aerogear-android-cookbook/blob/master/src/org/jboss/aerogear/cookbook/authentication/HowToUseAuthentication.java#L70 > ). > > It shouldn't matter if the endpoint is "login" or "enroll". Or parameters > are "login" or "username". > right - it's already flexible :) > > > > > > > But my hope is that, in the future, we only have OAuth2 and the 'legacy' > > bits like BASIC/DIGEST. Great thing here: they are actually (well) > defined > > protocols. > > That's pretty much what we do today, I guess. > > > > > the endpoints (for instance on AeroDoc) to vanilla PicketLink, > > > > should this iOS class/module just function like before? Or does > > > > > > Yes, they just need to be adapted and have AG Security removed. Today, > we > > > don't need anymore 2 jars only for login/logout. Just stick with > Apache > > > Shiro, PicketLink > > > > > > So, yeah if the endpoints ported to plain PL/Shiro/etc they would have > to > > follow this spec, right ? > > http://aerogear.org/docs/specs/aerogear-rest-api/#aerogear-security > > For examples, yes. But, we shouldn't me tied to this. What would happen > with the client if I want to name my endpoints with: "/register", "/signin" > and "/signout" ? > > See: > https://github.com/aerogear/aerogear-js/blob/master/tests/unit/authentication/authentication-rest.js#L13 > > yep - that is present as well. -Matthias > > > yeah - I picked iOS only because I know that code a bit better than > Android > > or JS ;-) > > I know, that new update for iOS 7.1 called "drain my battery" is awesome. > -- 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/20140325/4f9bcdd4/attachment.html From antoine.matyja at worldline.com Tue Mar 25 11:40:37 2014 From: antoine.matyja at worldline.com (A577127) Date: Tue, 25 Mar 2014 08:40:37 -0700 (PDT) Subject: [aerogear-dev] UnifiedPush Server deployment Message-ID: <1395762037361-7086.post@n5.nabble.com> Hey everyone :) I'm new to AeroGear and I'm trying to run the UnifiedPush server to try to send push notifications to my apps. I tryed to follow the tutorial on Github but got stuck at the deployment step. Then I tryed to deploy the .war downloaded here but didn't get better results. Let me give you more details about what I did. I'm on Windows 7. I use a proxy (proxy:3128). - I downloaded JBoss EAP 6.1.0. I added an user and can run it with standalone.bat and log to the Administration console from localhost:8080. - I downloaded the project from Github (as a zip) : aerogear-unified-push-server-master - I added an H2 datasource (it seemed to be the easiest) thanks to the tutorial on Github. Seems ok. - I tryed to deploy the server with maven (as stated in the tutorial) : mvn package jboss-as:deploy, but got errors (like a lot) : - Then I found a .war file on the website so I tryed to deploy it directly. I tryed several ways : from the Administration console (got errors), from the cli (same thing) and by dragging the .war file to /standalone/deployments. It failed but gave the best results : Stuff seems OK but if I click on "ejb3" I get an error. I also get this when I start the standalone.bat script : (it says that 49 services failed or missed dependancies) That's it... I can give more details if you want. I would appreciate any help :) Thanks in advance ! -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Server-deployment-tp7086.html Sent from the aerogear-dev mailing list archive at Nabble.com. From vmfamaral at gmail.com Tue Mar 25 11:46:31 2014 From: vmfamaral at gmail.com (oxsav) Date: Tue, 25 Mar 2014 08:46:31 -0700 (PDT) Subject: [aerogear-dev] Unified Push Java client Message-ID: <1395762391924-7087.post@n5.nabble.com> Hello. I'm trying to use the UPS Java Client in one of my Java Projects. As it says here: https://github.com/aerogear/aerogear-unifiedpush-java-client in maven it is just needed to add that dependencies to our project. My java project is being done in grade so I assume that in the dependencies I just need to use this: compile "org.jboss.aerogear:unifiedpush-java-client:0.5.0" compile "org.jboss.resteasy:resteasy-jackson-provider:2.3.2.Final" Right? Then when I try to import the libraries like this: import org.jboss.aerogear.unifiedpush.JavaSender; import org.jboss.aerogear.unifiedpush.SenderClient; import org.jboss.aerogear.unifiedpush.message.MessageResponseCallback; import org.jboss.aerogear.unifiedpush.message.UnifiedMessage; that doesn't recognize the org.jboss.aerogear.. Any idea? Thanks VA -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Tue Mar 25 11:52:12 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 16:52:12 +0100 Subject: [aerogear-dev] UnifiedPush Server deployment In-Reply-To: <1395762037361-7086.post@n5.nabble.com> References: <1395762037361-7086.post@n5.nabble.com> Message-ID: Hello there! thanks for the interest in our UnifiedPush Server when using the 0.10.1 WAR file from here: http://aerogear.org/push/ Make sure you are using these database configurations: https://github.com/aerogear/aerogear-unifiedpush-server/tree/0.10.1/databases We changed the DS JNDI name, very recently on master branch :-) This setup has been tested on JBoss AS 7.1.1 - so I *believe* it should work on EAP 6.1.0. Karel, please correct me, if I am wrong :-) BTW. a 0.10.2 is about to be released to fix that ;-)) On Tue, Mar 25, 2014 at 4:40 PM, A577127 wrote: > Hey everyone :) > > I'm new to AeroGear and I'm trying to run the UnifiedPush server to try to > send push notifications to my apps. > I tryed to follow the tutorial on Github > but got stuck > at > the deployment step. Then I tryed to deploy the .war downloaded here > but didn't get better results. > > Let me give you more details about what I did. I'm on Windows 7. I use a > proxy (proxy:3128). > > - I downloaded JBoss EAP 6.1.0. I added an user and can run it with > standalone.bat and log to the Administration console from localhost:8080. > > - I downloaded the project from Github (as a zip) : > aerogear-unified-push-server-master > > - I added an H2 datasource (it seemed to be the easiest) thanks to the > tutorial on Github. Seems ok. > > - I tryed to deploy the server with maven (as stated in the tutorial) : mvn > package jboss-as:deploy, but got errors (like a lot) : > > > > - Then I found a .war file on the website > so > I tryed to deploy it directly. I tryed several ways : from the > Administration console (got errors), from the cli (same thing) and by > dragging the .war file to /standalone/deployments. It failed but gave the > best results : > > > > Stuff seems OK but if I click on "ejb3" I get an error. I also get this > when > I start the standalone.bat script : > > > (it says that 49 services failed or missed dependancies) > > That's it... I can give more details if you want. I would appreciate any > help :) > > Thanks in advance ! > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Server-deployment-tp7086.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140325/bc73dcf4/attachment-0001.html From marti1003 at hotmail.com Tue Mar 25 12:03:52 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Tue, 25 Mar 2014 11:03:52 -0500 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? In-Reply-To: References: , , , , Message-ID: maybe we can use http://jekyllrb.com/ here you are an example http://docs.scala-lang.org/ and source code https://github.com/scala/scala.github.com Date: Tue, 25 Mar 2014 13:55:43 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist wrote: did we discuss using the wiki, or was that for something else not sure - wiki is nice, but a real guide/book is really something I prefer for the "official" documentation. wiki could be: setup up your XFVZ Database etc On Mar 25, 2014, at 5:11 AM, Corinne Krych wrote: > > On 25 Mar 2014, at 08:55, Sebastien Blanc wrote: > >> +1 >> We got already almost all the material in the current readme and we can split that nicely into a howto and then rewriting maybe some parts. >> >> >> >> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf wrote: >> Hi, >> >> I feel a bit of the documentation might be misleading and not always that great to go over. >> >> Instead of adding more and more the README, I think we should (w/in the REPO) start to write a guide/book on HOWTO. > > +1 to add the doc in the relevant repo > We could alway inlude part of the ascidoc text in aerogear web site with the same mechanism as shown in this PR: > https://github.com/aerogear/aerogear.org/pull/275 > > >> >> Regarding the actual format, I think asciidoc comes to mind; >> >> >> 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 _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.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/20140325/02202f98/attachment.html From scm.blanc at gmail.com Tue Mar 25 12:05:10 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 25 Mar 2014 17:05:10 +0100 Subject: [aerogear-dev] Unified Push Java client In-Reply-To: <1395762391924-7087.post@n5.nabble.com> References: <1395762391924-7087.post@n5.nabble.com> Message-ID: Hi, I did just did a test using this simple build.gradle apply plugin: 'java' sourceCompatibility = 1.5 version = '1.0' repositories { mavenCentral() } dependencies { testCompile group: 'junit', name: 'junit', version: '4.11' compile "org.jboss.aerogear:unifiedpush-java-client:0.5.0" compile "org.jboss.resteasy:resteasy-jackson-provider:2.3.2.Final" } And it can compile withou problems using this simple class : import org.jboss.aerogear.unifiedpush.JavaSender; import org.jboss.aerogear.unifiedpush.SenderClient; public class SenderWrapper { public void SenderWrapper() { JavaSender defaultJavaSender = new SenderClient("http://localhost:8080/ag-push"); } } Are you sure that your gradle file has mavenCentral() enabled ? On Tue, Mar 25, 2014 at 4:46 PM, oxsav wrote: > Hello. I'm trying to use the UPS Java Client in one of my Java Projects. > > As it says here: > https://github.com/aerogear/aerogear-unifiedpush-java-client > > in maven it is just needed to add that dependencies to our project. > > My java project is being done in grade so I assume that in the dependencies > I just need to use this: > > compile "org.jboss.aerogear:unifiedpush-java-client:0.5.0" > compile "org.jboss.resteasy:resteasy-jackson-provider:2.3.2.Final" > > Right? > > Then when I try to import the libraries like this: > > import org.jboss.aerogear.unifiedpush.JavaSender; > import org.jboss.aerogear.unifiedpush.SenderClient; > import org.jboss.aerogear.unifiedpush.message.MessageResponseCallback; > import org.jboss.aerogear.unifiedpush.message.UnifiedMessage; > > that doesn't recognize the org.jboss.aerogear.. Any idea? > > Thanks VA > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140325/a0e24ae8/attachment.html From antoine.matyja at worldline.com Tue Mar 25 12:08:12 2014 From: antoine.matyja at worldline.com (A577127) Date: Tue, 25 Mar 2014 09:08:12 -0700 (PDT) Subject: [aerogear-dev] UnifiedPush Server deployment In-Reply-To: References: <1395762037361-7086.post@n5.nabble.com> Message-ID: <1395763692010-7091.post@n5.nabble.com> Thanks for you answer, You was right, the zip file from github contains an old datasource name. I removed my H2 datasource and created a new one with the right cli file and now it works better. I successfully deployed the .war but I don't get anything at localhost:8080/ag-push. Am I missing something ? -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Server-deployment-tp7086p7091.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Tue Mar 25 12:08:10 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 17:08:10 +0100 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? In-Reply-To: References: Message-ID: On Tue, Mar 25, 2014 at 5:03 PM, Willy Martin Aguirre Rodriguez < marti1003 at hotmail.com> wrote: > maybe we can use http://jekyllrb.com/ > > yeah - our actual website is already using that: https://github.com/aerogear/aerogear.org#building :-) > here you are an example http://docs.scala-lang.org/ > and source code https://github.com/scala/scala.github.com > > > ------------------------------ > Date: Tue, 25 Mar 2014 13:55:43 +0100 > From: matzew at apache.org > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation > improvements ? > > > > > > On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist wrote: > > did we discuss using the wiki, or was that for something else > > > not sure - wiki is nice, but a real guide/book is really something I > prefer for the "official" documentation. > > wiki could be: > setup up your XFVZ Database etc > > > > On Mar 25, 2014, at 5:11 AM, Corinne Krych wrote: > > > > > On 25 Mar 2014, at 08:55, Sebastien Blanc wrote: > > > >> +1 > >> We got already almost all the material in the current readme and we can > split that nicely into a howto and then rewriting maybe some parts. > >> > >> > >> > >> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf > wrote: > >> Hi, > >> > >> I feel a bit of the documentation might be misleading and not always > that great to go over. > >> > >> Instead of adding more and more the README, I think we should (w/in the > REPO) start to write a guide/book on HOWTO. > > > > +1 to add the doc in the relevant repo > > We could alway inlude part of the ascidoc text in aerogear web site with > the same mechanism as shown in this PR: > > https://github.com/aerogear/aerogear.org/pull/275 > > > > > >> > >> Regarding the actual format, I think asciidoc comes to mind; > >> > >> > >> 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140325/b2d8444d/attachment-0001.html From matzew at apache.org Tue Mar 25 12:10:51 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 17:10:51 +0100 Subject: [aerogear-dev] UnifiedPush Server deployment In-Reply-To: <1395763692010-7091.post@n5.nabble.com> References: <1395762037361-7086.post@n5.nabble.com> <1395763692010-7091.post@n5.nabble.com> Message-ID: On Tue, Mar 25, 2014 at 5:08 PM, A577127 wrote: > Thanks for you answer, > > You was right, the zip file from github contains an old datasource name. I > removed my H2 datasource and created a new one with the right cli file and > now it works better. I successfully deployed the .war but I don't get > anything at localhost:8080/ag-push. > I'd recomment to rename the "unifiedpush-server-0.10.1.war" file to -> "ag-push.war" If you didn't do that, it should be up on: http://localhost:8080/unifiedpush-server-0.10.1 -M > Am I missing something ? > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Server-deployment-tp7086p7091.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140325/59c88fa9/attachment.html From antoine.matyja at worldline.com Tue Mar 25 12:28:43 2014 From: antoine.matyja at worldline.com (A577127) Date: Tue, 25 Mar 2014 09:28:43 -0700 (PDT) Subject: [aerogear-dev] UnifiedPush Server deployment In-Reply-To: References: <1395762037361-7086.post@n5.nabble.com> <1395763692010-7091.post@n5.nabble.com> Message-ID: <1395764923967-7094.post@n5.nabble.com> Thanks for the quick help Everything works fine now. -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Server-deployment-tp7086p7094.html Sent from the aerogear-dev mailing list archive at Nabble.com. From vmfamaral at gmail.com Tue Mar 25 12:37:01 2014 From: vmfamaral at gmail.com (oxsav) Date: Tue, 25 Mar 2014 09:37:01 -0700 (PDT) Subject: [aerogear-dev] Unified Push Java client In-Reply-To: References: <1395762391924-7087.post@n5.nabble.com> Message-ID: <1395765421843-7095.post@n5.nabble.com> My build.gradle has this content: /apply plugin: 'java' apply plugin: 'eclipse' apply plugin: 'idea' defaultTasks = ['assemble'] sourceCompatibility = '1.7' targetCompatibility = '1.7' configurations { provided } repositories { //maven { url 'https://oss.sonatype.org/content/repositories/snapshots' } mavenCentral() } dependencies { provided "org.vert-x:vertx-core:$vertxVersion" provided "org.vert-x:vertx-platform:$vertxVersion" testCompile "org.vert-x:vertx-lang-java:$vertxVersion" testCompile( "org.vert-x:vertx-testframework:$vertxVersion" ) { transitive = false } testCompile "junit:junit:$junitVersion" // Libraries needed to run the scala tools //scalaTools "org.scala-lang:scala-compiler:$scalaVersion" //scalaTools "org.scala-lang:scala-library:$scalaVersion" // Libraries needed for scala api //compile "org.scala-lang:scala-library:$scalaVersion" compile "org.jboss.aerogear:unifiedpush-java-client:0.5.0" compile "org.jboss.resteasy:resteasy-jackson-provider:2.3.2.Final" } sourceSets { main { compileClasspath = compileClasspath + configurations.provided } } task copyMod( type:Copy, dependsOn: 'classes' ) { into "build/copyMod/$modulename-v$version" from 'build/classes/main' from 'src/main/conf' into( 'lib' ) { from configurations.compile } } task prepareVertxTest(type: Sync, dependsOn: ['copyMod']) { from 'build/copyMod' into 'build/tmp/mod-test' } test { // Can't have the app on the vert.x classpath classpath = files( classpath.findAll { !( it.toString() ==~ /.+build\/(classes|resources)\/main$/ ) } ) // Some vert.x properties systemProperty 'vertx.test.timeout', 15 systemProperty 'vertx.mods', "$projectDir/build/tmp/mod-test" systemProperty 'vertx.version', "$project.version" systemProperty 'module.name', "$modulename-v$version" // Dump output testLogging.showStandardStreams = true // No idea why we need to depend on testClasses... dependsOn << [ 'testClasses', 'copyMod', 'prepareVertxTest' ] } task collectDeps(type: Copy) { group = 'vert.x' description = 'conveniently collect dependencies for other IDEs' destinationDir = file("build/deps") into("compile") { from configurations.compile } into("test") { from configurations.testCompile } } // Package into build/libs/mod.zip task dist( type: Zip, dependsOn: 'copyMod' ) { group = 'vert.x' description = "Assembles a vert.x module in 'mod.zip' format" destinationDir = project.file('build/libs') archiveName = 'mod.zip' from project.file("build/copyMod") } task release( type: Copy, dependsOn: ['dist', 'jar'] ) { group = 'vert.x' description = "Builds the module for use in the module repository into mods/$modulename-v$version" destinationDir = project.file('build/release') into ("$modulename-v$version") { from 'build/libs/mod.zip' from 'README.md' } } task install(type: Copy, dependsOn: 'copyMod') { try { destinationDir = new File(System.getenv()['VERTX_MODS']) } catch(NullPointerException e) { } from 'build/copyMod' } / Anything that I'm missing? -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087p7095.html Sent from the aerogear-dev mailing list archive at Nabble.com. From kpiwko at redhat.com Tue Mar 25 12:45:09 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Tue, 25 Mar 2014 17:45:09 +0100 Subject: [aerogear-dev] UnifiedPush Server deployment In-Reply-To: <1395762037361-7086.post@n5.nabble.com> References: <1395762037361-7086.post@n5.nabble.com> Message-ID: <20140325174509.23ab250a@kapy-ntb-x220> Hey, in the first place, is there a reason why to use EAP 6.1.0 instead of EAP 6.2.0, which is available for instance here: http://www.jboss.org/products ? Anyway, steps I've used to run UPS with EAP 6.1.0: 1/ Get EAP 6.1.0 2/ Get UPS from http://aerogear.org/push/ (0.10.1) 3/ Get UPS helpers from 0.10.1 tag (git clone https://github.com/aerogear/aerogear-unifiedpush-server.git && cd aerogear-unifiedpush-server && git checkout 0.10.1) 4/ Add H2 datasource start EAP 6.1 and install datasource [aerogear-unifiedpush-server]$ ../jboss-eap-6.1/bin/jboss-cli.sh --file=databases/h2-database-config.cli 5/ Deploy UPS war cp unifiedpush-server-0.10.1.war jboss-eap-6.1/standalone/deployments/ 6/ Login at http://localhost:8080/unifiedpush-server-0.10.1/ and enjoy HTH, Karel On Tue, 25 Mar 2014 08:40:37 -0700 (PDT) A577127 wrote: > Hey everyone :) > > I'm new to AeroGear and I'm trying to run the UnifiedPush server to try to > send push notifications to my apps. > I tryed to follow the tutorial on Github > but got stuck at > the deployment step. Then I tryed to deploy the .war downloaded here > but didn't get better results. > > Let me give you more details about what I did. I'm on Windows 7. I use a > proxy (proxy:3128). > > - I downloaded JBoss EAP 6.1.0. I added an user and can run it with > standalone.bat and log to the Administration console from localhost:8080. > > - I downloaded the project from Github (as a zip) : > aerogear-unified-push-server-master > > - I added an H2 datasource (it seemed to be the easiest) thanks to the > tutorial on Github. Seems ok. > > - I tryed to deploy the server with maven (as stated in the tutorial) : mvn > package jboss-as:deploy, but got errors (like a lot) : > > > > - Then I found a .war file on the website so > I tryed to deploy it directly. I tryed several ways : from the > Administration console (got errors), from the cli (same thing) and by > dragging the .war file to /standalone/deployments. It failed but gave the > best results : > > > > Stuff seems OK but if I click on "ejb3" I get an error. I also get this when > I start the standalone.bat script : > > > (it says that 49 services failed or missed dependancies) > > That's it... I can give more details if you want. I would appreciate any > help :) > > Thanks in advance ! > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Server-deployment-tp7086.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From scm.blanc at gmail.com Tue Mar 25 13:02:29 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 25 Mar 2014 18:02:29 +0100 Subject: [aerogear-dev] Unified Push Java client In-Reply-To: <1395765421843-7095.post@n5.nabble.com> References: <1395762391924-7087.post@n5.nabble.com> <1395765421843-7095.post@n5.nabble.com> Message-ID: Looks correct to me, even if there are many stuff in there :) Are you building a vertx mod ? Could you try a simple gradle / java project and just add the Unified Push Java Client dependencies ? Just to see if it compiles. On Tue, Mar 25, 2014 at 5:37 PM, oxsav wrote: > My build.gradle has this content: > > /apply plugin: 'java' > apply plugin: 'eclipse' > apply plugin: 'idea' > > defaultTasks = ['assemble'] > > sourceCompatibility = '1.7' > targetCompatibility = '1.7' > > configurations { > provided > } > > repositories { > //maven { url 'https://oss.sonatype.org/content/repositories/snapshots' > } > mavenCentral() > } > > dependencies { > provided "org.vert-x:vertx-core:$vertxVersion" > provided "org.vert-x:vertx-platform:$vertxVersion" > > testCompile "org.vert-x:vertx-lang-java:$vertxVersion" > testCompile( "org.vert-x:vertx-testframework:$vertxVersion" ) { > transitive = false > } > testCompile "junit:junit:$junitVersion" > > // Libraries needed to run the scala tools > //scalaTools "org.scala-lang:scala-compiler:$scalaVersion" > //scalaTools "org.scala-lang:scala-library:$scalaVersion" > > // Libraries needed for scala api > //compile "org.scala-lang:scala-library:$scalaVersion" > > compile "org.jboss.aerogear:unifiedpush-java-client:0.5.0" > compile "org.jboss.resteasy:resteasy-jackson-provider:2.3.2.Final" > > } > > sourceSets { > main { > compileClasspath = compileClasspath + configurations.provided > } > } > > task copyMod( type:Copy, dependsOn: 'classes' ) { > into "build/copyMod/$modulename-v$version" > from 'build/classes/main' > from 'src/main/conf' > into( 'lib' ) { > from configurations.compile > } > } > > task prepareVertxTest(type: Sync, dependsOn: ['copyMod']) { > from 'build/copyMod' > into 'build/tmp/mod-test' > } > > test { > // Can't have the app on the vert.x classpath > classpath = files( classpath.findAll { > !( it.toString() ==~ /.+build\/(classes|resources)\/main$/ ) > } ) > > // Some vert.x properties > systemProperty 'vertx.test.timeout', 15 > systemProperty 'vertx.mods', "$projectDir/build/tmp/mod-test" > systemProperty 'vertx.version', "$project.version" > systemProperty 'module.name', "$modulename-v$version" > > // Dump output > testLogging.showStandardStreams = true > > // No idea why we need to depend on testClasses... > dependsOn << [ 'testClasses', 'copyMod', 'prepareVertxTest' ] > } > > task collectDeps(type: Copy) { > group = 'vert.x' > description = 'conveniently collect dependencies for other IDEs' > destinationDir = file("build/deps") > into("compile") { > from configurations.compile > } > into("test") { > from configurations.testCompile > } > } > > // Package into build/libs/mod.zip > task dist( type: Zip, dependsOn: 'copyMod' ) { > group = 'vert.x' > description = "Assembles a vert.x module in 'mod.zip' format" > destinationDir = project.file('build/libs') > archiveName = 'mod.zip' > from project.file("build/copyMod") > } > > task release( type: Copy, dependsOn: ['dist', 'jar'] ) { > group = 'vert.x' > description = "Builds the module for use in the module repository into > mods/$modulename-v$version" > destinationDir = project.file('build/release') > into ("$modulename-v$version") { > from 'build/libs/mod.zip' > from 'README.md' > } > } > > task install(type: Copy, dependsOn: 'copyMod') { > try { > destinationDir = new File(System.getenv()['VERTX_MODS']) > } catch(NullPointerException e) { > } > from 'build/copyMod' > } > / > > Anything that I'm missing? > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087p7095.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140325/4e8dd08c/attachment.html From kpiwko at redhat.com Tue Mar 25 13:12:22 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Tue, 25 Mar 2014 18:12:22 +0100 Subject: [aerogear-dev] Unified Push Java client In-Reply-To: <1395765421843-7095.post@n5.nabble.com> References: <1395762391924-7087.post@n5.nabble.com> <1395765421843-7095.post@n5.nabble.com> Message-ID: <20140325181222.341565d0@kapy-ntb-x220> On Tue, 25 Mar 2014 09:37:01 -0700 (PDT) oxsav wrote: > My build.gradle has this content: > > /apply plugin: 'java' > apply plugin: 'eclipse' > apply plugin: 'idea' > > defaultTasks = ['assemble'] > > sourceCompatibility = '1.7' > targetCompatibility = '1.7' > > configurations { > provided > } > > repositories { > //maven { url 'https://oss.sonatype.org/content/repositories/snapshots' } > mavenCentral() > } > > dependencies { > provided "org.vert-x:vertx-core:$vertxVersion" > provided "org.vert-x:vertx-platform:$vertxVersion" > > testCompile "org.vert-x:vertx-lang-java:$vertxVersion" > testCompile( "org.vert-x:vertx-testframework:$vertxVersion" ) { > transitive = false > } > testCompile "junit:junit:$junitVersion" > > // Libraries needed to run the scala tools > //scalaTools "org.scala-lang:scala-compiler:$scalaVersion" > //scalaTools "org.scala-lang:scala-library:$scalaVersion" > > // Libraries needed for scala api > //compile "org.scala-lang:scala-library:$scalaVersion" > > compile "org.jboss.aerogear:unifiedpush-java-client:0.5.0" > compile "org.jboss.resteasy:resteasy-jackson-provider:2.3.2.Final" > > } > > sourceSets { > main { > compileClasspath = compileClasspath + configurations.provided Is the line above correct? According to http://www.gradle.org/docs/current/dsl/org.gradle.api.tasks.SourceSet.html default value is project.configurations.compile What happens if you alter or remove this line altogether? > } > } > > task copyMod( type:Copy, dependsOn: 'classes' ) { > into "build/copyMod/$modulename-v$version" > from 'build/classes/main' > from 'src/main/conf' > into( 'lib' ) { > from configurations.compile > } > } > > task prepareVertxTest(type: Sync, dependsOn: ['copyMod']) { > from 'build/copyMod' > into 'build/tmp/mod-test' > } > > test { > // Can't have the app on the vert.x classpath > classpath = files( classpath.findAll { > !( it.toString() ==~ /.+build\/(classes|resources)\/main$/ ) > } ) > > // Some vert.x properties > systemProperty 'vertx.test.timeout', 15 > systemProperty 'vertx.mods', "$projectDir/build/tmp/mod-test" > systemProperty 'vertx.version', "$project.version" > systemProperty 'module.name', "$modulename-v$version" > > // Dump output > testLogging.showStandardStreams = true > > // No idea why we need to depend on testClasses... > dependsOn << [ 'testClasses', 'copyMod', 'prepareVertxTest' ] > } > > task collectDeps(type: Copy) { > group = 'vert.x' > description = 'conveniently collect dependencies for other IDEs' > destinationDir = file("build/deps") > into("compile") { > from configurations.compile > } > into("test") { > from configurations.testCompile > } > } > > // Package into build/libs/mod.zip > task dist( type: Zip, dependsOn: 'copyMod' ) { > group = 'vert.x' > description = "Assembles a vert.x module in 'mod.zip' format" > destinationDir = project.file('build/libs') > archiveName = 'mod.zip' > from project.file("build/copyMod") > } > > task release( type: Copy, dependsOn: ['dist', 'jar'] ) { > group = 'vert.x' > description = "Builds the module for use in the module repository into > mods/$modulename-v$version" > destinationDir = project.file('build/release') > into ("$modulename-v$version") { > from 'build/libs/mod.zip' > from 'README.md' > } > } > > task install(type: Copy, dependsOn: 'copyMod') { > try { > destinationDir = new File(System.getenv()['VERTX_MODS']) > } catch(NullPointerException e) { > } > from 'build/copyMod' > } > / > > Anything that I'm missing? > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087p7095.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From vmfamaral at gmail.com Tue Mar 25 13:25:23 2014 From: vmfamaral at gmail.com (oxsav) Date: Tue, 25 Mar 2014 10:25:23 -0700 (PDT) Subject: [aerogear-dev] Unified Push Java client In-Reply-To: References: <1395762391924-7087.post@n5.nabble.com> <1395765421843-7095.post@n5.nabble.com> Message-ID: <1395768323676-7099.post@n5.nabble.com> Yes I'm doing a vertx mod. The idea is my Javascript client contact this module and then this module will handle all the notification messages. Storing it in myserver and send it to the chrome app. Ok I will test it and then I will say if it is working. Tks -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087p7099.html Sent from the aerogear-dev mailing list archive at Nabble.com. From vmfamaral at gmail.com Tue Mar 25 13:28:04 2014 From: vmfamaral at gmail.com (oxsav) Date: Tue, 25 Mar 2014 10:28:04 -0700 (PDT) Subject: [aerogear-dev] Unified Push Java client In-Reply-To: <1395768323676-7099.post@n5.nabble.com> References: <1395762391924-7087.post@n5.nabble.com> <1395765421843-7095.post@n5.nabble.com> <1395768323676-7099.post@n5.nabble.com> Message-ID: <1395768484331-7100.post@n5.nabble.com> It can't compile it even modified or removed. Just can see this error: Could not execute build using Gradle distribution 'http://services.gradle.org/distributions/gradle-1.0-bin.zip VA -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087p7100.html Sent from the aerogear-dev mailing list archive at Nabble.com. From hbons at redhat.com Tue Mar 25 14:40:37 2014 From: hbons at redhat.com (Hylke Bons) Date: Tue, 25 Mar 2014 18:40:37 +0000 Subject: [aerogear-dev] UPS UX updates In-Reply-To: <5331B750.1060609@redhat.com> References: <5331B750.1060609@redhat.com> Message-ID: <5331CDA5.1050405@redhat.com> Hello, https://github.com/hbons/aerogear-design/tree/master/ups-new-ux The above link contains mockups with an updated look and feel. I've tried to consolodate the info that we had on different pages on fewer pages, as a common critique was that the Application Details and Variant Details pages looked alike too much, so I've merged them. On one page I've added a sidebar that reflects future features (it's just for show). Other notable things are the orange info blocks where we want app developers to take action on information (the device registration and sending notifications in this case). I've deliberately made these stand out a bit more as we want people to act on the information. Please note that one row in the variants table shows up expanded in the mockups for illustration purposes. The rows will all be collapsed on first view, so it won't look as cluttered as you might think at first seeing the mockup. Let me know what you think and where we should go from here. Thanks, Hylke From marti1003 at hotmail.com Tue Mar 25 15:15:21 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Tue, 25 Mar 2014 14:15:21 -0500 Subject: [aerogear-dev] UPS UX updates In-Reply-To: <5331CDA5.1050405@redhat.com> References: <5331B750.1060609@redhat.com>,<5331CDA5.1050405@redhat.com> Message-ID: Nice design :) Do you planning to use http://foundation.zurb.com/ or another css framework? > Date: Tue, 25 Mar 2014 18:40:37 +0000 > From: hbons at redhat.com > To: aerogear-dev at lists.jboss.org > Subject: [aerogear-dev] UPS UX updates > > > > Hello, > > https://github.com/hbons/aerogear-design/tree/master/ups-new-ux > The above link contains mockups with an updated look and feel. > > I've tried to consolodate the info that we had on different pages on > fewer pages, as a common critique was that the Application Details and > Variant Details pages looked alike too much, so I've merged them. > > On one page I've added a sidebar that reflects future features (it's > just for show). > > Other notable things are the orange info blocks where we want app > developers to take action on information (the device registration and > sending notifications in this case). I've deliberately made these stand > out a bit more as we want people to act on the information. Please note > that one row in the variants table shows up expanded in the mockups for > illustration purposes. The rows will all be collapsed on first view, so > it won't look as cluttered as you might think at first seeing the mockup. > > Let me know what you think and where we should go from here. > > Thanks, > > Hylke > > > > _______________________________________________ > 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/20140325/0d26574f/attachment.html From lholmqui at redhat.com Tue Mar 25 15:31:36 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Tue, 25 Mar 2014 15:31:36 -0400 Subject: [aerogear-dev] New JS branches Message-ID: <9E656BE0-E3DE-414A-91EF-A65A4DFCE062@redhat.com> Hello My Fellow peeps, I've created some new branches in AeroGear.js canary - this branch will be for experimental things. 2.0 - for 2.0 things like the jQuery removal process get_to_tha_choppa - this is the branch for tracking ES6 features and of course we still have master, which is just the current 1.X stuff -Luke From matzew at apache.org Tue Mar 25 15:50:19 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Mar 2014 20:50:19 +0100 Subject: [aerogear-dev] UPS UX updates In-Reply-To: <5331CDA5.1050405@redhat.com> References: <5331B750.1060609@redhat.com> <5331CDA5.1050405@redhat.com> Message-ID: Awesome mock ups!! On Tuesday, March 25, 2014, Hylke Bons wrote: > > > Hello, > > https://github.com/hbons/aerogear-design/tree/master/ups-new-ux > The above link contains mockups with an updated look and feel. > > I've tried to consolodate the info that we had on different pages on > fewer pages, as a common critique was that the Application Details and > Variant Details pages looked alike too much, so I've merged them. > > On one page I've added a sidebar that reflects future features (it's > just for show). > > Other notable things are the orange info blocks where we want app > developers to take action on information (the device registration and > sending notifications in this case). I've deliberately made these stand > out a bit more as we want people to act on the information. Please note > that one row in the variants table shows up expanded in the mockups for > illustration purposes. The rows will all be collapsed on first view, so > it won't look as cluttered as you might think at first seeing the mockup. > > Let me know what you think and where we should go from here. > > Thanks, > > Hylke > > > > _______________________________________________ > 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/20140325/42bd679a/attachment.html From scm.blanc at gmail.com Tue Mar 25 15:52:06 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 25 Mar 2014 20:52:06 +0100 Subject: [aerogear-dev] UPS UX updates In-Reply-To: References: <5331B750.1060609@redhat.com> <5331CDA5.1050405@redhat.com> Message-ID: +1 Really cool ! On Tue, Mar 25, 2014 at 8:50 PM, Matthias Wessendorf wrote: > Awesome mock ups!! > > > On Tuesday, March 25, 2014, Hylke Bons wrote: > >> >> >> Hello, >> >> https://github.com/hbons/aerogear-design/tree/master/ups-new-ux >> The above link contains mockups with an updated look and feel. >> >> I've tried to consolodate the info that we had on different pages on >> fewer pages, as a common critique was that the Application Details and >> Variant Details pages looked alike too much, so I've merged them. >> >> On one page I've added a sidebar that reflects future features (it's >> just for show). >> >> Other notable things are the orange info blocks where we want app >> developers to take action on information (the device registration and >> sending notifications in this case). I've deliberately made these stand >> out a bit more as we want people to act on the information. Please note >> that one row in the variants table shows up expanded in the mockups for >> illustration purposes. The rows will all be collapsed on first view, so >> it won't look as cluttered as you might think at first seeing the mockup. >> >> Let me know what you think and where we should go from here. >> >> Thanks, >> >> Hylke >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140325/a9687fa5/attachment.html From scm.blanc at gmail.com Tue Mar 25 15:52:52 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 25 Mar 2014 20:52:52 +0100 Subject: [aerogear-dev] UPS UX updates In-Reply-To: References: <5331B750.1060609@redhat.com> <5331CDA5.1050405@redhat.com> Message-ID: On Tue, Mar 25, 2014 at 8:15 PM, Willy Martin Aguirre Rodriguez < marti1003 at hotmail.com> wrote: > Nice design :) > > Do you planning to use > http://foundation.zurb.com/ or another css framework? > I think the plan is to use https://www.patternfly.org/ > > > > Date: Tue, 25 Mar 2014 18:40:37 +0000 > > From: hbons at redhat.com > > To: aerogear-dev at lists.jboss.org > > Subject: [aerogear-dev] UPS UX updates > > > > > > > > > Hello, > > > > https://github.com/hbons/aerogear-design/tree/master/ups-new-ux > > The above link contains mockups with an updated look and feel. > > > > I've tried to consolodate the info that we had on different pages on > > fewer pages, as a common critique was that the Application Details and > > Variant Details pages looked alike too much, so I've merged them. > > > > On one page I've added a sidebar that reflects future features (it's > > just for show). > > > > Other notable things are the orange info blocks where we want app > > developers to take action on information (the device registration and > > sending notifications in this case). I've deliberately made these stand > > out a bit more as we want people to act on the information. Please note > > that one row in the variants table shows up expanded in the mockups for > > illustration purposes. The rows will all be collapsed on first view, so > > it won't look as cluttered as you might think at first seeing the mockup. > > > > Let me know what you think and where we should go from here. > > > > Thanks, > > > > Hylke > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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/20140325/1e3e79b6/attachment-0001.html From marti1003 at hotmail.com Tue Mar 25 18:11:01 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Tue, 25 Mar 2014 17:11:01 -0500 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? In-Reply-To: References: , , , , , , Message-ID: Idea for documentation: Is it possible to use unifiedpush server work in tomcat or jetty? I don't have much experience about Redhat but about Tomcat or Jetty I know, how to deploy a war. maybe there is a equivalent maybe there is a equivalence between applications servers. Try to add image for doc. screenshots of Jboss Date: Tue, 25 Mar 2014 17:08:10 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? On Tue, Mar 25, 2014 at 5:03 PM, Willy Martin Aguirre Rodriguez wrote: maybe we can use http://jekyllrb.com/ yeah - our actual website is already using that: https://github.com/aerogear/aerogear.org#building :-) here you are an example http://docs.scala-lang.org/ and source code https://github.com/scala/scala.github.com Date: Tue, 25 Mar 2014 13:55:43 +0100 From: matzew at apache.org To: aerogear-dev at lists.jboss.org Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist wrote: did we discuss using the wiki, or was that for something else not sure - wiki is nice, but a real guide/book is really something I prefer for the "official" documentation. wiki could be: setup up your XFVZ Database etc On Mar 25, 2014, at 5:11 AM, Corinne Krych wrote: > > On 25 Mar 2014, at 08:55, Sebastien Blanc wrote: > >> +1 >> We got already almost all the material in the current readme and we can split that nicely into a howto and then rewriting maybe some parts. >> >> >> >> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf wrote: >> Hi, >> >> I feel a bit of the documentation might be misleading and not always that great to go over. >> >> Instead of adding more and more the README, I think we should (w/in the REPO) start to write a guide/book on HOWTO. > > +1 to add the doc in the relevant repo > We could alway inlude part of the ascidoc text in aerogear web site with the same mechanism as shown in this PR: > https://github.com/aerogear/aerogear.org/pull/275 > > >> >> Regarding the actual format, I think asciidoc comes to mind; >> >> >> 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 _______________________________________________ aerogear-dev mailing list aerogear-dev at lists.jboss.org https://lists.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/20140325/6d9b4599/attachment.html From scm.blanc at gmail.com Wed Mar 26 03:50:55 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 26 Mar 2014 08:50:55 +0100 Subject: [aerogear-dev] Unified Push Java client In-Reply-To: <1395768484331-7100.post@n5.nabble.com> References: <1395762391924-7087.post@n5.nabble.com> <1395765421843-7095.post@n5.nabble.com> <1395768323676-7099.post@n5.nabble.com> <1395768484331-7100.post@n5.nabble.com> Message-ID: Hi, So it's a Gradle installation issue, a bit out of scope of this mailing list. How did you installed Gradle ? Seb On Tue, Mar 25, 2014 at 6:28 PM, oxsav wrote: > It can't compile it even modified or removed. Just can see this error: > > Could not execute build using Gradle distribution > 'http://services.gradle.org/distributions/gradle-1.0-bin.zip > > VA > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087p7100.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140326/fcb30749/attachment.html From antoine.matyja at worldline.com Wed Mar 26 04:16:42 2014 From: antoine.matyja at worldline.com (A577127) Date: Wed, 26 Mar 2014 01:16:42 -0700 (PDT) Subject: [aerogear-dev] UnifiedPush Server deployment In-Reply-To: <20140325174509.23ab250a@kapy-ntb-x220> References: <1395762037361-7086.post@n5.nabble.com> <20140325174509.23ab250a@kapy-ntb-x220> Message-ID: <1395821802966-7109.post@n5.nabble.com> Thanks for your answer but my problem was already solved thanks to Matthias. :) I use EAP 6.1.0 because JBoss' official page for JBoss AS gave me this version. (see this link : http://www.jboss.org/jbossas ) -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Server-deployment-tp7086p7109.html Sent from the aerogear-dev mailing list archive at Nabble.com. From cvasilak at gmail.com Wed Mar 26 04:25:39 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Wed, 26 Mar 2014 10:25:39 +0200 Subject: [aerogear-dev] xctool and xcpretty Message-ID: <48FEF34A-6AF7-4453-8981-2A3C03486BA9@gmail.com> Hi everyone, During the last couple of days, as part of my AGIOS-181[1] work, got bumped by problem issues of xctool[2] during builds both local and on travis. Let me try to explain the two major issues faced: a) first the current release fails to run logic tests for an Xcode 5.1 project, fixed in ?master' some hours ago[3] b) starting up the emulator to run ?application' tests always failed on travis [4]. Not sure why, switching to the build-in xcodebuild fixed the issue, so I guess its some issue with xctool. (used to work prior). In a nutshell, xctool tries to mimic the behaviour of xcodebuild during builds and understandable it can?t catch up with its future developments. Major benefit of xctool is the nice formatting output during tests which helps a lot to identify issues. The ideal would be a tool that relies on xcodebuild (so it?s always up-to-date with apple development at the minute of the release) and give a nice formatting output of the results. Fortunately enough the flourish iOS OSS community stepped in and ?xcpretty? was created[5]. It provides the same benefits of xctool (if better) but relies on xcodebuild for its build for maximum compatibility. Already major projects have adopted for their builds[6]. I think it?s sensible if we follow this path and adopt xcpretty for our builds. Wdyt? Regards, Christos [1] https://issues.jboss.org/browse/AGIOS-181 [2] https://github.com/facebook/xctool [3] https://github.com/facebook/xctool/issues/337 [4] https://travis-ci.org/cvasilak/aerogear-ios-integration/builds/21524580 [5] https://github.com/supermarin/xcpretty [6] https://github.com/AFNetworking/AFNetworking/blob/master/Rakefile#L34 From daniel.bevenius at gmail.com Wed Mar 26 04:28:46 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Wed, 26 Mar 2014 09:28:46 +0100 Subject: [aerogear-dev] xctool and xcpretty In-Reply-To: <48FEF34A-6AF7-4453-8981-2A3C03486BA9@gmail.com> References: <48FEF34A-6AF7-4453-8981-2A3C03486BA9@gmail.com> Message-ID: +1 Sounds like a good plan! On 26 March 2014 09:25, Christos Vasilakis wrote: > Hi everyone, > > During the last couple of days, as part of my AGIOS-181[1] work, got > bumped by problem issues of xctool[2] during builds both local and on > travis. Let me try to explain the two major issues faced: > > a) first the current release fails to run logic tests for an Xcode 5.1 > project, fixed in 'master' some hours ago[3] > b) starting up the emulator to run 'application' tests always failed on > travis [4]. Not sure why, switching to the build-in xcodebuild fixed the > issue, so I guess its some issue with xctool. (used to work prior). > > In a nutshell, xctool tries to mimic the behaviour of xcodebuild during > builds and understandable it can't catch up with its future developments. > Major benefit of xctool is the nice formatting output during tests which > helps a lot to identify issues. The ideal would be a tool that relies on > xcodebuild (so it's always up-to-date with apple development at the minute > of the release) and give a nice formatting output of the results. > Fortunately enough the flourish iOS OSS community stepped in and 'xcpretty' > was created[5]. It provides the same benefits of xctool (if better) but > relies on xcodebuild for its build for maximum compatibility. Already major > projects have adopted for their builds[6]. > > I think it's sensible if we follow this path and adopt xcpretty for our > builds. > > Wdyt? > > Regards, > Christos > > > > [1] https://issues.jboss.org/browse/AGIOS-181 > [2] https://github.com/facebook/xctool > [3] https://github.com/facebook/xctool/issues/337 > [4] > https://travis-ci.org/cvasilak/aerogear-ios-integration/builds/21524580 > [5] https://github.com/supermarin/xcpretty > [6] https://github.com/AFNetworking/AFNetworking/blob/master/Rakefile#L34 > > > _______________________________________________ > 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/20140326/d42ca5e4/attachment-0001.html From matzew at apache.org Wed Mar 26 04:30:39 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 09:30:39 +0100 Subject: [aerogear-dev] UPS UX updates In-Reply-To: References: <5331B750.1060609@redhat.com> <5331CDA5.1050405@redhat.com> Message-ID: As said before: overall they are really looking very great and modern! I really like them. A few questions on some of the screens: * applications.png List ("table") of all Push Applications: - Is there no side bar for this? * application-details-blue.png It's the details of one application, and has overview of all its variants. - Is the plan to list all variants on their platform? Instead of having a table? I do like that grouping! Just wondering :-) - When I click on a certain variant (e.g. the "Demo" variant of the iOS section ), there is no separate page/view for its' details? Like its installations ? I'd really prefer to have a page/view for all the details of a certain variant. Also the code snippets for a variant is missing - Sidebar: is that specific to an application? See notes on "applications.png" - The "Notifications" on the sidebar, what's that? - What's the "gear-wheel" for ? * "dialogs.png" - For an application construct, that's good enough; Creating a variant is a bit more complex (see current UI) - Is there no side bar for this? * installations.png - Is there no side bar for this? - If I understand the view/page correctly, its a list of ALL installations for one PushApplication. However, we should list the variants PER variant (see current UI). The Navigation path on the bread-crumbs would be "Applications >> Mobile HR >> Demo (iOS) >> Installations (number)" * loading.png - yeah, that is totally missing today :-)) Greetings, Matthias On Tue, Mar 25, 2014 at 8:50 PM, Matthias Wessendorf wrote: > Awesome mock ups!! > > > On Tuesday, March 25, 2014, Hylke Bons wrote: > >> >> >> Hello, >> >> https://github.com/hbons/aerogear-design/tree/master/ups-new-ux >> The above link contains mockups with an updated look and feel. >> >> I've tried to consolodate the info that we had on different pages on >> fewer pages, as a common critique was that the Application Details and >> Variant Details pages looked alike too much, so I've merged them. >> >> On one page I've added a sidebar that reflects future features (it's >> just for show). >> >> Other notable things are the orange info blocks where we want app >> developers to take action on information (the device registration and >> sending notifications in this case). I've deliberately made these stand >> out a bit more as we want people to act on the information. Please note >> that one row in the variants table shows up expanded in the mockups for >> illustration purposes. The rows will all be collapsed on first view, so >> it won't look as cluttered as you might think at first seeing the mockup. >> >> Let me know what you think and where we should go from here. >> >> Thanks, >> >> Hylke >> >> >> >> _______________________________________________ >> 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/20140326/ce6d47fc/attachment.html From matzew at apache.org Wed Mar 26 04:43:54 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 09:43:54 +0100 Subject: [aerogear-dev] xctool and xcpretty In-Reply-To: <48FEF34A-6AF7-4453-8981-2A3C03486BA9@gmail.com> References: <48FEF34A-6AF7-4453-8981-2A3C03486BA9@gmail.com> Message-ID: great analysis ! and yes, I agree it's a good plan! On Wed, Mar 26, 2014 at 9:25 AM, Christos Vasilakis wrote: > Hi everyone, > > During the last couple of days, as part of my AGIOS-181[1] work, got > bumped by problem issues of xctool[2] during builds both local and on > travis. Let me try to explain the two major issues faced: > > a) first the current release fails to run logic tests for an Xcode 5.1 > project, fixed in 'master' some hours ago[3] > b) starting up the emulator to run 'application' tests always failed on > travis [4]. Not sure why, switching to the build-in xcodebuild fixed the > issue, so I guess its some issue with xctool. (used to work prior). > > In a nutshell, xctool tries to mimic the behaviour of xcodebuild during > builds and understandable it can't catch up with its future developments. > Major benefit of xctool is the nice formatting output during tests which > helps a lot to identify issues. The ideal would be a tool that relies on > xcodebuild (so it's always up-to-date with apple development at the minute > of the release) and give a nice formatting output of the results. > Fortunately enough the flourish iOS OSS community stepped in and 'xcpretty' > was created[5]. It provides the same benefits of xctool (if better) but > relies on xcodebuild for its build for maximum compatibility. Already major > projects have adopted for their builds[6]. > > I think it's sensible if we follow this path and adopt xcpretty for our > builds. > > Wdyt? > > Regards, > Christos > > > > [1] https://issues.jboss.org/browse/AGIOS-181 > [2] https://github.com/facebook/xctool > [3] https://github.com/facebook/xctool/issues/337 > [4] > https://travis-ci.org/cvasilak/aerogear-ios-integration/builds/21524580 > [5] https://github.com/supermarin/xcpretty > [6] https://github.com/AFNetworking/AFNetworking/blob/master/Rakefile#L34 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140326/1179157f/attachment.html From kpiwko at redhat.com Wed Mar 26 05:03:14 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 26 Mar 2014 10:03:14 +0100 Subject: [aerogear-dev] xctool and xcpretty In-Reply-To: <48FEF34A-6AF7-4453-8981-2A3C03486BA9@gmail.com> References: <48FEF34A-6AF7-4453-8981-2A3C03486BA9@gmail.com> Message-ID: <20140326100314.0ff19676@kapy-ntb-x220> Anything that helps stability of iOS testing env will get automatic +1 for me. We fee the pain of xctool as well. The only downside I see here is that xcpretty uses Ruby and maintaining Ruby (gem) dependencies is a PITA in long term. Is there any plan to user bundler to keep gemset the same across various local dev envs and CI? Karel On Wed, 26 Mar 2014 10:25:39 +0200 Christos Vasilakis wrote: > Hi everyone, > > During the last couple of days, as part of my AGIOS-181[1] work, got bumped > by problem issues of xctool[2] during builds both local and on travis. Let me > try to explain the two major issues faced: > > a) first the current release fails to run logic tests for an Xcode 5.1 > project, fixed in ?master' some hours ago[3] b) starting up the emulator to > run ?application' tests always failed on travis [4]. Not sure why, switching > to the build-in xcodebuild fixed the issue, so I guess its some issue with > xctool. (used to work prior). > > In a nutshell, xctool tries to mimic the behaviour of xcodebuild during > builds and understandable it can?t catch up with its future developments. > Major benefit of xctool is the nice formatting output during tests which > helps a lot to identify issues. The ideal would be a tool that relies on > xcodebuild (so it?s always up-to-date with apple development at the minute of > the release) and give a nice formatting output of the results. Fortunately > enough the flourish iOS OSS community stepped in and ?xcpretty? was > created[5]. It provides the same benefits of xctool (if better) but relies > on xcodebuild for its build for maximum compatibility. Already major projects > have adopted for their builds[6]. > > I think it?s sensible if we follow this path and adopt xcpretty for our > builds. > > Wdyt? > > Regards, > Christos > > > > [1] https://issues.jboss.org/browse/AGIOS-181 > [2] https://github.com/facebook/xctool > [3] https://github.com/facebook/xctool/issues/337 > [4] https://travis-ci.org/cvasilak/aerogear-ios-integration/builds/21524580 > [5] https://github.com/supermarin/xcpretty > [6] https://github.com/AFNetworking/AFNetworking/blob/master/Rakefile#L34 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From kpiwko at redhat.com Wed Mar 26 05:07:12 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 26 Mar 2014 10:07:12 +0100 Subject: [aerogear-dev] UnifiedPush Server deployment In-Reply-To: <1395821802966-7109.post@n5.nabble.com> References: <1395762037361-7086.post@n5.nabble.com> <20140325174509.23ab250a@kapy-ntb-x220> <1395821802966-7109.post@n5.nabble.com> Message-ID: <20140326100712.4c6e7537@kapy-ntb-x220> On Wed, 26 Mar 2014 01:16:42 -0700 (PDT) A577127 wrote: > Thanks for your answer but my problem was already solved thanks to Matthias. > :) :-) > > I use EAP 6.1.0 because JBoss' official page for JBoss AS gave me this > version. (see this link : http://www.jboss.org/jbossas > ) > Nice catch, I've reported this as a bug - https://issues.jboss.org/browse/ORG-1967. There should definitely be EAP 6.2.0 instead. > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Server-deployment-tp7086p7109.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From kpiwko at redhat.com Wed Mar 26 05:15:05 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 26 Mar 2014 10:15:05 +0100 Subject: [aerogear-dev] UPS UX updates In-Reply-To: <5331CDA5.1050405@redhat.com> References: <5331B750.1060609@redhat.com> <5331CDA5.1050405@redhat.com> Message-ID: <20140326101505.45800372@kapy-ntb-x220> Awesome! We would need to change our underlying UI tests heavily but I can live with that, as this is much nicer ;-) On Tue, 25 Mar 2014 18:40:37 +0000 Hylke Bons wrote: > > > Hello, > > https://github.com/hbons/aerogear-design/tree/master/ups-new-ux > The above link contains mockups with an updated look and feel. > > I've tried to consolodate the info that we had on different pages on > fewer pages, as a common critique was that the Application Details and > Variant Details pages looked alike too much, so I've merged them. > > On one page I've added a sidebar that reflects future features (it's > just for show). > > Other notable things are the orange info blocks where we want app > developers to take action on information (the device registration and > sending notifications in this case). I've deliberately made these stand > out a bit more as we want people to act on the information. Please note > that one row in the variants table shows up expanded in the mockups for > illustration purposes. The rows will all be collapsed on first view, so > it won't look as cluttered as you might think at first seeing the mockup. > > Let me know what you think and where we should go from here. > > Thanks, > > Hylke > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From kpiwko at redhat.com Wed Mar 26 05:28:29 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 26 Mar 2014 10:28:29 +0100 Subject: [aerogear-dev] UnifiedPush Server + MondoDB ideas/requirements Message-ID: <20140326102829.17b88985@kapy-ntb-x220> Hey, I'm trying to collect requirements for MongoDB usage in UPS. So far, I have following list in mind: 1/ Drop-in replacement for JPA (avoiding two WARs if possible) 2/ db integration on AS/WF/EAP (module) 3/ integration with OpenShift MongoDB gear Additional interesting stuff I can think of: * Enabled horizontal scaling for MongoDB instances * transaction model Mongo vs JPA * performance tests NoSQL vs SQL * security model Mongo vs JPA * combination of JPA + MongDB storages (JBoss Teiid) If you have any ideas/requirements, please drop them here. I'm planning to use your ideas to form a frame of a diploma thesis. Thanks, Karel From scm.blanc at gmail.com Wed Mar 26 05:44:56 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 26 Mar 2014 10:44:56 +0100 Subject: [aerogear-dev] UPS UX updates In-Reply-To: References: <5331B750.1060609@redhat.com> <5331CDA5.1050405@redhat.com> Message-ID: On Wed, Mar 26, 2014 at 9:30 AM, Matthias Wessendorf wrote: > As said before: overall they are really looking very great and modern! I > really like them. > > A few questions on some of the screens: > > * applications.png > List ("table") of all Push Applications: > - Is there no side bar for this? > > * application-details-blue.png > It's the details of one application, and has overview of all its variants. > - Is the plan to list all variants on their platform? Instead of having a > table? I do like that grouping! Just wondering :-) > I also like the grouping but when we will introduce paging, it will be paging per groups ? Not sure how UX friendly that will be. - When I click on a certain variant (e.g. the "Demo" variant of the iOS > section ), there is no separate page/view for its' details? Like its > installations ? I'd really prefer to have a page/view for all the details > of a certain variant. Also the code snippets for a variant is missing > I also like it this way, all the info needed can fit and not sure if we want to navigate to another page jsut for the details (For editing yes => other page). The Code Snippets : Yeah A button/link would be needed > > - Sidebar: is that specific to an application? See notes on > "applications.png" > - The "Notifications" on the sidebar, what's that? > - What's the "gear-wheel" for ? > > * "dialogs.png" > - For an application construct, that's good enough; Creating a variant is > a bit more complex (see current UI) > - Is there no side bar for this? > I assume that for delete app/variant or reset id/secrets we will use the same dialogs > > > * installations.png > - Is there no side bar for this? > - If I understand the view/page correctly, its a list of ALL installations > for one PushApplication. However, we should list the variants PER variant > (see current UI). The Navigation path on the bread-crumbs would be > "Applications >> Mobile HR >> Demo (iOS) >> Installations (number)" > +1 but I think that was also Hylke's initial idea because on the application details screen you see that the link to installations is on the "variant" level. I think it was just a glitch in his bread-crumbs. > > * loading.png > - yeah, that is totally missing today :-)) > > > > > Greetings, > Matthias > > > > On Tue, Mar 25, 2014 at 8:50 PM, Matthias Wessendorf wrote: > >> Awesome mock ups!! >> >> >> On Tuesday, March 25, 2014, Hylke Bons wrote: >> >>> >>> >>> Hello, >>> >>> https://github.com/hbons/aerogear-design/tree/master/ups-new-ux >>> The above link contains mockups with an updated look and feel. >>> >>> I've tried to consolodate the info that we had on different pages on >>> fewer pages, as a common critique was that the Application Details and >>> Variant Details pages looked alike too much, so I've merged them. >>> >>> On one page I've added a sidebar that reflects future features (it's >>> just for show). >>> >>> Other notable things are the orange info blocks where we want app >>> developers to take action on information (the device registration and >>> sending notifications in this case). I've deliberately made these stand >>> out a bit more as we want people to act on the information. Please note >>> that one row in the variants table shows up expanded in the mockups for >>> illustration purposes. The rows will all be collapsed on first view, so >>> it won't look as cluttered as you might think at first seeing the mockup. >>> >>> Let me know what you think and where we should go from here. >>> >>> Thanks, >>> >>> Hylke >>> >>> >>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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/20140326/58ccdb10/attachment.html From matzew at apache.org Wed Mar 26 06:14:33 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 11:14:33 +0100 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? In-Reply-To: References: Message-ID: On Tue, Mar 25, 2014 at 11:11 PM, Willy Martin Aguirre Rodriguez < marti1003 at hotmail.com> wrote: > > Idea for documentation: > Is it possible to use unifiedpush server work in tomcat or jetty? > nope, due to javaee dependencies > I don't have much experience about Redhat but about Tomcat or Jetty I > know, how to deploy a war. > maybe there is a equivalent maybe there is a equivalence between > applications servers. > it's all on the README of the UnifiedPush Server: https://github.com/aerogear/aerogear-unifiedpush-server/tree/0.10.1#getting-started-with-the-server 1) Database config 2) start server 3) deploy the WAR * it's that simple (when building the project from scratch: "mvn package jboss-as:deploy") * another way is to just copy the WAR file to the $JBOSS/standalone/deployments folder No need for screenshots on that > Try to add image for doc. screenshots of Jboss > > ------------------------------ > Date: Tue, 25 Mar 2014 17:08:10 +0100 > > From: matzew at apache.org > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation > improvements ? > > > > > On Tue, Mar 25, 2014 at 5:03 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > > maybe we can use http://jekyllrb.com/ > > > yeah - our actual website is already using that: > > https://github.com/aerogear/aerogear.org#building > > :-) > > > here you are an example http://docs.scala-lang.org/ > and source code https://github.com/scala/scala.github.com > > > ------------------------------ > Date: Tue, 25 Mar 2014 13:55:43 +0100 > From: matzew at apache.org > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation > improvements ? > > > > > > On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist wrote: > > did we discuss using the wiki, or was that for something else > > > not sure - wiki is nice, but a real guide/book is really something I > prefer for the "official" documentation. > > wiki could be: > setup up your XFVZ Database etc > > > > On Mar 25, 2014, at 5:11 AM, Corinne Krych wrote: > > > > > On 25 Mar 2014, at 08:55, Sebastien Blanc wrote: > > > >> +1 > >> We got already almost all the material in the current readme and we can > split that nicely into a howto and then rewriting maybe some parts. > >> > >> > >> > >> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf > wrote: > >> Hi, > >> > >> I feel a bit of the documentation might be misleading and not always > that great to go over. > >> > >> Instead of adding more and more the README, I think we should (w/in the > REPO) start to write a guide/book on HOWTO. > > > > +1 to add the doc in the relevant repo > > We could alway inlude part of the ascidoc text in aerogear web site with > the same mechanism as shown in this PR: > > https://github.com/aerogear/aerogear.org/pull/275 > > > > > >> > >> Regarding the actual format, I think asciidoc comes to mind; > >> > >> > >> 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 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140326/b694f14e/attachment-0001.html From matzew at apache.org Wed Mar 26 06:15:42 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 11:15:42 +0100 Subject: [aerogear-dev] UnifiedPush Server + MondoDB ideas/requirements In-Reply-To: <20140326102829.17b88985@kapy-ntb-x220> References: <20140326102829.17b88985@kapy-ntb-x220> Message-ID: On Wed, Mar 26, 2014 at 10:28 AM, Karel Piwko wrote: > Hey, > > I'm trying to collect requirements for MongoDB usage in UPS. So far, I have > following list in mind: > > 1/ Drop-in replacement for JPA (avoiding two WARs if possible) > yeah, that would be best :-) > 2/ db integration on AS/WF/EAP (module) > 3/ integration with OpenShift MongoDB gear > +1 > > Additional interesting stuff I can think of: > > * Enabled horizontal scaling for MongoDB instances > * transaction model Mongo vs JPA > * performance tests NoSQL vs SQL > * security model Mongo vs JPA > * combination of JPA + MongDB storages (JBoss Teiid) > +1 sounds pretty reasonable > > If you have any ideas/requirements, please drop them here. I'm planning to > use > your ideas to form a frame of a diploma thesis. > That's awesome! > > Thanks, > > Karel > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140326/1453905d/attachment.html From cvasilak at gmail.com Wed Mar 26 06:58:52 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Wed, 26 Mar 2014 12:58:52 +0200 Subject: [aerogear-dev] xctool and xcpretty In-Reply-To: <20140326100314.0ff19676@kapy-ntb-x220> References: <48FEF34A-6AF7-4453-8981-2A3C03486BA9@gmail.com> <20140326100314.0ff19676@kapy-ntb-x220> Message-ID: <874F9158-5560-4183-AF9D-E3F95148DB1C@gmail.com> Hi Karel, answers inline On Mar 26, 2014, at 11:03 AM, Karel Piwko wrote: > Anything that helps stability of iOS testing env will get automatic +1 for > me. We fee the pain of xctool as well. nice to hear :) > > The only downside I see here is that xcpretty uses Ruby and maintaining Ruby > (gem) dependencies is a PITA in long term. Is there any plan to user bundler to > keep gemset the same across various local dev envs and CI? not at the moment, plan was to edit .travis.yml with something like this[1] but we can certainly look at if it eases the pain. You feel adding ?-v? on the 'gem install step' on .travis.yml will help a bit to circumvent the gem versioning issue, or going through full use of bundler is the way to go? Thinking if it is too much for an iOS project but can be wrong though. Regards, Christos [1] https://github.com/cvasilak/aerogear-ios/blob/0758ed6260300eb977c9c69c78b1e4d280da3a95/.travis.yml > > Karel > > On Wed, 26 Mar 2014 10:25:39 +0200 > Christos Vasilakis wrote: > >> Hi everyone, >> >> During the last couple of days, as part of my AGIOS-181[1] work, got bumped >> by problem issues of xctool[2] during builds both local and on travis. Let me >> try to explain the two major issues faced: >> >> a) first the current release fails to run logic tests for an Xcode 5.1 >> project, fixed in ?master' some hours ago[3] b) starting up the emulator to >> run ?application' tests always failed on travis [4]. Not sure why, switching >> to the build-in xcodebuild fixed the issue, so I guess its some issue with >> xctool. (used to work prior). >> >> In a nutshell, xctool tries to mimic the behaviour of xcodebuild during >> builds and understandable it can?t catch up with its future developments. >> Major benefit of xctool is the nice formatting output during tests which >> helps a lot to identify issues. The ideal would be a tool that relies on >> xcodebuild (so it?s always up-to-date with apple development at the minute of >> the release) and give a nice formatting output of the results. Fortunately >> enough the flourish iOS OSS community stepped in and ?xcpretty? was >> created[5]. It provides the same benefits of xctool (if better) but relies >> on xcodebuild for its build for maximum compatibility. Already major projects >> have adopted for their builds[6]. >> >> I think it?s sensible if we follow this path and adopt xcpretty for our >> builds. >> >> Wdyt? >> >> Regards, >> Christos >> >> >> >> [1] https://issues.jboss.org/browse/AGIOS-181 >> [2] https://github.com/facebook/xctool >> [3] https://github.com/facebook/xctool/issues/337 >> [4] https://travis-ci.org/cvasilak/aerogear-ios-integration/builds/21524580 >> [5] https://github.com/supermarin/xcpretty >> [6] https://github.com/AFNetworking/AFNetworking/blob/master/Rakefile#L34 >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 Mar 26 07:26:39 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 12:26:39 +0100 Subject: [aerogear-dev] [UnifiedPush Server] Documentation improvements ? In-Reply-To: References: Message-ID: Created a JIRA to track the work: https://issues.jboss.org/browse/AGPUSH-571 On Wed, Mar 26, 2014 at 11:14 AM, Matthias Wessendorf wrote: > > > > On Tue, Mar 25, 2014 at 11:11 PM, Willy Martin Aguirre Rodriguez < > marti1003 at hotmail.com> wrote: > >> >> Idea for documentation: >> Is it possible to use unifiedpush server work in tomcat or jetty? >> > > nope, due to javaee dependencies > > >> I don't have much experience about Redhat but about Tomcat or Jetty I >> know, how to deploy a war. >> maybe there is a equivalent maybe there is a equivalence between >> applications servers. >> > > it's all on the README of the UnifiedPush Server: > > https://github.com/aerogear/aerogear-unifiedpush-server/tree/0.10.1#getting-started-with-the-server > > 1) Database config > 2) start server > 3) deploy the WAR > * it's that simple (when building the project from scratch: "mvn package > jboss-as:deploy") > * another way is to just copy the WAR file to the > $JBOSS/standalone/deployments folder > > No need for screenshots on that > > > >> Try to add image for doc. screenshots of Jboss >> >> ------------------------------ >> Date: Tue, 25 Mar 2014 17:08:10 +0100 >> >> From: matzew at apache.org >> To: aerogear-dev at lists.jboss.org >> Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation >> improvements ? >> >> >> >> >> On Tue, Mar 25, 2014 at 5:03 PM, Willy Martin Aguirre Rodriguez < >> marti1003 at hotmail.com> wrote: >> >> maybe we can use http://jekyllrb.com/ >> >> >> yeah - our actual website is already using that: >> >> https://github.com/aerogear/aerogear.org#building >> >> :-) >> >> >> here you are an example http://docs.scala-lang.org/ >> and source code https://github.com/scala/scala.github.com >> >> >> ------------------------------ >> Date: Tue, 25 Mar 2014 13:55:43 +0100 >> From: matzew at apache.org >> To: aerogear-dev at lists.jboss.org >> Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation >> improvements ? >> >> >> >> >> >> On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist wrote: >> >> did we discuss using the wiki, or was that for something else >> >> >> not sure - wiki is nice, but a real guide/book is really something I >> prefer for the "official" documentation. >> >> wiki could be: >> setup up your XFVZ Database etc >> >> >> >> On Mar 25, 2014, at 5:11 AM, Corinne Krych >> wrote: >> >> > >> > On 25 Mar 2014, at 08:55, Sebastien Blanc wrote: >> > >> >> +1 >> >> We got already almost all the material in the current readme and we >> can split that nicely into a howto and then rewriting maybe some parts. >> >> >> >> >> >> >> >> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf < >> matzew at apache.org> wrote: >> >> Hi, >> >> >> >> I feel a bit of the documentation might be misleading and not always >> that great to go over. >> >> >> >> Instead of adding more and more the README, I think we should (w/in >> the REPO) start to write a guide/book on HOWTO. >> > >> > +1 to add the doc in the relevant repo >> > We could alway inlude part of the ascidoc text in aerogear web site >> with the same mechanism as shown in this PR: >> > https://github.com/aerogear/aerogear.org/pull/275 >> > >> > >> >> >> >> Regarding the actual format, I think asciidoc comes to mind; >> >> >> >> >> >> 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 >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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 > -- 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/20140326/0b9bf2a9/attachment-0001.html From bsutter at redhat.com Wed Mar 26 07:39:04 2014 From: bsutter at redhat.com (Burr Sutter) Date: Wed, 26 Mar 2014 07:39:04 -0400 Subject: [aerogear-dev] UnifiedPush Server + MondoDB ideas/requirements In-Reply-To: References: <20140326102829.17b88985@kapy-ntb-x220> Message-ID: On Mar 26, 2014, at 6:15 AM, Matthias Wessendorf wrote: > > > > On Wed, Mar 26, 2014 at 10:28 AM, Karel Piwko wrote: > Hey, > > I'm trying to collect requirements for MongoDB usage in UPS. So far, I have > following list in mind: > > 1/ Drop-in replacement for JPA (avoiding two WARs if possible) > > yeah, that would be best :-) +1 > > 2/ db integration on AS/WF/EAP (module) What are you thinking about from a JBoss module perspective? > 3/ integration with OpenShift MongoDB gear > > +1 +1 > > > Additional interesting stuff I can think of: > > * Enabled horizontal scaling for MongoDB instances > * transaction model Mongo vs JPA > * performance tests NoSQL vs SQL > * security model Mongo vs JPA > * combination of JPA + MongDB storages (JBoss Teiid) > > +1 sounds pretty reasonable For me, +1 to hortizontal scaling, transactions, performance, security but -1 for Teiid as a "data store" for our push registrations. There are other uses for Teiid but introducing a dependency here will be costly with little possible return on that investment. With that said, I do forsee some enterprise integration use cases that could involve Teiid but that would still be secondary to Camel and showing off things like jBPM (notifications of new tasks in the workflows). > > > If you have any ideas/requirements, please drop them here. I'm planning to use > your ideas to form a frame of a diploma thesis. > > That's awesome! > > > Thanks, > > Karel > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140326/64847946/attachment.html From matzew at apache.org Wed Mar 26 07:43:17 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 12:43:17 +0100 Subject: [aerogear-dev] UnifiedPush Server + MondoDB ideas/requirements In-Reply-To: References: <20140326102829.17b88985@kapy-ntb-x220> Message-ID: On Wed, Mar 26, 2014 at 12:39 PM, Burr Sutter wrote: > > On Mar 26, 2014, at 6:15 AM, Matthias Wessendorf > wrote: > > > > > On Wed, Mar 26, 2014 at 10:28 AM, Karel Piwko wrote: > >> Hey, >> >> I'm trying to collect requirements for MongoDB usage in UPS. So far, I >> have >> following list in mind: >> >> 1/ Drop-in replacement for JPA (avoiding two WARs if possible) >> > > yeah, that would be best :-) > > +1 > > > >> 2/ db integration on AS/WF/EAP (module) >> > What are you thinking about from a JBoss module perspective? > > 3/ integration with OpenShift MongoDB gear >> > > +1 > > +1 > > > >> >> Additional interesting stuff I can think of: >> >> * Enabled horizontal scaling for MongoDB instances >> * transaction model Mongo vs JPA >> * performance tests NoSQL vs SQL >> * security model Mongo vs JPA >> * combination of JPA + MongDB storages (JBoss Teiid) >> > > +1 sounds pretty reasonable > > For me, +1 to hortizontal scaling, transactions, performance, security > yeah > but -1 for Teiid as a "data store" for our push registrations. > > There are other uses for Teiid but introducing a dependency here will be > costly with little possible return on that investment. > agree! Let's keep Teiid out, for now > > With that said, I do forsee some enterprise integration use cases that > could involve Teiid but that would still be secondary to Camel and showing > off things like jBPM (notifications of new tasks in the workflows). > if requested later - could be done later > > > > >> >> If you have any ideas/requirements, please drop them here. I'm planning >> to use >> your ideas to form a frame of a diploma thesis. >> > > That's awesome! > > >> >> Thanks, >> >> Karel >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140326/2528d9cb/attachment.html From kpiwko at redhat.com Wed Mar 26 08:08:14 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 26 Mar 2014 13:08:14 +0100 Subject: [aerogear-dev] UnifiedPush Server + MondoDB ideas/requirements In-Reply-To: References: <20140326102829.17b88985@kapy-ntb-x220> Message-ID: <20140326130814.09aff6c7@kapy-ntb-x220> On Wed, 26 Mar 2014 07:39:04 -0400 Burr Sutter wrote: > > On Mar 26, 2014, at 6:15 AM, Matthias Wessendorf wrote: > > > > > > > > > On Wed, Mar 26, 2014 at 10:28 AM, Karel Piwko wrote: > > Hey, > > > > I'm trying to collect requirements for MongoDB usage in UPS. So far, I have > > following list in mind: > > > > 1/ Drop-in replacement for JPA (avoiding two WARs if possible) > > > > yeah, that would be best :-) > +1 > > > > 2/ db integration on AS/WF/EAP (module) > What are you thinking about from a JBoss module perspective? Google shows for instance: * https://issues.jboss.org/browse/WFLY-3139 * https://issues.jboss.org/browse/JBERET-48 * https://github.com/goldmann/wildfly-modules/tree/master/mongodb I understand it as MongoDB module will be provided (at least in WF) in the future to make usage of MongoDB from Java EE apps easier. UPS would profit from such setup, especially if we are able to make NoSQL a drop-in replacement for JPA. It would not matter whether you want MySQL or MongoDB as persistence storage, you'll just execute different cli script. > > > 3/ integration with OpenShift MongoDB gear > > > > +1 > +1 > > > > > > Additional interesting stuff I can think of: > > > > * Enabled horizontal scaling for MongoDB instances > > * transaction model Mongo vs JPA > > * performance tests NoSQL vs SQL > > * security model Mongo vs JPA > > * combination of JPA + MongDB storages (JBoss Teiid) > > > > +1 sounds pretty reasonable > For me, +1 to hortizontal scaling, transactions, performance, security > but -1 for Teiid as a "data store" for our push registrations. > > There are other uses for Teiid but introducing a dependency here will be > costly with little possible return on that investment. > > With that said, I do forsee some enterprise integration use cases that could > involve Teiid but that would still be secondary to Camel and showing off > things like jBPM (notifications of new tasks in the workflows). > Makes sense. > > > > > > > If you have any ideas/requirements, please drop them here. I'm planning to > > use your ideas to form a frame of a diploma thesis. > > > > That's awesome! > > > > > > Thanks, > > > > Karel > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.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 kpiwko at redhat.com Wed Mar 26 08:13:34 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 26 Mar 2014 13:13:34 +0100 Subject: [aerogear-dev] xctool and xcpretty In-Reply-To: <874F9158-5560-4183-AF9D-E3F95148DB1C@gmail.com> References: <48FEF34A-6AF7-4453-8981-2A3C03486BA9@gmail.com> <20140326100314.0ff19676@kapy-ntb-x220> <874F9158-5560-4183-AF9D-E3F95148DB1C@gmail.com> Message-ID: <20140326131334.27c7739f@kapy-ntb-x220> On Wed, 26 Mar 2014 12:58:52 +0200 Christos Vasilakis wrote: > Hi Karel, > > answers inline > > On Mar 26, 2014, at 11:03 AM, Karel Piwko wrote: > > > Anything that helps stability of iOS testing env will get automatic +1 for > > me. We fee the pain of xctool as well. > > nice to hear :) > > > > > The only downside I see here is that xcpretty uses Ruby and maintaining Ruby > > (gem) dependencies is a PITA in long term. Is there any plan to user > > bundler to keep gemset the same across various local dev envs and CI? > > not at the moment, plan was to edit .travis.yml with something like this[1] > but we can certainly look at if it eases the pain. You feel adding ?-v? on > the 'gem install step' on .travis.yml will help a bit to circumvent the gem > versioning issue, or going through full use of bundler is the way to go? > Thinking if it is too much for an iOS project but can be wrong though. You're right, -v for both cocoapods and xcpretty should be enough at this moment, bundler is too heavyweight for just 2 dependencies. > > Regards, > Christos > > [1] > https://github.com/cvasilak/aerogear-ios/blob/0758ed6260300eb977c9c69c78b1e4d280da3a95/.travis.yml > > > > > Karel > > > > On Wed, 26 Mar 2014 10:25:39 +0200 > > Christos Vasilakis wrote: > > > >> Hi everyone, > >> > >> During the last couple of days, as part of my AGIOS-181[1] work, got bumped > >> by problem issues of xctool[2] during builds both local and on travis. Let > >> me try to explain the two major issues faced: > >> > >> a) first the current release fails to run logic tests for an Xcode 5.1 > >> project, fixed in ?master' some hours ago[3] b) starting up the emulator to > >> run ?application' tests always failed on travis [4]. Not sure why, > >> switching to the build-in xcodebuild fixed the issue, so I guess its some > >> issue with xctool. (used to work prior). > >> > >> In a nutshell, xctool tries to mimic the behaviour of xcodebuild during > >> builds and understandable it can?t catch up with its future developments. > >> Major benefit of xctool is the nice formatting output during tests which > >> helps a lot to identify issues. The ideal would be a tool that relies on > >> xcodebuild (so it?s always up-to-date with apple development at the minute > >> of the release) and give a nice formatting output of the results. > >> Fortunately enough the flourish iOS OSS community stepped in and > >> ?xcpretty? was created[5]. It provides the same benefits of xctool (if > >> better) but relies on xcodebuild for its build for maximum compatibility. > >> Already major projects have adopted for their builds[6]. > >> > >> I think it?s sensible if we follow this path and adopt xcpretty for our > >> builds. > >> > >> Wdyt? > >> > >> Regards, > >> Christos > >> > >> > >> > >> [1] https://issues.jboss.org/browse/AGIOS-181 > >> [2] https://github.com/facebook/xctool > >> [3] https://github.com/facebook/xctool/issues/337 > >> [4] https://travis-ci.org/cvasilak/aerogear-ios-integration/builds/21524580 > >> [5] https://github.com/supermarin/xcpretty > >> [6] https://github.com/AFNetworking/AFNetworking/blob/master/Rakefile#L34 > >> > >> > >> _______________________________________________ > >> aerogear-dev mailing list > >> aerogear-dev at lists.jboss.org > >> https://lists.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 Wed Mar 26 08:37:20 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 26 Mar 2014 13:37:20 +0100 Subject: [aerogear-dev] QE testing tools landed in GH repository Message-ID: <20140326133720.73488147@kapy-ntb-x220> Hi, QE tools landed into https://github.com/aerogear/aerogear-testing-tools. There are following tools so far: * ups-cart-cli - executable to create AG UPS OSO/OSE [1] cartridge from github repository/branch and/or create some sample data on UPS (we use it for manual test, performance tests, migration tests, etc.) * arquillian-rule - support for JUnit rule with Arquillian injection (we use it for UPS data sampling in tests) * arquillian-smart-url - support for replacing http -> https in Arquillian injections and similar test related stuff (we use it to test https scenarios) * arquillian-non-deploying-openshift-container - support for testing UPS OSE cartridge by pretending that Arquillian deployed an application to OSE (we use it to test UPS on OpenShift) I hope that at least first one will be useful outside of QE automation. I plan to release tools to Maven Central/Bintray where appropriate. As always, any suggestions welcomed. Karel [1] AeroGear UnifiedPush Server on OpenShift Online/OpenShift Enterprise. Abbreviation abuse ftw! :-) From antoine.matyja at worldline.com Wed Mar 26 10:06:09 2014 From: antoine.matyja at worldline.com (A577127) Date: Wed, 26 Mar 2014 07:06:09 -0700 (PDT) Subject: [aerogear-dev] REST Installation Registration - Authentication problem Message-ID: <1395842769113-7128.post@n5.nabble.com> Hey, I have an AeroGear UnifiedPush Server running on Windows 7. I registered my application and got the Application ID and Master secret. I added a variant for my Android app. Now I want to register the installation for my app on my device. I want to do this without having to change my application, so instead of using AeroGear SDK for Android, I want to register my app's token "manually" with the REST API provided by AeroGear. I read this tutorial (#Installation Registration) : http://aerogear.org/docs/specs/aerogear-server-push/ Since I can't use curl on windows, I'm using "Postman", a chrome plugin to send custom HTTP requests. I had a few problems : - The URL https://SERVER:PORT/context/rest/registry/device doesn't respond to HTTPS. It does with HTTP. (same for all other rest urls) - I "translated" the curl command to POST parameters, but when I send it I get an authentication request, even though I already set the App ID and master secret in the header, in "Authorization" (I searched a little about it, the value is "AppID:MasterSecret" base64 encoded) I tryed to use the username/password from my AG UnifiedPush server, it didn't work, same for App ID/Master secret. After cancelling I get "Unauthorized Request" of course. Here's a screenshot of the HTTP POST request configuration : And the form I get when I send it : Thanks in advance, -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/REST-Installation-Registration-Authentication-problem-tp7128.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Wed Mar 26 10:18:48 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 15:18:48 +0100 Subject: [aerogear-dev] REST Installation Registration - Authentication problem In-Reply-To: <1395842769113-7128.post@n5.nabble.com> References: <1395842769113-7128.post@n5.nabble.com> Message-ID: On Wed, Mar 26, 2014 at 3:06 PM, A577127 wrote: > Hey, > > I have an AeroGear UnifiedPush Server running on Windows 7. I registered my > application and got the Application ID and Master secret. I added a variant > for my Android app. > > Now I want to register the installation for my app on my device. I want to > do this without having to change my application, so instead of using > AeroGear SDK for Android, I want to register my app's token "manually" with > the REST API provided by AeroGear. > > I read this tutorial (#Installation Registration) : > http://aerogear.org/docs/specs/aerogear-server-push/ > > > Since I can't use curl on windows, I'm using "Postman", a chrome plugin to > send custom HTTP requests. I had a few problems : > > - The URL https://SERVER:PORT/context/rest/registry/device doesn't respond > to HTTPS. It does with HTTP. (same for all other rest urls) > > - I "translated" the curl command to POST parameters, but when I send it I > get an authentication request, even though I already set the App ID and > master secret in the header, in "Authorization" (I searched a little about > it, the value is "AppID:MasterSecret" base64 encoded) > here, you need the variantID and the variantSecret (not the AppID:MasterSecret) -M > I tryed to use the username/password from my AG UnifiedPush server, it > didn't work, same for App ID/Master secret. After cancelling I get > "Unauthorized Request" of course. > > Here's a screenshot of the HTTP POST request configuration : > > And the form I get when I send it : > > > Thanks in advance, > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/REST-Installation-Registration-Authentication-problem-tp7128.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140326/457ac8fc/attachment.html From antoine.matyja at worldline.com Wed Mar 26 11:22:19 2014 From: antoine.matyja at worldline.com (A577127) Date: Wed, 26 Mar 2014 08:22:19 -0700 (PDT) Subject: [aerogear-dev] REST Installation Registration - Authentication problem In-Reply-To: <1395842769113-7128.post@n5.nabble.com> References: <1395842769113-7128.post@n5.nabble.com> Message-ID: <1395847339115-7130.post@n5.nabble.com> Thanks again for the quick answer, now I'm more familiar with variants :) So I managed to register my app and got and ID in the HTTP answer : Now I would like to send a push notification to my device. I'm sending another POST request (as stated in the tutorial) with this time the app ID/master secret for authorization. I get a HTTP 200 code with "Job submitted", but nothing happens on my device (note that I receive push notifications from my custom java server so the device isn't the problem). I also get this in my JBoss console : Everything seems ok... By the way, I must use a proxy server to browse the internet but didn't find any settings on the JBoss server to set it. Thanks for help -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/REST-Installation-Registration-Authentication-problem-tp7128p7130.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Wed Mar 26 11:41:07 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 16:41:07 +0100 Subject: [aerogear-dev] REST Installation Registration - Authentication problem In-Reply-To: <1395847339115-7130.post@n5.nabble.com> References: <1395842769113-7128.post@n5.nabble.com> <1395847339115-7130.post@n5.nabble.com> Message-ID: On Wed, Mar 26, 2014 at 4:22 PM, A577127 wrote: > Thanks again for the quick answer, now I'm more familiar with variants :) > > So I managed to register my app and got and ID in the HTTP answer : > > > > Now I would like to send a push notification to my device. I'm sending > another POST request (as stated in the tutorial) with this time the app > ID/master secret for authorization. > yes - or the new "Compose a push" UI (assuming you are using 0.10.1) There is a link on the "PushApplication" details page > > > > I get a HTTP 200 code with "Job submitted", but nothing happens on my > device > (note that I receive push notifications from my custom java server so the > device isn't the problem). that just means the server got the request - that does not actually mean it was really going from UPS -> Google -> device; There are no SLAs on that (Google/Apple do NOT guarantee delivery) > I also get this in my JBoss console : > > > > Everything seems ok... > > By the way, I must use a proxy server to browse the internet but didn't > find > any settings on the JBoss server to set it. > Ok, we do not yet have support for proxy server, on the UPS. It's tracked on a JIRA: https://issues.jboss.org/browse/AGPUSH-306 One thing you could try - is getting a free account on OpenShift: https://www.openshift.com/ > > Thanks for help > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/REST-Installation-Registration-Authentication-problem-tp7128p7130.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140326/aaf3d305/attachment.html From antoine.matyja at worldline.com Wed Mar 26 11:50:05 2014 From: antoine.matyja at worldline.com (A577127) Date: Wed, 26 Mar 2014 08:50:05 -0700 (PDT) Subject: [aerogear-dev] REST Installation Registration - Authentication problem In-Reply-To: References: <1395842769113-7128.post@n5.nabble.com> <1395847339115-7130.post@n5.nabble.com> Message-ID: <1395849005757-7132.post@n5.nabble.com> Ok, I will try Openshift until I find a better solution :( Thanks. -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/REST-Installation-Registration-Authentication-problem-tp7128p7132.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Wed Mar 26 11:53:29 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 16:53:29 +0100 Subject: [aerogear-dev] REST Installation Registration - Authentication problem In-Reply-To: <1395849005757-7132.post@n5.nabble.com> References: <1395842769113-7128.post@n5.nabble.com> <1395847339115-7130.post@n5.nabble.com> <1395849005757-7132.post@n5.nabble.com> Message-ID: On Wed, Mar 26, 2014 at 4:50 PM, A577127 wrote: > Ok, I will try Openshift until I find a better solution :( Thanks. > I think it's not too hard to add proxy support, see Sebastien's comments on: https://issues.jboss.org/browse/AGPUSH-306 If you are willing to help here, working on proxy support, that would be awesome. Greetings, Matthias > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/REST-Installation-Registration-Authentication-problem-tp7128p7132.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140326/8ae57815/attachment-0001.html From scm.blanc at gmail.com Wed Mar 26 12:08:49 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 26 Mar 2014 17:08:49 +0100 Subject: [aerogear-dev] REST Installation Registration - Authentication problem In-Reply-To: References: <1395842769113-7128.post@n5.nabble.com> <1395847339115-7130.post@n5.nabble.com> <1395849005757-7132.post@n5.nabble.com> Message-ID: On Wed, Mar 26, 2014 at 4:53 PM, Matthias Wessendorf wrote: > > > > On Wed, Mar 26, 2014 at 4:50 PM, A577127 wrote: > >> Ok, I will try Openshift until I find a better solution :( Thanks. >> > > I think it's not too hard to add proxy support, see Sebastien's comments > on: > https://issues.jboss.org/browse/AGPUSH-306 > > If you are willing to help here, working on proxy support, that would be > awesome. > +1 ! And you probably already have done some work around this since you have it working on your custom Java Server. > > Greetings, > Matthias > > > >> >> >> >> -- >> View this message in context: >> http://aerogear-dev.1069024.n5.nabble.com/REST-Installation-Registration-Authentication-problem-tp7128p7132.html >> Sent from the aerogear-dev mailing list archive at Nabble.com. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > 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/20140326/ccb64ca4/attachment.html From kpiwko at redhat.com Wed Mar 26 12:16:47 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Wed, 26 Mar 2014 17:16:47 +0100 Subject: [aerogear-dev] REST Installation Registration - Authentication problem In-Reply-To: <1395842769113-7128.post@n5.nabble.com> References: <1395842769113-7128.post@n5.nabble.com> Message-ID: <20140326171647.438dcbe2@kapy-ntb-x220> On Wed, 26 Mar 2014 07:06:09 -0700 (PDT) A577127 wrote: > Hey, > > I have an AeroGear UnifiedPush Server running on Windows 7. I registered my > application and got the Application ID and Master secret. I added a variant > for my Android app. > > Now I want to register the installation for my app on my device. I want to > do this without having to change my application, so instead of using > AeroGear SDK for Android, I want to register my app's token "manually" with > the REST API provided by AeroGear. > > I read this tutorial (#Installation Registration) : > http://aerogear.org/docs/specs/aerogear-server-push/ > > > Since I can't use curl on windows, I'm using "Postman", a chrome plugin to > send custom HTTP requests. I had a few problems : > > - The URL https://SERVER:PORT/context/rest/registry/device doesn't respond > to HTTPS. It does with HTTP. (same for all other rest urls) You have to enable https connector on the server. You need to: 1/ have a keystore/truststore with certificate (either real cert or you can create one on your own (you can actually use the one in integration-tests ) 2/ you need to enable https on the server - here is how we do that using jboss cli - https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/master/setup/enable_https.cli 3/ beware, by default https uses port 8443 instead of 8080 4/ if you are using own certificate, likely you'd need to alter Postman configuration somehow (no experience here). We are using RESTAssured instead of curl and it works fine. > > - I "translated" the curl command to POST parameters, but when I send it I > get an authentication request, even though I already set the App ID and > master secret in the header, in "Authorization" (I searched a little about > it, the value is "AppID:MasterSecret" base64 encoded) > I tryed to use the username/password from my AG UnifiedPush server, it > didn't work, same for App ID/Master secret. After cancelling I get > "Unauthorized Request" of course. > > Here's a screenshot of the HTTP POST request configuration : > > And the form I get when I send it : > > > Thanks in advance, > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/REST-Installation-Registration-Authentication-problem-tp7128.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From smikloso at redhat.com Wed Mar 26 13:27:20 2014 From: smikloso at redhat.com (Stefan Miklosovic) Date: Wed, 26 Mar 2014 13:27:20 -0400 (EDT) Subject: [aerogear-dev] UnifiedPush 0.10.2 - release coming soon (WAR and OpenShift) In-Reply-To: References: Message-ID: <1961848058.3276961.1395854840567.JavaMail.zimbra@redhat.com> Hi Matthias, we tried 0.10.2 integration tests and all is green - built war from GH dynamically against latest 0.10.2 commit and your staged 0.10.2 war as well. We try to focus on testing of 0.11 stream now. I tried to create that app on Openshift as described and it behaves ok as well. Regards Stefan Miklosovic Red Hat Brno - JBoss Mobile Platform e-mail: smikloso at redhat.com irc: smikloso ----- Original Message ----- > Hi, > in order to be consistent with the DS name changes on master, we did apply > them to the 0.10.x branch as well. That's the only content of the release: > updated DS name changes. > I have uploaded the WAR file to my _private_ staging repository: > http://people.apache.org/~matzew/aerogear-staging/ > Also, I have applied the updated WAR file (including the DB configuration > change) to the OpenShift cartridge. See: > https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/11 > If you want to test it - it's simple! Just go ahead and use my fork of the > repo: > rhc app create --no-git > https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-push > mysql-5.1 > Let me know the results of your testing; > If I hear nothing bad by Thursday evening, the merges will happen on Friday > Greetings, > 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/20140326/f76bb662/attachment.html From matzew at apache.org Wed Mar 26 13:43:24 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 18:43:24 +0100 Subject: [aerogear-dev] UnifiedPush 0.10.2 - release coming soon (WAR and OpenShift) In-Reply-To: <1961848058.3276961.1395854840567.JavaMail.zimbra@redhat.com> References: <1961848058.3276961.1395854840567.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Mar 26, 2014 at 6:27 PM, Stefan Miklosovic wrote: > Hi Matthias, > > > we tried 0.10.2 integration tests and all is green - built war from GH > dynamically against latest 0.10.2 commit and your staged 0.10.2 war as well. > awesome! > > We try to focus on testing of 0.11 stream now. > well - please don't :-) once this one is merged: it all changes: https://github.com/aerogear/aerogear-unifiedpush-server/pull/145 there is NO release of 0.11 for a couple of week... due to these JIRAs: https://issues.jboss.org/browse/AGPUSH-568 > > I tried to create that app on Openshift as described and it behaves ok as > well. > > > Regards > > Stefan Miklosovic > Red Hat Brno - JBoss Mobile Platform > > e-mail: smikloso at redhat.com > irc: smikloso > > ------------------------------ > > Hi, > > in order to be consistent with the DS name changes on master, we did apply > them to the 0.10.x branch as well. That's the only content of the release: > updated DS name changes. > > I have uploaded the WAR file to my _private_ staging repository: > http://people.apache.org/~matzew/aerogear-staging/ > > > Also, I have applied the updated WAR file (including the DB configuration > change) to the OpenShift cartridge. See: > > https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/11 > > > If you want to test it - it's simple! Just go ahead and use my fork of the > repo: > > rhc app create --no-git > https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.1 > > > Let me know the results of your testing; > If I hear nothing bad by Thursday evening, the merges will happen on Friday > > Greetings, > 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/20140326/a332fb47/attachment.html From vmfamaral at gmail.com Wed Mar 26 15:01:53 2014 From: vmfamaral at gmail.com (oxsav) Date: Wed, 26 Mar 2014 12:01:53 -0700 (PDT) Subject: [aerogear-dev] Unified Push Java client In-Reply-To: References: <1395762391924-7087.post@n5.nabble.com> <1395765421843-7095.post@n5.nabble.com> <1395768323676-7099.post@n5.nabble.com> <1395768484331-7100.post@n5.nabble.com> Message-ID: <1395860513726-7138.post@n5.nabble.com> Sorry for the delay. My mistake. I was only running this as a gradle build and not as a "java application" I think that was the problem. So the problem is now solved ;) Thanks, -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087p7138.html Sent from the aerogear-dev mailing list archive at Nabble.com. From scm.blanc at gmail.com Wed Mar 26 15:11:49 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Wed, 26 Mar 2014 20:11:49 +0100 Subject: [aerogear-dev] Unified Push Java client In-Reply-To: <1395860513726-7138.post@n5.nabble.com> References: <1395762391924-7087.post@n5.nabble.com> <1395765421843-7095.post@n5.nabble.com> <1395768323676-7099.post@n5.nabble.com> <1395768484331-7100.post@n5.nabble.com> <1395860513726-7138.post@n5.nabble.com> Message-ID: Cool ! Please keep us informed about your Vertx mod project which seems really interesting :) Seb On Wed, Mar 26, 2014 at 8:01 PM, oxsav wrote: > Sorry for the delay. My mistake. > > I was only running this as a gradle build and not as a "java application" I > think that was the problem. So the problem is now solved ;) > > Thanks, > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087p7138.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140326/2471f3d6/attachment.html From matzew at apache.org Wed Mar 26 16:05:55 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Mar 2014 21:05:55 +0100 Subject: [aerogear-dev] Unified Push Java client In-Reply-To: References: <1395762391924-7087.post@n5.nabble.com> <1395765421843-7095.post@n5.nabble.com> <1395768323676-7099.post@n5.nabble.com> <1395768484331-7100.post@n5.nabble.com> <1395860513726-7138.post@n5.nabble.com> Message-ID: On Wed, Mar 26, 2014 at 8:11 PM, Sebastien Blanc wrote: > Cool ! > Please keep us informed about your Vertx mod project which seems really > interesting :) > yes - contributions are always welcome! > Seb > > > On Wed, Mar 26, 2014 at 8:01 PM, oxsav wrote: > >> Sorry for the delay. My mistake. >> >> I was only running this as a gradle build and not as a "java application" >> I >> think that was the problem. So the problem is now solved ;) >> >> Thanks, >> >> >> >> -- >> View this message in context: >> http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Java-client-tp7087p7138.html >> Sent from the aerogear-dev mailing list archive at Nabble.com. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140326/8bd79a07/attachment.html From matzew at apache.org Thu Mar 27 07:07:58 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 27 Mar 2014 12:07:58 +0100 Subject: [aerogear-dev] [UnifiedPush] Version 0.10.2 got release Message-ID: Hi, as of today a new version of the UPS is available. It's almost exactly the same as the 0.10.1 version, besides a minor change, done by Bruno: https://issues.jboss.org/browse/AGPUSH-572 It's available on our website (aerogear.org/push and openshift). Enjoy! -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/20140327/d21f6094/attachment.html From marti1003 at hotmail.com Thu Mar 27 08:52:35 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Thu, 27 Mar 2014 07:52:35 -0500 Subject: [aerogear-dev] unifiedpush server with mysql Message-ID: I am trying to run unifiedpush server with mysql but I have some problem with datasource https://github.com/aerogear/aerogear-unifiedpush-server#mysql-database-configuration I get errors when I try to run /Path/to/JBossAS/bin/jboss-cli.sh --file=./databases/mysql-database-config.cli I added datasource config https://gist.github.com/marti1125/9806765 but I have this problem 07:36:19,418 ERROR [org.jboss.as.controller.management-operation] (Controller Bo ot Thread) JBAS014613: Operation ("add") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "UnifiedPushDS") ]) - failure description: { "JBAS014771: Services with missing/unavailable dependencies" => [ "jboss.driver-demander.java:jboss/datasources/UnifiedPushDS is missing [ jboss.jdbc-driver.com_mysql_jdbc_Driver]", "jboss.data-source.java:jboss/datasources/UnifiedPushDS is missing [jbos s.jdbc-driver.com_mysql_jdbc_Driver]" -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140327/ff7cbc51/attachment.html From matzew at apache.org Thu Mar 27 08:59:41 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 27 Mar 2014 13:59:41 +0100 Subject: [aerogear-dev] unifiedpush server with mysql In-Reply-To: References: Message-ID: Hi, (assuiming you are using JBoss AS 7.1.1); It looks like you are missing the JBDC driver. Did you deploy the module: cp -r databases/src/main/resources/modules/com /Path/to/JBossAS/modules/ and the actual JAR file (of the JDBC driver) ? mvn dependency:copy -Dartifact=mysql:mysql-connector-java:5.1.18 -DoutputDirectory=/Path/to/JBossAS/modules/com/mysql/jdbc/main/ (Oh, just in case.... for WildFly the script is _slightly_ different - not yet there) In any case, for simple starters, I'd highly recommend using the H2 database. Simply copy the DS-XML file into $JBOSS (or $WILDFLY) /standalone/deployments (yes - that works w/ WildFly as well - as is, no modification needed) Greetings, Matthias On Thu, Mar 27, 2014 at 1:52 PM, Willy Martin Aguirre Rodriguez < marti1003 at hotmail.com> wrote: > I am trying to run unifiedpush server with mysql but I have some problem > with datasource > > > https://github.com/aerogear/aerogear-unifiedpush-server#mysql-database-configuration > > I get errors when I try to run > > /Path/to/JBossAS/bin/jboss-cli.sh > --file=./databases/mysql-database-config.cli > > I added datasource config https://gist.github.com/marti1125/9806765 > > but I have this problem > > 07:36:19,418 ERROR [org.jboss.as.controller.management-operation] > (Controller Bo > ot Thread) JBAS014613: Operation ("add") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "UnifiedPushDS") > ]) - failure description: { > "JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.driver-demander.java:jboss/datasources/UnifiedPushDS is > missing [ > jboss.jdbc-driver.com_mysql_jdbc_Driver]", > "jboss.data-source.java:jboss/datasources/UnifiedPushDS is missing > [jbos > s.jdbc-driver.com_mysql_jdbc_Driver]" > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140327/a8ec3369/attachment.html From kpiwko at redhat.com Thu Mar 27 09:06:36 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Thu, 27 Mar 2014 14:06:36 +0100 Subject: [aerogear-dev] unifiedpush server with mysql In-Reply-To: References: Message-ID: <20140327140636.75167f37@kapy-ntb-x220> Hi, you're missing MySQL driver on server classpath. Datasource expects it is installed as JBoss/WF module: I'm not aware of better tutorial but you can follow these steps: 1/ You can get module scafold from here: https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/databases/src/main/resources/modules/ 2/ Get mysql-connector-java-5.1.18.jar file and put it into com/mysql/jdbc/main 3/ Copy whole module to AS7/WF modules directory (you just need the one starting with com, org is for postgres) HTH, Karel On Thu, 27 Mar 2014 07:52:35 -0500 Willy Martin Aguirre Rodriguez wrote: > I am trying to run unifiedpush server with mysql but I have some problem with > datasource > > https://github.com/aerogear/aerogear-unifiedpush-server#mysql-database-configuration > > I get errors when I try to run > > /Path/to/JBossAS/bin/jboss-cli.sh --file=./databases/mysql-database-config.cli > > I added datasource config https://gist.github.com/marti1125/9806765 > > but I have this problem > > 07:36:19,418 ERROR [org.jboss.as.controller.management-operation] (Controller > Bo ot Thread) JBAS014613: Operation ("add") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "UnifiedPushDS") > ]) - failure description: { > "JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.driver-demander.java:jboss/datasources/UnifiedPushDS is > missing [ jboss.jdbc-driver.com_mysql_jdbc_Driver]", > "jboss.data-source.java:jboss/datasources/UnifiedPushDS is missing > [jbos s.jdbc-driver.com_mysql_jdbc_Driver]" > From hbons at redhat.com Thu Mar 27 09:07:14 2014 From: hbons at redhat.com (Hylke Bons) Date: Thu, 27 Mar 2014 13:07:14 +0000 Subject: [aerogear-dev] UPS UX updates In-Reply-To: References: <5331B750.1060609@redhat.com> <5331CDA5.1050405@redhat.com> Message-ID: <53342282.5000801@redhat.com> Hey, On 26/03/2014 09:44, Sebastien Blanc wrote: > > > > On Wed, Mar 26, 2014 at 9:30 AM, Matthias Wessendorf > > wrote: > > As said before: overall they are really looking very great and > modern! I really like them. > > A few questions on some of the screens: > > * applications.png > List ("table") of all Push Applications: > - Is there no side bar for this? > I left out the sidebar in a couple of screens for time reasons. The sidebar when realised will be on every screen just like the header. > > * application-details-blue.png > It's the details of one application, and has overview of all its > variants. > - Is the plan to list all variants on their platform? Instead of > having a table? I do like that grouping! Just wondering :-) > > I also like the grouping but when we will introduce paging, it will be > paging per groups ? Not sure how UX friendly that will be. > Yea, it makes much more sense to do variant grouping by platform than just having one huge table like we had previously. Paging will happen per platform "group". > - When I click on a certain variant (e.g. the "Demo" variant of > the iOS section ), there is no separate page/view for its' > details? Like its installations ? I'd really prefer to have a > page/view for all the details of a certain variant. Also the code > snippets for a variant is missing > > > I also like it this way, all the info needed can fit and not sure if > we want to navigate to another page jsut for the details (For editing > yes => other page). > A problem with this was that the Application Details page looked too much like the Variant Details page. It's convenient to have all the needed actions and code snippets, for sending notifications and registering installations, one a single page. Why do you like having a separate Variant Details page? > The Code Snippets : Yeah A button/link would be needed This are the "What's this for?" links. We might want to reconsider the name for that. > > - Sidebar: is that specific to an application? See notes on > "applications.png" > - The "Notifications" on the sidebar, what's that? > - What's the "gear-wheel" for ? > The gear menu will have contextual actions like "Rename" and "Delete". It's less cluttered than having them as links or icons on every row. > > * "dialogs.png" > - For an application construct, that's good enough; Creating a > variant is a bit more complex (see current UI) > - Is there no side bar for this? > > > I assume that for delete app/variant or reset id/secrets we will use > the same dialogs > > > > * installations.png > - Is there no side bar for this? > - If I understand the view/page correctly, its a list of ALL > installations for one PushApplication. However, we should list the > variants PER variant (see current UI). The Navigation path on the > bread-crumbs would be "Applications >> Mobile HR >> Demo (iOS) >> > Installations (number)" > > +1 but I think that was also Hylke's initial idea because on the > application details screen you see that the link to installations is > on the "variant" level. I think it was just a glitch in his bread-crumbs. I wasn't too sure about what we could do here. In some cases it's good to have installations per variant, in others you want to see them per application. We could have both: every installation number shown in the group rows will be links to per variant installations. the "total" link at the top would link to a table will all the installations for the application. Hylke > > * loading.png > - yeah, that is totally missing today :-)) > > > > > Greetings, > Matthias > > > > On Tue, Mar 25, 2014 at 8:50 PM, Matthias Wessendorf > > wrote: > > Awesome mock ups!! > > > On Tuesday, March 25, 2014, Hylke Bons > wrote: > > > > Hello, > > https://github.com/hbons/aerogear-design/tree/master/ups-new-ux > The above link contains mockups with an updated look and feel. > > I've tried to consolodate the info that we had on > different pages on > fewer pages, as a common critique was that the Application > Details and > Variant Details pages looked alike too much, so I've > merged them. > > On one page I've added a sidebar that reflects future > features (it's > just for show). > > Other notable things are the orange info blocks where we > want app > developers to take action on information (the device > registration and > sending notifications in this case). I've deliberately > made these stand > out a bit more as we want people to act on the > information. Please note > that one row in the variants table shows up expanded in > the mockups for > illustration purposes. The rows will all be collapsed on > first view, so > it won't look as cluttered as you might think at first > seeing the mockup. > > Let me know what you think and where we should go from here. > > Thanks, > > Hylke > > > > _______________________________________________ > 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140327/4019a433/attachment.html From marti1003 at hotmail.com Thu Mar 27 09:11:43 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Thu, 27 Mar 2014 08:11:43 -0500 Subject: [aerogear-dev] unifiedpush server with mysql In-Reply-To: <20140327140636.75167f37@kapy-ntb-x220> References: , <20140327140636.75167f37@kapy-ntb-x220> Message-ID: I have the same problem with H2 C:\wildfly\bin>jboss-cli.bat --file=C:\unifiedpush\databases\h2-database-config. cli The batch failed with the following error (you are remaining in the batch editin g mode to have a chance to correct the error): {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS 014803: Duplicate resource [ (\"subsystem\" => \"datasources\"), (\"data-source\" => \"UnifiedPushDS\") ]"}} > Date: Thu, 27 Mar 2014 14:06:36 +0100 > From: kpiwko at redhat.com > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] unifiedpush server with mysql > > Hi, > > you're missing MySQL driver on server classpath. Datasource expects it is > installed as JBoss/WF module: > > I'm not aware of better tutorial but you can follow these steps: > > 1/ You can get module scafold from here: > https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/databases/src/main/resources/modules/ > > 2/ Get mysql-connector-java-5.1.18.jar file and put it into com/mysql/jdbc/main > > 3/ Copy whole module to AS7/WF modules directory (you just need the one > starting with com, org is for postgres) > > HTH, > > Karel > > > On Thu, 27 Mar 2014 07:52:35 -0500 > Willy Martin Aguirre Rodriguez wrote: > > > I am trying to run unifiedpush server with mysql but I have some problem with > > datasource > > > > https://github.com/aerogear/aerogear-unifiedpush-server#mysql-database-configuration > > > > I get errors when I try to run > > > > /Path/to/JBossAS/bin/jboss-cli.sh --file=./databases/mysql-database-config.cli > > > > I added datasource config https://gist.github.com/marti1125/9806765 > > > > but I have this problem > > > > 07:36:19,418 ERROR [org.jboss.as.controller.management-operation] (Controller > > Bo ot Thread) JBAS014613: Operation ("add") failed - address: ([ > > ("subsystem" => "datasources"), > > ("data-source" => "UnifiedPushDS") > > ]) - failure description: { > > "JBAS014771: Services with missing/unavailable dependencies" => [ > > "jboss.driver-demander.java:jboss/datasources/UnifiedPushDS is > > missing [ jboss.jdbc-driver.com_mysql_jdbc_Driver]", > > "jboss.data-source.java:jboss/datasources/UnifiedPushDS is missing > > [jbos s.jdbc-driver.com_mysql_jdbc_Driver]" > > > _______________________________________________ > 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/20140327/4ff80e33/attachment-0001.html From marti1003 at hotmail.com Thu Mar 27 09:15:34 2014 From: marti1003 at hotmail.com (Willy Martin Aguirre Rodriguez) Date: Thu, 27 Mar 2014 08:15:34 -0500 Subject: [aerogear-dev] unifiedpush server with mysql In-Reply-To: References: , , <20140327140636.75167f37@kapy-ntb-x220>, Message-ID: ups with h2-database works From: marti1003 at hotmail.com To: aerogear-dev at lists.jboss.org Date: Thu, 27 Mar 2014 08:11:43 -0500 Subject: Re: [aerogear-dev] unifiedpush server with mysql I have the same problem with H2 C:\wildfly\bin>jboss-cli.bat --file=C:\unifiedpush\databases\h2-database-config. cli The batch failed with the following error (you are remaining in the batch editin g mode to have a chance to correct the error): {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS 014803: Duplicate resource [ (\"subsystem\" => \"datasources\"), (\"data-source\" => \"UnifiedPushDS\") ]"}} > Date: Thu, 27 Mar 2014 14:06:36 +0100 > From: kpiwko at redhat.com > To: aerogear-dev at lists.jboss.org > Subject: Re: [aerogear-dev] unifiedpush server with mysql > > Hi, > > you're missing MySQL driver on server classpath. Datasource expects it is > installed as JBoss/WF module: > > I'm not aware of better tutorial but you can follow these steps: > > 1/ You can get module scafold from here: > https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/databases/src/main/resources/modules/ > > 2/ Get mysql-connector-java-5.1.18.jar file and put it into com/mysql/jdbc/main > > 3/ Copy whole module to AS7/WF modules directory (you just need the one > starting with com, org is for postgres) > > HTH, > > Karel > > > On Thu, 27 Mar 2014 07:52:35 -0500 > Willy Martin Aguirre Rodriguez wrote: > > > I am trying to run unifiedpush server with mysql but I have some problem with > > datasource > > > > https://github.com/aerogear/aerogear-unifiedpush-server#mysql-database-configuration > > > > I get errors when I try to run > > > > /Path/to/JBossAS/bin/jboss-cli.sh --file=./databases/mysql-database-config.cli > > > > I added datasource config https://gist.github.com/marti1125/9806765 > > > > but I have this problem > > > > 07:36:19,418 ERROR [org.jboss.as.controller.management-operation] (Controller > > Bo ot Thread) JBAS014613: Operation ("add") failed - address: ([ > > ("subsystem" => "datasources"), > > ("data-source" => "UnifiedPushDS") > > ]) - failure description: { > > "JBAS014771: Services with missing/unavailable dependencies" => [ > > "jboss.driver-demander.java:jboss/datasources/UnifiedPushDS is > > missing [ jboss.jdbc-driver.com_mysql_jdbc_Driver]", > > "jboss.data-source.java:jboss/datasources/UnifiedPushDS is missing > > [jbos s.jdbc-driver.com_mysql_jdbc_Driver]" > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140327/f1f21422/attachment.html From matzew at apache.org Thu Mar 27 10:00:36 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 27 Mar 2014 15:00:36 +0100 Subject: [aerogear-dev] UPS UX updates In-Reply-To: <53342282.5000801@redhat.com> References: <5331B750.1060609@redhat.com> <5331CDA5.1050405@redhat.com> <53342282.5000801@redhat.com> Message-ID: On Thu, Mar 27, 2014 at 2:07 PM, Hylke Bons wrote: > Hey, > > On 26/03/2014 09:44, Sebastien Blanc wrote: > > > > > On Wed, Mar 26, 2014 at 9:30 AM, Matthias Wessendorf wrote: > >> As said before: overall they are really looking very great and modern! >> I really like them. >> >> A few questions on some of the screens: >> >> * applications.png >> List ("table") of all Push Applications: >> - Is there no side bar for this? >> > > I left out the sidebar in a couple of screens for time reasons. The > sidebar when realised will be on every screen just like the header. > perfect! > > > >> * application-details-blue.png >> It's the details of one application, and has overview of all its variants. >> - Is the plan to list all variants on their platform? Instead of having a >> table? I do like that grouping! Just wondering :-) >> > > I also like the grouping but when we will introduce paging, it will be > paging per groups ? Not sure how UX friendly that will be. > > > Yea, it makes much more sense to do variant grouping by platform than just > having one huge table like we had previously. Paging will happen per > platform "group". > great! I'd don't see a huge problem here in pagination of the variatns; I doubt that one PushApp has a gazillion different variants > > > > - When I click on a certain variant (e.g. the "Demo" variant of the >> iOS section ), there is no separate page/view for its' details? Like its >> installations ? I'd really prefer to have a page/view for all the details >> of a certain variant. Also the code snippets for a variant is missing >> > > I also like it this way, all the info needed can fit and not sure if we > want to navigate to another page jsut for the details (For editing yes => > other page). > > A problem with this was that the Application Details page looked too > much like the Variant Details page. It's convenient to have all the needed > actions and code snippets, for sending notifications and registering > installations, one a single page. Why do you like having a separate Variant > Details page? > Ok, I now "understand" the new flow, of the UI. > > > > The Code Snippets : Yeah A button/link would be needed > > > This are the "What's this for?" links. We might want to reconsider the > name for that. > Now, I open the details of a variant (by clicking on it), and I see the LINK Clicking on it will give me a "popup" with the different code-snippet (note: we need Cordova + native), per variant, right ? > > > > >> >> - Sidebar: is that specific to an application? See notes on >> "applications.png" >> - The "Notifications" on the sidebar, what's that? >> - What's the "gear-wheel" for ? >> > > The gear menu will have contextual actions like "Rename" and "Delete". > It's less cluttered than having them as links or icons on every row. > ah!!! Took a bit to realize that :-) > > > >> * "dialogs.png" >> - For an application construct, that's good enough; Creating a variant is >> a bit more complex (see current UI) >> - Is there no side bar for this? >> > > I assume that for delete app/variant or reset id/secrets we will use the > same dialogs > >> >> >> * installations.png >> - Is there no side bar for this? >> - If I understand the view/page correctly, its a list of ALL >> installations for one PushApplication. However, we should list the variants >> PER variant (see current UI). The Navigation path on the bread-crumbs >> would be "Applications >> Mobile HR >> Demo (iOS) >> Installations >> (number)" >> > +1 but I think that was also Hylke's initial idea because on the > application details screen you see that the link to installations is on the > "variant" level. I think it was just a glitch in his bread-crumbs. > > > I wasn't too sure about what we could do here. In some cases it's good to > have installations per variant, in others you want to see them per > application. > for now, I think, let's list them only per variant - feels (for me) a bit more clean Thanks for the reply. I hope we are now all on the same page. Oh, any chance to get a bit rid of that blue; replacing by a different colour ? :-)) > We could have both: every installation number shown in the group rows will > be links to per variant installations. the "total" link at the top would > link to a table will all the installations for the application. > > Hylke > > > >> * loading.png >> - yeah, that is totally missing today :-)) >> >> >> >> >> Greetings, >> Matthias >> >> >> >> On Tue, Mar 25, 2014 at 8:50 PM, Matthias Wessendorf wrote: >> >>> Awesome mock ups!! >>> >>> >>> On Tuesday, March 25, 2014, Hylke Bons wrote: >>> >>>> >>>> >>>> Hello, >>>> >>>> https://github.com/hbons/aerogear-design/tree/master/ups-new-ux >>>> The above link contains mockups with an updated look and feel. >>>> >>>> I've tried to consolodate the info that we had on different pages on >>>> fewer pages, as a common critique was that the Application Details and >>>> Variant Details pages looked alike too much, so I've merged them. >>>> >>>> On one page I've added a sidebar that reflects future features (it's >>>> just for show). >>>> >>>> Other notable things are the orange info blocks where we want app >>>> developers to take action on information (the device registration and >>>> sending notifications in this case). I've deliberately made these stand >>>> out a bit more as we want people to act on the information. Please note >>>> that one row in the variants table shows up expanded in the mockups for >>>> illustration purposes. The rows will all be collapsed on first view, so >>>> it won't look as cluttered as you might think at first seeing the >>>> mockup. >>>> >>>> Let me know what you think and where we should go from here. >>>> >>>> Thanks, >>>> >>>> Hylke >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> _______________________________________________ >> 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 > -- 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/20140327/70ed1172/attachment-0001.html From hbons at redhat.com Thu Mar 27 11:51:53 2014 From: hbons at redhat.com (Hylke Bons) Date: Thu, 27 Mar 2014 15:51:53 +0000 Subject: [aerogear-dev] UPS UX updates In-Reply-To: References: <5331B750.1060609@redhat.com> <5331CDA5.1050405@redhat.com> <53342282.5000801@redhat.com> Message-ID: <53344919.3090506@redhat.com> On 27/03/2014 14:00, Matthias Wessendorf wrote: > > > > great! I'd don't see a huge problem here in pagination of the > variatns; I doubt that one PushApp has a gazillion different variants I don't think it will be a problem either. When variants are going into the bazillion numbers there will be many other problems in managing apart from pagination. Managing them will practically become impossible. > > > > > >> The Code Snippets : Yeah A button/link would be needed > > This are the "What's this for?" links. We might want to reconsider > the name for that. > > > Now, I open the details of a variant (by clicking on it), and I see > the LINK > > Clicking on it will give me a "popup" with the different code-snippet > (note: we need Cordova + native), per variant, right ? > > > > >> >> - Sidebar: is that specific to an application? See notes on >> "applications.png" >> - The "Notifications" on the sidebar, what's that? >> - What's the "gear-wheel" for ? >> > > The gear menu will have contextual actions like "Rename" and > "Delete". It's less cluttered than having them as links or icons > on every row. > > > > > ah!!! Took a bit to realize that :-) > > > > >> >> * "dialogs.png" >> - For an application construct, that's good enough; Creating >> a variant is a bit more complex (see current UI) >> - Is there no side bar for this? >> >> >> I assume that for delete app/variant or reset id/secrets we will >> use the same dialogs >> >> >> >> * installations.png >> - Is there no side bar for this? >> - If I understand the view/page correctly, its a list of ALL >> installations for one PushApplication. However, we should >> list the variants PER variant (see current UI). The >> Navigation path on the bread-crumbs would be "Applications >> >> Mobile HR >> Demo (iOS) >> Installations (number)" >> >> +1 but I think that was also Hylke's initial idea because on the >> application details screen you see that the link to installations >> is on the "variant" level. I think it was just a glitch in his >> bread-crumbs. > > I wasn't too sure about what we could do here. In some cases it's > good to have installations per variant, in others you want to see > them per application. > > > for now, I think, let's list them only per variant - feels (for me) a > bit more clean > I'm fine with that. > > Thanks for the reply. I hope we are now all on the same page. > > Oh, any chance to get a bit rid of that blue; replacing by a different > colour ? :-)) > This is the blue from patternfly.org, but we can discuss different options. What about yellow and black stripes? :P > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140327/96a47318/attachment.html From cvasilak at gmail.com Thu Mar 27 12:23:52 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Thu, 27 Mar 2014 18:23:52 +0200 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: <29DE6245-57E0-441C-B8D2-6B8693BF9A77@gmail.com> References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> <29DE6245-57E0-441C-B8D2-6B8693BF9A77@gmail.com> Message-ID: Hi everyone, fyi, as of yesterday update[1], agios lib now uses latest crypto and you can give it a spin, try with our with crypto-ios-demo[2] or our cookbook examples[3] (the cookbook exercises both the afnet upgrade of the library and latest crypto). If there are no issues found, plan is to merge and release new aerogear-ios v1.5 early next week that will incorporate these changes. Thanks, Christos [1] https://github.com/aerogear/aerogear-ios/pull/123 [2] https://github.com/cvasilak/aerogear-crypto-ios-demo/tree/AGIOS-181 [3] https://github.com/cvasilak/aerogear-ios-cookbook/tree/AGIOS-181 From michi.oshima at gmail.com Thu Mar 27 12:46:29 2014 From: michi.oshima at gmail.com (Michi Oshima) Date: Thu, 27 Mar 2014 12:46:29 -0400 Subject: [aerogear-dev] AeroGear Push Server cartridge, Quickstart client, and CORS Message-ID: Hi, I'm currently looking into AeroGear Push Server (Simple with Unified). For prototyping, I pieced together the following environment: 1. "AeroGear Push Server 0.10.0" cartridge running as an OpenShift application. 2. Git cloned aerogear-simplepush-unifiedpush-quickstart I edited unifiedpush.js so it points to my OpenShift application. Then I open index.html in a browser and I get the following error: - XMLHttpRequest cannot load https://aerogear-****. rhcloud.com/8443/simplepush/info. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin ' http://127.0.0.1:9000' is therefore not allowed access. (OK, I got the error from when hosted the index.html on a web server running locally. But I get pretty much the same result from just opening index.html from the file system.) Does this mean that simple push server on my OpenShift application does not support CORS? Or, am I not doing something right? Thanks, Michi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140327/1f3c5d98/attachment.html From lholmqui at redhat.com Thu Mar 27 12:55:09 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Thu, 27 Mar 2014 12:55:09 -0400 Subject: [aerogear-dev] AeroGear Push Server cartridge, Quickstart client, and CORS In-Reply-To: References: Message-ID: what browser are you using? On Mar 27, 2014, at 12:46 PM, Michi Oshima wrote: > Hi, > > I'm currently looking into AeroGear Push Server (Simple with Unified). > > For prototyping, I pieced together the following environment: > > 1. "AeroGear Push Server 0.10.0" cartridge running as an OpenShift application. > 2. Git cloned aerogear-simplepush-unifiedpush-quickstart > > I edited unifiedpush.js so it points to my OpenShift application. Then I open index.html in a browser and I get the following error: > > XMLHttpRequest cannot load https://aerogear-****.rhcloud.com/8443/simplepush/info. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:9000' is therefore not allowed access. > (OK, I got the error from when hosted the index.html on a web server running locally. But I get pretty much the same result from just opening index.html from the file system.) > > Does this mean that simple push server on my OpenShift application does not support CORS? Or, am I not doing something right? > > Thanks, > > Michi > > _______________________________________________ > 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/20140327/5748008d/attachment.html From michi.oshima at gmail.com Thu Mar 27 12:56:48 2014 From: michi.oshima at gmail.com (Michi Oshima) Date: Thu, 27 Mar 2014 12:56:48 -0400 Subject: [aerogear-dev] AeroGear Push Server cartridge, Quickstart client, and CORS In-Reply-To: References: Message-ID: Chrome, Version 33.0.1750.152, on Mac OS X. On Thu, Mar 27, 2014 at 12:55 PM, Lucas Holmquist wrote: > what browser are you using? > On Mar 27, 2014, at 12:46 PM, Michi Oshima wrote: > > Hi, > > I'm currently looking into AeroGear Push Server (Simple with Unified). > > For prototyping, I pieced together the following environment: > > 1. "AeroGear Push Server 0.10.0" > cartridge running as an OpenShift application. > 2. Git cloned aerogear-simplepush-unifiedpush-quickstart > > I edited unifiedpush.js so it points to my OpenShift application. Then I > open index.html in a browser and I get the following error: > > > - XMLHttpRequest cannot load https://aerogear-****. > rhcloud.com/8443/simplepush/info. No 'Access-Control-Allow-Origin' > header is present on the requested resource. Origin ' > http://127.0.0.1:9000' is therefore not allowed access. > > (OK, I got the error from when hosted the index.html on a web server > running locally. But I get pretty much the same result from just opening > index.html from the file system.) > > Does this mean that simple push server on my OpenShift application does > not support CORS? Or, am I not doing something right? > > Thanks, > > Michi > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140327/0305ff5f/attachment-0001.html From matzew at apache.org Thu Mar 27 13:18:29 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 27 Mar 2014 18:18:29 +0100 Subject: [aerogear-dev] AeroGear Push Server cartridge, Quickstart client, and CORS In-Reply-To: References: Message-ID: Hello Michi! thanks for the interest; I _just_ created a new instance, and I got the conenction to the SPS established. In here: https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart/blob/master/js/unifiedpush.js#L7 Make sure you are using "https://aerogear-****.rhcloud.com/8443/simplepush" On Thu, Mar 27, 2014 at 5:56 PM, Michi Oshima wrote: > Chrome, Version 33.0.1750.152, on Mac OS X. > > > On Thu, Mar 27, 2014 at 12:55 PM, Lucas Holmquist wrote: > >> what browser are you using? >> On Mar 27, 2014, at 12:46 PM, Michi Oshima >> wrote: >> >> Hi, >> >> I'm currently looking into AeroGear Push Server (Simple with Unified). >> >> For prototyping, I pieced together the following environment: >> >> 1. "AeroGear Push Server 0.10.0" >> cartridge running as an OpenShift application. >> 2. Git cloned aerogear-simplepush-unifiedpush-quickstart >> >> I edited unifiedpush.js so it points to my OpenShift application. Then I >> open index.html in a browser and I get the following error: >> >> >> - XMLHttpRequest cannot load https://aerogear-****. >> rhcloud.com/8443/simplepush/info. No 'Access-Control-Allow-Origin' >> header is present on the requested resource. Origin ' >> http://127.0.0.1:9000' is therefore not allowed access. >> >> (OK, I got the error from when hosted the index.html on a web server >> running locally. But I get pretty much the same result from just opening >> index.html from the file system.) >> >> Does this mean that simple push server on my OpenShift application does >> not support CORS? Or, am I not doing something right? >> >> Thanks, >> >> Michi >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140327/6d996f46/attachment.html From scm.blanc at gmail.com Thu Mar 27 13:23:18 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 27 Mar 2014 18:23:18 +0100 Subject: [aerogear-dev] AeroGear Push Server cartridge, Quickstart client, and CORS In-Reply-To: References: Message-ID: On Thu, Mar 27, 2014 at 6:18 PM, Matthias Wessendorf wrote: > Hello Michi! > > thanks for the interest; I _just_ created a new instance, and I got the > conenction to the SPS established. > > In here: > > https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart/blob/master/js/unifiedpush.js#L7 > > Make sure you are using "https://aerogear-****.rhcloud.com/8443/simplepush > " > I suppose it's a typo here "https://aerogear-****. rhcloud.com:8443/simplepush " and not " https://aerogear-****.rhcloud.com/8443/simplepush" > > > > > > > On Thu, Mar 27, 2014 at 5:56 PM, Michi Oshima wrote: > >> Chrome, Version 33.0.1750.152, on Mac OS X. >> >> >> On Thu, Mar 27, 2014 at 12:55 PM, Lucas Holmquist wrote: >> >>> what browser are you using? >>> On Mar 27, 2014, at 12:46 PM, Michi Oshima >>> wrote: >>> >>> Hi, >>> >>> I'm currently looking into AeroGear Push Server (Simple with Unified). >>> >>> For prototyping, I pieced together the following environment: >>> >>> 1. "AeroGear Push Server 0.10.0" >>> cartridge running as an OpenShift application. >>> 2. Git cloned aerogear-simplepush-unifiedpush-quickstart >>> >>> I edited unifiedpush.js so it points to my OpenShift application. Then >>> I open index.html in a browser and I get the following error: >>> >>> >>> - XMLHttpRequest cannot load https://aerogear-****. >>> rhcloud.com/8443/simplepush/info. No 'Access-Control-Allow-Origin' >>> header is present on the requested resource. Origin ' >>> http://127.0.0.1:9000' is therefore not allowed access. >>> >>> (OK, I got the error from when hosted the index.html on a web server >>> running locally. But I get pretty much the same result from just opening >>> index.html from the file system.) >>> >>> Does this mean that simple push server on my OpenShift application does >>> not support CORS? Or, am I not doing something right? >>> >>> Thanks, >>> >>> Michi >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140327/27b64625/attachment.html From michi.oshima at gmail.com Thu Mar 27 13:50:22 2014 From: michi.oshima at gmail.com (Michi Oshima) Date: Thu, 27 Mar 2014 13:50:22 -0400 Subject: [aerogear-dev] AeroGear Push Server cartridge, Quickstart client, and CORS In-Reply-To: References: Message-ID: Doh! Sorry to have you guys fix my typo. I corrected my typo ("/" --> ":"), and the quick-start example works now. Awesome. Thanks so much! Michi On Thu, Mar 27, 2014 at 1:23 PM, Sebastien Blanc wrote: > > > > On Thu, Mar 27, 2014 at 6:18 PM, Matthias Wessendorf wrote: > >> Hello Michi! >> >> thanks for the interest; I _just_ created a new instance, and I got the >> conenction to the SPS established. >> >> In here: >> >> https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart/blob/master/js/unifiedpush.js#L7 >> >> Make sure you are using "https://aerogear-****. >> rhcloud.com/8443/simplepush" >> > > I suppose it's a typo here "https://aerogear-****. > rhcloud.com:8443/simplepush " and not > "https://aerogear-****.rhcloud.com/8443/simplepush" > >> >> >> >> >> >> >> On Thu, Mar 27, 2014 at 5:56 PM, Michi Oshima wrote: >> >>> Chrome, Version 33.0.1750.152, on Mac OS X. >>> >>> >>> On Thu, Mar 27, 2014 at 12:55 PM, Lucas Holmquist wrote: >>> >>>> what browser are you using? >>>> On Mar 27, 2014, at 12:46 PM, Michi Oshima >>>> wrote: >>>> >>>> Hi, >>>> >>>> I'm currently looking into AeroGear Push Server (Simple with Unified). >>>> >>>> For prototyping, I pieced together the following environment: >>>> >>>> 1. "AeroGear Push Server 0.10.0" >>>> cartridge running as an OpenShift application. >>>> 2. Git cloned aerogear-simplepush-unifiedpush-quickstart >>>> >>>> I edited unifiedpush.js so it points to my OpenShift application. Then >>>> I open index.html in a browser and I get the following error: >>>> >>>> >>>> - XMLHttpRequest cannot load https://aerogear-****. >>>> rhcloud.com/8443/simplepush/info. No 'Access-Control-Allow-Origin' >>>> header is present on the requested resource. Origin ' >>>> http://127.0.0.1:9000' is therefore not allowed access. >>>> >>>> (OK, I got the error from when hosted the index.html on a web server >>>> running locally. But I get pretty much the same result from just opening >>>> index.html from the file system.) >>>> >>>> Does this mean that simple push server on my OpenShift application does >>>> not support CORS? Or, am I not doing something right? >>>> >>>> Thanks, >>>> >>>> Michi >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140327/dcdee5a7/attachment-0001.html From matzew at apache.org Thu Mar 27 14:38:59 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 27 Mar 2014 19:38:59 +0100 Subject: [aerogear-dev] AeroGear Push Server cartridge, Quickstart client, and CORS In-Reply-To: References: Message-ID: Glad it works :-) Let us know if anything else occurs -Matthias On Thursday, March 27, 2014, Michi Oshima wrote: > Doh! > > Sorry to have you guys fix my typo. I corrected my typo ("/" --> ":"), > and the quick-start example works now. Awesome. > > Thanks so much! > > Michi > > > On Thu, Mar 27, 2014 at 1:23 PM, Sebastien Blanc wrote: > > > > > On Thu, Mar 27, 2014 at 6:18 PM, Matthias Wessendorf wrote: > > Hello Michi! > > thanks for the interest; I _just_ created a new instance, and I got the > conenction to the SPS established. > > In here: > > https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart/blob/master/js/unifiedpush.js#L7 > > Make sure you are using "https://aerogear-****.rhcloud.com/8443/simplepush > " > > > I suppose it's a typo here "https://aerogear-****. > rhcloud.com:8443/simplepush " and not > "https://aerogear-****.rhcloud.com/8443/simplepush" > > > > > > > > On Thu, Mar 27, 2014 at 5:56 PM, Michi Oshima wrote: > > Chrome, Version 33.0.1750.152, on Mac OS X. > > > On Thu, Mar 27, 2014 at 12:55 PM, Lucas Holmquist wrote: > > what browser are you using? > On Mar 27, 2014, at 12:46 PM, Michi Oshima wrote: > > Hi, > > I'm currently looking into AeroGear Push Server (Simple with Unified). > > For prototyping, I pieced together the following environment: > > 1. "AeroGear Push Server 0.10.0" > cartridge running as an OpenShift application. > 2. Git cloned aerogear-simplepush-unifiedpush-quickstart > > I edited unifiedpush.js so it points to my OpenShift application. Then I > open index.html in a browser and I get the following error: > > > - XMLHttpRequest cannot load https://aerogear-****. > rhcloud.com/8443/simplepush/info. No 'Access-Control-Allow-Origin' > header is present on the requested resource. Origin ' > http://127.0.0.1:9000' is therefore not allowed access. > > (OK, I got the error from when hosted the index.html on a web server > running locally. But I get pretty much the same result from just opening > index.html from the file system.) > > Does this mean that simple push server on my OpenShift application does not > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140327/2a9526ae/attachment.html From kpiwko at redhat.com Fri Mar 28 05:12:04 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Fri, 28 Mar 2014 10:12:04 +0100 Subject: [aerogear-dev] AeroGear iOS 1.5 In-Reply-To: References: <88D548E1-AD2A-472E-BD92-74CDF043CFA2@gmail.com> <5C2B0DEB-E700-4A9D-B127-323A7A014352@gmail.com> <29DE6245-57E0-441C-B8D2-6B8693BF9A77@gmail.com> Message-ID: <20140328101204.509ea930@kapy-ntb-x220> Hi Christos, QE will have a look on Monday, so you can expect our report Monday evening if everything goes well. Karel On Thu, 27 Mar 2014 18:23:52 +0200 Christos Vasilakis wrote: > Hi everyone, > > fyi, as of yesterday update[1], agios lib now uses latest crypto and you can > give it a spin, try with our with crypto-ios-demo[2] or our cookbook > examples[3] (the cookbook exercises both the afnet upgrade of the library > and latest crypto). If there are no issues found, plan is to merge and > release new aerogear-ios v1.5 early next week that will incorporate these > changes. > > Thanks, > Christos > > [1] https://github.com/aerogear/aerogear-ios/pull/123 > [2] https://github.com/cvasilak/aerogear-crypto-ios-demo/tree/AGIOS-181 > [3] https://github.com/cvasilak/aerogear-ios-cookbook/tree/AGIOS-181 > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From antoine.matyja at worldline.com Fri Mar 28 11:07:43 2014 From: antoine.matyja at worldline.com (A577127) Date: Fri, 28 Mar 2014 08:07:43 -0700 (PDT) Subject: [aerogear-dev] Building UnifiedPush Server from sources Message-ID: <1396019263157-7159.post@n5.nabble.com> Hello, I need to try some stuff with the UnifiedPush server (eg redirecting HTTP POST requests to my own test server instead of GCM's server). However I'm not really familiar with JBoss. I've downloaded the sources from git here and I need to do a few things but didn't find out how to : - Import the project to Eclipse (classic Eclipse Import doesn't show anything) - Build a .war deployable file (I looked for an Ant target on Github but didn't find any) - Edit web interface (I saw that .js file was minified ; can I get a non-minified somewhere ?) I know my questions are quite evasive, if I ask for too much don't hesitate to just give me links to tutorials, I will take time to read them and try to solve these problems myself. Thanks, -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Building-UnifiedPush-Server-from-sources-tp7159.html Sent from the aerogear-dev mailing list archive at Nabble.com. From lholmqui at redhat.com Fri Mar 28 11:11:56 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Fri, 28 Mar 2014 11:11:56 -0400 Subject: [aerogear-dev] Building UnifiedPush Server from sources In-Reply-To: <1396019263157-7159.post@n5.nabble.com> References: <1396019263157-7159.post@n5.nabble.com> Message-ID: <67FE8CD8-DDAD-4AE1-B809-B867E3D41428@redhat.com> hi On Mar 28, 2014, at 11:07 AM, A577127 wrote: > Hello, > > I need to try some stuff with the UnifiedPush server (eg redirecting HTTP > POST requests to my own test server instead of GCM's server). However I'm > not really familiar with JBoss. > > I've downloaded the sources from git here > and I need to do > a few things but didn't find out how to : > - Import the project to Eclipse (classic Eclipse Import doesn't show > anything) > - Build a .war deployable file (I looked for an Ant target on Github but > didn't find any) we use maven https://github.com/aerogear/aerogear-unifiedpush-server#deploy-the-unifiedpush-server > - Edit web interface (I saw that .js file was minified ; can I get a > non-minified somewhere ?) the web UI is in the repo also https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/admin-ui there should be a read me with instructions on how to build that also > > I know my questions are quite evasive, if I ask for too much don't hesitate > to just give me links to tutorials, I will take time to read them and try to > solve these problems myself. > > Thanks, > > > > -- > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Building-UnifiedPush-Server-from-sources-tp7159.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140328/9da1bc0a/attachment.html From kpiwko at redhat.com Fri Mar 28 11:37:00 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Fri, 28 Mar 2014 16:37:00 +0100 Subject: [aerogear-dev] Building UnifiedPush Server from sources In-Reply-To: <1396019263157-7159.post@n5.nabble.com> References: <1396019263157-7159.post@n5.nabble.com> Message-ID: <20140328163700.0c6eb21f@kapy-ntb-x220> On Fri, 28 Mar 2014 08:07:43 -0700 (PDT) A577127 wrote: > Hello, > > I need to try some stuff with the UnifiedPush server (eg redirecting HTTP > POST requests to my own test server instead of GCM's server). However I'm > not really familiar with JBoss. > > I've downloaded the sources from git here > and I need to do > a few things but didn't find out how to : > - Import the project to Eclipse (classic Eclipse Import doesn't show > anything) If you are familiar with Eclipse, the best thing to do would be to install JBoss Tools on top of your Eclipse installation - it contains support for Maven, Git and plenty of other useful things You can get it according to instructions here: https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Developer_Studio/7.1/html/Installation_Guide/Install_JBoss_Developer_Studio_BYOE.html Or you can get Eclipse with JBoss Tools bundled as JBoss Developer Studio: https://www.jboss.org/products/devstudio.html > - Build a .war deployable file (I looked for an Ant target on Github but > didn't find any) > - Edit web interface (I saw that .js file was minified ; can I get a > non-minified somewhere ?) > > I know my questions are quite evasive, if I ask for too much don't hesitate > to just give me links to tutorials, I will take time to read them and try to > solve these problems myself. > > Thanks, > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Building-UnifiedPush-Server-from-sources-tp7159.html > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From jbalunas at redhat.com Fri Mar 28 11:40:36 2014 From: jbalunas at redhat.com (Jay Balunas) Date: Fri, 28 Mar 2014 11:40:36 -0400 Subject: [aerogear-dev] UPS Console US/Tech updates Message-ID: Hi All, After talking with Thomas about how liveoak has been working I think their approach to tracking there work there is a good approach. Take a look at these jira's for an example. https://issues.jboss.org/browse/LIVEOAK-91 https://issues.jboss.org/browse/LIVEOAK-80 Is this something we could do for our upcoming console and tech migration efforts? This will also make it a lot easier for us to judge where we are, and what work is left. Especially when we have assistance from others (such as some on the LiveOak team). Another area that Thomas and I talked about was the UX/HTML/CSS reviews and reuse. The updated mockups from Hylke [1] are obviously quite similar to LiveOak's console. There should be quite a bit of overlap with core HTML and CSS that should make it easier for Hylke to produce what we need. Any help that Gabriel will be able to assist, advise, and review which should help a lot. Thoughts? Thanks, -Jay [1] https://github.com/hbons/aerogear-design/blob/master/ups-new-ux/application-details-blue.png -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140328/72bcda7e/attachment-0001.html From matzew at apache.org Fri Mar 28 12:11:36 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 28 Mar 2014 17:11:36 +0100 Subject: [aerogear-dev] UPS Console US/Tech updates In-Reply-To: References: Message-ID: Hello, On Fri, Mar 28, 2014 at 4:40 PM, Jay Balunas wrote: > Hi All, > > After talking with Thomas about how liveoak has been working I think their > approach to tracking there work there is a good approach. Take a look at > these jira's for an example. > > https://issues.jboss.org/browse/LIVEOAK-91 > https://issues.jboss.org/browse/LIVEOAK-80 > > Is this something we could do for our upcoming console and tech migration > efforts? This will also make it a lot easier for us to judge where we are, > and what work is left. Especially when we have assistance from others > (such as some on the LiveOak team). > for the 'overall' work on doing the actual overhaul of the AdminUI for the UnifiedPush Server, I created this JIRA/Epic already: https://issues.jboss.org/browse/AGPUSH-573 Not sure, but perhaps we can make the following tickets become epics as well: https://issues.jboss.org/browse/AGPUSH-575 https://issues.jboss.org/browse/AGPUSH-576 where they have a bunch of sub-tasks. One sub-task per page. That would give as an exact list of steps > > Another area that Thomas and I talked about was the UX/HTML/CSS reviews > and reuse. The updated mockups from Hylke [1] are obviously quite similar > to LiveOak's console. There should be quite a bit of overlap with core > HTML and CSS that should make it easier for Hylke to produce what we need. > Any help that Gabriel will be able to assist, advise, and review which > should help a lot. > > Thoughts? > > Thanks, > -Jay > > [1] > https://github.com/hbons/aerogear-design/blob/master/ups-new-ux/application-details-blue.png > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140328/c60a4eb2/attachment.html From daniel.bevenius at gmail.com Mon Mar 31 03:05:55 2014 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Mon, 31 Mar 2014 09:05:55 +0200 Subject: [aerogear-dev] Team meeting Message-ID: Agenda: http://oksoclap.com/p/aerogear-team-mgt-20140331 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140331/607695bd/attachment.html From scm.blanc at gmail.com Mon Mar 31 05:00:27 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 31 Mar 2014 11:00:27 +0200 Subject: [aerogear-dev] UPS Console US/Tech updates In-Reply-To: References: Message-ID: On Fri, Mar 28, 2014 at 5:11 PM, Matthias Wessendorf wrote: > Hello, > > > On Fri, Mar 28, 2014 at 4:40 PM, Jay Balunas wrote: > >> Hi All, >> >> After talking with Thomas about how liveoak has been working I think >> their approach to tracking there work there is a good approach. Take a >> look at these jira's for an example. >> >> https://issues.jboss.org/browse/LIVEOAK-91 >> https://issues.jboss.org/browse/LIVEOAK-80 >> >> Is this something we could do for our upcoming console and tech migration >> efforts? This will also make it a lot easier for us to judge where we are, >> and what work is left. Especially when we have assistance from others >> (such as some on the LiveOak team). >> > > > for the 'overall' work on doing the actual overhaul of the AdminUI for the > UnifiedPush Server, I created this JIRA/Epic already: > > https://issues.jboss.org/browse/AGPUSH-573 > > Not sure, but perhaps we can make the following tickets become epics as > well: > https://issues.jboss.org/browse/AGPUSH-575 > https://issues.jboss.org/browse/AGPUSH-576 > > where they have a bunch of sub-tasks. One sub-task per page. That would > give as an exact list of steps > +1 let's break that into smaller sub-tasks like : Application Screen / Variant Screen / Installation Screen / KC / Login Integration. > > > >> >> Another area that Thomas and I talked about was the UX/HTML/CSS reviews >> and reuse. The updated mockups from Hylke [1] are obviously quite similar >> to LiveOak's console. There should be quite a bit of overlap with core >> HTML and CSS that should make it easier for Hylke to produce what we need. >> Any help that Gabriel will be able to assist, advise, and review which >> should help a lot. >> >> Thoughts? >> > For sure, we have to be efficient here and reuse all what is possible. We must also keep a close eye on this project https://github.com/patternfly/angular-patternfly which will help us a lot to align with LO (since these angular directive will be the one extracted from the LO project)). > >> Thanks, >> -Jay >> >> [1] >> https://github.com/hbons/aerogear-design/blob/master/ups-new-ux/application-details-blue.png >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.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/20140331/c3094933/attachment.html From matzew at apache.org Mon Mar 31 05:04:49 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 11:04:49 +0200 Subject: [aerogear-dev] UPS Console US/Tech updates In-Reply-To: References: Message-ID: On Mon, Mar 31, 2014 at 11:00 AM, Sebastien Blanc wrote: > > > > On Fri, Mar 28, 2014 at 5:11 PM, Matthias Wessendorf wrote: > >> Hello, >> >> >> On Fri, Mar 28, 2014 at 4:40 PM, Jay Balunas wrote: >> >>> Hi All, >>> >>> After talking with Thomas about how liveoak has been working I think >>> their approach to tracking there work there is a good approach. Take a >>> look at these jira's for an example. >>> >>> https://issues.jboss.org/browse/LIVEOAK-91 >>> https://issues.jboss.org/browse/LIVEOAK-80 >>> >>> Is this something we could do for our upcoming console and tech >>> migration efforts? This will also make it a lot easier for us to judge >>> where we are, and what work is left. Especially when we have assistance >>> from others (such as some on the LiveOak team). >>> >> >> >> for the 'overall' work on doing the actual overhaul of the AdminUI for >> the UnifiedPush Server, I created this JIRA/Epic already: >> >> https://issues.jboss.org/browse/AGPUSH-573 >> >> Not sure, but perhaps we can make the following tickets become epics as >> well: >> https://issues.jboss.org/browse/AGPUSH-575 >> https://issues.jboss.org/browse/AGPUSH-576 >> >> where they have a bunch of sub-tasks. One sub-task per page. That would >> give as an exact list of steps >> > > +1 let's break that into smaller sub-tasks like : Application Screen / > Variant Screen / Installation Screen / KC / Login Integration. > OK - let me do that > >> >> >>> >>> Another area that Thomas and I talked about was the UX/HTML/CSS reviews >>> and reuse. The updated mockups from Hylke [1] are obviously quite similar >>> to LiveOak's console. There should be quite a bit of overlap with core >>> HTML and CSS that should make it easier for Hylke to produce what we need. >>> Any help that Gabriel will be able to assist, advise, and review which >>> should help a lot. >>> >>> Thoughts? >>> >> > For sure, we have to be efficient here and reuse all what is possible. We > must also keep a close eye on this project > https://github.com/patternfly/angular-patternfly which will help us a lot > to align with LO (since these angular directive will be the one extracted > from the LO project)). > > > >> >>> Thanks, >>> -Jay >>> >>> [1] >>> https://github.com/hbons/aerogear-design/blob/master/ups-new-ux/application-details-blue.png >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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/20140331/b52ce115/attachment-0001.html From corinnekrych at gmail.com Mon Mar 31 07:48:46 2014 From: corinnekrych at gmail.com (Corinne Krych) Date: Mon, 31 Mar 2014 13:48:46 +0200 Subject: [aerogear-dev] aerogear.org revamp: team work In-Reply-To: References: <5CEC844E-310B-4DB7-AC89-43E5CC57EA18@gmail.com> Message-ID: Hello Abstractj I?ve reviewed and just fixed the genrated css file [1] and the site looks good to me with the latest mmaster chnages incorporated. +1 to carry on merging into sass branch. a New reabase might be needed as it?s already one week old.. sorry for the delay. ++ Corinne [1] https://github.com/aerogear/aerogear.org/commit/37dd1ff03f7a9cf737bef309f4ff0ce0189eeb7c On 20 Mar 2014, at 12:09, Bruno Oliveira wrote: > Ahoy, I did the rebase https://github.com/aerogear/aerogear.org/tree/sass-rebased. But due to my great skills on sass, something is wrong. > > > Any takers? > > -- > abstractj > > On March 19, 2014 at 11:01:25 AM, Corinne Krych (corinnekrych at gmail.com) wrote: >> Let me rebase. >> ++ >> Corinne >> On 19 Mar 2014, at 14:01, Bruno Oliveira wrote: >> >>> Hi Corinne, I was giving a look at sass branch and I?m really concerned due to the number >> of conflicts with ?master?. >>> >>> I think for the sanity of everyone, is healthy to regularly rebase that branch against >> master like Corinne mentioned before. I tried rebase, but due to my poor sass skills, >> I?m afraid of mess it up. >>> >>> What I did? >>> >>> git checkout sass >>> git rebase origin/master >>> >>> >>> -- >>> abstractj >>> >>> On February 24, 2014 at 11:09:59 AM, Corinne Krych (corinnekrych at gmail.com) wrote: >>>> Hello All, >>>> >>>> With aerogear web site roadmap [1] proposal we can start working together toward a >> new >>>> website. We already have a common branch (named sass - maybe not the best name) [2] where >>>> we can work together. It?s important to rebase/keep this branch up to date. >>>> >>>> Here is how we could work together efficiently: >>>> - take JIRA for 0.1.0 release, >>>> - branch from sass branch, do you work >>>> - send PR againt sass. >>>> - usual PR review >>>> - then PR can be merged into sass. >>>> >>>> If a ticket requires changes in page documentation like splitting a markdown page >> into >>>> several pages or move to asciidoc format etc? we should do this JIRA initial in master >>>> branch, send a PRL, get the PR merged and get the changes in sass branch. This way we can >>>> keep history and let the documentation evolves without fear for merging it into new >> site >>>> revamp branch. >>>> >>>> Thought? #agreed? >>>> >>>> ++ >>>> Corinne >>>> [1] http://aerogear.org/docs/planning/roadmaps/AeroGearWebSite/ >>>> [2 https://github.com/aerogear/aerogear.org/tree/sass >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >> >> > From bruno at abstractj.org Mon Mar 31 09:19:42 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 31 Mar 2014 10:19:42 -0300 Subject: [aerogear-dev] aerogear.org revamp: team work In-Reply-To: References: <5CEC844E-310B-4DB7-AC89-43E5CC57EA18@gmail.com> Message-ID: Np, go for it. -- abstractj On March 31, 2014 at 8:48:56 AM, Corinne Krych (corinnekrych at gmail.com) wrote: > > Hello Abstractj > > I?ve reviewed and just fixed the genrated css file [1] and the > site looks good to me with the latest mmaster chnages incorporated. > +1 to carry on merging into sass branch. > a New reabase might be needed as it?s already one week old.. sorry > for the delay. From matzew at apache.org Mon Mar 31 09:25:41 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 15:25:41 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples Message-ID: Hello there, we recently had talks about creating some simplified quickstarts and hello-word demos, related to the UnifiedPush Server and JBoss AS developers: * Hello World (No Server Code - just client receiving push, no fancy (complex) UI on the client, nor integrated into a Cookbook or something that has "dependencies") ** Cordova ** Android For iOS that is already there: https://github.com/aerogear/aerogear-push-ios-demo Yes, just usage of the "Push Registration SDKs", is the goal here: keep it simple, since native push can be a complicated use-case all on its own and so it will be good to make sure we cover the basics here. Beyond the Hello-World, we wanted some different quickstarts. The "server" components that come to mind would be: *Secured CRUD + Push Integration (Java Sender) ** JAX-RS + PicketLink ** SpringMVC/Spring Security ** JAX-RS + Apache Camel These need to function on both JBoss AS 7.X and EAP. Josh, from the JDF team, has already said he wants to help on the server projects (especially the JAX-RS/PL and Spring ones). yay! Note: Josh already has a simple backend started that is used in JDF quickstarts that would be good to re-use to make it easier for developers to transition from one to other. The goal would be the SERVER acts same to outside (identical REST endpoints, difference is only an impl. detail (e.g. JavaEE vs. Spring vs. Camel)) For these different servers, there would be mobile apps needed: * Android * Cordova * iOS The idea would be to keep them simple and straightforward as well, e.g. for iOS that means plain usage of NSURLConnection / NSURLSession. But for the "push registration" of the client, the iOS-push SDK would be used (same/similar would apply to Cordova or Android). Similar to the above 'Hello World', the quickstarts are going to be focused only on Push functionality, so for these we would leave out pipes and such until later versions. I will be creating Epics and subtasks in JIRA for this. For the location of all these projects, I had this "uber repo" location in mind: * https://github.com/aerogear/aerogear-push-helloworld * https://github.com/aerogear/aerogear-push-quickstarts Greetings, 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/20140331/f2e42e38/attachment.html From scm.blanc at gmail.com Mon Mar 31 09:32:59 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 31 Mar 2014 15:32:59 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: References: Message-ID: On Mon, Mar 31, 2014 at 3:25 PM, Matthias Wessendorf wrote: > Hello there, > > we recently had talks about creating some simplified quickstarts and > hello-word demos, related to the UnifiedPush Server and JBoss AS developers: > > * Hello World (No Server Code - just client receiving push, no fancy > (complex) UI on the client, nor integrated into a Cookbook or something > that has "dependencies") > ** Cordova > For Cordova, Erik's example that is shipped with the Push Plugin could be a good start : https://github.com/aerogear/aerogear-pushplugin-cordova/blob/master/example/index.html > ** Android > > For iOS that is already there: > https://github.com/aerogear/aerogear-push-ios-demo > > Yes, just usage of the "Push Registration SDKs", is the goal here: keep it > simple, since native push can be a complicated use-case all on its own and > so it will be good to make sure we cover the basics here. > > > Beyond the Hello-World, we wanted some different quickstarts. The "server" > components that come to mind would be: > > *Secured CRUD + Push Integration (Java Sender) > ** JAX-RS + PicketLink > ** SpringMVC/Spring Security > ** JAX-RS + Apache Camel > > These need to function on both JBoss AS 7.X and EAP. > > Josh, from the JDF team, has already said he wants to help on the server > projects (especially the JAX-RS/PL and Spring ones). yay! > Note: Josh already has a simple backend started that is used in JDF > quickstarts that would be good to re-use to make it easier for developers > to transition from one to other. > > > The goal would be the SERVER acts same to outside (identical REST > endpoints, difference is only an impl. detail (e.g. JavaEE vs. Spring vs. > Camel)) > > For these different servers, there would be mobile apps needed: > * Android > * Cordova > For Cordova we could use some of the work Josh started for the front end (using jquery mobile) > * iOS > > > The idea would be to keep them simple and straightforward as well, e.g. > for iOS that means plain usage of NSURLConnection / NSURLSession. But for > the "push registration" of the client, > the iOS-push SDK would be used (same/similar would apply to Cordova or > Android). Similar to the above 'Hello World', the quickstarts are going to > be focused only on Push functionality, so for these we would leave out > pipes and such until later versions. > > > I will be creating Epics and subtasks in JIRA for this. > > For the location of all these projects, I had this "uber repo" location in > mind: > * https://github.com/aerogear/aerogear-push-helloworld > * https://github.com/aerogear/aerogear-push-quickstarts > +1 sounds good > > Greetings, > 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/20140331/3f21892c/attachment.html From matzew at apache.org Mon Mar 31 09:37:56 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 15:37:56 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: References: Message-ID: On Mon, Mar 31, 2014 at 3:32 PM, Sebastien Blanc wrote: > > > > On Mon, Mar 31, 2014 at 3:25 PM, Matthias Wessendorf wrote: > >> Hello there, >> >> we recently had talks about creating some simplified quickstarts and >> hello-word demos, related to the UnifiedPush Server and JBoss AS developers: >> >> * Hello World (No Server Code - just client receiving push, no fancy >> (complex) UI on the client, nor integrated into a Cookbook or something >> that has "dependencies") >> ** Cordova >> > For Cordova, Erik's example that is shipped with the Push Plugin could be > a good start : > https://github.com/aerogear/aerogear-pushplugin-cordova/blob/master/example/index.html > > good call! For the Hello-World that needs to be its own application :-) But fully agree - we can use exactly this SRC for the Hello-World-Cordova app. Also, I think, from the plugin we could than also simply link to the "Hello World", right ? > ** Android >> >> For iOS that is already there: >> https://github.com/aerogear/aerogear-push-ios-demo >> >> Yes, just usage of the "Push Registration SDKs", is the goal here: keep >> it simple, since native push can be a complicated use-case all on its own >> and so it will be good to make sure we cover the basics here. >> >> >> Beyond the Hello-World, we wanted some different quickstarts. The >> "server" components that come to mind would be: >> >> *Secured CRUD + Push Integration (Java Sender) >> ** JAX-RS + PicketLink >> ** SpringMVC/Spring Security >> ** JAX-RS + Apache Camel >> >> These need to function on both JBoss AS 7.X and EAP. >> >> Josh, from the JDF team, has already said he wants to help on the server >> projects (especially the JAX-RS/PL and Spring ones). yay! >> Note: Josh already has a simple backend started that is used in JDF >> quickstarts that would be good to re-use to make it easier for developers >> to transition from one to other. >> >> >> The goal would be the SERVER acts same to outside (identical REST >> endpoints, difference is only an impl. detail (e.g. JavaEE vs. Spring vs. >> Camel)) >> >> For these different servers, there would be mobile apps needed: >> * Android >> * Cordova >> > For Cordova we could use some of the work Josh started for the front end > (using jquery mobile) > >> * iOS >> >> >> The idea would be to keep them simple and straightforward as well, e.g. >> for iOS that means plain usage of NSURLConnection / NSURLSession. But for >> the "push registration" of the client, >> the iOS-push SDK would be used (same/similar would apply to Cordova or >> Android). Similar to the above 'Hello World', the quickstarts are going to >> be focused only on Push functionality, so for these we would leave out >> pipes and such until later versions. >> >> >> I will be creating Epics and subtasks in JIRA for this. >> >> For the location of all these projects, I had this "uber repo" location >> in mind: >> * https://github.com/aerogear/aerogear-push-helloworld >> * https://github.com/aerogear/aerogear-push-quickstarts >> > > +1 sounds good > > >> >> Greetings, >> 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/20140331/54eac2cf/attachment-0001.html From supittma at redhat.com Mon Mar 31 09:58:57 2014 From: supittma at redhat.com (Summers Pittman) Date: Mon, 31 Mar 2014 09:58:57 -0400 Subject: [aerogear-dev] Modularization and Push Message-ID: <533974A1.1020406@redhat.com> Y'all, So there has been some concerns with the complexity of the build especially where including the Google GCM (push) libraries are concerned. Additionally there have been some requests for a separate "push" module which won't need the full aerogear android library. The full modularization of the library along with several other improvements is scheduled for the "2.0" epic. So my question is a) Should we make a 2.0 which is only the modularization sooner and iterate on that a few times before we include our improvements in a 3.0 or b) Should we create a "fork" project which is only a push module? This new project will get merged back into the main project when we have our complete modularizations. -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From matzew at apache.org Mon Mar 31 10:01:31 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 16:01:31 +0200 Subject: [aerogear-dev] Modularization and Push In-Reply-To: <533974A1.1020406@redhat.com> References: <533974A1.1020406@redhat.com> Message-ID: On Mon, Mar 31, 2014 at 3:58 PM, Summers Pittman wrote: > Y'all, > > So there has been some concerns with the complexity of the build > especially where including the Google GCM (push) libraries are > concerned. Additionally there have been some requests for a separate > "push" module which won't need the full aerogear android library. > > The full modularization of the library along with several other > improvements is scheduled for the "2.0" epic. > > So my question is a) Should we make a 2.0 which is only the > modularization sooner and iterate on that a few times before we include > our improvements in a 3.0 or b) Should we create a "fork" project which > is only a push module? This new project will get merged back into the > main project when we have our complete modularizations. > I am fine in having a branch, where the push related modularizations live in. Once we are ready for an overall modularization (aka 2.0 timeframe), let's do it than. but yeah - for now the fork/branch sounds good for me -M > > > > -- > 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/20140331/92af039f/attachment.html From scm.blanc at gmail.com Mon Mar 31 10:05:05 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 31 Mar 2014 16:05:05 +0200 Subject: [aerogear-dev] Modularization and Push In-Reply-To: <533974A1.1020406@redhat.com> References: <533974A1.1020406@redhat.com> Message-ID: On Mon, Mar 31, 2014 at 3:58 PM, Summers Pittman wrote: > Y'all, > > So there has been some concerns with the complexity of the build > especially where including the Google GCM (push) libraries are > concerned. Additionally there have been some requests for a separate > "push" module which won't need the full aerogear android library. > > The full modularization of the library along with several other > improvements is scheduled for the "2.0" epic. > https://issues.jboss.org/browse/AGDROID-236 mentions fix version : 1.4 , should that be updated ? > > So my question is a) Should we make a 2.0 which is only the > modularization sooner and iterate on that a few times before we include > our improvements in a 3.0 or b) Should we create a "fork" project which > is only a push module? This new project will get merged back into the > main project when we have our complete modularizations. > > > > -- > 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/20140331/fd9e2d89/attachment.html From supittma at redhat.com Mon Mar 31 10:06:42 2014 From: supittma at redhat.com (Summers Pittman) Date: Mon, 31 Mar 2014 10:06:42 -0400 Subject: [aerogear-dev] Modularization and Push In-Reply-To: References: <533974A1.1020406@redhat.com> Message-ID: <53397672.400@redhat.com> On Mon 31 Mar 2014 10:05:05 AM EDT, Sebastien Blanc wrote: > > > > On Mon, Mar 31, 2014 at 3:58 PM, Summers Pittman > wrote: > > Y'all, > > So there has been some concerns with the complexity of the build > especially where including the Google GCM (push) libraries are > concerned. Additionally there have been some requests for a separate > "push" module which won't need the full aerogear android library. > > The full modularization of the library along with several other > improvements is scheduled for the "2.0" epic. > > https://issues.jboss.org/browse/AGDROID-236 mentions fix version : 1.4 > , should that be updated ? > > > So my question is a) Should we make a 2.0 which is only the > modularization sooner and iterate on that a few times before we > include > our improvements in a 3.0 or b) Should we create a "fork" project > which > is only a push module? This new project will get merged back into the > main project when we have our complete modularizations. > > > > -- > 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 Updated. -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. From cvasilak at gmail.com Mon Mar 31 10:27:32 2014 From: cvasilak at gmail.com (Christos Vasilakis) Date: Mon, 31 Mar 2014 17:27:32 +0300 Subject: [aerogear-dev] Team meeting In-Reply-To: References: Message-ID: <572D5E22-36AD-46EA-B718-3A78CA0992AF@gmail.com> FYI meeting minutes: Meeting ended Mon Mar 31 14:11:13 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-31-13.47.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-31-13.47.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-31-13.47.log.html On Mar 31, 2014, at 10:05 AM, Daniel Bevenius wrote: > Agenda: > http://oksoclap.com/p/aerogear-team-mgt-20140331 > _______________________________________________ > 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/20140331/edc7c25e/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140331/edc7c25e/attachment.bin From daniel.bevenius at gmail.com Mon Mar 31 10:27:46 2014 From: daniel.bevenius at gmail.com (danielbevenius) Date: Mon, 31 Mar 2014 07:27:46 -0700 (PDT) Subject: [aerogear-dev] Team meeting In-Reply-To: References: Message-ID: <1396276066573-7176.post@n5.nabble.com> Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-31-13.47.html Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-31-13.47.txt Log: http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-03-31-13.47.log.html -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Team-meeting-tp7164p7176.html Sent from the aerogear-dev mailing list archive at Nabble.com. From kpiwko at redhat.com Mon Mar 31 10:39:16 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Mon, 31 Mar 2014 16:39:16 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: References: Message-ID: <20140331163916.5ed8d732@kapy-ntb-x220> On Mon, 31 Mar 2014 15:25:41 +0200 Matthias Wessendorf wrote: > Hello there, > > we recently had talks about creating some simplified quickstarts and > hello-word demos, related to the UnifiedPush Server and JBoss AS developers: > > * Hello World (No Server Code - just client receiving push, no fancy > (complex) UI on the client, nor integrated into a Cookbook or something > that has "dependencies") > ** Cordova > ** Android > > For iOS that is already there: > https://github.com/aerogear/aerogear-push-ios-demo > > Yes, just usage of the "Push Registration SDKs", is the goal here: keep it > simple, since native push can be a complicated use-case all on its own and > so it will be good to make sure we cover the basics here. > > > Beyond the Hello-World, we wanted some different quickstarts. The "server" > components that come to mind would be: > > *Secured CRUD + Push Integration (Java Sender) > ** JAX-RS + PicketLink > ** SpringMVC/Spring Security > ** JAX-RS + Apache Camel > > These need to function on both JBoss AS 7.X and EAP. > > Josh, from the JDF team, has already said he wants to help on the server > projects (especially the JAX-RS/PL and Spring ones). yay! > Note: Josh already has a simple backend started that is used in JDF > quickstarts that would be good to re-use to make it easier for developers > to transition from one to other. > > > The goal would be the SERVER acts same to outside (identical REST > endpoints, difference is only an impl. detail (e.g. JavaEE vs. Spring vs. > Camel)) > > For these different servers, there would be mobile apps needed: > * Android > * Cordova > * iOS I'm not sure if I got that. You mean extra 3 apps per each supported backed? Making it 9 additional apps to test and maintain? Should not the client be the same no matter have backend is set up? > > > The idea would be to keep them simple and straightforward as well, e.g. for > iOS that means plain usage of NSURLConnection / NSURLSession. But for the > "push registration" of the client, > the iOS-push SDK would be used (same/similar would apply to Cordova or > Android). Similar to the above 'Hello World', the quickstarts are going to > be focused only on Push functionality, so for these we would leave out > pipes and such until later versions. > > > I will be creating Epics and subtasks in JIRA for this. > > For the location of all these projects, I had this "uber repo" location in > mind: > * https://github.com/aerogear/aerogear-push-helloworld > * https://github.com/aerogear/aerogear-push-quickstarts > > Greetings, > Matthias > > > From matzew at apache.org Mon Mar 31 10:41:09 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 16:41:09 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: <20140331163916.5ed8d732@kapy-ntb-x220> References: <20140331163916.5ed8d732@kapy-ntb-x220> Message-ID: On Mon, Mar 31, 2014 at 4:39 PM, Karel Piwko wrote: > On Mon, 31 Mar 2014 15:25:41 +0200 > Matthias Wessendorf wrote: > > > Hello there, > > > > we recently had talks about creating some simplified quickstarts and > > hello-word demos, related to the UnifiedPush Server and JBoss AS > developers: > > > > * Hello World (No Server Code - just client receiving push, no fancy > > (complex) UI on the client, nor integrated into a Cookbook or something > > that has "dependencies") > > ** Cordova > > ** Android > > > > For iOS that is already there: > > https://github.com/aerogear/aerogear-push-ios-demo > > > > Yes, just usage of the "Push Registration SDKs", is the goal here: keep > it > > simple, since native push can be a complicated use-case all on its own > and > > so it will be good to make sure we cover the basics here. > > > > > > Beyond the Hello-World, we wanted some different quickstarts. The > "server" > > components that come to mind would be: > > > > *Secured CRUD + Push Integration (Java Sender) > > ** JAX-RS + PicketLink > > ** SpringMVC/Spring Security > > ** JAX-RS + Apache Camel > > > > These need to function on both JBoss AS 7.X and EAP. > > > > Josh, from the JDF team, has already said he wants to help on the server > > projects (especially the JAX-RS/PL and Spring ones). yay! > > Note: Josh already has a simple backend started that is used in JDF > > quickstarts that would be good to re-use to make it easier for developers > > to transition from one to other. > > > > > > The goal would be the SERVER acts same to outside (identical REST > > endpoints, difference is only an impl. detail (e.g. JavaEE vs. Spring vs. > > Camel)) > > > > For these different servers, there would be mobile apps needed: > > * Android > > * Cordova > > * iOS > > I'm not sure if I got that. You mean extra 3 apps per each supported > backed? > Making it 9 additional apps to test and maintain? > No: total of 3 server apps and 3 client apps > Should not the client be the same no matter have backend is set up? > > > > > > > The idea would be to keep them simple and straightforward as well, e.g. > for > > iOS that means plain usage of NSURLConnection / NSURLSession. But for the > > "push registration" of the client, > > the iOS-push SDK would be used (same/similar would apply to Cordova or > > Android). Similar to the above 'Hello World', the quickstarts are going > to > > be focused only on Push functionality, so for these we would leave out > > pipes and such until later versions. > > > > > > I will be creating Epics and subtasks in JIRA for this. > > > > For the location of all these projects, I had this "uber repo" location > in > > mind: > > * https://github.com/aerogear/aerogear-push-helloworld > > * https://github.com/aerogear/aerogear-push-quickstarts > > > > Greetings, > > Matthias > > > > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140331/9d036eec/attachment.html From kpiwko at redhat.com Mon Mar 31 11:03:12 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Mon, 31 Mar 2014 17:03:12 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: References: <20140331163916.5ed8d732@kapy-ntb-x220> Message-ID: <20140331170312.6132bc84@kapy-ntb-x220> On Mon, 31 Mar 2014 16:41:09 +0200 Matthias Wessendorf wrote: > On Mon, Mar 31, 2014 at 4:39 PM, Karel Piwko wrote: > > > On Mon, 31 Mar 2014 15:25:41 +0200 > > Matthias Wessendorf wrote: > > > > > Hello there, > > > > > > we recently had talks about creating some simplified quickstarts and > > > hello-word demos, related to the UnifiedPush Server and JBoss AS > > developers: > > > > > > * Hello World (No Server Code - just client receiving push, no fancy > > > (complex) UI on the client, nor integrated into a Cookbook or something > > > that has "dependencies") > > > ** Cordova > > > ** Android > > > > > > For iOS that is already there: > > > https://github.com/aerogear/aerogear-push-ios-demo > > > > > > Yes, just usage of the "Push Registration SDKs", is the goal here: keep > > it > > > simple, since native push can be a complicated use-case all on its own > > and > > > so it will be good to make sure we cover the basics here. > > > > > > > > > Beyond the Hello-World, we wanted some different quickstarts. The > > "server" > > > components that come to mind would be: > > > > > > *Secured CRUD + Push Integration (Java Sender) > > > ** JAX-RS + PicketLink > > > ** SpringMVC/Spring Security > > > ** JAX-RS + Apache Camel > > > > > > These need to function on both JBoss AS 7.X and EAP. > > > > > > Josh, from the JDF team, has already said he wants to help on the server > > > projects (especially the JAX-RS/PL and Spring ones). yay! > > > Note: Josh already has a simple backend started that is used in JDF > > > quickstarts that would be good to re-use to make it easier for developers > > > to transition from one to other. > > > > > > > > > The goal would be the SERVER acts same to outside (identical REST > > > endpoints, difference is only an impl. detail (e.g. JavaEE vs. Spring vs. > > > Camel)) > > > > > > For these different servers, there would be mobile apps needed: > > > * Android > > > * Cordova > > > * iOS > > > > I'm not sure if I got that. You mean extra 3 apps per each supported > > backed? > > Making it 9 additional apps to test and maintain? > > > > > No: total of 3 server apps and 3 client apps That's a weight off my shoulders :-) What do you guys feel of these quickstarts having additional registration button? E.g. it should be possible to provide UPS username/pass/variant name, and get variantId/secret dynamically via REST, so not hardcoded in app. You could then use one app to (re)connect to different UPS instances without redeploy. Once registered via button, variantId/secret could go into offline storage. Something similar to https://github.com/TadeasKriz/aerogear-push-test-android/blob/master/src/org/jboss/aerogear/pushtest/activity/RegistrationActivity.java#L57 I'm not sure if it's good for a quickstart but it should be valuable for a demo. > > > > Should not the client be the same no matter have backend is set up? > > > > > > > > > > > The idea would be to keep them simple and straightforward as well, e.g. > > for > > > iOS that means plain usage of NSURLConnection / NSURLSession. But for the > > > "push registration" of the client, > > > the iOS-push SDK would be used (same/similar would apply to Cordova or > > > Android). Similar to the above 'Hello World', the quickstarts are going > > to > > > be focused only on Push functionality, so for these we would leave out > > > pipes and such until later versions. > > > > > > > > > I will be creating Epics and subtasks in JIRA for this. > > > > > > For the location of all these projects, I had this "uber repo" location > > in > > > mind: > > > * https://github.com/aerogear/aerogear-push-helloworld > > > * https://github.com/aerogear/aerogear-push-quickstarts > > > > > > Greetings, > > > Matthias > > > > > > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > From kpiwko at redhat.com Mon Mar 31 11:07:03 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Mon, 31 Mar 2014 17:07:03 +0200 Subject: [aerogear-dev] Modularization and Push In-Reply-To: <533974A1.1020406@redhat.com> References: <533974A1.1020406@redhat.com> Message-ID: <20140331170703.7e719f86@kapy-ntb-x220> I'd prefer a) unless you plan to regularly release milestones of b) into Maven Central. Relying on snapshots in demos and tests is a PITA. And this looks like a lot of effort, so branch might be living its own life for a very long time. Karel On Mon, 31 Mar 2014 09:58:57 -0400 Summers Pittman wrote: > Y'all, > > So there has been some concerns with the complexity of the build > especially where including the Google GCM (push) libraries are > concerned. Additionally there have been some requests for a separate > "push" module which won't need the full aerogear android library. > > The full modularization of the library along with several other > improvements is scheduled for the "2.0" epic. > > So my question is a) Should we make a 2.0 which is only the > modularization sooner and iterate on that a few times before we include > our improvements in a 3.0 or b) Should we create a "fork" project which > is only a push module? This new project will get merged back into the > main project when we have our complete modularizations. > > > From scm.blanc at gmail.com Mon Mar 31 11:08:06 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 31 Mar 2014 17:08:06 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: <20140331170312.6132bc84@kapy-ntb-x220> References: <20140331163916.5ed8d732@kapy-ntb-x220> <20140331170312.6132bc84@kapy-ntb-x220> Message-ID: On Mon, Mar 31, 2014 at 5:03 PM, Karel Piwko wrote: > On Mon, 31 Mar 2014 16:41:09 +0200 > Matthias Wessendorf wrote: > > > On Mon, Mar 31, 2014 at 4:39 PM, Karel Piwko wrote: > > > > > On Mon, 31 Mar 2014 15:25:41 +0200 > > > Matthias Wessendorf wrote: > > > > > > > Hello there, > > > > > > > > we recently had talks about creating some simplified quickstarts and > > > > hello-word demos, related to the UnifiedPush Server and JBoss AS > > > developers: > > > > > > > > * Hello World (No Server Code - just client receiving push, no fancy > > > > (complex) UI on the client, nor integrated into a Cookbook or > something > > > > that has "dependencies") > > > > ** Cordova > > > > ** Android > > > > > > > > For iOS that is already there: > > > > https://github.com/aerogear/aerogear-push-ios-demo > > > > > > > > Yes, just usage of the "Push Registration SDKs", is the goal here: > keep > > > it > > > > simple, since native push can be a complicated use-case all on its > own > > > and > > > > so it will be good to make sure we cover the basics here. > > > > > > > > > > > > Beyond the Hello-World, we wanted some different quickstarts. The > > > "server" > > > > components that come to mind would be: > > > > > > > > *Secured CRUD + Push Integration (Java Sender) > > > > ** JAX-RS + PicketLink > > > > ** SpringMVC/Spring Security > > > > ** JAX-RS + Apache Camel > > > > > > > > These need to function on both JBoss AS 7.X and EAP. > > > > > > > > Josh, from the JDF team, has already said he wants to help on the > server > > > > projects (especially the JAX-RS/PL and Spring ones). yay! > > > > Note: Josh already has a simple backend started that is used in JDF > > > > quickstarts that would be good to re-use to make it easier for > developers > > > > to transition from one to other. > > > > > > > > > > > > The goal would be the SERVER acts same to outside (identical REST > > > > endpoints, difference is only an impl. detail (e.g. JavaEE vs. > Spring vs. > > > > Camel)) > > > > > > > > For these different servers, there would be mobile apps needed: > > > > * Android > > > > * Cordova > > > > * iOS > > > > > > I'm not sure if I got that. You mean extra 3 apps per each supported > > > backed? > > > Making it 9 additional apps to test and maintain? > > > > > > > > > No: total of 3 server apps and 3 client apps > > That's a weight off my shoulders :-) > > What do you guys feel of these quickstarts having additional registration > button? E.g. it should be possible to provide UPS username/pass/variant > name, > and get variantId/secret dynamically via REST, so not hardcoded in app. You > could then use one app to (re)connect to different UPS instances without > redeploy. Once registered via button, variantId/secret could go into > offline > storage. > > Something similar to > > https://github.com/TadeasKriz/aerogear-push-test-android/blob/master/src/org/jboss/aerogear/pushtest/activity/RegistrationActivity.java#L57 > I'm not sure if it's good for a quickstart but it should be valuable for a > demo. > Yeah for a demo I really see a value but a quickstart is really meant to show a base / clean state of a "real" app and being able to configure (through an UI) a push config is not really part of that IMO. > > > > > > > > > Should not the client be the same no matter have backend is set up? > > > > > > > > > > > > > > > The idea would be to keep them simple and straightforward as well, > e.g. > > > for > > > > iOS that means plain usage of NSURLConnection / NSURLSession. But > for the > > > > "push registration" of the client, > > > > the iOS-push SDK would be used (same/similar would apply to Cordova > or > > > > Android). Similar to the above 'Hello World', the quickstarts are > going > > > to > > > > be focused only on Push functionality, so for these we would leave > out > > > > pipes and such until later versions. > > > > > > > > > > > > I will be creating Epics and subtasks in JIRA for this. > > > > > > > > For the location of all these projects, I had this "uber repo" > location > > > in > > > > mind: > > > > * https://github.com/aerogear/aerogear-push-helloworld > > > > * https://github.com/aerogear/aerogear-push-quickstarts > > > > > > > > Greetings, > > > > Matthias > > > > > > > > > > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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/20140331/784c80cf/attachment-0001.html From matzew at apache.org Mon Mar 31 11:08:13 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 17:08:13 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: <20140331170312.6132bc84@kapy-ntb-x220> References: <20140331163916.5ed8d732@kapy-ntb-x220> <20140331170312.6132bc84@kapy-ntb-x220> Message-ID: On Mon, Mar 31, 2014 at 5:03 PM, Karel Piwko wrote: > On Mon, 31 Mar 2014 16:41:09 +0200 > Matthias Wessendorf wrote: > > > On Mon, Mar 31, 2014 at 4:39 PM, Karel Piwko wrote: > > > > > On Mon, 31 Mar 2014 15:25:41 +0200 > > > Matthias Wessendorf wrote: > > > > > > > Hello there, > > > > > > > > we recently had talks about creating some simplified quickstarts and > > > > hello-word demos, related to the UnifiedPush Server and JBoss AS > > > developers: > > > > > > > > * Hello World (No Server Code - just client receiving push, no fancy > > > > (complex) UI on the client, nor integrated into a Cookbook or > something > > > > that has "dependencies") > > > > ** Cordova > > > > ** Android > > > > > > > > For iOS that is already there: > > > > https://github.com/aerogear/aerogear-push-ios-demo > > > > > > > > Yes, just usage of the "Push Registration SDKs", is the goal here: > keep > > > it > > > > simple, since native push can be a complicated use-case all on its > own > > > and > > > > so it will be good to make sure we cover the basics here. > > > > > > > > > > > > Beyond the Hello-World, we wanted some different quickstarts. The > > > "server" > > > > components that come to mind would be: > > > > > > > > *Secured CRUD + Push Integration (Java Sender) > > > > ** JAX-RS + PicketLink > > > > ** SpringMVC/Spring Security > > > > ** JAX-RS + Apache Camel > > > > > > > > These need to function on both JBoss AS 7.X and EAP. > > > > > > > > Josh, from the JDF team, has already said he wants to help on the > server > > > > projects (especially the JAX-RS/PL and Spring ones). yay! > > > > Note: Josh already has a simple backend started that is used in JDF > > > > quickstarts that would be good to re-use to make it easier for > developers > > > > to transition from one to other. > > > > > > > > > > > > The goal would be the SERVER acts same to outside (identical REST > > > > endpoints, difference is only an impl. detail (e.g. JavaEE vs. > Spring vs. > > > > Camel)) > > > > > > > > For these different servers, there would be mobile apps needed: > > > > * Android > > > > * Cordova > > > > * iOS > > > > > > I'm not sure if I got that. You mean extra 3 apps per each supported > > > backed? > > > Making it 9 additional apps to test and maintain? > > > > > > > > > No: total of 3 server apps and 3 client apps > > That's a weight off my shoulders :-) > > What do you guys feel of these quickstarts having additional registration > button? E.g. it should be possible to provide UPS username/pass/variant > name, > and get variantId/secret dynamically via REST, so not hardcoded in app. You > could then use one app to (re)connect to different UPS instances without > redeploy. Once registered via button, variantId/secret could go into > offline > storage. > > Something similar to > > https://github.com/TadeasKriz/aerogear-push-test-android/blob/master/src/org/jboss/aerogear/pushtest/activity/RegistrationActivity.java#L57 > I'm not sure if it's good for a quickstart but it should be valuable for a > demo. > > sure, we can certainly do that. AeroDoc's 'issue' :-) is it has the cfg inside of the code. Once we get to hack on these clients, let's worry about details, but yes - certainly a valid point -M > > > > > > > > Should not the client be the same no matter have backend is set up? > > > > > > > > > > > > > > > The idea would be to keep them simple and straightforward as well, > e.g. > > > for > > > > iOS that means plain usage of NSURLConnection / NSURLSession. But > for the > > > > "push registration" of the client, > > > > the iOS-push SDK would be used (same/similar would apply to Cordova > or > > > > Android). Similar to the above 'Hello World', the quickstarts are > going > > > to > > > > be focused only on Push functionality, so for these we would leave > out > > > > pipes and such until later versions. > > > > > > > > > > > > I will be creating Epics and subtasks in JIRA for this. > > > > > > > > For the location of all these projects, I had this "uber repo" > location > > > in > > > > mind: > > > > * https://github.com/aerogear/aerogear-push-helloworld > > > > * https://github.com/aerogear/aerogear-push-quickstarts > > > > > > > > Greetings, > > > > Matthias > > > > > > > > > > > > > > > > > > _______________________________________________ > > > aerogear-dev mailing list > > > aerogear-dev at lists.jboss.org > > > https://lists.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/20140331/be480962/attachment.html From matzew at apache.org Mon Mar 31 11:09:14 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 17:09:14 +0200 Subject: [aerogear-dev] Modularization and Push In-Reply-To: <20140331170703.7e719f86@kapy-ntb-x220> References: <533974A1.1020406@redhat.com> <20140331170703.7e719f86@kapy-ntb-x220> Message-ID: On Mon, Mar 31, 2014 at 5:07 PM, Karel Piwko wrote: > I'd prefer a) unless you plan to regularly release milestones of b) into > Maven > Central. Relying on snapshots in demos and tests is a PITA. of course there will be an "android-push.jar" (library) on maven central > And this looks like > a lot of effort, so branch might be living its own life for a very long > time. > > Karel > > On Mon, 31 Mar 2014 09:58:57 -0400 > Summers Pittman wrote: > > > Y'all, > > > > So there has been some concerns with the complexity of the build > > especially where including the Google GCM (push) libraries are > > concerned. Additionally there have been some requests for a separate > > "push" module which won't need the full aerogear android library. > > > > The full modularization of the library along with several other > > improvements is scheduled for the "2.0" epic. > > > > So my question is a) Should we make a 2.0 which is only the > > modularization sooner and iterate on that a few times before we include > > our improvements in a 3.0 or b) Should we create a "fork" project which > > is only a push module? This new project will get merged back into the > > main project when we have our complete modularizations. > > > > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.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/20140331/57d94f39/attachment.html From scm.blanc at gmail.com Mon Mar 31 11:12:49 2014 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 31 Mar 2014 17:12:49 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: References: <20140331163916.5ed8d732@kapy-ntb-x220> <20140331170312.6132bc84@kapy-ntb-x220> Message-ID: On Mon, Mar 31, 2014 at 5:08 PM, Matthias Wessendorf wrote: > > > > On Mon, Mar 31, 2014 at 5:03 PM, Karel Piwko wrote: > >> On Mon, 31 Mar 2014 16:41:09 +0200 >> Matthias Wessendorf wrote: >> >> > On Mon, Mar 31, 2014 at 4:39 PM, Karel Piwko wrote: >> > >> > > On Mon, 31 Mar 2014 15:25:41 +0200 >> > > Matthias Wessendorf wrote: >> > > >> > > > Hello there, >> > > > >> > > > we recently had talks about creating some simplified quickstarts and >> > > > hello-word demos, related to the UnifiedPush Server and JBoss AS >> > > developers: >> > > > >> > > > * Hello World (No Server Code - just client receiving push, no fancy >> > > > (complex) UI on the client, nor integrated into a Cookbook or >> something >> > > > that has "dependencies") >> > > > ** Cordova >> > > > ** Android >> > > > >> > > > For iOS that is already there: >> > > > https://github.com/aerogear/aerogear-push-ios-demo >> > > > >> > > > Yes, just usage of the "Push Registration SDKs", is the goal here: >> keep >> > > it >> > > > simple, since native push can be a complicated use-case all on its >> own >> > > and >> > > > so it will be good to make sure we cover the basics here. >> > > > >> > > > >> > > > Beyond the Hello-World, we wanted some different quickstarts. The >> > > "server" >> > > > components that come to mind would be: >> > > > >> > > > *Secured CRUD + Push Integration (Java Sender) >> > > > ** JAX-RS + PicketLink >> > > > ** SpringMVC/Spring Security >> > > > ** JAX-RS + Apache Camel >> > > > >> > > > These need to function on both JBoss AS 7.X and EAP. >> > > > >> > > > Josh, from the JDF team, has already said he wants to help on the >> server >> > > > projects (especially the JAX-RS/PL and Spring ones). yay! >> > > > Note: Josh already has a simple backend started that is used in JDF >> > > > quickstarts that would be good to re-use to make it easier for >> developers >> > > > to transition from one to other. >> > > > >> > > > >> > > > The goal would be the SERVER acts same to outside (identical REST >> > > > endpoints, difference is only an impl. detail (e.g. JavaEE vs. >> Spring vs. >> > > > Camel)) >> > > > >> > > > For these different servers, there would be mobile apps needed: >> > > > * Android >> > > > * Cordova >> > > > * iOS >> > > >> > > I'm not sure if I got that. You mean extra 3 apps per each supported >> > > backed? >> > > Making it 9 additional apps to test and maintain? >> > > >> > >> > >> > No: total of 3 server apps and 3 client apps >> >> That's a weight off my shoulders :-) >> >> What do you guys feel of these quickstarts having additional registration >> button? E.g. it should be possible to provide UPS username/pass/variant >> name, >> and get variantId/secret dynamically via REST, so not hardcoded in app. >> You >> could then use one app to (re)connect to different UPS instances without >> redeploy. Once registered via button, variantId/secret could go into >> offline >> storage. >> >> Something similar to >> >> https://github.com/TadeasKriz/aerogear-push-test-android/blob/master/src/org/jboss/aerogear/pushtest/activity/RegistrationActivity.java#L57 >> I'm not sure if it's good for a quickstart but it should be valuable for >> a demo. >> >> > sure, we can certainly do that. > AeroDoc's 'issue' :-) is it has the cfg inside of the code. > Yes but for AeroDoc , that was only present in the backend (which make sense) and not the clients. But that make me think that it should be configurable in the server bits. > > Once we get to hack on these clients, let's worry about details, but yes - > certainly a valid point > > > -M > > > > >> >> > >> > >> > > Should not the client be the same no matter have backend is set up? >> > > >> > > > >> > > > >> > > > The idea would be to keep them simple and straightforward as well, >> e.g. >> > > for >> > > > iOS that means plain usage of NSURLConnection / NSURLSession. But >> for the >> > > > "push registration" of the client, >> > > > the iOS-push SDK would be used (same/similar would apply to Cordova >> or >> > > > Android). Similar to the above 'Hello World', the quickstarts are >> going >> > > to >> > > > be focused only on Push functionality, so for these we would leave >> out >> > > > pipes and such until later versions. >> > > > >> > > > >> > > > I will be creating Epics and subtasks in JIRA for this. >> > > > >> > > > For the location of all these projects, I had this "uber repo" >> location >> > > in >> > > > mind: >> > > > * https://github.com/aerogear/aerogear-push-helloworld >> > > > * https://github.com/aerogear/aerogear-push-quickstarts >> > > > >> > > > Greetings, >> > > > Matthias >> > > > >> > > > >> > > > >> > > >> > > _______________________________________________ >> > > aerogear-dev mailing list >> > > aerogear-dev at lists.jboss.org >> > > https://lists.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/20140331/02b586a8/attachment-0001.html From kpiwko at redhat.com Mon Mar 31 11:38:24 2014 From: kpiwko at redhat.com (Karel Piwko) Date: Mon, 31 Mar 2014 17:38:24 +0200 Subject: [aerogear-dev] Modularization and Push In-Reply-To: References: <533974A1.1020406@redhat.com> <20140331170703.7e719f86@kapy-ntb-x220> Message-ID: <20140331173824.26658c37@kapy-ntb-x220> On Mon, 31 Mar 2014 17:09:14 +0200 Matthias Wessendorf wrote: > On Mon, Mar 31, 2014 at 5:07 PM, Karel Piwko wrote: > > > I'd prefer a) unless you plan to regularly release milestones of b) into > > Maven > > Central. Relying on snapshots in demos and tests is a PITA. > > > of course there will be an "android-push.jar" (library) on maven central So the original question can be translated to: "Should we continue developing in master or in a feature branch?" > > > > > And this looks like > > a lot of effort, so branch might be living its own life for a very long > > time. > > > > Karel > > > > On Mon, 31 Mar 2014 09:58:57 -0400 > > Summers Pittman wrote: > > > > > Y'all, > > > > > > So there has been some concerns with the complexity of the build > > > especially where including the Google GCM (push) libraries are > > > concerned. Additionally there have been some requests for a separate > > > "push" module which won't need the full aerogear android library. > > > > > > The full modularization of the library along with several other > > > improvements is scheduled for the "2.0" epic. > > > > > > So my question is a) Should we make a 2.0 which is only the > > > modularization sooner and iterate on that a few times before we include > > > our improvements in a 3.0 or b) Should we create a "fork" project which > > > is only a push module? This new project will get merged back into the > > > main project when we have our complete modularizations. > > > > > > > > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > From hbons at redhat.com Mon Mar 31 11:53:43 2014 From: hbons at redhat.com (Hylke Bons) Date: Mon, 31 Mar 2014 16:53:43 +0100 Subject: [aerogear-dev] Modularization and Push In-Reply-To: <533974A1.1020406@redhat.com> References: <533974A1.1020406@redhat.com> Message-ID: <53398F87.8060205@redhat.com> Not that I can help, but just wanted to say this is good news! Other than being more modular it makes the project as a while easier to understand and present. :) Hylke On 31/03/2014 14:58, Summers Pittman wrote: > Y'all, > > So there has been some concerns with the complexity of the build > especially where including the Google GCM (push) libraries are > concerned. Additionally there have been some requests for a separate > "push" module which won't need the full aerogear android library. > > The full modularization of the library along with several other > improvements is scheduled for the "2.0" epic. > > So my question is a) Should we make a 2.0 which is only the > modularization sooner and iterate on that a few times before we include > our improvements in a 3.0 or b) Should we create a "fork" project which > is only a push module? This new project will get merged back into the > main project when we have our complete modularizations. > > > From supittma at redhat.com Mon Mar 31 12:10:07 2014 From: supittma at redhat.com (Summers Pittman) Date: Mon, 31 Mar 2014 12:10:07 -0400 Subject: [aerogear-dev] Modularization and Push In-Reply-To: <20140331173824.26658c37@kapy-ntb-x220> References: <533974A1.1020406@redhat.com> <20140331170703.7e719f86@kapy-ntb-x220> <20140331173824.26658c37@kapy-ntb-x220> Message-ID: <5339935F.4010008@redhat.com> On 03/31/2014 11:38 AM, Karel Piwko wrote: > On Mon, 31 Mar 2014 17:09:14 +0200 > Matthias Wessendorf wrote: > >> On Mon, Mar 31, 2014 at 5:07 PM, Karel Piwko wrote: >> >>> I'd prefer a) unless you plan to regularly release milestones of b) into >>> Maven >>> Central. Relying on snapshots in demos and tests is a PITA. >> >> of course there will be an "android-push.jar" (library) on maven central > So the original question can be translated to: "Should we continue developing in > master or in a feature branch?" The plan as I see it (and passos can correct me) is that we would keep aerogear-android as it is and create a "forked" project which is only aerogear-android-gcm-push and the bits it needs with no dependency on aerogear-android. This MAY be a jar but will probably be an apklib and aar artifact. We (android) don't want to modularize the whole project right now because that will be a lot of work to maintain 1.x compatibility for semver and we aren't ready to build 2.0 yet. > >> >> >>> And this looks like >>> a lot of effort, so branch might be living its own life for a very long >>> time. >>> >>> Karel >>> >>> On Mon, 31 Mar 2014 09:58:57 -0400 >>> Summers Pittman wrote: >>> >>>> Y'all, >>>> >>>> So there has been some concerns with the complexity of the build >>>> especially where including the Google GCM (push) libraries are >>>> concerned. Additionally there have been some requests for a separate >>>> "push" module which won't need the full aerogear android library. >>>> >>>> The full modularization of the library along with several other >>>> improvements is scheduled for the "2.0" epic. >>>> >>>> So my question is a) Should we make a 2.0 which is only the >>>> modularization sooner and iterate on that a few times before we include >>>> our improvements in a 3.0 or b) Should we create a "fork" project which >>>> is only a push module? This new project will get merged back into the >>>> main project when we have our complete modularizations. >>>> >>>> >>>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.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 bruno at abstractj.org Mon Mar 31 13:45:08 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 31 Mar 2014 14:45:08 -0300 Subject: [aerogear-dev] Passphrase encryption and clients Message-ID: Good morning, I?ve updated the idea here?https://gist.github.com/abstractj/ef1e3d53619796f4e87e Would you like to hear some feedback/questions. Thanks in advance. -- abstractj From bruno at abstractj.org Mon Mar 31 13:51:34 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 31 Mar 2014 14:51:34 -0300 Subject: [aerogear-dev] Modularization and Push In-Reply-To: <533974A1.1020406@redhat.com> References: <533974A1.1020406@redhat.com> Message-ID: I would vote for A -- abstractj On March 31, 2014 at 10:59:01 AM, Summers Pittman (supittma at redhat.com) wrote: > > Y'all, > > So there has been some concerns with the complexity of the build > especially where including the Google GCM (push) libraries > are > concerned. Additionally there have been some requests for a > separate > "push" module which won't need the full aerogear android library. > > The full modularization of the library along with several other > improvements is scheduled for the "2.0" epic. > > So my question is a) Should we make a 2.0 which is only the > modularization sooner and iterate on that a few times before > we include > our improvements in a 3.0 or b) Should we create a "fork" project > which > is only a push module? This new project will get merged back into > the > main project when we have our complete modularizations. From lholmqui at redhat.com Mon Mar 31 13:51:59 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 31 Mar 2014 13:51:59 -0400 Subject: [aerogear-dev] Passphrase encryption and clients In-Reply-To: References: Message-ID: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> wasn't sure where to put the question, so i'll do it here so are you asking if our "sender" clients should also do registration of apps/variants too? well, since the sender clients are just really replacing curl, then that would probably work On Mar 31, 2014, at 1:45 PM, Bruno Oliveira wrote: > Good morning, I?ve updated the idea here https://gist.github.com/abstractj/ef1e3d53619796f4e87e > > Would you like to hear some feedback/questions. > > Thanks in advance. > > -- > abstractj > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From bruno at abstractj.org Mon Mar 31 13:54:29 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 31 Mar 2014 14:54:29 -0300 Subject: [aerogear-dev] Passphrase encryption and clients In-Reply-To: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> References: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> Message-ID: Feel free to post your questions here, sorry about that. My question is: Should the sender implement certificate upload as a feature? -- abstractj On March 31, 2014 at 2:52:05 PM, Lucas Holmquist (lholmqui at redhat.com) wrote: > > wasn't sure where to put the question, so i'll do it here > > > so are you asking if our "sender" clients should also do registration > of apps/variants too? > > well, since the sender clients are just really replacing curl, > then that would probably work From lholmqui at redhat.com Mon Mar 31 13:58:26 2014 From: lholmqui at redhat.com (Lucas Holmquist) Date: Mon, 31 Mar 2014 13:58:26 -0400 Subject: [aerogear-dev] Passphrase encryption and clients In-Reply-To: References: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> Message-ID: <07B77A9A-4509-44DD-A13C-A158E65E344E@redhat.com> On Mar 31, 2014, at 1:54 PM, Bruno Oliveira wrote: > Feel free to post your questions here, sorry about that. > > My question is: Should the sender implement certificate upload as a feature? just thinking about this from a node.js perspective, i could be persuaded either way, although i think i lean toward client registration as being a separate module > > -- > abstractj > > On March 31, 2014 at 2:52:05 PM, Lucas Holmquist (lholmqui at redhat.com) wrote: >>> wasn't sure where to put the question, so i'll do it here >> >> >> so are you asking if our "sender" clients should also do registration >> of apps/variants too? >> >> well, since the sender clients are just really replacing curl, >> then that would probably work > From miguel21op at gmail.com Mon Mar 31 14:03:42 2014 From: miguel21op at gmail.com (Miiguel Lemos) Date: Mon, 31 Mar 2014 19:03:42 +0100 Subject: [aerogear-dev] Modularization and Push In-Reply-To: References: <533974A1.1020406@redhat.com> Message-ID: <45CFD6B3-70E6-421F-A5F5-1FEB5CC7B2A0@gmail.com> Using the GCM for push notifications has a very important advantage: it minimizes the battery consumption, since it reduces the processor overload, it's not needed to open a socket to check the server on a regular basis, etc. In my opinion this a critical matter, minimizing the probability of the user turning the notifications off. Enviado do meu iPad No dia 31/03/2014, ?s 18:51, Bruno Oliveira escreveu: > I would vote for A > > -- > abstractj > > On March 31, 2014 at 10:59:01 AM, Summers Pittman (supittma at redhat.com) wrote: >>> Y'all, >> >> So there has been some concerns with the complexity of the build >> especially where including the Google GCM (push) libraries >> are >> concerned. Additionally there have been some requests for a >> separate >> "push" module which won't need the full aerogear android library. >> >> The full modularization of the library along with several other >> improvements is scheduled for the "2.0" epic. >> >> So my question is a) Should we make a 2.0 which is only the >> modularization sooner and iterate on that a few times before >> we include >> our improvements in a 3.0 or b) Should we create a "fork" project >> which >> is only a push module? This new project will get merged back into >> the >> main project when we have our complete modularizations. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From bruno at abstractj.org Mon Mar 31 14:04:19 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 31 Mar 2014 15:04:19 -0300 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: <20140331170312.6132bc84@kapy-ntb-x220> References: <20140331163916.5ed8d732@kapy-ntb-x220> <20140331170312.6132bc84@kapy-ntb-x220> Message-ID: Not sure if I follow the idea, but if I have variantId/secret could I reconnect in different UPS instances? Maybe due to my lack of understanding I?m not following it, but IMO variant ID, secret, sender ID should never be exposed. But I can be wrong. -- abstractj On March 31, 2014 at 12:03:20 PM, Karel Piwko (kpiwko at redhat.com) wrote: > > That's a weight off my shoulders :-) > > What do you guys feel of these quickstarts having additional > registration > button? E.g. it should be possible to provide UPS username/pass/variant > name, > and get variantId/secret dynamically via REST, so not hardcoded > in app. You > could then use one app to (re)connect to different UPS instances > without > redeploy. Once registered via button, variantId/secret could > go into offline > storage. From matzew at apache.org Mon Mar 31 14:13:37 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 20:13:37 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: References: <20140331163916.5ed8d732@kapy-ntb-x220> <20140331170312.6132bc84@kapy-ntb-x220> Message-ID: On Monday, March 31, 2014, Bruno Oliveira wrote: > Not sure if I follow the idea, but if I have variantId/secret could I > reconnect in different UPS instances? Maybe due to my lack of understanding > I'm not following it, but IMO variant ID, secret, sender ID should never be > exposed. > > But I can be wrong. Well, thats what a device needs to register w/ the UPS > > -- > abstractj > > On March 31, 2014 at 12:03:20 PM, Karel Piwko (kpiwko at redhat.com) > wrote: > > > That's a weight off my shoulders :-) > > > > What do you guys feel of these quickstarts having additional > > registration > > button? E.g. it should be possible to provide UPS username/pass/variant > > name, > > and get variantId/secret dynamically via REST, so not hardcoded > > in app. You > > could then use one app to (re)connect to different UPS instances > > without > > redeploy. Once registered via button, variantId/secret could > > go into offline > > storage. > > > _______________________________________________ > 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/20140331/747371ca/attachment.html From matzew at apache.org Mon Mar 31 14:14:32 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 20:14:32 +0200 Subject: [aerogear-dev] Passphrase encryption and clients In-Reply-To: References: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> Message-ID: On Monday, March 31, 2014, Bruno Oliveira wrote: > Feel free to post your questions here, sorry about that. > > My question is: Should the sender implement certificate upload as a > feature? Nope > > -- > abstractj > > On March 31, 2014 at 2:52:05 PM, Lucas Holmquist (lholmqui at redhat.com) > wrote: > > > wasn't sure where to put the question, so i'll do it here > > > > > > so are you asking if our "sender" clients should also do registration > > of apps/variants too? > > > > well, since the sender clients are just really replacing curl, > > then that would probably work > > _______________________________________________ > 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/20140331/b6b309dc/attachment.html From matzew at apache.org Mon Mar 31 14:16:39 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 20:16:39 +0200 Subject: [aerogear-dev] Passphrase encryption and clients In-Reply-To: References: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> Message-ID: C? On Monday, March 31, 2014, Matthias Wessendorf wrote: > > > On Monday, March 31, 2014, Bruno Oliveira > > wrote: > >> Feel free to post your questions here, sorry about that. >> >> My question is: Should the sender implement certificate upload as a >> feature? > > > Nope > The certificate should be only provided when creating the actual iOS variant (e.g inside the AdminUI - or its REST APIs) > > > >> >> -- >> abstractj >> >> On March 31, 2014 at 2:52:05 PM, Lucas Holmquist (lholmqui at redhat.com) >> wrote: >> > > wasn't sure where to put the question, so i'll do it here >> > >> > >> > so are you asking if our "sender" clients should also do registration >> > of apps/variants too? >> > >> > well, since the sender clients are just really replacing curl, >> > then that would probably work >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > -- > Sent from Gmail Mobile > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140331/a857eb3d/attachment.html From bruno at abstractj.org Mon Mar 31 14:40:53 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 31 Mar 2014 15:40:53 -0300 Subject: [aerogear-dev] Passphrase encryption and clients In-Reply-To: References: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> Message-ID: So I think we reached a dead end. If you want passphrase encryption, and they must be reversible because Apple requires it. How your workflow would look like? 1. Login 2. Register an application 3. Make use of our client to encrypt passphrase/certificate 4. Use cURL to upload the encrypted data ???? >From the developers perspective I would never use that.? If the certificate should be only provided when creating the variant inside Admin UI, you don?t need a client like discussed here (https://issues.jboss.org/browse/AGPUSH-561). Why would I need a client to encrypt files and require cURL to upload it? -- abstractj On March 31, 2014 at 3:16:47 PM, Matthias Wessendorf (matzew at apache.org) wrote: > > C? > > On Monday, March 31, 2014(http://airmail.calendar/2014-03-31%2012:00:00%20GMT-3), > Matthias Wessendorf > wrote: > > > > > > On Monday, March 31, 2014(http://airmail.calendar/2014-03-31%2012:00:00%20GMT-3), > Bruno Oliveira > wrote: > > > Feel free to post your questions here, sorry about that. > > > > > > My question is: Should the sender implement certificate upload > as a feature? > > > > Nope > > > The certificate should be only provided when creating the actual > iOS variant (e.g inside the AdminUI - or its REST APIs) From bruno at abstractj.org Mon Mar 31 14:42:16 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 31 Mar 2014 15:42:16 -0300 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: References: <20140331163916.5ed8d732@kapy-ntb-x220> <20140331170312.6132bc84@kapy-ntb-x220> Message-ID: Behind the scenes, right? -- abstractj On March 31, 2014 at 3:13:45 PM, Matthias Wessendorf (matzew at apache.org) wrote: > > Well, thats what a device needs to register w/ the UPS From matzew at apache.org Mon Mar 31 15:16:55 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 21:16:55 +0200 Subject: [aerogear-dev] Passphrase encryption and clients In-Reply-To: References: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> Message-ID: Perhaps we never really talked about the same? Regarding usability, providing the Apple certificate for every sending to APNs would be really odd for my point of view ;) Anyways, I'd suggest we do a hangout tomorrow to discuss this. I will share a detailed write-up of our chat. Sounds good? On Monday, March 31, 2014, Bruno Oliveira wrote: > So I think we reached a dead end. If you want passphrase encryption, and > they must be reversible because Apple requires it. How your workflow would > look like? > > 1. Login > 2. Register an application > 3. Make use of our client to encrypt passphrase/certificate > 4. Use cURL to upload the encrypted data > > ???? > > From the developers perspective I would never use that. > > If the certificate should be only provided when creating the variant > inside Admin UI, you don't need a client like discussed here ( > https://issues.jboss.org/browse/AGPUSH-561). Why would I need a client to > encrypt files and require cURL to upload it? > > -- > abstractj > > On March 31, 2014 at 3:16:47 PM, Matthias Wessendorf (matzew at apache.org) > wrote: > > > C? > > > > On Monday, March 31, 2014( > http://airmail.calendar/2014-03-31%2012:00:00%20GMT-3), > > Matthias Wessendorf > > wrote: > > > > > > > > > On Monday, March 31, 2014( > http://airmail.calendar/2014-03-31%2012:00:00%20GMT-3), > > Bruno Oliveira > > wrote: > > > > Feel free to post your questions here, sorry about that. > > > > > > > > My question is: Should the sender implement certificate upload > > as a feature? > > > > > > Nope > > > > > > The certificate should be only provided when creating the actual > > iOS variant (e.g inside the AdminUI - or its REST APIs) > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140331/cb61b236/attachment-0001.html From scm.blanc at gmail.com Mon Mar 31 15:32:35 2014 From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=) Date: Mon, 31 Mar 2014 21:32:35 +0200 Subject: [aerogear-dev] UnifiedPush Server: Hello World- and Quickstart Examples In-Reply-To: References: <20140331163916.5ed8d732@kapy-ntb-x220> <20140331170312.6132bc84@kapy-ntb-x220> Message-ID: <1A0FC2DE-5110-4915-A989-7AFFA3F05D32@gmail.com> Yep Envoy? de mon iPhone > Le 31 mars 2014 ? 20:42, Bruno Oliveira a ?crit : > > Behind the scenes, right? > > -- > abstractj > > On March 31, 2014 at 3:13:45 PM, Matthias Wessendorf (matzew at apache.org) wrote: >>> Well, thats what a device needs to register w/ the UPS > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev From bruno at abstractj.org Mon Mar 31 15:39:18 2014 From: bruno at abstractj.org (Bruno Oliveira) Date: Mon, 31 Mar 2014 16:39:18 -0300 Subject: [aerogear-dev] Passphrase encryption and clients In-Reply-To: References: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> Message-ID: All good, sometimes security and usability never match. That?s the reason why I?m asking before. -- abstractj On March 31, 2014 at 4:16:56 PM, Matthias Wessendorf (matzew at apache.org) wrote: > > Perhaps we never really talked about the same? > > Regarding usability, providing the Apple certificate for every > sending to APNs would be really odd for my point of view ;) > > Anyways, I'd suggest we do a hangout tomorrow to discuss this. > I will share a detailed write-up of our chat. > > Sounds good? From matzew at apache.org Mon Mar 31 16:14:58 2014 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 31 Mar 2014 22:14:58 +0200 Subject: [aerogear-dev] Passphrase encryption and clients In-Reply-To: References: <1D451839-8F08-4C3B-942A-E39D46E160E3@redhat.com> Message-ID: Ok, Lets chat tomorrow. Good night! On Monday, March 31, 2014, Bruno Oliveira wrote: > All good, sometimes security and usability never match. That's the reason > why I'm asking before. > > -- > abstractj > > On March 31, 2014 at 4:16:56 PM, Matthias Wessendorf (matzew at apache.org) > wrote: > > > Perhaps we never really talked about the same? > > > > Regarding usability, providing the Apple certificate for every > > sending to APNs would be really odd for my point of view ;) > > > > Anyways, I'd suggest we do a hangout tomorrow to discuss this. > > I will share a detailed write-up of our chat. > > > > Sounds good? > > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140331/328aea92/attachment.html