From matzew at apache.org Tue Mar 7 06:36:07 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Mar 2017 12:36:07 +0100 Subject: [aerogear-dev] Maria/MySQL Galera Message-ID: Hi, I am experimenting w/ a HA DB, using Galera. I've found this docker-compose setup pretty good, so far: https://gist.github.com/matzew/136ee9054eb2863ca81a84feb871eb61 Wondering, do others here have experience w/ this setup ? Greetings, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170307/1f822ebb/attachment.html From matzew at apache.org Tue Mar 7 10:38:48 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 7 Mar 2017 16:38:48 +0100 Subject: [aerogear-dev] Maria/MySQL Galera In-Reply-To: References: Message-ID: I think i will PR this to our docker / db folder, on master On Tue, Mar 7, 2017 at 12:36 PM, Matthias Wessendorf wrote: > Hi, > > I am experimenting w/ a HA DB, using Galera. I've found this > docker-compose setup pretty good, so far: > https://gist.github.com/matzew/136ee9054eb2863ca81a84feb871eb61 > > Wondering, do others here have experience w/ this setup ? > > Greetings, > Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170307/ab420749/attachment.html From jgallaso at redhat.com Thu Mar 16 11:00:17 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Thu, 16 Mar 2017 16:00:17 +0100 Subject: [aerogear-dev] Cannot Set Up Admin UI Dev Environment Message-ID: Hi, I am trying to solve a bug in the push's admin-ui but I am not able to setup the dev environment. Anyone would help me a bit with this? So far I have all dependencies installed plus grunt, I have deployed my eap-6 and I have edited the local-config.json like this: { "home": "/home/jgallaso/projects/aerogear/aerogear-unifiedpush-server/admin-ui", "jbossweb": "/home/jgallaso/projects/eap-6.4/standalone/deployments/ag-push.war" } But I am getting an error when runnin ?g? grunt initLocalConfig ?$ ? grunt initLocalConfig >> Local Npm module "grunt-cli" not found. Is it installed? Running "initLocalConfig" task Fatal error: jbossweb directory /home/jgallaso/projects/eap-6.4/standalone/deployments/ag-push.war configured in ./local-config.json is not directory (must be exploded WAR) ?Thanks in advance and cheers,? -- *Jose Miguel Gallas Olmedo* Associate QE at Mobile Team, *Red Hat* +34 618 488 633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170316/564e573e/attachment-0001.html From lholmqui at redhat.com Thu Mar 16 14:35:51 2017 From: lholmqui at redhat.com (Luke Holmquist) Date: Thu, 16 Mar 2017 14:35:51 -0400 Subject: [aerogear-dev] Cannot Set Up Admin UI Dev Environment In-Reply-To: References: Message-ID: is that ag-push.war actually a directory, or is it the archive version. On Thu, Mar 16, 2017 at 11:00 AM, Jose Miguel Gallas Olmedo < jgallaso at redhat.com> wrote: > Hi, > > I am trying to solve a bug in the push's admin-ui but I am not able to > setup the dev environment. Anyone would help me a bit with this? > > So far I have all dependencies installed plus grunt, I have deployed my > eap-6 and I have edited the local-config.json like this: > > { > "home": "/home/jgallaso/projects/aerogear/aerogear-unifiedpush- > server/admin-ui", > "jbossweb": "/home/jgallaso/projects/eap- > 6.4/standalone/deployments/ag-push.war" > } > > > But I am getting an error when runnin > ?g? > grunt initLocalConfig > > ?$ ? > grunt initLocalConfig > >> Local Npm module "grunt-cli" not found. Is it installed? > > Running "initLocalConfig" task > Fatal error: jbossweb directory /home/jgallaso/projects/eap-6. > 4/standalone/deployments/ag-push.war configured in ./local-config.json is > not directory (must be exploded WAR) > > > ?Thanks in advance and cheers,? > > -- > *Jose Miguel Gallas Olmedo* > Associate QE at Mobile Team, *Red Hat* > > +34 618 488 633 <+34%20618%2048%2086%2033> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170316/eb88d3d5/attachment.html From jgallaso at redhat.com Fri Mar 17 04:14:06 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Fri, 17 Mar 2017 09:14:06 +0100 Subject: [aerogear-dev] Cannot Set Up Admin UI Dev Environment In-Reply-To: References:

Message-ID: Not a directory but an archive. On 16 March 2017 at 19:35, Luke Holmquist wrote: > is that ag-push.war actually a directory, or is it the archive version. > > > > > > On Thu, Mar 16, 2017 at 11:00 AM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> Hi, >> >> I am trying to solve a bug in the push's admin-ui but I am not able to >> setup the dev environment. Anyone would help me a bit with this? >> >> So far I have all dependencies installed plus grunt, I have deployed my >> eap-6 and I have edited the local-config.json like this: >> >> { >> "home": "/home/jgallaso/projects/aerogear/aerogear-unifiedpush-serve >> r/admin-ui", >> "jbossweb": "/home/jgallaso/projects/eap-6 >> .4/standalone/deployments/ag-push.war" >> } >> >> >> But I am getting an error when runnin >> ?g? >> grunt initLocalConfig >> >> ?$ ? >> grunt initLocalConfig >> >> Local Npm module "grunt-cli" not found. Is it installed? >> >> Running "initLocalConfig" task >> Fatal error: jbossweb directory /home/jgallaso/projects/eap-6. >> 4/standalone/deployments/ag-push.war configured in ./local-config.json >> is not directory (must be exploded WAR) >> >> >> ?Thanks in advance and cheers,? >> >> -- >> *Jose Miguel Gallas Olmedo* >> Associate QE at Mobile Team, *Red Hat* >> >> +34 618 488 633 <+34%20618%2048%2086%2033> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- *Jose Miguel Gallas Olmedo* Associate QE at Mobile Team, *Red Hat* +34 618 488 633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170317/d7887b02/attachment.html From jgallaso at redhat.com Fri Mar 17 05:40:55 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Fri, 17 Mar 2017 10:40:55 +0100 Subject: [aerogear-dev] ups admin ui In-Reply-To: References:

Message-ID: A bit late but I agree 100% with the idea of having the admin-ui as a separate project. Frontend and backend should never be the same piece, specially when nowadays we have so many good frameworks available for web. On 2 February 2017 at 17:11, Luke Holmquist wrote: > > > On Thu, Feb 2, 2017 at 10:58 AM, Leonardo Rossetti > wrote: > >> WAR/JAR file would be for UPS deployment/build only, the repository >> itself would only contain frontend related files (being published in NPM as >> well). >> >> Did a quick search on NPM and found this package[1], is this the one? >> >> [1] - https://www.npmjs.com/package/unifiedpush-admin-client >> > that's not the one. i do believe that is being used though in your new > node-test-suite thing > >> >> On Thu, Feb 2, 2017 at 1:32 PM, Sebastien Blanc >> wrote: >> >>> >>> >>> On Thu, Feb 2, 2017 at 3:04 PM, Matthias Wessendorf >>> wrote: >>> >>>> >>>> >>>> On Thu, Feb 2, 2017 at 2:50 PM, Luke Holmquist >>>> wrote: >>>> >>>>> I believe the UI was in its own repo during the first iteration(when >>>>> it was ember :)) >>>>> >>>>> >>>> yep, and it was a PITA to integrate the pure JS files >>>> >>>> >>>>> >>>>> If we want to attract contributors from the JS community, then making >>>>> it a WAR is not really a great idea, >>>>> >>>> >>>> sure, but... how useful is the UI outside of the context of push? and, >>>> bundling w/ push... perhaps we release it as NPM, and include that, >>>> somehow, into a WAR? >>>> >>> I think we already publish it as NPM module for the integration with >>> RHMAP. >>> >>>> I see no other option for our deployment model >>>> >>>> >>>>> >>>>> >>>>> On Thu, Feb 2, 2017 at 8:01 AM, Matthias Wessendorf >>>> > wrote: >>>>> >>>>>> separate repo, not sure >>>>>> separate WAR file, I think at some point I want to have a bunch of >>>>>> different WAR files: >>>>>> * sender_API.war >>>>>> * registration_API.war >>>>>> * ui.war >>>>>> core.jar (EJB w/ the messaging, as core) >>>>>> >>>>>> but, that's a bit in the future... we have some Swarm related JIRAs >>>>>> for that >>>>>> >>>>>> On Thu, Feb 2, 2017 at 1:31 PM, Leonardo Rossetti < >>>>>> lrossett at redhat.com> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> Currently we have the UPS admin UI embedded into >>>>>>> aerogear-unifiedpush-server project/repository. >>>>>>> >>>>>>> Could the admin-ui be a separated project (repository) with its own >>>>>>> war file? >>>>>>> >>>>>>> While it may increase release process complexity (a new project >>>>>>> dependency), I think it brings some benefits to the table, such as having a >>>>>>> development cycle of this own, easier to write automated tests and easier >>>>>>> to attract contributors from the javascript community (since we would be >>>>>>> using common javascript tools to build it). >>>>>>> >>>>>>> WDYT? >>>>>>> >>>>>>> -- >>>>>>> Leonardo Rossetti >>>>>>> lrossett at redhat.com >>>>>>> +55 11 99703 0621 <+55%2011%2099703-0621> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> aerogear-dev mailing list >>>>>>> aerogear-dev at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matthias Wessendorf >>>>>> >>>>>> blog: http://matthiaswessendorf.wordpress.com/ >>>>>> twitter: http://twitter.com/mwessendorf >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> twitter: http://twitter.com/mwessendorf >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Leonardo Rossetti >> lrossett at redhat.com >> +55 11 99703 0621 <+55%2011%2099703-0621> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- *Jose Miguel Gallas Olmedo* Associate QE at Mobile Team, *Red Hat* +34 618 488 633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170317/e6260378/attachment-0001.html From lholmqui at redhat.com Fri Mar 17 09:13:14 2017 From: lholmqui at redhat.com (Luke Holmquist) Date: Fri, 17 Mar 2017 09:13:14 -0400 Subject: [aerogear-dev] Cannot Set Up Admin UI Dev Environment In-Reply-To: References:

Message-ID: it should be a directory, I think after the man build or whatever its called in maven, there should be an ag-push directory as well as an ag-push.war in the server/out or whatever its called, I'm going from memory here :) On Fri, Mar 17, 2017 at 4:14 AM, Jose Miguel Gallas Olmedo < jgallaso at redhat.com> wrote: > Not a directory but an archive. > > On 16 March 2017 at 19:35, Luke Holmquist wrote: > >> is that ag-push.war actually a directory, or is it the archive version. >> >> >> >> >> >> On Thu, Mar 16, 2017 at 11:00 AM, Jose Miguel Gallas Olmedo < >> jgallaso at redhat.com> wrote: >> >>> Hi, >>> >>> I am trying to solve a bug in the push's admin-ui but I am not able to >>> setup the dev environment. Anyone would help me a bit with this? >>> >>> So far I have all dependencies installed plus grunt, I have deployed my >>> eap-6 and I have edited the local-config.json like this: >>> >>> { >>> "home": "/home/jgallaso/projects/aerogear/aerogear-unifiedpush-serve >>> r/admin-ui", >>> "jbossweb": "/home/jgallaso/projects/eap-6 >>> .4/standalone/deployments/ag-push.war" >>> } >>> >>> >>> But I am getting an error when runnin >>> ?g? >>> grunt initLocalConfig >>> >>> ?$ ? >>> grunt initLocalConfig >>> >> Local Npm module "grunt-cli" not found. Is it installed? >>> >>> Running "initLocalConfig" task >>> Fatal error: jbossweb directory /home/jgallaso/projects/eap-6. >>> 4/standalone/deployments/ag-push.war configured in ./local-config.json >>> is not directory (must be exploded WAR) >>> >>> >>> ?Thanks in advance and cheers,? >>> >>> -- >>> *Jose Miguel Gallas Olmedo* >>> Associate QE at Mobile Team, *Red Hat* >>> >>> +34 618 488 633 <+34%20618%2048%2086%2033> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > *Jose Miguel Gallas Olmedo* > Associate QE at Mobile Team, *Red Hat* > > +34 618 488 633 <+34%20618%2048%2086%2033> > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170317/763a2eec/attachment.html From zhangqiangcanada at gmail.com Mon Mar 20 20:40:27 2017 From: zhangqiangcanada at gmail.com (=?UTF-8?B?5byg5aux?=) Date: Mon, 20 Mar 2017 20:40:27 -0400 Subject: [aerogear-dev] Integrate Hbase with AeroGear Message-ID: Hello, I'm going to work on the GSoC project: Integrate Hbase with AeroGear. Now I'm troubled with how to integrate Hbase. Here are some thoughts of mine: 1. Use a JPA library: DataNucleus Hbase JPA link: https://github.com/datanucleus/datanucleus-hbase By using this we can reuse the data model today. But it's not that habsify. 2. Use Hbase java api directly. Also, redesign data models to fit column base database. Which way do you think is better? Or do you have some other good ideas? Thanks a lot! ~Michelle Zhang -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170320/d5fdaca7/attachment.html From zhangqiangcanada at gmail.com Mon Mar 20 21:25:18 2017 From: zhangqiangcanada at gmail.com (Michelle Zhang) Date: Mon, 20 Mar 2017 18:25:18 -0700 (MST) Subject: [aerogear-dev] Integrate Hbase with AeroGear Message-ID: <1490059518782-12916.post@n5.nabble.com> Hello, I'm going to work on the GSoC project: Integrate Hbase with AeroGear. Now I'm troubled with how to integrate Hbase. Here are some thoughts of mine: 1. Use a JPA library: DataNucleus Hbase JPA link: https://github.com/datanucleus/datanucleus-hbase By using this we can reuse the data model today. But it's not that habsify. 2. Use Hbase java api directly. Also, redesign data models to fit column base database. Which way do you think is better? Or do you have some other good ideas? Thanks a lot! ~Michelle Zhang -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Integrate-Hbase-with-AeroGear-tp12916.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Tue Mar 21 05:27:11 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 21 Mar 2017 09:27:11 +0000 Subject: [aerogear-dev] Integrate Hbase with AeroGear In-Reply-To: <1490059518782-12916.post@n5.nabble.com> References: <1490059518782-12916.post@n5.nabble.com> Message-ID: Hi Michelle, thanks for the interest in AeroGear, and thanks for reaching out to the community! While DataNucleus sounds promising, I think we get the most out of HBase using its good Java client. It has nice functionality, and there is no extra layer around. Regarding the model/schema, yes, we could write a migration script reading out of Postgres/mysql and transforming to HBase structure! Cheers, Matthias On Tue, 21 Mar 2017 at 03:42, Michelle Zhang wrote: > Hello, > I'm going to work on the GSoC project: Integrate Hbase with AeroGear. Now > I'm troubled with how to integrate Hbase. Here are some thoughts of mine: > 1. Use a JPA library: DataNucleus bg JPA > link: https://github.com/datanucleus/datanucleus-hbase > By using this we can reuse the data model today. But it's not that habsify. > 2. Use Hbase java api directly. Also, redesign data models to fit column > base database. > > Which way do you think is better? Or do you have some other good ideas? > > Thanks a lot! > ~Michelle Zhang > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Integrate-Hbase-with-AeroGear-tp12916.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 > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170321/112fb1f1/attachment.html From mm at napp.dk Tue Mar 21 07:48:23 2017 From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=) Date: Tue, 21 Mar 2017 11:48:23 +0000 Subject: [aerogear-dev] Aerogear Push custom key value pairs Message-ID: Hi there, We are trying to implement deep linking in our app. We are following the docs (https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/index.html#397083935) in order to send out custom key values pair in the ?user-data? object. But its not working for us. We have a AeroGear 1.1.0 and 1.1.3 servers running and the results are the same. Sending: curl -u "PushApplicationID:MasterSecret" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{ "message": { "alert": "Hello from the curl HTTP Sender!", "sound": "default", "user-data": { "someKey": "a-value", } }' https://SERVER:PORT/CONTEXT/rest/sender In the activity log of the web interface, we get: { "alert": "Hello from the curl HTTP Sender!", "priority": "normal", "criteria": { "categories": null, "variants": null, "alias": null, "deviceType": null }, "config": { "ttl": -1 } } Anyone got this working? BEST REGARDS __________________ MADS M?LLER CTO, PARTNER Napp A/S T: +45 42 42 80 60 M: +45 20 28 20 26 E: mm at napp.dk W: https://napp.dk __________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170321/4e5c4359/attachment-0001.html From polina.n.koleva at gmail.com Wed Mar 22 18:54:04 2017 From: polina.n.koleva at gmail.com (polinankoleva) Date: Wed, 22 Mar 2017 15:54:04 -0700 (MST) Subject: [aerogear-dev] Integrate Hbase with AeroGear In-Reply-To: <1490059518782-12916.post@n5.nabble.com> References: <1490059518782-12916.post@n5.nabble.com> Message-ID: <1490223244756-12920.post@n5.nabble.com> Hi, I am interested in the same project. I have found Apache Sqoop as a tool for efficiently transferring bulk data between Apache Hadoop and structured datastores such as relational databases. In our case from MySQL to HBase. I think it might be really useful. What do you think? Has anyone tried it? Polina -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Integrate-Hbase-with-AeroGear-tp12916p12920.html Sent from the aerogear-dev mailing list archive at Nabble.com. From polina.n.koleva at gmail.com Sun Mar 26 09:44:37 2017 From: polina.n.koleva at gmail.com (Polina Koleva) Date: Sun, 26 Mar 2017 06:44:37 -0700 (MST) Subject: [aerogear-dev] Documentation of UnifiedPush Server's modules Message-ID: <1490535877441-12921.post@n5.nabble.com> Hey, I am a masters student applying for GSOC project "HBase/Apache Kafka in UnifiedPush Server". I am exploring the codebase of the project so that I can understand the whole logical structure of it and its full functionality. I have noticed that it is divided into "modules". So I am thinking that maybe it will be good somewhere to have a brief description of each module and its function and maybe a diagram which module uses which. This can give a quick start of a developer new to the project and he can easily understand into which module to dive deeply. If you think it is a good idea, I can start doing it. Moreover, it will help me either. Besides, I have seen other open source projects organised in such a modular manner. Why have you decided to do it so modularly? And is this the practice usually? Sorry, if such documentation already exists and I haven't found it. Best regards, Polina Koleva -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Documentation-of-UnifiedPush-Server-s-modules-tp12921.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Mon Mar 27 06:18:44 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 27 Mar 2017 12:18:44 +0200 Subject: [aerogear-dev] Documentation of UnifiedPush Server's modules In-Reply-To: <1490535877441-12921.post@n5.nabble.com> References: <1490535877441-12921.post@n5.nabble.com> Message-ID: Hello, in terms of the structure, here is a list of the most relevant/important modules/folders: * admin-ui: Node.js application for our UI, bundled as a JAR file * model: contains API and JPA implementation of the "data model" * jaxrs: contains the REST endpoints of the server, some are used as "public API endpoints" (such as the sender or device registration), and others are less or more not public, they back the UI, and are protected by keycloak * service: Contains a "service layer", basically less or more smart API wrappers around the DAOs, which are implemented via JPA * push/model: Contains some push specific model classes, also reused by our java client * push/sender: most important package. Here happens the most important: Sending of the push notifications, which is implemented via JMS, and the metrics processing (also via JMS), and storing metrics to the DB layer * servers: builds the WAR files (for our custom keycloak, and our ag-push.war file) Besides that we have docker-compose files, and database configuration (e.g. separated DB docker files) Also, in the appendix of our users guide there is a bit of arch. overview: https://aerogear.org/docs/unifiedpush/ups_userguide/index/#appendix HTH, Matthias On Sun, Mar 26, 2017 at 3:44 PM, Polina Koleva wrote: > Hey, > I am a masters student applying for GSOC project "HBase/Apache Kafka in > UnifiedPush Server". > I am exploring the codebase of the project so that I can understand the > whole logical structure of it and its full functionality. > I have noticed that it is divided into "modules". So I am thinking that > maybe it will be good somewhere to have a brief description of each module > and its function and maybe a diagram which module uses which. This can give > a quick start of a developer new to the project and he can easily > understand > into which module to dive deeply. If you think it is a good idea, I can > start doing it. Moreover, it will help me either. > Besides, I have seen other open source projects organised in such a modular > manner. > Why have you decided to do it so modularly? And is this the practice > usually? > > Sorry, if such documentation already exists and I haven't found it. > > Best regards, > Polina Koleva > > > > -- > View this message in context: http://aerogear-dev.1069024. > n5.nabble.com/Documentation-of-UnifiedPush-Server-s-modules-tp12921.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/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170327/d2951d0b/attachment.html From doctormistral at gmail.com Tue Mar 28 06:14:42 2017 From: doctormistral at gmail.com (Doctor Mistral) Date: Tue, 28 Mar 2017 12:14:42 +0200 Subject: [aerogear-dev] Push plugin fork with 3 enhancements for Android Message-ID: <55d664a3-082f-5418-ca1b-f2da663680ea@gmail.com> Hi all, i've just shared a fork (drmistral/aerogear-cordova-push from Release 3.1.0) containing some enhancements and alignments with iOS side for the Android side of aerogear-cordova-push plugin. Hope you may find it useful. Here is my changes: 1. Set notifications number on app badge. - As in the iOS side, when the app is in background it is possible to set the badge number from the same callback that is defined for iOS. - Number is displayed even in the badge shortcut if defined. - Of course behaviour depends on the device but I'm tested it in a set of devices with Android 4.4+ and it works. - It uses me.leolin.shortcutbadger.ShortcutBadger. 2. Launch app from click on notification. This feature was supposed to be present but unfortunately I never get it working so I decided to check it and fix it. Now it seems working fine. 3. Update notification of "opened" stats on click on notification. In Android, notifications "opened" stats (visible from aerogear admin) were updated just when notification is received. Now (as for iOS) "opened" stats are updated when the notification is opened by clicking on it (that provokes app relaunch). Suggestions are welcome. Cheers Nando -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170328/b91d5847/attachment.html From dpassos at redhat.com Tue Mar 28 09:12:15 2017 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 28 Mar 2017 10:12:15 -0300 Subject: [aerogear-dev] Push plugin fork with 3 enhancements for Android In-Reply-To: <55d664a3-082f-5418-ca1b-f2da663680ea@gmail.com> References: <55d664a3-082f-5418-ca1b-f2da663680ea@gmail.com> Message-ID: Hey Nando, Why not send a PR with those improvements? On Tue, Mar 28, 2017 at 7:14 AM, Doctor Mistral wrote: > Hi all, > > i've just shared a fork (drmistral/aerogear-cordova-push from Release > 3.1.0) containing some enhancements and alignments with iOS side for the > Android side of aerogear-cordova-push plugin. Hope you may find it useful. > > Here is my changes: > > 1. Set notifications number on app badge. > > - As in the iOS side, when the app is in background it is possible to set > the badge number from the same callback that is defined for iOS. > - Number is displayed even in the badge shortcut if defined. > - Of course behaviour depends on the device but I'm tested it in a set of > devices with Android 4.4+ and it works. > - It uses me.leolin.shortcutbadger.ShortcutBadger. > > 2. Launch app from click on notification. > > This feature was supposed to be present but unfortunately I never get it > working so I decided to check it and fix it. Now it seems working fine. > > 3. Update notification of "opened" stats on click on notification. > > In Android, notifications " opened" stats (visible from aerogear admin) > were updated just when notification is received. Now (as for iOS) "opened" > stats are updated when the notification is opened by clicking on it (that > provokes app relaunch). > > Suggestions are welcome. > > Cheers > > Nando > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170328/d645ee0d/attachment.html From doctormistral at gmail.com Tue Mar 28 11:57:49 2017 From: doctormistral at gmail.com (Doctor Mistral) Date: Tue, 28 Mar 2017 17:57:49 +0200 Subject: [aerogear-dev] Push plugin fork with 3 enhancements for Android In-Reply-To: References: <55d664a3-082f-5418-ca1b-f2da663680ea@gmail.com> Message-ID: Hi Daniel, yes I'll do it! N. Il 28/03/17 15:12, Daniel Passos ha scritto: > Hey Nando, > > Why not send a PR with those improvements? > > On Tue, Mar 28, 2017 at 7:14 AM, Doctor Mistral > > wrote: > > Hi all, > > i've just shared a fork (drmistral/aerogear-cordova-push from > Release 3.1.0) containing some enhancements and alignments with > iOS side for the Android side of aerogear-cordova-push plugin. > Hope you may find it useful. > > Here is my changes: > > 1. Set notifications number on app badge. > > - As in the iOS side, when the app is in background it is > possible to set the badge number from the same callback that > is defined for iOS. > - Number is displayed even in the badge shortcut if defined. > - Of course behaviour depends on the device but I'm tested it > in a set of devices with Android 4.4+ and it works. > - It uses me.leolin.shortcutbadger.ShortcutBadger. > > 2. Launch app from click on notification. > > This feature was supposed to be present but unfortunately I > never get it working so I decided to check it and fix it. Now > it seems working fine. > > 3. Update notification of "opened" stats on click on notification. > > In Android, notifications "opened" stats (visible from > aerogear admin) were updated just when notification is > received. Now (as for iOS) "opened" stats are updated when the > notification is opened by clicking on it (that provokes app > relaunch). > > Suggestions are welcome. > > Cheers > > Nando > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > -- > -- Passos > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170328/bfc664e3/attachment-0001.html From dpassos at redhat.com Wed Mar 29 09:02:25 2017 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 29 Mar 2017 10:02:25 -0300 Subject: [aerogear-dev] Move AGDROID projects from Maven to Gradle Message-ID: Hi, I wanna move our AeroGear Android Library from Maven to Gradle structure to make our life easier and kill the maven-sdk-deployer[1] pre-req. As part of this process I also would like to move our current publish process from JBoss Nexus to Bintray[2] in favor to use the awesome bintray-release[3] Gradle plugin. Any thought or concern? [1] https://aerogear.org/docs/guides/aerogear-android/how-to-build-aerogear-android/ [2] https://bintray.com/aerogear [3] https://github.com/novoda/bintray-release -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170329/c3d75036/attachment.html From supittma at redhat.com Wed Mar 29 09:41:30 2017 From: supittma at redhat.com (Summers Pittman) Date: Wed, 29 Mar 2017 09:41:30 -0400 Subject: [aerogear-dev] Move AGDROID projects from Maven to Gradle In-Reply-To: References: Message-ID: On Wed, Mar 29, 2017 at 9:02 AM, Daniel Passos wrote: > Hi, > > I wanna move our AeroGear Android Library from Maven to Gradle structure > to make our life easier and kill the maven-sdk-deployer[1] pre-req. > > As part of this process I also would like to move our current publish > process from JBoss Nexus to Bintray[2] in favor to use the awesome > bintray-release[3] Gradle plugin. > > Any thought or concern? > > One of the problems we ran into last time we tried to migrate was a lot of our plugins (code coverage, license, etc) didn't support the Android Gradle plugin. That is my biggest concern. There were also issues getting the tests to run, but I don't remember what those were. Otherwise, let's make a go at this. > [1] https://aerogear.org/docs/guides/aerogear-android/how- > to-build-aerogear-android/ > [2] https://bintray.com/aerogear > [3] https://github.com/novoda/bintray-release > > -- > -- Passos > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170329/b5792158/attachment.html From omatskiv at redhat.com Wed Mar 29 09:46:37 2017 From: omatskiv at redhat.com (Oleg Matskiv) Date: Wed, 29 Mar 2017 15:46:37 +0200 Subject: [aerogear-dev] Move AGDROID projects from Maven to Gradle In-Reply-To: References: Message-ID: Hi Daniel, moving to Gradle sounds like a great idea to me. Oleg On Wed, Mar 29, 2017 at 3:02 PM, Daniel Passos wrote: > Hi, > > I wanna move our AeroGear Android Library from Maven to Gradle structure > to make our life easier and kill the maven-sdk-deployer[1] pre-req. > > As part of this process I also would like to move our current publish > process from JBoss Nexus to Bintray[2] in favor to use the awesome > bintray-release[3] Gradle plugin. > > Any thought or concern? > > [1] https://aerogear.org/docs/guides/aerogear-android/how- > to-build-aerogear-android/ > [2] https://bintray.com/aerogear > [3] https://github.com/novoda/bintray-release > > -- > -- Passos > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Oleg Matskiv Associate Quality Engineer Red Hat Mobile Application Platform omatskiv at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170329/9700bf51/attachment.html From anujgargcse at gmail.com Wed Mar 29 10:49:43 2017 From: anujgargcse at gmail.com (Anuj Garg) Date: Wed, 29 Mar 2017 20:19:43 +0530 Subject: [aerogear-dev] Move AGDROID projects from Maven to Gradle In-Reply-To: References: Message-ID: Hello Daniel, I would like to help. Though can not be sure about regular contribution because of inconsistency of life :) Regards Anuj Garg On Wed, Mar 29, 2017 at 7:16 PM, Oleg Matskiv wrote: > Hi Daniel, > moving to Gradle sounds like a great idea to me. > > Oleg > > On Wed, Mar 29, 2017 at 3:02 PM, Daniel Passos wrote: > >> Hi, >> >> I wanna move our AeroGear Android Library from Maven to Gradle structure >> to make our life easier and kill the maven-sdk-deployer[1] pre-req. >> >> As part of this process I also would like to move our current publish >> process from JBoss Nexus to Bintray[2] in favor to use the awesome >> bintray-release[3] Gradle plugin. >> >> Any thought or concern? >> >> [1] https://aerogear.org/docs/guides/aerogear-android/how-to- >> build-aerogear-android/ >> [2] https://bintray.com/aerogear >> [3] https://github.com/novoda/bintray-release >> >> -- >> -- Passos >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Oleg Matskiv > Associate Quality Engineer > Red Hat Mobile Application Platform > omatskiv at redhat.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/20170329/057a8f6c/attachment.html From dpassos at redhat.com Wed Mar 29 11:00:39 2017 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 29 Mar 2017 12:00:39 -0300 Subject: [aerogear-dev] Move AGDROID projects from Maven to Gradle In-Reply-To: References:

Message-ID: On Wed, Mar 29, 2017 at 10:41 AM, Summers Pittman wrote: > > > On Wed, Mar 29, 2017 at 9:02 AM, Daniel Passos wrote: > >> Hi, >> >> I wanna move our AeroGear Android Library from Maven to Gradle structure >> to make our life easier and kill the maven-sdk-deployer[1] pre-req. >> >> As part of this process I also would like to move our current publish >> process from JBoss Nexus to Bintray[2] in favor to use the awesome >> bintray-release[3] Gradle plugin. >> >> Any thought or concern? >> >> > One of the problems we ran into last time we tried to migrate was a lot of > our plugins (code coverage, license, etc) didn't support the Android Gradle > plugin. That is my biggest concern. There were also issues getting the > tests to run, but I don't remember what those were. > I will do some tests around it, but I think we don't have this kind of problems anymore. I was able to run tests also ship this using bintray-release[3]. I also tested it with coveralls and works like a charm. Anyway I will test all the things and send a PR to community test first. > Otherwise, let's make a go at this. > > >> [1] https://aerogear.org/docs/guides/aerogear-android/how-to- >> build-aerogear-android/ >> [2] https://bintray.com/aerogear >> [3] https://github.com/novoda/bintray-release >> >> -- >> -- Passos >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170329/88a48aa3/attachment-0001.html From matzew at apache.org Wed Mar 29 18:31:47 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 30 Mar 2017 00:31:47 +0200 Subject: [aerogear-dev] Move AGDROID projects from Maven to Gradle In-Reply-To: References: Message-ID: +1 On Wed, Mar 29, 2017 at 3:46 PM, Oleg Matskiv wrote: > Hi Daniel, > moving to Gradle sounds like a great idea to me. > > Oleg > > On Wed, Mar 29, 2017 at 3:02 PM, Daniel Passos wrote: > >> Hi, >> >> I wanna move our AeroGear Android Library from Maven to Gradle structure >> to make our life easier and kill the maven-sdk-deployer[1] pre-req. >> >> As part of this process I also would like to move our current publish >> process from JBoss Nexus to Bintray[2] in favor to use the awesome >> bintray-release[3] Gradle plugin. >> >> Any thought or concern? >> >> [1] https://aerogear.org/docs/guides/aerogear-android/how-to- >> build-aerogear-android/ >> [2] https://bintray.com/aerogear >> [3] https://github.com/novoda/bintray-release >> >> -- >> -- Passos >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Oleg Matskiv > Associate Quality Engineer > Red Hat Mobile Application Platform > omatskiv at redhat.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/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170330/ce555376/attachment.html From corinnekrych at gmail.com Thu Mar 30 02:46:28 2017 From: corinnekrych at gmail.com (Corinne Krych) Date: Thu, 30 Mar 2017 08:46:28 +0200 Subject: [aerogear-dev] Move AGDROID projects from Maven to Gradle In-Reply-To: References:

Message-ID: +1000 On 30 March 2017 at 00:31, Matthias Wessendorf wrote: > +1 > > On Wed, Mar 29, 2017 at 3:46 PM, Oleg Matskiv wrote: > >> Hi Daniel, >> moving to Gradle sounds like a great idea to me. >> >> Oleg >> >> On Wed, Mar 29, 2017 at 3:02 PM, Daniel Passos >> wrote: >> >>> Hi, >>> >>> I wanna move our AeroGear Android Library from Maven to Gradle structure >>> to make our life easier and kill the maven-sdk-deployer[1] pre-req. >>> >>> As part of this process I also would like to move our current publish >>> process from JBoss Nexus to Bintray[2] in favor to use the awesome >>> bintray-release[3] Gradle plugin. >>> >>> Any thought or concern? >>> >>> [1] https://aerogear.org/docs/guides/aerogear-android/how-to-bui >>> ld-aerogear-android/ >>> [2] https://bintray.com/aerogear >>> [3] https://github.com/novoda/bintray-release >>> >>> -- >>> -- Passos >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Oleg Matskiv >> Associate Quality Engineer >> Red Hat Mobile Application Platform >> omatskiv at redhat.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/ > 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/20170330/4d423996/attachment.html