From cvasilak at gmail.com  Thu May  1 07:25:14 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Thu, 1 May 2014 14:25:14 +0300
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
Message-ID: <3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>

Hi everyone,

have started working on the iOS native client of the contacts quick start app. Based on edewit branch[1] (which creates a contact on signup of a user) have created an initial version of the iOS client and you can find it here [2], together with a screencast showcasing the app in action [3].

Some comments observed during writing of the application which would like your feedback:

a)  for PUT, DELETE operations noticed that the jax-rs backend expects the id of the Contact to be present in the body of the request. Not sure why this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?

b) currently roles are used to distinguish between who is able to create/update/delete contact. When a user signs up (and contact is created),  by default the user is _not_ able to apply any CRUD operations apart from viewing (any operation results in unauthorised error). If we agree on this behaviour, would like to know how can I determine the role of the user (in order to update the UI accordingly, eg. disabling add,edit UI elements). Looking at the json response upon login of the user, couldn?t determine a ?key? that specifies the role (apart from an ?admin? key which stayed the same regardless of the type of the user).


Thanks,
Christos

[1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
[2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
[3] https://vimeo.com/93471554



On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Right, that makes sense, so let?s not join them. The alternate thing to do is to create a contact on sign up, because if you want to receive push notifications at least you should be in the list of contacts. We will still need to change the sign up page a little as we need a phone number and a birth date as well in order to create a contact.
> 
> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com> wrote:
> 
>> These are not strongly held opinions
>> 
>> One reason to keep Users & Contacts separate is...because that is normal for the average enterprise app - your have employees (users) and customers (contacts) - employees/users have different roles/privileges from customers.
>> 
>> The reason they are separated in the secured (PL) version of contacts-mobile-basic is because it simply evolved that way - contacts came first - users/roles added after the fact.   Ideally we would not modify the original too much as it allows a nice learning progression - start with the original contacts-mobile-basic, then upgrade to contacts-mobile-basic-secured, then upgrade to contacts-mobile-basic-secured-cordova (names just made up).
>> 
>> 
>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>> 
>>> Sure !
>>> Be sure to check this with Joshua as he drives the backend bits 
>>> S?bi
>>> 
>>> Envoy? de mon iPhone
>>> 
>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>> 
>>>> Hi,
>>>> 
>>>> How about merging the User model and the Contact into one entity? Seems like they have a lot in common, do we really need 2?
>>>> 
>>>> Cheers,
>>>> Erik Jan
>>>> 
>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>>>> 
>>>>> We should be using the email as alias and the email should also be used as login when registering in the secured part. A registration should also trigger the creation of that user / contact in the application.
>>>>> Author can be left empty By the client and filled by the backend . https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor must stay because the receiver must know who sends the message.
>>>>> 
>>>>> Envoy? de mon iPhone
>>>>> 
>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> I was working on the aerogear-push-quickstarts for Cordova and was wondering what to put for the alias on registration. The version that is there now has users that logs in and contacts that are fetched. What seems to be missing is that everybody gets all contacts instead of just mine (maybe that is fine), but users that sign up for the app are not contacts. So when I want to send a message to a specific mobile user they are not in my list and there is no way to have to define an alias to send to.
>>>>>> 
>>>>>> Also the interface for sending push notifications includes a author. I think it would be better if we remove this and let the service put in the logged in user. That way you can?t pretend to send a message like someone else.
>>>>>> 
>>>>>> 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
>>>> 
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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 bsutter at redhat.com  Thu May  1 10:46:20 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Thu, 1 May 2014 10:46:20 -0400
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
Message-ID: <4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>

Joshua owns the backend, let's see if he has a thought on this item.

On May 1, 2014, at 7:25 AM, Christos Vasilakis <cvasilak at gmail.com> wrote:

> Hi everyone,
> 
> have started working on the iOS native client of the contacts quick start app. Based on edewit branch[1] (which creates a contact on signup of a user) have created an initial version of the iOS client and you can find it here [2], together with a screencast showcasing the app in action [3].
> 
> Some comments observed during writing of the application which would like your feedback:
> 
> a)  for PUT, DELETE operations noticed that the jax-rs backend expects the id of the Contact to be present in the body of the request. Not sure why this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?
> 
> b) currently roles are used to distinguish between who is able to create/update/delete contact. When a user signs up (and contact is created),  by default the user is _not_ able to apply any CRUD operations apart from viewing (any operation results in unauthorised error). If we agree on this behaviour, would like to know how can I determine the role of the user (in order to update the UI accordingly, eg. disabling add,edit UI elements). Looking at the json response upon login of the user, couldn?t determine a ?key? that specifies the role (apart from an ?admin? key which stayed the same regardless of the type of the user).
> 
> 
> Thanks,
> Christos
> 
> [1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
> [3] https://vimeo.com/93471554
> 
> 
> 
> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
> 
>> Right, that makes sense, so let?s not join them. The alternate thing to do is to create a contact on sign up, because if you want to receive push notifications at least you should be in the list of contacts. We will still need to change the sign up page a little as we need a phone number and a birth date as well in order to create a contact.
>> 
>> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com> wrote:
>> 
>>> These are not strongly held opinions
>>> 
>>> One reason to keep Users & Contacts separate is...because that is normal for the average enterprise app - your have employees (users) and customers (contacts) - employees/users have different roles/privileges from customers.
>>> 
>>> The reason they are separated in the secured (PL) version of contacts-mobile-basic is because it simply evolved that way - contacts came first - users/roles added after the fact.   Ideally we would not modify the original too much as it allows a nice learning progression - start with the original contacts-mobile-basic, then upgrade to contacts-mobile-basic-secured, then upgrade to contacts-mobile-basic-secured-cordova (names just made up).
>>> 
>>> 
>>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>> 
>>>> Sure !
>>>> Be sure to check this with Joshua as he drives the backend bits 
>>>> S?bi
>>>> 
>>>> Envoy? de mon iPhone
>>>> 
>>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> How about merging the User model and the Contact into one entity? Seems like they have a lot in common, do we really need 2?
>>>>> 
>>>>> Cheers,
>>>>> Erik Jan
>>>>> 
>>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>>>>> 
>>>>>> We should be using the email as alias and the email should also be used as login when registering in the secured part. A registration should also trigger the creation of that user / contact in the application.
>>>>>> Author can be left empty By the client and filled by the backend . https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor must stay because the receiver must know who sends the message.
>>>>>> 
>>>>>> Envoy? de mon iPhone
>>>>>> 
>>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> I was working on the aerogear-push-quickstarts for Cordova and was wondering what to put for the alias on registration. The version that is there now has users that logs in and contacts that are fetched. What seems to be missing is that everybody gets all contacts instead of just mine (maybe that is fine), but users that sign up for the app are not contacts. So when I want to send a message to a specific mobile user they are not in my list and there is no way to have to define an alias to send to.
>>>>>>> 
>>>>>>> Also the interface for sending push notifications includes a author. I think it would be better if we remove this and let the service put in the logged in user. That way you can?t pretend to send a message like someone else.
>>>>>>> 
>>>>>>> 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
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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 May  2 11:06:51 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 2 May 2014 12:06:51 -0300
Subject: [aerogear-dev] AeroGear Android Push 0.1.1
Message-ID: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>

We have found a bug[1] in the AeroGear Android Push 0.1. It was fixed and
the new version (0.1.1) was already sent to nexus[2].

We'd like to ship it to Maven central next wednesday.

[1] https://issues.jboss.org/browse/AGDROID-214
[2]
http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3139/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140502/4a63c1b1/attachment.html 

From daniel at passos.me  Fri May  2 11:10:46 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 2 May 2014 12:10:46 -0300
Subject: [aerogear-dev] Android: HSTS issue with registration against
	OpenShift
In-Reply-To: <CAAg5f2RMLQu8CX_he-vWJcZ1TByTvGcZ34gK32bh03fT9ssf9A@mail.gmail.com>
References: <CAAg5f2RMLQu8CX_he-vWJcZ1TByTvGcZ34gK32bh03fT9ssf9A@mail.gmail.com>
Message-ID: <CAKjsGbs9zohEMCwdCneuyjXswh5_2HSZr0yu3T3-qDzeRwUZgw@mail.gmail.com>

It was fixed and the new version (0.1.1) was already sent to nexus. See [1]

[1]
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Android-Push-0-1-1-td7639.html

-- Passos

On Tue, Apr 29, 2014 at 5:14 AM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hi,
>
> I was wondering if AGDROID-214 could be addressed w/in the 1.4.0 release
> of the AG-Droid library. Especially since that release also contains the
> factored out "push library" apk/jar
>
> Thanks!
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140502/3cc123c5/attachment.html 

From jbalunas at redhat.com  Fri May  2 16:37:56 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Fri, 2 May 2014 16:37:56 -0400
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>
Message-ID: <2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>

I wanted to chime in here on additional/related items around the contacts use-case and specifically around how to integrate push.  Some of these have already been discussed so just getting in one place for my own sanity :-)

1) I agree that users and "contacts" are separate things.  I think it is best to think about them as was mentioned below - users (employees) and contacts (customers, leads, etc...).  This is easier to grok imo and could be helped by some simple wording in the UI.

Cons: 
** We then need a way to add "users" - otherwise we won't be sending many push messages.  Maybe users could be automatically created when an app first accesses the backend?  

2) Simplifying the push use-case:  If we change the use-case from saying hi to specific contacts to notifying all users when a new contact was created it could simplify not only the UI, but the server side processing for the push.  We could reserve the more specific push usage to the console, and/or AeroDoc.  

If we go with 2) we might be able to avoid the issues with 1) altogether because a broadcast would send to every app that has registered.  

Wdyt?


On May 1, 2014, at 10:46 AM, Burr Sutter <bsutter at redhat.com> wrote:

> Joshua owns the backend, let's see if he has a thought on this item.
> 
> On May 1, 2014, at 7:25 AM, Christos Vasilakis <cvasilak at gmail.com> wrote:
> 
>> Hi everyone,
>> 
>> have started working on the iOS native client of the contacts quick start app. Based on edewit branch[1] (which creates a contact on signup of a user) have created an initial version of the iOS client and you can find it here [2], together with a screencast showcasing the app in action [3].
>> 
>> Some comments observed during writing of the application which would like your feedback:
>> 
>> a)  for PUT, DELETE operations noticed that the jax-rs backend expects the id of the Contact to be present in the body of the request. Not sure why this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?
>> 
>> b) currently roles are used to distinguish between who is able to create/update/delete contact. When a user signs up (and contact is created),  by default the user is _not_ able to apply any CRUD operations apart from viewing (any operation results in unauthorised error). If we agree on this behaviour, would like to know how can I determine the role of the user (in order to update the UI accordingly, eg. disabling add,edit UI elements). Looking at the json response upon login of the user, couldn?t determine a ?key? that specifies the role (apart from an ?admin? key which stayed the same regardless of the type of the user).
>> 
>> 
>> Thanks,
>> Christos
>> 
>> [1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
>> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
>> [3] https://vimeo.com/93471554
>> 
>> 
>> 
>> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
>> 
>>> Right, that makes sense, so let?s not join them. The alternate thing to do is to create a contact on sign up, because if you want to receive push notifications at least you should be in the list of contacts. We will still need to change the sign up page a little as we need a phone number and a birth date as well in order to create a contact.
>>> 
>>> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com> wrote:
>>> 
>>>> These are not strongly held opinions
>>>> 
>>>> One reason to keep Users & Contacts separate is...because that is normal for the average enterprise app - your have employees (users) and customers (contacts) - employees/users have different roles/privileges from customers.
>>>> 
>>>> The reason they are separated in the secured (PL) version of contacts-mobile-basic is because it simply evolved that way - contacts came first - users/roles added after the fact.   Ideally we would not modify the original too much as it allows a nice learning progression - start with the original contacts-mobile-basic, then upgrade to contacts-mobile-basic-secured, then upgrade to contacts-mobile-basic-secured-cordova (names just made up).
>>>> 
>>>> 
>>>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>>> 
>>>>> Sure !
>>>>> Be sure to check this with Joshua as he drives the backend bits 
>>>>> S?bi
>>>>> 
>>>>> Envoy? de mon iPhone
>>>>> 
>>>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> How about merging the User model and the Contact into one entity? Seems like they have a lot in common, do we really need 2?
>>>>>> 
>>>>>> Cheers,
>>>>>> Erik Jan
>>>>>> 
>>>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>>>>>> 
>>>>>>> We should be using the email as alias and the email should also be used as login when registering in the secured part. A registration should also trigger the creation of that user / contact in the application.
>>>>>>> Author can be left empty By the client and filled by the backend . https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor must stay because the receiver must know who sends the message.
>>>>>>> 
>>>>>>> Envoy? de mon iPhone
>>>>>>> 
>>>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>>>>>> 
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> I was working on the aerogear-push-quickstarts for Cordova and was wondering what to put for the alias on registration. The version that is there now has users that logs in and contacts that are fetched. What seems to be missing is that everybody gets all contacts instead of just mine (maybe that is fine), but users that sign up for the app are not contacts. So when I want to send a message to a specific mobile user they are not in my list and there is no way to have to define an alias to send to.
>>>>>>>> 
>>>>>>>> Also the interface for sending push notifications includes a author. I think it would be better if we remove this and let the service put in the logged in user. That way you can?t pretend to send a message like someone else.
>>>>>>>> 
>>>>>>>> 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
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> 
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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  Fri May  2 17:14:26 2014
From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=)
Date: Fri, 2 May 2014 23:14:26 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>
	<2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>
Message-ID: <657431A5-E474-4C52-8E9F-1FAEE0E5EB76@gmail.com>



Envoy? de mon iPhone

> Le 2 mai 2014 ? 22:37, Jay Balunas <jbalunas at redhat.com> a ?crit :
> 
> I wanted to chime in here on additional/related items around the contacts use-case and specifically around how to integrate push.  Some of these have already been discussed so just getting in one place for my own sanity :-)
> 
> 1) I agree that users and "contacts" are separate things.  I think it is best to think about them as was mentioned below - users (employees) and contacts (customers, leads, etc...).  This is easier to grok imo and could be helped by some simple wording in the UI.
> 
> Cons: 
> ** We then need a way to add "users" - otherwise we won't be sending many push messages.  Maybe users could be automatically created when an app first accesses the backend?  
> 
> 2) Simplifying the push use-case:  If we change the use-case from saying hi to specific contacts to notifying all users when a new contact was created it could simplify not only the UI, but the server side processing for the push.  We could reserve the more specific push usage to the console, and/or AeroDoc.  
> 
> If we go with 2) we might be able to avoid the issues with 1) altogether because a broadcast would send to every app that has registered.  
> 
> Wdyt?
Yeah I like 2) , simplifies a lot but stills show the basics of push.
2 suggestions :
- let's make the notifications content like "<user> added a new contact : <first name> <last name>"

- in the backend since the trigger is the entity creation, let's take advantage of the callbacks/events that JPA provides , that will be a really good use case to show how the  the java sender can be integrated.
Spring also provides these kinds of hooks.
> 
> 
>> On May 1, 2014, at 10:46 AM, Burr Sutter <bsutter at redhat.com> wrote:
>> 
>> Joshua owns the backend, let's see if he has a thought on this item.
>> 
>>> On May 1, 2014, at 7:25 AM, Christos Vasilakis <cvasilak at gmail.com> wrote:
>>> 
>>> Hi everyone,
>>> 
>>> have started working on the iOS native client of the contacts quick start app. Based on edewit branch[1] (which creates a contact on signup of a user) have created an initial version of the iOS client and you can find it here [2], together with a screencast showcasing the app in action [3].
>>> 
>>> Some comments observed during writing of the application which would like your feedback:
>>> 
>>> a)  for PUT, DELETE operations noticed that the jax-rs backend expects the id of the Contact to be present in the body of the request. Not sure why this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?
>>> 
>>> b) currently roles are used to distinguish between who is able to create/update/delete contact. When a user signs up (and contact is created),  by default the user is _not_ able to apply any CRUD operations apart from viewing (any operation results in unauthorised error). If we agree on this behaviour, would like to know how can I determine the role of the user (in order to update the UI accordingly, eg. disabling add,edit UI elements). Looking at the json response upon login of the user, couldn?t determine a ?key? that specifies the role (apart from an ?admin? key which stayed the same regardless of the type of the user).
>>> 
>>> 
>>> Thanks,
>>> Christos
>>> 
>>> [1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
>>> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
>>> [3] https://vimeo.com/93471554
>>> 
>>> 
>>> 
>>>> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
>>>> 
>>>> Right, that makes sense, so let?s not join them. The alternate thing to do is to create a contact on sign up, because if you want to receive push notifications at least you should be in the list of contacts. We will still need to change the sign up page a little as we need a phone number and a birth date as well in order to create a contact.
>>>> 
>>>>> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com> wrote:
>>>>> 
>>>>> These are not strongly held opinions
>>>>> 
>>>>> One reason to keep Users & Contacts separate is...because that is normal for the average enterprise app - your have employees (users) and customers (contacts) - employees/users have different roles/privileges from customers.
>>>>> 
>>>>> The reason they are separated in the secured (PL) version of contacts-mobile-basic is because it simply evolved that way - contacts came first - users/roles added after the fact.   Ideally we would not modify the original too much as it allows a nice learning progression - start with the original contacts-mobile-basic, then upgrade to contacts-mobile-basic-secured, then upgrade to contacts-mobile-basic-secured-cordova (names just made up).
>>>>> 
>>>>> 
>>>>>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>>>>> 
>>>>>> Sure !
>>>>>> Be sure to check this with Joshua as he drives the backend bits 
>>>>>> S?bi
>>>>>> 
>>>>>> Envoy? de mon iPhone
>>>>>> 
>>>>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> How about merging the User model and the Contact into one entity? Seems like they have a lot in common, do we really need 2?
>>>>>>> 
>>>>>>> Cheers,
>>>>>>> Erik Jan
>>>>>>> 
>>>>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>>>>>>> 
>>>>>>>> We should be using the email as alias and the email should also be used as login when registering in the secured part. A registration should also trigger the creation of that user / contact in the application.
>>>>>>>> Author can be left empty By the client and filled by the backend . https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor must stay because the receiver must know who sends the message.
>>>>>>>> 
>>>>>>>> Envoy? de mon iPhone
>>>>>>>> 
>>>>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>>>>>>> 
>>>>>>>>> Hi,
>>>>>>>>> 
>>>>>>>>> I was working on the aerogear-push-quickstarts for Cordova and was wondering what to put for the alias on registration. The version that is there now has users that logs in and contacts that are fetched. What seems to be missing is that everybody gets all contacts instead of just mine (maybe that is fine), but users that sign up for the app are not contacts. So when I want to send a message to a specific mobile user they are not in my list and there is no way to have to define an alias to send to.
>>>>>>>>> 
>>>>>>>>> Also the interface for sending push notifications includes a author. I think it would be better if we remove this and let the service put in the logged in user. That way you can?t pretend to send a message like someone else.
>>>>>>>>> 
>>>>>>>>> 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
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>> 
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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 May  5 03:04:18 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 5 May 2014 09:04:18 +0200
Subject: [aerogear-dev] Team meeting
Message-ID: <CAFJm-3EsjHH9jtWqJU+a3LMj4QGaGiCUTZMPWdSYq+mYwkgUPw@mail.gmail.com>

Agenda:
http://oksoclap.com/p/aerogear-team-mgt-20140505
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140505/afa5a549/attachment.html 

From antoine.matyja at worldline.com  Mon May  5 03:21:22 2014
From: antoine.matyja at worldline.com (A577127)
Date: Mon, 5 May 2014 00:21:22 -0700 (PDT)
Subject: [aerogear-dev] UPS : JBoss EAP 6.2.0 + MySQL datasource gives
 me errors
In-Reply-To: <20140430164723.GA96758@abstractj.org>
References: <1398862247549-7625.post@n5.nabble.com>
	<20140430162853.47ea664d@kapy-ntb-x220>
	<1398870639710-7631.post@n5.nabble.com>
	<20140430164723.GA96758@abstractj.org>
Message-ID: <1399274482544-7644.post@n5.nabble.com>

There you go :
http://pastebin.com/X0yfmkDi
(sorry it's french)

(by the way it's Antoine not Antonie )



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/UPS-JBoss-EAP-6-2-0-MySQL-datasource-gives-me-errors-tp7625p7644.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From cvasilak at gmail.com  Mon May  5 03:34:59 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 5 May 2014 10:34:59 +0300
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>
	<2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>
Message-ID: <5639DBE5-69E0-4C06-8F9C-AAFD8105E140@gmail.com>

Hi,

answers inline

On May 2, 2014, at 11:37 PM, Jay Balunas <jbalunas at redhat.com> wrote:

> I wanted to chime in here on additional/related items around the contacts use-case and specifically around how to integrate push.  Some of these have already been discussed so just getting in one place for my own sanity :-)
> 
> 1) I agree that users and "contacts" are separate things.  I think it is best to think about them as was mentioned below - users (employees) and contacts (customers, leads, etc...).  This is easier to grok imo and could be helped by some simple wording in the UI.

+1


> Cons: 
> ** We then need a way to add "users" - otherwise we won't be sending many push messages.  Maybe users could be automatically created when an app first accesses the backend?  

already the backend provides endpoints for creation of ?users?, as well as a list of default users initialised once the app is first loaded. By default when a new user is created the security role assigned to it doesn?t allow the creation of new contacts,  you get back an ?Unauthorised? error. It doesn?t effect push per se, since an ?admin? user can create a contact and the notification can be send to all other users that are logged in, but we should document this behaviour. 

> 
> 2) Simplifying the push use-case:  If we change the use-case from saying hi to specific contacts to notifying all users when a new contact was created it could simplify not only the UI, but the server side processing for the push.  We could reserve the more specific push usage to the console, and/or AeroDoc.  
> 
> If we go with 2) we might be able to avoid the issues with 1) altogether because a broadcast would send to every app that has registered.  
> 
> Wdyt?

I am +1 on this behaviour.  IMHO its more clear for the end-user and the actual notification is used to ?alert? for a change on the server part that the app can decided to respond (e.g. fetch the new contact list).

Thanks,
Christos


> 
> 
> On May 1, 2014, at 10:46 AM, Burr Sutter <bsutter at redhat.com> wrote:
> 
>> Joshua owns the backend, let's see if he has a thought on this item.
>> 
>> On May 1, 2014, at 7:25 AM, Christos Vasilakis <cvasilak at gmail.com> wrote:
>> 
>>> Hi everyone,
>>> 
>>> have started working on the iOS native client of the contacts quick start app. Based on edewit branch[1] (which creates a contact on signup of a user) have created an initial version of the iOS client and you can find it here [2], together with a screencast showcasing the app in action [3].
>>> 
>>> Some comments observed during writing of the application which would like your feedback:
>>> 
>>> a)  for PUT, DELETE operations noticed that the jax-rs backend expects the id of the Contact to be present in the body of the request. Not sure why this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?
>>> 
>>> b) currently roles are used to distinguish between who is able to create/update/delete contact. When a user signs up (and contact is created),  by default the user is _not_ able to apply any CRUD operations apart from viewing (any operation results in unauthorised error). If we agree on this behaviour, would like to know how can I determine the role of the user (in order to update the UI accordingly, eg. disabling add,edit UI elements). Looking at the json response upon login of the user, couldn?t determine a ?key? that specifies the role (apart from an ?admin? key which stayed the same regardless of the type of the user).
>>> 
>>> 
>>> Thanks,
>>> Christos
>>> 
>>> [1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
>>> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
>>> [3] https://vimeo.com/93471554
>>> 
>>> 
>>> 
>>> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
>>> 
>>>> Right, that makes sense, so let?s not join them. The alternate thing to do is to create a contact on sign up, because if you want to receive push notifications at least you should be in the list of contacts. We will still need to change the sign up page a little as we need a phone number and a birth date as well in order to create a contact.
>>>> 
>>>> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com> wrote:
>>>> 
>>>>> These are not strongly held opinions
>>>>> 
>>>>> One reason to keep Users & Contacts separate is...because that is normal for the average enterprise app - your have employees (users) and customers (contacts) - employees/users have different roles/privileges from customers.
>>>>> 
>>>>> The reason they are separated in the secured (PL) version of contacts-mobile-basic is because it simply evolved that way - contacts came first - users/roles added after the fact.   Ideally we would not modify the original too much as it allows a nice learning progression - start with the original contacts-mobile-basic, then upgrade to contacts-mobile-basic-secured, then upgrade to contacts-mobile-basic-secured-cordova (names just made up).
>>>>> 
>>>>> 
>>>>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>>>> 
>>>>>> Sure !
>>>>>> Be sure to check this with Joshua as he drives the backend bits 
>>>>>> S?bi
>>>>>> 
>>>>>> Envoy? de mon iPhone
>>>>>> 
>>>>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> How about merging the User model and the Contact into one entity? Seems like they have a lot in common, do we really need 2?
>>>>>>> 
>>>>>>> Cheers,
>>>>>>> Erik Jan
>>>>>>> 
>>>>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <scm.blanc at gmail.com> wrote:
>>>>>>>> 
>>>>>>>> We should be using the email as alias and the email should also be used as login when registering in the secured part. A registration should also trigger the creation of that user / contact in the application.
>>>>>>>> Author can be left empty By the client and filled by the backend . https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor must stay because the receiver must know who sends the message.
>>>>>>>> 
>>>>>>>> Envoy? de mon iPhone
>>>>>>>> 
>>>>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com> a ?crit :
>>>>>>>>> 
>>>>>>>>> Hi,
>>>>>>>>> 
>>>>>>>>> I was working on the aerogear-push-quickstarts for Cordova and was wondering what to put for the alias on registration. The version that is there now has users that logs in and contacts that are fetched. What seems to be missing is that everybody gets all contacts instead of just mine (maybe that is fine), but users that sign up for the app are not contacts. So when I want to send a message to a specific mobile user they are not in my list and there is no way to have to define an alias to send to.
>>>>>>>>> 
>>>>>>>>> Also the interface for sending push notifications includes a author. I think it would be better if we remove this and let the service put in the logged in user. That way you can?t pretend to send a message like someone else.
>>>>>>>>> 
>>>>>>>>> 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
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>> 
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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 antoine.matyja at worldline.com  Mon May  5 07:56:06 2014
From: antoine.matyja at worldline.com (A577127)
Date: Mon, 5 May 2014 04:56:06 -0700 (PDT)
Subject: [aerogear-dev] UPS -> Windows 8 push notifications thoughts
Message-ID: <1399290966123-7646.post@n5.nabble.com>

Hello,

I'm looking for information about your future plans for implementing Windows
8 push notifications on the unified push server (if you've already thought
about it). I looked for topics on the mailing list but didn't find my
answers so I create this topic.

Since Windows 8 uses XML data format, what are you plans to implement it on
the UPS in the future ? Current supported platforms all use JSON, allowing
to send a notification to everyone from one command. Either you'll lose this
capability, either you'll have to "convert" JSON to XML, which is
problematic since Windows 8 has dozens of XML schemas (and some aren't
really compatible with Apple's one for example).

Thanks,



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/UPS-Windows-8-push-notifications-thoughts-tp7646.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From corinnekrych at gmail.com  Mon May  5 08:36:59 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Mon, 5 May 2014 14:36:59 +0200
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
References: <53595702.90900@redhat.com> <20140425213755.GB36605@abstractj.org>
	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
Message-ID: <E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>

Hello Summers

First quick review, here are the feedback/questions:

1. add a cookbook recipe to help for demoing Android OAuth2. I've successfully tested it using @secondsun 's demo [1]. It should be part of android-cookbook with some readme instructions on how to fill OAuth2 Google Drive config will help (See the one for iOS [2]). As we're using public OAuth client, no client secret is required we could used a pre-configured one like iOS and JS?

2. Android version is now definitively ahead of iOS one ;) as you?ve implemented refresh token but configuration is very alike for the naming etc? +1

3. I like AuthzSevice idea where we store the tokens for easier automatic refresh. Most end-user app will ask for grant only once so such a service that retieve and check validity of token is needed;
- But, what about making it configurable to leave the option to store or not to store tokens?
- The storage for refresh token should be more secure either encrypted storage with ag-crypto or keychain/keystore. wdyt?

4. not sure about what is the purpose of AdditionalAuthorizationParams in AuthzConfig?

5. Obviously as you said more work need to be done for removing token, Authorizer..
for iOs we have an epic AGIOS-188 [3] for all Oauth2 work. Checking Android tickets, I was a bit surprised by AGDROID-244 and AGDROID-242, does it mean support for OAuth? 

Good work! Need to look into AGIOS-145 refresh token and (newly created) AGIOS-190 AuthzService to catch up with you guys.

++
Corinne

[1] https://github.com/secondsun/aerogear-android-oauth2-demo
[2] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/GoogleDrive/GoogleDrive.md#google-setup-optional
[3] https://issues.jboss.org/browse/AGIOS-188

On 27 Apr 2014, at 08:55, Corinne Krych <corinnekrych at gmail.com> wrote:

> Yep same here i'd love to review it an compare with iOS version. I'll send feedback next week too.
> ++
> Corinne
> 
> On Friday, April 25, 2014, Bruno Oliveira <bruno at abstractj.org> wrote:
> Hi Summers, not sure about the timing. But I would like to review on the
> next week.
> 
> On 2014-04-24, Summers Pittman wrote:
> >
> > https://github.com/aerogear/aerogear-android/pull/146
> >
> > This PR is 1) big and 2) incomplete
> > (https://issues.jboss.org/browse/AGDROID/component/12319553). However,
> > it represents a certain set of functionality and I want to get
> > feedback/cleanup/merge before I continue making it even bigger.
> >
> > I would be EXCITED if someone can review this monster.  If it needs to
> > be cut up and submitted piecemeal to make it more digestible I will also
> > take feedback on how to do that.
> >
> > Summers
> >
> > --
> > 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
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From supittma at redhat.com  Mon May  5 09:01:00 2014
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 05 May 2014 09:01:00 -0400
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
References: <53595702.90900@redhat.com> <20140425213755.GB36605@abstractj.org>
	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
Message-ID: <53678B8C.3070105@redhat.com>

On Mon 05 May 2014 08:36:59 AM EDT, Corinne Krych wrote:
>
> Hello Summers
>
> First quick review, here are the feedback/questions:
>
> 1. add a cookbook recipe to help for demoing Android OAuth2. I've 
> successfully tested it using @secondsun 's demo [1]. It should be part 
> of android-cookbook with some readme instructions on how to fill 
> OAuth2 Google Drive config will help (See the one for iOS [2]). As 
> we're using public OAuth client, no client secret is required we could 
> used a pre-configured one like iOS and JS?
Probably true.  I'll add a JIRA.
https://issues.jboss.org/browse/AGDROID-248 (Docs)
https://issues.jboss.org/browse/AGDROID-249 (App)
>
> 2. Android version is now definitively ahead of iOS one ;) as you?ve 
> implemented refresh token but configuration is very alike for the 
> naming etc? +1
>
> 3. I like AuthzSevice idea where we store the tokens for easier 
> automatic refresh. Most end-user app will ask for grant only once so 
> such a service that retieve and check validity of token is needed;
> - But, what about making it configurable to leave the option to store 
> or not to store tokens?
Seems like it is somewhat related to this : 
https://issues.jboss.org/browse/AGDROID-241

Perhaps the jira should be to make storage configurable.  If we wanted 
to explicitly NOT store then we could make a dummy Store which just 
routed everything to /dev/null.
> - The storage for refresh token should be more secure either encrypted 
> storage with ag-crypto or keychain/keystore. wdyt?
See above
>
> 4. not sure about what is the purpose of AdditionalAuthorizationParams 
> in AuthzConfig?
So the OAuth2 spec isn't implemented very well.  As an example to get a 
refresh token from google you have to pass the parameter "access_type" 
with a value "offline".  This is not part of the spec per se.
>
> 5. Obviously as you said more work need to be done for removing token, 
> Authorizer..
> for iOs we have an epic AGIOS-188 [3] for all Oauth2 work. Checking 
> Android tickets, I was a bit surprised by AGDROID-244 and AGDROID-242, 
> does it mean support for OAuth?
I would like it.  After the PR is merged passos and I should have this 
scheduled.  I am sure these will not be a priority but it is a nice to have.
>
> Good work! Need to look into AGIOS-145 refresh token and (newly 
> created) AGIOS-190 AuthzService to catch up with you guys.
>
> ++
> Corinne
>
> [1] https://github.com/secondsun/aerogear-android-oauth2-demo
> [2] 
> https://github.com/aerogear/aerogear-ios-cookbook/blob/master/GoogleDrive/GoogleDrive.md#google-setup-optional
> [3] https://issues.jboss.org/browse/AGIOS-188
>
> On 27 Apr 2014, at 08:55, Corinne Krych <corinnekrych at gmail.com> wrote:
>
>>
>> Yep same here i'd love to review it an compare with iOS version. I'll 
>> send feedback next week too.
>> ++
>> Corinne
>>
>> On Friday, April 25, 2014, Bruno Oliveira <bruno at abstractj.org> wrote:
>> Hi Summers, not sure about the timing. But I would like to review on the
>> next week.
>>
>> On 2014-04-24, Summers Pittman wrote:
>>>
>>>
>>> https://github.com/aerogear/aerogear-android/pull/146
>>>
>>> This PR is 1) big and 2) incomplete
>>> (https://issues.jboss.org/browse/AGDROID/component/12319553). However,
>>> it represents a certain set of functionality and I want to get
>>> feedback/cleanup/merge before I continue making it even bigger.
>>>
>>> I would be EXCITED if someone can review this monster. If it needs to
>>> be cut up and submitted piecemeal to make it more digestible I will also
>>> take feedback on how to do that.
>>>
>>> Summers
>>>
>>> --
>>> 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
>>
>>
>> --
>>
>> 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



-- 
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.


From bruno at abstractj.org  Mon May  5 09:17:58 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 5 May 2014 10:17:58 -0300
Subject: [aerogear-dev] Offline specification 0.0.1
Message-ID: <20140505131758.GA195@abstractj.org>

Good morning slackland,

After debating with Passos and banging my head against the wall with the
possibilities for offline. This is what we have in mind as the next
steps for offline storage:
https://github.com/aerogear/aerogear.org/pull/296

I would like to thank Passos for the guidance with Android and
contributions to this specification.

Feedback is welcome

--

abstractj

From daniel at passos.me  Mon May  5 09:40:07 2014
From: daniel at passos.me (Daniel Passos)
Date: Mon, 5 May 2014 10:40:07 -0300
Subject: [aerogear-dev] Replace Factory by Registrations
Message-ID: <CAKjsGbu4275p7X75j0z=e0dWQ8NAz-UQb8iM5s_1AzpLrk_m-w@mail.gmail.com>

A long time ago Tadeas Kriz had a awesome idea to kill the ugly factory and
replace it for registrations[1]. Summers and I have been thinking about it
and we'd like to replace it in 2.0. So, we are starting the new agdroid
library for offline and we'd like start it using registrations[2] instead
Factory.

Wdyt? [1] https://gist.github.com/TadeasKriz/e0f5583e2a24c32dc253 [2]
https://gist.github.com/danielpassos/088498b553699f23ff51
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140505/54492177/attachment.html 

From bruno at abstractj.org  Mon May  5 09:49:17 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 5 May 2014 10:49:17 -0300
Subject: [aerogear-dev] Replace Factory by Registrations
In-Reply-To: <CAKjsGbu4275p7X75j0z=e0dWQ8NAz-UQb8iM5s_1AzpLrk_m-w@mail.gmail.com>
References: <CAKjsGbu4275p7X75j0z=e0dWQ8NAz-UQb8iM5s_1AzpLrk_m-w@mail.gmail.com>
Message-ID: <20140505134917.GC4585@abstractj.org>

Go for it!

On 2014-05-05, Daniel Passos wrote:
> A long time ago Tadeas Kriz had a awesome idea to kill the ugly factory and
> replace it for registrations[1]. Summers and I have been thinking about it
> and we'd like to replace it in 2.0. So, we are starting the new agdroid
> library for offline and we'd like start it using registrations[2] instead
> Factory.
>
> Wdyt? [1] https://gist.github.com/TadeasKriz/e0f5583e2a24c32dc253 [2]
> https://gist.github.com/danielpassos/088498b553699f23ff51

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From cvasilak at gmail.com  Mon May  5 10:18:46 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 5 May 2014 17:18:46 +0300
Subject: [aerogear-dev] Team meeting
In-Reply-To: <CAFJm-3EsjHH9jtWqJU+a3LMj4QGaGiCUTZMPWdSYq+mYwkgUPw@mail.gmail.com>
References: <CAFJm-3EsjHH9jtWqJU+a3LMj4QGaGiCUTZMPWdSYq+mYwkgUPw@mail.gmail.com>
Message-ID: <1C45904B-E194-4DB9-BE86-9FACAAC3128F@gmail.com>

fyi meeting minutes:

<jbott>	 Meeting ended Mon May  5 14:01:32 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
 <jbott>	 Minutes:        http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-05-13.45.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-05-13.45.txt
 <jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-05-13.45.log.html


On May 5, 2014, at 10:04 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> Agenda:
> http://oksoclap.com/p/aerogear-team-mgt-20140505
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140505/9a2771ec/attachment.html 

From daniel.bevenius at gmail.com  Mon May  5 10:31:08 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 5 May 2014 16:31:08 +0200
Subject: [aerogear-dev] SimplePush Server 0.11.0
In-Reply-To: <20140429125827.0dfcaa6f@kapy-ntb-x220>
References: <CAFJm-3HA3NM3kswb9jfcFi1tfx3QKGkGZL_5tqcnx8gHhzuZuQ@mail.gmail.com>
	<20140429125827.0dfcaa6f@kapy-ntb-x220>
Message-ID: <CAFJm-3EOJGv-Vbq_5SWNVBreBOFqtiXf1hAX1rzz6hjWRbgodw@mail.gmail.com>

AeroGear SimplePush 0.11.0 has been staged:
http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3144/

Let us know if you find any issues or require more time for testing. If
nothing crops up we will release on Thursday.




On 29 April 2014 12:58, Karel Piwko <kpiwko at redhat.com> wrote:

> Sounds good. Let me know when testing phase will be approaching.
>
> Karel
>
> On Wed, 23 Apr 2014 10:18:12 +0200
> Daniel Bevenius <daniel.bevenius at gmail.com> wrote:
>
> > Hi all,
> >
> > just wanted to give a heads up that I've rescheduled the release of
> > SimplePush 0.11.0 [1]. There are only two task remaining, but I'll be
> > working on other things for a while which is the reason for there not
> being
> > more.
> >
> > The main task of interest I think is [2], which allows notifications to
> be
> > done without a version in the body of the HTTP request. This I believe
> will
> > simplify the admin ui and perhaps other areas. If you'd like to see an
> > earlier release then let me know and I'll get it done. As of now though,
> > I've set the release date to May 6.
> >
> > /Dan
> >
> >
> > [1]
> >
> https://issues.jboss.org/browse/AGSMPLPUSH-16?filter=12321270&jql=project%20%3D%20AGSMPLPUSH%20AND%20fixVersion%20%3D%20%220.11.0%22%20AND%20status%20in%20(Open%2C%20%22Coding%20In%20Progress%22%2C%20Reopened%2C%20%22Pull%20Request%20Sent%22)
> >
> > [2] https://issues.jboss.org/browse/AGSMPLPUSH-54
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140505/bc7b9464/attachment.html 

From bruno at abstractj.org  Mon May  5 11:56:26 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 5 May 2014 12:56:26 -0300
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <53678B8C.3070105@redhat.com>
References: <53595702.90900@redhat.com> <20140425213755.GB36605@abstractj.org>
	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
	<53678B8C.3070105@redhat.com>
Message-ID: <20140505155626.GA23951@abstractj.org>

On 2014-05-05, Summers Pittman wrote:
> On Mon 05 May 2014 08:36:59 AM EDT, Corinne Krych wrote:
> >
> > 2. Android version is now definitively ahead of iOS one ;) as you?ve
> > implemented refresh token but configuration is very alike for the
> > naming etc? +1
> >
> > 3. I like AuthzSevice idea where we store the tokens for easier
> > automatic refresh. Most end-user app will ask for grant only once so
> > such a service that retieve and check validity of token is needed;
> > - But, what about making it configurable to leave the option to store
> > or not to store tokens?
> Seems like it is somewhat related to this :
> https://issues.jboss.org/browse/AGDROID-241
>
> Perhaps the jira should be to make storage configurable.  If we wanted
> to explicitly NOT store then we could make a dummy Store which just
> routed everything to /dev/null.

What's the real need behind store those tokens? If is really necessary,
that's ok, otherwise let's do not store it. Offline, OAuth2 tokens are
useless.

Or add an option to choose between store or not store like mentioned
here.

> > - The storage for refresh token should be more secure either encrypted
> > storage with ag-crypto or keychain/keystore. wdyt?
> See above

Encryption won't fix this, worse, will add an extra level of complexity
to the application. Let's think about it, what do we need for
encryption?

1. Generate a private key
2. If it doesn't have a password is worthless (for local storage)
3. Alright, is password based, let's encrypt everything now
4. Now at every inclusion of tokens, you prompt users for the password

They would remember your name forever sometimes attached to bad names.
IMO my suggestion is:

1. Leave it as is and never allow to store in any kind of external storage
2. Do not store (+1)
2. Cache and destroy it when the application is closed
4. Use encryption and make the whole application more complex

> >
> > 4. not sure about what is the purpose of AdditionalAuthorizationParams
> > in AuthzConfig?
> So the OAuth2 spec isn't implemented very well.  As an example to get a
> refresh token from google you have to pass the parameter "access_type"
> with a value "offline".  This is not part of the spec per se.
> >
> > 5. Obviously as you said more work need to be done for removing token,
> > Authorizer..
> > for iOs we have an epic AGIOS-188 [3] for all Oauth2 work. Checking
> > Android tickets, I was a bit surprised by AGDROID-244 and AGDROID-242,
> > does it mean support for OAuth?
> I would like it.  After the PR is merged passos and I should have this
> scheduled.  I am sure these will not be a priority but it is a nice to have.
> >
> > Good work! Need to look into AGIOS-145 refresh token and (newly
> > created) AGIOS-190 AuthzService to catch up with you guys.
> >
> > ++
> > Corinne
> >
> > [1] https://github.com/secondsun/aerogear-android-oauth2-demo
> > [2]
> > https://github.com/aerogear/aerogear-ios-cookbook/blob/master/GoogleDrive/GoogleDrive.md#google-setup-optional
> > [3] https://issues.jboss.org/browse/AGIOS-188
> >
> > On 27 Apr 2014, at 08:55, Corinne Krych <corinnekrych at gmail.com> wrote:
> >
> >>
> >> Yep same here i'd love to review it an compare with iOS version. I'll
> >> send feedback next week too.
> >> ++
> >> Corinne
> >>
> >> On Friday, April 25, 2014, Bruno Oliveira <bruno at abstractj.org> wrote:
> >> Hi Summers, not sure about the timing. But I would like to review on the
> >> next week.
> >>
> >> On 2014-04-24, Summers Pittman wrote:
> >>>
> >>>
> >>> https://github.com/aerogear/aerogear-android/pull/146
> >>>
> >>> This PR is 1) big and 2) incomplete
> >>> (https://issues.jboss.org/browse/AGDROID/component/12319553). However,
> >>> it represents a certain set of functionality and I want to get
> >>> feedback/cleanup/merge before I continue making it even bigger.
> >>>
> >>> I would be EXCITED if someone can review this monster. If it needs to
> >>> be cut up and submitted piecemeal to make it more digestible I will also
> >>> take feedback on how to do that.
> >>>
> >>> Summers
> >>>
> >>> --
> >>> 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
> >>
> >>
> >> --
> >>
> >> 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
>
>
>
> --
> 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

--

abstractj

From corinnekrych at gmail.com  Mon May  5 12:10:54 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Mon, 5 May 2014 18:10:54 +0200
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <20140505155626.GA23951@abstractj.org>
References: <53595702.90900@redhat.com> <20140425213755.GB36605@abstractj.org>
	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
	<53678B8C.3070105@redhat.com>
	<20140505155626.GA23951@abstractj.org>
Message-ID: <D755A71A-33A5-411A-BED7-74B1FA982607@gmail.com>


On 05 May 2014, at 17:56, Bruno Oliveira <bruno at abstractj.org> wrote:

> On 2014-05-05, Summers Pittman wrote:
>> On Mon 05 May 2014 08:36:59 AM EDT, Corinne Krych wrote:
>>> 
>>> 2. Android version is now definitively ahead of iOS one ;) as you?ve
>>> implemented refresh token but configuration is very alike for the
>>> naming etc? +1
>>> 
>>> 3. I like AuthzSevice idea where we store the tokens for easier
>>> automatic refresh. Most end-user app will ask for grant only once so
>>> such a service that retieve and check validity of token is needed;
>>> - But, what about making it configurable to leave the option to store
>>> or not to store tokens?
>> Seems like it is somewhat related to this :
>> https://issues.jboss.org/browse/AGDROID-241
>> 
>> Perhaps the jira should be to make storage configurable.  If we wanted
>> to explicitly NOT store then we could make a dummy Store which just
>> routed everything to /dev/null.
> 
> What's the real need behind store those tokens?

It?s useful (more UX friendly I guess) to ask only once if you want to grant access to this third party app. It?s a common pattern in application like GoogleDrive.
I?ve seen app that stores those token in KeyChain

> If is really necessary,
> that's ok, otherwise let's do not store it. Offline, OAuth2 tokens are
> useless.
> 
> Or add an option to choose between store or not store like mentioned
> here.

+1
Definitively have it optional 

> 
>>> - The storage for refresh token should be more secure either encrypted
>>> storage with ag-crypto or keychain/keystore. wdyt?
>> See above
> 
> Encryption won't fix this, worse, will add an extra level of complexity
> to the application. Let's think about it, what do we need for
> encryption?
> 
> 1. Generate a private key
> 2. If it doesn't have a password is worthless (for local storage)
> 3. Alright, is password based, let's encrypt everything now
> 4. Now at every inclusion of tokens, you prompt users for the password
> 
> They would remember your name forever sometimes attached to bad names.
> IMO my suggestion is:
> 
> 1. Leave it as is and never allow to store in any kind of external storage
> 2. Do not store (+1)
> 2. Cache and destroy it when the application is closed
> 4. Use encryption and make the whole application more complex


what about storing them in Keychain/Keystore?


> 
>>> 
>>> 4. not sure about what is the purpose of AdditionalAuthorizationParams
>>> in AuthzConfig?
>> So the OAuth2 spec isn't implemented very well.  As an example to get a
>> refresh token from google you have to pass the parameter "access_type"
>> with a value "offline".  This is not part of the spec per se.
>>> 
>>> 5. Obviously as you said more work need to be done for removing token,
>>> Authorizer..
>>> for iOs we have an epic AGIOS-188 [3] for all Oauth2 work. Checking
>>> Android tickets, I was a bit surprised by AGDROID-244 and AGDROID-242,
>>> does it mean support for OAuth?
>> I would like it.  After the PR is merged passos and I should have this
>> scheduled.  I am sure these will not be a priority but it is a nice to have.
>>> 
>>> Good work! Need to look into AGIOS-145 refresh token and (newly
>>> created) AGIOS-190 AuthzService to catch up with you guys.
>>> 
>>> ++
>>> Corinne
>>> 
>>> [1] https://github.com/secondsun/aerogear-android-oauth2-demo
>>> [2]
>>> https://github.com/aerogear/aerogear-ios-cookbook/blob/master/GoogleDrive/GoogleDrive.md#google-setup-optional
>>> [3] https://issues.jboss.org/browse/AGIOS-188
>>> 
>>> On 27 Apr 2014, at 08:55, Corinne Krych <corinnekrych at gmail.com> wrote:
>>> 
>>>> 
>>>> Yep same here i'd love to review it an compare with iOS version. I'll
>>>> send feedback next week too.
>>>> ++
>>>> Corinne
>>>> 
>>>> On Friday, April 25, 2014, Bruno Oliveira <bruno at abstractj.org> wrote:
>>>> Hi Summers, not sure about the timing. But I would like to review on the
>>>> next week.
>>>> 
>>>> On 2014-04-24, Summers Pittman wrote:
>>>>> 
>>>>> 
>>>>> https://github.com/aerogear/aerogear-android/pull/146
>>>>> 
>>>>> This PR is 1) big and 2) incomplete
>>>>> (https://issues.jboss.org/browse/AGDROID/component/12319553). However,
>>>>> it represents a certain set of functionality and I want to get
>>>>> feedback/cleanup/merge before I continue making it even bigger.
>>>>> 
>>>>> I would be EXCITED if someone can review this monster. If it needs to
>>>>> be cut up and submitted piecemeal to make it more digestible I will also
>>>>> take feedback on how to do that.
>>>>> 
>>>>> Summers
>>>>> 
>>>>> --
>>>>> 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
>>>> 
>>>> 
>>>> --
>>>> 
>>>> 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
>> 
>> 
>> 
>> --
>> 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
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From kpiwko at redhat.com  Mon May  5 12:04:59 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Mon, 5 May 2014 18:04:59 +0200
Subject: [aerogear-dev] Replace Factory by Registrations
In-Reply-To: <CAKjsGbu4275p7X75j0z=e0dWQ8NAz-UQb8iM5s_1AzpLrk_m-w@mail.gmail.com>
References: <CAKjsGbu4275p7X75j0z=e0dWQ8NAz-UQb8iM5s_1AzpLrk_m-w@mail.gmail.com>
Message-ID: <20140505180459.7c5c100c@kapy-ntb-x220>

Do you guys plan to only replace factory pattern by registrations or also
include second part of the Tadeas' proposal - making generics a first class
citizen of API?

Thanks,

Karel

On Mon, 5 May 2014 10:40:07 -0300
Daniel Passos <daniel at passos.me> wrote:

> A long time ago Tadeas Kriz had a awesome idea to kill the ugly factory and
> replace it for registrations[1]. Summers and I have been thinking about it
> and we'd like to replace it in 2.0. So, we are starting the new agdroid
> library for offline and we'd like start it using registrations[2] instead
> Factory.
> 
> Wdyt? [1] https://gist.github.com/TadeasKriz/e0f5583e2a24c32dc253 [2]
> https://gist.github.com/danielpassos/088498b553699f23ff51


From daniel at passos.me  Mon May  5 12:32:55 2014
From: daniel at passos.me (Daniel Passos)
Date: Mon, 5 May 2014 13:32:55 -0300
Subject: [aerogear-dev] Replace Factory by Registrations
In-Reply-To: <20140505180459.7c5c100c@kapy-ntb-x220>
References: <CAKjsGbu4275p7X75j0z=e0dWQ8NAz-UQb8iM5s_1AzpLrk_m-w@mail.gmail.com>
	<20140505180459.7c5c100c@kapy-ntb-x220>
Message-ID: <CAKjsGbt+4rayLvoruQu17fePqjvYiUZeYVWP75dNSSrjDa7bgg@mail.gmail.com>

On Mon, May 5, 2014 at 1:04 PM, Karel Piwko <kpiwko at redhat.com> wrote:

> Do you guys plan to only replace factory pattern by registrations or also
> include second part of the Tadeas' proposal - making generics a first class
> citizen of API?
>

Both. Registrations and making (but not so) generics a first class citizen

Take a look of this example[1].

[1] https://gist.github.com/danielpassos/088498b553699f23ff51


> Thanks,
>
> Karel
>
> On Mon, 5 May 2014 10:40:07 -0300
> Daniel Passos <daniel at passos.me> wrote:
>
> > A long time ago Tadeas Kriz had a awesome idea to kill the ugly factory
> and
> > replace it for registrations[1]. Summers and I have been thinking about
> it
> > and we'd like to replace it in 2.0. So, we are starting the new agdroid
> > library for offline and we'd like start it using registrations[2] instead
> > Factory.
> >
> > Wdyt? [1] https://gist.github.com/TadeasKriz/e0f5583e2a24c32dc253 [2]
> > https://gist.github.com/danielpassos/088498b553699f23ff51
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140505/79c6cfda/attachment.html 

From bruno at abstractj.org  Mon May  5 12:40:51 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 5 May 2014 13:40:51 -0300
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <D755A71A-33A5-411A-BED7-74B1FA982607@gmail.com>
References: <53595702.90900@redhat.com> <20140425213755.GB36605@abstractj.org>
	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
	<53678B8C.3070105@redhat.com>
	<20140505155626.GA23951@abstractj.org>
	<D755A71A-33A5-411A-BED7-74B1FA982607@gmail.com>
Message-ID: <20140505164051.GA34416@abstractj.org>

Hi Corinne, answers inline

On 2014-05-05, Corinne Krych wrote:
>
> On 05 May 2014, at 17:56, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > On 2014-05-05, Summers Pittman wrote:
> >> On Mon 05 May 2014 08:36:59 AM EDT, Corinne Krych wrote:
> >>> 3. I like AuthzSevice idea where we store the tokens for easier
> >>> automatic refresh. Most end-user app will ask for grant only once so
> >>> such a service that retieve and check validity of token is needed;
> >>> - But, what about making it configurable to leave the option to store
> >>> or not to store tokens?
> >> Seems like it is somewhat related to this :
> >> https://issues.jboss.org/browse/AGDROID-241
> >>
> >> Perhaps the jira should be to make storage configurable.  If we wanted
> >> to explicitly NOT store then we could make a dummy Store which just
> >> routed everything to /dev/null.
> >
> > What's the real need behind store those tokens?
>
> It?s useful (more UX friendly I guess) to ask only once if you want to grant access to this third party app. It?s a common pattern in application like GoogleDrive.
> I?ve seen app that stores those token in KeyChain

I can be wrong, but to open the KeyChain or Keystore a password is
required. How the workflow would look like? Or the plan is to set an
empty password?

>
> > If is really necessary,
> > that's ok, otherwise let's do not store it. Offline, OAuth2 tokens are
> > useless.
> >
> > Or add an option to choose between store or not store like mentioned
> > here.
>
> +1
> Definitively have it optional
>
> >
> >>> - The storage for refresh token should be more secure either encrypted
> >>> storage with ag-crypto or keychain/keystore. wdyt?
> >> See above
> >
> > Encryption won't fix this, worse, will add an extra level of complexity
> > to the application. Let's think about it, what do we need for
> > encryption?
> >
> > 1. Generate a private key
> > 2. If it doesn't have a password is worthless (for local storage)
> > 3. Alright, is password based, let's encrypt everything now
> > 4. Now at every inclusion of tokens, you prompt users for the password
> >
> > They would remember your name forever sometimes attached to bad names.
> > IMO my suggestion is:
> >
> > 1. Leave it as is and never allow to store in any kind of external storage
> > 2. Do not store (+1)
> > 2. Cache and destroy it when the application is closed
> > 4. Use encryption and make the whole application more complex
>
>
> what about storing them in Keychain/Keystore?

Please, see my question above.


--

abstractj

From kpiwko at redhat.com  Mon May  5 12:56:00 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Mon, 5 May 2014 18:56:00 +0200
Subject: [aerogear-dev] Replace Factory by Registrations
In-Reply-To: <CAKjsGbt+4rayLvoruQu17fePqjvYiUZeYVWP75dNSSrjDa7bgg@mail.gmail.com>
References: <CAKjsGbu4275p7X75j0z=e0dWQ8NAz-UQb8iM5s_1AzpLrk_m-w@mail.gmail.com>
	<20140505180459.7c5c100c@kapy-ntb-x220>
	<CAKjsGbt+4rayLvoruQu17fePqjvYiUZeYVWP75dNSSrjDa7bgg@mail.gmail.com>
Message-ID: <20140505185600.03aca70f@kapy-ntb-x220>

On Mon, 5 May 2014 13:32:55 -0300
Daniel Passos <daniel at passos.me> wrote:

> On Mon, May 5, 2014 at 1:04 PM, Karel Piwko <kpiwko at redhat.com> wrote:
> 
> > Do you guys plan to only replace factory pattern by registrations or also
> > include second part of the Tadeas' proposal - making generics a first class
> > citizen of API?
> >
> 
> Both. Registrations and making (but not so) generics a first class citizen
> 
> Take a look of this example[1].

Awesome! I've seen gist that but I wasn't quite sure.

> 
> [1] https://gist.github.com/danielpassos/088498b553699f23ff51
> 
> 
> > Thanks,
> >
> > Karel
> >
> > On Mon, 5 May 2014 10:40:07 -0300
> > Daniel Passos <daniel at passos.me> wrote:
> >
> > > A long time ago Tadeas Kriz had a awesome idea to kill the ugly factory
> > and
> > > replace it for registrations[1]. Summers and I have been thinking about
> > it
> > > and we'd like to replace it in 2.0. So, we are starting the new agdroid
> > > library for offline and we'd like start it using registrations[2] instead
> > > Factory.
> > >
> > > Wdyt? [1] https://gist.github.com/TadeasKriz/e0f5583e2a24c32dc253 [2]
> > > https://gist.github.com/danielpassos/088498b553699f23ff51
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >


From supittma at redhat.com  Mon May  5 12:57:55 2014
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 05 May 2014 12:57:55 -0400
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <20140505164051.GA34416@abstractj.org>
References: <53595702.90900@redhat.com>
	<20140425213755.GB36605@abstractj.org>	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>	<53678B8C.3070105@redhat.com>	<20140505155626.GA23951@abstractj.org>	<D755A71A-33A5-411A-BED7-74B1FA982607@gmail.com>
	<20140505164051.GA34416@abstractj.org>
Message-ID: <5367C313.1000804@redhat.com>

Corinne, Bruno, see reply inline.

On 05/05/2014 12:40 PM, Bruno Oliveira wrote:
> Hi Corinne, answers inline
>
> On 2014-05-05, Corinne Krych wrote:
>> On 05 May 2014, at 17:56, Bruno Oliveira <bruno at abstractj.org> wrote:
>>
>>> On 2014-05-05, Summers Pittman wrote:
>>>> On Mon 05 May 2014 08:36:59 AM EDT, Corinne Krych wrote:
>>>>> 3. I like AuthzSevice idea where we store the tokens for easier
>>>>> automatic refresh. Most end-user app will ask for grant only once so
>>>>> such a service that retieve and check validity of token is needed;
>>>>> - But, what about making it configurable to leave the option to store
>>>>> or not to store tokens?
>>>> Seems like it is somewhat related to this :
>>>> https://issues.jboss.org/browse/AGDROID-241
>>>>
>>>> Perhaps the jira should be to make storage configurable.  If we wanted
>>>> to explicitly NOT store then we could make a dummy Store which just
>>>> routed everything to /dev/null.
>>> What's the real need behind store those tokens?
>> It?s useful (more UX friendly I guess) to ask only once if you want to grant access to this third party app. It?s a common pattern in application like GoogleDrive.
>> I?ve seen app that stores those token in KeyChain
What Corrine said.  It is considered a bad experience to always ask for 
authorization.  Also this let's us have things stay in the background 
without always have to reauthorize.

Doubly also is that refresh tokens must be stored long term.
> I can be wrong, but to open the KeyChain or Keystore a password is
> required. How the workflow would look like? Or the plan is to set an
> empty password?
>
>>> If is really necessary,
>>> that's ok, otherwise let's do not store it. Offline, OAuth2 tokens are
>>> useless.
>>>
>>> Or add an option to choose between store or not store like mentioned
>>> here.
>> +1
>> Definitively have it optional
I'm fine with optional.  Though I think storing them should be the 
default behavior.
>>
>>>>> - The storage for refresh token should be more secure either encrypted
>>>>> storage with ag-crypto or keychain/keystore. wdyt?
>>>> See above
>>> Encryption won't fix this, worse, will add an extra level of complexity
>>> to the application. Let's think about it, what do we need for
>>> encryption?
>>>
>>> 1. Generate a private key
>>> 2. If it doesn't have a password is worthless (for local storage)
>>> 3. Alright, is password based, let's encrypt everything now
>>> 4. Now at every inclusion of tokens, you prompt users for the password
>>>
>>> They would remember your name forever sometimes attached to bad names.
>>> IMO my suggestion is:
>>>
>>> 1. Leave it as is and never allow to store in any kind of external storage
>>> 2. Do not store (+1)
>>> 2. Cache and destroy it when the application is closed
>>> 4. Use encryption and make the whole application more complex
>>
>> what about storing them in Keychain/Keystore?
> Please, see my question above.
My idea for this was lean on the crypto APIs to prompt for a 
password/passphrase when it is appropriate.

Since the refresh token (and to a lesser extend the access token) can be 
used to gain access to everything the app could it would be a nice 
feature to keep it stored encrypted to keep it safe from pesky file dumpers.
>
>
> --
>
> abstractj
> _______________________________________________
> 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 May  5 15:15:45 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 5 May 2014 16:15:45 -0300
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <5367C313.1000804@redhat.com>
References: <53595702.90900@redhat.com> <20140425213755.GB36605@abstractj.org>
	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
	<53678B8C.3070105@redhat.com>
	<20140505155626.GA23951@abstractj.org>
	<D755A71A-33A5-411A-BED7-74B1FA982607@gmail.com>
	<20140505164051.GA34416@abstractj.org>
	<5367C313.1000804@redhat.com>
Message-ID: <20140505191545.GB42885@abstractj.org>

Hi Summers, I totally understand the need to store. Just don't know how
the application will behave when token is required. Why?

Because you need to prompt for the password to decrypt. Btw I think it's
not a priority right now, correct? And also, make sure that offline spec
meet your needs, is important to avoid overlappings.

On 2014-05-05, Summers Pittman wrote:
> Corinne, Bruno, see reply inline.
>
> On 05/05/2014 12:40 PM, Bruno Oliveira wrote:
> > Hi Corinne, answers inline
> >
> > On 2014-05-05, Corinne Krych wrote:
> >> On 05 May 2014, at 17:56, Bruno Oliveira <bruno at abstractj.org> wrote:
> >>
> >>> On 2014-05-05, Summers Pittman wrote:
> >>>> On Mon 05 May 2014 08:36:59 AM EDT, Corinne Krych wrote:
> >>>>> 3. I like AuthzSevice idea where we store the tokens for easier
> >>>>> automatic refresh. Most end-user app will ask for grant only once so
> >>>>> such a service that retieve and check validity of token is needed;
> >>>>> - But, what about making it configurable to leave the option to store
> >>>>> or not to store tokens?
> >>>> Seems like it is somewhat related to this :
> >>>> https://issues.jboss.org/browse/AGDROID-241
> >>>>
> >>>> Perhaps the jira should be to make storage configurable.  If we wanted
> >>>> to explicitly NOT store then we could make a dummy Store which just
> >>>> routed everything to /dev/null.
> >>> What's the real need behind store those tokens?
> >> It?s useful (more UX friendly I guess) to ask only once if you want to grant access to this third party app. It?s a common pattern in application like GoogleDrive.
> >> I?ve seen app that stores those token in KeyChain
> What Corrine said.  It is considered a bad experience to always ask for
> authorization.  Also this let's us have things stay in the background
> without always have to reauthorize.
>
> Doubly also is that refresh tokens must be stored long term.
> > I can be wrong, but to open the KeyChain or Keystore a password is
> > required. How the workflow would look like? Or the plan is to set an
> > empty password?
> >
> >>> If is really necessary,
> >>> that's ok, otherwise let's do not store it. Offline, OAuth2 tokens are
> >>> useless.
> >>>
> >>> Or add an option to choose between store or not store like mentioned
> >>> here.
> >> +1
> >> Definitively have it optional
> I'm fine with optional.  Though I think storing them should be the
> default behavior.
> >>
> >>>>> - The storage for refresh token should be more secure either encrypted
> >>>>> storage with ag-crypto or keychain/keystore. wdyt?
> >>>> See above
> >>> Encryption won't fix this, worse, will add an extra level of complexity
> >>> to the application. Let's think about it, what do we need for
> >>> encryption?
> >>>
> >>> 1. Generate a private key
> >>> 2. If it doesn't have a password is worthless (for local storage)
> >>> 3. Alright, is password based, let's encrypt everything now
> >>> 4. Now at every inclusion of tokens, you prompt users for the password
> >>>
> >>> They would remember your name forever sometimes attached to bad names.
> >>> IMO my suggestion is:
> >>>
> >>> 1. Leave it as is and never allow to store in any kind of external storage
> >>> 2. Do not store (+1)
> >>> 2. Cache and destroy it when the application is closed
> >>> 4. Use encryption and make the whole application more complex
> >>
> >> what about storing them in Keychain/Keystore?
> > Please, see my question above.
> My idea for this was lean on the crypto APIs to prompt for a
> password/passphrase when it is appropriate.
>
> Since the refresh token (and to a lesser extend the access token) can be
> used to gain access to everything the app could it would be a nice
> feature to keep it stored encrypted to keep it safe from pesky file dumpers.
> >
> >
> > --
> >
> > abstractj
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj

From supittma at redhat.com  Mon May  5 16:32:56 2014
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 05 May 2014 16:32:56 -0400
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <20140505191545.GB42885@abstractj.org>
References: <53595702.90900@redhat.com> <20140425213755.GB36605@abstractj.org>
	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
	<53678B8C.3070105@redhat.com>
	<20140505155626.GA23951@abstractj.org>
	<D755A71A-33A5-411A-BED7-74B1FA982607@gmail.com>
	<20140505164051.GA34416@abstractj.org>
	<5367C313.1000804@redhat.com>
	<20140505191545.GB42885@abstractj.org>
Message-ID: <5367F578.2010703@redhat.com>

On Mon 05 May 2014 03:15:45 PM EDT, Bruno Oliveira wrote:
>
> Hi Summers, I totally understand the need to store. Just don't know how
> the application will behave when token is required. Why?
I'll try to answer with an example and feel free to interrupt me if I 
misunderstood you.

User Authorizes and all the appropriate tokens are stored in the 
AuthzService
User schedules a pipe to download something in the future.

In the future Pipe.read fires, but the token is expired.

The Pipe's onFailure method is called with a (hopefully) useful 
exception.  The user can refresh the auth token and retry, fire up a 
notification to say "User stuff went sidesways" or just crash (a 
personal favorite of mine).

>
> Because you need to prompt for the password to decrypt. Btw I think it's
> not a priority right now, correct? 
Right. Here is the relevant JIRA : 
https://issues.jboss.org/browse/AGDROID-241?jql=project%20%3D%20AGDROID%20AND%20component%20%3D%20authorization
> And also, make sure that offline spec
> meet your needs, is important to avoid overlappings.
Yeah.  The offline spec may be more useful for some parts of this.
>
> On 2014-05-05, Summers Pittman wrote:
>>
>> Corinne, Bruno, see reply inline.
>>
>> On 05/05/2014 12:40 PM, Bruno Oliveira wrote:
>>>
>>> Hi Corinne, answers inline
>>>
>>> On 2014-05-05, Corinne Krych wrote:
>>>>
>>>> On 05 May 2014, at 17:56, Bruno Oliveira <bruno at abstractj.org> wrote:
>>>>
>>>>>
>>>>> On 2014-05-05, Summers Pittman wrote:
>>>>>>
>>>>>> On Mon 05 May 2014 08:36:59 AM EDT, Corinne Krych wrote:
>>>>>>>
>>>>>>> 3. I like AuthzSevice idea where we store the tokens for easier
>>>>>>> automatic refresh. Most end-user app will ask for grant only once so
>>>>>>> such a service that retieve and check validity of token is needed;
>>>>>>> - But, what about making it configurable to leave the option to 
>>>>>>> store
>>>>>>> or not to store tokens?
>>>>>>
>>>>>> Seems like it is somewhat related to this :
>>>>>> https://issues.jboss.org/browse/AGDROID-241
>>>>>>
>>>>>> Perhaps the jira should be to make storage configurable. If we wanted
>>>>>> to explicitly NOT store then we could make a dummy Store which just
>>>>>> routed everything to /dev/null.
>>>>>
>>>>> What's the real need behind store those tokens?
>>>>
>>>> It?s useful (more UX friendly I guess) to ask only once if you want 
>>>> to grant access to this third party app. It?s a common pattern in 
>>>> application like GoogleDrive.
>>>> I?ve seen app that stores those token in KeyChain
>>>
>>
>> What Corrine said. It is considered a bad experience to always ask for
>> authorization. Also this let's us have things stay in the background
>> without always have to reauthorize.
>>
>> Doubly also is that refresh tokens must be stored long term.
>>>
>>> I can be wrong, but to open the KeyChain or Keystore a password is
>>> required. How the workflow would look like? Or the plan is to set an
>>> empty password?
>>>
>>>>
>>>>>
>>>>> If is really necessary,
>>>>> that's ok, otherwise let's do not store it. Offline, OAuth2 tokens are
>>>>> useless.
>>>>>
>>>>> Or add an option to choose between store or not store like mentioned
>>>>> here.
>>>>
>>>> +1
>>>> Definitively have it optional
>>>
>>
>> I'm fine with optional. Though I think storing them should be the
>> default behavior.
>>>
>>>>
>>>>
>>>>>
>>>>>>
>>>>>>>
>>>>>>> - The storage for refresh token should be more secure either 
>>>>>>> encrypted
>>>>>>> storage with ag-crypto or keychain/keystore. wdyt?
>>>>>>
>>>>>> See above
>>>>>
>>>>> Encryption won't fix this, worse, will add an extra level of 
>>>>> complexity
>>>>> to the application. Let's think about it, what do we need for
>>>>> encryption?
>>>>>
>>>>> 1. Generate a private key
>>>>> 2. If it doesn't have a password is worthless (for local storage)
>>>>> 3. Alright, is password based, let's encrypt everything now
>>>>> 4. Now at every inclusion of tokens, you prompt users for the password
>>>>>
>>>>> They would remember your name forever sometimes attached to bad names.
>>>>> IMO my suggestion is:
>>>>>
>>>>> 1. Leave it as is and never allow to store in any kind of external 
>>>>> storage
>>>>> 2. Do not store (+1)
>>>>> 2. Cache and destroy it when the application is closed
>>>>> 4. Use encryption and make the whole application more complex
>>>>
>>>>
>>>> what about storing them in Keychain/Keystore?
>>>
>>> Please, see my question above.
>>
>> My idea for this was lean on the crypto APIs to prompt for a
>> password/passphrase when it is appropriate.
>>
>> Since the refresh token (and to a lesser extend the access token) can be
>> used to gain access to everything the app could it would be a nice
>> feature to keep it stored encrypted to keep it safe from pesky file 
>> dumpers.
>>>
>>>
>>>
>>> --
>>>
>>> abstractj
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Summers Pittman
>>>
>>>>
>>>> Phone:404 941 4698
>>>> Java is my crack.
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> _______________________________________________
> 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 corinnekrych at gmail.com  Mon May  5 17:25:23 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Mon, 5 May 2014 23:25:23 +0200
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <5367F578.2010703@redhat.com>
References: <53595702.90900@redhat.com> <20140425213755.GB36605@abstractj.org>
	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
	<53678B8C.3070105@redhat.com>
	<20140505155626.GA23951@abstractj.org>
	<D755A71A-33A5-411A-BED7-74B1FA982607@gmail.com>
	<20140505164051.GA34416@abstractj.org>
	<5367C313.1000804@redhat.com>
	<20140505191545.GB42885@abstractj.org>
	<5367F578.2010703@redhat.com>
Message-ID: <FB217EF9-9A53-4AE1-8BE2-637A0D028563@gmail.com>

@summers, to me the default option should be to store refresh token at ?session? level (i.e.: in memory storage). that way renewal of access token can be done transparently without having to re-grant the app.
However if the developer choose permanent storage, we could propose encrypted storage which required password. Obviously as @abstractj mentioned it, we have the trade-off of password prompting which implies some constraints in workflow management. 
Password should be used once to store the refresh tokens and used at each start up of the app to retrieved refresh token from permanent storage to memory. 

++
Corinne

On 05 May 2014, at 22:32, Summers Pittman <supittma at redhat.com> wrote:

> On Mon 05 May 2014 03:15:45 PM EDT, Bruno Oliveira wrote:
>> 
>> Hi Summers, I totally understand the need to store. Just don't know how
>> the application will behave when token is required. Why?
> I'll try to answer with an example and feel free to interrupt me if I 
> misunderstood you.
> 
> User Authorizes and all the appropriate tokens are stored in the 
> AuthzService
> User schedules a pipe to download something in the future.
> 
> In the future Pipe.read fires, but the token is expired.
> 
> The Pipe's onFailure method is called with a (hopefully) useful 
> exception.  The user can refresh the auth token and retry, fire up a 
> notification to say "User stuff went sidesways" or just crash (a 
> personal favorite of mine).
> 
>> 
>> Because you need to prompt for the password to decrypt. Btw I think it's
>> not a priority right now, correct? 
> Right. Here is the relevant JIRA : 
> https://issues.jboss.org/browse/AGDROID-241?jql=project%20%3D%20AGDROID%20AND%20component%20%3D%20authorization
>> And also, make sure that offline spec
>> meet your needs, is important to avoid overlappings.
> Yeah.  The offline spec may be more useful for some parts of this.
>> 
>> On 2014-05-05, Summers Pittman wrote:
>>> 
>>> Corinne, Bruno, see reply inline.
>>> 
>>> On 05/05/2014 12:40 PM, Bruno Oliveira wrote:
>>>> 
>>>> Hi Corinne, answers inline
>>>> 
>>>> On 2014-05-05, Corinne Krych wrote:
>>>>> 
>>>>> On 05 May 2014, at 17:56, Bruno Oliveira <bruno at abstractj.org> wrote:
>>>>> 
>>>>>> 
>>>>>> On 2014-05-05, Summers Pittman wrote:
>>>>>>> 
>>>>>>> On Mon 05 May 2014 08:36:59 AM EDT, Corinne Krych wrote:
>>>>>>>> 
>>>>>>>> 3. I like AuthzSevice idea where we store the tokens for easier
>>>>>>>> automatic refresh. Most end-user app will ask for grant only once so
>>>>>>>> such a service that retieve and check validity of token is needed;
>>>>>>>> - But, what about making it configurable to leave the option to 
>>>>>>>> store
>>>>>>>> or not to store tokens?
>>>>>>> 
>>>>>>> Seems like it is somewhat related to this :
>>>>>>> https://issues.jboss.org/browse/AGDROID-241
>>>>>>> 
>>>>>>> Perhaps the jira should be to make storage configurable. If we wanted
>>>>>>> to explicitly NOT store then we could make a dummy Store which just
>>>>>>> routed everything to /dev/null.
>>>>>> 
>>>>>> What's the real need behind store those tokens?
>>>>> 
>>>>> It?s useful (more UX friendly I guess) to ask only once if you want 
>>>>> to grant access to this third party app. It?s a common pattern in 
>>>>> application like GoogleDrive.
>>>>> I?ve seen app that stores those token in KeyChain
>>>> 
>>> 
>>> What Corrine said. It is considered a bad experience to always ask for
>>> authorization. Also this let's us have things stay in the background
>>> without always have to reauthorize.
>>> 
>>> Doubly also is that refresh tokens must be stored long term.
>>>> 
>>>> I can be wrong, but to open the KeyChain or Keystore a password is
>>>> required. How the workflow would look like? Or the plan is to set an
>>>> empty password?
>>>> 
>>>>> 
>>>>>> 
>>>>>> If is really necessary,
>>>>>> that's ok, otherwise let's do not store it. Offline, OAuth2 tokens are
>>>>>> useless.
>>>>>> 
>>>>>> Or add an option to choose between store or not store like mentioned
>>>>>> here.
>>>>> 
>>>>> +1
>>>>> Definitively have it optional
>>>> 
>>> 
>>> I'm fine with optional. Though I think storing them should be the
>>> default behavior.
>>>> 
>>>>> 
>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>>> 
>>>>>>>> - The storage for refresh token should be more secure either 
>>>>>>>> encrypted
>>>>>>>> storage with ag-crypto or keychain/keystore. wdyt?
>>>>>>> 
>>>>>>> See above
>>>>>> 
>>>>>> Encryption won't fix this, worse, will add an extra level of 
>>>>>> complexity
>>>>>> to the application. Let's think about it, what do we need for
>>>>>> encryption?
>>>>>> 
>>>>>> 1. Generate a private key
>>>>>> 2. If it doesn't have a password is worthless (for local storage)
>>>>>> 3. Alright, is password based, let's encrypt everything now
>>>>>> 4. Now at every inclusion of tokens, you prompt users for the password
>>>>>> 
>>>>>> They would remember your name forever sometimes attached to bad names.
>>>>>> IMO my suggestion is:
>>>>>> 
>>>>>> 1. Leave it as is and never allow to store in any kind of external 
>>>>>> storage
>>>>>> 2. Do not store (+1)
>>>>>> 2. Cache and destroy it when the application is closed
>>>>>> 4. Use encryption and make the whole application more complex
>>>>> 
>>>>> 
>>>>> what about storing them in Keychain/Keystore?
>>>> 
>>>> Please, see my question above.
>>> 
>>> My idea for this was lean on the crypto APIs to prompt for a
>>> password/passphrase when it is appropriate.
>>> 
>>> Since the refresh token (and to a lesser extend the access token) can be
>>> used to gain access to everything the app could it would be a nice
>>> feature to keep it stored encrypted to keep it safe from pesky file 
>>> dumpers.
>>>> 
>>>> 
>>>> 
>>>> --
>>>> 
>>>> abstractj
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> 
>>> --
>>> Summers Pittman
>>>> 
>>>>> 
>>>>> Phone:404 941 4698
>>>>> Java is my crack.
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> --
>> 
>> abstractj
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Summers Pittman
>>> Phone:404 941 4698
>>> Java is my crack.
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From bruno at abstractj.org  Mon May  5 17:38:15 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 5 May 2014 18:38:15 -0300
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <5367F578.2010703@redhat.com>
References: <20140425213755.GB36605@abstractj.org>
	<CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
	<53678B8C.3070105@redhat.com>
	<20140505155626.GA23951@abstractj.org>
	<D755A71A-33A5-411A-BED7-74B1FA982607@gmail.com>
	<20140505164051.GA34416@abstractj.org>
	<5367C313.1000804@redhat.com>
	<20140505191545.GB42885@abstractj.org>
	<5367F578.2010703@redhat.com>
Message-ID: <20140505213815.GA62677@abstractj.org>

On 2014-05-05, Summers Pittman wrote:
> On Mon 05 May 2014 03:15:45 PM EDT, Bruno Oliveira wrote:
> >
> >Hi Summers, I totally understand the need to store. Just don't know how
> >the application will behave when token is required. Why?
> I'll try to answer with an example and feel free to interrupt me if I
> misunderstood you.
>
> User Authorizes and all the appropriate tokens are stored in the
> AuthzService
> User schedules a pipe to download something in the future.
>
> In the future Pipe.read fires, but the token is expired.
>
> The Pipe's onFailure method is called with a (hopefully) useful exception.
> The user can refresh the auth token and retry, fire up a notification to say
> "User stuff went sidesways" or just crash (a personal favorite of mine).

Only to be clear, no problem on storing access tokens or nor renewing
tokens. What I don't get is if you guys want to use encryption for some
reason, how it would look like to call for example some API.

I see the whole proposal into this way (I'm taking shortcuts here to go
straight to the point)

1. Get the access token
2. Reconstruct the private key based on some password provided
3. Encrypt access token

Now I want to send a request to my server

4. Require the password to reconstruct my private key
5. Decrypt it from the local storage or whatever
6. Send the HTTP request (I will just be lazy and copy
from google)


```
GET /youtube/v3/channels?part=id&mine=true HTTP/1.1
Host: www.googleapis.com
Authorization: Bearer 1/6BMfW9j53gdGImsixUH6kU5RsR4zwI9lUVX-tqf8JXQ&
```

Next login, if the token is the same, repeat the steps 4 to 6. What I'm
trying to say here is: password-based encryption will hurt your
usability, we must think about temporary keys instead of request the
password everytime I need to send a request to the server.

Yep, I know these tokens will be renewed. But you need the previous one
to request a new token.

--

abstractj

From bruno at abstractj.org  Mon May  5 17:40:51 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 5 May 2014 18:40:51 -0300
Subject: [aerogear-dev] Android OAuth2 PR
In-Reply-To: <FB217EF9-9A53-4AE1-8BE2-637A0D028563@gmail.com>
References: <CAL8vO=d2OS=4LTcQ0s6WkoR44uHA1k_8sy-OYNXncrBz49vwRA@mail.gmail.com>
	<E32C9A74-DF1F-4561-A357-6A6AEF0EF0C2@gmail.com>
	<53678B8C.3070105@redhat.com>
	<20140505155626.GA23951@abstractj.org>
	<D755A71A-33A5-411A-BED7-74B1FA982607@gmail.com>
	<20140505164051.GA34416@abstractj.org>
	<5367C313.1000804@redhat.com>
	<20140505191545.GB42885@abstractj.org>
	<5367F578.2010703@redhat.com>
	<FB217EF9-9A53-4AE1-8BE2-637A0D028563@gmail.com>
Message-ID: <20140505214051.GB62677@abstractj.org>

My 2 cents,

+1 on it and call it a day

On 2014-05-05, Corinne Krych wrote:
> @summers, to me the default option should be to store refresh token at ?session? level (i.e.: in memory storage). that way renewal of access token can be done transparently without having to re-grant the app.
> However if the developer choose permanent storage, we could propose encrypted storage which required password. Obviously as @abstractj mentioned it, we have the trade-off of password prompting which implies some constraints in workflow management.
> Password should be used once to store the refresh tokens and used at each start up of the app to retrieved refresh token from permanent storage to memory.

--

abstractj

From scm.blanc at gmail.com  Tue May  6 03:10:29 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 6 May 2014 09:10:29 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <5639DBE5-69E0-4C06-8F9C-AAFD8105E140@gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>
	<2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>
	<5639DBE5-69E0-4C06-8F9C-AAFD8105E140@gmail.com>
Message-ID: <CAD_dpu2GZ32kteN+xmGkipqMJK7T7i-UnN7qa_8r6GfGNhFVkg@mail.gmail.com>

Anyone else ?
If we all agree I can adapt the temporary backend I deployed including this
new behaviour.

Sebi



On Mon, May 5, 2014 at 9:34 AM, Christos Vasilakis <cvasilak at gmail.com>wrote:

> Hi,
>
> answers inline
>
> On May 2, 2014, at 11:37 PM, Jay Balunas <jbalunas at redhat.com> wrote:
>
> > I wanted to chime in here on additional/related items around the
> contacts use-case and specifically around how to integrate push.  Some of
> these have already been discussed so just getting in one place for my own
> sanity :-)
> >
> > 1) I agree that users and "contacts" are separate things.  I think it is
> best to think about them as was mentioned below - users (employees) and
> contacts (customers, leads, etc...).  This is easier to grok imo and could
> be helped by some simple wording in the UI.
>
> +1
>
>
> > Cons:
> > ** We then need a way to add "users" - otherwise we won't be sending
> many push messages.  Maybe users could be automatically created when an app
> first accesses the backend?
>
> already the backend provides endpoints for creation of ?users?, as well as
> a list of default users initialised once the app is first loaded. By
> default when a new user is created the security role assigned to it doesn?t
> allow the creation of new contacts,  you get back an ?Unauthorised? error.
> It doesn?t effect push per se, since an ?admin? user can create a contact
> and the notification can be send to all other users that are logged in, but
> we should document this behaviour.
>
> >
> > 2) Simplifying the push use-case:  If we change the use-case from saying
> hi to specific contacts to notifying all users when a new contact was
> created it could simplify not only the UI, but the server side processing
> for the push.  We could reserve the more specific push usage to the
> console, and/or AeroDoc.
> >
> > If we go with 2) we might be able to avoid the issues with 1) altogether
> because a broadcast would send to every app that has registered.
> >
> > Wdyt?
>
> I am +1 on this behaviour.  IMHO its more clear for the end-user and the
> actual notification is used to ?alert? for a change on the server part that
> the app can decided to respond (e.g. fetch the new contact list).
>
> Thanks,
> Christos
>
>
> >
> >
> > On May 1, 2014, at 10:46 AM, Burr Sutter <bsutter at redhat.com> wrote:
> >
> >> Joshua owns the backend, let's see if he has a thought on this item.
> >>
> >> On May 1, 2014, at 7:25 AM, Christos Vasilakis <cvasilak at gmail.com>
> wrote:
> >>
> >>> Hi everyone,
> >>>
> >>> have started working on the iOS native client of the contacts quick
> start app. Based on edewit branch[1] (which creates a contact on signup of
> a user) have created an initial version of the iOS client and you can find
> it here [2], together with a screencast showcasing the app in action [3].
> >>>
> >>> Some comments observed during writing of the application which would
> like your feedback:
> >>>
> >>> a)  for PUT, DELETE operations noticed that the jax-rs backend expects
> the id of the Contact to be present in the body of the request. Not sure
> why this was chosen instead of @Path(?id?) resulting against /contacts/{id}
> ?
> >>>
> >>> b) currently roles are used to distinguish between who is able to
> create/update/delete contact. When a user signs up (and contact is
> created),  by default the user is _not_ able to apply any CRUD operations
> apart from viewing (any operation results in unauthorised error). If we
> agree on this behaviour, would like to know how can I determine the role of
> the user (in order to update the UI accordingly, eg. disabling add,edit UI
> elements). Looking at the json response upon login of the user, couldn?t
> determine a ?key? that specifies the role (apart from an ?admin? key which
> stayed the same regardless of the type of the user).
> >>>
> >>>
> >>> Thanks,
> >>> Christos
> >>>
> >>> [1]
> https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
> >>> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
> >>> [3] https://vimeo.com/93471554
> >>>
> >>>
> >>>
> >>> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
> >>>
> >>>> Right, that makes sense, so let?s not join them. The alternate thing
> to do is to create a contact on sign up, because if you want to receive
> push notifications at least you should be in the list of contacts. We will
> still need to change the sign up page a little as we need a phone number
> and a birth date as well in order to create a contact.
> >>>>
> >>>> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com> wrote:
> >>>>
> >>>>> These are not strongly held opinions
> >>>>>
> >>>>> One reason to keep Users & Contacts separate is...because that is
> normal for the average enterprise app - your have employees (users) and
> customers (contacts) - employees/users have different roles/privileges from
> customers.
> >>>>>
> >>>>> The reason they are separated in the secured (PL) version of
> contacts-mobile-basic is because it simply evolved that way - contacts came
> first - users/roles added after the fact.   Ideally we would not modify the
> original too much as it allows a nice learning progression - start with the
> original contacts-mobile-basic, then upgrade to
> contacts-mobile-basic-secured, then upgrade to
> contacts-mobile-basic-secured-cordova (names just made up).
> >>>>>
> >>>>>
> >>>>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <scm.blanc at gmail.com>
> wrote:
> >>>>>
> >>>>>> Sure !
> >>>>>> Be sure to check this with Joshua as he drives the backend bits
> >>>>>> S?bi
> >>>>>>
> >>>>>> Envoy? de mon iPhone
> >>>>>>
> >>>>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a
> ?crit :
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> How about merging the User model and the Contact into one entity?
> Seems like they have a lot in common, do we really need 2?
> >>>>>>>
> >>>>>>> Cheers,
> >>>>>>> Erik Jan
> >>>>>>>
> >>>>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <scm.blanc at gmail.com>
> wrote:
> >>>>>>>>
> >>>>>>>> We should be using the email as alias and the email should also
> be used as login when registering in the secured part. A registration
> should also trigger the creation of that user / contact in the application.
> >>>>>>>> Author can be left empty By the client and filled by the backend
> .
> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthormust stay because the receiver must know who sends the message.
> >>>>>>>>
> >>>>>>>> Envoy? de mon iPhone
> >>>>>>>>
> >>>>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com> a
> ?crit :
> >>>>>>>>>
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> I was working on the aerogear-push-quickstarts for Cordova and
> was wondering what to put for the alias on registration. The version that
> is there now has users that logs in and contacts that are fetched. What
> seems to be missing is that everybody gets all contacts instead of just
> mine (maybe that is fine), but users that sign up for the app are not
> contacts. So when I want to send a message to a specific mobile user they
> are not in my list and there is no way to have to define an alias to send
> to.
> >>>>>>>>>
> >>>>>>>>> Also the interface for sending push notifications includes a
> author. I think it would be better if we remove this and let the service
> put in the logged in user. That way you can?t pretend to send a message
> like someone else.
> >>>>>>>>>
> >>>>>>>>> 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
> >>>>>>>
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> aerogear-dev mailing list
> >>>>>>> aerogear-dev at lists.jboss.org
> >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> aerogear-dev mailing list
> >>>>>> aerogear-dev at lists.jboss.org
> >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> aerogear-dev mailing list
> >>>>> aerogear-dev at lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.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/20140506/900537ac/attachment.html 

From matzew at apache.org  Tue May  6 04:51:35 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 May 2014 10:51:35 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <CAD_dpu2GZ32kteN+xmGkipqMJK7T7i-UnN7qa_8r6GfGNhFVkg@mail.gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>
	<2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>
	<5639DBE5-69E0-4C06-8F9C-AAFD8105E140@gmail.com>
	<CAD_dpu2GZ32kteN+xmGkipqMJK7T7i-UnN7qa_8r6GfGNhFVkg@mail.gmail.com>
Message-ID: <CAAg5f2RMOFGKgUvwoJ-TVVG+6pavtkxXaqqrQ18idDcU=uF7Fw@mail.gmail.com>

yes, sounds like 2) is the way to go


On Tue, May 6, 2014 at 9:10 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Anyone else ?
> If we all agree I can adapt the temporary backend I deployed including
> this new behaviour.
>
> Sebi
>
>
>
> On Mon, May 5, 2014 at 9:34 AM, Christos Vasilakis <cvasilak at gmail.com>wrote:
>
>> Hi,
>>
>> answers inline
>>
>> On May 2, 2014, at 11:37 PM, Jay Balunas <jbalunas at redhat.com> wrote:
>>
>> > I wanted to chime in here on additional/related items around the
>> contacts use-case and specifically around how to integrate push.  Some of
>> these have already been discussed so just getting in one place for my own
>> sanity :-)
>> >
>> > 1) I agree that users and "contacts" are separate things.  I think it
>> is best to think about them as was mentioned below - users (employees) and
>> contacts (customers, leads, etc...).  This is easier to grok imo and could
>> be helped by some simple wording in the UI.
>>
>> +1
>>
>>
>> > Cons:
>> > ** We then need a way to add "users" - otherwise we won't be sending
>> many push messages.  Maybe users could be automatically created when an app
>> first accesses the backend?
>>
>> already the backend provides endpoints for creation of ?users?, as well
>> as a list of default users initialised once the app is first loaded. By
>> default when a new user is created the security role assigned to it doesn?t
>> allow the creation of new contacts,  you get back an ?Unauthorised? error.
>> It doesn?t effect push per se, since an ?admin? user can create a contact
>> and the notification can be send to all other users that are logged in, but
>> we should document this behaviour.
>>
>> >
>> > 2) Simplifying the push use-case:  If we change the use-case from
>> saying hi to specific contacts to notifying all users when a new contact
>> was created it could simplify not only the UI, but the server side
>> processing for the push.  We could reserve the more specific push usage to
>> the console, and/or AeroDoc.
>> >
>> > If we go with 2) we might be able to avoid the issues with 1)
>> altogether because a broadcast would send to every app that has registered.
>> >
>> > Wdyt?
>>
>> I am +1 on this behaviour.  IMHO its more clear for the end-user and the
>> actual notification is used to ?alert? for a change on the server part that
>> the app can decided to respond (e.g. fetch the new contact list).
>>
>> Thanks,
>> Christos
>>
>>
>> >
>> >
>> > On May 1, 2014, at 10:46 AM, Burr Sutter <bsutter at redhat.com> wrote:
>> >
>> >> Joshua owns the backend, let's see if he has a thought on this item.
>> >>
>> >> On May 1, 2014, at 7:25 AM, Christos Vasilakis <cvasilak at gmail.com>
>> wrote:
>> >>
>> >>> Hi everyone,
>> >>>
>> >>> have started working on the iOS native client of the contacts quick
>> start app. Based on edewit branch[1] (which creates a contact on signup of
>> a user) have created an initial version of the iOS client and you can find
>> it here [2], together with a screencast showcasing the app in action [3].
>> >>>
>> >>> Some comments observed during writing of the application which would
>> like your feedback:
>> >>>
>> >>> a)  for PUT, DELETE operations noticed that the jax-rs backend
>> expects the id of the Contact to be present in the body of the request. Not
>> sure why this was chosen instead of @Path(?id?) resulting against
>> /contacts/{id} ?
>> >>>
>> >>> b) currently roles are used to distinguish between who is able to
>> create/update/delete contact. When a user signs up (and contact is
>> created),  by default the user is _not_ able to apply any CRUD operations
>> apart from viewing (any operation results in unauthorised error). If we
>> agree on this behaviour, would like to know how can I determine the role of
>> the user (in order to update the UI accordingly, eg. disabling add,edit UI
>> elements). Looking at the json response upon login of the user, couldn?t
>> determine a ?key? that specifies the role (apart from an ?admin? key which
>> stayed the same regardless of the type of the user).
>> >>>
>> >>>
>> >>> Thanks,
>> >>> Christos
>> >>>
>> >>> [1]
>> https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
>> >>> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
>> >>> [3] https://vimeo.com/93471554
>> >>>
>> >>>
>> >>>
>> >>> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com>
>> wrote:
>> >>>
>> >>>> Right, that makes sense, so let?s not join them. The alternate thing
>> to do is to create a contact on sign up, because if you want to receive
>> push notifications at least you should be in the list of contacts. We will
>> still need to change the sign up page a little as we need a phone number
>> and a birth date as well in order to create a contact.
>> >>>>
>> >>>> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com> wrote:
>> >>>>
>> >>>>> These are not strongly held opinions
>> >>>>>
>> >>>>> One reason to keep Users & Contacts separate is...because that is
>> normal for the average enterprise app - your have employees (users) and
>> customers (contacts) - employees/users have different roles/privileges from
>> customers.
>> >>>>>
>> >>>>> The reason they are separated in the secured (PL) version of
>> contacts-mobile-basic is because it simply evolved that way - contacts came
>> first - users/roles added after the fact.   Ideally we would not modify the
>> original too much as it allows a nice learning progression - start with the
>> original contacts-mobile-basic, then upgrade to
>> contacts-mobile-basic-secured, then upgrade to
>> contacts-mobile-basic-secured-cordova (names just made up).
>> >>>>>
>> >>>>>
>> >>>>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <scm.blanc at gmail.com>
>> wrote:
>> >>>>>
>> >>>>>> Sure !
>> >>>>>> Be sure to check this with Joshua as he drives the backend bits
>> >>>>>> S?bi
>> >>>>>>
>> >>>>>> Envoy? de mon iPhone
>> >>>>>>
>> >>>>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a
>> ?crit :
>> >>>>>>>
>> >>>>>>> Hi,
>> >>>>>>>
>> >>>>>>> How about merging the User model and the Contact into one entity?
>> Seems like they have a lot in common, do we really need 2?
>> >>>>>>>
>> >>>>>>> Cheers,
>> >>>>>>> Erik Jan
>> >>>>>>>
>> >>>>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <scm.blanc at gmail.com>
>> wrote:
>> >>>>>>>>
>> >>>>>>>> We should be using the email as alias and the email should also
>> be used as login when registering in the secured part. A registration
>> should also trigger the creation of that user / contact in the application.
>> >>>>>>>> Author can be left empty By the client and filled by the backend
>> .
>> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthormust stay because the receiver must know who sends the message.
>> >>>>>>>>
>> >>>>>>>> Envoy? de mon iPhone
>> >>>>>>>>
>> >>>>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com> a
>> ?crit :
>> >>>>>>>>>
>> >>>>>>>>> Hi,
>> >>>>>>>>>
>> >>>>>>>>> I was working on the aerogear-push-quickstarts for Cordova and
>> was wondering what to put for the alias on registration. The version that
>> is there now has users that logs in and contacts that are fetched. What
>> seems to be missing is that everybody gets all contacts instead of just
>> mine (maybe that is fine), but users that sign up for the app are not
>> contacts. So when I want to send a message to a specific mobile user they
>> are not in my list and there is no way to have to define an alias to send
>> to.
>> >>>>>>>>>
>> >>>>>>>>> Also the interface for sending push notifications includes a
>> author. I think it would be better if we remove this and let the service
>> put in the logged in user. That way you can?t pretend to send a message
>> like someone else.
>> >>>>>>>>>
>> >>>>>>>>> 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
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> _______________________________________________
>> >>>>>>> aerogear-dev mailing list
>> >>>>>>> aerogear-dev at lists.jboss.org
>> >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>>>>
>> >>>>>> _______________________________________________
>> >>>>>> aerogear-dev mailing list
>> >>>>>> aerogear-dev at lists.jboss.org
>> >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>>>
>> >>>>>
>> >>>>> _______________________________________________
>> >>>>> aerogear-dev mailing list
>> >>>>> aerogear-dev at lists.jboss.org
>> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>>
>> >>>>
>> >>>> _______________________________________________
>> >>>> aerogear-dev mailing list
>> >>>> aerogear-dev at lists.jboss.org
>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> aerogear-dev mailing list
>> >>> aerogear-dev at lists.jboss.org
>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>
>> >>
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >> aerogear-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140506/428bdffe/attachment-0001.html 

From scm.blanc at gmail.com  Tue May  6 05:47:20 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 6 May 2014 11:47:20 +0200
Subject: [aerogear-dev] AeroGear Android Push 0.1.1
In-Reply-To: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>
References: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>
Message-ID: <CAD_dpu2aOBdcuuY1VqoeyVR1De4gY6yREVqLuUou5zBzNGYV5g@mail.gmail.com>

Hi !
I just gave it a test with the Push HelloWorld :

- https://issues.jboss.org/browse/AGPUSH-627 is fixed , I'm getting a nice
error notification on the device

- https://issues.jboss.org/browse/AGDROID-214 -> I'm getting exactly the
same issue as Matzew , looks like the redirect is not working.

Sebi



On Fri, May 2, 2014 at 5:06 PM, Daniel Passos <daniel at passos.me> wrote:

> We have found a bug[1] in the AeroGear Android Push 0.1. It was fixed and
> the new version (0.1.1) was already sent to nexus[2].
>
> We'd like to ship it to Maven central next wednesday.
>
> [1] https://issues.jboss.org/browse/AGDROID-214
> [2]
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3139/
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140506/d7b729d2/attachment.html 

From matzew at apache.org  Tue May  6 05:49:39 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 May 2014 11:49:39 +0200
Subject: [aerogear-dev] Keycloak integration
Message-ID: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>

Hello folks!

Bill Burk was helping on the Keycloak front and besides fixing related
items on the Keycloak server, he also created an example that we can use as
a template for the actual integration. See [1]

In the past, Bruno and I did integrate w/ an external Keycloak server (see
[2]), and we did include the keycloak.json file (See [3]). Thanks to Bill's
work on Keycloak, the 'protected app' no longer needs that, see [4].
Also there is no more the need to customize the Keycloak Rest Application
(Stian and I did look into that as well).


Good news: This means the UPS can stay as it is -> no need to change
internals (e.g. the 'bundle all in one WAR file' did force us to change our
'/rest' URLs, as Keycloak uses them, see [5]).

Inside of our 'modular' Keycloak branch (see [2] again), we can apply the
work from Bill:
* our current 'server' module will use a listener similar to [4]
* create a "ups-auth" module similar to [6]

On the 'ups-auth module' there is one area where we need to have some
future improvement:
* testrealm.json -> needs to be in Java code, due to the URL being
hard-coded in there (we need to resolve the URL of the host, running the
bits). But, IMO for now that should be good enough.

Bruno did offer to help out on the Keycloak integration, so that I can go
back to the analytics and mertrics feature. Thanks abstractj!! <3

Greetings,
Matthias

[1]
https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
[2]
https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
[3]
https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
[4]
https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
[5]
https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
[6]
https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140506/f017e84f/attachment.html 

From corinnekrych at gmail.com  Tue May  6 05:59:43 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Tue, 6 May 2014 11:59:43 +0200
Subject: [aerogear-dev] Keycloak integration
In-Reply-To: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
References: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
Message-ID: <647EB099-5DC8-49D7-8F42-C9F991271B80@gmail.com>

Good work!

I wonder... It might be good to use the same integration for our OAuth2 server side demo in [1]
Here I used a KC server with realm.json configuration. Would it be possible/worth it to replace all the configuration with plain Java?

++
Corinne.
[1]  https://github.com/aerogear/aerogear-integration-tests-server/pull/4

On 06 May 2014, at 11:49, Matthias Wessendorf <matzew at apache.org> wrote:

> Hello folks!
> 
> Bill Burk was helping on the Keycloak front and besides fixing related items on the Keycloak server, he also created an example that we can use as a template for the actual integration. See [1]
> 
> In the past, Bruno and I did integrate w/ an external Keycloak server (see [2]), and we did include the keycloak.json file (See [3]). Thanks to Bill's work on Keycloak, the 'protected app' no longer needs that, see [4].
> Also there is no more the need to customize the Keycloak Rest Application (Stian and I did look into that as well).
> 
> 
> Good news: This means the UPS can stay as it is -> no need to change internals (e.g. the 'bundle all in one WAR file' did force us to change our '/rest' URLs, as Keycloak uses them, see [5]).
> 
> Inside of our 'modular' Keycloak branch (see [2] again), we can apply the work from Bill:
> * our current 'server' module will use a listener similar to [4]
> * create a "ups-auth" module similar to [6]
> 
> On the 'ups-auth module' there is one area where we need to have some future improvement:
> * testrealm.json -> needs to be in Java code, due to the URL being hard-coded in there (we need to resolve the URL of the host, running the bits). But, IMO for now that should be good enough.
> 
> Bruno did offer to help out on the Keycloak integration, so that I can go back to the analytics and mertrics feature. Thanks abstractj!! <3
> 
> Greetings,
> Matthias
> 
> [1] https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
> [2] https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
> [3] https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
> [4] https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
> [5] https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
> [6] https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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 May  6 07:04:00 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 May 2014 13:04:00 +0200
Subject: [aerogear-dev] Keycloak integration
In-Reply-To: <647EB099-5DC8-49D7-8F42-C9F991271B80@gmail.com>
References: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
	<647EB099-5DC8-49D7-8F42-C9F991271B80@gmail.com>
Message-ID: <CAAg5f2QRokJuxN66toZcc2W_X0YGAW6073hmjWP1U2MyJqTv6w@mail.gmail.com>

Yeah, sounds reasonable to me.



On Tuesday, May 6, 2014, Corinne Krych <corinnekrych at gmail.com> wrote:

> Good work!
>
> I wonder... It might be good to use the same integration for our OAuth2
> server side demo in [1]
> Here I used a KC server with realm.json configuration. Would it be
> possible/worth it to replace all the configuration with plain Java?
>
> ++
> Corinne.
> [1]  https://github.com/aerogear/aerogear-integration-tests-server/pull/4
>
> On 06 May 2014, at 11:49, Matthias Wessendorf <matzew at apache.org<javascript:;>>
> wrote:
>
> > Hello folks!
> >
> > Bill Burk was helping on the Keycloak front and besides fixing related
> items on the Keycloak server, he also created an example that we can use as
> a template for the actual integration. See [1]
> >
> > In the past, Bruno and I did integrate w/ an external Keycloak server
> (see [2]), and we did include the keycloak.json file (See [3]). Thanks to
> Bill's work on Keycloak, the 'protected app' no longer needs that, see [4].
> > Also there is no more the need to customize the Keycloak Rest
> Application (Stian and I did look into that as well).
> >
> >
> > Good news: This means the UPS can stay as it is -> no need to change
> internals (e.g. the 'bundle all in one WAR file' did force us to change our
> '/rest' URLs, as Keycloak uses them, see [5]).
> >
> > Inside of our 'modular' Keycloak branch (see [2] again), we can apply
> the work from Bill:
> > * our current 'server' module will use a listener similar to [4]
> > * create a "ups-auth" module similar to [6]
> >
> > On the 'ups-auth module' there is one area where we need to have some
> future improvement:
> > * testrealm.json -> needs to be in Java code, due to the URL being
> hard-coded in there (we need to resolve the URL of the host, running the
> bits). But, IMO for now that should be good enough.
> >
> > Bruno did offer to help out on the Keycloak integration, so that I can
> go back to the analytics and mertrics feature. Thanks abstractj!! <3
> >
> > Greetings,
> > Matthias
> >
> > [1]
> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
> > [2]
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
> > [3]
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
> > [4]
> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
> > [5]
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
> > [6]
> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org <javascript:;>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <javascript:;>
> 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/20140506/77d0c98d/attachment.html 

From matzew at apache.org  Tue May  6 07:31:52 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 May 2014 13:31:52 +0200
Subject: [aerogear-dev] Keycloak integration
In-Reply-To: <CAAg5f2QRokJuxN66toZcc2W_X0YGAW6073hmjWP1U2MyJqTv6w@mail.gmail.com>
References: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
	<647EB099-5DC8-49D7-8F42-C9F991271B80@gmail.com>
	<CAAg5f2QRokJuxN66toZcc2W_X0YGAW6073hmjWP1U2MyJqTv6w@mail.gmail.com>
Message-ID: <CAAg5f2RfiXFF+Z9deP4n9f3m-q3hUOQfqcaKi3JwkAMWNQQETA@mail.gmail.com>

Let's see how the UPS integration goes, before we have too much KC
integration fields, ok ?
Once we got that done, I guess we have a good experience on proper
integration

-M


On Tue, May 6, 2014 at 1:04 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> Yeah, sounds reasonable to me.
>
>
>
> On Tuesday, May 6, 2014, Corinne Krych <corinnekrych at gmail.com> wrote:
>
>> Good work!
>>
>> I wonder... It might be good to use the same integration for our OAuth2
>> server side demo in [1]
>> Here I used a KC server with realm.json configuration. Would it be
>> possible/worth it to replace all the configuration with plain Java?
>>
>> ++
>> Corinne.
>> [1]  https://github.com/aerogear/aerogear-integration-tests-server/pull/4
>>
>> On 06 May 2014, at 11:49, Matthias Wessendorf <matzew at apache.org> wrote:
>>
>> > Hello folks!
>> >
>> > Bill Burk was helping on the Keycloak front and besides fixing related
>> items on the Keycloak server, he also created an example that we can use as
>> a template for the actual integration. See [1]
>> >
>> > In the past, Bruno and I did integrate w/ an external Keycloak server
>> (see [2]), and we did include the keycloak.json file (See [3]). Thanks to
>> Bill's work on Keycloak, the 'protected app' no longer needs that, see [4].
>> > Also there is no more the need to customize the Keycloak Rest
>> Application (Stian and I did look into that as well).
>> >
>> >
>> > Good news: This means the UPS can stay as it is -> no need to change
>> internals (e.g. the 'bundle all in one WAR file' did force us to change our
>> '/rest' URLs, as Keycloak uses them, see [5]).
>> >
>> > Inside of our 'modular' Keycloak branch (see [2] again), we can apply
>> the work from Bill:
>> > * our current 'server' module will use a listener similar to [4]
>> > * create a "ups-auth" module similar to [6]
>> >
>> > On the 'ups-auth module' there is one area where we need to have some
>> future improvement:
>> > * testrealm.json -> needs to be in Java code, due to the URL being
>> hard-coded in there (we need to resolve the URL of the host, running the
>> bits). But, IMO for now that should be good enough.
>> >
>> > Bruno did offer to help out on the Keycloak integration, so that I can
>> go back to the analytics and mertrics feature. Thanks abstractj!! <3
>> >
>> > Greetings,
>> > Matthias
>> >
>> > [1]
>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
>> > [2]
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
>> > [3]
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
>> > [4]
>> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
>> > [5]
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
>> > [6]
>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> --
> Sent from Gmail Mobile
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140506/2d851f16/attachment-0001.html 

From corinnekrych at gmail.com  Tue May  6 07:36:50 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Tue, 6 May 2014 13:36:50 +0200
Subject: [aerogear-dev] Keycloak integration
In-Reply-To: <CAAg5f2RfiXFF+Z9deP4n9f3m-q3hUOQfqcaKi3JwkAMWNQQETA@mail.gmail.com>
References: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
	<647EB099-5DC8-49D7-8F42-C9F991271B80@gmail.com>
	<CAAg5f2QRokJuxN66toZcc2W_X0YGAW6073hmjWP1U2MyJqTv6w@mail.gmail.com>
	<CAAg5f2RfiXFF+Z9deP4n9f3m-q3hUOQfqcaKi3JwkAMWNQQETA@mail.gmail.com>
Message-ID: <A2E32615-46B1-4545-A2AC-30D4EA48F869@gmail.com>

Good idea.
We?ll keep that initial version and we?ll make it evolved later when KC-integration got more stable.
for now I?ve speciifed which KC version it?s working with.
++
Corinne
On 06 May 2014, at 13:31, Matthias Wessendorf <matzew at apache.org> wrote:

> Let's see how the UPS integration goes, before we have too much KC integration fields, ok ? 
> Once we got that done, I guess we have a good experience on proper integration
> 
> -M
> 
> 
> On Tue, May 6, 2014 at 1:04 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> Yeah, sounds reasonable to me.
> 
> 
> 
> On Tuesday, May 6, 2014, Corinne Krych <corinnekrych at gmail.com> wrote:
> Good work!
> 
> I wonder... It might be good to use the same integration for our OAuth2 server side demo in [1]
> Here I used a KC server with realm.json configuration. Would it be possible/worth it to replace all the configuration with plain Java?
> 
> ++
> Corinne.
> [1]  https://github.com/aerogear/aerogear-integration-tests-server/pull/4
> 
> On 06 May 2014, at 11:49, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> > Hello folks!
> >
> > Bill Burk was helping on the Keycloak front and besides fixing related items on the Keycloak server, he also created an example that we can use as a template for the actual integration. See [1]
> >
> > In the past, Bruno and I did integrate w/ an external Keycloak server (see [2]), and we did include the keycloak.json file (See [3]). Thanks to Bill's work on Keycloak, the 'protected app' no longer needs that, see [4].
> > Also there is no more the need to customize the Keycloak Rest Application (Stian and I did look into that as well).
> >
> >
> > Good news: This means the UPS can stay as it is -> no need to change internals (e.g. the 'bundle all in one WAR file' did force us to change our '/rest' URLs, as Keycloak uses them, see [5]).
> >
> > Inside of our 'modular' Keycloak branch (see [2] again), we can apply the work from Bill:
> > * our current 'server' module will use a listener similar to [4]
> > * create a "ups-auth" module similar to [6]
> >
> > On the 'ups-auth module' there is one area where we need to have some future improvement:
> > * testrealm.json -> needs to be in Java code, due to the URL being hard-coded in there (we need to resolve the URL of the host, running the bits). But, IMO for now that should be good enough.
> >
> > Bruno did offer to help out on the Keycloak integration, so that I can go back to the analytics and mertrics feature. Thanks abstractj!! <3
> >
> > Greetings,
> > Matthias
> >
> > [1] https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
> > [2] https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
> > [3] https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
> > [4] https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
> > [5] https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
> > [6] https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> -- 
> Sent from Gmail Mobile
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From bruno at abstractj.org  Tue May  6 09:07:24 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 6 May 2014 10:07:24 -0300
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <CAAg5f2RMOFGKgUvwoJ-TVVG+6pavtkxXaqqrQ18idDcU=uF7Fw@mail.gmail.com>
References: <8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>
	<2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>
	<5639DBE5-69E0-4C06-8F9C-AAFD8105E140@gmail.com>
	<CAD_dpu2GZ32kteN+xmGkipqMJK7T7i-UnN7qa_8r6GfGNhFVkg@mail.gmail.com>
	<CAAg5f2RMOFGKgUvwoJ-TVVG+6pavtkxXaqqrQ18idDcU=uF7Fw@mail.gmail.com>
Message-ID: <20140506130724.GA95390@abstractj.org>

2 sounds reasonable, go for it

On 2014-05-06, Matthias Wessendorf wrote:
> yes, sounds like 2) is the way to go
>
>
> On Tue, May 6, 2014 at 9:10 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> > Anyone else ?
> > If we all agree I can adapt the temporary backend I deployed including
> > this new behaviour.
> >
> > Sebi
> >
> >
> >
> > On Mon, May 5, 2014 at 9:34 AM, Christos Vasilakis <cvasilak at gmail.com>wrote:
> >
> >> Hi,
> >>
> >> answers inline
> >>
> >> On May 2, 2014, at 11:37 PM, Jay Balunas <jbalunas at redhat.com> wrote:
> >>
> >> > I wanted to chime in here on additional/related items around the
> >> contacts use-case and specifically around how to integrate push.  Some of
> >> these have already been discussed so just getting in one place for my own
> >> sanity :-)
> >> >
> >> > 1) I agree that users and "contacts" are separate things.  I think it
> >> is best to think about them as was mentioned below - users (employees) and
> >> contacts (customers, leads, etc...).  This is easier to grok imo and could
> >> be helped by some simple wording in the UI.
> >>
> >> +1
> >>
> >>
> >> > Cons:
> >> > ** We then need a way to add "users" - otherwise we won't be sending
> >> many push messages.  Maybe users could be automatically created when an app
> >> first accesses the backend?
> >>
> >> already the backend provides endpoints for creation of ?users?, as well
> >> as a list of default users initialised once the app is first loaded. By
> >> default when a new user is created the security role assigned to it doesn?t
> >> allow the creation of new contacts,  you get back an ?Unauthorised? error.
> >> It doesn?t effect push per se, since an ?admin? user can create a contact
> >> and the notification can be send to all other users that are logged in, but
> >> we should document this behaviour.
> >>
> >> >
> >> > 2) Simplifying the push use-case:  If we change the use-case from
> >> saying hi to specific contacts to notifying all users when a new contact
> >> was created it could simplify not only the UI, but the server side
> >> processing for the push.  We could reserve the more specific push usage to
> >> the console, and/or AeroDoc.
> >> >
> >> > If we go with 2) we might be able to avoid the issues with 1)
> >> altogether because a broadcast would send to every app that has registered.
> >> >
> >> > Wdyt?
> >>
> >> I am +1 on this behaviour.  IMHO its more clear for the end-user and the
> >> actual notification is used to ?alert? for a change on the server part that
> >> the app can decided to respond (e.g. fetch the new contact list).
> >>
> >> Thanks,
> >> Christos
> >>
> >>
> >> >
> >> >
> >> > On May 1, 2014, at 10:46 AM, Burr Sutter <bsutter at redhat.com> wrote:
> >> >
> >> >> Joshua owns the backend, let's see if he has a thought on this item.
> >> >>
> >> >> On May 1, 2014, at 7:25 AM, Christos Vasilakis <cvasilak at gmail.com>
> >> wrote:
> >> >>
> >> >>> Hi everyone,
> >> >>>
> >> >>> have started working on the iOS native client of the contacts quick
> >> start app. Based on edewit branch[1] (which creates a contact on signup of
> >> a user) have created an initial version of the iOS client and you can find
> >> it here [2], together with a screencast showcasing the app in action [3].
> >> >>>
> >> >>> Some comments observed during writing of the application which would
> >> like your feedback:
> >> >>>
> >> >>> a)  for PUT, DELETE operations noticed that the jax-rs backend
> >> expects the id of the Contact to be present in the body of the request. Not
> >> sure why this was chosen instead of @Path(?id?) resulting against
> >> /contacts/{id} ?
> >> >>>
> >> >>> b) currently roles are used to distinguish between who is able to
> >> create/update/delete contact. When a user signs up (and contact is
> >> created),  by default the user is _not_ able to apply any CRUD operations
> >> apart from viewing (any operation results in unauthorised error). If we
> >> agree on this behaviour, would like to know how can I determine the role of
> >> the user (in order to update the UI accordingly, eg. disabling add,edit UI
> >> elements). Looking at the json response upon login of the user, couldn?t
> >> determine a ?key? that specifies the role (apart from an ?admin? key which
> >> stayed the same regardless of the type of the user).
> >> >>>
> >> >>>
> >> >>> Thanks,
> >> >>> Christos
> >> >>>
> >> >>> [1]
> >> https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
> >> >>> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
> >> >>> [3] https://vimeo.com/93471554
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com>
> >> wrote:
> >> >>>
> >> >>>> Right, that makes sense, so let?s not join them. The alternate thing
> >> to do is to create a contact on sign up, because if you want to receive
> >> push notifications at least you should be in the list of contacts. We will
> >> still need to change the sign up page a little as we need a phone number
> >> and a birth date as well in order to create a contact.
> >> >>>>
> >> >>>> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com> wrote:
> >> >>>>
> >> >>>>> These are not strongly held opinions
> >> >>>>>
> >> >>>>> One reason to keep Users & Contacts separate is...because that is
> >> normal for the average enterprise app - your have employees (users) and
> >> customers (contacts) - employees/users have different roles/privileges from
> >> customers.
> >> >>>>>
> >> >>>>> The reason they are separated in the secured (PL) version of
> >> contacts-mobile-basic is because it simply evolved that way - contacts came
> >> first - users/roles added after the fact.   Ideally we would not modify the
> >> original too much as it allows a nice learning progression - start with the
> >> original contacts-mobile-basic, then upgrade to
> >> contacts-mobile-basic-secured, then upgrade to
> >> contacts-mobile-basic-secured-cordova (names just made up).
> >> >>>>>
> >> >>>>>
> >> >>>>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <scm.blanc at gmail.com>
> >> wrote:
> >> >>>>>
> >> >>>>>> Sure !
> >> >>>>>> Be sure to check this with Joshua as he drives the backend bits
> >> >>>>>> S?bi
> >> >>>>>>
> >> >>>>>> Envoy? de mon iPhone
> >> >>>>>>
> >> >>>>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a
> >> ?crit :
> >> >>>>>>>
> >> >>>>>>> Hi,
> >> >>>>>>>
> >> >>>>>>> How about merging the User model and the Contact into one entity?
> >> Seems like they have a lot in common, do we really need 2?
> >> >>>>>>>
> >> >>>>>>> Cheers,
> >> >>>>>>> Erik Jan
> >> >>>>>>>
> >> >>>>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <scm.blanc at gmail.com>
> >> wrote:
> >> >>>>>>>>
> >> >>>>>>>> We should be using the email as alias and the email should also
> >> be used as login when registering in the secured part. A registration
> >> should also trigger the creation of that user / contact in the application.
> >> >>>>>>>> Author can be left empty By the client and filled by the backend
> >> .
> >> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthormust stay because the receiver must know who sends the message.
> >> >>>>>>>>
> >> >>>>>>>> Envoy? de mon iPhone
> >> >>>>>>>>
> >> >>>>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com> a
> >> ?crit :
> >> >>>>>>>>>
> >> >>>>>>>>> Hi,
> >> >>>>>>>>>
> >> >>>>>>>>> I was working on the aerogear-push-quickstarts for Cordova and
> >> was wondering what to put for the alias on registration. The version that
> >> is there now has users that logs in and contacts that are fetched. What
> >> seems to be missing is that everybody gets all contacts instead of just
> >> mine (maybe that is fine), but users that sign up for the app are not
> >> contacts. So when I want to send a message to a specific mobile user they
> >> are not in my list and there is no way to have to define an alias to send
> >> to.
> >> >>>>>>>>>
> >> >>>>>>>>> Also the interface for sending push notifications includes a
> >> author. I think it would be better if we remove this and let the service
> >> put in the logged in user. That way you can?t pretend to send a message
> >> like someone else.
> >> >>>>>>>>>
> >> >>>>>>>>> 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
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>> _______________________________________________
> >> >>>>>>> aerogear-dev mailing list
> >> >>>>>>> aerogear-dev at lists.jboss.org
> >> >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> >>>>>>
> >> >>>>>> _______________________________________________
> >> >>>>>> aerogear-dev mailing list
> >> >>>>>> aerogear-dev at lists.jboss.org
> >> >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> >>>>>
> >> >>>>>
> >> >>>>> _______________________________________________
> >> >>>>> aerogear-dev mailing list
> >> >>>>> aerogear-dev at lists.jboss.org
> >> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> >>>>
> >> >>>>
> >> >>>> _______________________________________________
> >> >>>> aerogear-dev mailing list
> >> >>>> aerogear-dev at lists.jboss.org
> >> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> >>>
> >> >>>
> >> >>> _______________________________________________
> >> >>> aerogear-dev mailing list
> >> >>> aerogear-dev at lists.jboss.org
> >> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> aerogear-dev mailing list
> >> >> aerogear-dev at lists.jboss.org
> >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> >
> >> >
> >> > _______________________________________________
> >> > aerogear-dev mailing list
> >> > aerogear-dev at lists.jboss.org
> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From bsutter at redhat.com  Tue May  6 09:26:04 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Tue, 6 May 2014 09:26:04 -0400
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <20140506130724.GA95390@abstractj.org>
References: <8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>
	<2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>
	<5639DBE5-69E0-4C06-8F9C-AAFD8105E140@gmail.com>
	<CAD_dpu2GZ32kteN+xmGkipqMJK7T7i-UnN7qa_8r6GfGNhFVkg@mail.gmail.com>
	<CAAg5f2RMOFGKgUvwoJ-TVVG+6pavtkxXaqqrQ18idDcU=uF7Fw@mail.gmail.com>
	<20140506130724.GA95390@abstractj.org>
Message-ID: <8D7904A2-7475-4A4F-A494-FB807B801D4C@redhat.com>

Number 2

Broadcast push for new contact/customer to all users/salespeople 
Cordova-ized for iOS and Android
Native Objective-C & Android Java impls as well, is that about right?



On May 6, 2014, at 9:07 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> 2 sounds reasonable, go for it
> 
> On 2014-05-06, Matthias Wessendorf wrote:
>> yes, sounds like 2) is the way to go
>> 
>> 
>> On Tue, May 6, 2014 at 9:10 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>> 
>>> Anyone else ?
>>> If we all agree I can adapt the temporary backend I deployed including
>>> this new behaviour.
>>> 
>>> Sebi
>>> 
>>> 
>>> 
>>> On Mon, May 5, 2014 at 9:34 AM, Christos Vasilakis <cvasilak at gmail.com>wrote:
>>> 
>>>> Hi,
>>>> 
>>>> answers inline
>>>> 
>>>> On May 2, 2014, at 11:37 PM, Jay Balunas <jbalunas at redhat.com> wrote:
>>>> 
>>>>> I wanted to chime in here on additional/related items around the
>>>> contacts use-case and specifically around how to integrate push.  Some of
>>>> these have already been discussed so just getting in one place for my own
>>>> sanity :-)
>>>>> 
>>>>> 1) I agree that users and "contacts" are separate things.  I think it
>>>> is best to think about them as was mentioned below - users (employees) and
>>>> contacts (customers, leads, etc...).  This is easier to grok imo and could
>>>> be helped by some simple wording in the UI.
>>>> 
>>>> +1
>>>> 
>>>> 
>>>>> Cons:
>>>>> ** We then need a way to add "users" - otherwise we won't be sending
>>>> many push messages.  Maybe users could be automatically created when an app
>>>> first accesses the backend?
>>>> 
>>>> already the backend provides endpoints for creation of ?users?, as well
>>>> as a list of default users initialised once the app is first loaded. By
>>>> default when a new user is created the security role assigned to it doesn?t
>>>> allow the creation of new contacts,  you get back an ?Unauthorised? error.
>>>> It doesn?t effect push per se, since an ?admin? user can create a contact
>>>> and the notification can be send to all other users that are logged in, but
>>>> we should document this behaviour.
>>>> 
>>>>> 
>>>>> 2) Simplifying the push use-case:  If we change the use-case from
>>>> saying hi to specific contacts to notifying all users when a new contact
>>>> was created it could simplify not only the UI, but the server side
>>>> processing for the push.  We could reserve the more specific push usage to
>>>> the console, and/or AeroDoc.
>>>>> 
>>>>> If we go with 2) we might be able to avoid the issues with 1)
>>>> altogether because a broadcast would send to every app that has registered.
>>>>> 
>>>>> Wdyt?
>>>> 
>>>> I am +1 on this behaviour.  IMHO its more clear for the end-user and the
>>>> actual notification is used to ?alert? for a change on the server part that
>>>> the app can decided to respond (e.g. fetch the new contact list).
>>>> 
>>>> Thanks,
>>>> Christos
>>>> 
>>>> 
>>>>> 
>>>>> 
>>>>> On May 1, 2014, at 10:46 AM, Burr Sutter <bsutter at redhat.com> wrote:
>>>>> 
>>>>>> Joshua owns the backend, let's see if he has a thought on this item.
>>>>>> 
>>>>>> On May 1, 2014, at 7:25 AM, Christos Vasilakis <cvasilak at gmail.com>
>>>> wrote:
>>>>>> 
>>>>>>> Hi everyone,
>>>>>>> 
>>>>>>> have started working on the iOS native client of the contacts quick
>>>> start app. Based on edewit branch[1] (which creates a contact on signup of
>>>> a user) have created an initial version of the iOS client and you can find
>>>> it here [2], together with a screencast showcasing the app in action [3].
>>>>>>> 
>>>>>>> Some comments observed during writing of the application which would
>>>> like your feedback:
>>>>>>> 
>>>>>>> a)  for PUT, DELETE operations noticed that the jax-rs backend
>>>> expects the id of the Contact to be present in the body of the request. Not
>>>> sure why this was chosen instead of @Path(?id?) resulting against
>>>> /contacts/{id} ?
>>>>>>> 
>>>>>>> b) currently roles are used to distinguish between who is able to
>>>> create/update/delete contact. When a user signs up (and contact is
>>>> created),  by default the user is _not_ able to apply any CRUD operations
>>>> apart from viewing (any operation results in unauthorised error). If we
>>>> agree on this behaviour, would like to know how can I determine the role of
>>>> the user (in order to update the UI accordingly, eg. disabling add,edit UI
>>>> elements). Looking at the json response upon login of the user, couldn?t
>>>> determine a ?key? that specifies the role (apart from an ?admin? key which
>>>> stayed the same regardless of the type of the user).
>>>>>>> 
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> Christos
>>>>>>> 
>>>>>>> [1]
>>>> https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
>>>>>>> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
>>>>>>> [3] https://vimeo.com/93471554
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com>
>>>> wrote:
>>>>>>> 
>>>>>>>> Right, that makes sense, so let?s not join them. The alternate thing
>>>> to do is to create a contact on sign up, because if you want to receive
>>>> push notifications at least you should be in the list of contacts. We will
>>>> still need to change the sign up page a little as we need a phone number
>>>> and a birth date as well in order to create a contact.
>>>>>>>> 
>>>>>>>> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com> wrote:
>>>>>>>> 
>>>>>>>>> These are not strongly held opinions
>>>>>>>>> 
>>>>>>>>> One reason to keep Users & Contacts separate is...because that is
>>>> normal for the average enterprise app - your have employees (users) and
>>>> customers (contacts) - employees/users have different roles/privileges from
>>>> customers.
>>>>>>>>> 
>>>>>>>>> The reason they are separated in the secured (PL) version of
>>>> contacts-mobile-basic is because it simply evolved that way - contacts came
>>>> first - users/roles added after the fact.   Ideally we would not modify the
>>>> original too much as it allows a nice learning progression - start with the
>>>> original contacts-mobile-basic, then upgrade to
>>>> contacts-mobile-basic-secured, then upgrade to
>>>> contacts-mobile-basic-secured-cordova (names just made up).
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> Sure !
>>>>>>>>>> Be sure to check this with Joshua as he drives the backend bits
>>>>>>>>>> S?bi
>>>>>>>>>> 
>>>>>>>>>> Envoy? de mon iPhone
>>>>>>>>>> 
>>>>>>>>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a
>>>> ?crit :
>>>>>>>>>>> 
>>>>>>>>>>> Hi,
>>>>>>>>>>> 
>>>>>>>>>>> How about merging the User model and the Contact into one entity?
>>>> Seems like they have a lot in common, do we really need 2?
>>>>>>>>>>> 
>>>>>>>>>>> Cheers,
>>>>>>>>>>> Erik Jan
>>>>>>>>>>> 
>>>>>>>>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> We should be using the email as alias and the email should also
>>>> be used as login when registering in the secured part. A registration
>>>> should also trigger the creation of that user / contact in the application.
>>>>>>>>>>>> Author can be left empty By the client and filled by the backend
>>>> .
>>>> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthormust stay because the receiver must know who sends the message.
>>>>>>>>>>>> 
>>>>>>>>>>>> Envoy? de mon iPhone
>>>>>>>>>>>> 
>>>>>>>>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com> a
>>>> ?crit :
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I was working on the aerogear-push-quickstarts for Cordova and
>>>> was wondering what to put for the alias on registration. The version that
>>>> is there now has users that logs in and contacts that are fetched. What
>>>> seems to be missing is that everybody gets all contacts instead of just
>>>> mine (maybe that is fine), but users that sign up for the app are not
>>>> contacts. So when I want to send a message to a specific mobile user they
>>>> are not in my list and there is no way to have to define an alias to send
>>>> to.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Also the interface for sending push notifications includes a
>>>> author. I think it would be better if we remove this and let the service
>>>> put in the logged in user. That way you can?t pretend to send a message
>>>> like someone else.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 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
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> aerogear-dev mailing list
>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>> 
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>> 
>> 
>> 
>> --
>> Matthias Wessendorf
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> --
> 
> abstractj
> _______________________________________________
> 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 May  6 09:31:21 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 6 May 2014 15:31:21 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <8D7904A2-7475-4A4F-A494-FB807B801D4C@redhat.com>
References: <8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<4EBA6DE6-DC41-476D-9975-4342262036A5@redhat.com>
	<2CBE4194-380C-4934-A07C-D62B23E016F8@redhat.com>
	<5639DBE5-69E0-4C06-8F9C-AAFD8105E140@gmail.com>
	<CAD_dpu2GZ32kteN+xmGkipqMJK7T7i-UnN7qa_8r6GfGNhFVkg@mail.gmail.com>
	<CAAg5f2RMOFGKgUvwoJ-TVVG+6pavtkxXaqqrQ18idDcU=uF7Fw@mail.gmail.com>
	<20140506130724.GA95390@abstractj.org>
	<8D7904A2-7475-4A4F-A494-FB807B801D4C@redhat.com>
Message-ID: <CAD_dpu28Dz3eNo-+O2wrT-rFD6PfKKqKLK8F2ZvBWAqMgnPboQ@mail.gmail.com>

On Tue, May 6, 2014 at 3:26 PM, Burr Sutter <bsutter at redhat.com> wrote:

> Number 2
>
> Broadcast push for new contact/customer to all users/salespeople
> Cordova-ized for iOS and Android
> Native Objective-C & Android Java impls as well, is that about right?
>
yes

>
>
>
> On May 6, 2014, at 9:07 AM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > 2 sounds reasonable, go for it
> >
> > On 2014-05-06, Matthias Wessendorf wrote:
> >> yes, sounds like 2) is the way to go
> >>
> >>
> >> On Tue, May 6, 2014 at 9:10 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
> >>
> >>> Anyone else ?
> >>> If we all agree I can adapt the temporary backend I deployed including
> >>> this new behaviour.
> >>>
> >>> Sebi
> >>>
> >>>
> >>>
> >>> On Mon, May 5, 2014 at 9:34 AM, Christos Vasilakis <cvasilak at gmail.com
> >wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> answers inline
> >>>>
> >>>> On May 2, 2014, at 11:37 PM, Jay Balunas <jbalunas at redhat.com> wrote:
> >>>>
> >>>>> I wanted to chime in here on additional/related items around the
> >>>> contacts use-case and specifically around how to integrate push.
>  Some of
> >>>> these have already been discussed so just getting in one place for my
> own
> >>>> sanity :-)
> >>>>>
> >>>>> 1) I agree that users and "contacts" are separate things.  I think it
> >>>> is best to think about them as was mentioned below - users
> (employees) and
> >>>> contacts (customers, leads, etc...).  This is easier to grok imo and
> could
> >>>> be helped by some simple wording in the UI.
> >>>>
> >>>> +1
> >>>>
> >>>>
> >>>>> Cons:
> >>>>> ** We then need a way to add "users" - otherwise we won't be sending
> >>>> many push messages.  Maybe users could be automatically created when
> an app
> >>>> first accesses the backend?
> >>>>
> >>>> already the backend provides endpoints for creation of ?users?, as
> well
> >>>> as a list of default users initialised once the app is first loaded.
> By
> >>>> default when a new user is created the security role assigned to it
> doesn?t
> >>>> allow the creation of new contacts,  you get back an ?Unauthorised?
> error.
> >>>> It doesn?t effect push per se, since an ?admin? user can create a
> contact
> >>>> and the notification can be send to all other users that are logged
> in, but
> >>>> we should document this behaviour.
> >>>>
> >>>>>
> >>>>> 2) Simplifying the push use-case:  If we change the use-case from
> >>>> saying hi to specific contacts to notifying all users when a new
> contact
> >>>> was created it could simplify not only the UI, but the server side
> >>>> processing for the push.  We could reserve the more specific push
> usage to
> >>>> the console, and/or AeroDoc.
> >>>>>
> >>>>> If we go with 2) we might be able to avoid the issues with 1)
> >>>> altogether because a broadcast would send to every app that has
> registered.
> >>>>>
> >>>>> Wdyt?
> >>>>
> >>>> I am +1 on this behaviour.  IMHO its more clear for the end-user and
> the
> >>>> actual notification is used to ?alert? for a change on the server
> part that
> >>>> the app can decided to respond (e.g. fetch the new contact list).
> >>>>
> >>>> Thanks,
> >>>> Christos
> >>>>
> >>>>
> >>>>>
> >>>>>
> >>>>> On May 1, 2014, at 10:46 AM, Burr Sutter <bsutter at redhat.com> wrote:
> >>>>>
> >>>>>> Joshua owns the backend, let's see if he has a thought on this item.
> >>>>>>
> >>>>>> On May 1, 2014, at 7:25 AM, Christos Vasilakis <cvasilak at gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> Hi everyone,
> >>>>>>>
> >>>>>>> have started working on the iOS native client of the contacts quick
> >>>> start app. Based on edewit branch[1] (which creates a contact on
> signup of
> >>>> a user) have created an initial version of the iOS client and you can
> find
> >>>> it here [2], together with a screencast showcasing the app in action
> [3].
> >>>>>>>
> >>>>>>> Some comments observed during writing of the application which
> would
> >>>> like your feedback:
> >>>>>>>
> >>>>>>> a)  for PUT, DELETE operations noticed that the jax-rs backend
> >>>> expects the id of the Contact to be present in the body of the
> request. Not
> >>>> sure why this was chosen instead of @Path(?id?) resulting against
> >>>> /contacts/{id} ?
> >>>>>>>
> >>>>>>> b) currently roles are used to distinguish between who is able to
> >>>> create/update/delete contact. When a user signs up (and contact is
> >>>> created),  by default the user is _not_ able to apply any CRUD
> operations
> >>>> apart from viewing (any operation results in unauthorised error). If
> we
> >>>> agree on this behaviour, would like to know how can I determine the
> role of
> >>>> the user (in order to update the UI accordingly, eg. disabling
> add,edit UI
> >>>> elements). Looking at the json response upon login of the user,
> couldn?t
> >>>> determine a ?key? that specifies the role (apart from an ?admin? key
> which
> >>>> stayed the same regardless of the type of the user).
> >>>>>>>
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Christos
> >>>>>>>
> >>>>>>> [1]
> >>>> https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
> >>>>>>> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
> >>>>>>> [3] https://vimeo.com/93471554
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <edewit at redhat.com>
> >>>> wrote:
> >>>>>>>
> >>>>>>>> Right, that makes sense, so let?s not join them. The alternate
> thing
> >>>> to do is to create a contact on sign up, because if you want to
> receive
> >>>> push notifications at least you should be in the list of contacts. We
> will
> >>>> still need to change the sign up page a little as we need a phone
> number
> >>>> and a birth date as well in order to create a contact.
> >>>>>>>>
> >>>>>>>> On 23 Apr,2014, at 16:26 , Burr Sutter <bsutter at redhat.com>
> wrote:
> >>>>>>>>
> >>>>>>>>> These are not strongly held opinions
> >>>>>>>>>
> >>>>>>>>> One reason to keep Users & Contacts separate is...because that is
> >>>> normal for the average enterprise app - your have employees (users)
> and
> >>>> customers (contacts) - employees/users have different
> roles/privileges from
> >>>> customers.
> >>>>>>>>>
> >>>>>>>>> The reason they are separated in the secured (PL) version of
> >>>> contacts-mobile-basic is because it simply evolved that way -
> contacts came
> >>>> first - users/roles added after the fact.   Ideally we would not
> modify the
> >>>> original too much as it allows a nice learning progression - start
> with the
> >>>> original contacts-mobile-basic, then upgrade to
> >>>> contacts-mobile-basic-secured, then upgrade to
> >>>> contacts-mobile-basic-secured-cordova (names just made up).
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <
> scm.blanc at gmail.com>
> >>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Sure !
> >>>>>>>>>> Be sure to check this with Joshua as he drives the backend bits
> >>>>>>>>>> S?bi
> >>>>>>>>>>
> >>>>>>>>>> Envoy? de mon iPhone
> >>>>>>>>>>
> >>>>>>>>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <edewit at redhat.com> a
> >>>> ?crit :
> >>>>>>>>>>>
> >>>>>>>>>>> Hi,
> >>>>>>>>>>>
> >>>>>>>>>>> How about merging the User model and the Contact into one
> entity?
> >>>> Seems like they have a lot in common, do we really need 2?
> >>>>>>>>>>>
> >>>>>>>>>>> Cheers,
> >>>>>>>>>>> Erik Jan
> >>>>>>>>>>>
> >>>>>>>>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <
> scm.blanc at gmail.com>
> >>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> We should be using the email as alias and the email should
> also
> >>>> be used as login when registering in the secured part. A registration
> >>>> should also trigger the creation of that user / contact in the
> application.
> >>>>>>>>>>>> Author can be left empty By the client and filled by the
> backend
> >>>> .
> >>>>
> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthormuststay because the receiver must know who sends the message.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Envoy? de mon iPhone
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <edewit at redhat.com>
> a
> >>>> ?crit :
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I was working on the aerogear-push-quickstarts for Cordova
> and
> >>>> was wondering what to put for the alias on registration. The version
> that
> >>>> is there now has users that logs in and contacts that are fetched.
> What
> >>>> seems to be missing is that everybody gets all contacts instead of
> just
> >>>> mine (maybe that is fine), but users that sign up for the app are not
> >>>> contacts. So when I want to send a message to a specific mobile user
> they
> >>>> are not in my list and there is no way to have to define an alias to
> send
> >>>> to.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Also the interface for sending push notifications includes a
> >>>> author. I think it would be better if we remove this and let the
> service
> >>>> put in the logged in user. That way you can?t pretend to send a
> message
> >>>> like someone else.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> 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
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> _______________________________________________
> >>>>>>>>>>> aerogear-dev mailing list
> >>>>>>>>>>> aerogear-dev at lists.jboss.org
> >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> aerogear-dev mailing list
> >>>>>>>>>> aerogear-dev at lists.jboss.org
> >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> aerogear-dev mailing list
> >>>>>>>>> aerogear-dev at lists.jboss.org
> >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> aerogear-dev mailing list
> >>>>>>>> aerogear-dev at lists.jboss.org
> >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>>>
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> aerogear-dev mailing list
> >>>>>>> aerogear-dev at lists.jboss.org
> >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> aerogear-dev mailing list
> >>>>>> aerogear-dev at lists.jboss.org
> >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> aerogear-dev mailing list
> >>>>> aerogear-dev at lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.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/20140506/72c5c484/attachment-0001.html 

From matzew at apache.org  Tue May  6 09:57:48 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 May 2014 15:57:48 +0200
Subject: [aerogear-dev] Release of 0.10.3 ?
Message-ID: <CAAg5f2RfBhxrb3SoJbfPAFcQ1=vFj467ObTVHNXvgnhha=R2xQ@mail.gmail.com>

Hello,

based on Eriks latest Cordova Plugin release (got a new, simplified API),
he also updated the Cordova code snippets.

This is a good reason to retire the 0.10.2 version that we ship (and
provide on OpenShift online).

In addition I also added some improvements for GCM logging/exception
handling (see  AGPUSH-624).

I'd be happy to get the release process of that branch started soon...

https://github.com/aerogear/aerogear-unifiedpush-server/commits/0.10.x



Any comments ?


-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/20140506/fcea0b3e/attachment.html 

From daniel at passos.me  Tue May  6 10:19:42 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 6 May 2014 11:19:42 -0300
Subject: [aerogear-dev] AeroGear Android Push 0.1.1
In-Reply-To: <CAD_dpu2aOBdcuuY1VqoeyVR1De4gY6yREVqLuUou5zBzNGYV5g@mail.gmail.com>
References: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>
	<CAD_dpu2aOBdcuuY1VqoeyVR1De4gY6yREVqLuUou5zBzNGYV5g@mail.gmail.com>
Message-ID: <CAKjsGbuRLZSoGuT-_Ewu+F3JDwUO7E71dZO4A_XMGYgeDoDJDw@mail.gmail.com>

Talking with Summers about what is the best options to solved that, we have
some options:

1) Catch the 302 and handle it inside of the rest provider. [1]

2) We can fix the IOException which is being thrown, throw the
HttpException correctly, and in the registrar check for 30x and then rerun
the operation [2]

3) We let the HttpException escape to the callback handler

We don't like the option 1, because increases complexity in the
HttpRestProvider class and it hides the 30x messages from the developers
should they want to handle them.  Furthermore, Summers argues that since
the registration code is being called often it would be better for the
developer to be aware of them and have to handle them in her code instead
of ours.  In short, if there are redirects then the developer should be
made aware so she can update her URL and make fewer HTTP requests (this is
important on mobile for battery life, data caps, etc).

[1]
https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/http/HttpRestProvider.java#L256
[2]
https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/unifiedpush/AeroGearGCMPushRegistrar.java#L139-L144

So, wdyt?



On Tue, May 6, 2014 at 6:47 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi !
> I just gave it a test with the Push HelloWorld :
>
> - https://issues.jboss.org/browse/AGPUSH-627 is fixed , I'm getting a
> nice error notification on the device
>
> - https://issues.jboss.org/browse/AGDROID-214 -> I'm getting exactly the
> same issue as Matzew , looks like the redirect is not working.
>
> Sebi
>
>
>
> On Fri, May 2, 2014 at 5:06 PM, Daniel Passos <daniel at passos.me> wrote:
>
>> We have found a bug[1] in the AeroGear Android Push 0.1. It was fixed and
>> the new version (0.1.1) was already sent to nexus[2].
>>
>> We'd like to ship it to Maven central next wednesday.
>>
>> [1] https://issues.jboss.org/browse/AGDROID-214
>> [2]
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3139/
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140506/fcba9a68/attachment.html 

From jowilson at redhat.com  Thu May  1 10:32:25 2014
From: jowilson at redhat.com (Joshua Wilson)
Date: Thu, 1 May 2014 10:32:25 -0400 (EDT)
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
Message-ID: <2a9f339f.00001c7c.0000002d@AMENTRAR978LMH>

Christos,



To answer a) since the Contact is being passed in, it is not necessary to 
also pass in the ID.  For PUT all the information needs to be passed back 
for the update. While the DELETE only needs the ID, the whole contact is 
being sent.



I am open to discussing this if you think there is something wrong with the 
design.



Joshua



From: Christos Vasilakis [via aerogear-dev] 
[mailto:ml-node+s1069024n7636h31 at n5.nabble.com]
Sent: Thursday, May 01, 2014 7:27 AM
To: joshuaw
Subject: Re: [aerogear-dev] contacts-mobile-basic quick start



Hi everyone,

have started working on the iOS native client of the contacts quick start 
app. Based on edewit branch[1] (which creates a contact on signup of a user) 
have created an initial version of the iOS client and you can find it here 
[2], together with a screencast showcasing the app in action [3].

Some comments observed during writing of the application which would like 
your feedback:

a)  for PUT, DELETE operations noticed that the jax-rs backend expects the 
id of the Contact to be present in the body of the request. Not sure why 
this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?

b) currently roles are used to distinguish between who is able to 
create/update/delete contact. When a user signs up (and contact is created), 
by default the user is _not_ able to apply any CRUD operations apart from 
viewing (any operation results in unauthorised error). If we agree on this 
behaviour, would like to know how can I determine the role of the user (in 
order to update the UI accordingly, eg. disabling add,edit UI elements). 
Looking at the json response upon login of the user, couldn?t determine a 
?key? that specifies the role (apart from an ?admin? key which stayed the 
same regardless of the type of the user).


Thanks,
Christos

[1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
[2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
[3] https://vimeo.com/93471554



On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <[hidden email]> wrote:


> Right, that makes sense, so let?s not join them. The alternate thing to do 
> is to create a contact on sign up, because if you want to receive push 
> notifications at least you should be in the list of contacts. We will 
> still need to change the sign up page a little as we need a phone number 
> and a birth date as well in order to create a contact.
>
> On 23 Apr,2014, at 16:26 , Burr Sutter <[hidden email]> wrote:
>
>> These are not strongly held opinions
>>
>> One reason to keep Users & Contacts separate is...because that is normal 
>> for the average enterprise app - your have employees (users) and 
>> customers (contacts) - employees/users have different roles/privileges 
>> from customers.
>>
>> The reason they are separated in the secured (PL) version of 
>> contacts-mobile-basic is because it simply evolved that way - contacts 
>> came first - users/roles added after the fact.   Ideally we would not 
>> modify the original too much as it allows a nice learning progression - 
>> start with the original contacts-mobile-basic, then upgrade to 
>> contacts-mobile-basic-secured, then upgrade to 
>> contacts-mobile-basic-secured-cordova (names just made up).
>>
>>
>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <[hidden email]> wrote:
>>
>>> Sure !
>>> Be sure to check this with Joshua as he drives the backend bits
>>> S?bi
>>>
>>> Envoy? de mon iPhone
>>>
>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <[hidden email]> a ?crit :
>>>>
>>>> Hi,
>>>>
>>>> How about merging the User model and the Contact into one entity? Seems 
>>>> like they have a lot in common, do we really need 2?
>>>>
>>>> Cheers,
>>>> Erik Jan
>>>>
>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <[hidden email]> wrote:
>>>>>
>>>>> We should be using the email as alias and the email should also be 
>>>>> used as login when registering in the secured part. A registration 
>>>>> should also trigger the creation of that user / contact in the 
>>>>> application.
>>>>> Author can be left empty By the client and filled by the backend . 
>>>>> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor 
>>>>> must stay because the receiver must know who sends the message.
>>>>>
>>>>> Envoy? de mon iPhone
>>>>>
>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <[hidden email]> a ?crit :
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I was working on the aerogear-push-quickstarts for Cordova and was 
>>>>>> wondering what to put for the alias on registration. The version that 
>>>>>> is there now has users that logs in and contacts that are fetched. 
>>>>>> What seems to be missing is that everybody gets all contacts instead 
>>>>>> of just mine (maybe that is fine), but users that sign up for the app 
>>>>>> are not contacts. So when I want to send a message to a specific 
>>>>>> mobile user they are not in my list and there is no way to have to 
>>>>>> define an alias to send to.
>>>>>>
>>>>>> Also the interface for sending push notifications includes a author. 
>>>>>> I think it would be better if we remove this and let the service put 
>>>>>> in the logged in user. That way you can?t pretend to send a message 
>>>>>> like someone else.
>>>>>>
>>>>>> What do you think?
>>>>>>
>>>>>> Cheers,
>>>>>> Erik Jan
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> [hidden email]
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



_______________________________________________
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-contacts-mobile-basic-quick-start-tp7534p7636.html

To start a new topic under aerogear-dev, email 
ml-node+s1069024n1h46 at n5.nabble.com
To unsubscribe from aerogear-dev, click here 
<http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=am93aWxzb25AcmVkaGF0LmNvbXwxfC0xNTQxNTU0OTE2> 
.
NAML

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140501/bb748ce0/attachment-0001.html 

From jowilson at redhat.com  Thu May  1 10:32:43 2014
From: jowilson at redhat.com (joshuaw)
Date: Thu, 1 May 2014 07:32:43 -0700 (PDT)
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
Message-ID: <2a9f339f.00001c7c.0000002d@AMENTRAR978LMH>

Christos,



To answer a) since the Contact is being passed in, it is not necessary to 
also pass in the ID.  For PUT all the information needs to be passed back 
for the update. While the DELETE only needs the ID, the whole contact is 
being sent.



I am open to discussing this if you think there is something wrong with the 
design.



Joshua



From: Christos Vasilakis [via aerogear-dev] 
[mailto:ml-node+s1069024n7636h31 at n5.nabble.com]
Sent: Thursday, May 01, 2014 7:27 AM
To: joshuaw
Subject: Re: [aerogear-dev] contacts-mobile-basic quick start



Hi everyone,

have started working on the iOS native client of the contacts quick start 
app. Based on edewit branch[1] (which creates a contact on signup of a user) 
have created an initial version of the iOS client and you can find it here 
[2], together with a screencast showcasing the app in action [3].

Some comments observed during writing of the application which would like 
your feedback:

a)  for PUT, DELETE operations noticed that the jax-rs backend expects the 
id of the Contact to be present in the body of the request. Not sure why 
this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?

b) currently roles are used to distinguish between who is able to 
create/update/delete contact. When a user signs up (and contact is created), 
by default the user is _not_ able to apply any CRUD operations apart from 
viewing (any operation results in unauthorised error). If we agree on this 
behaviour, would like to know how can I determine the role of the user (in 
order to update the UI accordingly, eg. disabling add,edit UI elements). 
Looking at the json response upon login of the user, couldn?t determine a 
?key? that specifies the role (apart from an ?admin? key which stayed the 
same regardless of the type of the user).


Thanks,
Christos

[1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
[2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
[3] https://vimeo.com/93471554



On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <[hidden email]> wrote:


> Right, that makes sense, so let?s not join them. The alternate thing to do 
> is to create a contact on sign up, because if you want to receive push 
> notifications at least you should be in the list of contacts. We will 
> still need to change the sign up page a little as we need a phone number 
> and a birth date as well in order to create a contact.
>
> On 23 Apr,2014, at 16:26 , Burr Sutter <[hidden email]> wrote:
>
>> These are not strongly held opinions
>>
>> One reason to keep Users & Contacts separate is...because that is normal 
>> for the average enterprise app - your have employees (users) and 
>> customers (contacts) - employees/users have different roles/privileges 
>> from customers.
>>
>> The reason they are separated in the secured (PL) version of 
>> contacts-mobile-basic is because it simply evolved that way - contacts 
>> came first - users/roles added after the fact.   Ideally we would not 
>> modify the original too much as it allows a nice learning progression - 
>> start with the original contacts-mobile-basic, then upgrade to 
>> contacts-mobile-basic-secured, then upgrade to 
>> contacts-mobile-basic-secured-cordova (names just made up).
>>
>>
>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <[hidden email]> wrote:
>>
>>> Sure !
>>> Be sure to check this with Joshua as he drives the backend bits
>>> S?bi
>>>
>>> Envoy? de mon iPhone
>>>
>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <[hidden email]> a ?crit :
>>>>
>>>> Hi,
>>>>
>>>> How about merging the User model and the Contact into one entity? Seems 
>>>> like they have a lot in common, do we really need 2?
>>>>
>>>> Cheers,
>>>> Erik Jan
>>>>
>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <[hidden email]> wrote:
>>>>>
>>>>> We should be using the email as alias and the email should also be 
>>>>> used as login when registering in the secured part. A registration 
>>>>> should also trigger the creation of that user / contact in the 
>>>>> application.
>>>>> Author can be left empty By the client and filled by the backend . 
>>>>> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor 
>>>>> must stay because the receiver must know who sends the message.
>>>>>
>>>>> Envoy? de mon iPhone
>>>>>
>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <[hidden email]> a ?crit :
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I was working on the aerogear-push-quickstarts for Cordova and was 
>>>>>> wondering what to put for the alias on registration. The version that 
>>>>>> is there now has users that logs in and contacts that are fetched. 
>>>>>> What seems to be missing is that everybody gets all contacts instead 
>>>>>> of just mine (maybe that is fine), but users that sign up for the app 
>>>>>> are not contacts. So when I want to send a message to a specific 
>>>>>> mobile user they are not in my list and there is no way to have to 
>>>>>> define an alias to send to.
>>>>>>
>>>>>> Also the interface for sending push notifications includes a author. 
>>>>>> I think it would be better if we remove this and let the service put 
>>>>>> in the logged in user. That way you can?t pretend to send a message 
>>>>>> like someone else.
>>>>>>
>>>>>> What do you think?
>>>>>>
>>>>>> Cheers,
>>>>>> Erik Jan
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> [hidden email]
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



_______________________________________________
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-contacts-mobile-basic-quick-start-tp7534p7636.html

To start a new topic under aerogear-dev, email 
ml-node+s1069024n1h46 at n5.nabble.com
To unsubscribe from aerogear-dev, click here 
<http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=am93aWxzb25AcmVkaGF0LmNvbXwxfC0xNTQxNTU0OTE2> 
.
NAML





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-contacts-mobile-basic-quick-start-tp7534p7637.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/20140501/bb748ce0/attachment-0002.html 

From jowilson at redhat.com  Tue May  6 10:20:34 2014
From: jowilson at redhat.com (joshuaw)
Date: Tue, 6 May 2014 07:20:34 -0700 (PDT)
Subject: [aerogear-dev] color scheme feed back
Message-ID: <1399386034855-7678.post@n5.nabble.com>

I am working on some new themes (color schemes) for jQuery Mobile 1.4.  Would
you all mind providing your thoughts on them.

http://themeroller.jquerymobile.com/?ver=1.4.2&style_id=20140506-50
<http://themeroller.jquerymobile.com/?ver=1.4.2&style_id=20140506-50>  

Please interact with the buttons as they change color if you click them or
hover over them.

Also, this is more of a rough draft and if you have ideas for me to try that
is fine too.

thanks,
Joshua



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/color-scheme-feed-back-tp7678.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Tue May  6 10:39:25 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 May 2014 16:39:25 +0200
Subject: [aerogear-dev] AeroGear Android Push 0.1.1
In-Reply-To: <CAKjsGbuRLZSoGuT-_Ewu+F3JDwUO7E71dZO4A_XMGYgeDoDJDw@mail.gmail.com>
References: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>
	<CAD_dpu2aOBdcuuY1VqoeyVR1De4gY6yREVqLuUou5zBzNGYV5g@mail.gmail.com>
	<CAKjsGbuRLZSoGuT-_Ewu+F3JDwUO7E71dZO4A_XMGYgeDoDJDw@mail.gmail.com>
Message-ID: <CAAg5f2Q23AGGKCZif=0ksg4r05HP2m4hwksr+Vn7TmOfDuyMMQ@mail.gmail.com>

On Tue, May 6, 2014 at 4:19 PM, Daniel Passos <daniel at passos.me> wrote:

> Talking with Summers about what is the best options to solved that, we
> have some options:
>
> 1) Catch the 302 and handle it inside of the rest provider. [1]
>
> 2) We can fix the IOException which is being thrown, throw the
> HttpException correctly, and in the registrar check for 30x and then rerun
> the operation [2]
>

yes!

+ add a (fatal/warning) log message



>
> 3) We let the HttpException escape to the callback handler
>
> We don't like the option 1, because increases complexity in the
> HttpRestProvider class and it hides the 30x messages from the developers
> should they want to handle them.  Furthermore, Summers argues that since
> the registration code is being called often it would be better for the
> developer to be aware of them and have to handle them in her code instead
> of ours.
>

sure, but IMO a 30x should be respected. Let's add a warning, so their
logcat tells them when they are testing



>  In short, if there are redirects then the developer should be made aware
> so she can update her URL and make fewer HTTP requests (this is important
> on mobile for battery life, data caps, etc).
>
> [1]
> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/http/HttpRestProvider.java#L256
> [2]
> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/unifiedpush/AeroGearGCMPushRegistrar.java#L139-L144
>
> So, wdyt?
>
>
>
> On Tue, May 6, 2014 at 6:47 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
>
>> Hi !
>> I just gave it a test with the Push HelloWorld :
>>
>> - https://issues.jboss.org/browse/AGPUSH-627 is fixed , I'm getting a
>> nice error notification on the device
>>
>> - https://issues.jboss.org/browse/AGDROID-214 -> I'm getting exactly the
>> same issue as Matzew , looks like the redirect is not working.
>>
>> Sebi
>>
>>
>>
>> On Fri, May 2, 2014 at 5:06 PM, Daniel Passos <daniel at passos.me> wrote:
>>
>>> We have found a bug[1] in the AeroGear Android Push 0.1. It was fixed
>>> and the new version (0.1.1) was already sent to nexus[2].
>>>
>>> We'd like to ship it to Maven central next wednesday.
>>>
>>> [1] https://issues.jboss.org/browse/AGDROID-214
>>> [2]
>>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3139/
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140506/67f9aca6/attachment-0001.html 

From matzew at apache.org  Tue May  6 10:39:49 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 May 2014 16:39:49 +0200
Subject: [aerogear-dev] color scheme feed back
In-Reply-To: <1399386034855-7678.post@n5.nabble.com>
References: <1399386034855-7678.post@n5.nabble.com>
Message-ID: <CAAg5f2SPMFrDotnkzd0Z9_f22xrMsGu-SBoXyiP5G0TiS5ZcGA@mail.gmail.com>

I like C


On Tue, May 6, 2014 at 4:20 PM, joshuaw <jowilson at redhat.com> wrote:

> I am working on some new themes (color schemes) for jQuery Mobile 1.4.
>  Would
> you all mind providing your thoughts on them.
>
> http://themeroller.jquerymobile.com/?ver=1.4.2&style_id=20140506-50
> <http://themeroller.jquerymobile.com/?ver=1.4.2&style_id=20140506-50>
>
> Please interact with the buttons as they change color if you click them or
> hover over them.
>
> Also, this is more of a rough draft and if you have ideas for me to try
> that
> is fine too.
>
> thanks,
> Joshua
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/color-scheme-feed-back-tp7678.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/20140506/2db86b81/attachment.html 

From bruno at abstractj.org  Tue May  6 10:42:10 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 6 May 2014 11:42:10 -0300
Subject: [aerogear-dev] AeroGear Android Push 0.1.1
In-Reply-To: <CAKjsGbuRLZSoGuT-_Ewu+F3JDwUO7E71dZO4A_XMGYgeDoDJDw@mail.gmail.com>
References: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>
	<CAD_dpu2aOBdcuuY1VqoeyVR1De4gY6yREVqLuUou5zBzNGYV5g@mail.gmail.com>
	<CAKjsGbuRLZSoGuT-_Ewu+F3JDwUO7E71dZO4A_XMGYgeDoDJDw@mail.gmail.com>
Message-ID: <20140506144210.GE2638@abstractj.org>

Option 2 sounds like a plan to me

On 2014-05-06, Daniel Passos wrote:
> Talking with Summers about what is the best options to solved that, we have
> some options:
>
> 1) Catch the 302 and handle it inside of the rest provider. [1]
>
> 2) We can fix the IOException which is being thrown, throw the
> HttpException correctly, and in the registrar check for 30x and then rerun
> the operation [2]
>
> 3) We let the HttpException escape to the callback handler
>
> We don't like the option 1, because increases complexity in the
> HttpRestProvider class and it hides the 30x messages from the developers
> should they want to handle them.  Furthermore, Summers argues that since
> the registration code is being called often it would be better for the
> developer to be aware of them and have to handle them in her code instead
> of ours.  In short, if there are redirects then the developer should be
> made aware so she can update her URL and make fewer HTTP requests (this is
> important on mobile for battery life, data caps, etc).
>
> [1]
> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/http/HttpRestProvider.java#L256
> [2]
> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/unifiedpush/AeroGearGCMPushRegistrar.java#L139-L144
>
> So, wdyt?
>
>
>
> On Tue, May 6, 2014 at 6:47 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> > Hi !
> > I just gave it a test with the Push HelloWorld :
> >
> > - https://issues.jboss.org/browse/AGPUSH-627 is fixed , I'm getting a
> > nice error notification on the device
> >
> > - https://issues.jboss.org/browse/AGDROID-214 -> I'm getting exactly the
> > same issue as Matzew , looks like the redirect is not working.
> >
> > Sebi
> >
> >
> >
> > On Fri, May 2, 2014 at 5:06 PM, Daniel Passos <daniel at passos.me> wrote:
> >
> >> We have found a bug[1] in the AeroGear Android Push 0.1. It was fixed and
> >> the new version (0.1.1) was already sent to nexus[2].
> >>
> >> We'd like to ship it to Maven central next wednesday.
> >>
> >> [1] https://issues.jboss.org/browse/AGDROID-214
> >> [2]
> >> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3139/
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From supittma at redhat.com  Tue May  6 10:54:26 2014
From: supittma at redhat.com (Summers Pittman)
Date: Tue, 06 May 2014 10:54:26 -0400
Subject: [aerogear-dev] AeroGear Android Push 0.1.1
In-Reply-To: <20140506144210.GE2638@abstractj.org>
References: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>
	<CAD_dpu2aOBdcuuY1VqoeyVR1De4gY6yREVqLuUou5zBzNGYV5g@mail.gmail.com>
	<CAKjsGbuRLZSoGuT-_Ewu+F3JDwUO7E71dZO4A_XMGYgeDoDJDw@mail.gmail.com>
	<20140506144210.GE2638@abstractj.org>
Message-ID: <5368F7A2.2070706@redhat.com>

On Tue 06 May 2014 10:42:10 AM EDT, Bruno Oliveira wrote:
> Option 2 sounds like a plan to me
>

Sweet.

RestProvider throws httpexception (status:302)
Registrar catches it and logs a warning.
Retries with new location.
if OK then onSuccess
else then onError.

IE We will only follow ONE redirect.

> On 2014-05-06, Daniel Passos wrote:
>> Talking with Summers about what is the best options to solved that, we have
>> some options:
>>
>> 1) Catch the 302 and handle it inside of the rest provider. [1]
>>
>> 2) We can fix the IOException which is being thrown, throw the
>> HttpException correctly, and in the registrar check for 30x and then rerun
>> the operation [2]
>>
>> 3) We let the HttpException escape to the callback handler
>>
>> We don't like the option 1, because increases complexity in the
>> HttpRestProvider class and it hides the 30x messages from the developers
>> should they want to handle them.  Furthermore, Summers argues that since
>> the registration code is being called often it would be better for the
>> developer to be aware of them and have to handle them in her code instead
>> of ours.  In short, if there are redirects then the developer should be
>> made aware so she can update her URL and make fewer HTTP requests (this is
>> important on mobile for battery life, data caps, etc).
>>
>> [1]
>> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/http/HttpRestProvider.java#L256
>> [2]
>> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/unifiedpush/AeroGearGCMPushRegistrar.java#L139-L144
>>
>> So, wdyt?
>>
>>
>>
>> On Tue, May 6, 2014 at 6:47 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>
>>> Hi !
>>> I just gave it a test with the Push HelloWorld :
>>>
>>> - https://issues.jboss.org/browse/AGPUSH-627 is fixed , I'm getting a
>>> nice error notification on the device
>>>
>>> - https://issues.jboss.org/browse/AGDROID-214 -> I'm getting exactly the
>>> same issue as Matzew , looks like the redirect is not working.
>>>
>>> Sebi
>>>
>>>
>>>
>>> On Fri, May 2, 2014 at 5:06 PM, Daniel Passos <daniel at passos.me> wrote:
>>>
>>>> We have found a bug[1] in the AeroGear Android Push 0.1. It was fixed and
>>>> the new version (0.1.1) was already sent to nexus[2].
>>>>
>>>> We'd like to ship it to Maven central next wednesday.
>>>>
>>>> [1] https://issues.jboss.org/browse/AGDROID-214
>>>> [2]
>>>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3139/
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.


From matzew at apache.org  Tue May  6 11:13:35 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 May 2014 17:13:35 +0200
Subject: [aerogear-dev] AeroGear Android Push 0.1.1
In-Reply-To: <5368F7A2.2070706@redhat.com>
References: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>
	<CAD_dpu2aOBdcuuY1VqoeyVR1De4gY6yREVqLuUou5zBzNGYV5g@mail.gmail.com>
	<CAKjsGbuRLZSoGuT-_Ewu+F3JDwUO7E71dZO4A_XMGYgeDoDJDw@mail.gmail.com>
	<20140506144210.GE2638@abstractj.org> <5368F7A2.2070706@redhat.com>
Message-ID: <CAAg5f2SJJJBoacr3O2v_Dq5JGNCyx3suE9assZhMn6kbriRNvw@mail.gmail.com>

On Tue, May 6, 2014 at 4:54 PM, Summers Pittman <supittma at redhat.com> wrote:

> On Tue 06 May 2014 10:42:10 AM EDT, Bruno Oliveira wrote:
> > Option 2 sounds like a plan to me
> >
>
> Sweet.
>
> RestProvider throws httpexception (status:302)
> Registrar catches it and logs a warning.
> Retries with new location.
> if OK then onSuccess
> else then onError.
>
> IE We will only follow ONE redirect.
>

yes :) no need to join a redirect party

>
> > On 2014-05-06, Daniel Passos wrote:
> >> Talking with Summers about what is the best options to solved that, we
> have
> >> some options:
> >>
> >> 1) Catch the 302 and handle it inside of the rest provider. [1]
> >>
> >> 2) We can fix the IOException which is being thrown, throw the
> >> HttpException correctly, and in the registrar check for 30x and then
> rerun
> >> the operation [2]
> >>
> >> 3) We let the HttpException escape to the callback handler
> >>
> >> We don't like the option 1, because increases complexity in the
> >> HttpRestProvider class and it hides the 30x messages from the developers
> >> should they want to handle them.  Furthermore, Summers argues that since
> >> the registration code is being called often it would be better for the
> >> developer to be aware of them and have to handle them in her code
> instead
> >> of ours.  In short, if there are redirects then the developer should be
> >> made aware so she can update her URL and make fewer HTTP requests (this
> is
> >> important on mobile for battery life, data caps, etc).
> >>
> >> [1]
> >>
> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/http/HttpRestProvider.java#L256
> >> [2]
> >>
> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/unifiedpush/AeroGearGCMPushRegistrar.java#L139-L144
> >>
> >> So, wdyt?
> >>
> >>
> >>
> >> On Tue, May 6, 2014 at 6:47 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
> >>
> >>> Hi !
> >>> I just gave it a test with the Push HelloWorld :
> >>>
> >>> - https://issues.jboss.org/browse/AGPUSH-627 is fixed , I'm getting a
> >>> nice error notification on the device
> >>>
> >>> - https://issues.jboss.org/browse/AGDROID-214 -> I'm getting exactly
> the
> >>> same issue as Matzew , looks like the redirect is not working.
> >>>
> >>> Sebi
> >>>
> >>>
> >>>
> >>> On Fri, May 2, 2014 at 5:06 PM, Daniel Passos <daniel at passos.me>
> wrote:
> >>>
> >>>> We have found a bug[1] in the AeroGear Android Push 0.1. It was fixed
> and
> >>>> the new version (0.1.1) was already sent to nexus[2].
> >>>>
> >>>> We'd like to ship it to Maven central next wednesday.
> >>>>
> >>>> [1] https://issues.jboss.org/browse/AGDROID-214
> >>>> [2]
> >>>>
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3139/
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> aerogear-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140506/1f5d028c/attachment.html 

From cvasilak at gmail.com  Tue May  6 12:18:53 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 6 May 2014 19:18:53 +0300
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <2a9f339f.00001c7c.0000002d@AMENTRAR978LMH>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<2a9f339f.00001c7c.0000002d@AMENTRAR978LMH>
Message-ID: <C6EFE2C9-FE64-4D87-B21D-BF550130BBD0@gmail.com>

Hi Joshua,

my belief is that for PUT, DELETE ops the client should go against /contacts/{id} URI

Anyone else have a different view of it ?

Thanks,
Christos


On May 1, 2014, at 5:32 PM, joshuaw <jowilson at redhat.com> wrote:

> Christos,
> 
>  
> 
> To answer a) since the Contact is being passed in, it is not necessary to also pass in the ID.  For PUT all the information needs to be passed back for the update. While the DELETE only needs the ID, the whole contact is being sent. 
> 
>  
> 
> I am open to discussing this if you think there is something wrong with the design.
> 
>  
> 
> Joshua
> 
>  
> 
> From: Christos Vasilakis [via aerogear-dev] [mailto:[hidden email]] 
> Sent: Thursday, May 01, 2014 7:27 AM
> To: joshuaw
> Subject: Re: [aerogear-dev] contacts-mobile-basic quick start
> 
>  
> 
> Hi everyone, 
> 
> have started working on the iOS native client of the contacts quick start app. Based on edewit branch[1] (which creates a contact on signup of a user) have created an initial version of the iOS client and you can find it here [2], together with a screencast showcasing the app in action [3]. 
> 
> Some comments observed during writing of the application which would like your feedback: 
> 
> a)  for PUT, DELETE operations noticed that the jax-rs backend expects the id of the Contact to be present in the body of the request. Not sure why this was chosen instead of @Path(?id?) resulting against /contacts/{id} ? 
> 
> b) currently roles are used to distinguish between who is able to create/update/delete contact. When a user signs up (and contact is created),  by default the user is _not_ able to apply any CRUD operations apart from viewing (any operation results in unauthorised error). If we agree on this behaviour, would like to know how can I determine the role of the user (in order to update the UI accordingly, eg. disabling add,edit UI elements). Looking at the json response upon login of the user, couldn?t determine a ?key? that specifies the role (apart from an ?admin? key which stayed the same regardless of the type of the user). 
> 
> 
> Thanks, 
> Christos 
> 
> [1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
> [3] https://vimeo.com/93471554
> 
> 
> 
> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <[hidden email]> wrote:
> 
> 
> 
> > Right, that makes sense, so let?s not join them. The alternate thing to do is to create a contact on sign up, because if you want to receive push notifications at least you should be in the list of contacts. We will still need to change the sign up page a little as we need a phone number and a birth date as well in order to create a contact. 
> > 
> > On 23 Apr,2014, at 16:26 , Burr Sutter <[hidden email]> wrote: 
> > 
> >> These are not strongly held opinions 
> >> 
> >> One reason to keep Users & Contacts separate is...because that is normal for the average enterprise app - your have employees (users) and customers (contacts) - employees/users have different roles/privileges from customers. 
> >> 
> >> The reason they are separated in the secured (PL) version of contacts-mobile-basic is because it simply evolved that way - contacts came first - users/roles added after the fact.   Ideally we would not modify the original too much as it allows a nice learning progression - start with the original contacts-mobile-basic, then upgrade to contacts-mobile-basic-secured, then upgrade to contacts-mobile-basic-secured-cordova (names just made up). 
> >> 
> >> 
> >> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <[hidden email]> wrote: 
> >> 
> >>> Sure ! 
> >>> Be sure to check this with Joshua as he drives the backend bits 
> >>> S?bi 
> >>> 
> >>> Envoy? de mon iPhone 
> >>> 
> >>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <[hidden email]> a ?crit : 
> >>>> 
> >>>> Hi, 
> >>>> 
> >>>> How about merging the User model and the Contact into one entity? Seems like they have a lot in common, do we really need 2? 
> >>>> 
> >>>> Cheers, 
> >>>> Erik Jan 
> >>>> 
> >>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <[hidden email]> wrote: 
> >>>>> 
> >>>>> We should be using the email as alias and the email should also be used as login when registering in the secured part. A registration should also trigger the creation of that user / contact in the application. 
> >>>>> Author can be left empty By the client and filled by the backend . https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor must stay because the receiver must know who sends the message. 
> >>>>> 
> >>>>> Envoy? de mon iPhone 
> >>>>> 
> >>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <[hidden email]> a ?crit : 
> >>>>>> 
> >>>>>> Hi, 
> >>>>>> 
> >>>>>> I was working on the aerogear-push-quickstarts for Cordova and was wondering what to put for the alias on registration. The version that is there now has users that logs in and contacts that are fetched. What seems to be missing is that everybody gets all contacts instead of just mine (maybe that is fine), but users that sign up for the app are not contacts. So when I want to send a message to a specific mobile user they are not in my list and there is no way to have to define an alias to send to. 
> >>>>>> 
> >>>>>> Also the interface for sending push notifications includes a author. I think it would be better if we remove this and let the service put in the logged in user. That way you can?t pretend to send a message like someone else. 
> >>>>>> 
> >>>>>> What do you think? 
> >>>>>> 
> >>>>>> Cheers, 
> >>>>>> Erik Jan 
> >>>>>> _______________________________________________ 
> >>>>>> aerogear-dev mailing list 
> >>>>>> [hidden email] 
> >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>> 
> >>>>> _______________________________________________ 
> >>>>> aerogear-dev mailing list 
> >>>>> [hidden email] 
> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>> 
> >>>> 
> >>>> _______________________________________________ 
> >>>> aerogear-dev mailing list 
> >>>> [hidden email] 
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>> 
> >>> _______________________________________________ 
> >>> aerogear-dev mailing list 
> >>> [hidden email] 
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> 
> >> 
> >> _______________________________________________ 
> >> aerogear-dev mailing list 
> >> [hidden email] 
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > 
> > 
> > _______________________________________________ 
> > aerogear-dev mailing list 
> > [hidden email] 
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> _______________________________________________ 
> 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-contacts-mobile-basic-quick-start-tp7534p7636.html
> 
> To start a new topic under aerogear-dev, email [hidden email] 
> To unsubscribe from aerogear-dev, click here.
> NAML
> 
> 
> View this message in context: RE: [aerogear-dev] contacts-mobile-basic quick start
> 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/20140506/bd5a848e/attachment-0001.html 

From scm.blanc at gmail.com  Tue May  6 12:31:42 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 6 May 2014 18:31:42 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <C6EFE2C9-FE64-4D87-B21D-BF550130BBD0@gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<2a9f339f.00001c7c.0000002d@AMENTRAR978LMH>
	<C6EFE2C9-FE64-4D87-B21D-BF550130BBD0@gmail.com>
Message-ID: <CAD_dpu14noCN+1k2Vyhz2JT_rsDRGv34znifr3ViObw5BQmpCA@mail.gmail.com>

On Tue, May 6, 2014 at 6:18 PM, Christos Vasilakis <cvasilak at gmail.com>wrote:

> Hi Joshua,
>
> my belief is that for PUT, DELETE ops the client should go against
> /contacts/{id} URI
>

+1 , The best practice with REST is  that an existing resource
representation includes the id in the URI.


> Anyone else have a different view of it ?
>
> Thanks,
> Christos
>
>
> On May 1, 2014, at 5:32 PM, joshuaw <jowilson at redhat.com> wrote:
>
> Christos,
>
>
>
> To answer a) since the Contact is being passed in, it is not necessary to
> also pass in the ID.  For PUT all the information needs to be passed back
> for the update. While the DELETE only needs the ID, the whole contact is
> being sent.
>
>
>
> I am open to discussing this if you think there is something wrong with
> the design.
>
>
>
> Joshua
>
>
>
> *From:* Christos Vasilakis [via aerogear-dev] [mailto:[hidden email]]
> *Sent:* Thursday, May 01, 2014 7:27 AM
> *To:* joshuaw
> *Subject:* Re: [aerogear-dev] contacts-mobile-basic quick start
>
>
>
> Hi everyone,
>
> have started working on the iOS native client of the contacts quick start
> app. Based on edewit branch[1] (which creates a contact on signup of a
> user) have created an initial version of the iOS client and you can find it
> here [2], together with a screencast showcasing the app in action [3].
>
> Some comments observed during writing of the application which would like
> your feedback:
>
> a)  for PUT, DELETE operations noticed that the jax-rs backend expects the
> id of the Contact to be present in the body of the request. Not sure why
> this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?
>
> b) currently roles are used to distinguish between who is able to
> create/update/delete contact. When a user signs up (and contact is
> created),  by default the user is _not_ able to apply any CRUD operations
> apart from viewing (any operation results in unauthorised error). If we
> agree on this behaviour, would like to know how can I determine the role of
> the user (in order to update the UI accordingly, eg. disabling add,edit UI
> elements). Looking at the json response upon login of the user, couldn?t
> determine a ?key? that specifies the role (apart from an ?admin? key which
> stayed the same regardless of the type of the user).
>
>
> Thanks,
> Christos
>
> [1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
> [2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
> [3] https://vimeo.com/93471554
>
>
>
> On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <[hidden email]> wrote:
>
>
> > Right, that makes sense, so let?s not join them. The alternate thing to
> do is to create a contact on sign up, because if you want to receive push
> notifications at least you should be in the list of contacts. We will still
> need to change the sign up page a little as we need a phone number and a
> birth date as well in order to create a contact.
> >
> > On 23 Apr,2014, at 16:26 , Burr Sutter <[hidden email]> wrote:
> >
> >> These are not strongly held opinions
> >>
> >> One reason to keep Users & Contacts separate is...because that is
> normal for the average enterprise app - your have employees (users) and
> customers (contacts) - employees/users have different roles/privileges from
> customers.
> >>
> >> The reason they are separated in the secured (PL) version of
> contacts-mobile-basic is because it simply evolved that way - contacts came
> first - users/roles added after the fact.   Ideally we would not modify the
> original too much as it allows a nice learning progression - start with the
> original contacts-mobile-basic, then upgrade to
> contacts-mobile-basic-secured, then upgrade to
> contacts-mobile-basic-secured-cordova (names just made up).
> >>
> >>
> >> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <[hidden email]> wrote:
> >>
> >>> Sure !
> >>> Be sure to check this with Joshua as he drives the backend bits
> >>> S?bi
> >>>
> >>> Envoy? de mon iPhone
> >>>
> >>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <[hidden email]> a ?crit :
> >>>>
> >>>> Hi,
> >>>>
> >>>> How about merging the User model and the Contact into one entity?
> Seems like they have a lot in common, do we really need 2?
> >>>>
> >>>> Cheers,
> >>>> Erik Jan
> >>>>
> >>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <[hidden email]> wrote:
> >>>>>
> >>>>> We should be using the email as alias and the email should also be
> used as login when registering in the secured part. A registration should
> also trigger the creation of that user / contact in the application.
> >>>>> Author can be left empty By the client and filled by the backend .
> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor must
> stay because the receiver must know who sends the message.
> >>>>>
> >>>>> Envoy? de mon iPhone
> >>>>>
> >>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <[hidden email]> a ?crit
> :
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> I was working on the aerogear-push-quickstarts for Cordova and was
> wondering what to put for the alias on registration. The version that is
> there now has users that logs in and contacts that are fetched. What seems
> to be missing is that everybody gets all contacts instead of just mine
> (maybe that is fine), but users that sign up for the app are not contacts.
> So when I want to send a message to a specific mobile user they are not in
> my list and there is no way to have to define an alias to send to.
> >>>>>>
> >>>>>> Also the interface for sending push notifications includes a
> author. I think it would be better if we remove this and let the service
> put in the logged in user. That way you can?t pretend to send a message
> like someone else.
> >>>>>>
> >>>>>> What do you think?
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Erik Jan
> >>>>>> _______________________________________________
> >>>>>> aerogear-dev mailing list
> >>>>>> [hidden email]
> >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>
> >>>>> _______________________________________________
> >>>>> aerogear-dev mailing list
> >>>>> [hidden email]
> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>> [hidden email]
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> [hidden email]
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> [hidden email]
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > [hidden email]
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> 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-contacts-mobile-basic-quick-start-tp7534p7636.html
>
> To start a new topic under aerogear-dev, email [hidden email]
> To unsubscribe from aerogear-dev, click here.
> NAML<http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> ------------------------------
> View this message in context: RE: [aerogear-dev] contacts-mobile-basic
> quick start<http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-contacts-mobile-basic-quick-start-tp7534p7637.html>
> Sent from the aerogear-dev mailing list archive<http://aerogear-dev.1069024.n5.nabble.com/>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/20140506/ddb4a324/attachment.html 

From matzew at apache.org  Tue May  6 16:59:21 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 May 2014 22:59:21 +0200
Subject: [aerogear-dev] AeroGear Android Push 0.1.1
In-Reply-To: <CAAg5f2SJJJBoacr3O2v_Dq5JGNCyx3suE9assZhMn6kbriRNvw@mail.gmail.com>
References: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>
	<CAD_dpu2aOBdcuuY1VqoeyVR1De4gY6yREVqLuUou5zBzNGYV5g@mail.gmail.com>
	<CAKjsGbuRLZSoGuT-_Ewu+F3JDwUO7E71dZO4A_XMGYgeDoDJDw@mail.gmail.com>
	<20140506144210.GE2638@abstractj.org> <5368F7A2.2070706@redhat.com>
	<CAAg5f2SJJJBoacr3O2v_Dq5JGNCyx3suE9assZhMn6kbriRNvw@mail.gmail.com>
Message-ID: <CAAg5f2T-PVtuOiv+5_j4W4hzjdaUcaB0F5-Ucv62Ti-Y7Tv3Wg@mail.gmail.com>

regarding the version # - I'd prefer to bump up to 0.2.0


On Tue, May 6, 2014 at 5:13 PM, Matthias Wessendorf <matzew at apache.org>wrote:

>
>
>
> On Tue, May 6, 2014 at 4:54 PM, Summers Pittman <supittma at redhat.com>wrote:
>
>> On Tue 06 May 2014 10:42:10 AM EDT, Bruno Oliveira wrote:
>> > Option 2 sounds like a plan to me
>> >
>>
>> Sweet.
>>
>> RestProvider throws httpexception (status:302)
>> Registrar catches it and logs a warning.
>> Retries with new location.
>> if OK then onSuccess
>> else then onError.
>>
>> IE We will only follow ONE redirect.
>>
>
> yes :) no need to join a redirect party
>
>>
>> > On 2014-05-06, Daniel Passos wrote:
>> >> Talking with Summers about what is the best options to solved that, we
>> have
>> >> some options:
>> >>
>> >> 1) Catch the 302 and handle it inside of the rest provider. [1]
>> >>
>> >> 2) We can fix the IOException which is being thrown, throw the
>> >> HttpException correctly, and in the registrar check for 30x and then
>> rerun
>> >> the operation [2]
>> >>
>> >> 3) We let the HttpException escape to the callback handler
>> >>
>> >> We don't like the option 1, because increases complexity in the
>> >> HttpRestProvider class and it hides the 30x messages from the
>> developers
>> >> should they want to handle them.  Furthermore, Summers argues that
>> since
>> >> the registration code is being called often it would be better for the
>> >> developer to be aware of them and have to handle them in her code
>> instead
>> >> of ours.  In short, if there are redirects then the developer should be
>> >> made aware so she can update her URL and make fewer HTTP requests
>> (this is
>> >> important on mobile for battery life, data caps, etc).
>> >>
>> >> [1]
>> >>
>> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/http/HttpRestProvider.java#L256
>> >> [2]
>> >>
>> https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/impl/unifiedpush/AeroGearGCMPushRegistrar.java#L139-L144
>> >>
>> >> So, wdyt?
>> >>
>> >>
>> >>
>> >> On Tue, May 6, 2014 at 6:47 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>> >>
>> >>> Hi !
>> >>> I just gave it a test with the Push HelloWorld :
>> >>>
>> >>> - https://issues.jboss.org/browse/AGPUSH-627 is fixed , I'm getting a
>> >>> nice error notification on the device
>> >>>
>> >>> - https://issues.jboss.org/browse/AGDROID-214 -> I'm getting exactly
>> the
>> >>> same issue as Matzew , looks like the redirect is not working.
>> >>>
>> >>> Sebi
>> >>>
>> >>>
>> >>>
>> >>> On Fri, May 2, 2014 at 5:06 PM, Daniel Passos <daniel at passos.me>
>> wrote:
>> >>>
>> >>>> We have found a bug[1] in the AeroGear Android Push 0.1. It was
>> fixed and
>> >>>> the new version (0.1.1) was already sent to nexus[2].
>> >>>>
>> >>>> We'd like to ship it to Maven central next wednesday.
>> >>>>
>> >>>> [1] https://issues.jboss.org/browse/AGDROID-214
>> >>>> [2]
>> >>>>
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3139/
>> >>>>
>> >>>>
>> >>>> _______________________________________________
>> >>>> aerogear-dev mailing list
>> >>>> aerogear-dev at lists.jboss.org
>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> aerogear-dev mailing list
>> >>> aerogear-dev at lists.jboss.org
>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>
>> >
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >> aerogear-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> >
>> > --
>> >
>> > abstractj
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Summers Pittman
>> >>Phone:404 941 4698
>> >>Java is my crack.
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140506/eba9d839/attachment-0001.html 

From qmx at qmx.me  Tue May  6 17:47:36 2014
From: qmx at qmx.me (Douglas Campos)
Date: Tue, 6 May 2014 18:47:36 -0300
Subject: [aerogear-dev] AeroGear Android Push 0.1.1
In-Reply-To: <CAAg5f2T-PVtuOiv+5_j4W4hzjdaUcaB0F5-Ucv62Ti-Y7Tv3Wg@mail.gmail.com>
References: <CAKjsGbsCN3kStVWfOV3nSppg0PAhxhsm=4Lbp7D8pcruB5nikA@mail.gmail.com>
	<CAD_dpu2aOBdcuuY1VqoeyVR1De4gY6yREVqLuUou5zBzNGYV5g@mail.gmail.com>
	<CAKjsGbuRLZSoGuT-_Ewu+F3JDwUO7E71dZO4A_XMGYgeDoDJDw@mail.gmail.com>
	<20140506144210.GE2638@abstractj.org> <5368F7A2.2070706@redhat.com>
	<CAAg5f2SJJJBoacr3O2v_Dq5JGNCyx3suE9assZhMn6kbriRNvw@mail.gmail.com>
	<CAAg5f2T-PVtuOiv+5_j4W4hzjdaUcaB0F5-Ucv62Ti-Y7Tv3Wg@mail.gmail.com>
Message-ID: <20140506214736.GA1275@rohan.local>

On Tue, May 06, 2014 at 10:59:21PM +0200, Matthias Wessendorf wrote:
> regarding the version # - I'd prefer to bump up to 0.2.0

On what reasoning? It feels like a patch release to me.

-- 
qmx

From jowilson at redhat.com  Tue May  6 19:08:50 2014
From: jowilson at redhat.com (Joshua Wilson)
Date: Tue, 6 May 2014 19:08:50 -0400 (EDT)
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <CAD_dpu14noCN+1k2Vyhz2JT_rsDRGv34znifr3ViObw5BQmpCA@mail.gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<2a9f339f.00001c7c.0000002d@AMENTRAR978LMH>
	<C6EFE2C9-FE64-4D87-B21D-BF550130BBD0@gmail.com>
	<CAD_dpu14noCN+1k2Vyhz2JT_rsDRGv34znifr3ViObw5BQmpCA@mail.gmail.com>
Message-ID: <2102f268.000024fc.0000001e@AMENTRAR978LMH>

We are fixing the REST API to fit the ?Standard?, that would match your 
request to include IDs. (my fault for knowing the standard/right way)



From: S?bastien Blanc [via aerogear-dev] 
[mailto:ml-node+s1069024n7686h81 at n5.nabble.com]
Sent: Tuesday, May 06, 2014 12:32 PM
To: joshuaw
Subject: Re: [aerogear-dev] contacts-mobile-basic quick start







On Tue, May 6, 2014 at 6:18 PM, Christos Vasilakis <[hidden email]> wrote:

Hi Joshua,



my belief is that for PUT, DELETE ops the client should go against 
/contacts/{id} URI



+1 , The best practice with REST is  that an existing resource 
representation includes the id in the URI.





Anyone else have a different view of it ?



Thanks,

Christos





On May 1, 2014, at 5:32 PM, joshuaw <[hidden email]> wrote:



Christos,



To answer a) since the Contact is being passed in, it is not necessary to 
also pass in the ID.  For PUT all the information needs to be passed back 
for the update. While the DELETE only needs the ID, the whole contact is 
being sent.



I am open to discussing this if you think there is something wrong with the 
design.



Joshua



From: Christos Vasilakis [via aerogear-dev] [mailto:[hidden email]]
Sent: Thursday, May 01, 2014 7:27 AM
To: joshuaw
Subject: Re: [aerogear-dev] contacts-mobile-basic quick start



Hi everyone,

have started working on the iOS native client of the contacts quick start 
app. Based on edewit branch[1] (which creates a contact on signup of a user) 
have created an initial version of the iOS client and you can find it here 
[2], together with a screencast showcasing the app in action [3].

Some comments observed during writing of the application which would like 
your feedback:

a)  for PUT, DELETE operations noticed that the jax-rs backend expects the 
id of the Contact to be present in the body of the request. Not sure why 
this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?

b) currently roles are used to distinguish between who is able to 
create/update/delete contact. When a user signs up (and contact is created), 
by default the user is _not_ able to apply any CRUD operations apart from 
viewing (any operation results in unauthorised error). If we agree on this 
behaviour, would like to know how can I determine the role of the user (in 
order to update the UI accordingly, eg. disabling add,edit UI elements). 
Looking at the json response upon login of the user, couldn?t determine a 
?key? that specifies the role (apart from an ?admin? key which stayed the 
same regardless of the type of the user).


Thanks,
Christos

[1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
[2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
[3] https://vimeo.com/93471554



On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <[hidden email]> wrote:




> Right, that makes sense, so let?s not join them. The alternate thing to do 
> is to create a contact on sign up, because if you want to receive push 
> notifications at least you should be in the list of contacts. We will 
> still need to change the sign up page a little as we need a phone number 
> and a birth date as well in order to create a contact.
>
> On 23 Apr,2014, at 16:26 , Burr Sutter <[hidden email]> wrote:
>
>> These are not strongly held opinions
>>
>> One reason to keep Users & Contacts separate is...because that is normal 
>> for the average enterprise app - your have employees (users) and 
>> customers (contacts) - employees/users have different roles/privileges 
>> from customers.
>>
>> The reason they are separated in the secured (PL) version of 
>> contacts-mobile-basic is because it simply evolved that way - contacts 
>> came first - users/roles added after the fact.   Ideally we would not 
>> modify the original too much as it allows a nice learning progression - 
>> start with the original contacts-mobile-basic, then upgrade to 
>> contacts-mobile-basic-secured, then upgrade to 
>> contacts-mobile-basic-secured-cordova (names just made up).
>>
>>
>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <[hidden email]> wrote:
>>
>>> Sure !
>>> Be sure to check this with Joshua as he drives the backend bits
>>> S?bi
>>>
>>> Envoy? de mon iPhone
>>>
>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <[hidden email]> a ?crit :
>>>>
>>>> Hi,
>>>>
>>>> How about merging the User model and the Contact into one entity? Seems 
>>>> like they have a lot in common, do we really need 2?
>>>>
>>>> Cheers,
>>>> Erik Jan
>>>>
>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <[hidden email]> wrote:
>>>>>
>>>>> We should be using the email as alias and the email should also be 
>>>>> used as login when registering in the secured part. A registration 
>>>>> should also trigger the creation of that user / contact in the 
>>>>> application.
>>>>> Author can be left empty By the client and filled by the backend . 
>>>>> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor 
>>>>> must stay because the receiver must know who sends the message.
>>>>>
>>>>> Envoy? de mon iPhone
>>>>>
>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <[hidden email]> a ?crit :
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I was working on the aerogear-push-quickstarts for Cordova and was 
>>>>>> wondering what to put for the alias on registration. The version that 
>>>>>> is there now has users that logs in and contacts that are fetched. 
>>>>>> What seems to be missing is that everybody gets all contacts instead 
>>>>>> of just mine (maybe that is fine), but users that sign up for the app 
>>>>>> are not contacts. So when I want to send a message to a specific 
>>>>>> mobile user they are not in my list and there is no way to have to 
>>>>>> define an alias to send to.
>>>>>>
>>>>>> Also the interface for sending push notifications includes a author. 
>>>>>> I think it would be better if we remove this and let the service put 
>>>>>> in the logged in user. That way you can?t pretend to send a message 
>>>>>> like someone else.
>>>>>>
>>>>>> What do you think?
>>>>>>
>>>>>> Cheers,
>>>>>> Erik Jan
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> [hidden email]
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/aerogear-dev






_______________________________________________
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-contacts-mobile-basic-quick-start-tp7534p7636.html

To start a new topic under aerogear-dev, email [hidden email]
To unsubscribe from aerogear-dev, click here.
NAML



  _____

View this message in context: RE: [aerogear-dev] contacts-mobile-basic quick 
start 
<http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-contacts-mobile-basic-quick-start-tp7534p7637.html>
Sent from the aerogear-dev mailing list archive 
<http://aerogear-dev.1069024.n5.nabble.com/>  at Nabble.com.

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev




_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev




_______________________________________________
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-contacts-mobile-basic-quick-start-tp7534p7686.html

To start a new topic under aerogear-dev, email 
ml-node+s1069024n1h46 at n5.nabble.com
To unsubscribe from aerogear-dev, click here 
<http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=am93aWxzb25AcmVkaGF0LmNvbXwxfC0xNTQxNTU0OTE2> 
.
NAML

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140506/a210e0dc/attachment-0001.html 

From jowilson at redhat.com  Tue May  6 19:09:10 2014
From: jowilson at redhat.com (joshuaw)
Date: Tue, 6 May 2014 16:09:10 -0700 (PDT)
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <CAD_dpu14noCN+1k2Vyhz2JT_rsDRGv34znifr3ViObw5BQmpCA@mail.gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<5B19161A-39B3-4F60-9F89-722D16A1B513@gmail.com>
	<8DBA0510-C8DE-4390-96A4-B0332DF72E69@redhat.com>
	<C7F93642-DB8E-42C8-8A51-EBA0BDEF2AF0@gmail.com>
	<DE14152A-3B3A-4AA7-B2D5-8D4616AC90F4@redhat.com>
	<1961051A-24C4-4A8F-98FA-F5667B139810@redhat.com>
	<3158CBEC-1305-4A12-9463-103AE8E7D868@gmail.com>
	<2a9f339f.00001c7c.0000002d@AMENTRAR978LMH>
	<C6EFE2C9-FE64-4D87-B21D-BF550130BBD0@gmail.com>
	<CAD_dpu14noCN+1k2Vyhz2JT_rsDRGv34znifr3ViObw5BQmpCA@mail.gmail.com>
Message-ID: <2102f268.000024fc.0000001e@AMENTRAR978LMH>

We are fixing the REST API to fit the ?Standard?, that would match your 
request to include IDs. (my fault for knowing the standard/right way)



From: S?bastien Blanc [via aerogear-dev] 
[mailto:ml-node+s1069024n7686h81 at n5.nabble.com]
Sent: Tuesday, May 06, 2014 12:32 PM
To: joshuaw
Subject: Re: [aerogear-dev] contacts-mobile-basic quick start







On Tue, May 6, 2014 at 6:18 PM, Christos Vasilakis <[hidden email]> wrote:

Hi Joshua,



my belief is that for PUT, DELETE ops the client should go against 
/contacts/{id} URI



+1 , The best practice with REST is  that an existing resource 
representation includes the id in the URI.





Anyone else have a different view of it ?



Thanks,

Christos





On May 1, 2014, at 5:32 PM, joshuaw <[hidden email]> wrote:



Christos,



To answer a) since the Contact is being passed in, it is not necessary to 
also pass in the ID.  For PUT all the information needs to be passed back 
for the update. While the DELETE only needs the ID, the whole contact is 
being sent.



I am open to discussing this if you think there is something wrong with the 
design.



Joshua



From: Christos Vasilakis [via aerogear-dev] [mailto:[hidden email]]
Sent: Thursday, May 01, 2014 7:27 AM
To: joshuaw
Subject: Re: [aerogear-dev] contacts-mobile-basic quick start



Hi everyone,

have started working on the iOS native client of the contacts quick start 
app. Based on edewit branch[1] (which creates a contact on signup of a user) 
have created an initial version of the iOS client and you can find it here 
[2], together with a screencast showcasing the app in action [3].

Some comments observed during writing of the application which would like 
your feedback:

a)  for PUT, DELETE operations noticed that the jax-rs backend expects the 
id of the Contact to be present in the body of the request. Not sure why 
this was chosen instead of @Path(?id?) resulting against /contacts/{id} ?

b) currently roles are used to distinguish between who is able to 
create/update/delete contact. When a user signs up (and contact is created), 
by default the user is _not_ able to apply any CRUD operations apart from 
viewing (any operation results in unauthorised error). If we agree on this 
behaviour, would like to know how can I determine the role of the user (in 
order to update the UI accordingly, eg. disabling add,edit UI elements). 
Looking at the json response upon login of the user, couldn?t determine a 
?key? that specifies the role (apart from an ?admin? key which stayed the 
same regardless of the type of the user).


Thanks,
Christos

[1] https://github.com/edewit/jboss-wfk-quickstarts/tree/push_and_secured
[2] https://github.com/cvasilak/aerogear-push-quickstarts/tree/ios
[3] https://vimeo.com/93471554



On Apr 23, 2014, at 5:43 PM, Erik Jan de Wit <[hidden email]> wrote:




> Right, that makes sense, so let?s not join them. The alternate thing to do 
> is to create a contact on sign up, because if you want to receive push 
> notifications at least you should be in the list of contacts. We will 
> still need to change the sign up page a little as we need a phone number 
> and a birth date as well in order to create a contact.
>
> On 23 Apr,2014, at 16:26 , Burr Sutter <[hidden email]> wrote:
>
>> These are not strongly held opinions
>>
>> One reason to keep Users & Contacts separate is...because that is normal 
>> for the average enterprise app - your have employees (users) and 
>> customers (contacts) - employees/users have different roles/privileges 
>> from customers.
>>
>> The reason they are separated in the secured (PL) version of 
>> contacts-mobile-basic is because it simply evolved that way - contacts 
>> came first - users/roles added after the fact.   Ideally we would not 
>> modify the original too much as it allows a nice learning progression - 
>> start with the original contacts-mobile-basic, then upgrade to 
>> contacts-mobile-basic-secured, then upgrade to 
>> contacts-mobile-basic-secured-cordova (names just made up).
>>
>>
>> On Apr 23, 2014, at 10:16 AM, S?bastien Blanc <[hidden email]> wrote:
>>
>>> Sure !
>>> Be sure to check this with Joshua as he drives the backend bits
>>> S?bi
>>>
>>> Envoy? de mon iPhone
>>>
>>>> Le 23 avr. 2014 ? 15:56, Erik Jan de Wit <[hidden email]> a ?crit :
>>>>
>>>> Hi,
>>>>
>>>> How about merging the User model and the Contact into one entity? Seems 
>>>> like they have a lot in common, do we really need 2?
>>>>
>>>> Cheers,
>>>> Erik Jan
>>>>
>>>>> On 23 Apr,2014, at 14:34 , S?bastien Blanc <[hidden email]> wrote:
>>>>>
>>>>> We should be using the email as alias and the email should also be 
>>>>> used as login when registering in the secured part. A registration 
>>>>> should also trigger the creation of that user / contact in the 
>>>>> application.
>>>>> Author can be left empty By the client and filled by the backend . 
>>>>> https://github.com/sebastienblanc/jboss-wfk-quickstarts/tree/push_and_securedAuthor 
>>>>> must stay because the receiver must know who sends the message.
>>>>>
>>>>> Envoy? de mon iPhone
>>>>>
>>>>>> Le 23 avr. 2014 ? 13:35, Erik Jan de Wit <[hidden email]> a ?crit :
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I was working on the aerogear-push-quickstarts for Cordova and was 
>>>>>> wondering what to put for the alias on registration. The version that 
>>>>>> is there now has users that logs in and contacts that are fetched. 
>>>>>> What seems to be missing is that everybody gets all contacts instead 
>>>>>> of just mine (maybe that is fine), but users that sign up for the app 
>>>>>> are not contacts. So when I want to send a message to a specific 
>>>>>> mobile user they are not in my list and there is no way to have to 
>>>>>> define an alias to send to.
>>>>>>
>>>>>> Also the interface for sending push notifications includes a author. 
>>>>>> I think it would be better if we remove this and let the service put 
>>>>>> in the logged in user. That way you can?t pretend to send a message 
>>>>>> like someone else.
>>>>>>
>>>>>> What do you think?
>>>>>>
>>>>>> Cheers,
>>>>>> Erik Jan
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> [hidden email]
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/aerogear-dev






_______________________________________________
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-contacts-mobile-basic-quick-start-tp7534p7636.html

To start a new topic under aerogear-dev, email [hidden email]
To unsubscribe from aerogear-dev, click here.
NAML



  _____

View this message in context: RE: [aerogear-dev] contacts-mobile-basic quick 
start 
<http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-contacts-mobile-basic-quick-start-tp7534p7637.html>
Sent from the aerogear-dev mailing list archive 
<http://aerogear-dev.1069024.n5.nabble.com/>  at Nabble.com.

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev




_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev




_______________________________________________
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-contacts-mobile-basic-quick-start-tp7534p7686.html

To start a new topic under aerogear-dev, email 
ml-node+s1069024n1h46 at n5.nabble.com
To unsubscribe from aerogear-dev, click here 
<http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=am93aWxzb25AcmVkaGF0LmNvbXwxfC0xNTQxNTU0OTE2> 
.
NAML





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-contacts-mobile-basic-quick-start-tp7534p7689.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/20140506/a210e0dc/attachment-0003.html 

From scm.blanc at gmail.com  Wed May  7 03:13:56 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 7 May 2014 09:13:56 +0200
Subject: [aerogear-dev] Release of 0.10.3 ?
In-Reply-To: <CAAg5f2RfBhxrb3SoJbfPAFcQ1=vFj467ObTVHNXvgnhha=R2xQ@mail.gmail.com>
References: <CAAg5f2RfBhxrb3SoJbfPAFcQ1=vFj467ObTVHNXvgnhha=R2xQ@mail.gmail.com>
Message-ID: <CAD_dpu2hVg0=OTWqRW4rL4nWqs-Sh66VmexSAu92bR3nyjDQ1A@mail.gmail.com>

Sounds good to me !
Ping me when you start the process so that I provide a Console UI update PR.

Seb



On Tue, May 6, 2014 at 3:57 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hello,
>
> based on Eriks latest Cordova Plugin release (got a new, simplified API),
> he also updated the Cordova code snippets.
>
> This is a good reason to retire the 0.10.2 version that we ship (and
> provide on OpenShift online).
>
> In addition I also added some improvements for GCM logging/exception
> handling (see  AGPUSH-624).
>
> I'd be happy to get the release process of that branch started soon...
>
> https://github.com/aerogear/aerogear-unifiedpush-server/commits/0.10.x
>
>
>
> Any comments ?
>
>
> -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/20140507/3ef59fe4/attachment.html 

From edewit at redhat.com  Wed May  7 03:36:28 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 7 May 2014 09:36:28 +0200
Subject: [aerogear-dev] paging installations new console
Message-ID: <9EA24B7B-B865-46AD-B450-B2910704132E@redhat.com>

Hi all,

As we are working on implementing the new visual design for the console we ran into something. Right now when you fetch a PushApplication from the rest service everything is eager fetched including all variants for that application but also all installations for all these variants.

Now in the old console these installations where only used to list the number of installations on the ?application details? page next to the variant, for the new console I?ve introduced a count ?call? to do the same so we no longer need this eager fetch.

This count query is a bit hard as we have separated the association of the variants per type so in order to have a count of the number of installations we have to do x queries where ( x is the number of device types)

Example:

"select v.variantID, count(*) from PushApplication pa join pa.androidVariants v join v.installations i "
                + "where pushApplicationID = :pushApplicationID and i.enabled = true "
                + "group by v.variantID";

This query will give the total number of installations for each variant, but only for android. So what I would like to suggest it to simplify the data model and only have a relation with variants instead of one per type this will also make the data model more extendable (when a new device type is introduced the data model doesn?t have to change). If grouping of these variants is needed clients will need to do it themselves.

WDYT
	Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140507/1af742ca/attachment.html 

From kpiwko at redhat.com  Wed May  7 04:39:44 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 7 May 2014 10:39:44 +0200
Subject: [aerogear-dev] paging installations new console
In-Reply-To: <9EA24B7B-B865-46AD-B450-B2910704132E@redhat.com>
References: <9EA24B7B-B865-46AD-B450-B2910704132E@redhat.com>
Message-ID: <20140507103944.44825e8d@kapy-ntb-x220>

I think it is a good idea to simplify underlying model. Could we 
additionally provide SQL views that groups only one variant and expose it
via REST point? 

So clients will get the best of both worlds.

Not sure if H2 supports SQL views but there is a different way how to map
data there for sure.

Karel


On Wed, 7 May 2014 09:36:28 +0200
Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi all,
> 
> As we are working on implementing the new visual design for the console we
> ran into something. Right now when you fetch a PushApplication from the rest
> service everything is eager fetched including all variants for that
> application but also all installations for all these variants.
> 
> Now in the old console these installations where only used to list the number
> of installations on the ?application details? page next to the variant, for
> the new console I?ve introduced a count ?call? to do the same so we no longer
> need this eager fetch.
> 
> This count query is a bit hard as we have separated the association of the
> variants per type so in order to have a count of the number of installations
> we have to do x queries where ( x is the number of device types)
> 
> Example:
> 
> "select v.variantID, count(*) from PushApplication pa join pa.androidVariants
> v join v.installations i "
>                 + "where pushApplicationID = :pushApplicationID and i.enabled
> = true "
>                 + "group by v.variantID";
> 
> This query will give the total number of installations for each variant, but
> only for android. So what I would like to suggest it to simplify the data
> model and only have a relation with variants instead of one per type this
> will also make the data model more extendable (when a new device type is
> introduced the data model doesn?t have to change). If grouping of these
> variants is needed clients will need to do it themselves.
> 
> WDYT
> 	Erik Jan

From matzew at apache.org  Wed May  7 05:54:17 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 7 May 2014 11:54:17 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
Message-ID: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>

Hi,

as discussed , we need some sort of 'stats' around push, like:
* time of sending
* receivers (e.g. categories, alias ?)
* content/payload of the message
* could be sent out to APNs/GCM


But, where, or how to add this ?
My current thought is:

When a user did select an "Application", he enters the "Application Details
Page" (see [1]), now here, on the sidebar (see [2]) he would see the
"Notifications" icon.

Clicking on that  "Notifications" icon, would give you a new page, that
contains the "Send Notifications..." button (currently located in [1]), and
a table of all the push messages that were sent out for the _current_
selected Application.

Any thoughts ?

-Matthias

[1]
https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
[2]
https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140507/ad79259f/attachment.html 

From matzew at apache.org  Wed May  7 07:35:15 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 7 May 2014 13:35:15 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
Message-ID: <CAAg5f2RMHB019npB11wmGtpXMWZSHwHN=MnJKe8XZ+8oTexXgg@mail.gmail.com>

On Wed, May 7, 2014 at 11:54 AM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hi,
>
> as discussed , we need some sort of 'stats' around push, like:
> * time of sending
> * receivers (e.g. categories, alias ?)
> * content/payload of the message
> * could be sent out to APNs/GCM
>
>
> But, where, or how to add this ?
> My current thought is:
>
> When a user did select an "Application", he enters the "Application
> Details Page" (see [1]), now here, on the sidebar (see [2]) he would see
> the "Notifications" icon.
>
> Clicking on that  "Notifications" icon, would give you a new page, that
> contains the "Send Notifications..." button (currently located in [1]), and
> a table of all the push messages that were sent out for the _current_
> selected Application.
>


Actually..... not sure... perhaps we keep the "Application Details Page"
for just working w/ the App (e.g. renaming, updating certs/keys), and
always have the "Notification icon" on the sidebar.

When you click on the icon, you have to select a Application, and after
that, you see the new page, that contains the "Send Notifications..."
button (currently located in [1]), and a table of all the push messages
that were sent out for the _current_ selected Application.

any thoughts ?


-Matthias


>
> Any thoughts ?
>
> -Matthias
>
> [1]
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
> [2]
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>
>
> --
> 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/20140507/1e161483/attachment.html 

From edewit at redhat.com  Wed May  7 07:38:42 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 7 May 2014 13:38:42 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CAAg5f2RMHB019npB11wmGtpXMWZSHwHN=MnJKe8XZ+8oTexXgg@mail.gmail.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<CAAg5f2RMHB019npB11wmGtpXMWZSHwHN=MnJKe8XZ+8oTexXgg@mail.gmail.com>
Message-ID: <73D91016-6C8E-4564-9E02-A1369AFD9B92@redhat.com>

Yeah the side bar works better when it?s not context aware, as it?s on all pages.

On 7 May,2014, at 13:35 , Matthias Wessendorf <matzew at apache.org> wrote:

> 
> 
> 
> On Wed, May 7, 2014 at 11:54 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> Hi,
> 
> as discussed , we need some sort of 'stats' around push, like:
> * time of sending
> * receivers (e.g. categories, alias ?)
> * content/payload of the message
> * could be sent out to APNs/GCM
> 
> 
> But, where, or how to add this ? 
> My current thought is:
> 
> When a user did select an "Application", he enters the "Application Details Page" (see [1]), now here, on the sidebar (see [2]) he would see the "Notifications" icon.
> 
> Clicking on that  "Notifications" icon, would give you a new page, that contains the "Send Notifications..." button (currently located in [1]), and a table of all the push messages that were sent out for the _current_ selected Application.
> 
> 
> Actually..... not sure... perhaps we keep the "Application Details Page" for just working w/ the App (e.g. renaming, updating certs/keys), and always have the "Notification icon" on the sidebar.
> 
> When you click on the icon, you have to select a Application, and after that, you see the new page, that contains the "Send Notifications..." button (currently located in [1]), and a table of all the push messages that were sent out for the _current_ selected Application.
> 
> any thoughts ?
> 
> 
> 
> -Matthias
> 
>  
> 
> Any thoughts ? 
> 
> -Matthias
> 
> [1] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
> [2] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
> 
> 
> -- 
> 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/20140507/967c20ec/attachment-0001.html 

From matzew at apache.org  Wed May  7 07:46:56 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 7 May 2014 13:46:56 +0200
Subject: [aerogear-dev] Release of 0.10.3 ?
In-Reply-To: <CAAg5f2RfBhxrb3SoJbfPAFcQ1=vFj467ObTVHNXvgnhha=R2xQ@mail.gmail.com>
References: <CAAg5f2RfBhxrb3SoJbfPAFcQ1=vFj467ObTVHNXvgnhha=R2xQ@mail.gmail.com>
Message-ID: <CAAg5f2RMO9O4euUisr9=DcCMcfTMTYdL3EW6JAjhWL0RQhwtCg@mail.gmail.com>

Any thoughts ?




On Tue, May 6, 2014 at 3:57 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hello,
>
> based on Eriks latest Cordova Plugin release (got a new, simplified API),
> he also updated the Cordova code snippets.
>
> This is a good reason to retire the 0.10.2 version that we ship (and
> provide on OpenShift online).
>
> In addition I also added some improvements for GCM logging/exception
> handling (see  AGPUSH-624).
>
> I'd be happy to get the release process of that branch started soon...
>
> https://github.com/aerogear/aerogear-unifiedpush-server/commits/0.10.x
>
>
>
> Any comments ?
>
>
> -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/20140507/a9b9ab1d/attachment.html 

From matzew at apache.org  Wed May  7 07:55:13 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 7 May 2014 13:55:13 +0200
Subject: [aerogear-dev] New release of the Sender ?
Message-ID: <CAAg5f2SETe4ayT889JSaNORt02gEb5EpOe=a4wSHTnFxfy_ehA@mail.gmail.com>

Hi,

since a few month we had not had a release of the sender. Mainly we got
support for:
* Proxy server configuration
* AGPUSH-559 (HTTPS connection support)
* AGPUSH-619 (fix on the mismatch of the TTL payload)

However there are a few PRs open:
https://github.com/aerogear/aerogear-unifiedpush-java-client/pulls

I'd like to keep them open (as that does not hurt), and evaluate them
_after_ this release.
Especially our QE folks would appreciate a release, as well as the entire
community.

The open PRs will be evaluated right after that release.

Any thoughts ?

-Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140507/f06eee4d/attachment.html 

From daniel.bevenius at gmail.com  Wed May  7 08:02:29 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Wed, 7 May 2014 14:02:29 +0200
Subject: [aerogear-dev] New release of the Sender ?
In-Reply-To: <CAAg5f2SETe4ayT889JSaNORt02gEb5EpOe=a4wSHTnFxfy_ehA@mail.gmail.com>
References: <CAAg5f2SETe4ayT889JSaNORt02gEb5EpOe=a4wSHTnFxfy_ehA@mail.gmail.com>
Message-ID: <CAFJm-3HqJXgu8=pVZFC_Z2pbqt+bGPGOhgOu=e-X4N7nXjb4Sg@mail.gmail.com>

Sounds good.


On 7 May 2014 13:55, Matthias Wessendorf <matzew at apache.org> wrote:

> Hi,
>
> since a few month we had not had a release of the sender. Mainly we got
> support for:
> * Proxy server configuration
> * AGPUSH-559 (HTTPS connection support)
> * AGPUSH-619 (fix on the mismatch of the TTL payload)
>
> However there are a few PRs open:
> https://github.com/aerogear/aerogear-unifiedpush-java-client/pulls
>
> I'd like to keep them open (as that does not hurt), and evaluate them
> _after_ this release.
> Especially our QE folks would appreciate a release, as well as the entire
> community.
>
> The open PRs will be evaluated right after that release.
>
> Any thoughts ?
>
> -Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140507/aa8dddc5/attachment.html 

From daniel at passos.me  Wed May  7 08:03:28 2014
From: daniel at passos.me (Daniel Passos)
Date: Wed, 7 May 2014 09:03:28 -0300
Subject: [aerogear-dev] AeroGear Android Push 0.2 on staging
Message-ID: <CAKjsGbuj-n4GYsMXMko3PES09RB_1KRyK1_hL8zL1CFa0P4eew@mail.gmail.com>

Hi Folks,

The new version of AeroGear Android Push was shipped to Nexus[1].

We plain release it to Maven Central in the next friday

Feel free to test and send your feedback

[1]
http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3165/

-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140507/f1dba6fa/attachment.html 

From bruno at abstractj.org  Wed May  7 08:03:56 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 7 May 2014 09:03:56 -0300
Subject: [aerogear-dev] New release of the Sender ?
In-Reply-To: <CAFJm-3HqJXgu8=pVZFC_Z2pbqt+bGPGOhgOu=e-X4N7nXjb4Sg@mail.gmail.com>
References: <CAAg5f2SETe4ayT889JSaNORt02gEb5EpOe=a4wSHTnFxfy_ehA@mail.gmail.com>
	<CAFJm-3HqJXgu8=pVZFC_Z2pbqt+bGPGOhgOu=e-X4N7nXjb4Sg@mail.gmail.com>
Message-ID: <20140507120356.GA13311@abstractj.org>

Ship it!

On 2014-05-07, Daniel Bevenius wrote:
> Sounds good.
>
>
> On 7 May 2014 13:55, Matthias Wessendorf <matzew at apache.org> wrote:
>
> > Hi,
> >
> > since a few month we had not had a release of the sender. Mainly we got
> > support for:
> > * Proxy server configuration
> > * AGPUSH-559 (HTTPS connection support)
> > * AGPUSH-619 (fix on the mismatch of the TTL payload)
> >
> > However there are a few PRs open:
> > https://github.com/aerogear/aerogear-unifiedpush-java-client/pulls
> >
> > I'd like to keep them open (as that does not hurt), and evaluate them
> > _after_ this release.
> > Especially our QE folks would appreciate a release, as well as the entire
> > community.
> >
> > The open PRs will be evaluated right after that release.
> >
> > Any thoughts ?
> >
> > -Matthias
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From bruno at abstractj.org  Wed May  7 08:10:46 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 7 May 2014 09:10:46 -0300
Subject: [aerogear-dev] Release of 0.10.3 ?
In-Reply-To: <CAAg5f2RMO9O4euUisr9=DcCMcfTMTYdL3EW6JAjhWL0RQhwtCg@mail.gmail.com>
References: <CAAg5f2RfBhxrb3SoJbfPAFcQ1=vFj467ObTVHNXvgnhha=R2xQ@mail.gmail.com>
	<CAAg5f2RMO9O4euUisr9=DcCMcfTMTYdL3EW6JAjhWL0RQhwtCg@mail.gmail.com>
Message-ID: <20140507121046.GB13311@abstractj.org>

+1

In addition, would be nice to replace "AeroGear Push 0.X" by the real
release on OpenShift


On 2014-05-07, Matthias Wessendorf wrote:
> Any thoughts ?
>
>
>
>
> On Tue, May 6, 2014 at 3:57 PM, Matthias Wessendorf <matzew at apache.org>wrote:
>
> > Hello,
> >
> > based on Eriks latest Cordova Plugin release (got a new, simplified API),
> > he also updated the Cordova code snippets.
> >
> > This is a good reason to retire the 0.10.2 version that we ship (and
> > provide on OpenShift online).
> >
> > In addition I also added some improvements for GCM logging/exception
> > handling (see  AGPUSH-624).
> >
> > I'd be happy to get the release process of that branch started soon...
> >
> > https://github.com/aerogear/aerogear-unifiedpush-server/commits/0.10.x
> >
> >
> >
> > Any comments ?
> >
> >
> > -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

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From avibelli at redhat.com  Wed May  7 08:48:23 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Wed, 7 May 2014 05:48:23 -0700 (PDT)
Subject: [aerogear-dev] Release of AeroGear Parent
Message-ID: <1399466903286-7702.post@n5.nabble.com>

Hello, 
I would like to know when the aerogear-parent will be possibly released.
With the latest changes that define the AeroGear BOMs, once aerogear-parent
is released all the AeroGear projects will have the possibility to consume
those BOMs.

Thanks
Andrea



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-tp7702.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Wed May  7 09:15:36 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 7 May 2014 15:15:36 +0200
Subject: [aerogear-dev] AeroGear Android Push 0.2 on staging
In-Reply-To: <CAKjsGbuj-n4GYsMXMko3PES09RB_1KRyK1_hL8zL1CFa0P4eew@mail.gmail.com>
References: <CAKjsGbuj-n4GYsMXMko3PES09RB_1KRyK1_hL8zL1CFa0P4eew@mail.gmail.com>
Message-ID: <CAD_dpu2jn4oe3YwZMfZbgFcNJh=gAjLAJGKeEaHxCqP+JrVTpw@mail.gmail.com>

Tested and works !
Ship it !



On Wed, May 7, 2014 at 2:03 PM, Daniel Passos <daniel at passos.me> wrote:

> Hi Folks,
>
> The new version of AeroGear Android Push was shipped to Nexus[1].
>
> We plain release it to Maven Central in the next friday
>
> Feel free to test and send your feedback
>
> [1]
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3165/
>
> -- 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/20140507/01d5e55c/attachment-0001.html 

From scm.blanc at gmail.com  Wed May  7 09:17:16 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 7 May 2014 15:17:16 +0200
Subject: [aerogear-dev] New release of the Sender ?
In-Reply-To: <20140507120356.GA13311@abstractj.org>
References: <CAAg5f2SETe4ayT889JSaNORt02gEb5EpOe=a4wSHTnFxfy_ehA@mail.gmail.com>
	<CAFJm-3HqJXgu8=pVZFC_Z2pbqt+bGPGOhgOu=e-X4N7nXjb4Sg@mail.gmail.com>
	<20140507120356.GA13311@abstractj.org>
Message-ID: <CAD_dpu12=oUBZipXCJapC1JHOyjG0SFmoOn=odFqS+WepAqYNQ@mail.gmail.com>

+1
@matzew: I can take care of the release if needed



On Wed, May 7, 2014 at 2:03 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Ship it!
>
> On 2014-05-07, Daniel Bevenius wrote:
> > Sounds good.
> >
> >
> > On 7 May 2014 13:55, Matthias Wessendorf <matzew at apache.org> wrote:
> >
> > > Hi,
> > >
> > > since a few month we had not had a release of the sender. Mainly we got
> > > support for:
> > > * Proxy server configuration
> > > * AGPUSH-559 (HTTPS connection support)
> > > * AGPUSH-619 (fix on the mismatch of the TTL payload)
> > >
> > > However there are a few PRs open:
> > > https://github.com/aerogear/aerogear-unifiedpush-java-client/pulls
> > >
> > > I'd like to keep them open (as that does not hurt), and evaluate them
> > > _after_ this release.
> > > Especially our QE folks would appreciate a release, as well as the
> entire
> > > community.
> > >
> > > The open PRs will be evaluated right after that release.
> > >
> > > Any thoughts ?
> > >
> > > -Matthias
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> 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/20140507/c69f45cb/attachment.html 

From jbalunas at redhat.com  Wed May  7 10:34:18 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Wed, 7 May 2014 10:34:18 -0400
Subject: [aerogear-dev] Release of AeroGear Parent
In-Reply-To: <1399466903286-7702.post@n5.nabble.com>
References: <1399466903286-7702.post@n5.nabble.com>
Message-ID: <836C4F19-E313-4E1F-A7B2-3EE072BDCE1B@redhat.com>


On May 7, 2014, at 8:48 AM, Andrea Vibelli <avibelli at redhat.com> wrote:

> Hello, 
> I would like to know when the aerogear-parent will be possibly released.
> With the latest changes that define the AeroGear BOMs, once aerogear-parent
> is released all the AeroGear projects will have the possibility to consume
> those BOMs.

+1 It would be good to get the parent and BOM references updates in place.

Team - What are some of the updates, verification/testing that would be needed to get this released?

> 
> Thanks
> Andrea
> 
> 
> 
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-tp7702.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 May  7 10:38:36 2014
From: smikloso at redhat.com (Stefan Miklosovic)
Date: Wed, 7 May 2014 10:38:36 -0400 (EDT)
Subject: [aerogear-dev] pushplugin release
In-Reply-To: <C219CA5A-728D-48C6-8AE3-87C4ACF6C5E6@redhat.com>
References: <C219CA5A-728D-48C6-8AE3-87C4ACF6C5E6@redhat.com>
Message-ID: <855483380.1104948.1399473516486.JavaMail.zimbra@redhat.com>

Hi,

regarding of a release, I looked at it little bit closer and these are my findings.

I tried latest master with cordova plugin add https://github.com/aerogear/aerogear-pushplugin-cordova and 
I tried it on this demo (1)

1) What does not work

a) Android 2.3.3 emulator with Google API + mentioned demo, whole app crashes upon its start like (2)
b) Android 2.3.4 physical device (My Sony Ericsson with Android 2.3.4) - it shows this weird dialog (3)
c) Android 4.1.2 physical device (Samsung) - same as (3) however once it shows it and once not ... it is not deterministic

Regarding of (3), even I cancel it, it just freezes and does nothing.

2) What works by automatic test but not deterministically

Android 4.4.2 emulator + Google API 

This is little bit more complicated. Droidium can test in a such way that in case AVD of your emulator is not 
present on your machine, that AVD is automatically created in test execution itself and emulator is booted, 
APK is deployed there tests are carried out and emulator is dynamically deleted when test stops.

Even emulator is booted and APK is installed there and test proceeds, in the background Google GCM service seems 
to be not initialized in time we are sending a message so it is kind of not delivered. By debugging it step-by-step
it seems it has enough time to initialize itself.

However, the same issue with a message being not delivered has occured at fully prepared emulator as well.

3) What works manually

Android 4.4.2 emulator + Google API meaning without test but buy sending a message from web admin of (4)

Issues:

1) For testing purposes we have this UPS installation (4) and while I was coping with this testing manually, 
when I sent some message from UPS web admin, it appeared on emulator twice, so it was basically sent two times. Any explanation for this?

2) Sometime that message was not delivered to emulator at all, meaning even I send it from test it has not appeared on emulator. By accident 
this was resolved when I refreshed web admin in browser. I do not know if this is somehow related but why not ...

I used this test (5) which uses Arquillian Droidium. Test is pretty straightforward and if you know some Selenium you are already done.

(1) https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova
(2) http://pastebin.com/raw.php?i=CLrR07mH
(3) http://devio.us/~stewe/DSC_0164.JPG
(4) https://cordovaci-mobileqa.rhcloud.com
(5) https://github.com/smiklosovic/cordova-pushplugin-test-/blob/master/src/test/java/org/jboss/aerogear/push/plugin/cordova/AeroGearPushPluginCordovaTestCase.java

Stefan Miklosovic
Red Hat Brno - JBoss Mobile Platform

e-mail: smikloso at redhat.com
irc: smikloso

----- Original Message -----
> Hi,
> 
> I?ve announced it before, but didn?t came around to actually do it and we
> started discussing the version number. So end of the week I?ll release a new
> version of the aerogear-pushplugin-cordova (for real this time) with version
> 0.5.0 this will include the 64 bit support the new API and some small bug
> fixes.
> 
> Cheers,
> 	Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>


From bruno at abstractj.org  Wed May  7 10:38:50 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 7 May 2014 11:38:50 -0300
Subject: [aerogear-dev] Release of AeroGear Parent
In-Reply-To: <836C4F19-E313-4E1F-A7B2-3EE072BDCE1B@redhat.com>
References: <1399466903286-7702.post@n5.nabble.com>
	<836C4F19-E313-4E1F-A7B2-3EE072BDCE1B@redhat.com>
Message-ID: <20140507143850.GA38299@abstractj.org>

I can stage it for testing and release it late tomorrow.

On 2014-05-07, Jay Balunas wrote:
>
> On May 7, 2014, at 8:48 AM, Andrea Vibelli <avibelli at redhat.com> wrote:
>
> > Hello,
> > I would like to know when the aerogear-parent will be possibly released.
> > With the latest changes that define the AeroGear BOMs, once aerogear-parent
> > is released all the AeroGear projects will have the possibility to consume
> > those BOMs.
>
> +1 It would be good to get the parent and BOM references updates in place.
>
> Team - What are some of the updates, verification/testing that would be needed to get this released?
>
> >
> > Thanks
> > Andrea
> >
> >
> >
> > --
> > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-tp7702.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

--

abstractj

From bruno at abstractj.org  Wed May  7 10:52:53 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 7 May 2014 11:52:53 -0300
Subject: [aerogear-dev] Release of AeroGear Parent
In-Reply-To: <836C4F19-E313-4E1F-A7B2-3EE072BDCE1B@redhat.com>
References: <1399466903286-7702.post@n5.nabble.com>
	<836C4F19-E313-4E1F-A7B2-3EE072BDCE1B@redhat.com>
Message-ID: <20140507145253.GA40026@abstractj.org>

Before stage aerogear-parent, I want to know if someone will review/merge
this change https://github.com/aerogear/aerogear-misc/pull/2, to get it
in with the next release. I guess, this PR is important.

I'm planning to release under 0.2.0, instead of 0.1.1. Thoughts?

On 2014-05-07, Jay Balunas wrote:
>
> On May 7, 2014, at 8:48 AM, Andrea Vibelli <avibelli at redhat.com> wrote:
>
> > Hello,
> > I would like to know when the aerogear-parent will be possibly released.
> > With the latest changes that define the AeroGear BOMs, once aerogear-parent
> > is released all the AeroGear projects will have the possibility to consume
> > those BOMs.
>
> +1 It would be good to get the parent and BOM references updates in place.
>
> Team - What are some of the updates, verification/testing that would be needed to get this released?
>
> >
> > Thanks
> > Andrea
> >
> >
> >
> > --
> > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-tp7702.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

--

abstractj

From avibelli at redhat.com  Wed May  7 11:03:34 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Wed, 7 May 2014 08:03:34 -0700 (PDT)
Subject: [aerogear-dev] Release of AeroGear Parent
In-Reply-To: <20140507145253.GA40026@abstractj.org>
References: <1399466903286-7702.post@n5.nabble.com>
	<836C4F19-E313-4E1F-A7B2-3EE072BDCE1B@redhat.com>
	<20140507145253.GA40026@abstractj.org>
Message-ID: <1399475014414-7709.post@n5.nabble.com>

Yes, that PR should be merged before this one.
The final effect of the PR on aerogear-misc is to use version 2.9 of
maven-javadoc-plugin instead of 2.8.1, all the other changes are cleaning up
the code and removals of duplicated declared plugins.


Bruno Oliveira wrote
> Before stage aerogear-parent, I want to know if someone will review/merge
> this change https://github.com/aerogear/aerogear-misc/pull/2, to get it
> in with the next release. I guess, this PR is important.
> 
> I'm planning to release under 0.2.0, instead of 0.1.1. Thoughts?
> 
> On 2014-05-07, Jay Balunas wrote:
>>
>> On May 7, 2014, at 8:48 AM, Andrea Vibelli &lt;

> avibelli@

> &gt; wrote:
>>
>> > Hello,
>> > I would like to know when the aerogear-parent will be possibly
>> released.
>> > With the latest changes that define the AeroGear BOMs, once
>> aerogear-parent
>> > is released all the AeroGear projects will have the possibility to
>> consume
>> > those BOMs.
>>
>> +1 It would be good to get the parent and BOM references updates in
>> place.
>>
>> Team - What are some of the updates, verification/testing that would be
>> needed to get this released?
>>
>> >
>> > Thanks
>> > Andrea
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-tp7702.html
>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > 

> aerogear-dev at .jboss

>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> 

> aerogear-dev at .jboss

>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-tp7702p7709.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From bruno at abstractj.org  Wed May  7 11:14:11 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 7 May 2014 12:14:11 -0300
Subject: [aerogear-dev] Release of AeroGear Parent
In-Reply-To: <1399475014414-7709.post@n5.nabble.com>
References: <1399466903286-7702.post@n5.nabble.com>
	<836C4F19-E313-4E1F-A7B2-3EE072BDCE1B@redhat.com>
	<20140507145253.GA40026@abstractj.org>
	<1399475014414-7709.post@n5.nabble.com>
Message-ID: <20140507151411.GA41694@abstractj.org>

Thanks, Andrea.

Volunteers to review aerogear-misc?

On 2014-05-07, Andrea Vibelli wrote:
> Yes, that PR should be merged before this one.
> The final effect of the PR on aerogear-misc is to use version 2.9 of
> maven-javadoc-plugin instead of 2.8.1, all the other changes are cleaning up
> the code and removals of duplicated declared plugins.
>
>
> Bruno Oliveira wrote
> > Before stage aerogear-parent, I want to know if someone will review/merge
> > this change https://github.com/aerogear/aerogear-misc/pull/2, to get it
> > in with the next release. I guess, this PR is important.
> >
> > I'm planning to release under 0.2.0, instead of 0.1.1. Thoughts?
> >
> > On 2014-05-07, Jay Balunas wrote:
> >>
> >> On May 7, 2014, at 8:48 AM, Andrea Vibelli &lt;
>
> > avibelli@
>
> > &gt; wrote:
> >>
> >> > Hello,
> >> > I would like to know when the aerogear-parent will be possibly
> >> released.
> >> > With the latest changes that define the AeroGear BOMs, once
> >> aerogear-parent
> >> > is released all the AeroGear projects will have the possibility to
> >> consume
> >> > those BOMs.
> >>
> >> +1 It would be good to get the parent and BOM references updates in
> >> place.
> >>
> >> Team - What are some of the updates, verification/testing that would be
> >> needed to get this released?
> >>
> >> >
> >> > Thanks
> >> > Andrea
> >> >
> >> >
> >> >
> >> > --
> >> > View this message in context:
> >> http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-tp7702.html
> >> > Sent from the aerogear-dev mailing list archive at Nabble.com.
> >> > _______________________________________________
> >> > aerogear-dev mailing list
> >> >
>
> > aerogear-dev at .jboss
>
> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >>
>
> > aerogear-dev at .jboss
>
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> > --
> >
> > abstractj
> > _______________________________________________
> > aerogear-dev mailing list
>
> > aerogear-dev at .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-tp7702p7709.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

--

abstractj

From supittma at redhat.com  Wed May  7 10:40:30 2014
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 07 May 2014 10:40:30 -0400
Subject: [aerogear-dev] Release of AeroGear Parent
In-Reply-To: <836C4F19-E313-4E1F-A7B2-3EE072BDCE1B@redhat.com>
References: <1399466903286-7702.post@n5.nabble.com>
	<836C4F19-E313-4E1F-A7B2-3EE072BDCE1B@redhat.com>
Message-ID: <536A45DE.1090800@redhat.com>

On 05/07/2014 10:34 AM, Jay Balunas wrote:
> On May 7, 2014, at 8:48 AM, Andrea Vibelli <avibelli at redhat.com> wrote:
>
>> Hello,
>> I would like to know when the aerogear-parent will be possibly released.
>> With the latest changes that define the AeroGear BOMs, once aerogear-parent
>> is released all the AeroGear projects will have the possibility to consume
>> those BOMs.
> +1 It would be good to get the parent and BOM references updates in place.
>
> Team - What are some of the updates, verification/testing that would be needed to get this released?
We have to update the pom.  If Travis passes and the Cookbook apps work 
then we will just roll it into 1.4.0
>
>> Thanks
>> Andrea
>>
>>
>>
>> --
>> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-tp7702.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


-- 
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.


From avibelli at redhat.com  Wed May  7 11:26:18 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Wed, 7 May 2014 08:26:18 -0700 (PDT)
Subject: [aerogear-dev] pushplugin release
In-Reply-To: <855483380.1104948.1399473516486.JavaMail.zimbra@redhat.com>
References: <C219CA5A-728D-48C6-8AE3-87C4ACF6C5E6@redhat.com>
	<855483380.1104948.1399473516486.JavaMail.zimbra@redhat.com>
Message-ID: <1399476378602-7712.post@n5.nabble.com>

Hi, 
I have encountered issue a) of section 1) on a physical device running
Android 2.3.6.

My 2 cents:
I have encountered this type of error when UI Thread is being worked on from
inside a background thread (typically doInBackground() method inside an
AsyncTask), however I do not see any such situation inside doInBackground()
of AeroGearGCMPushRegistrar.register. I think UI is updated only inside
onPostExecute() here, will make some more investigations about his issue.


Stefan Miklosovic wrote
> Hi,
> 
> regarding of a release, I looked at it little bit closer and these are my
> findings.
> 
> I tried latest master with cordova plugin add
> https://github.com/aerogear/aerogear-pushplugin-cordova and 
> I tried it on this demo (1)
> 
> 1) What does not work
> 
> a) Android 2.3.3 emulator with Google API + mentioned demo, whole app
> crashes upon its start like (2)
> b) Android 2.3.4 physical device (My Sony Ericsson with Android 2.3.4) -
> it shows this weird dialog (3)
> c) Android 4.1.2 physical device (Samsung) - same as (3) however once it
> shows it and once not ... it is not deterministic
> 
> Regarding of (3), even I cancel it, it just freezes and does nothing.
> 
> 2) What works by automatic test but not deterministically
> 
> Android 4.4.2 emulator + Google API 
> 
> This is little bit more complicated. Droidium can test in a such way that
> in case AVD of your emulator is not 
> present on your machine, that AVD is automatically created in test
> execution itself and emulator is booted, 
> APK is deployed there tests are carried out and emulator is dynamically
> deleted when test stops.
> 
> Even emulator is booted and APK is installed there and test proceeds, in
> the background Google GCM service seems 
> to be not initialized in time we are sending a message so it is kind of
> not delivered. By debugging it step-by-step
> it seems it has enough time to initialize itself.
> 
> However, the same issue with a message being not delivered has occured at
> fully prepared emulator as well.
> 
> 3) What works manually
> 
> Android 4.4.2 emulator + Google API meaning without test but buy sending a
> message from web admin of (4)
> 
> Issues:
> 
> 1) For testing purposes we have this UPS installation (4) and while I was
> coping with this testing manually, 
> when I sent some message from UPS web admin, it appeared on emulator
> twice, so it was basically sent two times. Any explanation for this?
> 
> 2) Sometime that message was not delivered to emulator at all, meaning
> even I send it from test it has not appeared on emulator. By accident 
> this was resolved when I refreshed web admin in browser. I do not know if
> this is somehow related but why not ...
> 
> I used this test (5) which uses Arquillian Droidium. Test is pretty
> straightforward and if you know some Selenium you are already done.
> 
> (1)
> https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova
> (2) http://pastebin.com/raw.php?i=CLrR07mH
> (3) http://devio.us/~stewe/DSC_0164.JPG
> (4) https://cordovaci-mobileqa.rhcloud.com
> (5)
> https://github.com/smiklosovic/cordova-pushplugin-test-/blob/master/src/test/java/org/jboss/aerogear/push/plugin/cordova/AeroGearPushPluginCordovaTestCase.java
> 
> Stefan Miklosovic
> Red Hat Brno - JBoss Mobile Platform
> 
> e-mail: 

> smikloso@

> irc: smikloso
> 
> ----- Original Message -----
>> Hi,
>> 
>> I?ve announced it before, but didn?t came around to actually do it and we
>> started discussing the version number. So end of the week I?ll release a
>> new
>> version of the aerogear-pushplugin-cordova (for real this time) with
>> version
>> 0.5.0 this will include the 64 bit support the new API and some small bug
>> fixes.
>> 
>> Cheers,
>> 	Erik Jan
>> _______________________________________________
>> aerogear-dev mailing list
>> 

> aerogear-dev at .jboss

>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-pushplugin-release-tp7502p7712.html
Sent from the aerogear-dev mailing list archive at Nabble.com.


From edewit at redhat.com  Wed May  7 12:07:00 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 7 May 2014 18:07:00 +0200
Subject: [aerogear-dev] pushplugin release
In-Reply-To: <855483380.1104948.1399473516486.JavaMail.zimbra@redhat.com>
References: <C219CA5A-728D-48C6-8AE3-87C4ACF6C5E6@redhat.com>
	<855483380.1104948.1399473516486.JavaMail.zimbra@redhat.com>
Message-ID: <DB327944-98A7-493D-8A8B-EB51D987A278@redhat.com>

Hi,

On 7 May,2014, at 16:38 , Stefan Miklosovic <smikloso at redhat.com> wrote:

> Hi,
> 
> regarding of a release, I looked at it little bit closer and these are my findings.
> 
> I tried latest master with cordova plugin add https://github.com/aerogear/aerogear-pushplugin-cordova and 
> I tried it on this demo (1)
> 
> 1) What does not work
> 
> a) Android 2.3.3 emulator with Google API + mentioned demo, whole app crashes upon its start like (2)
> b) Android 2.3.4 physical device (My Sony Ericsson with Android 2.3.4) - it shows this weird dialog (3)

This could be because you are using the cordova.js that's not compatible with the platform you're running the application on. How did you build the the APK and how do you create the platform?

> c) Android 4.1.2 physical device (Samsung) - same as (3) however once it shows it and once not ... it is not deterministic
> 
> Regarding of (3), even I cancel it, it just freezes and does nothing.

this gap_poll is how the plugins communicate with the web view if that doesn?t work nothing will.

> 
> 2) What works by automatic test but not deterministically
> 
> Android 4.4.2 emulator + Google API 
> 
> This is little bit more complicated. Droidium can test in a such way that in case AVD of your emulator is not 
> present on your machine, that AVD is automatically created in test execution itself and emulator is booted, 
> APK is deployed there tests are carried out and emulator is dynamically deleted when test stops.
> 
> Even emulator is booted and APK is installed there and test proceeds, in the background Google GCM service seems 
> to be not initialized in time we are sending a message so it is kind of not delivered. By debugging it step-by-step
> it seems it has enough time to initialize itself.
> 
Well if the application has not registered itself then it will be impossible for it to receive messages. So the APK should be installed and started before the message will get send.

> However, the same issue with a message being not delivered has occured at fully prepared emulator as well.
> 
> 3) What works manually
> 
> Android 4.4.2 emulator + Google API meaning without test but buy sending a message from web admin of (4)
> 
> Issues:
> 
> 1) For testing purposes we have this UPS installation (4) and while I was coping with this testing manually, 
> when I sent some message from UPS web admin, it appeared on emulator twice, so it was basically sent two times. Any explanation for this?

It could be that you have the same device registered twice? Or two applications?

> 
> 2) Sometime that message was not delivered to emulator at all, meaning even I send it from test it has not appeared on emulator. By accident 
> this was resolved when I refreshed web admin in browser. I do not know if this is somehow related but why not ...
> 
> I used this test (5) which uses Arquillian Droidium. Test is pretty straightforward and if you know some Selenium you are already done.
> 
> (1) https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova
> (2) http://pastebin.com/raw.php?i=CLrR07mH
> (3) http://devio.us/~stewe/DSC_0164.JPG
> (4) https://cordovaci-mobileqa.rhcloud.com
> (5) https://github.com/smiklosovic/cordova-pushplugin-test-/blob/master/src/test/java/org/jboss/aerogear/push/plugin/cordova/AeroGearPushPluginCordovaTestCase.java
> 
> Stefan Miklosovic
> Red Hat Brno - JBoss Mobile Platform
> 
> e-mail: smikloso at redhat.com
> irc: smikloso
> 



From scm.blanc at gmail.com  Wed May  7 12:30:27 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 7 May 2014 18:30:27 +0200
Subject: [aerogear-dev] Java Sender 0.6.0 Release
Message-ID: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>

Hi folks,
The AeroGear UnifiedPush Java Client 0.6.0 has been staged :

https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172

This release contains the following changes :

* Proxy server configuration
* AGPUSH-559 (HTTPS connection support)
* AGPUSH-619 (fix on the mismatch of the TTL payload)

I plan to release to maven central on Friday, so please test and report any
issues !

Sebi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140507/3766589f/attachment.html 

From scm.blanc at gmail.com  Wed May  7 12:50:18 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 7 May 2014 18:50:18 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CAAg5f2RMHB019npB11wmGtpXMWZSHwHN=MnJKe8XZ+8oTexXgg@mail.gmail.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<CAAg5f2RMHB019npB11wmGtpXMWZSHwHN=MnJKe8XZ+8oTexXgg@mail.gmail.com>
Message-ID: <CAD_dpu3UYKcTEdyz5ugK1fojyPQjddEnM7W3FR8dh=HEhHj_GQ@mail.gmail.com>

On Wed, May 7, 2014 at 1:35 PM, Matthias Wessendorf <matzew at apache.org>wrote:

>
>
>
> On Wed, May 7, 2014 at 11:54 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>> Hi,
>>
>> as discussed , we need some sort of 'stats' around push, like:
>> * time of sending
>> * receivers (e.g. categories, alias ?)
>> * content/payload of the message
>> * could be sent out to APNs/GCM
>>
>>
>> But, where, or how to add this ?
>> My current thought is:
>>
>> When a user did select an "Application", he enters the "Application
>> Details Page" (see [1]), now here, on the sidebar (see [2]) he would see
>> the "Notifications" icon.
>>
>> Clicking on that  "Notifications" icon, would give you a new page, that
>> contains the "Send Notifications..." button (currently located in [1]), and
>> a table of all the push messages that were sent out for the _current_
>> selected Application.
>>
>
>
> Actually..... not sure... perhaps we keep the "Application Details Page"
> for just working w/ the App (e.g. renaming, updating certs/keys), and
> always have the "Notification icon" on the sidebar.
>
+1

>
> When you click on the icon, you have to select a Application, and after
> that, you see the new page, that contains the "Send Notifications..."
> button (currently located in [1]), and a table of all the push messages
> that were sent out for the _current_ selected Application.
>

Sounds good but just not sure to also migrate the "Send Notifications ..."
 feature there. On one side it makes sense to have it there but on the
other hand it's also nice to have a direct access to this feature when you
are on the application detail page. Other point : maybe when we will
introduce roles, some might not have the rights to check the stats but
still have the right to send a test message.

So, maybe we can duplicate the "Send Notifications ..." button and keeping
it also on the application detail page, wdyt ?




> any thoughts ?
>
>
> -Matthias
>
>
>>
>> Any thoughts ?
>>
>> -Matthias
>>
>> [1]
>> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>> [2]
>> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>>
>>
>> --
>> 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/20140507/8d8defe5/attachment.html 

From kpiwko at redhat.com  Wed May  7 13:41:15 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 7 May 2014 19:41:15 +0200
Subject: [aerogear-dev] pushplugin release
In-Reply-To: <855483380.1104948.1399473516486.JavaMail.zimbra@redhat.com>
References: <C219CA5A-728D-48C6-8AE3-87C4ACF6C5E6@redhat.com>
	<855483380.1104948.1399473516486.JavaMail.zimbra@redhat.com>
Message-ID: <20140507194115.0c77f72a@kapy-ntb-x220>

Hi Stefan,

few comments inline.

Karel

On Wed, 7 May 2014 10:38:36 -0400 (EDT)
Stefan Miklosovic <smikloso at redhat.com> wrote:

> Hi,
> 
> regarding of a release, I looked at it little bit closer and these are my
> findings.
> 
> I tried latest master with cordova plugin add
> https://github.com/aerogear/aerogear-pushplugin-cordova and I tried it on
> this demo (1)
> 
> 1) What does not work
> 
> a) Android 2.3.3 emulator with Google API + mentioned demo, whole app crashes
> upon its start like (2) b) Android 2.3.4 physical device (My Sony Ericsson
> with Android 2.3.4) - it shows this weird dialog (3) 

Is this error dialog present for both automated (Droidium) and manual (Cordova
CLI) deployments on real device? If not, it might be caused by Selendroid. Same
for c)

> c) Android 4.1.2
> physical device (Samsung) - same as (3) however once it shows it and once
> not ... it is not deterministic
> 
> Regarding of (3), even I cancel it, it just freezes and does nothing.
> 
> 2) What works by automatic test but not deterministically
> 
> Android 4.4.2 emulator + Google API 
> 
> This is little bit more complicated. Droidium can test in a such way that in
> case AVD of your emulator is not present on your machine, that AVD is
> automatically created in test execution itself and emulator is booted, APK is
> deployed there tests are carried out and emulator is dynamically deleted when
> test stops.
> 
> Even emulator is booted and APK is installed there and test proceeds, in the
> background Google GCM service seems to be not initialized in time we are
> sending a message so it is kind of not delivered. By debugging it
> step-by-step it seems it has enough time to initialize itself.

We need an element (with id) in app we can wait for to appear to signalize
registration was finished. Valid feature request for all android/ios/cordova
variants I believe.

> 
> However, the same issue with a message being not delivered has occured at
> fully prepared emulator as well.
> 

This makes sense to me as registration happen after app is installed and opened.

> 3) What works manually
> 
> Android 4.4.2 emulator + Google API meaning without test but buy sending a
> message from web admin of (4)
> 
> Issues:
> 
> 1) For testing purposes we have this UPS installation (4) and while I was
> coping with this testing manually, when I sent some message from UPS web
> admin, it appeared on emulator twice, so it was basically sent two times. Any
> explanation for this?
> 
> 2) Sometime that message was not delivered to emulator at all, meaning even I
> send it from test it has not appeared on emulator. By accident this was
> resolved when I refreshed web admin in browser. I do not know if this is
> somehow related but why not ...

Well, delivery is not guaranteed and can take some time. Might be just a
coincidence :-)

> 
> I used this test (5) which uses Arquillian Droidium. Test is pretty
> straightforward and if you know some Selenium you are already done.
> 
> (1) https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova
> (2) http://pastebin.com/raw.php?i=CLrR07mH
> (3) http://devio.us/~stewe/DSC_0164.JPG
> (4) https://cordovaci-mobileqa.rhcloud.com
> (5)
> https://github.com/smiklosovic/cordova-pushplugin-test-/blob/master/src/test/java/org/jboss/aerogear/push/plugin/cordova/AeroGearPushPluginCordovaTestCase.java
> 
> Stefan Miklosovic
> Red Hat Brno - JBoss Mobile Platform
> 
> e-mail: smikloso at redhat.com
> irc: smikloso
> 
> ----- Original Message -----
> > Hi,
> > 
> > I?ve announced it before, but didn?t came around to actually do it and we
> > started discussing the version number. So end of the week I?ll release a new
> > version of the aerogear-pushplugin-cordova (for real this time) with version
> > 0.5.0 this will include the 64 bit support the new API and some small bug
> > fixes.
> > 
> > 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


From kpiwko at redhat.com  Wed May  7 13:51:33 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 7 May 2014 19:51:33 +0200
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
Message-ID: <20140507195133.45062037@kapy-ntb-x220>

That's awesome, both fixed issues will help us!

However, I doubt there is somebody who could have a look from QE till Friday,
everybody is out slacking till Monday.

Karel

On Wed, 7 May 2014 18:30:27 +0200
Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi folks,
> The AeroGear UnifiedPush Java Client 0.6.0 has been staged :
> 
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
> 
> This release contains the following changes :
> 
> * Proxy server configuration
> * AGPUSH-559 (HTTPS connection support)
> * AGPUSH-619 (fix on the mismatch of the TTL payload)
> 
> I plan to release to maven central on Friday, so please test and report any
> issues !
> 
> Sebi


From kpiwko at redhat.com  Wed May  7 13:56:39 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 7 May 2014 19:56:39 +0200
Subject: [aerogear-dev] SimplePush Server 0.11.0
In-Reply-To: <CAFJm-3EOJGv-Vbq_5SWNVBreBOFqtiXf1hAX1rzz6hjWRbgodw@mail.gmail.com>
References: <CAFJm-3HA3NM3kswb9jfcFi1tfx3QKGkGZL_5tqcnx8gHhzuZuQ@mail.gmail.com>
	<20140429125827.0dfcaa6f@kapy-ntb-x220>
	<CAFJm-3EOJGv-Vbq_5SWNVBreBOFqtiXf1hAX1rzz6hjWRbgodw@mail.gmail.com>
Message-ID: <20140507195639.1e0105d1@kapy-ntb-x220>

Hi,

I had chance to test just Netty implementation with memory backed store.
I will be able to continue with Vert.x and AS/WF modules on Friday.

Karel


On Mon, 5 May 2014 16:31:08 +0200
Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> AeroGear SimplePush 0.11.0 has been staged:
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3144/
> 
> Let us know if you find any issues or require more time for testing. If
> nothing crops up we will release on Thursday.
> 
> 
> 
> 
> On 29 April 2014 12:58, Karel Piwko <kpiwko at redhat.com> wrote:
> 
> > Sounds good. Let me know when testing phase will be approaching.
> >
> > Karel
> >
> > On Wed, 23 Apr 2014 10:18:12 +0200
> > Daniel Bevenius <daniel.bevenius at gmail.com> wrote:
> >
> > > Hi all,
> > >
> > > just wanted to give a heads up that I've rescheduled the release of
> > > SimplePush 0.11.0 [1]. There are only two task remaining, but I'll be
> > > working on other things for a while which is the reason for there not
> > being
> > > more.
> > >
> > > The main task of interest I think is [2], which allows notifications to
> > be
> > > done without a version in the body of the HTTP request. This I believe
> > will
> > > simplify the admin ui and perhaps other areas. If you'd like to see an
> > > earlier release then let me know and I'll get it done. As of now though,
> > > I've set the release date to May 6.
> > >
> > > /Dan
> > >
> > >
> > > [1]
> > >
> > https://issues.jboss.org/browse/AGSMPLPUSH-16?filter=12321270&jql=project%20%3D%20AGSMPLPUSH%20AND%20fixVersion%20%3D%20%220.11.0%22%20AND%20status%20in%20(Open%2C%20%22Coding%20In%20Progress%22%2C%20Reopened%2C%20%22Pull%20Request%20Sent%22)
> > >
> > > [2] https://issues.jboss.org/browse/AGSMPLPUSH-54
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >


From daniel.bevenius at gmail.com  Wed May  7 14:28:04 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Wed, 7 May 2014 20:28:04 +0200
Subject: [aerogear-dev] SimplePush Server 0.11.0
In-Reply-To: <20140507195639.1e0105d1@kapy-ntb-x220>
References: <CAFJm-3HA3NM3kswb9jfcFi1tfx3QKGkGZL_5tqcnx8gHhzuZuQ@mail.gmail.com>
	<20140429125827.0dfcaa6f@kapy-ntb-x220>
	<CAFJm-3EOJGv-Vbq_5SWNVBreBOFqtiXf1hAX1rzz6hjWRbgodw@mail.gmail.com>
	<20140507195639.1e0105d1@kapy-ntb-x220>
Message-ID: <CAFJm-3Eig8tMK_xCf__ESgSgpsh5caNRPBBKy1ANSVrDx_ss7w@mail.gmail.com>

Awesome, thanks!

onsdagen den 7:e maj 2014 skrev Karel Piwko <kpiwko at redhat.com>:

> Hi,
>
> I had chance to test just Netty implementation with memory backed store.
> I will be able to continue with Vert.x and AS/WF modules on Friday.
>
> Karel
>
>
> On Mon, 5 May 2014 16:31:08 +0200
> Daniel Bevenius <daniel.bevenius at gmail.com <javascript:;>> wrote:
>
> > AeroGear SimplePush 0.11.0 has been staged:
> >
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3144/
> >
> > Let us know if you find any issues or require more time for testing. If
> > nothing crops up we will release on Thursday.
> >
> >
> >
> >
> > On 29 April 2014 12:58, Karel Piwko <kpiwko at redhat.com <javascript:;>>
> wrote:
> >
> > > Sounds good. Let me know when testing phase will be approaching.
> > >
> > > Karel
> > >
> > > On Wed, 23 Apr 2014 10:18:12 +0200
> > > Daniel Bevenius <daniel.bevenius at gmail.com <javascript:;>> wrote:
> > >
> > > > Hi all,
> > > >
> > > > just wanted to give a heads up that I've rescheduled the release of
> > > > SimplePush 0.11.0 [1]. There are only two task remaining, but I'll be
> > > > working on other things for a while which is the reason for there not
> > > being
> > > > more.
> > > >
> > > > The main task of interest I think is [2], which allows notifications
> to
> > > be
> > > > done without a version in the body of the HTTP request. This I
> believe
> > > will
> > > > simplify the admin ui and perhaps other areas. If you'd like to see
> an
> > > > earlier release then let me know and I'll get it done. As of now
> though,
> > > > I've set the release date to May 6.
> > > >
> > > > /Dan
> > > >
> > > >
> > > > [1]
> > > >
> > >
> https://issues.jboss.org/browse/AGSMPLPUSH-16?filter=12321270&jql=project%20%3D%20AGSMPLPUSH%20AND%20fixVersion%20%3D%20%220.11.0%22%20AND%20status%20in%20(Open%2C%20%22Coding%20In%20Progress%22%2C%20Reopened%2C%20%22Pull%20Request%20Sent%22)
> > > >
> > > > [2] https://issues.jboss.org/browse/AGSMPLPUSH-54
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org <javascript:;>
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <javascript:;>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140507/660be159/attachment.html 

From bruno at abstractj.org  Wed May  7 16:29:15 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 7 May 2014 17:29:15 -0300
Subject: [aerogear-dev] AeroGear parent 0.2.0 staged
Message-ID: <20140507202915.GA98810@abstractj.org>

Good morning my friends,

After banging my head against the wall with all the verbosity from
Maven I managed to stage AeroGear parent and AeroGear Misc.

Here comes the respective repositories:

- http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3180/
- http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3173/

What went wrong?

Maven is a beast an if you don't add the respective tags it can't be
released on Nexus(https://github.com/aerogear/aerogear-parent/commits/master).

Also, aerogear-misc requires Java 7 as the minimum JDK and
aerogear-parent requires Java 6. It sounds inconsistent to me, should we
change?

If you have any idea about how to improve the goddamn verbosity, I would
thank you for the whole eternity.

--

abstractj

From avibelli at redhat.com  Wed May  7 16:54:40 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Wed, 7 May 2014 13:54:40 -0700 (PDT)
Subject: [aerogear-dev] AeroGear parent 0.2.0 staged
In-Reply-To: <20140507202915.GA98810@abstractj.org>
References: <20140507202915.GA98810@abstractj.org>
Message-ID: <1399496079988-7721.post@n5.nabble.com>

Hi Bruno, 
I think I owe you a couple of hundreds of beers...

I did not include all the necessary tags that, before the decision of not
injecting aerogear-parent inside the BOMs, were directly inherited from the
parent. My fault.
And yes, I would keep the versions aligned, I would aerogear-misc require
Java 6 as the minimum JDK.

Thanks a lot.



Bruno Oliveira wrote
> Good morning my friends,
> 
> After banging my head against the wall with all the verbosity from
> Maven I managed to stage AeroGear parent and AeroGear Misc.
> 
> Here comes the respective repositories:
> 
> -
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3180/
> -
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3173/
> 
> What went wrong?
> 
> Maven is a beast an if you don't add the respective tags it can't be
> released on
> Nexus(https://github.com/aerogear/aerogear-parent/commits/master).
> 
> Also, aerogear-misc requires Java 7 as the minimum JDK and
> aerogear-parent requires Java 6. It sounds inconsistent to me, should we
> change?
> 
> If you have any idea about how to improve the goddamn verbosity, I would
> thank you for the whole eternity.
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-parent-0-2-0-staged-tp7720p7721.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From bruno at abstractj.org  Wed May  7 17:37:06 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 7 May 2014 18:37:06 -0300
Subject: [aerogear-dev] AeroGear parent 0.2.0 staged
In-Reply-To: <1399496079988-7721.post@n5.nabble.com>
References: <20140507202915.GA98810@abstractj.org>
	<1399496079988-7721.post@n5.nabble.com>
Message-ID: <20140507213706.GA12825@abstractj.org>

No problem Andrea, that happens. I've already aligned aerogear-misc with parent. Here
comes the new staging url for misc:

http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3182/

Let me know if something is wrong.

On 2014-05-07, Andrea Vibelli wrote:
> Hi Bruno,
> I think I owe you a couple of hundreds of beers...
>
> I did not include all the necessary tags that, before the decision of not
> injecting aerogear-parent inside the BOMs, were directly inherited from the
> parent. My fault.
> And yes, I would keep the versions aligned, I would aerogear-misc require
> Java 6 as the minimum JDK.
>
> Thanks a lot.
>
>
>
> Bruno Oliveira wrote
> > Good morning my friends,
> >
> > After banging my head against the wall with all the verbosity from
> > Maven I managed to stage AeroGear parent and AeroGear Misc.
> >
> > Here comes the respective repositories:
> >
> > -
> > http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3180/
> > -
> > http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3173/
> >
> > What went wrong?
> >
> > Maven is a beast an if you don't add the respective tags it can't be
> > released on
> > Nexus(https://github.com/aerogear/aerogear-parent/commits/master).
> >
> > Also, aerogear-misc requires Java 7 as the minimum JDK and
> > aerogear-parent requires Java 6. It sounds inconsistent to me, should we
> > change?
> >
> > If you have any idea about how to improve the goddamn verbosity, I would
> > thank you for the whole eternity.
> >
> > --
> >
> > abstractj
> > _______________________________________________
> > aerogear-dev mailing list
>
> > aerogear-dev at .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-parent-0-2-0-staged-tp7720p7721.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

--

abstractj

JBoss, a division of Red Hat

From mwessendorf at gmail.com  Thu May  8 02:25:48 2014
From: mwessendorf at gmail.com (Matthias Wessendorf)
Date: Thu, 8 May 2014 08:25:48 +0200
Subject: [aerogear-dev] paging installations new console
In-Reply-To: <9EA24B7B-B865-46AD-B450-B2910704132E@redhat.com>
References: <9EA24B7B-B865-46AD-B450-B2910704132E@redhat.com>
Message-ID: <CAAg5f2SskWVrPztUQ9BySs64bJxCshmiP76PkYAC6QEMP7wSVQ@mail.gmail.com>

On Wed, May 7, 2014 at 9:36 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi all,
>
> As we are working on implementing the new visual design for the console we
> ran into something. Right now when you fetch a PushApplication from the
> rest service everything is eager fetched including all variants for that
> application but also all installations for all these variants.
>


yes - that is odd, and should be changed; all of the eager things (I think
I added a TODO on these collections)


>
> Now in the old console these installations where only used to list the
> number of installations on the ?application details? page next to the
> variant, for the new console I?ve introduced a count ?call? to do the same
> so we no longer need this eager fetch.
>

cool!


>
> This count query is a bit hard as we have separated the association of the
> variants per type so in order to have a count of the number of
> installations we have to do x queries where ( x is the number of device
> types)
>
> Example:
>
> "select v.variantID, count(*) from PushApplication pa join pa.androidVariants v join v.installations i "
>                 + "where pushApplicationID = :pushApplicationID and i.enabled = true "
>                 + "group by v.variantID";
>
>
> This query will give the total number of installations for each variant,
> but only for android. So what I would like to suggest it to simplify the
> data model and only have a relation with variants instead of one per type
> this will also make the data model more extendable (when a new device type
> is introduced the data model doesn?t have to change). If grouping of these
> variants is needed clients will need to do it themselves.
>

that would still allow us to say "Android-free variant has 10000
installations; iPad variant has 5000 installations", right ?

-M



>
> WDYT
> 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/20140508/fb3115b9/attachment-0001.html 

From edewit at redhat.com  Thu May  8 03:19:34 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 8 May 2014 09:19:34 +0200
Subject: [aerogear-dev] paging installations new console
In-Reply-To: <CAAg5f2SskWVrPztUQ9BySs64bJxCshmiP76PkYAC6QEMP7wSVQ@mail.gmail.com>
References: <9EA24B7B-B865-46AD-B450-B2910704132E@redhat.com>
	<CAAg5f2SskWVrPztUQ9BySs64bJxCshmiP76PkYAC6QEMP7wSVQ@mail.gmail.com>
Message-ID: <F6064C42-F74A-43CC-9982-1902A1D38554@redhat.com>

Two in one:

On 8 May,2014, at 8:25 , Matthias Wessendorf <mwessendorf at gmail.com> wrote:

> 
> This query will give the total number of installations for each variant, but only for android. So what I would like to suggest it to simplify the data model and only have a relation with variants instead of one per type this will also make the data model more extendable (when a new device type is introduced the data model doesn?t have to change). If grouping of these variants is needed clients will need to do it themselves.
> 
> that would still allow us to say "Android-free variant has 10000 installations; iPad variant has 5000 installations", right ? 
> 

Right, but do it in one query instead of x and have a more flexible data model at the same time.

On 7 May,2014, Karel Piwko wrote:

> I think it is a good idea to simplify underlying model. Could we 
> additionally provide SQL views that groups only one variant and expose it
> via REST point? 

Right I would like to keep the REST endpoint the same as this is our interface. Don?t know if we should base the grouping on views as we should support multiple databases, and like you said don?t know if this can be done for H2, for now let?s keep it simple and just do a `group by` query?

 Cheers,
	Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140508/cce37ae8/attachment.html 

From mwessendorf at gmail.com  Thu May  8 05:52:06 2014
From: mwessendorf at gmail.com (Matthias Wessendorf)
Date: Thu, 8 May 2014 11:52:06 +0200
Subject: [aerogear-dev] UnifiedPush 0.10.3 - release coming soon (WAR and
	OpenShift)
Message-ID: <CAAg5f2RhVFCrGd90d+9i1+7g+YOvTK5xV8-k_otc3Jr+JOAf3Q@mail.gmail.com>

Hi,

in order to be consistent with the latest Cordova changes name, we did
apply them (and improved GCM exception handling) to the 0.10.x branch as
well. That's the only content of the release:
* Cordova registration snippets match the LATEST (0.5.x) plugin
* GCM exception handling improved

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/13


If you want to test it - it's simple! Just go ahead and use my fork of the
repo:

rhc app create --no-git <YOUR COOL APP NAME>
https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.5


Let me know the results of your testing;
If I hear nothing bad by Tuesday evening (give it a few more days due to
European holidays), the merges will happen on Wednesday


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/20140508/63c5fbcb/attachment.html 

From bruno at abstractj.org  Thu May  8 06:42:34 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 8 May 2014 07:42:34 -0300
Subject: [aerogear-dev] AeroGear parent 0.2.0 staged
In-Reply-To: <20140507213706.GA12825@abstractj.org>
References: <20140507202915.GA98810@abstractj.org>
	<1399496079988-7721.post@n5.nabble.com>
	<20140507213706.GA12825@abstractj.org>
Message-ID: <20140508104234.GA50228@abstractj.org>

I'm planning to release the artifacts below if I don't hear anything
at 2 p.m BRT.

So, if you want to try, let me know.

On 2014-05-07, Bruno Oliveira wrote:
> No problem Andrea, that happens. I've already aligned aerogear-misc with parent. Here
> comes the new staging url for misc:
>
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3182/
>
> Let me know if something is wrong.
>
> On 2014-05-07, Andrea Vibelli wrote:
> > Hi Bruno,
> > I think I owe you a couple of hundreds of beers...
> >
> > I did not include all the necessary tags that, before the decision of not
> > injecting aerogear-parent inside the BOMs, were directly inherited from the
> > parent. My fault.
> > And yes, I would keep the versions aligned, I would aerogear-misc require
> > Java 6 as the minimum JDK.
> >
> > Thanks a lot.
> >
> >
> >
> > Bruno Oliveira wrote
> > > Good morning my friends,
> > >
> > > After banging my head against the wall with all the verbosity from
> > > Maven I managed to stage AeroGear parent and AeroGear Misc.
> > >
> > > Here comes the respective repositories:
> > >
> > > -
> > > http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3180/
> > > -
> > > http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3173/
> > >
> > > What went wrong?
> > >
> > > Maven is a beast an if you don't add the respective tags it can't be
> > > released on
> > > Nexus(https://github.com/aerogear/aerogear-parent/commits/master).
> > >
> > > Also, aerogear-misc requires Java 7 as the minimum JDK and
> > > aerogear-parent requires Java 6. It sounds inconsistent to me, should we
> > > change?
> > >
> > > If you have any idea about how to improve the goddamn verbosity, I would
> > > thank you for the whole eternity.
> > >
> > > --
> > >
> > > abstractj
> > > _______________________________________________
> > > aerogear-dev mailing list
> >
> > > aerogear-dev at .jboss
> >
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> >
> >
> > --
> > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-parent-0-2-0-staged-tp7720p7721.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
>
> --
>
> abstractj
>
> JBoss, a division of Red Hat

--

abstractj

From avibelli at redhat.com  Thu May  8 07:55:09 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Thu, 8 May 2014 04:55:09 -0700 (PDT)
Subject: [aerogear-dev] AeroGear parent 0.2.0 staged
In-Reply-To: <20140508104234.GA50228@abstractj.org>
References: <20140507202915.GA98810@abstractj.org>
	<1399496079988-7721.post@n5.nabble.com>
	<20140507213706.GA12825@abstractj.org>
	<20140508104234.GA50228@abstractj.org>
Message-ID: <1399550109933-7727.post@n5.nabble.com>

Excellent for me, thanks!


Bruno Oliveira wrote
> I'm planning to release the artifacts below if I don't hear anything
> at 2 p.m BRT.
> 
> So, if you want to try, let me know.
> 
> On 2014-05-07, Bruno Oliveira wrote:
>> No problem Andrea, that happens. I've already aligned aerogear-misc with
>> parent. Here
>> comes the new staging url for misc:
>>
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3182/
>>
>> Let me know if something is wrong.
>>
>> On 2014-05-07, Andrea Vibelli wrote:
>> > Hi Bruno,
>> > I think I owe you a couple of hundreds of beers...
>> >
>> > I did not include all the necessary tags that, before the decision of
>> not
>> > injecting aerogear-parent inside the BOMs, were directly inherited from
>> the
>> > parent. My fault.
>> > And yes, I would keep the versions aligned, I would aerogear-misc
>> require
>> > Java 6 as the minimum JDK.
>> >
>> > Thanks a lot.
>> >
>> >
>> >
>> > Bruno Oliveira wrote
>> > > Good morning my friends,
>> > >
>> > > After banging my head against the wall with all the verbosity from
>> > > Maven I managed to stage AeroGear parent and AeroGear Misc.
>> > >
>> > > Here comes the respective repositories:
>> > >
>> > > -
>> > >
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3180/
>> > > -
>> > >
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3173/
>> > >
>> > > What went wrong?
>> > >
>> > > Maven is a beast an if you don't add the respective tags it can't be
>> > > released on
>> > > Nexus(https://github.com/aerogear/aerogear-parent/commits/master).
>> > >
>> > > Also, aerogear-misc requires Java 7 as the minimum JDK and
>> > > aerogear-parent requires Java 6. It sounds inconsistent to me, should
>> we
>> > > change?
>> > >
>> > > If you have any idea about how to improve the goddamn verbosity, I
>> would
>> > > thank you for the whole eternity.
>> > >
>> > > --
>> > >
>> > > abstractj
>> > > _______________________________________________
>> > > aerogear-dev mailing list
>> >
>> > > aerogear-dev at .jboss
>> >
>> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> >
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-parent-0-2-0-staged-tp7720p7721.html
>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > 

> aerogear-dev at .jboss

>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> --
>>
>> abstractj
>>
>> JBoss, a division of Red Hat
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-parent-0-2-0-staged-tp7720p7727.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From daniel at passos.me  Thu May  8 10:31:42 2014
From: daniel at passos.me (Daniel Passos)
Date: Thu, 8 May 2014 11:31:42 -0300
Subject: [aerogear-dev] Modularizing the Android Library
In-Reply-To: <20140306143829.65e1e4aa@kapy-ntb-x220>
References: <5317317F.1010209@redhat.com>
	<20140306143829.65e1e4aa@kapy-ntb-x220>
Message-ID: <CAKjsGbvnCKv6nvcfgaVLg805ZRQBjSHYm7qKtyrWTDjUkN+c2Q@mail.gmail.com>

Hi Folks,

Just to y'all know, that is what we are planning for android modules

aerogear-android-core (pipe, auth, autz)
aerogear-android-store
aerogear-android-push
aerogear-android-security|encrypt (keyservices)
aerogear-android-offline
aerogear-android-sync
aerogear-android-messaging

wdyt?

-- Passos


On Thu, Mar 6, 2014 at 10:38 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> 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 <supittma at redhat.com> 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?
> >
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140508/c69268e9/attachment.html 

From lholmqui at redhat.com  Thu May  8 10:34:29 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Thu, 8 May 2014 10:34:29 -0400
Subject: [aerogear-dev] EmpireJS - day 1
Message-ID: <D1CC331B-88E8-4AEA-B1C7-7F4AFB3D44FA@redhat.com>

Monday and Tuesday i had the pleasure of going to EmpireJS in NYC. It was my first "pure" Javascript conference( previous conf's were a mix of languages ).

Overall it was really cool. Some talks were better than others( as with most conferences ). The videos are also up for on youtube.

I'm going to break this up into 2 emails, one for Day 1 and the other for Day 2

Day 1

Sorting Algorithms in Javascript

by Jenn Schiffer of California Style Sheets Fame

youtube link: https://www.youtube.com/watch?v=uRyqlhjXYQI

This was actually a pretty cool talk. She went over the fact that ECMAScript doesn't actually have a stable sorting spec.

She went over 3 difference sorting algorithms,

Insertion Sort( stable, small amounts of data ),

Bubble Sort( never use this one ),

Merge Sort( fast and stable, for large data sets - DO NOT USE IN THE BROWSER )

and were to best use them.

https://www.youtube.com/watch?v=kPRA0W1kECg

awesome visualization of how sorts work

Anatomy of a Successful Module

by Trevor Landau - of isJS fame

youtube link: https://www.youtube.com/watch?v=BNnRpiHxESc

basically just an overview of how to get your module in the eyes and hands of the people( npm, node/javascript weekly, etc... ), nothing about actually creating a good module.

The Final Frontier

by Domenic Denicola

youtube link: https://www.youtube.com/watch?v=XzRBgj1AJYA

This was a cool talk, talking about how we need to start thinking about the future and need to "level up" the web.

he went into this like offline, and about the ServiceWorker spec that is being worked on by FF/Chrome

also talked about User Experience and the need for responsiveness and System integration

Also talk about the Developer Experience and how we need better base primitives( webcrypto, promises )

BeagleBone Black: The versatile JS underdog

by Kassandra Perch

youtube link: https://www.youtube.com/watch?v=OXWBaDsmvys

Another cool talk. The BeagleBone Black is hardware, similar to the rasberry pi but has node pre installed and you can ssh into( no need for a separate monitor ).

She talk about how she know nothing about electronics but can still do cool stuff with it. i believe the sdk is a wrapper on top of the johnny-five library

she had a cool demo, showing LED's. it inspired me to buy one after the talk.

Exploiting a Pocket Universe

by Drew Petersen

youtube link: https://www.youtube.com/watch?v=p1dINlm1W9M

basically talking about games and using web workers to offload some tasks to help with Frames Per Second

The Road to Web Components

by Tom Dale, i think he is one of the guys that wrote Angular

youtube link: https://www.youtube.com/watch?v=yLyyXHhSl8w

This was a cool talk. He was talking about Web Components and what they are and What they are not.

Basically web components give us the ability to create our own html tags, but shouldn't be used to place the whole application architecture, sort of what polymer might be trying to do.

They are useful because they can be resusable and isolated and could possible help us bridge eco-systems( angular/ember apps )

Went on to show Ember Components - how to use web components today

Backbone.Marionette and RequireJS

by Daniel Cousineau

youtube link: https://www.youtube.com/watch?v=4K4JKtAGPu4

The no build system build system

by Peter M?ller

youtube link: https://www.youtube.com/watch?v=N_gRlmmF4Rc

talking abouthttps://github.com/assetgraph/assetgraph

Front-end Style Guides and Greenfields

by Mark Wunsch

youtube link: https://www.youtube.com/watch?v=JQHAQ_ckrXk

these are my exact notes: "no fucking idea what this talk was suppose to be about"

Gadgets for Holistic Web Detection

by Eric Shepherd

youtube link: https://www.youtube.com/watch?v=VpqPpbw_gns

talking about the different ways of detections for web apps

resolution detection - bad performance

device detection - difficult across the different stacks

feature detection - sort of good, sort of not

but we need all 3

for resolution we should be designing for the smallest width

and designers should be adding breakpoints in the designs as well as providing templates for all the different sizes

also nesting of CSS is an anti-pattern

Lesser Known Debugging Techniques

by Amjad Masad

youtube link: https://www.youtube.com/watch?v=rcjUR4icvoQ

kind of a neat talk about the different tips and tricks of debugging JS.

showed a couple of non documented functions in chrome dev tools, like debug() and monitor()

also some cool debugging techniques to set break points in "getters" and "setters" of prototypes

introduced flo, http://facebook.github.io/fb-flo/ , an OSS tools from facebook

Code Memes

by David Byrd

youtube link: https://www.youtube.com/watch?v=ajo8ZKsdSLg

basically just talking about how we can write expressions in javascript different ways, and certain ways have become popular. And that you could create your own.

for example,

// Something like this

var name;
if( x ) {
    name = x
} else {
    name = "Bob"
}

// Is written like this

var name = x || "Bob";

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140508/f256e94b/attachment-0001.html 

From scm.blanc at gmail.com  Thu May  8 11:38:13 2014
From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=)
Date: Thu, 8 May 2014 17:38:13 +0200
Subject: [aerogear-dev] EmpireJS - day 1
In-Reply-To: <D1CC331B-88E8-4AEA-B1C7-7F4AFB3D44FA@redhat.com>
References: <D1CC331B-88E8-4AEA-B1C7-7F4AFB3D44FA@redhat.com>
Message-ID: <51FBAC20-8953-4464-B096-C5EA99DA29B9@gmail.com>



Envoy? de mon iPhone

> Le 8 mai 2014 ? 16:34, Lucas Holmquist <lholmqui at redhat.com> a ?crit :
> 
> Monday and Tuesday i had the pleasure of going to EmpireJS in NYC. It was my first "pure" Javascript conference( previous conf's were a mix of languages ).
> 
> Overall it was really cool. Some talks were better than others( as with most conferences ). The videos are also up for on youtube.
> 
> I'm going to break this up into 2 emails, one for Day 1 and the other for Day 2
> 
> Day 1
> Sorting Algorithms in Javascript
> by Jenn Schiffer of California Style Sheets Fame
> 
> youtube link: https://www.youtube.com/watch?v=uRyqlhjXYQI
> 
> This was actually a pretty cool talk. She went over the fact that ECMAScript doesn't actually have a stable sorting spec.
> 
> She went over 3 difference sorting algorithms,
> 
> Insertion Sort( stable, small amounts of data ),
> 
> Bubble Sort( never use this one ),
> 
> Merge Sort( fast and stable, for large data sets - DO NOT USE IN THE BROWSER )
> 
> and were to best use them.
> 
> https://www.youtube.com/watch?v=kPRA0W1kECg
> 
> awesome visualization of how sorts work
> 
> Anatomy of a Successful Module
> by Trevor Landau - of isJS fame
> 
> youtube link: https://www.youtube.com/watch?v=BNnRpiHxESc
> 
> basically just an overview of how to get your module in the eyes and hands of the people( npm, node/javascript weekly, etc... ), nothing about actually creating a good module.
> 
> The Final Frontier
> by Domenic Denicola
> 
> youtube link: https://www.youtube.com/watch?v=XzRBgj1AJYA
> 
> This was a cool talk, talking about how we need to start thinking about the future and need to "level up" the web.
> 
> he went into this like offline, and about the ServiceWorker spec that is being worked on by FF/Chrome
> 
I know that the Simple Push guys at mozilla are currently rewriting the client part to take benefit of the ServiceWorkers, sounds cool , especially for silent notifications !
> also talked about User Experience and the need for responsiveness and System integration
> 
> Also talk about the Developer Experience and how we need better base primitives( webcrypto, promises )
> 
> BeagleBone Black: The versatile JS underdog
> by Kassandra Perch
> 
> youtube link: https://www.youtube.com/watch?v=OXWBaDsmvys
> 
> Another cool talk. The BeagleBone Black is hardware, similar to the rasberry pi but has node pre installed and you can ssh into( no need for a separate monitor ).
> 
> She talk about how she know nothing about electronics but can still do cool stuff with it. i believe the sdk is a wrapper on top of the johnny-five library
> 
> she had a cool demo, showing LED's. it inspired me to buy one after the talk.
> 
> Exploiting a Pocket Universe
> by Drew Petersen
> 
> youtube link: https://www.youtube.com/watch?v=p1dINlm1W9M
> 
> basically talking about games and using web workers to offload some tasks to help with Frames Per Second
> 
> The Road to Web Components
> by Tom Dale, i think he is one of the guys that wrote Angular
> 
> youtube link: https://www.youtube.com/watch?v=yLyyXHhSl8w
> 
> This was a cool talk. He was talking about Web Components and what they are and What they are not.
> 
> Basically web components give us the ability to create our own html tags, but shouldn't be used to place the whole application architecture, sort of what polymer might be trying to do.
> 
> They are useful because they can be resusable and isolated and could possible help us bridge eco-systems( angular/ember apps )
> 
> Went on to show Ember Components - how to use web components today
> 
> Backbone.Marionette and RequireJS
> by Daniel Cousineau
> 
> youtube link: https://www.youtube.com/watch?v=4K4JKtAGPu4
> 
> The no build system build system
> by Peter M?ller
> 
> youtube link: https://www.youtube.com/watch?v=N_gRlmmF4Rc
> 
> talking abouthttps://github.com/assetgraph/assetgraph
> 
> Front-end Style Guides and Greenfields
> by Mark Wunsch
> 
> youtube link: https://www.youtube.com/watch?v=JQHAQ_ckrXk
> 
> these are my exact notes: "no fucking idea what this talk was suppose to be about"
> 
> Gadgets for Holistic Web Detection
> by Eric Shepherd
> 
> youtube link: https://www.youtube.com/watch?v=VpqPpbw_gns
> 
> talking about the different ways of detections for web apps
> 
> resolution detection - bad performance
> 
> device detection - difficult across the different stacks
> 
> feature detection - sort of good, sort of not
> 
> but we need all 3
> 
> for resolution we should be designing for the smallest width
> 
> and designers should be adding breakpoints in the designs as well as providing templates for all the different sizes
> 
> also nesting of CSS is an anti-pattern
> 
> Lesser Known Debugging Techniques
> by Amjad Masad
> 
> youtube link: https://www.youtube.com/watch?v=rcjUR4icvoQ
> 
> kind of a neat talk about the different tips and tricks of debugging JS.
> 
> showed a couple of non documented functions in chrome dev tools, like debug() and monitor()
> 
> also some cool debugging techniques to set break points in "getters" and "setters" of prototypes
> 
> introduced flo, http://facebook.github.io/fb-flo/ , an OSS tools from facebook
> 
> Code Memes
> by David Byrd
> 
> youtube link: https://www.youtube.com/watch?v=ajo8ZKsdSLg
> 
> basically just talking about how we can write expressions in javascript different ways, and certain ways have become popular. And that you could create your own.
> 
> for example,
> 
> // Something like this
> 
> var name;
> if( x ) {
>     name = x
> } else {
>     name = "Bob"
> }
> 
> // Is written like this
> 
> var name = x || "Bob";
> 
Thx for this very detailed write up !!
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140508/fcc18ffa/attachment-0001.html 

From bruno at abstractj.org  Thu May  8 11:55:13 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 8 May 2014 12:55:13 -0300
Subject: [aerogear-dev] AeroGear Parent and Misc released
Message-ID: <20140508155513.GA59708@abstractj.org>

Ahoy peeps, AeroGear parent and misc were release on Nexus. Now is just
the matter of wait for Maven Central synchronization.

--

abstractj

From jbalunas at redhat.com  Thu May  8 14:56:48 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Thu, 8 May 2014 14:56:48 -0400
Subject: [aerogear-dev] AeroGear Parent and Misc released
In-Reply-To: <20140508155513.GA59708@abstractj.org>
References: <20140508155513.GA59708@abstractj.org>
Message-ID: <7A729F93-DBDC-46AF-9F1B-B2CB0EF555DB@redhat.com>

Nice! 

On May 8, 2014, at 11:55 AM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Ahoy peeps, AeroGear parent and misc were release on Nexus. Now is just
> the matter of wait for Maven Central synchronization.
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From bruno at abstractj.org  Thu May  8 15:28:00 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 8 May 2014 16:28:00 -0300
Subject: [aerogear-dev] Modularizing the Android Library
In-Reply-To: <CAKjsGbvnCKv6nvcfgaVLg805ZRQBjSHYm7qKtyrWTDjUkN+c2Q@mail.gmail.com>
References: <5317317F.1010209@redhat.com>
	<20140306143829.65e1e4aa@kapy-ntb-x220>
	<CAKjsGbvnCKv6nvcfgaVLg805ZRQBjSHYm7qKtyrWTDjUkN+c2Q@mail.gmail.com>
Message-ID: <20140508192800.GB69433@abstractj.org>

Aloha,

My 2 cents here, IMO aerogear-android-security only. It includes all
the sec requirements like aerogear-crypto-java or authentication with
OAuth2.

aerogear-android-store is kinda of a dependency for Offline. So I'm not
sure if they must stay separated or be a single module.

On 2014-05-08, Daniel Passos wrote:
> Hi Folks,
>
> Just to y'all know, that is what we are planning for android modules
>
> aerogear-android-core (pipe, auth, autz)
> aerogear-android-store
> aerogear-android-push
> aerogear-android-security|encrypt (keyservices)
> aerogear-android-offline
> aerogear-android-sync
> aerogear-android-messaging
>
> wdyt?
>
> -- Passos
>
>
> On Thu, Mar 6, 2014 at 10:38 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>
> > 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 <supittma at redhat.com> 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?
> > >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From bruno at abstractj.org  Thu May  8 15:29:25 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 8 May 2014 16:29:25 -0300
Subject: [aerogear-dev] EmpireJS - day 1
In-Reply-To: <D1CC331B-88E8-4AEA-B1C7-7F4AFB3D44FA@redhat.com>
References: <D1CC331B-88E8-4AEA-B1C7-7F4AFB3D44FA@redhat.com>
Message-ID: <20140508192925.GC69433@abstractj.org>

Thanks for the write up Luke.

On 2014-05-08, Lucas Holmquist wrote:
> Monday and Tuesday i had the pleasure of going to EmpireJS in NYC. It was my first "pure" Javascript conference( previous conf's were a mix of languages ).
>
> Overall it was really cool. Some talks were better than others( as with most conferences ). The videos are also up for on youtube.
>
> I'm going to break this up into 2 emails, one for Day 1 and the other for Day 2
>
> Day 1
>
> Sorting Algorithms in Javascript
>
> by Jenn Schiffer of California Style Sheets Fame
>
> youtube link: https://www.youtube.com/watch?v=uRyqlhjXYQI
>
> This was actually a pretty cool talk. She went over the fact that ECMAScript doesn't actually have a stable sorting spec.
>
> She went over 3 difference sorting algorithms,
>
> Insertion Sort( stable, small amounts of data ),
>
> Bubble Sort( never use this one ),
>
> Merge Sort( fast and stable, for large data sets - DO NOT USE IN THE BROWSER )
>
> and were to best use them.
>
> https://www.youtube.com/watch?v=kPRA0W1kECg
>
> awesome visualization of how sorts work
>
> Anatomy of a Successful Module
>
> by Trevor Landau - of isJS fame
>
> youtube link: https://www.youtube.com/watch?v=BNnRpiHxESc
>
> basically just an overview of how to get your module in the eyes and hands of the people( npm, node/javascript weekly, etc... ), nothing about actually creating a good module.
>
> The Final Frontier
>
> by Domenic Denicola
>
> youtube link: https://www.youtube.com/watch?v=XzRBgj1AJYA
>
> This was a cool talk, talking about how we need to start thinking about the future and need to "level up" the web.
>
> he went into this like offline, and about the ServiceWorker spec that is being worked on by FF/Chrome
>
> also talked about User Experience and the need for responsiveness and System integration
>
> Also talk about the Developer Experience and how we need better base primitives( webcrypto, promises )
>
> BeagleBone Black: The versatile JS underdog
>
> by Kassandra Perch
>
> youtube link: https://www.youtube.com/watch?v=OXWBaDsmvys
>
> Another cool talk. The BeagleBone Black is hardware, similar to the rasberry pi but has node pre installed and you can ssh into( no need for a separate monitor ).
>
> She talk about how she know nothing about electronics but can still do cool stuff with it. i believe the sdk is a wrapper on top of the johnny-five library
>
> she had a cool demo, showing LED's. it inspired me to buy one after the talk.
>
> Exploiting a Pocket Universe
>
> by Drew Petersen
>
> youtube link: https://www.youtube.com/watch?v=p1dINlm1W9M
>
> basically talking about games and using web workers to offload some tasks to help with Frames Per Second
>
> The Road to Web Components
>
> by Tom Dale, i think he is one of the guys that wrote Angular
>
> youtube link: https://www.youtube.com/watch?v=yLyyXHhSl8w
>
> This was a cool talk. He was talking about Web Components and what they are and What they are not.
>
> Basically web components give us the ability to create our own html tags, but shouldn't be used to place the whole application architecture, sort of what polymer might be trying to do.
>
> They are useful because they can be resusable and isolated and could possible help us bridge eco-systems( angular/ember apps )
>
> Went on to show Ember Components - how to use web components today
>
> Backbone.Marionette and RequireJS
>
> by Daniel Cousineau
>
> youtube link: https://www.youtube.com/watch?v=4K4JKtAGPu4
>
> The no build system build system
>
> by Peter M?ller
>
> youtube link: https://www.youtube.com/watch?v=N_gRlmmF4Rc
>
> talking abouthttps://github.com/assetgraph/assetgraph
>
> Front-end Style Guides and Greenfields
>
> by Mark Wunsch
>
> youtube link: https://www.youtube.com/watch?v=JQHAQ_ckrXk
>
> these are my exact notes: "no fucking idea what this talk was suppose to be about"
>
> Gadgets for Holistic Web Detection
>
> by Eric Shepherd
>
> youtube link: https://www.youtube.com/watch?v=VpqPpbw_gns
>
> talking about the different ways of detections for web apps
>
> resolution detection - bad performance
>
> device detection - difficult across the different stacks
>
> feature detection - sort of good, sort of not
>
> but we need all 3
>
> for resolution we should be designing for the smallest width
>
> and designers should be adding breakpoints in the designs as well as providing templates for all the different sizes
>
> also nesting of CSS is an anti-pattern
>
> Lesser Known Debugging Techniques
>
> by Amjad Masad
>
> youtube link: https://www.youtube.com/watch?v=rcjUR4icvoQ
>
> kind of a neat talk about the different tips and tricks of debugging JS.
>
> showed a couple of non documented functions in chrome dev tools, like debug() and monitor()
>
> also some cool debugging techniques to set break points in "getters" and "setters" of prototypes
>
> introduced flo, http://facebook.github.io/fb-flo/ , an OSS tools from facebook
>
> Code Memes
>
> by David Byrd
>
> youtube link: https://www.youtube.com/watch?v=ajo8ZKsdSLg
>
> basically just talking about how we can write expressions in javascript different ways, and certain ways have become popular. And that you could create your own.
>
> for example,
>
> // Something like this
>
> var name;
> if( x ) {
>     name = x
> } else {
>     name = "Bob"
> }
>
> // Is written like this
>
> var name = x || "Bob";
>

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From daniel.bevenius at gmail.com  Fri May  9 00:30:05 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 9 May 2014 06:30:05 +0200
Subject: [aerogear-dev] EmpireJS - day 1
In-Reply-To: <20140508192925.GC69433@abstractj.org>
References: <D1CC331B-88E8-4AEA-B1C7-7F4AFB3D44FA@redhat.com>
	<20140508192925.GC69433@abstractj.org>
Message-ID: <CAFJm-3GFTg3EJUF-nh2rt+XEJ_R_BhZJAjkUBL9F=e+UP6Nr=A@mail.gmail.com>

+1 nice write up!

torsdagen den 8:e maj 2014 skrev Bruno Oliveira <bruno at abstractj.org>:

> Thanks for the write up Luke.
>
> On 2014-05-08, Lucas Holmquist wrote:
> > Monday and Tuesday i had the pleasure of going to EmpireJS in NYC. It
> was my first "pure" Javascript conference( previous conf's were a mix of
> languages ).
> >
> > Overall it was really cool. Some talks were better than others( as with
> most conferences ). The videos are also up for on youtube.
> >
> > I'm going to break this up into 2 emails, one for Day 1 and the other
> for Day 2
> >
> > Day 1
> >
> > Sorting Algorithms in Javascript
> >
> > by Jenn Schiffer of California Style Sheets Fame
> >
> > youtube link: Jenn Schiffer   Sorting Algorithms<https://www.youtube.com/watch?v=uRyqlhjXYQI>
> >
> > This was actually a pretty cool talk. She went over the fact that
> ECMAScript doesn't actually have a stable sorting spec.
> >
> > She went over 3 difference sorting algorithms,
> >
> > Insertion Sort( stable, small amounts of data ),
> >
> > Bubble Sort( never use this one ),
> >
> > Merge Sort( fast and stable, for large data sets - DO NOT USE IN THE
> BROWSER )
> >
> > and were to best use them.
> >
> > 15 Sorting Algorithms in 6 Minutes<https://www.youtube.com/watch?v=kPRA0W1kECg>
> >
> > awesome visualization of how sorts work
> >
> > Anatomy of a Successful Module
> >
> > by Trevor Landau - of isJS fame
> >
> > youtube link: Trevor Landau   Anatomy of a Successful Module<https://www.youtube.com/watch?v=BNnRpiHxESc>
> >
> > basically just an overview of how to get your module in the eyes and
> hands of the people( npm, node/javascript weekly, etc... ), nothing about
> actually creating a good module.
> >
> > The Final Frontier
> >
> > by Domenic Denicola
> >
> > youtube link: Domenic Denicola   The Final Frontier<https://www.youtube.com/watch?v=XzRBgj1AJYA>
> >
> > This was a cool talk, talking about how we need to start thinking about
> the future and need to "level up" the web.
> >
> > he went into this like offline, and about the ServiceWorker spec that is
> being worked on by FF/Chrome
> >
> > also talked about User Experience and the need for responsiveness and
> System integration
> >
> > Also talk about the Developer Experience and how we need better base
> primitives( webcrypto, promises )
> >
> > BeagleBone Black: The versatile JS underdog
> >
> > by Kassandra Perch
> >
> > youtube link: Kassandra Perch   The versatile JS underdog<https://www.youtube.com/watch?v=OXWBaDsmvys>
> >
> > Another cool talk. The BeagleBone Black is hardware, similar to the
> rasberry pi but has node pre installed and you can ssh into( no need for a
> separate monitor ).
> >
> > She talk about how she know nothing about electronics but can still do
> cool stuff with it. i believe the sdk is a wrapper on top of the
> johnny-five library
> >
> > she had a cool demo, showing LED's. it inspired me to buy one after the
> talk.
> >
> > Exploiting a Pocket Universe
> >
> > by Drew Petersen
> >
> > youtube link: Drew Petersen   Exploiting a Pocket Universe<https://www.youtube.com/watch?v=p1dINlm1W9M>
> >
> > basically talking about games and using web workers to offload some
> tasks to help with Frames Per Second
> >
> > The Road to Web Components
> >
> > by Tom Dale, i think he is one of the guys that wrote Angular
> >
> > youtube link: Tom Dale   The Road to Web Components<https://www.youtube.com/watch?v=yLyyXHhSl8w>
> >
> > This was a cool talk. He was talking about Web Components and what they
> are and What they are not.
> >
> > Basically web components give us the ability to create our own html
> tags, but shouldn't be used to place the whole application architecture,
> sort of what polymer might be trying to do.
> >
> > They are useful because they can be resusable and isolated and could
> possible help us bridge eco-systems( angular/ember apps )
> >
> > Went on to show Ember Components - how to use web components today
> >
> > Backbone.Marionette and RequireJS
> >
> > by Daniel Cousineau
> >
> > youtube link: Daniel Cousineau   Backbone Marionette and Require JS<https://www.youtube.com/watch?v=4K4JKtAGPu4>
> >
> > The no build system build system
> >
> > by Peter M?ller
> >
> > youtube link: Peter Mu?ller   The no build system build system<https://www.youtube.com/watch?v=N_gRlmmF4Rc>
> >
> > talking abouthttps://github.com/assetgraph/assetgraph
> >
> > Front-end Style Guides and Greenfields
> >
> > by Mark Wunsch
> >
> > youtube link: Mark Wunsch   Front end Style Guildes and Greenfields<https://www.youtube.com/watch?v=JQHAQ_ckrXk>
> >
> > these are my exact notes: "no fucking idea what this talk was suppose to
> be about"
> >
> > Gadgets for Holistic Web Detection
> >
> > by Eric Shepherd
> >
> > youtube link: Eric Shepherd   Gadgets for Hollistic Web Detection<https://www.youtube.com/watch?v=VpqPpbw_gns>
> >
> > talking about the different ways of detections for web apps
> >
> > resolution detection - bad performance
> >
> > device detection - difficult across the different stacks
> >
> > feature detection - sort of good, sort of not
> >
> > but we need all 3
> >
> > for resolution we should be designing for the smallest width
> >
> > and designers should be adding breakpoints in the designs as well as
> providing templates for all the different sizes
> >
> > also nesting of CSS is an anti-pattern
> >
> > Lesser Known Debugging Techniques
> >
> > by Amjad Masad
> >
> > youtube link: Amjad Masad   Lesser known Debugging Techniques<https://www.youtube.com/watch?v=rcjUR4icvoQ>
> >
> > kind of a neat talk about the different tips and tricks of debugging JS.
> >
> > showed a couple of non documented functions in chrome dev tools, like
> debug() and monitor()
> >
> > also some cool debugging techniques to set break points in "getters" and
> "setters" of prototypes
> >
> > introduced flo, http://facebook.github.io/fb-flo/ , an OSS tools from
> facebook
> >
> > Code Memes
> >
> > by David Byrd
> >
> > youtube link: David Byrd   Code Memes<https://www.youtube.com/watch?v=ajo8ZKsdSLg>
> >
> > basically just talking about how we can write expressions in javascript
> different ways, and certain ways have become popular. And that you could
> create your own.
> >
> > for example,
> >
> > // Something like this
> >
> > var name;
> > if( x ) {
> >     name = x
> > } else {
> >     name = "Bob"
> > }
> >
> > // Is written like this
> >
> > var name = x || "Bob";
> >
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org <javascript:;>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <javascript:;>
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140509/160e7d89/attachment-0001.html 

From corinnekrych at gmail.com  Fri May  9 02:17:14 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 9 May 2014 08:17:14 +0200
Subject: [aerogear-dev] EmpireJS - day 1
In-Reply-To: <CAFJm-3GFTg3EJUF-nh2rt+XEJ_R_BhZJAjkUBL9F=e+UP6Nr=A@mail.gmail.com>
References: <D1CC331B-88E8-4AEA-B1C7-7F4AFB3D44FA@redhat.com>
	<20140508192925.GC69433@abstractj.org>
	<CAFJm-3GFTg3EJUF-nh2rt+XEJ_R_BhZJAjkUBL9F=e+UP6Nr=A@mail.gmail.com>
Message-ID: <CC28D88F-C3C9-4607-AE2E-0013CF627D6E@gmail.com>

+1
Good content for a blog post ;)
On 09 May 2014, at 06:30, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> +1 nice write up!
> 
> torsdagen den 8:e maj 2014 skrev Bruno Oliveira <bruno at abstractj.org>:
> Thanks for the write up Luke.
> 
> On 2014-05-08, Lucas Holmquist wrote:
> > Monday and Tuesday i had the pleasure of going to EmpireJS in NYC. It was my first "pure" Javascript conference( previous conf's were a mix of languages ).
> >
> > Overall it was really cool. Some talks were better than others( as with most conferences ). The videos are also up for on youtube.
> >
> > I'm going to break this up into 2 emails, one for Day 1 and the other for Day 2
> >
> > Day 1
> >
> > Sorting Algorithms in Javascript
> >
> > by Jenn Schiffer of California Style Sheets Fame
> >
> > youtube link: Jenn Schiffer   Sorting Algorithms
> >
> > This was actually a pretty cool talk. She went over the fact that ECMAScript doesn't actually have a stable sorting spec.
> >
> > She went over 3 difference sorting algorithms,
> >
> > Insertion Sort( stable, small amounts of data ),
> >
> > Bubble Sort( never use this one ),
> >
> > Merge Sort( fast and stable, for large data sets - DO NOT USE IN THE BROWSER )
> >
> > and were to best use them.
> >
> > 15 Sorting Algorithms in 6 Minutes
> >
> > awesome visualization of how sorts work
> >
> > Anatomy of a Successful Module
> >
> > by Trevor Landau - of isJS fame
> >
> > youtube link: Trevor Landau   Anatomy of a Successful Module
> >
> > basically just an overview of how to get your module in the eyes and hands of the people( npm, node/javascript weekly, etc... ), nothing about actually creating a good module.
> >
> > The Final Frontier
> >
> > by Domenic Denicola
> >
> > youtube link: Domenic Denicola   The Final Frontier
> >
> > This was a cool talk, talking about how we need to start thinking about the future and need to "level up" the web.
> >
> > he went into this like offline, and about the ServiceWorker spec that is being worked on by FF/Chrome
> >
> > also talked about User Experience and the need for responsiveness and System integration
> >
> > Also talk about the Developer Experience and how we need better base primitives( webcrypto, promises )
> >
> > BeagleBone Black: The versatile JS underdog
> >
> > by Kassandra Perch
> >
> > youtube link: Kassandra Perch   The versatile JS underdog
> >
> > Another cool talk. The BeagleBone Black is hardware, similar to the rasberry pi but has node pre installed and you can ssh into( no need for a separate monitor ).
> >
> > She talk about how she know nothing about electronics but can still do cool stuff with it. i believe the sdk is a wrapper on top of the johnny-five library
> >
> > she had a cool demo, showing LED's. it inspired me to buy one after the talk.
> >
> > Exploiting a Pocket Universe
> >
> > by Drew Petersen
> >
> > youtube link: Drew Petersen   Exploiting a Pocket Universe
> >
> > basically talking about games and using web workers to offload some tasks to help with Frames Per Second
> >
> > The Road to Web Components
> >
> > by Tom Dale, i think he is one of the guys that wrote Angular
> >
> > youtube link: Tom Dale   The Road to Web Components
> >
> > This was a cool talk. He was talking about Web Components and what they are and What they are not.
> >
> > Basically web components give us the ability to create our own html tags, but shouldn't be used to place the whole application architecture, sort of what polymer might be trying to do.
> >
> > They are useful because they can be resusable and isolated and could possible help us bridge eco-systems( angular/ember apps )
> >
> > Went on to show Ember Components - how to use web components today
> >
> > Backbone.Marionette and RequireJS
> >
> > by Daniel Cousineau
> >
> > youtube link: Daniel Cousineau   Backbone Marionette and Require JS
> >
> > The no build system build system
> >
> > by Peter M?ller
> >
> > youtube link: Peter M?ller   The no build system build system
> >
> > talking abouthttps://github.com/assetgraph/assetgraph
> >
> > Front-end Style Guides and Greenfields
> >
> > by Mark Wunsch
> >
> > youtube link: Mark Wunsch   Front end Style Guildes and Greenfields
> >
> > these are my exact notes: "no fucking idea what this talk was suppose to be about"
> >
> > Gadgets for Holistic Web Detection
> >
> > by Eric Shepherd
> >
> > youtube link: Eric Shepherd   Gadgets for Hollistic Web Detection
> >
> > talking about the different ways of detections for web apps
> >
> > resolution detection - bad performance
> >
> > device detection - difficult across the different stacks
> >
> > feature detection - sort of good, sort of not
> >
> > but we need all 3
> >
> > for resolution we should be designing for the smallest width
> >
> > and designers should be adding breakpoints in the designs as well as providing templates for all the different sizes
> >
> > also nesting of CSS is an anti-pattern
> >
> > Lesser Known Debugging Techniques
> >
> > by Amjad Masad
> >
> > youtube link: Amjad Masad   Lesser known Debugging Techniques
> >
> > kind of a neat talk about the different tips and tricks of debugging JS.
> >
> > showed a couple of non documented functions in chrome dev tools, like debug() and monitor()
> >
> > also some cool debugging techniques to set break points in "getters" and "setters" of prototypes
> >
> > introduced flo, http://facebook.github.io/fb-flo/ , an OSS tools from facebook
> >
> > Code Memes
> >
> > by David Byrd
> >
> > youtube link: David Byrd   Code Memes
> >
> > basically just talking about how we can write expressions in javascript different ways, and certain ways have become popular. And that you could create your own.
> >
> > for example,
> >
> > // Something like this
> >
> > var name;
> > if( x ) {
> >     name = x
> > } else {
> >     name = "Bob"
> > }
> >
> > // Is written like this
> >
> > var name = x || "Bob";
> >
> 
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> --
> 
> 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 cvasilak at gmail.com  Fri May  9 02:37:46 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Fri, 9 May 2014 09:37:46 +0300
Subject: [aerogear-dev] EmpireJS - day 1
In-Reply-To: <D1CC331B-88E8-4AEA-B1C7-7F4AFB3D44FA@redhat.com>
References: <D1CC331B-88E8-4AEA-B1C7-7F4AFB3D44FA@redhat.com>
Message-ID: <BCAF5500-F80E-4171-B691-C72962DB21C9@gmail.com>

+1 nice write up Luke

On May 8, 2014, at 5:34 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:

> Monday and Tuesday i had the pleasure of going to EmpireJS in NYC. It was my first "pure" Javascript conference( previous conf's were a mix of languages ).
> 
> Overall it was really cool. Some talks were better than others( as with most conferences ). The videos are also up for on youtube.
> 
> I'm going to break this up into 2 emails, one for Day 1 and the other for Day 2
> 
> Day 1
> 
> Sorting Algorithms in Javascript
> 
> by Jenn Schiffer of California Style Sheets Fame
> 
> youtube link: https://www.youtube.com/watch?v=uRyqlhjXYQI
> 
> This was actually a pretty cool talk. She went over the fact that ECMAScript doesn't actually have a stable sorting spec.
> 
> She went over 3 difference sorting algorithms,
> 
> Insertion Sort( stable, small amounts of data ),
> 
> Bubble Sort( never use this one ),
> 
> Merge Sort( fast and stable, for large data sets - DO NOT USE IN THE BROWSER )
> 
> and were to best use them.
> 
> https://www.youtube.com/watch?v=kPRA0W1kECg
> 
> awesome visualization of how sorts work
> 
> Anatomy of a Successful Module
> 
> by Trevor Landau - of isJS fame
> 
> youtube link: https://www.youtube.com/watch?v=BNnRpiHxESc
> 
> basically just an overview of how to get your module in the eyes and hands of the people( npm, node/javascript weekly, etc... ), nothing about actually creating a good module.
> 
> The Final Frontier
> 
> by Domenic Denicola
> 
> youtube link: https://www.youtube.com/watch?v=XzRBgj1AJYA
> 
> This was a cool talk, talking about how we need to start thinking about the future and need to "level up" the web.
> 
> he went into this like offline, and about the ServiceWorker spec that is being worked on by FF/Chrome
> 
> also talked about User Experience and the need for responsiveness and System integration
> 
> Also talk about the Developer Experience and how we need better base primitives( webcrypto, promises )
> 
> BeagleBone Black: The versatile JS underdog
> 
> by Kassandra Perch
> 
> youtube link: https://www.youtube.com/watch?v=OXWBaDsmvys
> 
> Another cool talk. The BeagleBone Black is hardware, similar to the rasberry pi but has node pre installed and you can ssh into( no need for a separate monitor ).
> 
> She talk about how she know nothing about electronics but can still do cool stuff with it. i believe the sdk is a wrapper on top of the johnny-five library
> 
> she had a cool demo, showing LED's. it inspired me to buy one after the talk.
> 
> Exploiting a Pocket Universe
> 
> by Drew Petersen
> 
> youtube link: https://www.youtube.com/watch?v=p1dINlm1W9M
> 
> basically talking about games and using web workers to offload some tasks to help with Frames Per Second
> 
> The Road to Web Components
> 
> by Tom Dale, i think he is one of the guys that wrote Angular
> 
> youtube link: https://www.youtube.com/watch?v=yLyyXHhSl8w
> 
> This was a cool talk. He was talking about Web Components and what they are and What they are not.
> 
> Basically web components give us the ability to create our own html tags, but shouldn't be used to place the whole application architecture, sort of what polymer might be trying to do.
> 
> They are useful because they can be resusable and isolated and could possible help us bridge eco-systems( angular/ember apps )
> 
> Went on to show Ember Components - how to use web components today
> 
> Backbone.Marionette and RequireJS
> 
> by Daniel Cousineau
> 
> youtube link: https://www.youtube.com/watch?v=4K4JKtAGPu4
> 
> The no build system build system
> 
> by Peter M?ller
> 
> youtube link: https://www.youtube.com/watch?v=N_gRlmmF4Rc
> 
> talking abouthttps://github.com/assetgraph/assetgraph
> 
> Front-end Style Guides and Greenfields
> 
> by Mark Wunsch
> 
> youtube link: https://www.youtube.com/watch?v=JQHAQ_ckrXk
> 
> these are my exact notes: "no fucking idea what this talk was suppose to be about"
> 
> Gadgets for Holistic Web Detection
> 
> by Eric Shepherd
> 
> youtube link: https://www.youtube.com/watch?v=VpqPpbw_gns
> 
> talking about the different ways of detections for web apps
> 
> resolution detection - bad performance
> 
> device detection - difficult across the different stacks
> 
> feature detection - sort of good, sort of not
> 
> but we need all 3
> 
> for resolution we should be designing for the smallest width
> 
> and designers should be adding breakpoints in the designs as well as providing templates for all the different sizes
> 
> also nesting of CSS is an anti-pattern
> 
> Lesser Known Debugging Techniques
> 
> by Amjad Masad
> 
> youtube link: https://www.youtube.com/watch?v=rcjUR4icvoQ
> 
> kind of a neat talk about the different tips and tricks of debugging JS.
> 
> showed a couple of non documented functions in chrome dev tools, like debug() and monitor()
> 
> also some cool debugging techniques to set break points in "getters" and "setters" of prototypes
> 
> introduced flo, http://facebook.github.io/fb-flo/ , an OSS tools from facebook
> 
> Code Memes
> 
> by David Byrd
> 
> youtube link: https://www.youtube.com/watch?v=ajo8ZKsdSLg
> 
> basically just talking about how we can write expressions in javascript different ways, and certain ways have become popular. And that you could create your own.
> 
> for example,
> 
> // Something like this
> 
> var name;
> if( x ) {
>     name = x
> } else {
>     name = "Bob"
> }
> 
> // Is written like this
> 
> var name = x || "Bob";
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140509/86580a1a/attachment-0001.html 

From corinnekrych at gmail.com  Fri May  9 02:52:16 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 9 May 2014 08:52:16 +0200
Subject: [aerogear-dev] Modularizing the Android Library
In-Reply-To: <20140508192800.GB69433@abstractj.org>
References: <5317317F.1010209@redhat.com>
	<20140306143829.65e1e4aa@kapy-ntb-x220>
	<CAKjsGbvnCKv6nvcfgaVLg805ZRQBjSHYm7qKtyrWTDjUkN+c2Q@mail.gmail.com>
	<20140508192800.GB69433@abstractj.org>
Message-ID: <A63879F1-E093-4CDF-BC2B-A55F7B3C6CAB@gmail.com>

Hi Passos,

Actually this library sepration is not just an android concern. We need modularity for iOS too. It something we?ve been talking about too in or last iOS meeting [1]. I have created an epic JIRA [2] to track iOS modularity. Once we agreed on library content, we create more sub-tasks.
Here is what I was thinking (here i leave android but same for iOS):

aerogear-android-pipe
aerogear-android-secure-pipe (auth, autz) dependant on aerogear-android-pipe
aerogear-android-store
aerogear-android-push-registration (one of the repo need renaming, for ios we have registration at the end)
aerogear-android-secure-store (keyservices) dependant on aerogear-android-store
aerogear-android-offline dependant on aerogear-android-store
aerogear-android-sync dependant on aerogear-android-pipe (?) and/or aerogear-android-offline
aerogear-ios-crypto

@abstractj I?d keep auth/authz and encryption separate as it has different dependancy one on pipe and another on store. Having small modules gives the user more choice. An app might want auth without encryption for ex.
@passos what is messaging for?

++
Corinne
[1] http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-04-08-11.46.txt
[2] https://issues.jboss.org/browse/AGIOS-192

On 08 May 2014, at 21:28, Bruno Oliveira <bruno at abstractj.org> wrote:

> Aloha,
> 
> My 2 cents here, IMO aerogear-android-security only. It includes all
> the sec requirements like aerogear-crypto-java or authentication with
> OAuth2.
> 
> aerogear-android-store is kinda of a dependency for Offline. So I'm not
> sure if they must stay separated or be a single module.
> 
> On 2014-05-08, Daniel Passos wrote:
>> Hi Folks,
>> 
>> Just to y'all know, that is what we are planning for android modules
>> 
>> aerogear-android-core (pipe, auth, autz)
>> aerogear-android-store
>> aerogear-android-push
>> aerogear-android-security|encrypt (keyservices)
>> aerogear-android-offline
>> aerogear-android-sync
>> aerogear-android-messaging
>> 
>> wdyt?
>> 
>> -- Passos
>> 
>> 
>> On Thu, Mar 6, 2014 at 10:38 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>> 
>>> 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 <supittma at redhat.com> 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?
>>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From corinnekrych at gmail.com  Fri May  9 02:55:21 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 9 May 2014 08:55:21 +0200
Subject: [aerogear-dev] Modularizing the Android Library
In-Reply-To: <A63879F1-E093-4CDF-BC2B-A55F7B3C6CAB@gmail.com>
References: <5317317F.1010209@redhat.com>
	<20140306143829.65e1e4aa@kapy-ntb-x220>
	<CAKjsGbvnCKv6nvcfgaVLg805ZRQBjSHYm7qKtyrWTDjUkN+c2Q@mail.gmail.com>
	<20140508192800.GB69433@abstractj.org>
	<A63879F1-E093-4CDF-BC2B-A55F7B3C6CAB@gmail.com>
Message-ID: <4CD71A7A-EDE1-4648-AB3E-E4DDB383D824@gmail.com>

Oops
[2] https://issues.jboss.org/browse/AGIOS-187
 
On 09 May 2014, at 08:52, Corinne Krych <corinnekrych at gmail.com> wrote:

> [2] https://issues.jboss.org/browse/AGIOS-192


From avibelli at redhat.com  Fri May  9 03:29:03 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Fri, 9 May 2014 00:29:03 -0700 (PDT)
Subject: [aerogear-dev] AeroGear Parent and Misc released
In-Reply-To: <7A729F93-DBDC-46AF-9F1B-B2CB0EF555DB@redhat.com>
References: <20140508155513.GA59708@abstractj.org>
	<7A729F93-DBDC-46AF-9F1B-B2CB0EF555DB@redhat.com>
Message-ID: <1399620543385-7740.post@n5.nabble.com>

AeroGear parent and misc are available on Maven Central, however I see a
weirdness: aerogear-misc has a new 0.2.0 version on Central, but it should
have a 0.1.2 version (that corresponds to the tag it has upstream).
We should align Maven Central and upstream.


Jay Balunas wrote
> Nice! 
> 
> On May 8, 2014, at 11:55 AM, Bruno Oliveira &lt;

> bruno@

> &gt; wrote:
> 
>> Ahoy peeps, AeroGear parent and misc were release on Nexus. Now is just
>> the matter of wait for Maven Central synchronization.
>> 
>> --
>> 
>> abstractj
>> _______________________________________________
>> aerogear-dev mailing list
>> 

> aerogear-dev at .jboss

>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Parent-and-Misc-released-tp7731p7740.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From mwessendorf at gmail.com  Fri May  9 06:21:15 2014
From: mwessendorf at gmail.com (Matthias Wessendorf)
Date: Fri, 9 May 2014 12:21:15 +0200
Subject: [aerogear-dev] [aerogear-misc] release issue
Message-ID: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>

Hi,

Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
number (0.2.0).
This artifact was already pushed to maven central.

On IRC we had the following idea:
* update master to 0.1.2-SNAPSHOT
* perform the release again (that hopefully will result in 0.1.2 on maven
central)

That still means we have a 0.2.0 on maven central. I will ask my contacts
at Sonatype to remove the 0.2.0 bits;

If folks are OK w/ that, I am happy to perform these steps by Monday morning

Greetings,
Matthias

[1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140509/a98d4da5/attachment.html 

From avibelli at redhat.com  Fri May  9 06:30:35 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Fri, 9 May 2014 03:30:35 -0700 (PDT)
Subject: [aerogear-dev] [aerogear-misc] release issue
In-Reply-To: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
References: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
Message-ID: <1399631435255-7742.post@n5.nabble.com>

That is fine from my point of view.
This means that:
1) aerogear-parent 0.2.0 is broken until aerogear-misc 0.1.2 is released on
Central (it uses 0.1.2)
2) after aerogear-misc 0.2.0 is eventually removed from Central, we could
remove also the corresponding tag 0.2.0 from upstream repo

Thanks
Andrea


Matthias Wessendorf-2 wrote
> Hi,
> 
> Andrea reported that the 0.1.2 release (see [1]) contains the wrong
> version
> number (0.2.0).
> This artifact was already pushed to maven central.
> 
> On IRC we had the following idea:
> * update master to 0.1.2-SNAPSHOT
> * perform the release again (that hopefully will result in 0.1.2 on maven
> central)
> 
> That still means we have a 0.2.0 on maven central. I will ask my contacts
> at Sonatype to remove the 0.2.0 bits;
> 
> If folks are OK w/ that, I am happy to perform these steps by Monday
> morning
> 
> Greetings,
> Matthias
> 
> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-misc-release-issue-tp7741p7742.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From daniel.bevenius at gmail.com  Fri May  9 07:05:15 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 9 May 2014 13:05:15 +0200
Subject: [aerogear-dev] [aerogear-misc] release issue
In-Reply-To: <1399631435255-7742.post@n5.nabble.com>
References: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
	<1399631435255-7742.post@n5.nabble.com>
Message-ID: <CAFJm-3FqLhvDjhbJy2-vnC54sYxZOAqsc0xjx-D7cDVbpdtHxw@mail.gmail.com>

I think that sounds reasonable.


On 9 May 2014 12:30, Andrea Vibelli <avibelli at redhat.com> wrote:

> That is fine from my point of view.
> This means that:
> 1) aerogear-parent 0.2.0 is broken until aerogear-misc 0.1.2 is released on
> Central (it uses 0.1.2)
> 2) after aerogear-misc 0.2.0 is eventually removed from Central, we could
> remove also the corresponding tag 0.2.0 from upstream repo
>
> Thanks
> Andrea
>
>
> Matthias Wessendorf-2 wrote
> > Hi,
> >
> > Andrea reported that the 0.1.2 release (see [1]) contains the wrong
> > version
> > number (0.2.0).
> > This artifact was already pushed to maven central.
> >
> > On IRC we had the following idea:
> > * update master to 0.1.2-SNAPSHOT
> > * perform the release again (that hopefully will result in 0.1.2 on maven
> > central)
> >
> > That still means we have a 0.2.0 on maven central. I will ask my contacts
> > at Sonatype to remove the 0.2.0 bits;
> >
> > If folks are OK w/ that, I am happy to perform these steps by Monday
> > morning
> >
> > Greetings,
> > Matthias
> >
> > [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
>
> > aerogear-dev at .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-misc-release-issue-tp7741p7742.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/20140509/a32a660c/attachment.html 

From kpiwko at redhat.com  Fri May  9 07:25:41 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 9 May 2014 13:25:41 +0200
Subject: [aerogear-dev] SimplePush Server 0.11.0
In-Reply-To: <CAFJm-3Eig8tMK_xCf__ESgSgpsh5caNRPBBKy1ANSVrDx_ss7w@mail.gmail.com>
References: <CAFJm-3HA3NM3kswb9jfcFi1tfx3QKGkGZL_5tqcnx8gHhzuZuQ@mail.gmail.com>
	<20140429125827.0dfcaa6f@kapy-ntb-x220>
	<CAFJm-3EOJGv-Vbq_5SWNVBreBOFqtiXf1hAX1rzz6hjWRbgodw@mail.gmail.com>
	<20140507195639.1e0105d1@kapy-ntb-x220>
	<CAFJm-3Eig8tMK_xCf__ESgSgpsh5caNRPBBKy1ANSVrDx_ss7w@mail.gmail.com>
Message-ID: <20140509132541.0f5439ed@kapy-ntb-x220>

Looks good to me.

What was tested:
* Netty module
* Vert.x on Vert.x 2.0.2.Final
* WildFly module on WF 8.0.0.Final

join

* simplepush-quickstart
* simplepush-unifiedpush-quickstart ( with brand new UPS 0.10.3)

join

* Firefox 29
* Chrome 27

No functional issues were found, however following PRs make it easier in
future:
* https://github.com/aerogear/aerogear.org/pull/297
* https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart/pull/3
* https://github.com/aerogear/aerogear-simplepush-quickstart/pull/3

I'm wondering why Travis triggers for these two examples that have no build to
be performed.

Karel

On Wed, 7 May 2014 20:28:04 +0200
Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> Awesome, thanks!
> 
> onsdagen den 7:e maj 2014 skrev Karel Piwko <kpiwko at redhat.com>:
> 
> > Hi,
> >
> > I had chance to test just Netty implementation with memory backed store.
> > I will be able to continue with Vert.x and AS/WF modules on Friday.
> >
> > Karel
> >
> >
> > On Mon, 5 May 2014 16:31:08 +0200
> > Daniel Bevenius <daniel.bevenius at gmail.com <javascript:;>> wrote:
> >
> > > AeroGear SimplePush 0.11.0 has been staged:
> > >
> > http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3144/
> > >
> > > Let us know if you find any issues or require more time for testing. If
> > > nothing crops up we will release on Thursday.
> > >
> > >
> > >
> > >
> > > On 29 April 2014 12:58, Karel Piwko <kpiwko at redhat.com <javascript:;>>
> > wrote:
> > >
> > > > Sounds good. Let me know when testing phase will be approaching.
> > > >
> > > > Karel
> > > >
> > > > On Wed, 23 Apr 2014 10:18:12 +0200
> > > > Daniel Bevenius <daniel.bevenius at gmail.com <javascript:;>> wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > just wanted to give a heads up that I've rescheduled the release of
> > > > > SimplePush 0.11.0 [1]. There are only two task remaining, but I'll be
> > > > > working on other things for a while which is the reason for there not
> > > > being
> > > > > more.
> > > > >
> > > > > The main task of interest I think is [2], which allows notifications
> > to
> > > > be
> > > > > done without a version in the body of the HTTP request. This I
> > believe
> > > > will
> > > > > simplify the admin ui and perhaps other areas. If you'd like to see
> > an
> > > > > earlier release then let me know and I'll get it done. As of now
> > though,
> > > > > I've set the release date to May 6.
> > > > >
> > > > > /Dan
> > > > >
> > > > >
> > > > > [1]
> > > > >
> > > >
> > https://issues.jboss.org/browse/AGSMPLPUSH-16?filter=12321270&jql=project%20%3D%20AGSMPLPUSH%20AND%20fixVersion%20%3D%20%220.11.0%22%20AND%20status%20in%20(Open%2C%20%22Coding%20In%20Progress%22%2C%20Reopened%2C%20%22Pull%20Request%20Sent%22)
> > > > >
> > > > > [2] https://issues.jboss.org/browse/AGSMPLPUSH-54
> > > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org <javascript:;>
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org <javascript:;>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >


From kpiwko at redhat.com  Fri May  9 07:39:40 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 9 May 2014 13:39:40 +0200
Subject: [aerogear-dev] AS/WF Modules location - proposing change
Message-ID: <20140509133940.1a29b07f@kapy-ntb-x220>

Hi,

I've come across this document -
https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganization.
It explains how WF/EAP (since EAP 6.1.0) modules are organized. 

Based on document, I believe we should change our tutorials and ask users to
install modules to:

${modules.basedir}/system/add-ons/aerogear
${modules.basedir}/system/add-ons/dbs 

That would keep base clean, allowing easier update of underlying container 
and also it will let us use the patching mechanism for our code, e.g:

${modules.basedir}/system/add-ons/aerogear/patches/security-fix-1

Thoughts? Note, add-on names were randomly generated.

Thanks,

Karel

From daniel.bevenius at gmail.com  Fri May  9 07:48:57 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 9 May 2014 13:48:57 +0200
Subject: [aerogear-dev] SimplePush Server 0.11.0
In-Reply-To: <20140509132541.0f5439ed@kapy-ntb-x220>
References: <CAFJm-3HA3NM3kswb9jfcFi1tfx3QKGkGZL_5tqcnx8gHhzuZuQ@mail.gmail.com>
	<20140429125827.0dfcaa6f@kapy-ntb-x220>
	<CAFJm-3EOJGv-Vbq_5SWNVBreBOFqtiXf1hAX1rzz6hjWRbgodw@mail.gmail.com>
	<20140507195639.1e0105d1@kapy-ntb-x220>
	<CAFJm-3Eig8tMK_xCf__ESgSgpsh5caNRPBBKy1ANSVrDx_ss7w@mail.gmail.com>
	<20140509132541.0f5439ed@kapy-ntb-x220>
Message-ID: <CAFJm-3FzTa1ub_0w8KEdax2GSeEqQDW2ib=5RONNAg=f0huhUA@mail.gmail.com>

Hi Karel,

thanks for doing this!

>I'm wondering why Travis triggers for these two examples that have no
build to be performed.
Not sure why this is. Need to look into this.

/Dan



On 9 May 2014 13:25, Karel Piwko <kpiwko at redhat.com> wrote:

> Looks good to me.
>
> What was tested:
> * Netty module
> * Vert.x on Vert.x 2.0.2.Final
> * WildFly module on WF 8.0.0.Final
>
> join
>
> * simplepush-quickstart
> * simplepush-unifiedpush-quickstart ( with brand new UPS 0.10.3)
>
> join
>
> * Firefox 29
> * Chrome 27
>
> No functional issues were found, however following PRs make it easier in
> future:
> * https://github.com/aerogear/aerogear.org/pull/297
> *
> https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart/pull/3
> * https://github.com/aerogear/aerogear-simplepush-quickstart/pull/3
>
> I'm wondering why Travis triggers for these two examples that have no
> build to
> be performed.
>
> Karel
>
> On Wed, 7 May 2014 20:28:04 +0200
> Daniel Bevenius <daniel.bevenius at gmail.com> wrote:
>
> > Awesome, thanks!
> >
> > onsdagen den 7:e maj 2014 skrev Karel Piwko <kpiwko at redhat.com>:
> >
> > > Hi,
> > >
> > > I had chance to test just Netty implementation with memory backed
> store.
> > > I will be able to continue with Vert.x and AS/WF modules on Friday.
> > >
> > > Karel
> > >
> > >
> > > On Mon, 5 May 2014 16:31:08 +0200
> > > Daniel Bevenius <daniel.bevenius at gmail.com <javascript:;>> wrote:
> > >
> > > > AeroGear SimplePush 0.11.0 has been staged:
> > > >
> > >
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3144/
> > > >
> > > > Let us know if you find any issues or require more time for testing.
> If
> > > > nothing crops up we will release on Thursday.
> > > >
> > > >
> > > >
> > > >
> > > > On 29 April 2014 12:58, Karel Piwko <kpiwko at redhat.com<javascript:;>>
> > > wrote:
> > > >
> > > > > Sounds good. Let me know when testing phase will be approaching.
> > > > >
> > > > > Karel
> > > > >
> > > > > On Wed, 23 Apr 2014 10:18:12 +0200
> > > > > Daniel Bevenius <daniel.bevenius at gmail.com <javascript:;>> wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > just wanted to give a heads up that I've rescheduled the release
> of
> > > > > > SimplePush 0.11.0 [1]. There are only two task remaining, but
> I'll be
> > > > > > working on other things for a while which is the reason for
> there not
> > > > > being
> > > > > > more.
> > > > > >
> > > > > > The main task of interest I think is [2], which allows
> notifications
> > > to
> > > > > be
> > > > > > done without a version in the body of the HTTP request. This I
> > > believe
> > > > > will
> > > > > > simplify the admin ui and perhaps other areas. If you'd like to
> see
> > > an
> > > > > > earlier release then let me know and I'll get it done. As of now
> > > though,
> > > > > > I've set the release date to May 6.
> > > > > >
> > > > > > /Dan
> > > > > >
> > > > > >
> > > > > > [1]
> > > > > >
> > > > >
> > >
> https://issues.jboss.org/browse/AGSMPLPUSH-16?filter=12321270&jql=project%20%3D%20AGSMPLPUSH%20AND%20fixVersion%20%3D%20%220.11.0%22%20AND%20status%20in%20(Open%2C%20%22Coding%20In%20Progress%22%2C%20Reopened%2C%20%22Pull%20Request%20Sent%22)
> > > > > >
> > > > > > [2] https://issues.jboss.org/browse/AGSMPLPUSH-54
> > > > >
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org <javascript:;>
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org <javascript:;>
> > > https://lists.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/20140509/16d9305d/attachment.html 

From kpiwko at redhat.com  Fri May  9 07:56:55 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 9 May 2014 13:56:55 +0200
Subject: [aerogear-dev] paging installations new console
In-Reply-To: <F6064C42-F74A-43CC-9982-1902A1D38554@redhat.com>
References: <9EA24B7B-B865-46AD-B450-B2910704132E@redhat.com>
	<CAAg5f2SskWVrPztUQ9BySs64bJxCshmiP76PkYAC6QEMP7wSVQ@mail.gmail.com>
	<F6064C42-F74A-43CC-9982-1902A1D38554@redhat.com>
Message-ID: <20140509135655.3758746f@kapy-ntb-x220>

On Thu, 8 May 2014 09:19:34 +0200
Erik Jan de Wit <edewit at redhat.com> wrote:

> Two in one:
> 
> On 8 May,2014, at 8:25 , Matthias Wessendorf <mwessendorf at gmail.com> wrote:
> 
> > 
> > This query will give the total number of installations for each variant,
> > but only for android. So what I would like to suggest it to simplify the
> > data model and only have a relation with variants instead of one per type
> > this will also make the data model more extendable (when a new device type
> > is introduced the data model doesn?t have to change). If grouping of these
> > variants is needed clients will need to do it themselves.
> > 
> > that would still allow us to say "Android-free variant has 10000
> > installations; iPad variant has 5000 installations", right ? 
> > 
> 
> Right, but do it in one query instead of x and have a more flexible data
> model at the same time.
> 
> On 7 May,2014, Karel Piwko wrote:
> 
> > I think it is a good idea to simplify underlying model. Could we 
> > additionally provide SQL views that groups only one variant and expose it
> > via REST point? 
> 
> Right I would like to keep the REST endpoint the same as this is our
> interface. Don?t know if we should base the grouping on views as we should
> support multiple databases, and like you said don?t know if this can be done
> for H2, for now let?s keep it simple and just do a `group by` query?

Sure. SQL view might only be an performance optimization for some of the
databases. Optional feature tbd in future.

> 
>  Cheers,
> 	Erik Jan

From daniel.bevenius at gmail.com  Fri May  9 08:06:47 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 9 May 2014 14:06:47 +0200
Subject: [aerogear-dev] AS/WF Modules location - proposing change
In-Reply-To: <20140509133940.1a29b07f@kapy-ntb-x220>
References: <20140509133940.1a29b07f@kapy-ntb-x220>
Message-ID: <CAFJm-3EPtq++9f774DsSH=xH8CFiwczbvxU4Sm3vt05SfJc-vw@mail.gmail.com>

Thanks for pointing that document out. I'll read through it but, this
sounds like a good idea to me. I'll create task for SimplePush and
UnfiedPush next based on what is agree upon here.




On 9 May 2014 13:39, Karel Piwko <kpiwko at redhat.com> wrote:

> Hi,
>
> I've come across this document -
>
> https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganization
> .
> It explains how WF/EAP (since EAP 6.1.0) modules are organized.
>
> Based on document, I believe we should change our tutorials and ask users
> to
> install modules to:
>
> ${modules.basedir}/system/add-ons/aerogear
> ${modules.basedir}/system/add-ons/dbs
>
> That would keep base clean, allowing easier update of underlying container
> and also it will let us use the patching mechanism for our code, e.g:
>
> ${modules.basedir}/system/add-ons/aerogear/patches/security-fix-1
>
> Thoughts? Note, add-on names were randomly generated.
>
> Thanks,
>
> Karel
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140509/e696c3e3/attachment.html 

From daniel.bevenius at gmail.com  Fri May  9 08:11:29 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 9 May 2014 14:11:29 +0200
Subject: [aerogear-dev] SimplePush Server 0.11.0
In-Reply-To: <CAFJm-3FzTa1ub_0w8KEdax2GSeEqQDW2ib=5RONNAg=f0huhUA@mail.gmail.com>
References: <CAFJm-3HA3NM3kswb9jfcFi1tfx3QKGkGZL_5tqcnx8gHhzuZuQ@mail.gmail.com>
	<20140429125827.0dfcaa6f@kapy-ntb-x220>
	<CAFJm-3EOJGv-Vbq_5SWNVBreBOFqtiXf1hAX1rzz6hjWRbgodw@mail.gmail.com>
	<20140507195639.1e0105d1@kapy-ntb-x220>
	<CAFJm-3Eig8tMK_xCf__ESgSgpsh5caNRPBBKy1ANSVrDx_ss7w@mail.gmail.com>
	<20140509132541.0f5439ed@kapy-ntb-x220>
	<CAFJm-3FzTa1ub_0w8KEdax2GSeEqQDW2ib=5RONNAg=f0huhUA@mail.gmail.com>
Message-ID: <CAFJm-3Hfbh_WnRuRtp2k9-bLoNrGKZRvNHQHn7SXHvZem5Ksng@mail.gmail.com>

We have pressed the button and now we just have to wait for it to be
replicated to Maven Central.

/Dan


On 9 May 2014 13:48, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> Hi Karel,
>
> thanks for doing this!
>
> >I'm wondering why Travis triggers for these two examples that have no
> build to be performed.
> Not sure why this is. Need to look into this.
>
> /Dan
>
>
>
> On 9 May 2014 13:25, Karel Piwko <kpiwko at redhat.com> wrote:
>
>> Looks good to me.
>>
>> What was tested:
>> * Netty module
>> * Vert.x on Vert.x 2.0.2.Final
>> * WildFly module on WF 8.0.0.Final
>>
>> join
>>
>> * simplepush-quickstart
>> * simplepush-unifiedpush-quickstart ( with brand new UPS 0.10.3)
>>
>> join
>>
>> * Firefox 29
>> * Chrome 27
>>
>> No functional issues were found, however following PRs make it easier in
>> future:
>> * https://github.com/aerogear/aerogear.org/pull/297
>> *
>> https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart/pull/3
>> * https://github.com/aerogear/aerogear-simplepush-quickstart/pull/3
>>
>> I'm wondering why Travis triggers for these two examples that have no
>> build to
>> be performed.
>>
>> Karel
>>
>> On Wed, 7 May 2014 20:28:04 +0200
>> Daniel Bevenius <daniel.bevenius at gmail.com> wrote:
>>
>> > Awesome, thanks!
>> >
>> > onsdagen den 7:e maj 2014 skrev Karel Piwko <kpiwko at redhat.com>:
>> >
>> > > Hi,
>> > >
>> > > I had chance to test just Netty implementation with memory backed
>> store.
>> > > I will be able to continue with Vert.x and AS/WF modules on Friday.
>> > >
>> > > Karel
>> > >
>> > >
>> > > On Mon, 5 May 2014 16:31:08 +0200
>> > > Daniel Bevenius <daniel.bevenius at gmail.com <javascript:;>> wrote:
>> > >
>> > > > AeroGear SimplePush 0.11.0 has been staged:
>> > > >
>> > >
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3144/
>> > > >
>> > > > Let us know if you find any issues or require more time for
>> testing. If
>> > > > nothing crops up we will release on Thursday.
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On 29 April 2014 12:58, Karel Piwko <kpiwko at redhat.com<javascript:;>>
>> > > wrote:
>> > > >
>> > > > > Sounds good. Let me know when testing phase will be approaching.
>> > > > >
>> > > > > Karel
>> > > > >
>> > > > > On Wed, 23 Apr 2014 10:18:12 +0200
>> > > > > Daniel Bevenius <daniel.bevenius at gmail.com <javascript:;>> wrote:
>> > > > >
>> > > > > > Hi all,
>> > > > > >
>> > > > > > just wanted to give a heads up that I've rescheduled the
>> release of
>> > > > > > SimplePush 0.11.0 [1]. There are only two task remaining, but
>> I'll be
>> > > > > > working on other things for a while which is the reason for
>> there not
>> > > > > being
>> > > > > > more.
>> > > > > >
>> > > > > > The main task of interest I think is [2], which allows
>> notifications
>> > > to
>> > > > > be
>> > > > > > done without a version in the body of the HTTP request. This I
>> > > believe
>> > > > > will
>> > > > > > simplify the admin ui and perhaps other areas. If you'd like to
>> see
>> > > an
>> > > > > > earlier release then let me know and I'll get it done. As of now
>> > > though,
>> > > > > > I've set the release date to May 6.
>> > > > > >
>> > > > > > /Dan
>> > > > > >
>> > > > > >
>> > > > > > [1]
>> > > > > >
>> > > > >
>> > >
>> https://issues.jboss.org/browse/AGSMPLPUSH-16?filter=12321270&jql=project%20%3D%20AGSMPLPUSH%20AND%20fixVersion%20%3D%20%220.11.0%22%20AND%20status%20in%20(Open%2C%20%22Coding%20In%20Progress%22%2C%20Reopened%2C%20%22Pull%20Request%20Sent%22)
>> > > > > >
>> > > > > > [2] https://issues.jboss.org/browse/AGSMPLPUSH-54
>> > > > >
>> > > > > _______________________________________________
>> > > > > aerogear-dev mailing list
>> > > > > aerogear-dev at lists.jboss.org <javascript:;>
>> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >
>> > >
>> > > _______________________________________________
>> > > aerogear-dev mailing list
>> > > aerogear-dev at lists.jboss.org <javascript:;>
>> > > https://lists.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/20140509/157b3e2b/attachment-0001.html 

From kpiwko at redhat.com  Fri May  9 08:12:58 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 9 May 2014 14:12:58 +0200
Subject: [aerogear-dev] [aerogear-misc] release issue
In-Reply-To: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
References: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
Message-ID: <20140509141258.45271762@kapy-ntb-x220>

What about:

1/ Release ag-misc 0.1.2 to Central to fix ag-parent
2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
=> aligns minor version with ag-misc
=> Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send a PR)

No deletes needed. Maven world will not collapse ;-)

Karel


On Fri, 9 May 2014 12:21:15 +0200
Matthias Wessendorf <mwessendorf at gmail.com> wrote:

> Hi,
> 
> Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
> number (0.2.0).
> This artifact was already pushed to maven central.
> 
> On IRC we had the following idea:
> * update master to 0.1.2-SNAPSHOT
> * perform the release again (that hopefully will result in 0.1.2 on maven
> central)
> 
> That still means we have a 0.2.0 on maven central. I will ask my contacts
> at Sonatype to remove the 0.2.0 bits;
> 
> If folks are OK w/ that, I am happy to perform these steps by Monday morning
> 
> Greetings,
> Matthias
> 
> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
> 


From scm.blanc at gmail.com  Fri May  9 08:20:54 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 9 May 2014 14:20:54 +0200
Subject: [aerogear-dev] UnifiedPush 0.10.3 - release coming soon (WAR
	and OpenShift)
In-Reply-To: <CAAg5f2RhVFCrGd90d+9i1+7g+YOvTK5xV8-k_otc3Jr+JOAf3Q@mail.gmail.com>
References: <CAAg5f2RhVFCrGd90d+9i1+7g+YOvTK5xV8-k_otc3Jr+JOAf3Q@mail.gmail.com>
Message-ID: <CAD_dpu03M8imCpZAGAkPoTpuM32C8LA2R9aGwUzVWaig+fbnPg@mail.gmail.com>

Hi,
Tested the WAR : +1
Tested the cartridge : +1

Just one small remark on the cartridge : In my application list, the label
shows 0.10.0 : http://s28.postimg.org/gn8cll1r1/ups1003.png
Must be just a property to change in the cartridge.





On Thu, May 8, 2014 at 11:52 AM, Matthias Wessendorf
<mwessendorf at gmail.com>wrote:

> Hi,
>
> in order to be consistent with the latest Cordova changes name, we did
> apply them (and improved GCM exception handling) to the 0.10.x branch as
> well. That's the only content of the release:
> * Cordova registration snippets match the LATEST (0.5.x) plugin
> * GCM exception handling improved
>
> 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/13
>
>
> If you want to test it - it's simple! Just go ahead and use my fork of the
> repo:
>
> rhc app create --no-git <YOUR COOL APP NAME>
> https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.5
>
>
> Let me know the results of your testing;
> If I hear nothing bad by Tuesday evening (give it a few more days due to
> European holidays), the merges will happen on Wednesday
>
>
> 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/20140509/384e8a3a/attachment.html 

From kpiwko at redhat.com  Fri May  9 08:36:39 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 9 May 2014 14:36:39 +0200
Subject: [aerogear-dev] UnifiedPush 0.10.3 - release coming soon (WAR
 and OpenShift)
In-Reply-To: <CAD_dpu03M8imCpZAGAkPoTpuM32C8LA2R9aGwUzVWaig+fbnPg@mail.gmail.com>
References: <CAAg5f2RhVFCrGd90d+9i1+7g+YOvTK5xV8-k_otc3Jr+JOAf3Q@mail.gmail.com>
	<CAD_dpu03M8imCpZAGAkPoTpuM32C8LA2R9aGwUzVWaig+fbnPg@mail.gmail.com>
Message-ID: <20140509143639.1360c2d3@kapy-ntb-x220>

On Fri, 9 May 2014 14:20:54 +0200
Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi,
> Tested the WAR : +1
> Tested the cartridge : +1
> 
> Just one small remark on the cartridge : In my application list, the label
> shows 0.10.0 : http://s28.postimg.org/gn8cll1r1/ups1003.png
> Must be just a property to change in the cartridge.

It's here:
https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/blob/master/metadata/manifest.yml

If we change description, should not we also change version in metadata? It
would lead to zillions of version in
https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/tree/master/versions
though.

And it would also make cartridge bigger and slower to download over the time -
well, that would happen even now just much slowly.

Could not we just download WAR from Maven Central in the cartridge based on
the metadata? I can prepare such PR, hoping it would not conflict with KC cart
updates.

> 
> 
> 
> 
> 
> On Thu, May 8, 2014 at 11:52 AM, Matthias Wessendorf
> <mwessendorf at gmail.com>wrote:
> 
> > Hi,
> >
> > in order to be consistent with the latest Cordova changes name, we did
> > apply them (and improved GCM exception handling) to the 0.10.x branch as
> > well. That's the only content of the release:
> > * Cordova registration snippets match the LATEST (0.5.x) plugin
> > * GCM exception handling improved
> >
> > 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/13
> >
> >
> > If you want to test it - it's simple! Just go ahead and use my fork of the
> > repo:
> >
> > rhc app create --no-git <YOUR COOL APP NAME>
> > https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.5
> >
> >
> > Let me know the results of your testing;
> > If I hear nothing bad by Tuesday evening (give it a few more days due to
> > European holidays), the merges will happen on Wednesday
> >
> >
> > 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
> >


From daniel at passos.me  Fri May  9 08:47:02 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 9 May 2014 09:47:02 -0300
Subject: [aerogear-dev] AeroGear Android Push 0.2 on staging
In-Reply-To: <CAD_dpu2jn4oe3YwZMfZbgFcNJh=gAjLAJGKeEaHxCqP+JrVTpw@mail.gmail.com>
References: <CAKjsGbuj-n4GYsMXMko3PES09RB_1KRyK1_hL8zL1CFa0P4eew@mail.gmail.com>
	<CAD_dpu2jn4oe3YwZMfZbgFcNJh=gAjLAJGKeEaHxCqP+JrVTpw@mail.gmail.com>
Message-ID: <CAKjsGbuwMZ4ujdpJNhoF9ruRSkEaJBuQKL9VRFVhBCCiK+HNXw@mail.gmail.com>

Released on Maven Central \o/


On Wed, May 7, 2014 at 10:15 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:

> Tested and works !
> Ship it !
>
>
>
> On Wed, May 7, 2014 at 2:03 PM, Daniel Passos <daniel at passos.me> wrote:
>
>> Hi Folks,
>>
>> The new version of AeroGear Android Push was shipped to Nexus[1].
>>
>> We plain release it to Maven Central in the next friday
>>
>> Feel free to test and send your feedback
>>
>> [1]
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3165/
>>
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140509/91b795d7/attachment.html 

From lholmqui at redhat.com  Fri May  9 09:27:51 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 9 May 2014 09:27:51 -0400
Subject: [aerogear-dev] Empire JS day 2
Message-ID: <2D8C1BF3-7A44-4863-99B5-A04F9A5195B4@redhat.com>

Now for Day 2,

going off topic for a second, i realized that after the first day, my jeans weren't skinny enough. Ok back to the talks

Build Artifacts in Source Control

by Clay Smith

youtube link: https://www.youtube.com/watch?v=KxqVtsnP6Ko - part 1

https://www.youtube.com/watch?v=ViPsP7HzMJ4 - part 2

this talk was about how it is bad to put compiled production distribution stuff in git/vcs

also talk about using the github release api

and that we need better tools for production builds

Preventing XSS & CSRF

by Jeremy Stashewsky

youtube link: https://www.youtube.com/watch?v=_jubb3g1HVg

this was a cool talk about Cross Site Scripting and Cross Site Request Forgery and some techniques to help prevent it

Bits of Nodebots.Next / Animating with Javascript

by Rick Waldron

youtube link: https://www.youtube.com/watch?v=0-6_iA1zZDk

An awesome talk. Just watch the video

Hacking Webforms with Phantom.js

by Alyssa Ravasio

youtube link: https://www.youtube.com/watch?v=HYKP0vZsTSI

a interesting talk about using phantom.js to fill out forms.

Her business is a camping booking site. Existing booking sites for campsites are crappy, and there is only really one. There is no public API for camp listings, so a user goes to her site, books their campsite on a nice looking/nice experience site, then in the background, phantom.js goes to the crappy site and books the camp site.

MyDB

by Guillermo Rauch - socket.io author( i think )

youtube link: https://www.youtube.com/watch?v=0jwygdZW-r0

kind of a neat talk about sync, probably somewhat relevant to what we might be doing

BigPipe

by Arnout Kazemier - from nodejitsu

youtube link: https://www.youtube.com/watch?v=sYArq4XhdFo

BigPipe is something that Facebook was suppose to deliver, but never really did, so these guys did there own thing

it's basically the ability to render different parts of the page asyncly, using what they call pagelets

an example of BigPipe in use is browsenpm.org

Transitioning Groupon to node.js

by Sean McCullough

youtube link: https://www.youtube.com/watch?v=TWVblTpUlxM

kind of a neat talk about moving groupon's rails stack to node.js and some of the challenges and why it was right for them

Hacking Art with Node.js and Image Analysis

by John Resig - Author of a little know library called jQuery

youtube link: https://www.youtube.com/watch?v=_JrJdD2Ssnk

showing off some library's that he wrote to do image analysis, didn't really show any code though

WebRTC can be easy

by Michelle Bu - author of PeerJS

youtube link: https://www.youtube.com/watch?v=ONxw9R1Fxfs

pretty neat talk about WebRTC and making it easier to use.

The hidden benefits of static analysis

by Kirill Cherkashin and Tsering Shrestha

youtube link: https://www.youtube.com/watch?v=3ZqTvexCtZM

talk about how JS tools can be awesome even though JS is a dynamic language.

showed some WebStorm IDE js autocomplete stuff

and some other libs like spy-js

Easing into ECMAScript 6 and Beyond

by Ben Newman - works at facebook

youtube link: https://www.youtube.com/watch?v=kXY9hIPKuLQ

showing off his library "recast" and how we should always be transpiling to code for the future without choking on it

Pixel Art and Javascript

by Vince Allen

youtube link: https://www.youtube.com/watch?v=W6tP3nJp3NM

Needed to leave to catch a train, so i missed this one, so just watch the video
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140509/a11f3838/attachment-0001.html 

From m.scholtes at nol-is.de  Fri May  9 09:21:07 2014
From: m.scholtes at nol-is.de (Mark Scholtes)
Date: Fri, 09 May 2014 15:21:07 +0200
Subject: [aerogear-dev] NotifyingHandler and PushApplication
Message-ID: <536CD643.1090000@nol-is.de>

Hi!

I want to use the UnifiedPush Server within an androis app. I have set 
up the server and everything is fine.
But now I want to implement the client in the app. I am using Titanium 
and the Alloy Framework.

I don't know how to use the aerogear-android in this environment.

Do you have an idea how to solve my problem or is there an easier way to 
interact with the server?

With kind regards
Mit freundlichem Gru?
i. A. Mark Scholtes
---

NOLIS GmbH
Sitz Nienburg/Weser
Gesch?ftsf?hrer: Uwe Warnecke
Registergericht Walsrode - HRB 30797

Celler Stra?e 53
31582 Nienburg/Weser

Telefon: 0 50 21 / 88 77 555
Telefax: 0 50 21 / 88 77 599
E-Mail: m.scholtes at nolis.de <mailto://m.scholtes at nolis.de>
Internet: http://www.nolis.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140509/8bb478c6/attachment.html 

From daniel at passos.me  Fri May  9 10:39:08 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 9 May 2014 11:39:08 -0300
Subject: [aerogear-dev] NotifyingHandler and PushApplication
In-Reply-To: <536CD643.1090000@nol-is.de>
References: <536CD643.1090000@nol-is.de>
Message-ID: <CAKjsGbuxfD6UMPZKra3ZVfNxrqyW78zdnY8pPHcuobgTA6rguA@mail.gmail.com>

Hi Mark,

Thanks for your interest.

Unfortunately we don't have experience with that framework.

Have you looked at our documentations[1][2]? and our examples apps[3][4[

[1] http://aerogear.org/docs/guides/aerogear-android/push/
[2] http://aerogear.org/docs/guides/aerogear-push-android/
[3] https://github.com/aerogear/aerogear-android-cookbook
[4] https://github.com/aerogear/aerogear-push-helloworld

-- Passos


On Fri, May 9, 2014 at 10:21 AM, Mark Scholtes <m.scholtes at nol-is.de> wrote:

>  Hi!
>
> I want to use the UnifiedPush Server within an androis app. I have set up
> the server and everything is fine.
> But now I want to implement the client in the app. I am using Titanium and
> the Alloy Framework.
>
> I don't know how to use the aerogear-android in this environment.
>
> Do you have an idea how to solve my problem or is there an easier way to
> interact with the server?
>
> With kind regards
> Mit freundlichem Gru?
> i. A. Mark Scholtes
> ---
>
> NOLIS GmbH
> Sitz Nienburg/Weser
> Gesch?ftsf?hrer: Uwe Warnecke
> Registergericht Walsrode - HRB 30797
>
> Celler Stra?e 53
> 31582 Nienburg/Weser
>
> Telefon: 0 50 21 / 88 77 555
> Telefax: 0 50 21 / 88 77 599
> E-Mail: m.scholtes at nolis.de <//m.scholtes at nolis.de>
> Internet: http://www.nolis.de
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140509/c3774ec1/attachment.html 

From avibelli at redhat.com  Fri May  9 11:45:35 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Fri, 9 May 2014 08:45:35 -0700 (PDT)
Subject: [aerogear-dev] [aerogear-misc] release issue
In-Reply-To: <20140509141258.45271762@kapy-ntb-x220>
References: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
	<20140509141258.45271762@kapy-ntb-x220>
Message-ID: <1399650335010-7757.post@n5.nabble.com>

Great that we agree on 1), which is the most important.
@Karel: what change would you require about checkstyle plugin (just
wondering)?
It's already defined in the pluginManagement of jboss-parent, and it's
declared in the plugin of aerogear-parent, so it's inherited by all
projects.
The configuration of the plugin would be this one for every project:

    <pluginManagement>
      <plugins>   
        ....
        <plugin>
          <artifactId>maven-checkstyle-plugin</artifactId>
          <version>2.10</version>
        </plugin>
        ...
      </plugins>
    </pluginManagement>
    
    <plugin>
        <artifactId>maven-checkstyle-plugin</artifactId>
        <version>2.10</version>
        <executions>
          <execution>
            <id>checkstyle-report</id>
            <phase>process-classes</phase>
            <goals>
              <goal>check</goal>
            </goals>
            <configuration>
              <includeTestSourceDirectory>true</includeTestSourceDirectory>
              <configLocation>/checkstyle-rules.xml</configLocation>
              <logViolationsToConsole>true</logViolationsToConsole>
              <violationSeverity>error</violationSeverity>
            </configuration>
          </execution>
        </executions>
        <dependencies>
          <dependency>
            <groupId>org.jboss.aerogear</groupId>
            <artifactId>aerogear-misc</artifactId>
            <version>0.1.2</version>
            <scope>compile</scope>
          </dependency>
        </dependencies>
        <configuration>
          <includeTestSourceDirectory>true</includeTestSourceDirectory>
          <configLocation>/checkstyle-rules.xml</configLocation>
          <logViolationsToConsole>true</logViolationsToConsole>
          <violationSeverity>error</violationSeverity>
        </configuration>
      </plugin>


Thanks
Andrea


Karel Piwko wrote
> What about:
> 
> 1/ Release ag-misc 0.1.2 to Central to fix ag-parent
> 2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
> => aligns minor version with ag-misc
> => Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send a
> PR)
> 
> No deletes needed. Maven world will not collapse ;-)
> 
> Karel
> 
> 
> On Fri, 9 May 2014 12:21:15 +0200
> Matthias Wessendorf &lt;

> mwessendorf@

> &gt; wrote:
> 
>> Hi,
>> 
>> Andrea reported that the 0.1.2 release (see [1]) contains the wrong
>> version
>> number (0.2.0).
>> This artifact was already pushed to maven central.
>> 
>> On IRC we had the following idea:
>> * update master to 0.1.2-SNAPSHOT
>> * perform the release again (that hopefully will result in 0.1.2 on maven
>> central)
>> 
>> That still means we have a 0.2.0 on maven central. I will ask my contacts
>> at Sonatype to remove the 0.2.0 bits;
>> 
>> If folks are OK w/ that, I am happy to perform these steps by Monday
>> morning
>> 
>> Greetings,
>> Matthias
>> 
>> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
>> 
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-misc-release-issue-tp7741p7757.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From kpiwko at redhat.com  Fri May  9 12:36:30 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Fri, 9 May 2014 18:36:30 +0200
Subject: [aerogear-dev] [aerogear-misc] release issue
In-Reply-To: <1399650335010-7757.post@n5.nabble.com>
References: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
	<20140509141258.45271762@kapy-ntb-x220>
	<1399650335010-7757.post@n5.nabble.com>
Message-ID: <20140509183630.06d5d82c@kapy-ntb-x220>

On Fri, 9 May 2014 08:45:35 -0700 (PDT)
Andrea Vibelli <avibelli at redhat.com> wrote:

> Great that we agree on 1), which is the most important.
> @Karel: what change would you require about checkstyle plugin (just
> wondering)?

Right, I've realized that it is already there after posting. Thanks Andrea!

> 
> 
> Karel Piwko wrote
> > What about:
> > 
> > 1/ Release ag-misc 0.1.2 to Central to fix ag-parent
> > 2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
> > => aligns minor version with ag-misc
> > => Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send a
> > PR)
> > 
> > No deletes needed. Maven world will not collapse ;-)
> > 
> > Karel
> > 
> > 
> > On Fri, 9 May 2014 12:21:15 +0200
> > Matthias Wessendorf &lt;
> 
> > mwessendorf@
> 
> > &gt; wrote:
> > 
> >> Hi,
> >> 
> >> Andrea reported that the 0.1.2 release (see [1]) contains the wrong
> >> version
> >> number (0.2.0).
> >> This artifact was already pushed to maven central.
> >> 
> >> On IRC we had the following idea:
> >> * update master to 0.1.2-SNAPSHOT
> >> * perform the release again (that hopefully will result in 0.1.2 on maven
> >> central)
> >> 
> >> That still means we have a 0.2.0 on maven central. I will ask my contacts
> >> at Sonatype to remove the 0.2.0 bits;
> >> 
> >> If folks are OK w/ that, I am happy to perform these steps by Monday
> >> morning
> >> 
> >> Greetings,
> >> Matthias
> >> 
> >> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
> >> 
> > 
> > _______________________________________________
> > aerogear-dev mailing list
> 
> > aerogear-dev at .jboss
> 
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> 
> 
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-aerogear-misc-release-issue-tp7741p7757.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 matzew at apache.org  Mon May 12 01:55:56 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 12 May 2014 07:55:56 +0200
Subject: [aerogear-dev] AeroGear-Misc 0.1.2 has been staged
Message-ID: <CAAg5f2Qatk46x6AX-ppuGjJcWVaXsdkNaayFewVHqm3BGrsXWw@mail.gmail.com>

Hello,

to follow up on last weeks issues w/ the release, I have staged the 0.1.2
version:

http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/

Let me know if that version works, and I will release tomorrow

-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/20140512/b79c5fa9/attachment.html 

From matzew at apache.org  Mon May 12 02:02:11 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 12 May 2014 08:02:11 +0200
Subject: [aerogear-dev] AS/WF Modules location - proposing change
In-Reply-To: <CAFJm-3EPtq++9f774DsSH=xH8CFiwczbvxU4Sm3vt05SfJc-vw@mail.gmail.com>
References: <20140509133940.1a29b07f@kapy-ntb-x220>
	<CAFJm-3EPtq++9f774DsSH=xH8CFiwczbvxU4Sm3vt05SfJc-vw@mail.gmail.com>
Message-ID: <CAAg5f2Te65ef86b-__n8e+mV6b4vBk-fpS5k2E784XAc-yU8Mg@mail.gmail.com>

+1 I agree


On Fri, May 9, 2014 at 2:06 PM, Daniel Bevenius
<daniel.bevenius at gmail.com>wrote:

> Thanks for pointing that document out. I'll read through it but, this
> sounds like a good idea to me. I'll create task for SimplePush and
> UnfiedPush next based on what is agree upon here.
>
>
>
>
> On 9 May 2014 13:39, Karel Piwko <kpiwko at redhat.com> wrote:
>
>> Hi,
>>
>> I've come across this document -
>>
>> https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganization
>> .
>> It explains how WF/EAP (since EAP 6.1.0) modules are organized.
>>
>> Based on document, I believe we should change our tutorials and ask users
>> to
>> install modules to:
>>
>> ${modules.basedir}/system/add-ons/aerogear
>> ${modules.basedir}/system/add-ons/dbs
>>
>> That would keep base clean, allowing easier update of underlying container
>> and also it will let us use the patching mechanism for our code, e.g:
>>
>> ${modules.basedir}/system/add-ons/aerogear/patches/security-fix-1
>>
>> Thoughts? Note, add-on names were randomly generated.
>>
>> 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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140512/34db6e3d/attachment-0001.html 

From matzew at apache.org  Mon May 12 02:25:13 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 12 May 2014 08:25:13 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CAD_dpu3UYKcTEdyz5ugK1fojyPQjddEnM7W3FR8dh=HEhHj_GQ@mail.gmail.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<CAAg5f2RMHB019npB11wmGtpXMWZSHwHN=MnJKe8XZ+8oTexXgg@mail.gmail.com>
	<CAD_dpu3UYKcTEdyz5ugK1fojyPQjddEnM7W3FR8dh=HEhHj_GQ@mail.gmail.com>
Message-ID: <CAAg5f2R4QGcdGuK5ZgnJY2YLgU=0PevygTsamcA=-b5590hTWg@mail.gmail.com>

Hylke, any feedback?

IMO we are done:
* 'Send Notifications' available from sidebar icon (with a "Select
Application" UI, when clicking the Notification icon on the sidebar)
* 'Send Notifications' available from Application Details page (as designed
and current UI implements)


-Matthias






On Wed, May 7, 2014 at 6:50 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

>
>
>
> On Wed, May 7, 2014 at 1:35 PM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>>
>>
>>
>> On Wed, May 7, 2014 at 11:54 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>>
>>> Hi,
>>>
>>> as discussed , we need some sort of 'stats' around push, like:
>>> * time of sending
>>> * receivers (e.g. categories, alias ?)
>>> * content/payload of the message
>>> * could be sent out to APNs/GCM
>>>
>>>
>>> But, where, or how to add this ?
>>> My current thought is:
>>>
>>> When a user did select an "Application", he enters the "Application
>>> Details Page" (see [1]), now here, on the sidebar (see [2]) he would see
>>> the "Notifications" icon.
>>>
>>> Clicking on that  "Notifications" icon, would give you a new page, that
>>> contains the "Send Notifications..." button (currently located in [1]), and
>>> a table of all the push messages that were sent out for the _current_
>>> selected Application.
>>>
>>
>>
>> Actually..... not sure... perhaps we keep the "Application Details Page"
>> for just working w/ the App (e.g. renaming, updating certs/keys), and
>> always have the "Notification icon" on the sidebar.
>>
> +1
>
>>
>> When you click on the icon, you have to select a Application, and after
>> that, you see the new page, that contains the "Send Notifications..."
>> button (currently located in [1]), and a table of all the push messages
>> that were sent out for the _current_ selected Application.
>>
>
> Sounds good but just not sure to also migrate the "Send Notifications ..."
>  feature there. On one side it makes sense to have it there but on the
> other hand it's also nice to have a direct access to this feature when you
> are on the application detail page. Other point : maybe when we will
> introduce roles, some might not have the rights to check the stats but
> still have the right to send a test message.
>
> So, maybe we can duplicate the "Send Notifications ..." button and keeping
> it also on the application detail page, wdyt ?
>
>
>
>
>> any thoughts ?
>>
>>
>> -Matthias
>>
>>
>>>
>>> Any thoughts ?
>>>
>>> -Matthias
>>>
>>> [1]
>>> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>>> [2]
>>> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>>>
>>>
>>> --
>>> 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/20140512/1f342f1c/attachment.html 

From matzew at apache.org  Mon May 12 02:37:34 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 12 May 2014 08:37:34 +0200
Subject: [aerogear-dev] UnifiedPush 0.10.3 - release coming soon (WAR
	and OpenShift)
In-Reply-To: <CAD_dpu03M8imCpZAGAkPoTpuM32C8LA2R9aGwUzVWaig+fbnPg@mail.gmail.com>
References: <CAAg5f2RhVFCrGd90d+9i1+7g+YOvTK5xV8-k_otc3Jr+JOAf3Q@mail.gmail.com>
	<CAD_dpu03M8imCpZAGAkPoTpuM32C8LA2R9aGwUzVWaig+fbnPg@mail.gmail.com>
Message-ID: <CAAg5f2TE5C=26DMH4KGG4Bux69qvRpG1L+ZNrZ7GiEWcAD-_oA@mail.gmail.com>

On Fri, May 9, 2014 at 2:20 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi,
> Tested the WAR : +1
> Tested the cartridge : +1
>
> Just one small remark on the cartridge : In my application list, the label
> shows 0.10.0 : http://s28.postimg.org/gn8cll1r1/ups1003.png
> Must be just a property to change in the cartridge.
>

that's fine


>
>
>
>
>
> On Thu, May 8, 2014 at 11:52 AM, Matthias Wessendorf <
> mwessendorf at gmail.com> wrote:
>
>> Hi,
>>
>> in order to be consistent with the latest Cordova changes name, we did
>> apply them (and improved GCM exception handling) to the 0.10.x branch as
>> well. That's the only content of the release:
>> * Cordova registration snippets match the LATEST (0.5.x) plugin
>> * GCM exception handling improved
>>
>> 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/13
>>
>>
>> If you want to test it - it's simple! Just go ahead and use my fork of
>> the repo:
>>
>> rhc app create --no-git <YOUR COOL APP NAME>
>> https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.5
>>
>>
>> Let me know the results of your testing;
>> If I hear nothing bad by Tuesday evening (give it a few more days due to
>> European holidays), the merges will happen on Wednesday
>>
>>
>> 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/20140512/153bfdb3/attachment.html 

From daniel.bevenius at gmail.com  Mon May 12 02:56:42 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 12 May 2014 08:56:42 +0200
Subject: [aerogear-dev] Team meeting
Message-ID: <CAFJm-3EuLJdA1kHQVod7VfgWjo1YkvRnCWcJNgBiwA=fpS+q5Q@mail.gmail.com>

Agenda:
http://oksoclap.com/p/aerogear-team-mgt-201405012
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140512/3552e13c/attachment.html 

From avibelli at redhat.com  Mon May 12 04:04:39 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Mon, 12 May 2014 01:04:39 -0700 (PDT)
Subject: [aerogear-dev] AeroGear-Misc 0.1.2 has been staged
In-Reply-To: <CAAg5f2Qatk46x6AX-ppuGjJcWVaXsdkNaayFewVHqm3BGrsXWw@mail.gmail.com>
References: <CAAg5f2Qatk46x6AX-ppuGjJcWVaXsdkNaayFewVHqm3BGrsXWw@mail.gmail.com>
Message-ID: <1399881879821-7764.post@n5.nabble.com>

Hi Matthias, 
aerogear-misc tag 0.1.2 is correct now, and can be released for me, great!
However I found a couple of issues on other tags/branches:
* tag 0.2.0 has a wrong <scm> configuration inside pom.xml: <tag> should be
0.2.0, not 0.1.2 (but it's already released on Central, maybe we can delete
it after your emails to Sonatype)
* master branch: shouldn't the version be 0.1.3-SNAPSHOT (in case we could
delete 0.2.0 from Maven Central), or 0.2.1-SNAPSHOT?

Thanks
Andrea

Matthias Wessendorf wrote
> Hello,
> 
> to follow up on last weeks issues w/ the release, I have staged the 0.1.2
> version:
> 
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/
> 
> Let me know if that version works, and I will release tomorrow
> 
> -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 .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7764.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Mon May 12 04:19:16 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 12 May 2014 10:19:16 +0200
Subject: [aerogear-dev] AeroGear-Misc 0.1.2 has been staged
In-Reply-To: <1399881879821-7764.post@n5.nabble.com>
References: <CAAg5f2Qatk46x6AX-ppuGjJcWVaXsdkNaayFewVHqm3BGrsXWw@mail.gmail.com>
	<1399881879821-7764.post@n5.nabble.com>
Message-ID: <CAAg5f2TYBs7=vg1PiTBiUXwrVjcV1PshrrtjRsMrj10aGsFpMA@mail.gmail.com>

On Mon, May 12, 2014 at 10:04 AM, Andrea Vibelli <avibelli at redhat.com>wrote:

> Hi Matthias,
> aerogear-misc tag 0.1.2 is correct now, and can be released for me, great!
> However I found a couple of issues on other tags/branches:
> * tag 0.2.0 has a wrong <scm> configuration inside pom.xml: <tag> should be
> 0.2.0, not 0.1.2 (but it's already released on Central, maybe we can delete
> it after your emails to Sonatype)
>

yes - that's just me renaming the old incorrect 0.1.2 tag :-)

I will re-release the 0.2.0 w/ correct SCM including a delete of the
current 0.2.0 tag.


> * master branch: shouldn't the version be 0.1.3-SNAPSHOT (in case we could
> delete 0.2.0 from Maven Central), or 0.2.1-SNAPSHOT?
>

that will happen once we do the re-release of the 0.2.0


-M


>
> Thanks
> Andrea
>
> Matthias Wessendorf wrote
> > Hello,
> >
> > to follow up on last weeks issues w/ the release, I have staged the 0.1.2
> > version:
> >
> >
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/
> >
> > Let me know if that version works, and I will release tomorrow
> >
> > -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 .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7764.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/20140512/ee9890b7/attachment-0001.html 

From avibelli at redhat.com  Mon May 12 04:22:12 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Mon, 12 May 2014 01:22:12 -0700 (PDT)
Subject: [aerogear-dev] AeroGear-Misc 0.1.2 has been staged
In-Reply-To: <CAAg5f2TYBs7=vg1PiTBiUXwrVjcV1PshrrtjRsMrj10aGsFpMA@mail.gmail.com>
References: <CAAg5f2Qatk46x6AX-ppuGjJcWVaXsdkNaayFewVHqm3BGrsXWw@mail.gmail.com>
	<1399881879821-7764.post@n5.nabble.com>
	<CAAg5f2TYBs7=vg1PiTBiUXwrVjcV1PshrrtjRsMrj10aGsFpMA@mail.gmail.com>
Message-ID: <1399882932395-7766.post@n5.nabble.com>

Ok excellent, all fine then!

Thanks!
Andrea


Matthias Wessendorf wrote
> On Mon, May 12, 2014 at 10:04 AM, Andrea Vibelli &lt;

> avibelli@

> &gt;wrote:
> 
>> Hi Matthias,
>> aerogear-misc tag 0.1.2 is correct now, and can be released for me,
>> great!
>> However I found a couple of issues on other tags/branches:
>> * tag 0.2.0 has a wrong 
> <scm>
>  configuration inside pom.xml: 
> <tag>
>  should be
>> 0.2.0, not 0.1.2 (but it's already released on Central, maybe we can
>> delete
>> it after your emails to Sonatype)
>>
> 
> yes - that's just me renaming the old incorrect 0.1.2 tag :-)
> 
> I will re-release the 0.2.0 w/ correct SCM including a delete of the
> current 0.2.0 tag.
> 
> 
>> * master branch: shouldn't the version be 0.1.3-SNAPSHOT (in case we
>> could
>> delete 0.2.0 from Maven Central), or 0.2.1-SNAPSHOT?
>>
> 
> that will happen once we do the re-release of the 0.2.0
> 
> 
> -M
> 
> 
>>
>> Thanks
>> Andrea
>>
>> Matthias Wessendorf wrote
>> > Hello,
>> >
>> > to follow up on last weeks issues w/ the release, I have staged the
>> 0.1.2
>> > version:
>> >
>> >
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/
>> >
>> > Let me know if that version works, and I will release tomorrow
>> >
>> > -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 .jboss
>>
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7764.html
>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> _______________________________________________
>> aerogear-dev mailing list
>> 

> aerogear-dev at .jboss

>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
> 
> 
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev


Matthias Wessendorf wrote
> On Mon, May 12, 2014 at 10:04 AM, Andrea Vibelli &lt;

> avibelli@

> &gt;wrote:
> 
>> Hi Matthias,
>> aerogear-misc tag 0.1.2 is correct now, and can be released for me,
>> great!
>> However I found a couple of issues on other tags/branches:
>> * tag 0.2.0 has a wrong 
> <scm>
>  configuration inside pom.xml: 
> <tag>
>  should be
>> 0.2.0, not 0.1.2 (but it's already released on Central, maybe we can
>> delete
>> it after your emails to Sonatype)
>>
> 
> yes - that's just me renaming the old incorrect 0.1.2 tag :-)
> 
> I will re-release the 0.2.0 w/ correct SCM including a delete of the
> current 0.2.0 tag.
> 
> 
>> * master branch: shouldn't the version be 0.1.3-SNAPSHOT (in case we
>> could
>> delete 0.2.0 from Maven Central), or 0.2.1-SNAPSHOT?
>>
> 
> that will happen once we do the re-release of the 0.2.0
> 
> 
> -M
> 
> 
>>
>> Thanks
>> Andrea
>>
>> Matthias Wessendorf wrote
>> > Hello,
>> >
>> > to follow up on last weeks issues w/ the release, I have staged the
>> 0.1.2
>> > version:
>> >
>> >
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/
>> >
>> > Let me know if that version works, and I will release tomorrow
>> >
>> > -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 .jboss
>>
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7764.html
>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> _______________________________________________
>> aerogear-dev mailing list
>> 

> aerogear-dev at .jboss

>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
> 
> 
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7766.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Mon May 12 04:36:03 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 12 May 2014 10:36:03 +0200
Subject: [aerogear-dev] [UPS] New AdminUI (using Angular.js and Bootstrap)
Message-ID: <CAAg5f2TX2+QGqcAV7bVFL2o4ZmXDHfjUx2DYpFK3XSK3nca7qQ@mail.gmail.com>

Hello,

I just met w/ Erik, Lukas and Sebi on the new AdminUI. Progress (as you can
tell from the commits log, [1]) is very good. Yay!


In the hangout the team agreed on trying to submit an initial PR for
merging the new UI (except Keycloak and Statistics - as they are handled by
different JIRAs), by end of this week.

Further we did decide:
Once that PR has been merged and tested we will ping our friends from
LiveOak (mainly Viliam) to do a review. Based on his review, the team will
apply Viliam's suggestions/PRs.


-Matthias

[1] https://github.com/aerogear/aerogear-unifiedpush-server/commits/angular

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140512/3e129a5c/attachment.html 

From matzew at apache.org  Mon May 12 04:53:28 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 12 May 2014 10:53:28 +0200
Subject: [aerogear-dev] Creating a Cordova Project in Jira
In-Reply-To: <9878038C-DA9F-4235-8694-1A9D01E6EDC8@gmail.com>
References: <CAD_dpu1q1+awYh=Bn1DU4rU-C5qHowDcxvnt68vqxkV5RDrSPw@mail.gmail.com>
	<9878038C-DA9F-4235-8694-1A9D01E6EDC8@gmail.com>
Message-ID: <CAAg5f2QL63uyU8Ub53U64Yr6-LjGDUzZA4KKCh=cCSzWUi9faw@mail.gmail.com>

+1 on AGCORDOVA  (if that name is possible...)



On Wed, Apr 2, 2014 at 11:06 AM, Miiguel Lemos <miguel21op at gmail.com> wrote:

> Yes, of course ;-)
>
> Enviado do meu iPad
>
> No dia 02/04/2014, ?s 08:40, Sebastien Blanc <scm.blanc at gmail.com>
> escreveu:
>
> Hi,
>
> For all the projects we have a specific Project  : AGPUSH, AGJS, AGSEC etc
> ...
> I think it would be nice to have also one for Cordova and I propose :
> AGCORDOVA
>
>
> wdyt ?
>
> JIRA : https://issues.jboss.org/browse/AEROGEAR-1464
>
> _______________________________________________
>
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140512/7035f808/attachment.html 

From matzew at apache.org  Mon May 12 05:10:24 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 12 May 2014 11:10:24 +0200
Subject: [aerogear-dev] [planing] AeroGear Mobile Push 1.0.0 release
Message-ID: <CAAg5f2S_EWXFnc_NpL48Wzos1S-HCDATU=+kmZU+OpH8hbbaUw@mail.gmail.com>

Hello folks!

This summer we will release the AeroGear Mobile Push 1.0.0 to the
community. This 'logical' release will contain a few items (that are all on
their own versioning):

   - UnifiedPush Server
      - including Keycloak integration
      - including statistics around Push messages sent out
   - Client SDKs (for Android, Cordova and iOS)
   - Examples/Quickstarts
      - Simple HelloWorld examples (for Android, Cordova and iOS)
      - more advanced Quickstart (different server integration options
      (E.g. JAvaEE and Spring) + Clients for Android, Cordova and iOS)
   - Openshift Cartridge
   - Documentation

To track these items, I have created a JIRA label "MobilePush-1.0", see
[1]. For new JIRAs that are relevant for this initial community release,
please use that label so that tracking of the items is much easier ;-)

I will update the existing roadmap (yes, the 1.0.0 is already in there)
based on current changes and delay's

Thanks!
Matthias

[1] https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140512/054ffef0/attachment.html 

From tolisemm at gmail.com  Mon May 12 06:21:16 2014
From: tolisemm at gmail.com (tolis emmanouilidis)
Date: Mon, 12 May 2014 13:21:16 +0300
Subject: [aerogear-dev] NotifyingHandler and PushApplication
In-Reply-To: <CAKjsGbuxfD6UMPZKra3ZVfNxrqyW78zdnY8pPHcuobgTA6rguA@mail.gmail.com>
References: <536CD643.1090000@nol-is.de>
	<CAKjsGbuxfD6UMPZKra3ZVfNxrqyW78zdnY8pPHcuobgTA6rguA@mail.gmail.com>
Message-ID: <CAN5SbcbcfLB+qQomAZ4wG2mRvWa8ituQhD7achQvAPoOBy=hTQ@mail.gmail.com>

Titanium uses JavaScript, right? I suppose that you can include custom
JavaScript libraries. So AeroGear JS [1] seems to be the solution in order
to interact with the Unified Push server. You might want to check the
corresponding quickstart [2]

[1]: https://github.com/aerogear/aerogear-js
[2]: https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart

Thanks,
Tolis



2014-05-09 17:39 GMT+03:00 Daniel Passos <daniel at passos.me>:

> Hi Mark,
>
> Thanks for your interest.
>
> Unfortunately we don't have experience with that framework.
>
> Have you looked at our documentations[1][2]? and our examples apps[3][4[
>
> [1] http://aerogear.org/docs/guides/aerogear-android/push/
> [2] http://aerogear.org/docs/guides/aerogear-push-android/
> [3] https://github.com/aerogear/aerogear-android-cookbook
> [4] https://github.com/aerogear/aerogear-push-helloworld
>
> -- Passos
>
>
> On Fri, May 9, 2014 at 10:21 AM, Mark Scholtes <m.scholtes at nol-is.de>wrote:
>
>>  Hi!
>>
>> I want to use the UnifiedPush Server within an androis app. I have set up
>> the server and everything is fine.
>> But now I want to implement the client in the app. I am using Titanium
>> and the Alloy Framework.
>>
>> I don't know how to use the aerogear-android in this environment.
>>
>> Do you have an idea how to solve my problem or is there an easier way to
>> interact with the server?
>>
>> With kind regards
>> Mit freundlichem Gru?
>> i. A. Mark Scholtes
>> ---
>>
>> NOLIS GmbH
>> Sitz Nienburg/Weser
>> Gesch?ftsf?hrer: Uwe Warnecke
>> Registergericht Walsrode - HRB 30797
>>
>> Celler Stra?e 53
>> 31582 Nienburg/Weser
>>
>> Telefon: 0 50 21 / 88 77 555
>> Telefax: 0 50 21 / 88 77 599
>> E-Mail: m.scholtes at nolis.de <//m.scholtes at nolis.de>
>> Internet: http://www.nolis.de
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140512/170fc92e/attachment-0001.html 

From lholmqui at redhat.com  Mon May 12 08:19:50 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 12 May 2014 08:19:50 -0400
Subject: [aerogear-dev] NotifyingHandler and PushApplication
In-Reply-To: <CAN5SbcbcfLB+qQomAZ4wG2mRvWa8ituQhD7achQvAPoOBy=hTQ@mail.gmail.com>
References: <536CD643.1090000@nol-is.de>
	<CAKjsGbuxfD6UMPZKra3ZVfNxrqyW78zdnY8pPHcuobgTA6rguA@mail.gmail.com>
	<CAN5SbcbcfLB+qQomAZ4wG2mRvWa8ituQhD7achQvAPoOBy=hTQ@mail.gmail.com>
Message-ID: <084C238D-BB6B-4C74-9EDF-7DCDA1C503EA@redhat.com>


On May 12, 2014, at 6:21 AM, tolis emmanouilidis <tolisemm at gmail.com> wrote:

> Titanium uses JavaScript, right? I suppose that you can include custom JavaScript libraries. So AeroGear JS [1] seems to be the solution in order to interact with the Unified Push server. You might want to check the corresponding quickstart [2]

this might work for communication to the UPS,  but i?m not sure how it would be able to interact with GCM

> 
> [1]: https://github.com/aerogear/aerogear-js
> [2]: https://github.com/aerogear/aerogear-simplepush-unifiedpush-quickstart
> 
> Thanks,
> Tolis
>   
> 
> 
> 2014-05-09 17:39 GMT+03:00 Daniel Passos <daniel at passos.me>:
> Hi Mark,
> 
> Thanks for your interest.
> 
> Unfortunately we don't have experience with that framework.
> 
> Have you looked at our documentations[1][2]? and our examples apps[3][4[
> 
> [1] http://aerogear.org/docs/guides/aerogear-android/push/
> [2] http://aerogear.org/docs/guides/aerogear-push-android/
> [3] https://github.com/aerogear/aerogear-android-cookbook
> [4] https://github.com/aerogear/aerogear-push-helloworld
> 
> -- Passos
> 
> 
> On Fri, May 9, 2014 at 10:21 AM, Mark Scholtes <m.scholtes at nol-is.de> wrote:
> Hi!
> 
> I want to use the UnifiedPush Server within an androis app. I have set up the server and everything is fine.
> But now I want to implement the client in the app. I am using Titanium and the Alloy Framework.
> 
> I don't know how to use the aerogear-android in this environment.
> 
> Do you have an idea how to solve my problem or is there an easier way to interact with the server?
> 
> With kind regards
> Mit freundlichem Gru?
> i. A. Mark Scholtes
> ---
> 
> NOLIS GmbH
> Sitz Nienburg/Weser
> Gesch?ftsf?hrer: Uwe Warnecke
> Registergericht Walsrode - HRB 30797
> 
> Celler Stra?e 53
> 31582 Nienburg/Weser
> 
> Telefon: 0 50 21 / 88 77 555
> Telefax: 0 50 21 / 88 77 599
> E-Mail: m.scholtes at nolis.de
> Internet: http://www.nolis.de
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140512/28183214/attachment.html 

From daniel.bevenius at gmail.com  Mon May 12 10:12:01 2014
From: daniel.bevenius at gmail.com (danielbevenius)
Date: Mon, 12 May 2014 07:12:01 -0700 (PDT)
Subject: [aerogear-dev] Team meeting
In-Reply-To: <CAFJm-3EuLJdA1kHQVod7VfgWjo1YkvRnCWcJNgBiwA=fpS+q5Q@mail.gmail.com>
References: <CAFJm-3EuLJdA1kHQVod7VfgWjo1YkvRnCWcJNgBiwA=fpS+q5Q@mail.gmail.com>
Message-ID: <1399903921076-7772.post@n5.nabble.com>

Meeting notes:


Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-12-13.44.html

Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-12-13.44.txt

Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-12-13.44.log.html



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Team-meeting-tp7763p7772.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From lholmqui at redhat.com  Mon May 12 11:18:16 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 12 May 2014 11:18:16 -0400
Subject: [aerogear-dev] AeroGear JS 1.5.0 pre-release
Message-ID: <5581DC26-F780-4012-BB8C-FA1AE5E4E3B4@redhat.com>

Hey peeps,

this week we will be releasing AeroGear.js 1.5.0.

Here is a link to the release notes

https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12313725&version=12324171


There is still 1 open issue,  https://issues.jboss.org/browse/AGJS-41 , but shouldn?t affect the main repo since it is just a cookbook recipe


i?ve tagged a 1.5.0-dev release, https://github.com/aerogear/aerogear-js/tree/1.5.0-dev, which will be replaced once we do the official release

If you would like to check it out,  go for it.  We will plan to release wednesday


-Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140512/6ca56b1b/attachment.html 

From m.scholtes at nol-is.de  Mon May 12 10:02:35 2014
From: m.scholtes at nol-is.de (Mark Scholtes)
Date: Mon, 12 May 2014 16:02:35 +0200
Subject: [aerogear-dev] UnifiedPush Server (0.10.2) Error in Response
In-Reply-To: <536CD643.1090000@nol-is.de>
References: <536CD643.1090000@nol-is.de>
Message-ID: <5370D47B.1050008@nol-is.de>

Hi!

I want to register a device, but the response from the unified push 
server seems to be broken:

!!org.jboss.aerogear.unifiedpush.model.InstallationImpl
alias: juntian
categories: !!set {tagging: null}
deviceToken: b3baa6597da6abe8
deviceType: Full Android on x86 Emulator
enabled: true
id: b62be19e-62b3-4b80-bbbb-a136eee34921
operatingSystem: android
osVersion: 2.3.7
platform: android
simplePushEndpoint: null


This is not a valid JSON.

I was testing on OpenShift. UnifiedPush Server (0.10.2)
https://aerogear-madaneus.rhcloud.com


With kind regards
Mit freundlichem Gru?
i. A. Mark Scholtes
---

NOLIS GmbH
Sitz Nienburg/Weser
Gesch?ftsf?hrer: Uwe Warnecke
Registergericht Walsrode - HRB 30797

Celler Stra?e 53
31582 Nienburg/Weser

Telefon: 0 50 21 / 88 77 555
Telefax: 0 50 21 / 88 77 599
E-Mail: m.scholtes at nolis.de <mailto://m.scholtes at nolis.de>
Internet: http://www.nolis.de



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140512/b0590121/attachment.html 

From matzew at apache.org  Tue May 13 02:14:40 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 13 May 2014 08:14:40 +0200
Subject: [aerogear-dev] AeroGear-Misc 0.1.2 has been staged
In-Reply-To: <1399882932395-7766.post@n5.nabble.com>
References: <CAAg5f2Qatk46x6AX-ppuGjJcWVaXsdkNaayFewVHqm3BGrsXWw@mail.gmail.com>
	<1399881879821-7764.post@n5.nabble.com>
	<CAAg5f2TYBs7=vg1PiTBiUXwrVjcV1PshrrtjRsMrj10aGsFpMA@mail.gmail.com>
	<1399882932395-7766.post@n5.nabble.com>
Message-ID: <CAAg5f2RXDhLA3REO8Ja9Hkhu-gkaZ+diWGhbT3=yCCNetoxe9w@mail.gmail.com>

Andrea,

I have clicked the 'release' button - should be on Maven Central w/in one
day..

-M


On Mon, May 12, 2014 at 10:22 AM, Andrea Vibelli <avibelli at redhat.com>wrote:

> Ok excellent, all fine then!
>
> Thanks!
> Andrea
>
>
> Matthias Wessendorf wrote
> > On Mon, May 12, 2014 at 10:04 AM, Andrea Vibelli &lt;
>
> > avibelli@
>
> > &gt;wrote:
> >
> >> Hi Matthias,
> >> aerogear-misc tag 0.1.2 is correct now, and can be released for me,
> >> great!
> >> However I found a couple of issues on other tags/branches:
> >> * tag 0.2.0 has a wrong
> > <scm>
> >  configuration inside pom.xml:
> > <tag>
> >  should be
> >> 0.2.0, not 0.1.2 (but it's already released on Central, maybe we can
> >> delete
> >> it after your emails to Sonatype)
> >>
> >
> > yes - that's just me renaming the old incorrect 0.1.2 tag :-)
> >
> > I will re-release the 0.2.0 w/ correct SCM including a delete of the
> > current 0.2.0 tag.
> >
> >
> >> * master branch: shouldn't the version be 0.1.3-SNAPSHOT (in case we
> >> could
> >> delete 0.2.0 from Maven Central), or 0.2.1-SNAPSHOT?
> >>
> >
> > that will happen once we do the re-release of the 0.2.0
> >
> >
> > -M
> >
> >
> >>
> >> Thanks
> >> Andrea
> >>
> >> Matthias Wessendorf wrote
> >> > Hello,
> >> >
> >> > to follow up on last weeks issues w/ the release, I have staged the
> >> 0.1.2
> >> > version:
> >> >
> >> >
> >>
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/
> >> >
> >> > Let me know if that version works, and I will release tomorrow
> >> >
> >> > -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 .jboss
> >>
> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7764.html
> >> Sent from the aerogear-dev mailing list archive at Nabble.com.
> >> _______________________________________________
> >> aerogear-dev mailing list
> >>
>
> > aerogear-dev at .jboss
>
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
>
> > aerogear-dev at .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> Matthias Wessendorf wrote
> > On Mon, May 12, 2014 at 10:04 AM, Andrea Vibelli &lt;
>
> > avibelli@
>
> > &gt;wrote:
> >
> >> Hi Matthias,
> >> aerogear-misc tag 0.1.2 is correct now, and can be released for me,
> >> great!
> >> However I found a couple of issues on other tags/branches:
> >> * tag 0.2.0 has a wrong
> > <scm>
> >  configuration inside pom.xml:
> > <tag>
> >  should be
> >> 0.2.0, not 0.1.2 (but it's already released on Central, maybe we can
> >> delete
> >> it after your emails to Sonatype)
> >>
> >
> > yes - that's just me renaming the old incorrect 0.1.2 tag :-)
> >
> > I will re-release the 0.2.0 w/ correct SCM including a delete of the
> > current 0.2.0 tag.
> >
> >
> >> * master branch: shouldn't the version be 0.1.3-SNAPSHOT (in case we
> >> could
> >> delete 0.2.0 from Maven Central), or 0.2.1-SNAPSHOT?
> >>
> >
> > that will happen once we do the re-release of the 0.2.0
> >
> >
> > -M
> >
> >
> >>
> >> Thanks
> >> Andrea
> >>
> >> Matthias Wessendorf wrote
> >> > Hello,
> >> >
> >> > to follow up on last weeks issues w/ the release, I have staged the
> >> 0.1.2
> >> > version:
> >> >
> >> >
> >>
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/
> >> >
> >> > Let me know if that version works, and I will release tomorrow
> >> >
> >> > -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 .jboss
> >>
> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7764.html
> >> Sent from the aerogear-dev mailing list archive at Nabble.com.
> >> _______________________________________________
> >> aerogear-dev mailing list
> >>
>
> > aerogear-dev at .jboss
>
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> >
> > _______________________________________________
> > aerogear-dev mailing list
>
> > aerogear-dev at .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7766.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/20140513/a26bcde4/attachment-0001.html 

From avibelli at redhat.com  Tue May 13 02:55:04 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Mon, 12 May 2014 23:55:04 -0700 (PDT)
Subject: [aerogear-dev] AeroGear-Misc 0.1.2 has been staged
In-Reply-To: <CAAg5f2RXDhLA3REO8Ja9Hkhu-gkaZ+diWGhbT3=yCCNetoxe9w@mail.gmail.com>
References: <CAAg5f2Qatk46x6AX-ppuGjJcWVaXsdkNaayFewVHqm3BGrsXWw@mail.gmail.com>
	<1399881879821-7764.post@n5.nabble.com>
	<CAAg5f2TYBs7=vg1PiTBiUXwrVjcV1PshrrtjRsMrj10aGsFpMA@mail.gmail.com>
	<1399882932395-7766.post@n5.nabble.com>
	<CAAg5f2RXDhLA3REO8Ja9Hkhu-gkaZ+diWGhbT3=yCCNetoxe9w@mail.gmail.com>
Message-ID: <1399964104201-7776.post@n5.nabble.com>

Excellent, thanks Matthias!
Andrea


Matthias Wessendorf wrote
> Andrea,
> 
> I have clicked the 'release' button - should be on Maven Central w/in one
> day..
> 
> -M
> 
> 
> On Mon, May 12, 2014 at 10:22 AM, Andrea Vibelli &lt;

> avibelli@

> &gt;wrote:
> 
>> Ok excellent, all fine then!
>>
>> Thanks!
>> Andrea
>>
>>
>> Matthias Wessendorf wrote
>> > On Mon, May 12, 2014 at 10:04 AM, Andrea Vibelli &lt;
>>
>> > avibelli@
>>
>> > &gt;wrote:
>> >
>> >> Hi Matthias,
>> >> aerogear-misc tag 0.1.2 is correct now, and can be released for me,
>> >> great!
>> >> However I found a couple of issues on other tags/branches:
>> >> * tag 0.2.0 has a wrong
>> > 
> <scm>
>> >  configuration inside pom.xml:
>> > 
> <tag>
>> >  should be
>> >> 0.2.0, not 0.1.2 (but it's already released on Central, maybe we can
>> >> delete
>> >> it after your emails to Sonatype)
>> >>
>> >
>> > yes - that's just me renaming the old incorrect 0.1.2 tag :-)
>> >
>> > I will re-release the 0.2.0 w/ correct SCM including a delete of the
>> > current 0.2.0 tag.
>> >
>> >
>> >> * master branch: shouldn't the version be 0.1.3-SNAPSHOT (in case we
>> >> could
>> >> delete 0.2.0 from Maven Central), or 0.2.1-SNAPSHOT?
>> >>
>> >
>> > that will happen once we do the re-release of the 0.2.0
>> >
>> >
>> > -M
>> >
>> >
>> >>
>> >> Thanks
>> >> Andrea
>> >>
>> >> Matthias Wessendorf wrote
>> >> > Hello,
>> >> >
>> >> > to follow up on last weeks issues w/ the release, I have staged the
>> >> 0.1.2
>> >> > version:
>> >> >
>> >> >
>> >>
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/
>> >> >
>> >> > Let me know if that version works, and I will release tomorrow
>> >> >
>> >> > -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 .jboss
>> >>
>> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7764.html
>> >> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >>
>>
>> > aerogear-dev at .jboss
>>
>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>
>> >
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>>
>> > aerogear-dev at .jboss
>>
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> Matthias Wessendorf wrote
>> > On Mon, May 12, 2014 at 10:04 AM, Andrea Vibelli &lt;
>>
>> > avibelli@
>>
>> > &gt;wrote:
>> >
>> >> Hi Matthias,
>> >> aerogear-misc tag 0.1.2 is correct now, and can be released for me,
>> >> great!
>> >> However I found a couple of issues on other tags/branches:
>> >> * tag 0.2.0 has a wrong
>> > 
> <scm>
>> >  configuration inside pom.xml:
>> > 
> <tag>
>> >  should be
>> >> 0.2.0, not 0.1.2 (but it's already released on Central, maybe we can
>> >> delete
>> >> it after your emails to Sonatype)
>> >>
>> >
>> > yes - that's just me renaming the old incorrect 0.1.2 tag :-)
>> >
>> > I will re-release the 0.2.0 w/ correct SCM including a delete of the
>> > current 0.2.0 tag.
>> >
>> >
>> >> * master branch: shouldn't the version be 0.1.3-SNAPSHOT (in case we
>> >> could
>> >> delete 0.2.0 from Maven Central), or 0.2.1-SNAPSHOT?
>> >>
>> >
>> > that will happen once we do the re-release of the 0.2.0
>> >
>> >
>> > -M
>> >
>> >
>> >>
>> >> Thanks
>> >> Andrea
>> >>
>> >> Matthias Wessendorf wrote
>> >> > Hello,
>> >> >
>> >> > to follow up on last weeks issues w/ the release, I have staged the
>> >> 0.1.2
>> >> > version:
>> >> >
>> >> >
>> >>
>> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/
>> >> >
>> >> > Let me know if that version works, and I will release tomorrow
>> >> >
>> >> > -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 .jboss
>> >>
>> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7764.html
>> >> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >>
>>
>> > aerogear-dev at .jboss
>>
>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>
>> >
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>>
>> > aerogear-dev at .jboss
>>
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7766.html
>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> _______________________________________________
>> aerogear-dev mailing list
>> 

> aerogear-dev at .jboss

>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
> 
> 
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7776.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From edewit at redhat.com  Tue May 13 02:59:48 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 13 May 2014 08:59:48 +0200
Subject: [aerogear-dev] UnifiedPush Server (0.10.2) Error in Response
In-Reply-To: <5370D47B.1050008@nol-is.de>
References: <536CD643.1090000@nol-is.de> <5370D47B.1050008@nol-is.de>
Message-ID: <19A40F75-10FA-4C35-BEB3-6B8152EA6A1D@redhat.com>

Hi Mark,

Thanks for trying out our UnifiedPush server, could you please describe what you have done so that we could reproduce it? I?ve just tested with a curl request, but that seems to work still.

curl -u "40997720-b901-4c75-b49e-b19fe63e6207:d0418812-1150-4697-b268-7d614c4a6b81" -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{ "deviceToken" : "BPA91bHpbMXepp4odlb20vYOv0gQyNIyFu2X3OXR3TjqR8qecgWivima_UiLPFgUBs_10Nys2TUwUyWlixrIta35NXW-5Z85OdXcbb_3s3p0qaa_a7NpFlaX9GpidK_BdQNMsx2gX8BrE4Uw7s22nPCcEn1U1_mo-T6hcF5unYt965PDwRTRss7", "categories" : ["foo", "d"]}' http://localhost:8080/ag-push/rest/registry/device

{"id":"6d96fb2f-71be-4c8c-b5c0-d10648336a0c","enabled":true,"deviceToken":"BPA91bHpbMXepp4odlb20vYOv0gQyNIyFu2X3OXR3TjqR8qecgWivima_UiLPFgUBs_10Nys2TUwUyWlixrIta35NXW-5Z85OdXcbb_3s3p0qaa_a7NpFlaX9GpidK_BdQNMsx2gX8BrE4Uw7s22nPCcEn1U1_mo-T6hcF5unYt965PDwRTRss7","deviceType":null,"operatingSystem":null,"osVersion":null,"alias":null,"categories":["d","foo"],"platform":"android","simplePushEndpoint":null,"variantType":null}

Cheers,
	Erik Jan

On 12 May,2014, at 16:02 , Mark Scholtes <m.scholtes at nol-is.de> wrote:

> Hi!
> 
> I want to register a device, but the response from the unified push server seems to be broken:
> 
> !!org.jboss.aerogear.unifiedpush.model.InstallationImpl
> alias: juntian
> categories: !!set {tagging: null}
> deviceToken: b3baa6597da6abe8
> deviceType: Full Android on x86 Emulator
> enabled: true
> id: b62be19e-62b3-4b80-bbbb-a136eee34921
> operatingSystem: android
> osVersion: 2.3.7
> platform: android
> simplePushEndpoint: null
> 
> 
> This is not a valid JSON.
> 
> I was testing on OpenShift. UnifiedPush Server (0.10.2)
> https://aerogear-madaneus.rhcloud.com
> 
> 
> With kind regards
> Mit freundlichem Gru?
> i. A. Mark Scholtes
> ---
> 
> NOLIS GmbH
> Sitz Nienburg/Weser
> Gesch?ftsf?hrer: Uwe Warnecke
> Registergericht Walsrode - HRB 30797
> 
> Celler Stra?e 53
> 31582 Nienburg/Weser
> 
> Telefon: 0 50 21 / 88 77 555
> Telefax: 0 50 21 / 88 77 599
> E-Mail: m.scholtes at nolis.de
> Internet: http://www.nolis.de
> 
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140513/2c6f5547/attachment.html 

From matzew at apache.org  Tue May 13 03:41:22 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 13 May 2014 09:41:22 +0200
Subject: [aerogear-dev] AeroGear-Misc 0.1.2 has been staged
In-Reply-To: <1399964104201-7776.post@n5.nabble.com>
References: <CAAg5f2Qatk46x6AX-ppuGjJcWVaXsdkNaayFewVHqm3BGrsXWw@mail.gmail.com>
	<1399881879821-7764.post@n5.nabble.com>
	<CAAg5f2TYBs7=vg1PiTBiUXwrVjcV1PshrrtjRsMrj10aGsFpMA@mail.gmail.com>
	<1399882932395-7766.post@n5.nabble.com>
	<CAAg5f2RXDhLA3REO8Ja9Hkhu-gkaZ+diWGhbT3=yCCNetoxe9w@mail.gmail.com>
	<1399964104201-7776.post@n5.nabble.com>
Message-ID: <CAAg5f2Q1MK79tFHuaAENjXAtcH+ZVDbYttQV1dJwiyEVF2WC6Q@mail.gmail.com>

I will start re-release of 0.2.0 later today



On Tuesday, May 13, 2014, Andrea Vibelli <avibelli at redhat.com> wrote:

> Excellent, thanks Matthias!
> Andrea
>
>
> Matthias Wessendorf wrote
> > Andrea,
> >
> > I have clicked the 'release' button - should be on Maven Central w/in one
> > day..
> >
> > -M
> >
> >
> > On Mon, May 12, 2014 at 10:22 AM, Andrea Vibelli &lt;
>
> > avibelli@
>
> > &gt;wrote:
> >
> >> Ok excellent, all fine then!
> >>
> >> Thanks!
> >> Andrea
> >>
> >>
> >> Matthias Wessendorf wrote
> >> > On Mon, May 12, 2014 at 10:04 AM, Andrea Vibelli &lt;
> >>
> >> > avibelli@
> >>
> >> > &gt;wrote:
> >> >
> >> >> Hi Matthias,
> >> >> aerogear-misc tag 0.1.2 is correct now, and can be released for me,
> >> >> great!
> >> >> However I found a couple of issues on other tags/branches:
> >> >> * tag 0.2.0 has a wrong
> >> >
> > <scm>
> >> >  configuration inside pom.xml:
> >> >
> > <tag>
> >> >  should be
> >> >> 0.2.0, not 0.1.2 (but it's already released on Central, maybe we can
> >> >> delete
> >> >> it after your emails to Sonatype)
> >> >>
> >> >
> >> > yes - that's just me renaming the old incorrect 0.1.2 tag :-)
> >> >
> >> > I will re-release the 0.2.0 w/ correct SCM including a delete of the
> >> > current 0.2.0 tag.
> >> >
> >> >
> >> >> * master branch: shouldn't the version be 0.1.3-SNAPSHOT (in case we
> >> >> could
> >> >> delete 0.2.0 from Maven Central), or 0.2.1-SNAPSHOT?
> >> >>
> >> >
> >> > that will happen once we do the re-release of the 0.2.0
> >> >
> >> >
> >> > -M
> >> >
> >> >
> >> >>
> >> >> Thanks
> >> >> Andrea
> >> >>
> >> >> Matthias Wessendorf wrote
> >> >> > Hello,
> >> >> >
> >> >> > to follow up on last weeks issues w/ the release, I have staged the
> >> >> 0.1.2
> >> >> > version:
> >> >> >
> >> >> >
> >> >>
> >>
> http://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3196/
> >> >> >
> >> >> > Let me know if that version works, and I will release tomorrow
> >> >> >
> >> >> > -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 .jboss
> >> >>
> >> >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7764.html
> >> >> Sent from the aerogear-dev mailing list archive at Nabble.com.
> >> >> _______________________________________________
> >> >> aerogear-dev mailing list
> >> >>
> >>
> >> > aerogear-dev at .jboss
> >>
> >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Matthias Wessendorf
> >> >
> >> > blog: http://matthiaswessendorf.wordpress.com/
> >> > sessions: http://www.slideshare.net/mwessendo<http://www.slideshare.net/mwessendorf>View
> this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Misc-0-1-2-has-been-staged-tp7759p7776.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <javascript:;>
> 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/20140513/d3949b24/attachment.html 

From hbons at redhat.com  Tue May 13 04:47:14 2014
From: hbons at redhat.com (Hylke Bons)
Date: Tue, 13 May 2014 09:47:14 +0100
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
Message-ID: <5371DC12.8070308@redhat.com>

Hello,

Depending on the use case, it may even deserve its own spot in the 
sidebar. Like already mentioned on the thread, it's better to keep the 
number of items there fixed. We may have have several entry points to 
the logs, and an overview of some statistics can be useful as a landing 
page before going into "Applications".

Let's step back for a moment before looking at the UI: What are we 
trying to solve by providing a log?

- Let administrators know everything is going well? (or, that there was 
a problem?)
- Looking at resources used? Bandwidth, costs?
- App adoption/growth numbers over time? How well is my app doing?

I'm not sure about the technical possibilities. Thoughts?

Thanks,

Hylke



On 07/05/2014 10:54, Matthias Wessendorf wrote:
> Hi,
>
> as discussed , we need some sort of 'stats' around push, like:
> * time of sending
> * receivers (e.g. categories, alias ?)
> * content/payload of the message
> * could be sent out to APNs/GCM
>
>
> But, where, or how to add this ?
> My current thought is:
>
> When a user did select an "Application", he enters the "Application 
> Details Page" (see [1]), now here, on the sidebar (see [2]) he would 
> see the "Notifications" icon.
>
> Clicking on that  "Notifications" icon, would give you a new page, 
> that contains the "Send Notifications..." button (currently located in 
> [1]), and a table of all the push messages that were sent out for the 
> _current_ selected Application.
>
> Any thoughts ?
>
> -Matthias
>
> [1] 
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
> [2] 
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>
>
> -- 
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140513/e2182702/attachment-0001.html 

From hbons at redhat.com  Tue May 13 04:49:36 2014
From: hbons at redhat.com (Hylke Bons)
Date: Tue, 13 May 2014 09:49:36 +0100
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CAD_dpu3UYKcTEdyz5ugK1fojyPQjddEnM7W3FR8dh=HEhHj_GQ@mail.gmail.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>	<CAAg5f2RMHB019npB11wmGtpXMWZSHwHN=MnJKe8XZ+8oTexXgg@mail.gmail.com>
	<CAD_dpu3UYKcTEdyz5ugK1fojyPQjddEnM7W3FR8dh=HEhHj_GQ@mail.gmail.com>
Message-ID: <5371DCA0.8070602@redhat.com>

On 07/05/2014 17:50, Sebastien Blanc wrote:
>
> Sounds good but just not sure to also migrate the "Send Notifications 
> ..."  feature there. On one side it makes sense to have it there but 
> on the other hand it's also nice to have a direct access to this 
> feature when you are on the application detail page. Other point : 
> maybe when we will introduce roles, some might not have the rights to 
> check the stats but still have the right to send a test message.
>
> So, maybe we can duplicate the "Send Notifications ..." button and 
> keeping it also on the application detail page, wdyt ?
>
>

Yes, this is what Matthias and I talked about as well. It would be good 
to have a access to this functionality on the top level as well as in 
the context of the Application Details page.

Hylke



>
>     any thoughts ?
>
>
>     -Matthias
>
>
>         Any thoughts ?
>
>         -Matthias
>
>         [1]
>         https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>         [2]
>         https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>
>
>         -- 
>         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 <mailto:aerogear-dev at lists.jboss.org>
>     https://lists.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/20140513/c8a6d1eb/attachment.html 

From jbalunas at redhat.com  Tue May 13 14:19:57 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Tue, 13 May 2014 14:19:57 -0400
Subject: [aerogear-dev] Creating a Cordova Project in Jira
In-Reply-To: <CAAg5f2QL63uyU8Ub53U64Yr6-LjGDUzZA4KKCh=cCSzWUi9faw@mail.gmail.com>
References: <CAD_dpu1q1+awYh=Bn1DU4rU-C5qHowDcxvnt68vqxkV5RDrSPw@mail.gmail.com>
	<9878038C-DA9F-4235-8694-1A9D01E6EDC8@gmail.com>
	<CAAg5f2QL63uyU8Ub53U64Yr6-LjGDUzZA4KKCh=cCSzWUi9faw@mail.gmail.com>
Message-ID: <3ED44151-4C60-49F4-9E57-0EDBB62C7E42@redhat.com>

I just created the jira project AGCORDOVA for us and updated the jira - https://issues.jboss.org/browse/AEROGEAR-1464

Erik - I assigned it to you so that the proper component, and versions can be added as needed.  

On May 12, 2014, at 4:53 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> +1 on AGCORDOVA  (if that name is possible...)
> 
> 
> 
> On Wed, Apr 2, 2014 at 11:06 AM, Miiguel Lemos <miguel21op at gmail.com> wrote:
> Yes, of course ;-)
> 
> Enviado do meu iPad
> 
> No dia 02/04/2014, ?s 08:40, Sebastien Blanc <scm.blanc at gmail.com> escreveu:
> 
>> Hi,
>> 
>> For all the projects we have a specific Project  : AGPUSH, AGJS, AGSEC etc ...
>> I think it would be nice to have also one for Cordova and I propose : AGCORDOVA
>> 
>> 
>> wdyt ? 
>> 
>> JIRA : https://issues.jboss.org/browse/AEROGEAR-1464
>> _______________________________________________
>> 
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140513/bcbd5213/attachment.html 

From jbalunas at redhat.com  Tue May 13 16:23:18 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Tue, 13 May 2014 16:23:18 -0400
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <5371DC12.8070308@redhat.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
Message-ID: <88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>

Wanted to chime in here.  The overall goal of the metrics/stats imo, is around letting developers/administrators know what is happening with the server.  Messages in/out, registrations, etc....  This will also help new developers see activity and do some basic debugging if devices fail to register or messages fail to send.  

Maybe in the future we'll get into more analytics, resource usage type stuff but for Mobile Push 1.0 I think this is overkill.  For example I would not expect us to store this data over 30 days or so, and have viewing options like "last hour", "last 24 hours", "yesterday", "last 7 days", etc...

Building on what Matthias posted below, here are some breakdowns of stats we could/should track:

Registration:
-- Device registered with [x,y,z] metadata
-- Device removed with [x,y,z] metadata 

Messages:
-- Push request <timestamp-id> received from [ip] with [x,y,z] metadata
-- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS, CD GCM, etc...]
-- Push request <timestamp-id> had foo errors : details

These would all have app and variant info as part of the metadata so they can filtered/broken down as needed.

This should give us a great base for all kinds of table and chart views.
-- Registrations over time for the server, specific app, specific variant
-- Messages over time for the server, specific app, specific variant
-- Table of the above if feasible :-)

Obviously we may need to scale down as needed, and discuss more, but this is what I was thinking about.

Thoughts?


On May 13, 2014, at 4:47 AM, Hylke Bons <hbons at redhat.com> wrote:

> Hello,
> 
> Depending on the use case, it may even deserve its own spot in the sidebar. Like already mentioned on the thread, it's better to keep the number of items there fixed. We may have have several entry points to the logs, and an overview of some statistics can be useful as a landing page before going into "Applications".
> 
> Let's step back for a moment before looking at the UI: What are we trying to solve by providing a log?
> 
> - Let administrators know everything is going well? (or, that there was a problem?)
> - Looking at resources used? Bandwidth, costs?
> - App adoption/growth numbers over time? How well is my app doing?
> 
> I'm not sure about the technical possibilities. Thoughts?
> 
> Thanks,
> 
> Hylke
> 
> 
> 
> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>> Hi,
>> 
>> as discussed , we need some sort of 'stats' around push, like:
>> * time of sending
>> * receivers (e.g. categories, alias ?)
>> * content/payload of the message
>> * could be sent out to APNs/GCM
>> 
>> 
>> But, where, or how to add this ? 
>> My current thought is:
>> 
>> When a user did select an "Application", he enters the "Application Details Page" (see [1]), now here, on the sidebar (see [2]) he would see the "Notifications" icon.
>> 
>> Clicking on that  "Notifications" icon, would give you a new page, that contains the "Send Notifications..." button (currently located in [1]), and a table of all the push messages that were sent out for the _current_ selected Application.
>> 
>> Any thoughts ? 
>> 
>> -Matthias
>> 
>> [1] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>> [2] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140513/11410ea4/attachment-0001.html 

From jbalunas at redhat.com  Tue May 13 16:25:23 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Tue, 13 May 2014 16:25:23 -0400
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
	<88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
Message-ID: <7F8BC7FF-6CB4-43D6-8313-DD22165AF2DC@redhat.com>

Oh, and I also like the idea of the side bar always being the same and giving the users a simple place to get this info.  

It might be possible to "pre-load" the display based on the URL as well so we could have linkable views with context when drilling down - although that might be a better upgrade in the future :-)

On May 13, 2014, at 4:23 PM, Jay Balunas <jbalunas at redhat.com> wrote:

> Wanted to chime in here.  The overall goal of the metrics/stats imo, is around letting developers/administrators know what is happening with the server.  Messages in/out, registrations, etc....  This will also help new developers see activity and do some basic debugging if devices fail to register or messages fail to send.  
> 
> Maybe in the future we'll get into more analytics, resource usage type stuff but for Mobile Push 1.0 I think this is overkill.  For example I would not expect us to store this data over 30 days or so, and have viewing options like "last hour", "last 24 hours", "yesterday", "last 7 days", etc...
> 
> Building on what Matthias posted below, here are some breakdowns of stats we could/should track:
> 
> Registration:
> -- Device registered with [x,y,z] metadata
> -- Device removed with [x,y,z] metadata 
> 
> Messages:
> -- Push request <timestamp-id> received from [ip] with [x,y,z] metadata
> -- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS, CD GCM, etc...]
> -- Push request <timestamp-id> had foo errors : details
> 
> These would all have app and variant info as part of the metadata so they can filtered/broken down as needed.
> 
> This should give us a great base for all kinds of table and chart views.
> -- Registrations over time for the server, specific app, specific variant
> -- Messages over time for the server, specific app, specific variant
> -- Table of the above if feasible :-)
> 
> Obviously we may need to scale down as needed, and discuss more, but this is what I was thinking about.
> 
> Thoughts?
> 
> 
> On May 13, 2014, at 4:47 AM, Hylke Bons <hbons at redhat.com> wrote:
> 
>> Hello,
>> 
>> Depending on the use case, it may even deserve its own spot in the sidebar. Like already mentioned on the thread, it's better to keep the number of items there fixed. We may have have several entry points to the logs, and an overview of some statistics can be useful as a landing page before going into "Applications".
>> 
>> Let's step back for a moment before looking at the UI: What are we trying to solve by providing a log?
>> 
>> - Let administrators know everything is going well? (or, that there was a problem?)
>> - Looking at resources used? Bandwidth, costs?
>> - App adoption/growth numbers over time? How well is my app doing?
>> 
>> I'm not sure about the technical possibilities. Thoughts?
>> 
>> Thanks,
>> 
>> Hylke
>> 
>> 
>> 
>> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>>> Hi,
>>> 
>>> as discussed , we need some sort of 'stats' around push, like:
>>> * time of sending
>>> * receivers (e.g. categories, alias ?)
>>> * content/payload of the message
>>> * could be sent out to APNs/GCM
>>> 
>>> 
>>> But, where, or how to add this ? 
>>> My current thought is:
>>> 
>>> When a user did select an "Application", he enters the "Application Details Page" (see [1]), now here, on the sidebar (see [2]) he would see the "Notifications" icon.
>>> 
>>> Clicking on that  "Notifications" icon, would give you a new page, that contains the "Send Notifications..." button (currently located in [1]), and a table of all the push messages that were sent out for the _current_ selected Application.
>>> 
>>> Any thoughts ? 
>>> 
>>> -Matthias
>>> 
>>> [1] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>>> [2] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>>> 
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.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/20140513/570381da/attachment.html 

From matzew at apache.org  Wed May 14 03:10:24 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 14 May 2014 09:10:24 +0200
Subject: [aerogear-dev] Keycloak integration
In-Reply-To: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
References: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
Message-ID: <CAAg5f2QQpkXSv7NBbC02=FqgbHt3GTQNSk9-KcWOZL-siS7JEQ@mail.gmail.com>

Hello,

here is an update on the integration: Bill did some updates to his example
template and worked on more things inside of Keycloak for a better
integration.

Yesterday, I used his example work and applied it to our UPS:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration


There is now an 'auth-server' module which produces a WAR (that also
contains an AeroGear theme), to be deployed to the AS:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration/auth-server


The 'server' module is using a ContextListener for the configuration work,
instead of the previous keycloak.json file:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-two-war-integration/server/src/main/java/org/jboss/aerogear/unifiedpush/keycloak/BootstrapListener.java

Deploying the two WARs (auth before ups) will show the integration
(admin:admin is the initial password).

IMO this is a huge step towards a proper Keycloak integration, but some
items are still open:
- nicer config (using his testrealm.json inside of the auth-server)
- user/roles mgmt
- integration w/ the new UI
- ...

When Bruno is back, the work on this branch will continue.

That's it for now.

-Matthias






On Tue, May 6, 2014 at 11:49 AM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hello folks!
>
> Bill Burk was helping on the Keycloak front and besides fixing related
> items on the Keycloak server, he also created an example that we can use as
> a template for the actual integration. See [1]
>
> In the past, Bruno and I did integrate w/ an external Keycloak server (see
> [2]), and we did include the keycloak.json file (See [3]). Thanks to Bill's
> work on Keycloak, the 'protected app' no longer needs that, see [4].
> Also there is no more the need to customize the Keycloak Rest Application
> (Stian and I did look into that as well).
>
>
> Good news: This means the UPS can stay as it is -> no need to change
> internals (e.g. the 'bundle all in one WAR file' did force us to change our
> '/rest' URLs, as Keycloak uses them, see [5]).
>
> Inside of our 'modular' Keycloak branch (see [2] again), we can apply the
> work from Bill:
> * our current 'server' module will use a listener similar to [4]
> * create a "ups-auth" module similar to [6]
>
> On the 'ups-auth module' there is one area where we need to have some
> future improvement:
> * testrealm.json -> needs to be in Java code, due to the URL being
> hard-coded in there (we need to resolve the URL of the host, running the
> bits). But, IMO for now that should be good enough.
>
> Bruno did offer to help out on the Keycloak integration, so that I can go
> back to the analytics and mertrics feature. Thanks abstractj!! <3
>
> Greetings,
> Matthias
>
> [1]
> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
> [2]
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
> [3]
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
> [4]
> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
> [5]
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
> [6]
> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
>
>
> --
> 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/20140514/a102a459/attachment.html 

From matzew at apache.org  Wed May 14 03:59:19 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 14 May 2014 09:59:19 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <5371DC12.8070308@redhat.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
Message-ID: <CAAg5f2Rh=Zz4T_NXJJo5S6AysAmUTJT-d1=KRsE2Mznn+QSvyA@mail.gmail.com>

On Tue, May 13, 2014 at 10:47 AM, Hylke Bons <hbons at redhat.com> wrote:

>  Hello,
>
> Depending on the use case, it may even deserve its own spot in the
> sidebar. Like already mentioned on the thread, it's better to keep the
> number of items there fixed. We may have have several entry points to the
> logs, and an overview of some statistics can be useful as a landing page
> before going into "Applications".
>
> Let's step back for a moment before looking at the UI: What are we trying
> to solve by providing a log?
>
> - Let administrators know everything is going well? (or, that there was a
> problem?)
>

yes, see the data I mentioned earlier in the thread


> - Looking at resources used? Bandwidth, costs?
>

Nope


> - App adoption/growth numbers over time? How well is my app doing?
>

Nope


>
> I'm not sure about the technical possibilities. Thoughts?
>
yeah, the nopes are not possible :)


>
> Thanks,
>
> Hylke
>
>
>
>
> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>
>  Hi,
>
>  as discussed , we need some sort of 'stats' around push, like:
> * time of sending
> * receivers (e.g. categories, alias ?)
> * content/payload of the message
> * could be sent out to APNs/GCM
>
>
>  But, where, or how to add this ?
> My current thought is:
>
>  When a user did select an "Application", he enters the "Application
> Details Page" (see [1]), now here, on the sidebar (see [2]) he would see
> the "Notifications" icon.
>
>  Clicking on that  "Notifications" icon, would give you a new page, that
> contains the "Send Notifications..." button (currently located in [1]), and
> a table of all the push messages that were sent out for the _current_
> selected Application.
>
>  Any thoughts ?
>
>  -Matthias
>
>  [1]
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
> [2]
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>
>
>  --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140514/720c8c93/attachment-0001.html 

From matzew at apache.org  Wed May 14 04:46:35 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 14 May 2014 10:46:35 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
	<88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
Message-ID: <CAAg5f2TCjw=Vz51W6R7S1Y5iymhyRpYpdmUZ5Vgr_HsARQ6tHg@mail.gmail.com>

On Tue, May 13, 2014 at 10:23 PM, Jay Balunas <jbalunas at redhat.com> wrote:

> Wanted to chime in here.  The overall goal of the metrics/stats imo, is
> around letting developers/administrators know what is happening with the
> server.  Messages in/out, registrations, etc....  This will also help new
> developers see activity and do some basic debugging if devices fail to
> register or messages fail to send.
>
> Maybe in the future we'll get into more analytics, resource usage type
> stuff but for Mobile Push 1.0 I think this is overkill.  For example I
> would not expect us to store this data over 30 days or so, and have viewing
> options like "last hour", "last 24 hours", "yesterday", "last 7 days",
> etc...
>

yeah - a simple history of messages sent


>
> Building on what Matthias posted below, here are some breakdowns of stats
> we could/should track:
>
> Registration:
> -- Device registered with [x,y,z] metadata
> -- Device removed with [x,y,z] metadata
>

let's focus on message sent stats for now


>
> Messages:
> -- Push request <timestamp-id> received from [ip] with [x,y,z] metadata
> -- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS, CD
> GCM, etc...]
> -- Push request <timestamp-id> had foo errors : details
>

Yes, these are nice items for the details once you click on a push message
in that 'history table view' (e.g. IP address, full criteria, error
details, etc).

The table itself could be really simple:
* time of sending
* content/payload of the message
* could be sent out to (e.g. a status icon *green/red*)

Once a user clicks an entry, we would display more details


> These would all have app and variant info as part of the metadata so they
> can filtered/broken down as needed.
>
> This should give us a great base for all kinds of table and chart views.
> -- Registrations over time for the server, specific app, specific variant
> -- Messages over time for the server, specific app, specific variant
> -- Table of the above if feasible :-)
>


yeah, all that is good - but IMO more a dashboard (e.g. over time we could
also show how often an app has been launched (per variant) - and with some
work on the registration SDKs, we could (not 1.0) show how often an app has
been opened by a push

>
> Obviously we may need to scale down as needed, and discuss more, but this
> is what I was thinking about.
>
> Thoughts?
>
>
> On May 13, 2014, at 4:47 AM, Hylke Bons <hbons at redhat.com> wrote:
>
>  Hello,
>
> Depending on the use case, it may even deserve its own spot in the
> sidebar. Like already mentioned on the thread, it's better to keep the
> number of items there fixed. We may have have several entry points to the
> logs, and an overview of some statistics can be useful as a landing page
> before going into "Applications".
>
> Let's step back for a moment before looking at the UI: What are we trying
> to solve by providing a log?
>
> - Let administrators know everything is going well? (or, that there was a
> problem?)
> - Looking at resources used? Bandwidth, costs?
> - App adoption/growth numbers over time? How well is my app doing?
>
> I'm not sure about the technical possibilities. Thoughts?
>
> Thanks,
>
> Hylke
>
>
>
> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>
>  Hi,
>
>  as discussed , we need some sort of 'stats' around push, like:
> * time of sending
> * receivers (e.g. categories, alias ?)
> * content/payload of the message
> * could be sent out to APNs/GCM
>
>
>  But, where, or how to add this ?
> My current thought is:
>
>  When a user did select an "Application", he enters the "Application
> Details Page" (see [1]), now here, on the sidebar (see [2]) he would see
> the "Notifications" icon.
>
>  Clicking on that  "Notifications" icon, would give you a new page, that
> contains the "Send Notifications..." button (currently located in [1]), and
> a table of all the push messages that were sent out for the _current_
> selected Application.
>
>  Any thoughts ?
>
>  -Matthias
>
>  [1]
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
> [2]
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>
>
>  --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>  _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140514/1fa5ef1e/attachment.html 

From matzew at apache.org  Wed May 14 04:48:39 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 14 May 2014 10:48:39 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <7F8BC7FF-6CB4-43D6-8313-DD22165AF2DC@redhat.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
	<88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
	<7F8BC7FF-6CB4-43D6-8313-DD22165AF2DC@redhat.com>
Message-ID: <CAAg5f2SZKTJnRzHhNysr=aROHAs659cfNOX+uv_AzN0q2kRJfg@mail.gmail.com>

On Tue, May 13, 2014 at 10:25 PM, Jay Balunas <jbalunas at redhat.com> wrote:

> Oh, and I also like the idea of the side bar always being the same and
> giving the users a simple place to get this info.
>

yes!

Hylke,
so we should have the notications icon to get to the "messages stats view",
which also could contain a link to the "send push", right ?



>
> It might be possible to "pre-load" the display based on the URL as well so
> we could have linkable views with context when drilling down - although
> that might be a better upgrade in the future :-)
>
> On May 13, 2014, at 4:23 PM, Jay Balunas <jbalunas at redhat.com> wrote:
>
> Wanted to chime in here.  The overall goal of the metrics/stats imo, is
> around letting developers/administrators know what is happening with the
> server.  Messages in/out, registrations, etc....  This will also help new
> developers see activity and do some basic debugging if devices fail to
> register or messages fail to send.
>
> Maybe in the future we'll get into more analytics, resource usage type
> stuff but for Mobile Push 1.0 I think this is overkill.  For example I
> would not expect us to store this data over 30 days or so, and have viewing
> options like "last hour", "last 24 hours", "yesterday", "last 7 days",
> etc...
>
> Building on what Matthias posted below, here are some breakdowns of stats
> we could/should track:
>
> Registration:
> -- Device registered with [x,y,z] metadata
> -- Device removed with [x,y,z] metadata
>
> Messages:
> -- Push request <timestamp-id> received from [ip] with [x,y,z] metadata
> -- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS, CD
> GCM, etc...]
> -- Push request <timestamp-id> had foo errors : details
>
> These would all have app and variant info as part of the metadata so they
> can filtered/broken down as needed.
>
> This should give us a great base for all kinds of table and chart views.
> -- Registrations over time for the server, specific app, specific variant
> -- Messages over time for the server, specific app, specific variant
> -- Table of the above if feasible :-)
>
> Obviously we may need to scale down as needed, and discuss more, but this
> is what I was thinking about.
>
> Thoughts?
>
>
> On May 13, 2014, at 4:47 AM, Hylke Bons <hbons at redhat.com> wrote:
>
>  Hello,
>
> Depending on the use case, it may even deserve its own spot in the
> sidebar. Like already mentioned on the thread, it's better to keep the
> number of items there fixed. We may have have several entry points to the
> logs, and an overview of some statistics can be useful as a landing page
> before going into "Applications".
>
> Let's step back for a moment before looking at the UI: What are we trying
> to solve by providing a log?
>
> - Let administrators know everything is going well? (or, that there was a
> problem?)
> - Looking at resources used? Bandwidth, costs?
> - App adoption/growth numbers over time? How well is my app doing?
>
> I'm not sure about the technical possibilities. Thoughts?
>
> Thanks,
>
> Hylke
>
>
>
> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>
>  Hi,
>
>  as discussed , we need some sort of 'stats' around push, like:
> * time of sending
> * receivers (e.g. categories, alias ?)
> * content/payload of the message
> * could be sent out to APNs/GCM
>
>
>  But, where, or how to add this ?
> My current thought is:
>
>  When a user did select an "Application", he enters the "Application
> Details Page" (see [1]), now here, on the sidebar (see [2]) he would see
> the "Notifications" icon.
>
>  Clicking on that  "Notifications" icon, would give you a new page, that
> contains the "Send Notifications..." button (currently located in [1]), and
> a table of all the push messages that were sent out for the _current_
> selected Application.
>
>  Any thoughts ?
>
>  -Matthias
>
>  [1]
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
> [2]
> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>
>
>  --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>  _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140514/d8021350/attachment-0001.html 

From hbons at redhat.com  Wed May 14 06:14:18 2014
From: hbons at redhat.com (Hylke Bons)
Date: Wed, 14 May 2014 11:14:18 +0100
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CAAg5f2Rh=Zz4T_NXJJo5S6AysAmUTJT-d1=KRsE2Mznn+QSvyA@mail.gmail.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>	<5371DC12.8070308@redhat.com>
	<CAAg5f2Rh=Zz4T_NXJJo5S6AysAmUTJT-d1=KRsE2Mznn+QSvyA@mail.gmail.com>
Message-ID: <537341FA.6020706@redhat.com>

Thanks guys, this clears up a lot about what we want to cover and can do.
I'll make some proposals that we can discuss on Friday.

Hylke

On 14/05/2014 08:59, Matthias Wessendorf wrote:
>
>
>
> On Tue, May 13, 2014 at 10:47 AM, Hylke Bons <hbons at redhat.com 
> <mailto:hbons at redhat.com>> wrote:
>
>     Hello,
>
>     Depending on the use case, it may even deserve its own spot in the
>     sidebar. Like already mentioned on the thread, it's better to keep
>     the number of items there fixed. We may have have several entry
>     points to the logs, and an overview of some statistics can be
>     useful as a landing page before going into "Applications".
>
>     Let's step back for a moment before looking at the UI: What are we
>     trying to solve by providing a log?
>
>     - Let administrators know everything is going well? (or, that
>     there was a problem?)
>
>
> yes, see the data I mentioned earlier in the thread
>
>     - Looking at resources used? Bandwidth, costs?
>
>
> Nope
>
>     - App adoption/growth numbers over time? How well is my app doing?
>
>
> Nope
>
>
>     I'm not sure about the technical possibilities. Thoughts?
>
> yeah, the nopes are not possible :)
>
>
>     Thanks,
>
>     Hylke
>
>
>
>
>     On 07/05/2014 10:54, Matthias Wessendorf wrote:
>>     Hi,
>>
>>     as discussed , we need some sort of 'stats' around push, like:
>>     * time of sending
>>     * receivers (e.g. categories, alias ?)
>>     * content/payload of the message
>>     * could be sent out to APNs/GCM
>>
>>
>>     But, where, or how to add this ?
>>     My current thought is:
>>
>>     When a user did select an "Application", he enters the
>>     "Application Details Page" (see [1]), now here, on the sidebar
>>     (see [2]) he would see the "Notifications" icon.
>>
>>     Clicking on that  "Notifications" icon, would give you a new
>>     page, that contains the "Send Notifications..." button (currently
>>     located in [1]), and a table of all the push messages that were
>>     sent out for the _current_ selected Application.
>>
>>     Any thoughts ?
>>
>>     -Matthias
>>
>>     [1]
>>     https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>>     [2]
>>     https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>>
>>
>>     -- 
>>     Matthias Wessendorf
>>
>>     blog: http://matthiaswessendorf.wordpress.com/
>>     sessions: http://www.slideshare.net/mwessendorf
>>     twitter: http://twitter.com/mwessendorf
>>
>>
>>     _______________________________________________
>>     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
>
>
>     _______________________________________________
>     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
>
>
>
>
> -- 
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140514/cfef1622/attachment.html 

From tkriz at redhat.com  Wed May 14 07:06:12 2014
From: tkriz at redhat.com (Tadeas Kriz)
Date: Wed, 14 May 2014 13:06:12 +0200
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
Message-ID: <CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>

Hey,

I?ve updated and run unifiedpush server integration tests with the Java Sender 0.6.0 and it worked without any problem. Also the tests on travis are green.

?
Tadeas Kriz

On 07 May 2014, at 18:30, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi folks,
> The AeroGear UnifiedPush Java Client 0.6.0 has been staged : 
> 
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
> 
> This release contains the following changes : 
> 
> * Proxy server configuration
> * AGPUSH-559 (HTTPS connection support)
> * AGPUSH-619 (fix on the mismatch of the TTL payload)
> 
> I plan to release to maven central on Friday, so please test and report any issues ! 
> 
> 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/20140514/9702fe3b/attachment.html 

From smikloso at redhat.com  Wed May 14 07:54:49 2014
From: smikloso at redhat.com (Stefan Miklosovic)
Date: Wed, 14 May 2014 07:54:49 -0400 (EDT)
Subject: [aerogear-dev] pushplugin release
In-Reply-To: <20140507194115.0c77f72a@kapy-ntb-x220>
References: <C219CA5A-728D-48C6-8AE3-87C4ACF6C5E6@redhat.com>
	<855483380.1104948.1399473516486.JavaMail.zimbra@redhat.com>
	<20140507194115.0c77f72a@kapy-ntb-x220>
Message-ID: <1159760144.2877413.1400068489254.JavaMail.zimbra@redhat.com>

Update:

Matthias wanted to check out also Android version of that hellopush demo

(this https://github.com/aerogear/aerogear-push-helloworld/tree/master/android) with this https://github.com/aerogear/aerogear-android-push)

== Android version:

Android emulator 4.4.2 manually - works ok
Android emulator 2.3.3 manually - works ok

Android physical device 2.3.3 manually - ok

I gave up on automated test since the instrumentation of that package is because of some to me yet unknown reason unsuccessfull.

== Cordova version with this unmodified project as is https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova:

Android physical device 2.3.3 manually - does the same thing as with Matthias try http://pastebin.com/raw.php?i=CLrR07mH

Android emulator device 2.3.3 Google API manually - does not display that dialog, starts normally, gets stuck on "registering ..." and does nothing after it, log is following

I/ActivityManager(   60): Displayed org.jboss.aerogear.unifiedpush.HelloWorld/.AeroGearUnifiedPushHelloWorld: +991ms
D/CordovaActivity(  495): onMessage(onPageStarted,file:///android_asset/www/index.html)
D/CordovaLog(  495): file:///android_asset/www/cordova.js: Line 966 : Falling back on PROMPT mode since _cordovaNative is missing. Expected for Android 3.2 and lower only.
I/Web Console(  495): Falling back on PROMPT mode since _cordovaNative is missing. Expected for Android 3.2 and lower only. at file:///android_asset/www/cordova.js:966
D/CordovaActivity(  495): onMessage(spinner,stop)
D/CordovaWebViewClient(  495): onPageFinished(file:///android_asset/www/index.html)
D/CordovaActivity(  495): onMessage(onPageFinished,file:///android_asset/www/index.html)

this is funny

D/CordovaLog(  495): file:///android_asset/www/js/index.js: Line 39 : ReferenceError: Can't find variable: push
E/Web Console(  495): ReferenceError: Can't find variable: push at file:///android_asset/www/js/index.js:39

D/dalvikvm(  126): GC_EXPLICIT freed 123K, 47% free 3176K/5895K, external 6045K/7549K, paused 47ms
D/dalvikvm(  525): GC_EXPLICIT freed 1020K, 54% free 4027K/8711K, external 3024K/3370K, paused 94ms

It is the same thing with manual Android physical 4.1.2 and with emulator 4.4.2 manual

Android emulator device 2.3.3 automated test

shows that dialog as I posted as an image and fails - it seems that switching to webview from Selendroid does some weird stuff ...

I was basically not able to run Cordova project successfully by any way, not sure what happened from the last time, 2.3.3 cases crashe or got stuck, 4+ cases got stuck as well but havent crashed.

I am wondering what that Can't find variable: push at file:///android_asset/www/js/index.js:39 means, it behaved ok from the last time.

It becomes pretty chaotic to cover all cases, as I said I gave up automated tests from now on.

Stefan Miklosovic
Red Hat Brno - JBoss Mobile Platform

e-mail: smikloso at redhat.com
irc: smikloso

----- Original Message -----
> Hi Stefan,
> 
> few comments inline.
> 
> Karel
> 
> On Wed, 7 May 2014 10:38:36 -0400 (EDT)
> Stefan Miklosovic <smikloso at redhat.com> wrote:
> 
> > Hi,
> > 
> > regarding of a release, I looked at it little bit closer and these are my
> > findings.
> > 
> > I tried latest master with cordova plugin add
> > https://github.com/aerogear/aerogear-pushplugin-cordova and I tried it on
> > this demo (1)
> > 
> > 1) What does not work
> > 
> > a) Android 2.3.3 emulator with Google API + mentioned demo, whole app
> > crashes
> > upon its start like (2) b) Android 2.3.4 physical device (My Sony Ericsson
> > with Android 2.3.4) - it shows this weird dialog (3)
> 
> Is this error dialog present for both automated (Droidium) and manual
> (Cordova
> CLI) deployments on real device? If not, it might be caused by Selendroid.
> Same
> for c)
> 
> > c) Android 4.1.2
> > physical device (Samsung) - same as (3) however once it shows it and once
> > not ... it is not deterministic
> > 
> > Regarding of (3), even I cancel it, it just freezes and does nothing.
> > 
> > 2) What works by automatic test but not deterministically
> > 
> > Android 4.4.2 emulator + Google API
> > 
> > This is little bit more complicated. Droidium can test in a such way that
> > in
> > case AVD of your emulator is not present on your machine, that AVD is
> > automatically created in test execution itself and emulator is booted, APK
> > is
> > deployed there tests are carried out and emulator is dynamically deleted
> > when
> > test stops.
> > 
> > Even emulator is booted and APK is installed there and test proceeds, in
> > the
> > background Google GCM service seems to be not initialized in time we are
> > sending a message so it is kind of not delivered. By debugging it
> > step-by-step it seems it has enough time to initialize itself.
> 
> We need an element (with id) in app we can wait for to appear to signalize
> registration was finished. Valid feature request for all android/ios/cordova
> variants I believe.
> 
> > 
> > However, the same issue with a message being not delivered has occured at
> > fully prepared emulator as well.
> > 
> 
> This makes sense to me as registration happen after app is installed and
> opened.
> 
> > 3) What works manually
> > 
> > Android 4.4.2 emulator + Google API meaning without test but buy sending a
> > message from web admin of (4)
> > 
> > Issues:
> > 
> > 1) For testing purposes we have this UPS installation (4) and while I was
> > coping with this testing manually, when I sent some message from UPS web
> > admin, it appeared on emulator twice, so it was basically sent two times.
> > Any
> > explanation for this?
> > 
> > 2) Sometime that message was not delivered to emulator at all, meaning even
> > I
> > send it from test it has not appeared on emulator. By accident this was
> > resolved when I refreshed web admin in browser. I do not know if this is
> > somehow related but why not ...
> 
> Well, delivery is not guaranteed and can take some time. Might be just a
> coincidence :-)
> 
> > 
> > I used this test (5) which uses Arquillian Droidium. Test is pretty
> > straightforward and if you know some Selenium you are already done.
> > 
> > (1)
> > https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova
> > (2) http://pastebin.com/raw.php?i=CLrR07mH
> > (3) http://devio.us/~stewe/DSC_0164.JPG
> > (4) https://cordovaci-mobileqa.rhcloud.com
> > (5)
> > https://github.com/smiklosovic/cordova-pushplugin-test-/blob/master/src/test/java/org/jboss/aerogear/push/plugin/cordova/AeroGearPushPluginCordovaTestCase.java
> > 
> > Stefan Miklosovic
> > Red Hat Brno - JBoss Mobile Platform
> > 
> > e-mail: smikloso at redhat.com
> > irc: smikloso
> > 
> > ----- Original Message -----
> > > Hi,
> > > 
> > > I?ve announced it before, but didn?t came around to actually do it and we
> > > started discussing the version number. So end of the week I?ll release a
> > > new
> > > version of the aerogear-pushplugin-cordova (for real this time) with
> > > version
> > > 0.5.0 this will include the 64 bit support the new API and some small bug
> > > fixes.
> > > 
> > > 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


From scm.blanc at gmail.com  Wed May 14 08:25:41 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 14 May 2014 14:25:41 +0200
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
	<CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>
Message-ID: <CAD_dpu2Me8nQTYaPDiTTMwASWhYvJtXxu9Nnk9f5+r8x55xk4A@mail.gmail.com>

Thx Tadeas !

The release button has been pressed !
Now it's just a matter to sync with Maven Central.

Sebi


On Wed, May 14, 2014 at 1:06 PM, Tadeas Kriz <tkriz at redhat.com> wrote:

> Hey,
>
> I?ve updated and run unifiedpush server integration tests with the Java
> Sender 0.6.0 and it worked without any problem. Also the tests on travis
> are green.
>
> ?
> Tadeas Kriz
>
> On 07 May 2014, at 18:30, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> Hi folks,
> The AeroGear UnifiedPush Java Client 0.6.0 has been staged :
>
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
>
> This release contains the following changes :
>
> * Proxy server configuration
> * AGPUSH-559 (HTTPS connection support)
> * AGPUSH-619 (fix on the mismatch of the TTL payload)
>
> I plan to release to maven central on Friday, so please test and report
> any issues !
>
> 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/20140514/f99836e5/attachment.html 

From jbalunas at redhat.com  Wed May 14 08:40:23 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Wed, 14 May 2014 08:40:23 -0400
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CAAg5f2TCjw=Vz51W6R7S1Y5iymhyRpYpdmUZ5Vgr_HsARQ6tHg@mail.gmail.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
	<88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
	<CAAg5f2TCjw=Vz51W6R7S1Y5iymhyRpYpdmUZ5Vgr_HsARQ6tHg@mail.gmail.com>
Message-ID: <CD5CF366-144C-41F8-B3E0-E504E301601A@redhat.com>


On May 14, 2014, at 4:46 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> 
> 
> 
> On Tue, May 13, 2014 at 10:23 PM, Jay Balunas <jbalunas at redhat.com> wrote:
> Wanted to chime in here.  The overall goal of the metrics/stats imo, is around letting developers/administrators know what is happening with the server.  Messages in/out, registrations, etc....  This will also help new developers see activity and do some basic debugging if devices fail to register or messages fail to send.  
> 
> Maybe in the future we'll get into more analytics, resource usage type stuff but for Mobile Push 1.0 I think this is overkill.  For example I would not expect us to store this data over 30 days or so, and have viewing options like "last hour", "last 24 hours", "yesterday", "last 7 days", etc...
> 
> yeah - a simple history of messages sent
>  
> 
> Building on what Matthias posted below, here are some breakdowns of stats we could/should track:
> 
> Registration:
> -- Device registered with [x,y,z] metadata
> -- Device removed with [x,y,z] metadata 
> 
> let's focus on message sent stats for now

Makes sense as a first pass.  We're already logging this to file anyway iirc.

>  
> 
> Messages:
> -- Push request <timestamp-id> received from [ip] with [x,y,z] metadata
> -- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS, CD GCM, etc...]
> -- Push request <timestamp-id> had foo errors : details
> 
> Yes, these are nice items for the details once you click on a push message in that 'history table view' (e.g. IP address, full criteria, error details, etc).

I thinking this would be the the data collected, what and how to show it would be part of the whole discussion.

> 
> The table itself could be really simple:
> * time of sending
> * content/payload of the message
> * could be sent out to (e.g. a status icon *green/red*)
> 
> Once a user clicks an entry, we would display more details

+1

> 
> 
> These would all have app and variant info as part of the metadata so they can filtered/broken down as needed.
> 
> This should give us a great base for all kinds of table and chart views.
> -- Registrations over time for the server, specific app, specific variant
> -- Messages over time for the server, specific app, specific variant
> -- Table of the above if feasible :-)
> 
> 
> yeah, all that is good - but IMO more a dashboard

I thought that was basically what we were going for - sort of a simple dashboard type page?  With the table you describe above and maybe a chart of messages sent over time or something like that?  

> (e.g. over time we could also show how often an app has been launched (per variant) - and with some work on the registration SDKs, we could (not 1.0) show how often an app has been opened by a push 

Very cool ideas for sure :-)

> 
> Obviously we may need to scale down as needed, and discuss more, but this is what I was thinking about.
> 
> Thoughts?
> 
> 
> On May 13, 2014, at 4:47 AM, Hylke Bons <hbons at redhat.com> wrote:
> 
>> Hello,
>> 
>> Depending on the use case, it may even deserve its own spot in the sidebar. Like already mentioned on the thread, it's better to keep the number of items there fixed. We may have have several entry points to the logs, and an overview of some statistics can be useful as a landing page before going into "Applications".
>> 
>> Let's step back for a moment before looking at the UI: What are we trying to solve by providing a log?
>> 
>> - Let administrators know everything is going well? (or, that there was a problem?)
>> - Looking at resources used? Bandwidth, costs?
>> - App adoption/growth numbers over time? How well is my app doing?
>> 
>> I'm not sure about the technical possibilities. Thoughts?
>> 
>> Thanks,
>> 
>> Hylke
>> 
>> 
>> 
>> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>>> Hi,
>>> 
>>> as discussed , we need some sort of 'stats' around push, like:
>>> * time of sending
>>> * receivers (e.g. categories, alias ?)
>>> * content/payload of the message
>>> * could be sent out to APNs/GCM
>>> 
>>> 
>>> But, where, or how to add this ? 
>>> My current thought is:
>>> 
>>> When a user did select an "Application", he enters the "Application Details Page" (see [1]), now here, on the sidebar (see [2]) he would see the "Notifications" icon.
>>> 
>>> Clicking on that  "Notifications" icon, would give you a new page, that contains the "Send Notifications..." button (currently located in [1]), and a table of all the push messages that were sent out for the _current_ selected Application.
>>> 
>>> Any thoughts ? 
>>> 
>>> -Matthias
>>> 
>>> [1] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>>> [2] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>>> 
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140514/2b74051b/attachment.html 

From avibelli at redhat.com  Wed May 14 09:49:27 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Wed, 14 May 2014 06:49:27 -0700 (PDT)
Subject: [aerogear-dev] Using the AeroGear BOMs
Message-ID: <1400075367412-7793.post@n5.nabble.com>

Hi all, 
I have started sending PR to many projects, to make Maven AeroGear projects
use the brand new BOMs available in Maven Central and now consumable after
the release of aerogear-misc 0.1.2 on Central.

So far I have sent PR for:
aerogear-aerodoc-android
aerogear-android-cookbook
aerogear-android
aerogear-android-push
aerogear-crypto-android-demo
aerogear-crypto-java
aerogear-otp-android-demo
aerogear-otp-java
aerogear-unifiedpush-java-client

I will send PR for the following in the next days:
aerogear-simplepush-java-client
aerogear-simplepush-server
aerogear-unifiedpush-server-integration-tests
aerogear-unifiedpush-server
aerogear-helloworld-android

Did I forget something?

Thanks!
Andrea



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Using-the-AeroGear-BOMs-tp7793.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Wed May 14 10:10:15 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 14 May 2014 16:10:15 +0200
Subject: [aerogear-dev] Keycloak integration
In-Reply-To: <CAAg5f2QQpkXSv7NBbC02=FqgbHt3GTQNSk9-KcWOZL-siS7JEQ@mail.gmail.com>
References: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
	<CAAg5f2QQpkXSv7NBbC02=FqgbHt3GTQNSk9-KcWOZL-siS7JEQ@mail.gmail.com>
Message-ID: <CAAg5f2T+nZRhqwHSSWBCugOQ0aqLp8mhxxT7rcfG4iXNFSnNLQ@mail.gmail.com>

I have submitted an _early_ PR to master to get the KC bits in - this will
help the Angular.js based UI overhaul, as its currently lacks a proper
login UI ;-)

https://github.com/aerogear/aerogear-unifiedpush-server/pull/156

Once that is merged to MASTER, the angular branch can be rebased on this;

Note: I added notes for users, to go w/ a 'stable' 0.10.x version...


-Matthias


On Wed, May 14, 2014 at 9:10 AM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hello,
>
> here is an update on the integration: Bill did some updates to his example
> template and worked on more things inside of Keycloak for a better
> integration.
>
> Yesterday, I used his example work and applied it to our UPS:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration
>
>
> There is now an 'auth-server' module which produces a WAR (that also
> contains an AeroGear theme), to be deployed to the AS:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration/auth-server
>
>
> The 'server' module is using a ContextListener for the configuration work,
> instead of the previous keycloak.json file:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-two-war-integration/server/src/main/java/org/jboss/aerogear/unifiedpush/keycloak/BootstrapListener.java
>
> Deploying the two WARs (auth before ups) will show the integration
> (admin:admin is the initial password).
>
> IMO this is a huge step towards a proper Keycloak integration, but some
> items are still open:
> - nicer config (using his testrealm.json inside of the auth-server)
> - user/roles mgmt
> - integration w/ the new UI
> - ...
>
> When Bruno is back, the work on this branch will continue.
>
> That's it for now.
>
> -Matthias
>
>
>
>
>
>
> On Tue, May 6, 2014 at 11:49 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>> Hello folks!
>>
>> Bill Burk was helping on the Keycloak front and besides fixing related
>> items on the Keycloak server, he also created an example that we can use as
>> a template for the actual integration. See [1]
>>
>> In the past, Bruno and I did integrate w/ an external Keycloak server
>> (see [2]), and we did include the keycloak.json file (See [3]). Thanks to
>> Bill's work on Keycloak, the 'protected app' no longer needs that, see [4].
>> Also there is no more the need to customize the Keycloak Rest Application
>> (Stian and I did look into that as well).
>>
>>
>> Good news: This means the UPS can stay as it is -> no need to change
>> internals (e.g. the 'bundle all in one WAR file' did force us to change our
>> '/rest' URLs, as Keycloak uses them, see [5]).
>>
>> Inside of our 'modular' Keycloak branch (see [2] again), we can apply the
>> work from Bill:
>> * our current 'server' module will use a listener similar to [4]
>> * create a "ups-auth" module similar to [6]
>>
>> On the 'ups-auth module' there is one area where we need to have some
>> future improvement:
>> * testrealm.json -> needs to be in Java code, due to the URL being
>> hard-coded in there (we need to resolve the URL of the host, running the
>> bits). But, IMO for now that should be good enough.
>>
>> Bruno did offer to help out on the Keycloak integration, so that I can go
>> back to the analytics and mertrics feature. Thanks abstractj!! <3
>>
>> Greetings,
>> Matthias
>>
>> [1]
>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
>> [2]
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
>> [3]
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
>> [4]
>> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
>> [5]
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
>> [6]
>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
>>
>>
>> --
>> 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/20140514/81d52c56/attachment-0001.html 

From bsutter at redhat.com  Wed May 14 10:48:04 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Wed, 14 May 2014 10:48:04 -0400
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CD5CF366-144C-41F8-B3E0-E504E301601A@redhat.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
	<88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
	<CAAg5f2TCjw=Vz51W6R7S1Y5iymhyRpYpdmUZ5Vgr_HsARQ6tHg@mail.gmail.com>
	<CD5CF366-144C-41F8-B3E0-E504E301601A@redhat.com>
Message-ID: <6538B3CE-3768-4B63-BCB8-0CC323ACE8C1@redhat.com>

I am interested in the sorting/filtering of the columns - how many send requests happened in the last hour, last day, last week - how many installations were impacted by those requests - based on the aliases, categories, etc that were used.

I don't recall a proposed UI/mockup/wireframes on this topic.


On May 14, 2014, at 8:40 AM, Jay Balunas <jbalunas at redhat.com> wrote:

> 
> On May 14, 2014, at 4:46 AM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
>> 
>> 
>> 
>> On Tue, May 13, 2014 at 10:23 PM, Jay Balunas <jbalunas at redhat.com> wrote:
>> Wanted to chime in here.  The overall goal of the metrics/stats imo, is around letting developers/administrators know what is happening with the server.  Messages in/out, registrations, etc....  This will also help new developers see activity and do some basic debugging if devices fail to register or messages fail to send.  
>> 
>> Maybe in the future we'll get into more analytics, resource usage type stuff but for Mobile Push 1.0 I think this is overkill.  For example I would not expect us to store this data over 30 days or so, and have viewing options like "last hour", "last 24 hours", "yesterday", "last 7 days", etc...
>> 
>> yeah - a simple history of messages sent
>>  
>> 
>> Building on what Matthias posted below, here are some breakdowns of stats we could/should track:
>> 
>> Registration:
>> -- Device registered with [x,y,z] metadata
>> -- Device removed with [x,y,z] metadata 
>> 
>> let's focus on message sent stats for now
> 
> Makes sense as a first pass.  We're already logging this to file anyway iirc.
> 
>>  
>> 
>> Messages:
>> -- Push request <timestamp-id> received from [ip] with [x,y,z] metadata
>> -- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS, CD GCM, etc...]
>> -- Push request <timestamp-id> had foo errors : details
>> 
>> Yes, these are nice items for the details once you click on a push message in that 'history table view' (e.g. IP address, full criteria, error details, etc).
> 
> I thinking this would be the the data collected, what and how to show it would be part of the whole discussion.
> 
>> 
>> The table itself could be really simple:
>> * time of sending
>> * content/payload of the message
>> * could be sent out to (e.g. a status icon *green/red*)
>> 
>> Once a user clicks an entry, we would display more details
> 
> +1
> 
>> 
>> 
>> These would all have app and variant info as part of the metadata so they can filtered/broken down as needed.
>> 
>> This should give us a great base for all kinds of table and chart views.
>> -- Registrations over time for the server, specific app, specific variant
>> -- Messages over time for the server, specific app, specific variant
>> -- Table of the above if feasible :-)
>> 
>> 
>> yeah, all that is good - but IMO more a dashboard
> 
> I thought that was basically what we were going for - sort of a simple dashboard type page?  With the table you describe above and maybe a chart of messages sent over time or something like that?  
> 
>> (e.g. over time we could also show how often an app has been launched (per variant) - and with some work on the registration SDKs, we could (not 1.0) show how often an app has been opened by a push 
> 
> Very cool ideas for sure :-)
> 
>> 
>> Obviously we may need to scale down as needed, and discuss more, but this is what I was thinking about.
>> 
>> Thoughts?
>> 
>> 
>> On May 13, 2014, at 4:47 AM, Hylke Bons <hbons at redhat.com> wrote:
>> 
>>> Hello,
>>> 
>>> Depending on the use case, it may even deserve its own spot in the sidebar. Like already mentioned on the thread, it's better to keep the number of items there fixed. We may have have several entry points to the logs, and an overview of some statistics can be useful as a landing page before going into "Applications".
>>> 
>>> Let's step back for a moment before looking at the UI: What are we trying to solve by providing a log?
>>> 
>>> - Let administrators know everything is going well? (or, that there was a problem?)
>>> - Looking at resources used? Bandwidth, costs?
>>> - App adoption/growth numbers over time? How well is my app doing?
>>> 
>>> I'm not sure about the technical possibilities. Thoughts?
>>> 
>>> Thanks,
>>> 
>>> Hylke
>>> 
>>> 
>>> 
>>> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>>>> Hi,
>>>> 
>>>> as discussed , we need some sort of 'stats' around push, like:
>>>> * time of sending
>>>> * receivers (e.g. categories, alias ?)
>>>> * content/payload of the message
>>>> * could be sent out to APNs/GCM
>>>> 
>>>> 
>>>> But, where, or how to add this ? 
>>>> My current thought is:
>>>> 
>>>> When a user did select an "Application", he enters the "Application Details Page" (see [1]), now here, on the sidebar (see [2]) he would see the "Notifications" icon.
>>>> 
>>>> Clicking on that  "Notifications" icon, would give you a new page, that contains the "Send Notifications..." button (currently located in [1]), and a table of all the push messages that were sent out for the _current_ selected Application.
>>>> 
>>>> Any thoughts ? 
>>>> 
>>>> -Matthias
>>>> 
>>>> [1] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>>>> [2] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>>>> 
>>>> 
>>>> -- 
>>>> Matthias Wessendorf 
>>>> 
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> sessions: http://www.slideshare.net/mwessendorf
>>>> twitter: http://twitter.com/mwessendorf
>>>> 
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140514/f49d9ed7/attachment.html 

From lholmqui at redhat.com  Wed May 14 10:49:03 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Wed, 14 May 2014 10:49:03 -0400
Subject: [aerogear-dev] AeroGear JS 1.5.0 pre-release
In-Reply-To: <5581DC26-F780-4012-BB8C-FA1AE5E4E3B4@redhat.com>
References: <5581DC26-F780-4012-BB8C-FA1AE5E4E3B4@redhat.com>
Message-ID: <98B665C8-639C-4F44-BBED-6D86ACBEB9CD@redhat.com>

Hello,

we?ve released the 1.5.0 version of the AeroGear.js library

http://blog.lholmquist.org/aerogear-js-1-5-0/

checkout some highlights

On May 12, 2014, at 11:18 AM, Lucas Holmquist <lholmqui at redhat.com> wrote:

> Hey peeps,
> 
> this week we will be releasing AeroGear.js 1.5.0.
> 
> Here is a link to the release notes
> 
> https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12313725&version=12324171
> 
> 
> There is still 1 open issue,  https://issues.jboss.org/browse/AGJS-41 , but shouldn?t affect the main repo since it is just a cookbook recipe
> 
> 
> i?ve tagged a 1.5.0-dev release, https://github.com/aerogear/aerogear-js/tree/1.5.0-dev, which will be replaced once we do the official release
> 
> If you would like to check it out,  go for it.  We will plan to release wednesday
> 
> 
> -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/20140514/bded7538/attachment-0001.html 

From matzew at apache.org  Wed May 14 11:23:12 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 14 May 2014 17:23:12 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <6538B3CE-3768-4B63-BCB8-0CC323ACE8C1@redhat.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
	<88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
	<CAAg5f2TCjw=Vz51W6R7S1Y5iymhyRpYpdmUZ5Vgr_HsARQ6tHg@mail.gmail.com>
	<CD5CF366-144C-41F8-B3E0-E504E301601A@redhat.com>
	<6538B3CE-3768-4B63-BCB8-0CC323ACE8C1@redhat.com>
Message-ID: <CAAg5f2R=SEvju7VMQO22ngc_JDYX1rQZoesGk1TSTg5MEVDK3Q@mail.gmail.com>

On Wed, May 14, 2014 at 4:48 PM, Burr Sutter <bsutter at redhat.com> wrote:

> I am interested in the sorting/filtering of the columns - how many send
> requests happened in the last hour, last day, last week
>

the filter might be on the more fancy side of things - at least I want a
normal table asap


> - how many installations were impacted by those requests - based on the
> aliases, categories, etc that were used.
>

yeah, see the initial data that we used in this thread :-)


>
> I don't recall a proposed UI/mockup/wireframes on this topic.
>

Hylke is working on that; we should be having something later this week


>
>
> On May 14, 2014, at 8:40 AM, Jay Balunas <jbalunas at redhat.com> wrote:
>
>
> On May 14, 2014, at 4:46 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>
>
>
> On Tue, May 13, 2014 at 10:23 PM, Jay Balunas <jbalunas at redhat.com> wrote:
>
>> Wanted to chime in here.  The overall goal of the metrics/stats imo, is
>> around letting developers/administrators know what is happening with the
>> server.  Messages in/out, registrations, etc....  This will also help new
>> developers see activity and do some basic debugging if devices fail to
>> register or messages fail to send.
>>
>> Maybe in the future we'll get into more analytics, resource usage type
>> stuff but for Mobile Push 1.0 I think this is overkill.  For example I
>> would not expect us to store this data over 30 days or so, and have viewing
>> options like "last hour", "last 24 hours", "yesterday", "last 7 days",
>> etc...
>>
>
> yeah - a simple history of messages sent
>
>
>>
>> Building on what Matthias posted below, here are some breakdowns of stats
>> we could/should track:
>>
>> Registration:
>> -- Device registered with [x,y,z] metadata
>> -- Device removed with [x,y,z] metadata
>>
>
> let's focus on message sent stats for now
>
>
> Makes sense as a first pass.  We're already logging this to file anyway
> iirc.
>
>
>
>>
>> Messages:
>> -- Push request <timestamp-id> received from [ip] with [x,y,z] metadata
>> -- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS,
>> CD GCM, etc...]
>> -- Push request <timestamp-id> had foo errors : details
>>
>
> Yes, these are nice items for the details once you click on a push message
> in that 'history table view' (e.g. IP address, full criteria, error
> details, etc).
>
>
> I thinking this would be the the data collected, what and how to show it
> would be part of the whole discussion.
>
>
> The table itself could be really simple:
> * time of sending
> * content/payload of the message
> * could be sent out to (e.g. a status icon *green/red*)
>
> Once a user clicks an entry, we would display more details
>
>
> +1
>
>
>
>> These would all have app and variant info as part of the metadata so they
>> can filtered/broken down as needed.
>>
>> This should give us a great base for all kinds of table and chart views.
>> -- Registrations over time for the server, specific app, specific variant
>> -- Messages over time for the server, specific app, specific variant
>> -- Table of the above if feasible :-)
>>
>
>
> yeah, all that is good - but IMO more a dashboard
>
>
> I thought that was basically what we were going for - sort of a simple
> dashboard type page?  With the table you describe above and maybe a chart
> of messages sent over time or something like that?
>
> (e.g. over time we could also show how often an app has been launched (per
> variant) - and with some work on the registration SDKs, we could (not 1.0)
> show how often an app has been opened by a push
>
>
> Very cool ideas for sure :-)
>
>
>> Obviously we may need to scale down as needed, and discuss more, but this
>> is what I was thinking about.
>>
>> Thoughts?
>>
>>
>> On May 13, 2014, at 4:47 AM, Hylke Bons <hbons at redhat.com> wrote:
>>
>> Hello,
>>
>> Depending on the use case, it may even deserve its own spot in the
>> sidebar. Like already mentioned on the thread, it's better to keep the
>> number of items there fixed. We may have have several entry points to the
>> logs, and an overview of some statistics can be useful as a landing page
>> before going into "Applications".
>>
>> Let's step back for a moment before looking at the UI: What are we trying
>> to solve by providing a log?
>>
>> - Let administrators know everything is going well? (or, that there was a
>> problem?)
>> - Looking at resources used? Bandwidth, costs?
>> - App adoption/growth numbers over time? How well is my app doing?
>>
>> I'm not sure about the technical possibilities. Thoughts?
>>
>> Thanks,
>>
>> Hylke
>>
>>
>>
>> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>>
>> Hi,
>>
>> as discussed , we need some sort of 'stats' around push, like:
>> * time of sending
>> * receivers (e.g. categories, alias ?)
>> * content/payload of the message
>> * could be sent out to APNs/GCM
>>
>>
>> But, where, or how to add this ?
>> My current thought is:
>>
>> When a user did select an "Application", he enters the "Application
>> Details Page" (see [1]), now here, on the sidebar (see [2]) he would see
>> the "Notifications" icon.
>>
>> Clicking on that  "Notifications" icon, would give you a new page, that
>> contains the "Send Notifications..." button (currently located in [1]), and
>> a table of all the push messages that were sent out for the _current_
>> selected Application.
>>
>> Any thoughts ?
>>
>> -Matthias
>>
>> [1]
>> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>> [2]
>> https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>>
>> _______________________________________________
>> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140514/acdfdf6e/attachment.html 

From bsutter at redhat.com  Wed May 14 11:30:19 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Wed, 14 May 2014 11:30:19 -0400
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <CAAg5f2R=SEvju7VMQO22ngc_JDYX1rQZoesGk1TSTg5MEVDK3Q@mail.gmail.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
	<88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
	<CAAg5f2TCjw=Vz51W6R7S1Y5iymhyRpYpdmUZ5Vgr_HsARQ6tHg@mail.gmail.com>
	<CD5CF366-144C-41F8-B3E0-E504E301601A@redhat.com>
	<6538B3CE-3768-4B63-BCB8-0CC323ACE8C1@redhat.com>
	<CAAg5f2R=SEvju7VMQO22ngc_JDYX1rQZoesGk1TSTg5MEVDK3Q@mail.gmail.com>
Message-ID: <8DDD672E-1A89-4A67-8AEB-7F23D93CE029@redhat.com>

please remind me of the 4 (?) different criteria used to filter who gets a push message
alias
category
device platform/os



On May 14, 2014, at 11:23 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> 
> 
> 
> On Wed, May 14, 2014 at 4:48 PM, Burr Sutter <bsutter at redhat.com> wrote:
> I am interested in the sorting/filtering of the columns - how many send requests happened in the last hour, last day, last week
> 
> the filter might be on the more fancy side of things - at least I want a normal table asap
>  
> - how many installations were impacted by those requests - based on the aliases, categories, etc that were used.
> 
> yeah, see the initial data that we used in this thread :-)
>  
> 
> I don't recall a proposed UI/mockup/wireframes on this topic.
> 
> Hylke is working on that; we should be having something later this week
>  
> 
> 
> On May 14, 2014, at 8:40 AM, Jay Balunas <jbalunas at redhat.com> wrote:
> 
>> 
>> On May 14, 2014, at 4:46 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>> 
>>> 
>>> 
>>> 
>>> On Tue, May 13, 2014 at 10:23 PM, Jay Balunas <jbalunas at redhat.com> wrote:
>>> Wanted to chime in here.  The overall goal of the metrics/stats imo, is around letting developers/administrators know what is happening with the server.  Messages in/out, registrations, etc....  This will also help new developers see activity and do some basic debugging if devices fail to register or messages fail to send.  
>>> 
>>> Maybe in the future we'll get into more analytics, resource usage type stuff but for Mobile Push 1.0 I think this is overkill.  For example I would not expect us to store this data over 30 days or so, and have viewing options like "last hour", "last 24 hours", "yesterday", "last 7 days", etc...
>>> 
>>> yeah - a simple history of messages sent
>>>  
>>> 
>>> Building on what Matthias posted below, here are some breakdowns of stats we could/should track:
>>> 
>>> Registration:
>>> -- Device registered with [x,y,z] metadata
>>> -- Device removed with [x,y,z] metadata 
>>> 
>>> let's focus on message sent stats for now
>> 
>> Makes sense as a first pass.  We're already logging this to file anyway iirc.
>> 
>>>  
>>> 
>>> Messages:
>>> -- Push request <timestamp-id> received from [ip] with [x,y,z] metadata
>>> -- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS, CD GCM, etc...]
>>> -- Push request <timestamp-id> had foo errors : details
>>> 
>>> Yes, these are nice items for the details once you click on a push message in that 'history table view' (e.g. IP address, full criteria, error details, etc).
>> 
>> I thinking this would be the the data collected, what and how to show it would be part of the whole discussion.
>> 
>>> 
>>> The table itself could be really simple:
>>> * time of sending
>>> * content/payload of the message
>>> * could be sent out to (e.g. a status icon *green/red*)
>>> 
>>> Once a user clicks an entry, we would display more details
>> 
>> +1
>> 
>>> 
>>> 
>>> These would all have app and variant info as part of the metadata so they can filtered/broken down as needed.
>>> 
>>> This should give us a great base for all kinds of table and chart views.
>>> -- Registrations over time for the server, specific app, specific variant
>>> -- Messages over time for the server, specific app, specific variant
>>> -- Table of the above if feasible :-)
>>> 
>>> 
>>> yeah, all that is good - but IMO more a dashboard
>> 
>> I thought that was basically what we were going for - sort of a simple dashboard type page?  With the table you describe above and maybe a chart of messages sent over time or something like that?  
>> 
>>> (e.g. over time we could also show how often an app has been launched (per variant) - and with some work on the registration SDKs, we could (not 1.0) show how often an app has been opened by a push 
>> 
>> Very cool ideas for sure :-)
>> 
>>> 
>>> Obviously we may need to scale down as needed, and discuss more, but this is what I was thinking about.
>>> 
>>> Thoughts?
>>> 
>>> 
>>> On May 13, 2014, at 4:47 AM, Hylke Bons <hbons at redhat.com> wrote:
>>> 
>>>> Hello,
>>>> 
>>>> Depending on the use case, it may even deserve its own spot in the sidebar. Like already mentioned on the thread, it's better to keep the number of items there fixed. We may have have several entry points to the logs, and an overview of some statistics can be useful as a landing page before going into "Applications".
>>>> 
>>>> Let's step back for a moment before looking at the UI: What are we trying to solve by providing a log?
>>>> 
>>>> - Let administrators know everything is going well? (or, that there was a problem?)
>>>> - Looking at resources used? Bandwidth, costs?
>>>> - App adoption/growth numbers over time? How well is my app doing?
>>>> 
>>>> I'm not sure about the technical possibilities. Thoughts?
>>>> 
>>>> Thanks,
>>>> 
>>>> Hylke
>>>> 
>>>> 
>>>> 
>>>> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>>>>> Hi,
>>>>> 
>>>>> as discussed , we need some sort of 'stats' around push, like:
>>>>> * time of sending
>>>>> * receivers (e.g. categories, alias ?)
>>>>> * content/payload of the message
>>>>> * could be sent out to APNs/GCM
>>>>> 
>>>>> 
>>>>> But, where, or how to add this ? 
>>>>> My current thought is:
>>>>> 
>>>>> When a user did select an "Application", he enters the "Application Details Page" (see [1]), now here, on the sidebar (see [2]) he would see the "Notifications" icon.
>>>>> 
>>>>> Clicking on that  "Notifications" icon, would give you a new page, that contains the "Send Notifications..." button (currently located in [1]), and a table of all the push messages that were sent out for the _current_ selected Application.
>>>>> 
>>>>> Any thoughts ? 
>>>>> 
>>>>> -Matthias
>>>>> 
>>>>> [1] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>>>>> [2] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Matthias Wessendorf 
>>>>> 
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> 
>>> -- 
>>> Matthias Wessendorf 
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140514/d9e4ca6a/attachment-0001.html 

From scm.blanc at gmail.com  Wed May 14 15:18:06 2014
From: scm.blanc at gmail.com (=?utf-8?Q?S=C3=A9bastien_Blanc?=)
Date: Wed, 14 May 2014 21:18:06 +0200
Subject: [aerogear-dev] [UPS] UI for Sent Push stats
In-Reply-To: <8DDD672E-1A89-4A67-8AEB-7F23D93CE029@redhat.com>
References: <CAAg5f2Q4DbW-orvbZU2Xh3iU2hYr_fw9o96O-QEaqcjezkD6xw@mail.gmail.com>
	<5371DC12.8070308@redhat.com>
	<88660A9F-94EB-499D-B4CB-75A0A726A739@redhat.com>
	<CAAg5f2TCjw=Vz51W6R7S1Y5iymhyRpYpdmUZ5Vgr_HsARQ6tHg@mail.gmail.com>
	<CD5CF366-144C-41F8-B3E0-E504E301601A@redhat.com>
	<6538B3CE-3768-4B63-BCB8-0CC323ACE8C1@redhat.com>
	<CAAg5f2R=SEvju7VMQO22ngc_JDYX1rQZoesGk1TSTg5MEVDK3Q@mail.gmail.com>
	<8DDD672E-1A89-4A67-8AEB-7F23D93CE029@redhat.com>
Message-ID: <1D367307-F64E-4354-BC7C-CD4119E3584A@gmail.com>

variants

Envoy? de mon iPhone

> Le 14 mai 2014 ? 17:30, Burr Sutter <bsutter at redhat.com> a ?crit :
> 
> please remind me of the 4 (?) different criteria used to filter who gets a push message
> alias
> category
> device platform/os
> 
> 
> 
>> On May 14, 2014, at 11:23 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>> 
>> 
>> 
>> 
>>> On Wed, May 14, 2014 at 4:48 PM, Burr Sutter <bsutter at redhat.com> wrote:
>>> I am interested in the sorting/filtering of the columns - how many send requests happened in the last hour, last day, last week
>> 
>> the filter might be on the more fancy side of things - at least I want a normal table asap
>>  
>>> - how many installations were impacted by those requests - based on the aliases, categories, etc that were used.
>> 
>> yeah, see the initial data that we used in this thread :-)
>>  
>>> 
>>> I don't recall a proposed UI/mockup/wireframes on this topic.
>> 
>> Hylke is working on that; we should be having something later this week
>>  
>>> 
>>> 
>>>> On May 14, 2014, at 8:40 AM, Jay Balunas <jbalunas at redhat.com> wrote:
>>>> 
>>>> 
>>>>> On May 14, 2014, at 4:46 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Tue, May 13, 2014 at 10:23 PM, Jay Balunas <jbalunas at redhat.com> wrote:
>>>>>> Wanted to chime in here.  The overall goal of the metrics/stats imo, is around letting developers/administrators know what is happening with the server.  Messages in/out, registrations, etc....  This will also help new developers see activity and do some basic debugging if devices fail to register or messages fail to send.  
>>>>>> 
>>>>>> Maybe in the future we'll get into more analytics, resource usage type stuff but for Mobile Push 1.0 I think this is overkill.  For example I would not expect us to store this data over 30 days or so, and have viewing options like "last hour", "last 24 hours", "yesterday", "last 7 days", etc...
>>>>> 
>>>>> yeah - a simple history of messages sent
>>>>>  
>>>>>> 
>>>>>> Building on what Matthias posted below, here are some breakdowns of stats we could/should track:
>>>>>> 
>>>>>> Registration:
>>>>>> -- Device registered with [x,y,z] metadata
>>>>>> -- Device removed with [x,y,z] metadata 
>>>>> 
>>>>> let's focus on message sent stats for now
>>>> 
>>>> Makes sense as a first pass.  We're already logging this to file anyway iirc.
>>>> 
>>>>>  
>>>>>> 
>>>>>> Messages:
>>>>>> -- Push request <timestamp-id> received from [ip] with [x,y,z] metadata
>>>>>> -- Push request <timestamp-id> matched XYZ devices and sent [ AB: APNS, CD GCM, etc...]
>>>>>> -- Push request <timestamp-id> had foo errors : details
>>>>> 
>>>>> Yes, these are nice items for the details once you click on a push message in that 'history table view' (e.g. IP address, full criteria, error details, etc).
>>>> 
>>>> I thinking this would be the the data collected, what and how to show it would be part of the whole discussion.
>>>> 
>>>>> 
>>>>> The table itself could be really simple:
>>>>> * time of sending
>>>>> * content/payload of the message
>>>>> * could be sent out to (e.g. a status icon *green/red*)
>>>>> 
>>>>> Once a user clicks an entry, we would display more details
>>>> 
>>>> +1
>>>> 
>>>>> 
>>>>>> 
>>>>>> These would all have app and variant info as part of the metadata so they can filtered/broken down as needed.
>>>>>> 
>>>>>> This should give us a great base for all kinds of table and chart views.
>>>>>> -- Registrations over time for the server, specific app, specific variant
>>>>>> -- Messages over time for the server, specific app, specific variant
>>>>>> -- Table of the above if feasible :-)
>>>>> 
>>>>> 
>>>>> yeah, all that is good - but IMO more a dashboard
>>>> 
>>>> I thought that was basically what we were going for - sort of a simple dashboard type page?  With the table you describe above and maybe a chart of messages sent over time or something like that?  
>>>> 
>>>>> (e.g. over time we could also show how often an app has been launched (per variant) - and with some work on the registration SDKs, we could (not 1.0) show how often an app has been opened by a push 
>>>> 
>>>> Very cool ideas for sure :-)
>>>> 
>>>>>> 
>>>>>> Obviously we may need to scale down as needed, and discuss more, but this is what I was thinking about.
>>>>>> 
>>>>>> Thoughts?
>>>>>> 
>>>>>> 
>>>>>>> On May 13, 2014, at 4:47 AM, Hylke Bons <hbons at redhat.com> wrote:
>>>>>>> 
>>>>>>> Hello,
>>>>>>> 
>>>>>>> Depending on the use case, it may even deserve its own spot in the sidebar. Like already mentioned on the thread, it's better to keep the number of items there fixed. We may have have several entry points to the logs, and an overview of some statistics can be useful as a landing page before going into "Applications".
>>>>>>> 
>>>>>>> Let's step back for a moment before looking at the UI: What are we trying to solve by providing a log?
>>>>>>> 
>>>>>>> - Let administrators know everything is going well? (or, that there was a problem?)
>>>>>>> - Looking at resources used? Bandwidth, costs?
>>>>>>> - App adoption/growth numbers over time? How well is my app doing?
>>>>>>> 
>>>>>>> I'm not sure about the technical possibilities. Thoughts?
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> 
>>>>>>> Hylke
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On 07/05/2014 10:54, Matthias Wessendorf wrote:
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> as discussed , we need some sort of 'stats' around push, like:
>>>>>>>> * time of sending
>>>>>>>> * receivers (e.g. categories, alias ?)
>>>>>>>> * content/payload of the message
>>>>>>>> * could be sent out to APNs/GCM
>>>>>>>> 
>>>>>>>> 
>>>>>>>> But, where, or how to add this ? 
>>>>>>>> My current thought is:
>>>>>>>> 
>>>>>>>> When a user did select an "Application", he enters the "Application Details Page" (see [1]), now here, on the sidebar (see [2]) he would see the "Notifications" icon.
>>>>>>>> 
>>>>>>>> Clicking on that  "Notifications" icon, would give you a new page, that contains the "Send Notifications..." button (currently located in [1]), and a table of all the push messages that were sent out for the _current_ selected Application.
>>>>>>>> 
>>>>>>>> Any thoughts ? 
>>>>>>>> 
>>>>>>>> -Matthias
>>>>>>>> 
>>>>>>>> [1] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/6.png
>>>>>>>> [2] https://github.com/hbons/aerogear-design/blob/master/Unified%20Push%20Server/Export/3.png
>>>>>>>> 
>>>>>>>> 
>>>>>>>> -- 
>>>>>>>> Matthias Wessendorf 
>>>>>>>> 
>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>> 
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> aerogear-dev mailing list
>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Matthias Wessendorf 
>>>>> 
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140514/314e824b/attachment-0001.html 

From corinnekrych at gmail.com  Thu May 15 03:56:28 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 15 May 2014 09:56:28 +0200
Subject: [aerogear-dev] OAuth2 authotization and Pipe integration
Message-ID: <5FC7D59B-B71A-42A6-882E-543076E61C18@gmail.com>

Hello folks

I?ve been thinking about providing a more fluid integration between authz and pipes.

Right now to read a list of GoogleDrive document, we need to read the pipe in the success callback of authz? requestAccess:

    AGAuthorizer* authorizer = [AGAuthorizer authorizer];    
    _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
         ...
    }]; 
    
    [_restAuthzModule requestAccessSuccess:^(id object) {
      		 id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
       		 [config setName:@"files"];
       		 [config setAuthzModule:authzModule]; // inject authz
     		 }];
    
   		 [documents read:^(id responseObject) {
        		// do sth with response
   		 } failure:^(NSError *error) {
       			 // when an error occurs...
   		 }];
    } failure:^(NSError *error) {
        NSLog(@"Failure in getting access token");
    }];

What about if we just initialize authzModule and inject it into pipe. Once the pipe read (or any crud) it will be the pipe that first fetch tokens (or  renew - whaetever is needed) and on success read the pipe. Basically we do the callback chaining internally in the Pipe instead of letting the developer deal with it.

    AGAuthorizer* authorizer = [AGAuthorizer authorizer];    
    _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
         ...
    }]; 
    
    id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
      		 [config setName:@"files"];
       		 [config setAuthzModule:authzModule]; // inject authz
    }];
    
    [documents read:^(id responseObject) {
        		// do sth with response
      } failure:^(NSError *error) {
       			 // when an error occurs...
    }];

It feels much fluid on the user.
Doing so we ?force? the app flow to ask token when it needs it, not in advance at startup of app. but i think this is good practice to lazy authz your app.

Thoughts?

Test repo can be found here:
https://github.com/corinnekrych/aerogear-ios/blob/transparent.refresh/AeroGear-iOS/pipeline/AGRESTPipe.m#L169
https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-145.refresh/GoogleDrive/GoogleDrive/AGViewController.m

++
Corinne

From mwessendorf at gmail.com  Thu May 15 05:20:33 2014
From: mwessendorf at gmail.com (Matthias Wessendorf)
Date: Thu, 15 May 2014 11:20:33 +0200
Subject: [aerogear-dev] Keycloak integration
In-Reply-To: <CAAg5f2T+nZRhqwHSSWBCugOQ0aqLp8mhxxT7rcfG4iXNFSnNLQ@mail.gmail.com>
References: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
	<CAAg5f2QQpkXSv7NBbC02=FqgbHt3GTQNSk9-KcWOZL-siS7JEQ@mail.gmail.com>
	<CAAg5f2T+nZRhqwHSSWBCugOQ0aqLp8mhxxT7rcfG4iXNFSnNLQ@mail.gmail.com>
Message-ID: <CAAg5f2Tz2Qp91mtJ+tnVdbJHv1OZ516eoGgooX+eziq9Q9zDjg@mail.gmail.com>

this got merged;

I have update the EPIC for this task:
https://issues.jboss.org/browse/AGPUSH-568


On Wed, May 14, 2014 at 4:10 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> I have submitted an _early_ PR to master to get the KC bits in - this will
> help the Angular.js based UI overhaul, as its currently lacks a proper
> login UI ;-)
>
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/156
>
> Once that is merged to MASTER, the angular branch can be rebased on this;
>
> Note: I added notes for users, to go w/ a 'stable' 0.10.x version...
>
>
> -Matthias
>
>
> On Wed, May 14, 2014 at 9:10 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>> Hello,
>>
>> here is an update on the integration: Bill did some updates to his
>> example template and worked on more things inside of Keycloak for a better
>> integration.
>>
>> Yesterday, I used his example work and applied it to our UPS:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration
>>
>>
>> There is now an 'auth-server' module which produces a WAR (that also
>> contains an AeroGear theme), to be deployed to the AS:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration/auth-server
>>
>>
>> The 'server' module is using a ContextListener for the configuration
>> work, instead of the previous keycloak.json file:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-two-war-integration/server/src/main/java/org/jboss/aerogear/unifiedpush/keycloak/BootstrapListener.java
>>
>> Deploying the two WARs (auth before ups) will show the integration
>> (admin:admin is the initial password).
>>
>> IMO this is a huge step towards a proper Keycloak integration, but some
>> items are still open:
>> - nicer config (using his testrealm.json inside of the auth-server)
>> - user/roles mgmt
>> - integration w/ the new UI
>> - ...
>>
>> When Bruno is back, the work on this branch will continue.
>>
>> That's it for now.
>>
>> -Matthias
>>
>>
>>
>>
>>
>>
>> On Tue, May 6, 2014 at 11:49 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>>
>>> Hello folks!
>>>
>>> Bill Burk was helping on the Keycloak front and besides fixing related
>>> items on the Keycloak server, he also created an example that we can use as
>>> a template for the actual integration. See [1]
>>>
>>> In the past, Bruno and I did integrate w/ an external Keycloak server
>>> (see [2]), and we did include the keycloak.json file (See [3]). Thanks to
>>> Bill's work on Keycloak, the 'protected app' no longer needs that, see [4].
>>> Also there is no more the need to customize the Keycloak Rest
>>> Application (Stian and I did look into that as well).
>>>
>>>
>>> Good news: This means the UPS can stay as it is -> no need to change
>>> internals (e.g. the 'bundle all in one WAR file' did force us to change our
>>> '/rest' URLs, as Keycloak uses them, see [5]).
>>>
>>> Inside of our 'modular' Keycloak branch (see [2] again), we can apply
>>> the work from Bill:
>>> * our current 'server' module will use a listener similar to [4]
>>> * create a "ups-auth" module similar to [6]
>>>
>>> On the 'ups-auth module' there is one area where we need to have some
>>> future improvement:
>>> * testrealm.json -> needs to be in Java code, due to the URL being
>>> hard-coded in there (we need to resolve the URL of the host, running the
>>> bits). But, IMO for now that should be good enough.
>>>
>>> Bruno did offer to help out on the Keycloak integration, so that I can
>>> go back to the analytics and mertrics feature. Thanks abstractj!! <3
>>>
>>> Greetings,
>>> Matthias
>>>
>>> [1]
>>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
>>> [2]
>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
>>> [3]
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
>>> [4]
>>> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
>>> [5]
>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
>>> [6]
>>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
>>>
>>>
>>> --
>>> 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/20140515/576c15c9/attachment.html 

From kpiwko at redhat.com  Thu May 15 06:52:50 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Thu, 15 May 2014 12:52:50 +0200
Subject: [aerogear-dev] Using the AeroGear BOMs
In-Reply-To: <1400075367412-7793.post@n5.nabble.com>
References: <1400075367412-7793.post@n5.nabble.com>
Message-ID: <20140515125250.4130e974@kapy-ntb-x220>

On Wed, 14 May 2014 06:49:27 -0700 (PDT)
Andrea Vibelli <avibelli at redhat.com> wrote:

> Hi all, 
> I have started sending PR to many projects, to make Maven AeroGear projects
> use the brand new BOMs available in Maven Central and now consumable after
> the release of aerogear-misc 0.1.2 on Central.
> 
> So far I have sent PR for:
> aerogear-aerodoc-android
> aerogear-android-cookbook
> aerogear-android
> aerogear-android-push
> aerogear-crypto-android-demo
> aerogear-crypto-java
> aerogear-otp-android-demo
> aerogear-otp-java
> aerogear-unifiedpush-java-client
> 
> I will send PR for the following in the next days:
> aerogear-simplepush-java-client
> aerogear-simplepush-server
> aerogear-unifiedpush-server-integration-tests

Please wait until Tadeas merges junit-rule branch first.


> aerogear-unifiedpush-server
> aerogear-helloworld-android
> 
> Did I forget something?
> 
> Thanks!
> Andrea
> 
> 
> 
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Using-the-AeroGear-BOMs-tp7793.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  Thu May 15 07:23:04 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Thu, 15 May 2014 13:23:04 +0200
Subject: [aerogear-dev] UnifiedPush 0.10.3 - release coming soon (WAR
 and OpenShift)
In-Reply-To: <CAAg5f2TE5C=26DMH4KGG4Bux69qvRpG1L+ZNrZ7GiEWcAD-_oA@mail.gmail.com>
References: <CAAg5f2RhVFCrGd90d+9i1+7g+YOvTK5xV8-k_otc3Jr+JOAf3Q@mail.gmail.com>
	<CAD_dpu03M8imCpZAGAkPoTpuM32C8LA2R9aGwUzVWaig+fbnPg@mail.gmail.com>
	<CAAg5f2TE5C=26DMH4KGG4Bux69qvRpG1L+ZNrZ7GiEWcAD-_oA@mail.gmail.com>
Message-ID: <20140515132304.6a40caa9@kapy-ntb-x220>

Might have been caused by QE demanding too much time to bless the release ;-),
however registration snippets for SP in UPS 0.10.3 are now obsolete with
Aerogear JS 1.5.0.

vvv
UPClient = AeroGear.UnifiedPushClient(variantId, variantSecret, unifiedPushUrl
+ "/rest/registry/device");
^^^

What is the plan here? Restage 0.10.3?

Thanks,

Karel

On Mon, 12 May 2014 08:37:34 +0200
Matthias Wessendorf <matzew at apache.org> wrote:

> On Fri, May 9, 2014 at 2:20 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
> > Hi,
> > Tested the WAR : +1
> > Tested the cartridge : +1
> >
> > Just one small remark on the cartridge : In my application list, the label
> > shows 0.10.0 : http://s28.postimg.org/gn8cll1r1/ups1003.png
> > Must be just a property to change in the cartridge.
> >
> 
> that's fine
> 
> 
> >
> >
> >
> >
> >
> > On Thu, May 8, 2014 at 11:52 AM, Matthias Wessendorf <
> > mwessendorf at gmail.com> wrote:
> >
> >> Hi,
> >>
> >> in order to be consistent with the latest Cordova changes name, we did
> >> apply them (and improved GCM exception handling) to the 0.10.x branch as
> >> well. That's the only content of the release:
> >> * Cordova registration snippets match the LATEST (0.5.x) plugin
> >> * GCM exception handling improved
> >>
> >> 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/13
> >>
> >>
> >> If you want to test it - it's simple! Just go ahead and use my fork of
> >> the repo:
> >>
> >> rhc app create --no-git <YOUR COOL APP NAME>
> >> https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.5
> >>
> >>
> >> Let me know the results of your testing;
> >> If I hear nothing bad by Tuesday evening (give it a few more days due to
> >> European holidays), the merges will happen on Wednesday
> >>
> >>
> >> 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
> >
> 
> 
> 


From hbons at redhat.com  Thu May 15 11:19:55 2014
From: hbons at redhat.com (Hylke Bons)
Date: Thu, 15 May 2014 16:19:55 +0100
Subject: [aerogear-dev] First go at stats/activity wireframes
Message-ID: <5374DB1B.9020405@redhat.com>

Hey,

Here's an initial version: 
https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png

I tried to incorporate most wishes expressed in the other thread.

Most notable things:
- Landing page with an overview of stats, most active apps, and error 
messages
- Activity table shows both registration and notification events
- Activity table is per variant, and not all activity on the server. 
Unless there's a usecase to have every event for every app/variant in a 
table I don't think we actually need it. The important thing is to get 
to error messages easily.

Things to do/think about:
- links/entry points to the activity table
- filtering the activity table

This is just the first iteration and we will improve on this.
Let me know what you think.

Thanks,

Hylke

From kpiwko at redhat.com  Thu May 15 11:42:16 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Thu, 15 May 2014 17:42:16 +0200
Subject: [aerogear-dev] UnifiedPush 0.10.3 - release coming soon (WAR
 and OpenShift)
In-Reply-To: <20140515132304.6a40caa9@kapy-ntb-x220>
References: <CAAg5f2RhVFCrGd90d+9i1+7g+YOvTK5xV8-k_otc3Jr+JOAf3Q@mail.gmail.com>
	<CAD_dpu03M8imCpZAGAkPoTpuM32C8LA2R9aGwUzVWaig+fbnPg@mail.gmail.com>
	<CAAg5f2TE5C=26DMH4KGG4Bux69qvRpG1L+ZNrZ7GiEWcAD-_oA@mail.gmail.com>
	<20140515132304.6a40caa9@kapy-ntb-x220>
Message-ID: <20140515174216.142dc107@kapy-ntb-x220>

Looks good to me. Push the beast into the wild!

Unit tests: passed
Integration tests: passed
UI tests: passed
Cart tests: passed
Registration snippet: fixed, now it is valid for Aerogear JS 1.5.0

Karel



On Thu, 15 May 2014 13:23:04 +0200
Karel Piwko <kpiwko at redhat.com> wrote:

> Might have been caused by QE demanding too much time to bless the release ;-),
> however registration snippets for SP in UPS 0.10.3 are now obsolete with
> Aerogear JS 1.5.0.
> 
> vvv
> UPClient = AeroGear.UnifiedPushClient(variantId, variantSecret, unifiedPushUrl
> + "/rest/registry/device");
> ^^^
> 
> What is the plan here? Restage 0.10.3?
> 
> Thanks,
> 
> Karel
> 
> On Mon, 12 May 2014 08:37:34 +0200
> Matthias Wessendorf <matzew at apache.org> wrote:
> 
> > On Fri, May 9, 2014 at 2:20 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> > 
> > > Hi,
> > > Tested the WAR : +1
> > > Tested the cartridge : +1
> > >
> > > Just one small remark on the cartridge : In my application list, the label
> > > shows 0.10.0 : http://s28.postimg.org/gn8cll1r1/ups1003.png
> > > Must be just a property to change in the cartridge.
> > >
> > 
> > that's fine
> > 
> > 
> > >
> > >
> > >
> > >
> > >
> > > On Thu, May 8, 2014 at 11:52 AM, Matthias Wessendorf <
> > > mwessendorf at gmail.com> wrote:
> > >
> > >> Hi,
> > >>
> > >> in order to be consistent with the latest Cordova changes name, we did
> > >> apply them (and improved GCM exception handling) to the 0.10.x branch as
> > >> well. That's the only content of the release:
> > >> * Cordova registration snippets match the LATEST (0.5.x) plugin
> > >> * GCM exception handling improved
> > >>
> > >> 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/13
> > >>
> > >>
> > >> If you want to test it - it's simple! Just go ahead and use my fork of
> > >> the repo:
> > >>
> > >> rhc app create --no-git <YOUR COOL APP NAME>
> > >> https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.5
> > >>
> > >>
> > >> Let me know the results of your testing;
> > >> If I hear nothing bad by Tuesday evening (give it a few more days due to
> > >> European holidays), the merges will happen on Wednesday
> > >>
> > >>
> > >> 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
> > >
> > 
> > 
> > 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From supittma at redhat.com  Thu May 15 11:44:51 2014
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 15 May 2014 11:44:51 -0400
Subject: [aerogear-dev] OAuth2 authotization and Pipe integration
In-Reply-To: <5FC7D59B-B71A-42A6-882E-543076E61C18@gmail.com>
References: <5FC7D59B-B71A-42A6-882E-543076E61C18@gmail.com>
Message-ID: <5374E0F3.8060803@redhat.com>

I don't like it because it moves the concerns of bad accounts, account 
creation, authorization lifecycle error handling into the failure 
method of the pipe callback.  Those concerns don't belong there.

However I am fine with the module refreshing the accesstoken if a 
refresh token is provided.  If an error happens then that is something 
more "in line" with reasonable expectations for a authorized request.


On Thu 15 May 2014 03:56:28 AM EDT, Corinne Krych wrote:
> Hello folks
>
> I?ve been thinking about providing a more fluid integration between authz and pipes.
>
> Right now to read a list of GoogleDrive document, we need to read the pipe in the success callback of authz? requestAccess:
>
>      AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>      _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>           ...
>      }];
>
>      [_restAuthzModule requestAccessSuccess:^(id object) {
>        		 id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>         		 [config setName:@"files"];
>         		 [config setAuthzModule:authzModule]; // inject authz
>       		 }];
>
>     		 [documents read:^(id responseObject) {
>          		// do sth with response
>     		 } failure:^(NSError *error) {
>         			 // when an error occurs...
>     		 }];
>      } failure:^(NSError *error) {
>          NSLog(@"Failure in getting access token");
>      }];
>
> What about if we just initialize authzModule and inject it into pipe. Once the pipe read (or any crud) it will be the pipe that first fetch tokens (or  renew - whaetever is needed) and on success read the pipe. Basically we do the callback chaining internally in the Pipe instead of letting the developer deal with it.
>
>      AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>      _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>           ...
>      }];
>
>      id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>        		 [config setName:@"files"];
>         		 [config setAuthzModule:authzModule]; // inject authz
>      }];
>
>      [documents read:^(id responseObject) {
>          		// do sth with response
>        } failure:^(NSError *error) {
>         			 // when an error occurs...
>      }];
>
> It feels much fluid on the user.
> Doing so we ?force? the app flow to ask token when it needs it, not in advance at startup of app. but i think this is good practice to lazy authz your app.
>
> Thoughts?
>
> Test repo can be found here:
> https://github.com/corinnekrych/aerogear-ios/blob/transparent.refresh/AeroGear-iOS/pipeline/AGRESTPipe.m#L169
> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-145.refresh/GoogleDrive/GoogleDrive/AGViewController.m
>
> ++
> Corinne
> _______________________________________________
> 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 May 15 11:47:58 2014
From: daniel at passos.me (Daniel Passos)
Date: Thu, 15 May 2014 12:47:58 -0300
Subject: [aerogear-dev] Using the AeroGear BOMs
In-Reply-To: <1400075367412-7793.post@n5.nabble.com>
References: <1400075367412-7793.post@n5.nabble.com>
Message-ID: <CAKjsGbusu2FKxBgZNKj84pP8BcM-_Qojv864txTFn1oaiVLtjg@mail.gmail.com>

In Android land => https://gist.github.com/danielpassos/e4a652cc34c0b865504b


On Wed, May 14, 2014 at 10:49 AM, Andrea Vibelli <avibelli at redhat.com>wrote:

> Hi all,
> I have started sending PR to many projects, to make Maven AeroGear projects
> use the brand new BOMs available in Maven Central and now consumable after
> the release of aerogear-misc 0.1.2 on Central.
>
> So far I have sent PR for:
> aerogear-aerodoc-android
> aerogear-android-cookbook
> aerogear-android
> aerogear-android-push
> aerogear-crypto-android-demo
> aerogear-crypto-java
> aerogear-otp-android-demo
> aerogear-otp-java
> aerogear-unifiedpush-java-client
>
> I will send PR for the following in the next days:
> aerogear-simplepush-java-client
> aerogear-simplepush-server
> aerogear-unifiedpush-server-integration-tests
> aerogear-unifiedpush-server
> aerogear-helloworld-android
>
> Did I forget something?
>
> Thanks!
> Andrea
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Using-the-AeroGear-BOMs-tp7793.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/20140515/7e78ab8b/attachment.html 

From tkriz at redhat.com  Thu May 15 11:52:52 2014
From: tkriz at redhat.com (Tadeas Kriz)
Date: Thu, 15 May 2014 17:52:52 +0200
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <CAD_dpu2Me8nQTYaPDiTTMwASWhYvJtXxu9Nnk9f5+r8x55xk4A@mail.gmail.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
	<CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>
	<CAD_dpu2Me8nQTYaPDiTTMwASWhYvJtXxu9Nnk9f5+r8x55xk4A@mail.gmail.com>
Message-ID: <A251A24A-A263-48C8-B09B-A4E4F18714F8@redhat.com>

Hey,

I?ve found out a problem with the release. The .pom file is missing and because of that maven cannot resolve its dependencies resulting in `NoClassDefFoundError` in runtime. When I go to [1], I can click on the `unifiedpush-java-client-0.6.0.pom` and it?s shown properly. But when I run `mvn dependency:tree`, maven complains with:

`[WARNING] The POM for org.jboss.aerogear:unifiedpush-java-client:jar:0.6.0 is missing, no dependency information available`

In the directory on maven central [2], the .pom [3] file seems to be present, but try to open it. 404 will open the door.

I think I saw something similar happened before with some other release of aerogear library to maven central, but I can?t recall when and what was the solution. Any ideas on this?

Thanks.

1 - http://search.maven.org/#artifactdetails%7Corg.jboss.aerogear%7Cunifiedpush-java-client%7C0.6.0%7Cjar
2 - http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/
3 - http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom

?
Tadeas Kriz

On 14 May 2014, at 14:25, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Thx Tadeas !
> 
> The release button has been pressed ! 
> Now it's just a matter to sync with Maven Central.
> 
> Sebi
> 
> 
> On Wed, May 14, 2014 at 1:06 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
> Hey,
> 
> I?ve updated and run unifiedpush server integration tests with the Java Sender 0.6.0 and it worked without any problem. Also the tests on travis are green.
> 
> ?
> Tadeas Kriz
> 
> On 07 May 2014, at 18:30, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
>> Hi folks,
>> The AeroGear UnifiedPush Java Client 0.6.0 has been staged : 
>> 
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
>> 
>> This release contains the following changes : 
>> 
>> * Proxy server configuration
>> * AGPUSH-559 (HTTPS connection support)
>> * AGPUSH-619 (fix on the mismatch of the TTL payload)
>> 
>> I plan to release to maven central on Friday, so please test and report any issues ! 
>> 
>> 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
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140515/088427a6/attachment.html 

From corinnekrych at gmail.com  Thu May 15 12:08:03 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 15 May 2014 18:08:03 +0200
Subject: [aerogear-dev] OAuth2 authotization and Pipe integration
In-Reply-To: <5374E0F3.8060803@redhat.com>
References: <5FC7D59B-B71A-42A6-882E-543076E61C18@gmail.com>
	<5374E0F3.8060803@redhat.com>
Message-ID: <F4B6F67E-01EA-46A6-8A7F-EA115BD5708C@gmail.com>

So seamless refreshing token but declarative token initial request. Right?
#agreed seamless refresh
decalrative auhz request and revoke request.
If we all agree (JS included) I?ll create an iOS JIRA ticket and go for it.

JS folks, wdyt?

++
Corinne
On 15 May 2014, at 17:44, Summers Pittman <supittma at redhat.com> wrote:

> I don't like it because it moves the concerns of bad accounts, account creation, authorization lifecycle error handling into the failure method of the pipe callback.  Those concerns don't belong there.
> 
> However I am fine with the module refreshing the accesstoken if a refresh token is provided.  If an error happens then that is something more "in line" with reasonable expectations for a authorized request.
> 
> 
> On Thu 15 May 2014 03:56:28 AM EDT, Corinne Krych wrote:
>> Hello folks
>> 
>> I?ve been thinking about providing a more fluid integration between authz and pipes.
>> 
>> Right now to read a list of GoogleDrive document, we need to read the pipe in the success callback of authz? requestAccess:
>> 
>>     AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>>     _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>>          ...
>>     }];
>> 
>>     [_restAuthzModule requestAccessSuccess:^(id object) {
>>       		 id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>>        		 [config setName:@"files"];
>>        		 [config setAuthzModule:authzModule]; // inject authz
>>      		 }];
>> 
>>    		 [documents read:^(id responseObject) {
>>         		// do sth with response
>>    		 } failure:^(NSError *error) {
>>        			 // when an error occurs...
>>    		 }];
>>     } failure:^(NSError *error) {
>>         NSLog(@"Failure in getting access token");
>>     }];
>> 
>> What about if we just initialize authzModule and inject it into pipe. Once the pipe read (or any crud) it will be the pipe that first fetch tokens (or  renew - whaetever is needed) and on success read the pipe. Basically we do the callback chaining internally in the Pipe instead of letting the developer deal with it.
>> 
>>     AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>>     _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>>          ...
>>     }];
>> 
>>     id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>>       		 [config setName:@"files"];
>>        		 [config setAuthzModule:authzModule]; // inject authz
>>     }];
>> 
>>     [documents read:^(id responseObject) {
>>         		// do sth with response
>>       } failure:^(NSError *error) {
>>        			 // when an error occurs...
>>     }];
>> 
>> It feels much fluid on the user.
>> Doing so we ?force? the app flow to ask token when it needs it, not in advance at startup of app. but i think this is good practice to lazy authz your app.
>> 
>> Thoughts?
>> 
>> Test repo can be found here:
>> https://github.com/corinnekrych/aerogear-ios/blob/transparent.refresh/AeroGear-iOS/pipeline/AGRESTPipe.m#L169
>> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-145.refresh/GoogleDrive/GoogleDrive/AGViewController.m
>> 
>> ++
>> Corinne
>> _______________________________________________
>> 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  Thu May 15 12:12:17 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Thu, 15 May 2014 12:12:17 -0400
Subject: [aerogear-dev] OAuth2 authotization and Pipe integration
In-Reply-To: <F4B6F67E-01EA-46A6-8A7F-EA115BD5708C@gmail.com>
References: <5FC7D59B-B71A-42A6-882E-543076E61C18@gmail.com>
	<5374E0F3.8060803@redhat.com>
	<F4B6F67E-01EA-46A6-8A7F-EA115BD5708C@gmail.com>
Message-ID: <1B826249-94E8-4544-84B5-9F5488278890@redhat.com>

for js we don?t have refresh tokens,  for security reasons.


I know with googles js api,  they do a background refresh( iframe stuff ).


go for it


On May 15, 2014, at 12:08 PM, Corinne Krych <corinnekrych at gmail.com> wrote:

> So seamless refreshing token but declarative token initial request. Right?
> #agreed seamless refresh
> decalrative auhz request and revoke request.
> If we all agree (JS included) I?ll create an iOS JIRA ticket and go for it.
> 
> JS folks, wdyt?
> 
> ++
> Corinne
> On 15 May 2014, at 17:44, Summers Pittman <supittma at redhat.com> wrote:
> 
>> I don't like it because it moves the concerns of bad accounts, account creation, authorization lifecycle error handling into the failure method of the pipe callback.  Those concerns don't belong there.
>> 
>> However I am fine with the module refreshing the accesstoken if a refresh token is provided.  If an error happens then that is something more "in line" with reasonable expectations for a authorized request.
>> 
>> 
>> On Thu 15 May 2014 03:56:28 AM EDT, Corinne Krych wrote:
>>> Hello folks
>>> 
>>> I?ve been thinking about providing a more fluid integration between authz and pipes.
>>> 
>>> Right now to read a list of GoogleDrive document, we need to read the pipe in the success callback of authz? requestAccess:
>>> 
>>>    AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>>>    _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>>>         ...
>>>    }];
>>> 
>>>    [_restAuthzModule requestAccessSuccess:^(id object) {
>>>      		 id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>>>       		 [config setName:@"files"];
>>>       		 [config setAuthzModule:authzModule]; // inject authz
>>>     		 }];
>>> 
>>>   		 [documents read:^(id responseObject) {
>>>        		// do sth with response
>>>   		 } failure:^(NSError *error) {
>>>       			 // when an error occurs...
>>>   		 }];
>>>    } failure:^(NSError *error) {
>>>        NSLog(@"Failure in getting access token");
>>>    }];
>>> 
>>> What about if we just initialize authzModule and inject it into pipe. Once the pipe read (or any crud) it will be the pipe that first fetch tokens (or  renew - whaetever is needed) and on success read the pipe. Basically we do the callback chaining internally in the Pipe instead of letting the developer deal with it.
>>> 
>>>    AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>>>    _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>>>         ...
>>>    }];
>>> 
>>>    id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>>>      		 [config setName:@"files"];
>>>       		 [config setAuthzModule:authzModule]; // inject authz
>>>    }];
>>> 
>>>    [documents read:^(id responseObject) {
>>>        		// do sth with response
>>>      } failure:^(NSError *error) {
>>>       			 // when an error occurs...
>>>    }];
>>> 
>>> It feels much fluid on the user.
>>> Doing so we ?force? the app flow to ask token when it needs it, not in advance at startup of app. but i think this is good practice to lazy authz your app.
>>> 
>>> Thoughts?
>>> 
>>> Test repo can be found here:
>>> https://github.com/corinnekrych/aerogear-ios/blob/transparent.refresh/AeroGear-iOS/pipeline/AGRESTPipe.m#L169
>>> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-145.refresh/GoogleDrive/GoogleDrive/AGViewController.m
>>> 
>>> ++
>>> Corinne
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> 
>> --
>> Summers Pittman
>>>> Phone:404 941 4698
>>>> Java is my crack.
>> 
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From scm.blanc at gmail.com  Thu May 15 12:19:08 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 15 May 2014 18:19:08 +0200
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <A251A24A-A263-48C8-B09B-A4E4F18714F8@redhat.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
	<CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>
	<CAD_dpu2Me8nQTYaPDiTTMwASWhYvJtXxu9Nnk9f5+r8x55xk4A@mail.gmail.com>
	<A251A24A-A263-48C8-B09B-A4E4F18714F8@redhat.com>
Message-ID: <CAD_dpu0Y6toYaz0nRL1Q2GDCJCjiW9KHF5_FutVFXJVFT4GiXQ@mail.gmail.com>

Strange,
I can open [3]
http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pomwith
success.
Could you just retry ? Maybe temp issue in maven central



On Thu, May 15, 2014 at 5:52 PM, Tadeas Kriz <tkriz at redhat.com> wrote:

> Hey,
>
> I?ve found out a problem with the release. The .pom file is missing and
> because of that maven cannot resolve its dependencies resulting in
> `NoClassDefFoundError` in runtime. When I go to [1], I can click on the
> `unifiedpush-java-client-0.6.0.pom` and it?s shown properly. But when I run
> `mvn dependency:tree`, maven complains with:
>
> `[WARNING] The POM for
> org.jboss.aerogear:unifiedpush-java-client:jar:0.6.0 is missing, no
> dependency information available`
>
> In the directory on maven central [2], the .pom [3] file seems to be
> present, but try to open it. 404 will open the door.
>
> I think I saw something similar happened before with some other release of
> aerogear library to maven central, but I can?t recall when and what was the
> solution. Any ideas on this?
>
> Thanks.
>
> 1 -
> http://search.maven.org/#artifactdetails%7Corg.jboss.aerogear%7Cunifiedpush-java-client%7C0.6.0%7Cjar
> 2 -
> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/
> 3 -
> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom
>
> ?
> Tadeas Kriz
>
> On 14 May 2014, at 14:25, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> Thx Tadeas !
>
> The release button has been pressed !
> Now it's just a matter to sync with Maven Central.
>
> Sebi
>
>
> On Wed, May 14, 2014 at 1:06 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
>
>> Hey,
>>
>> I?ve updated and run unifiedpush server integration tests with the Java
>> Sender 0.6.0 and it worked without any problem. Also the tests on travis
>> are green.
>>
>> ?
>> Tadeas Kriz
>>
>> On 07 May 2014, at 18:30, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>
>> Hi folks,
>> The AeroGear UnifiedPush Java Client 0.6.0 has been staged :
>>
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
>>
>> This release contains the following changes :
>>
>> * Proxy server configuration
>> * AGPUSH-559 (HTTPS connection support)
>> * AGPUSH-619 (fix on the mismatch of the TTL payload)
>>
>> I plan to release to maven central on Friday, so please test and report
>> any issues !
>>
>> 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
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140515/9c5fc40d/attachment.html 

From tkriz at redhat.com  Thu May 15 12:22:07 2014
From: tkriz at redhat.com (Tadeas Kriz)
Date: Thu, 15 May 2014 18:22:07 +0200
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <CAD_dpu0Y6toYaz0nRL1Q2GDCJCjiW9KHF5_FutVFXJVFT4GiXQ@mail.gmail.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
	<CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>
	<CAD_dpu2Me8nQTYaPDiTTMwASWhYvJtXxu9Nnk9f5+r8x55xk4A@mail.gmail.com>
	<A251A24A-A263-48C8-B09B-A4E4F18714F8@redhat.com>
	<CAD_dpu0Y6toYaz0nRL1Q2GDCJCjiW9KHF5_FutVFXJVFT4GiXQ@mail.gmail.com>
Message-ID: <17D1D172-847F-4135-A037-6F0D011D6542@redhat.com>

I did retry it, same outcome.



Doesn?t work with ?wget? either.

?
Tadeas Kriz

On 15 May 2014, at 18:19, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Strange,
> I can open [3] http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom with success.
> Could you just retry ? Maybe temp issue in maven central 
> 
> 
> 
> On Thu, May 15, 2014 at 5:52 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
> Hey,
> 
> I?ve found out a problem with the release. The .pom file is missing and because of that maven cannot resolve its dependencies resulting in `NoClassDefFoundError` in runtime. When I go to [1], I can click on the `unifiedpush-java-client-0.6.0.pom` and it?s shown properly. But when I run `mvn dependency:tree`, maven complains with:
> 
> `[WARNING] The POM for org.jboss.aerogear:unifiedpush-java-client:jar:0.6.0 is missing, no dependency information available`
> 
> In the directory on maven central [2], the .pom [3] file seems to be present, but try to open it. 404 will open the door.
> 
> I think I saw something similar happened before with some other release of aerogear library to maven central, but I can?t recall when and what was the solution. Any ideas on this?
> 
> Thanks.
> 
> 1 - http://search.maven.org/#artifactdetails%7Corg.jboss.aerogear%7Cunifiedpush-java-client%7C0.6.0%7Cjar
> 2 - http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/
> 3 - http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom
> 
> ?
> Tadeas Kriz
> 
> On 14 May 2014, at 14:25, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
>> Thx Tadeas !
>> 
>> The release button has been pressed ! 
>> Now it's just a matter to sync with Maven Central.
>> 
>> Sebi
>> 
>> 
>> On Wed, May 14, 2014 at 1:06 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
>> Hey,
>> 
>> I?ve updated and run unifiedpush server integration tests with the Java Sender 0.6.0 and it worked without any problem. Also the tests on travis are green.
>> 
>> ?
>> Tadeas Kriz
>> 
>> On 07 May 2014, at 18:30, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>> 
>>> Hi folks,
>>> The AeroGear UnifiedPush Java Client 0.6.0 has been staged : 
>>> 
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
>>> 
>>> This release contains the following changes : 
>>> 
>>> * Proxy server configuration
>>> * AGPUSH-559 (HTTPS connection support)
>>> * AGPUSH-619 (fix on the mismatch of the TTL payload)
>>> 
>>> I plan to release to maven central on Friday, so please test and report any issues ! 
>>> 
>>> 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
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140515/b26f1adf/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2014-05-15 at 18.21.10.png
Type: image/png
Size: 83281 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140515/b26f1adf/attachment-0001.png 

From mwessendorf at gmail.com  Thu May 15 12:21:54 2014
From: mwessendorf at gmail.com (mwessendorf)
Date: Thu, 15 May 2014 09:21:54 -0700 (PDT)
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <5374DB1B.9020405@redhat.com>
References: <5374DB1B.9020405@redhat.com>
Message-ID: <1400170914549-7812.post@n5.nabble.com>

Hello!

a few comments:
* landing-page: A dashboard is nice! But as said on the initial thread,
let's focus on the stats around Push messages. If time allows we can define
a 'dashboard' a bit more (e.g. adding notes 'how often an app was opened on
a mobile device', etc) 

*activity table: Based on our IRC chat in the afternoon, you already updated
it to only show the push messages. thanks!

* Table per variant; I am not sure... I think as a user I just want to
initially see a table of all the messages I send (per application). Clicking
on the details (expanded row), I had in mind there to show more details,
like

2000 receivers for Variant-A       -      SUCCESS
3000 receivers for Variant-B       -      FAILURE SENDING
4000 receivers for Variant-C       -      SUCCESS







Hylke Bons wrote
> Hey,
> 
> Here's an initial version: 
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> 
> I tried to incorporate most wishes expressed in the other thread.
> 
> Most notable things:
> - Landing page with an overview of stats, most active apps, and error 
> messages
> - Activity table shows both registration and notification events
> - Activity table is per variant, and not all activity on the server. 
> Unless there's a usecase to have every event for every app/variant in a 
> table I don't think we actually need it. The important thing is to get 
> to error messages easily.
> 
> Things to do/think about:
> - links/entry points to the activity table
> - filtering the activity table
> 
> This is just the first iteration and we will improve on this.
> Let me know what you think.
> 
> Thanks,
> 
> Hylke
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-First-go-at-stats-activity-wireframes-tp7804p7812.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Thu May 15 12:25:39 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 15 May 2014 18:25:39 +0200
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <17D1D172-847F-4135-A037-6F0D011D6542@redhat.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
	<CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>
	<CAD_dpu2Me8nQTYaPDiTTMwASWhYvJtXxu9Nnk9f5+r8x55xk4A@mail.gmail.com>
	<A251A24A-A263-48C8-B09B-A4E4F18714F8@redhat.com>
	<CAD_dpu0Y6toYaz0nRL1Q2GDCJCjiW9KHF5_FutVFXJVFT4GiXQ@mail.gmail.com>
	<17D1D172-847F-4135-A037-6F0D011D6542@redhat.com>
Message-ID: <CAD_dpu2ZwzRm2vgHWktRZj8Z2Yex47XwU8ySbPKQp3im0Go=nQ@mail.gmail.com>

[image: sender]

Could anyone else try ?



On Thu, May 15, 2014 at 6:22 PM, Tadeas Kriz <tkriz at redhat.com> wrote:

> I did retry it, same outcome.
>
>
> Doesn?t work with ?wget? either.
>
> ?
> Tadeas Kriz
>
> On 15 May 2014, at 18:19, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> Strange,
> I can open [3]
> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pomwith success.
> Could you just retry ? Maybe temp issue in maven central
>
>
>
> On Thu, May 15, 2014 at 5:52 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
>
>> Hey,
>>
>> I?ve found out a problem with the release. The .pom file is missing and
>> because of that maven cannot resolve its dependencies resulting in
>> `NoClassDefFoundError` in runtime. When I go to [1], I can click on the
>> `unifiedpush-java-client-0.6.0.pom` and it?s shown properly. But when I run
>> `mvn dependency:tree`, maven complains with:
>>
>> `[WARNING] The POM for
>> org.jboss.aerogear:unifiedpush-java-client:jar:0.6.0 is missing, no
>> dependency information available`
>>
>> In the directory on maven central [2], the .pom [3] file seems to be
>> present, but try to open it. 404 will open the door.
>>
>> I think I saw something similar happened before with some other release
>> of aerogear library to maven central, but I can?t recall when and what was
>> the solution. Any ideas on this?
>>
>> Thanks.
>>
>> 1 -
>> http://search.maven.org/#artifactdetails%7Corg.jboss.aerogear%7Cunifiedpush-java-client%7C0.6.0%7Cjar
>> 2 -
>> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/
>> 3 -
>> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom
>>
>> ?
>> Tadeas Kriz
>>
>> On 14 May 2014, at 14:25, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>
>> Thx Tadeas !
>>
>> The release button has been pressed !
>> Now it's just a matter to sync with Maven Central.
>>
>> Sebi
>>
>>
>> On Wed, May 14, 2014 at 1:06 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
>>
>>> Hey,
>>>
>>> I?ve updated and run unifiedpush server integration tests with the Java
>>> Sender 0.6.0 and it worked without any problem. Also the tests on travis
>>> are green.
>>>
>>> ?
>>> Tadeas Kriz
>>>
>>> On 07 May 2014, at 18:30, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>
>>> Hi folks,
>>> The AeroGear UnifiedPush Java Client 0.6.0 has been staged :
>>>
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
>>>
>>> This release contains the following changes :
>>>
>>> * Proxy server configuration
>>> * AGPUSH-559 (HTTPS connection support)
>>> * AGPUSH-619 (fix on the mismatch of the TTL payload)
>>>
>>> I plan to release to maven central on Friday, so please test and report
>>> any issues !
>>>
>>> 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
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140515/d0891812/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2014-05-15 at 18.21.10.png
Type: image/png
Size: 83281 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140515/d0891812/attachment-0001.png 

From daniel at passos.me  Thu May 15 12:46:15 2014
From: daniel at passos.me (Daniel Passos)
Date: Thu, 15 May 2014 13:46:15 -0300
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <CAD_dpu2ZwzRm2vgHWktRZj8Z2Yex47XwU8ySbPKQp3im0Go=nQ@mail.gmail.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
	<CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>
	<CAD_dpu2Me8nQTYaPDiTTMwASWhYvJtXxu9Nnk9f5+r8x55xk4A@mail.gmail.com>
	<A251A24A-A263-48C8-B09B-A4E4F18714F8@redhat.com>
	<CAD_dpu0Y6toYaz0nRL1Q2GDCJCjiW9KHF5_FutVFXJVFT4GiXQ@mail.gmail.com>
	<17D1D172-847F-4135-A037-6F0D011D6542@redhat.com>
	<CAD_dpu2ZwzRm2vgHWktRZj8Z2Yex47XwU8ySbPKQp3im0Go=nQ@mail.gmail.com>
Message-ID: <CAKjsGbv3SNJw4KZPXUsMrL+x3EuP3s2VoUT3qV_7at0gy6-zJQ@mail.gmail.com>

Works for me => http://take.ms/80QV2


On Thu, May 15, 2014 at 1:25 PM, Sebastien Blanc <scm.blanc at gmail.com>wrote:

> [image: sender]
>
> Could anyone else try ?
>
>
>
> On Thu, May 15, 2014 at 6:22 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
>
>> I did retry it, same outcome.
>>
>>
>> Doesn?t work with ?wget? either.
>>
>> ?
>> Tadeas Kriz
>>
>> On 15 May 2014, at 18:19, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>
>> Strange,
>> I can open [3]
>> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pomwith success.
>> Could you just retry ? Maybe temp issue in maven central
>>
>>
>>
>> On Thu, May 15, 2014 at 5:52 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
>>
>>> Hey,
>>>
>>> I?ve found out a problem with the release. The .pom file is missing and
>>> because of that maven cannot resolve its dependencies resulting in
>>> `NoClassDefFoundError` in runtime. When I go to [1], I can click on the
>>> `unifiedpush-java-client-0.6.0.pom` and it?s shown properly. But when I run
>>> `mvn dependency:tree`, maven complains with:
>>>
>>> `[WARNING] The POM for
>>> org.jboss.aerogear:unifiedpush-java-client:jar:0.6.0 is missing, no
>>> dependency information available`
>>>
>>> In the directory on maven central [2], the .pom [3] file seems to be
>>> present, but try to open it. 404 will open the door.
>>>
>>> I think I saw something similar happened before with some other release
>>> of aerogear library to maven central, but I can?t recall when and what was
>>> the solution. Any ideas on this?
>>>
>>> Thanks.
>>>
>>> 1 -
>>> http://search.maven.org/#artifactdetails%7Corg.jboss.aerogear%7Cunifiedpush-java-client%7C0.6.0%7Cjar
>>> 2 -
>>> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/
>>> 3 -
>>> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom
>>>
>>> ?
>>> Tadeas Kriz
>>>
>>> On 14 May 2014, at 14:25, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>
>>> Thx Tadeas !
>>>
>>> The release button has been pressed !
>>> Now it's just a matter to sync with Maven Central.
>>>
>>> Sebi
>>>
>>>
>>> On Wed, May 14, 2014 at 1:06 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
>>>
>>>> Hey,
>>>>
>>>> I?ve updated and run unifiedpush server integration tests with the Java
>>>> Sender 0.6.0 and it worked without any problem. Also the tests on travis
>>>> are green.
>>>>
>>>> ?
>>>> Tadeas Kriz
>>>>
>>>> On 07 May 2014, at 18:30, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>>
>>>> Hi folks,
>>>> The AeroGear UnifiedPush Java Client 0.6.0 has been staged :
>>>>
>>>>
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
>>>>
>>>> This release contains the following changes :
>>>>
>>>> * Proxy server configuration
>>>> * AGPUSH-559 (HTTPS connection support)
>>>> * AGPUSH-619 (fix on the mismatch of the TTL payload)
>>>>
>>>> I plan to release to maven central on Friday, so please test and report
>>>> any issues !
>>>>
>>>> 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
>>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140515/0c22fa21/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2014-05-15 at 18.21.10.png
Type: image/png
Size: 83281 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140515/0c22fa21/attachment-0001.png 

From edewit at redhat.com  Thu May 15 14:02:40 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 15 May 2014 20:02:40 +0200
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <CAKjsGbv3SNJw4KZPXUsMrL+x3EuP3s2VoUT3qV_7at0gy6-zJQ@mail.gmail.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
	<CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>
	<CAD_dpu2Me8nQTYaPDiTTMwASWhYvJtXxu9Nnk9f5+r8x55xk4A@mail.gmail.com>
	<A251A24A-A263-48C8-B09B-A4E4F18714F8@redhat.com>
	<CAD_dpu0Y6toYaz0nRL1Q2GDCJCjiW9KHF5_FutVFXJVFT4GiXQ@mail.gmail.com>
	<17D1D172-847F-4135-A037-6F0D011D6542@redhat.com>
	<CAD_dpu2ZwzRm2vgHWktRZj8Z2Yex47XwU8ySbPKQp3im0Go=nQ@mail.gmail.com>
	<CAKjsGbv3SNJw4KZPXUsMrL+x3EuP3s2VoUT3qV_7at0gy6-zJQ@mail.gmail.com>
Message-ID: <67E0D512-6321-4882-9C28-28311D30D2A7@redhat.com>

works for me as well

On 15 May,2014, at 18:46 , Daniel Passos <daniel at passos.me> wrote:

> Works for me => http://take.ms/80QV2
> 
> 
> On Thu, May 15, 2014 at 1:25 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
> 
> Could anyone else try ? 
> 
> 
> 
> On Thu, May 15, 2014 at 6:22 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
> I did retry it, same outcome.
> 
> <Screen Shot 2014-05-15 at 18.21.10.png>
> 
> Doesn?t work with ?wget? either.
> 
> ?
> Tadeas Kriz
> 
> On 15 May 2014, at 18:19, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
>> Strange,
>> I can open [3] http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom with success.
>> Could you just retry ? Maybe temp issue in maven central 
>> 
>> 
>> 
>> On Thu, May 15, 2014 at 5:52 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
>> Hey,
>> 
>> I?ve found out a problem with the release. The .pom file is missing and because of that maven cannot resolve its dependencies resulting in `NoClassDefFoundError` in runtime. When I go to [1], I can click on the `unifiedpush-java-client-0.6.0.pom` and it?s shown properly. But when I run `mvn dependency:tree`, maven complains with:
>> 
>> `[WARNING] The POM for org.jboss.aerogear:unifiedpush-java-client:jar:0.6.0 is missing, no dependency information available`
>> 
>> In the directory on maven central [2], the .pom [3] file seems to be present, but try to open it. 404 will open the door.
>> 
>> I think I saw something similar happened before with some other release of aerogear library to maven central, but I can?t recall when and what was the solution. Any ideas on this?
>> 
>> Thanks.
>> 
>> 1 - http://search.maven.org/#artifactdetails%7Corg.jboss.aerogear%7Cunifiedpush-java-client%7C0.6.0%7Cjar
>> 2 - http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/
>> 3 - http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom
>> 
>> ?
>> Tadeas Kriz
>> 
>> On 14 May 2014, at 14:25, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>> 
>>> Thx Tadeas !
>>> 
>>> The release button has been pressed ! 
>>> Now it's just a matter to sync with Maven Central.
>>> 
>>> Sebi
>>> 
>>> 
>>> On Wed, May 14, 2014 at 1:06 PM, Tadeas Kriz <tkriz at redhat.com> wrote:
>>> Hey,
>>> 
>>> I?ve updated and run unifiedpush server integration tests with the Java Sender 0.6.0 and it worked without any problem. Also the tests on travis are green.
>>> 
>>> ?
>>> Tadeas Kriz
>>> 
>>> On 07 May 2014, at 18:30, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>> 
>>>> Hi folks,
>>>> The AeroGear UnifiedPush Java Client 0.6.0 has been staged : 
>>>> 
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
>>>> 
>>>> This release contains the following changes : 
>>>> 
>>>> * Proxy server configuration
>>>> * AGPUSH-559 (HTTPS connection support)
>>>> * AGPUSH-619 (fix on the mismatch of the TTL payload)
>>>> 
>>>> I plan to release to maven central on Friday, so please test and report any issues ! 
>>>> 
>>>> 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
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140515/2f930bb1/attachment.html 

From mwessendorf at gmail.com  Thu May 15 14:06:35 2014
From: mwessendorf at gmail.com (mwessendorf)
Date: Thu, 15 May 2014 11:06:35 -0700 (PDT)
Subject: [aerogear-dev] Java Sender 0.6.0 Release
In-Reply-To: <CAD_dpu0Y6toYaz0nRL1Q2GDCJCjiW9KHF5_FutVFXJVFT4GiXQ@mail.gmail.com>
References: <CAD_dpu3a3_Mo1CPzm4PJW2XnDjX2n-yeZO2i0Kmi2XPFnR8YNA@mail.gmail.com>
	<CA320FF1-326A-48FB-993E-904B71AD3AAF@redhat.com>
	<CAD_dpu2Me8nQTYaPDiTTMwASWhYvJtXxu9Nnk9f5+r8x55xk4A@mail.gmail.com>
	<A251A24A-A263-48C8-B09B-A4E4F18714F8@redhat.com>
	<CAD_dpu0Y6toYaz0nRL1Q2GDCJCjiW9KHF5_FutVFXJVFT4GiXQ@mail.gmail.com>
Message-ID: <1400177195902-7817.post@n5.nabble.com>

searched on maven central:
http://search.maven.org/#artifactdetails%7Corg.jboss.aerogear%7Cunifiedpush-java-client%7C0.6.0%7Cjar

and I do see the .pom file as well:
http://search.maven.org/remotecontent?filepath=org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom

Greetings,
Matthias


Sebastien Blanc wrote
> Strange,
> I can open [3]
> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pomwith
> success.
> Could you just retry ? Maybe temp issue in maven central
> 
> 
> 
> On Thu, May 15, 2014 at 5:52 PM, Tadeas Kriz &lt;

> tkriz@

> &gt; wrote:
> 
>> Hey,
>>
>> I?ve found out a problem with the release. The .pom file is missing and
>> because of that maven cannot resolve its dependencies resulting in
>> `NoClassDefFoundError` in runtime. When I go to [1], I can click on the
>> `unifiedpush-java-client-0.6.0.pom` and it?s shown properly. But when I
>> run
>> `mvn dependency:tree`, maven complains with:
>>
>> `[WARNING] The POM for
>> org.jboss.aerogear:unifiedpush-java-client:jar:0.6.0 is missing, no
>> dependency information available`
>>
>> In the directory on maven central [2], the .pom [3] file seems to be
>> present, but try to open it. 404 will open the door.
>>
>> I think I saw something similar happened before with some other release
>> of
>> aerogear library to maven central, but I can?t recall when and what was
>> the
>> solution. Any ideas on this?
>>
>> Thanks.
>>
>> 1 -
>> http://search.maven.org/#artifactdetails%7Corg.jboss.aerogear%7Cunifiedpush-java-client%7C0.6.0%7Cjar
>> 2 -
>> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/
>> 3 -
>> http://repo.maven.apache.org/maven2/org/jboss/aerogear/unifiedpush-java-client/0.6.0/unifiedpush-java-client-0.6.0.pom
>>
>> ?
>> Tadeas Kriz
>>
>> On 14 May 2014, at 14:25, Sebastien Blanc &lt;

> scm.blanc@

> &gt; wrote:
>>
>> Thx Tadeas !
>>
>> The release button has been pressed !
>> Now it's just a matter to sync with Maven Central.
>>
>> Sebi
>>
>>
>> On Wed, May 14, 2014 at 1:06 PM, Tadeas Kriz &lt;

> tkriz@

> &gt; wrote:
>>
>>> Hey,
>>>
>>> I?ve updated and run unifiedpush server integration tests with the Java
>>> Sender 0.6.0 and it worked without any problem. Also the tests on travis
>>> are green.
>>>
>>> ?
>>> Tadeas Kriz
>>>
>>> On 07 May 2014, at 18:30, Sebastien Blanc &lt;

> scm.blanc@

> &gt; wrote:
>>>
>>> Hi folks,
>>> The AeroGear UnifiedPush Java Client 0.6.0 has been staged :
>>>
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-3172
>>>
>>> This release contains the following changes :
>>>
>>> * Proxy server configuration
>>> * AGPUSH-559 (HTTPS connection support)
>>> * AGPUSH-619 (fix on the mismatch of the TTL payload)
>>>
>>> I plan to release to maven central on Friday, so please test and report
>>> any issues !
>>>
>>> Sebi
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> 

> aerogear-dev at .jboss

>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> 

> aerogear-dev at .jboss

>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> 

> aerogear-dev at .jboss

>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> 

> aerogear-dev at .jboss

>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Java-Sender-0-6-0-Release-tp7714p7817.html
Sent from the aerogear-dev mailing list archive at Nabble.com.


From mwessendorf at gmail.com  Fri May 16 06:14:56 2014
From: mwessendorf at gmail.com (Matthias Wessendorf)
Date: Fri, 16 May 2014 12:14:56 +0200
Subject: [aerogear-dev] [ANN] - UPS 0.10.3 is out
Message-ID: <CAAg5f2RHzeLB924Jprjj3r2x2Zm6xZrg4Dmjs6z3zsCHLZfDrg@mail.gmail.com>

Hi,

based on last weeks testing, I have released the 0.10.3 version of UPS to
bintray and OpenShift online.

-Matthias


On Thu, May 8, 2014 at 11:52 AM, Matthias Wessendorf
<mwessendorf at gmail.com>wrote:

> Hi,
>
> in order to be consistent with the latest Cordova changes name, we did
> apply them (and improved GCM exception handling) to the 0.10.x branch as
> well. That's the only content of the release:
> * Cordova registration snippets match the LATEST (0.5.x) plugin
> * GCM exception handling improved
>
> 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/13
>
>
> If you want to test it - it's simple! Just go ahead and use my fork of the
> repo:
>
> rhc app create --no-git <YOUR COOL APP NAME>
> https://cartreflect-claytondev.rhcloud.com/reflect?github=matzew/openshift-origin-cartridge-aerogear-pushmysql-5.5
>
>
> Let me know the results of your testing;
> If I hear nothing bad by Tuesday evening (give it a few more days due to
> European holidays), the merges will happen on Wednesday
>
>
> 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/20140516/8ddcb55f/attachment-0001.html 

From mwessendorf at gmail.com  Fri May 16 07:11:22 2014
From: mwessendorf at gmail.com (mwessendorf)
Date: Fri, 16 May 2014 04:11:22 -0700 (PDT)
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <1400170914549-7812.post@n5.nabble.com>
References: <5374DB1B.9020405@redhat.com>
	<1400170914549-7812.post@n5.nabble.com>
Message-ID: <1400238682421-7819.post@n5.nabble.com>

Note: On IRC Hylke shared a new version:
https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png

I am not 100% sure on the "Last error" thing, but perhaps we can find
something to display there.

After thinking about it, Hylke - any comment on the below ?


mwessendorf wrote
> * Table per variant; I am not sure... I think as a user I just want to
> initially see a table of all the messages I send (per application).
> Clicking on the details (expanded row), I had in mind there to show more
> details, like
> 
> 2000 receivers for Variant-A       -      SUCCESS
> 3000 receivers for Variant-B       -      FAILURE SENDING
> 4000 receivers for Variant-C       -      SUCCESS







--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-First-go-at-stats-activity-wireframes-tp7804p7819.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Fri May 16 08:09:08 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 16 May 2014 14:09:08 +0200
Subject: [aerogear-dev] Keycloak integration
In-Reply-To: <CAAg5f2Tz2Qp91mtJ+tnVdbJHv1OZ516eoGgooX+eziq9Q9zDjg@mail.gmail.com>
References: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
	<CAAg5f2QQpkXSv7NBbC02=FqgbHt3GTQNSk9-KcWOZL-siS7JEQ@mail.gmail.com>
	<CAAg5f2T+nZRhqwHSSWBCugOQ0aqLp8mhxxT7rcfG4iXNFSnNLQ@mail.gmail.com>
	<CAAg5f2Tz2Qp91mtJ+tnVdbJHv1OZ516eoGgooX+eziq9Q9zDjg@mail.gmail.com>
Message-ID: <CAD_dpu3m+YRy-=SZbXsVfzC_qKwEMoT5Om2xx6iiY82_Y1WcDw@mail.gmail.com>

In addition to that I would like to mention that we rebased the Keycloak
work from master into the Angular/UI Overhaul migration branch  , it's
currently on this branch :

https://github.com/aerogear/aerogear-unifiedpush-server/tree/angular_keycloak

To make testing easier a bundle (a not yet optimized) Console in the webapp
folder.

Sebi





On Thu, May 15, 2014 at 11:20 AM, Matthias Wessendorf <mwessendorf at gmail.com
> wrote:

> this got merged;
>
> I have update the EPIC for this task:
> https://issues.jboss.org/browse/AGPUSH-568
>
>
> On Wed, May 14, 2014 at 4:10 PM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>> I have submitted an _early_ PR to master to get the KC bits in - this
>> will help the Angular.js based UI overhaul, as its currently lacks a proper
>> login UI ;-)
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/156
>>
>> Once that is merged to MASTER, the angular branch can be rebased on this;
>>
>> Note: I added notes for users, to go w/ a 'stable' 0.10.x version...
>>
>>
>> -Matthias
>>
>>
>> On Wed, May 14, 2014 at 9:10 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>>
>>> Hello,
>>>
>>> here is an update on the integration: Bill did some updates to his
>>> example template and worked on more things inside of Keycloak for a better
>>> integration.
>>>
>>> Yesterday, I used his example work and applied it to our UPS:
>>>
>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration
>>>
>>>
>>> There is now an 'auth-server' module which produces a WAR (that also
>>> contains an AeroGear theme), to be deployed to the AS:
>>>
>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration/auth-server
>>>
>>>
>>> The 'server' module is using a ContextListener for the configuration
>>> work, instead of the previous keycloak.json file:
>>>
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-two-war-integration/server/src/main/java/org/jboss/aerogear/unifiedpush/keycloak/BootstrapListener.java
>>>
>>> Deploying the two WARs (auth before ups) will show the integration
>>> (admin:admin is the initial password).
>>>
>>> IMO this is a huge step towards a proper Keycloak integration, but some
>>> items are still open:
>>> - nicer config (using his testrealm.json inside of the auth-server)
>>> - user/roles mgmt
>>> - integration w/ the new UI
>>> - ...
>>>
>>> When Bruno is back, the work on this branch will continue.
>>>
>>> That's it for now.
>>>
>>> -Matthias
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, May 6, 2014 at 11:49 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>>>
>>>> Hello folks!
>>>>
>>>> Bill Burk was helping on the Keycloak front and besides fixing related
>>>> items on the Keycloak server, he also created an example that we can use as
>>>> a template for the actual integration. See [1]
>>>>
>>>> In the past, Bruno and I did integrate w/ an external Keycloak server
>>>> (see [2]), and we did include the keycloak.json file (See [3]). Thanks to
>>>> Bill's work on Keycloak, the 'protected app' no longer needs that, see [4].
>>>> Also there is no more the need to customize the Keycloak Rest
>>>> Application (Stian and I did look into that as well).
>>>>
>>>>
>>>> Good news: This means the UPS can stay as it is -> no need to change
>>>> internals (e.g. the 'bundle all in one WAR file' did force us to change our
>>>> '/rest' URLs, as Keycloak uses them, see [5]).
>>>>
>>>> Inside of our 'modular' Keycloak branch (see [2] again), we can apply
>>>> the work from Bill:
>>>> * our current 'server' module will use a listener similar to [4]
>>>> * create a "ups-auth" module similar to [6]
>>>>
>>>> On the 'ups-auth module' there is one area where we need to have some
>>>> future improvement:
>>>> * testrealm.json -> needs to be in Java code, due to the URL being
>>>> hard-coded in there (we need to resolve the URL of the host, running the
>>>> bits). But, IMO for now that should be good enough.
>>>>
>>>> Bruno did offer to help out on the Keycloak integration, so that I can
>>>> go back to the analytics and mertrics feature. Thanks abstractj!! <3
>>>>
>>>> Greetings,
>>>> Matthias
>>>>
>>>> [1]
>>>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
>>>> [2]
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
>>>> [3]
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
>>>> [4]
>>>> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
>>>> [5]
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
>>>> [6]
>>>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
>>>>
>>>>
>>>> --
>>>> 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
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140516/3ccf3e97/attachment.html 

From hbons at redhat.com  Fri May 16 08:11:39 2014
From: hbons at redhat.com (Hylke Bons)
Date: Fri, 16 May 2014 13:11:39 +0100
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <1400170914549-7812.post@n5.nabble.com>
References: <5374DB1B.9020405@redhat.com>
	<1400170914549-7812.post@n5.nabble.com>
Message-ID: <5376007B.9070804@redhat.com>

My reasoning behing having separate tables was that you have less noise 
and less data to look at at once. It's also easier to present 
information. It's not mutually exclusive with a complete table though, 
we can still have that if desired.

Hylke


On 15/05/2014 17:21, mwessendorf wrote:
> Hello!
>
> a few comments:
> * landing-page: A dashboard is nice! But as said on the initial thread,
> let's focus on the stats around Push messages. If time allows we can define
> a 'dashboard' a bit more (e.g. adding notes 'how often an app was opened on
> a mobile device', etc)
>
> *activity table: Based on our IRC chat in the afternoon, you already updated
> it to only show the push messages. thanks!
>
> * Table per variant; I am not sure... I think as a user I just want to
> initially see a table of all the messages I send (per application). Clicking
> on the details (expanded row), I had in mind there to show more details,
> like
>
> 2000 receivers for Variant-A       -      SUCCESS
> 3000 receivers for Variant-B       -      FAILURE SENDING
> 4000 receivers for Variant-C       -      SUCCESS
>
>
>
>
>
>
>
> Hylke Bons wrote
>> Hey,
>>
>> Here's an initial version:
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>
>> I tried to incorporate most wishes expressed in the other thread.
>>
>> Most notable things:
>> - Landing page with an overview of stats, most active apps, and error
>> messages
>> - Activity table shows both registration and notification events
>> - Activity table is per variant, and not all activity on the server.
>> Unless there's a usecase to have every event for every app/variant in a
>> table I don't think we actually need it. The important thing is to get
>> to error messages easily.
>>
>> Things to do/think about:
>> - links/entry points to the activity table
>> - filtering the activity table
>>
>> This is just the first iteration and we will improve on this.
>> Let me know what you think.
>>
>> Thanks,
>>
>> Hylke
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at .jboss
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-First-go-at-stats-activity-wireframes-tp7804p7812.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 hbons at redhat.com  Fri May 16 08:16:02 2014
From: hbons at redhat.com (Hylke Bons)
Date: Fri, 16 May 2014 13:16:02 +0100
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <1400238682421-7819.post@n5.nabble.com>
References: <5374DB1B.9020405@redhat.com>	<1400170914549-7812.post@n5.nabble.com>
	<1400238682421-7819.post@n5.nabble.com>
Message-ID: <53760182.2020903@redhat.com>

On 16/05/2014 12:11, mwessendorf wrote:
> Note: On IRC Hylke shared a new version:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
> I am not 100% sure on the "Last error" thing, but perhaps we can find
> something to display there.

If we're able to scroll directly to the problematic push message when 
coming from for example, the dashboard, we don't really need it. It's 
there so to prevent excessive scrolling/paging when trying to find out 
what went wrong and fix the problem.

Hylke

>
> After thinking about it, Hylke - any comment on the below ?
>
>
> mwessendorf wrote
>> * Table per variant; I am not sure... I think as a user I just want to
>> initially see a table of all the messages I send (per application).
>> Clicking on the details (expanded row), I had in mind there to show more
>> details, like
>>
>> 2000 receivers for Variant-A       -      SUCCESS
>> 3000 receivers for Variant-B       -      FAILURE SENDING
>> 4000 receivers for Variant-C       -      SUCCESS
>
>
>
>
>
>
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-First-go-at-stats-activity-wireframes-tp7804p7819.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 corinnekrych at gmail.com  Fri May 16 09:47:55 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 16 May 2014 15:47:55 +0200
Subject: [aerogear-dev] OAuth2 authotization and Pipe integration
In-Reply-To: <1B826249-94E8-4544-84B5-9F5488278890@redhat.com>
References: <5FC7D59B-B71A-42A6-882E-543076E61C18@gmail.com>
	<5374E0F3.8060803@redhat.com>
	<F4B6F67E-01EA-46A6-8A7F-EA115BD5708C@gmail.com>
	<1B826249-94E8-4544-84B5-9F5488278890@redhat.com>
Message-ID: <15F08255-249F-440B-8592-19803F57E0BE@gmail.com>

Hello Luke,

Our native clients (with Google Drive app) use authz code grant type [1]. With this mode refresh token are issued.
Our JS GoogleDrive demo is using implicit grant[2] as recommended for browser based app. In this mode no refresh token is issued and grant should be asked as often as the access token expired (1h for Google).

What about hybrid? We could use something like the demo in this blog post[3]. so we can have refresh token too.

wdyt?
++
Corinne

[1] http://tools.ietf.org/html/rfc6749#section-4.1
[2] http://tools.ietf.org/html/rfc6749#section-4.2
[3]http://www.itsalif.info/content/oauth-google-api-gapi-phonegap-childbrowser-jquery

On 15 May 2014, at 18:12, Lucas Holmquist <lholmqui at redhat.com> wrote:

> for js we don?t have refresh tokens,  for security reasons.
> 
> 
> I know with googles js api,  they do a background refresh( iframe stuff ).
> 
> 
> go for it
> 
> 
> On May 15, 2014, at 12:08 PM, Corinne Krych <corinnekrych at gmail.com> wrote:
> 
>> So seamless refreshing token but declarative token initial request. Right?
>> #agreed seamless refresh
>> decalrative auhz request and revoke request.
>> If we all agree (JS included) I?ll create an iOS JIRA ticket and go for it.
>> 
>> JS folks, wdyt?
>> 
>> ++
>> Corinne
>> On 15 May 2014, at 17:44, Summers Pittman <supittma at redhat.com> wrote:
>> 
>>> I don't like it because it moves the concerns of bad accounts, account creation, authorization lifecycle error handling into the failure method of the pipe callback.  Those concerns don't belong there.
>>> 
>>> However I am fine with the module refreshing the accesstoken if a refresh token is provided.  If an error happens then that is something more "in line" with reasonable expectations for a authorized request.
>>> 
>>> 
>>> On Thu 15 May 2014 03:56:28 AM EDT, Corinne Krych wrote:
>>>> Hello folks
>>>> 
>>>> I?ve been thinking about providing a more fluid integration between authz and pipes.
>>>> 
>>>> Right now to read a list of GoogleDrive document, we need to read the pipe in the success callback of authz? requestAccess:
>>>> 
>>>>   AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>>>>   _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>>>>        ...
>>>>   }];
>>>> 
>>>>   [_restAuthzModule requestAccessSuccess:^(id object) {
>>>>     		 id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>>>>      		 [config setName:@"files"];
>>>>      		 [config setAuthzModule:authzModule]; // inject authz
>>>>    		 }];
>>>> 
>>>>  		 [documents read:^(id responseObject) {
>>>>       		// do sth with response
>>>>  		 } failure:^(NSError *error) {
>>>>      			 // when an error occurs...
>>>>  		 }];
>>>>   } failure:^(NSError *error) {
>>>>       NSLog(@"Failure in getting access token");
>>>>   }];
>>>> 
>>>> What about if we just initialize authzModule and inject it into pipe. Once the pipe read (or any crud) it will be the pipe that first fetch tokens (or  renew - whaetever is needed) and on success read the pipe. Basically we do the callback chaining internally in the Pipe instead of letting the developer deal with it.
>>>> 
>>>>   AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>>>>   _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>>>>        ...
>>>>   }];
>>>> 
>>>>   id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>>>>     		 [config setName:@"files"];
>>>>      		 [config setAuthzModule:authzModule]; // inject authz
>>>>   }];
>>>> 
>>>>   [documents read:^(id responseObject) {
>>>>       		// do sth with response
>>>>     } failure:^(NSError *error) {
>>>>      			 // when an error occurs...
>>>>   }];
>>>> 
>>>> It feels much fluid on the user.
>>>> Doing so we ?force? the app flow to ask token when it needs it, not in advance at startup of app. but i think this is good practice to lazy authz your app.
>>>> 
>>>> Thoughts?
>>>> 
>>>> Test repo can be found here:
>>>> https://github.com/corinnekrych/aerogear-ios/blob/transparent.refresh/AeroGear-iOS/pipeline/AGRESTPipe.m#L169
>>>> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-145.refresh/GoogleDrive/GoogleDrive/AGViewController.m
>>>> 
>>>> ++
>>>> Corinne
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> 
>>> --
>>> Summers Pittman
>>>>> Phone:404 941 4698
>>>>> Java is my crack.
>>> 
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From supittma at redhat.com  Fri May 16 10:02:49 2014
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 16 May 2014 10:02:49 -0400
Subject: [aerogear-dev] Oauth2 integration test PR
Message-ID: <53761A89.5040909@redhat.com>

https://github.com/aerogear/aerogear-android-integration-tests/pull/29

Needs to be run against the oauth_again branch.

-- 
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.


From supittma at redhat.com  Fri May 16 10:05:05 2014
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 16 May 2014 10:05:05 -0400
Subject: [aerogear-dev] Sync proposal 2 electric boogaloo
Message-ID: <53761B11.7000804@redhat.com>


Its that time of month again where I pay attention to sync. lohlmquist 
and I have been banging on some ideas for a few moments here and there 
and this is what has popped out so far:

https://gist.github.com/secondsun/fdb681bc5a56f389b7dc

Interesting bits start here : 
https://gist.github.com/secondsun/fdb681bc5a56f389b7dc#api-specification
I have put together an android PoC for the repository API here 
:https://github.com/secondsun/aerogear-android-sync/tree/master/android

wdyt?

-- 
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.


From lholmqui at redhat.com  Fri May 16 10:15:56 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Fri, 16 May 2014 10:15:56 -0400
Subject: [aerogear-dev] OAuth2 authotization and Pipe integration
In-Reply-To: <15F08255-249F-440B-8592-19803F57E0BE@gmail.com>
References: <5FC7D59B-B71A-42A6-882E-543076E61C18@gmail.com>
	<5374E0F3.8060803@redhat.com>
	<F4B6F67E-01EA-46A6-8A7F-EA115BD5708C@gmail.com>
	<1B826249-94E8-4544-84B5-9F5488278890@redhat.com>
	<15F08255-249F-440B-8592-19803F57E0BE@gmail.com>
Message-ID: <2B8870DD-6DBC-40DC-B7A8-2B1E9EAAE7F0@redhat.com>


On May 16, 2014, at 9:47 AM, Corinne Krych <corinnekrych at gmail.com> wrote:

> Hello Luke,
> 
> Our native clients (with Google Drive app) use authz code grant type [1]. With this mode refresh token are issued.
> Our JS GoogleDrive demo is using implicit grant[2] as recommended for browser based app. In this mode no refresh token is issued and grant should be asked as often as the access token expired (1h for Google).
> 
> What about hybrid? We could use something like the demo in this blog post[3]. so we can have refresh token too.

for hybrid,  a refresh token would be fine,

for the Jboss Keynote demo in 2013, the link below is similar to what i did

> 
> wdyt?
> ++
> Corinne
> 
> [1] http://tools.ietf.org/html/rfc6749#section-4.1
> [2] http://tools.ietf.org/html/rfc6749#section-4.2
> [3]http://www.itsalif.info/content/oauth-google-api-gapi-phonegap-childbrowser-jquery
> 
> On 15 May 2014, at 18:12, Lucas Holmquist <lholmqui at redhat.com> wrote:
> 
>> for js we don?t have refresh tokens,  for security reasons.
>> 
>> 
>> I know with googles js api,  they do a background refresh( iframe stuff ).
>> 
>> 
>> go for it
>> 
>> 
>> On May 15, 2014, at 12:08 PM, Corinne Krych <corinnekrych at gmail.com> wrote:
>> 
>>> So seamless refreshing token but declarative token initial request. Right?
>>> #agreed seamless refresh
>>> decalrative auhz request and revoke request.
>>> If we all agree (JS included) I?ll create an iOS JIRA ticket and go for it.
>>> 
>>> JS folks, wdyt?
>>> 
>>> ++
>>> Corinne
>>> On 15 May 2014, at 17:44, Summers Pittman <supittma at redhat.com> wrote:
>>> 
>>>> I don't like it because it moves the concerns of bad accounts, account creation, authorization lifecycle error handling into the failure method of the pipe callback.  Those concerns don't belong there.
>>>> 
>>>> However I am fine with the module refreshing the accesstoken if a refresh token is provided.  If an error happens then that is something more "in line" with reasonable expectations for a authorized request.
>>>> 
>>>> 
>>>> On Thu 15 May 2014 03:56:28 AM EDT, Corinne Krych wrote:
>>>>> Hello folks
>>>>> 
>>>>> I?ve been thinking about providing a more fluid integration between authz and pipes.
>>>>> 
>>>>> Right now to read a list of GoogleDrive document, we need to read the pipe in the success callback of authz? requestAccess:
>>>>> 
>>>>>  AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>>>>>  _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>>>>>       ...
>>>>>  }];
>>>>> 
>>>>>  [_restAuthzModule requestAccessSuccess:^(id object) {
>>>>>    		 id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>>>>>     		 [config setName:@"files"];
>>>>>     		 [config setAuthzModule:authzModule]; // inject authz
>>>>>   		 }];
>>>>> 
>>>>> 		 [documents read:^(id responseObject) {
>>>>>      		// do sth with response
>>>>> 		 } failure:^(NSError *error) {
>>>>>     			 // when an error occurs...
>>>>> 		 }];
>>>>>  } failure:^(NSError *error) {
>>>>>      NSLog(@"Failure in getting access token");
>>>>>  }];
>>>>> 
>>>>> What about if we just initialize authzModule and inject it into pipe. Once the pipe read (or any crud) it will be the pipe that first fetch tokens (or  renew - whaetever is needed) and on success read the pipe. Basically we do the callback chaining internally in the Pipe instead of letting the developer deal with it.
>>>>> 
>>>>>  AGAuthorizer* authorizer = [AGAuthorizer authorizer];
>>>>>  _restAuthzModule = [authorizer authz:^(id<AGAuthzConfig> config) {
>>>>>       ...
>>>>>  }];
>>>>> 
>>>>>  id<AGPipe> documents = [googleDocuments pipe:^(id<AGPipeConfig> config) {
>>>>>    		 [config setName:@"files"];
>>>>>     		 [config setAuthzModule:authzModule]; // inject authz
>>>>>  }];
>>>>> 
>>>>>  [documents read:^(id responseObject) {
>>>>>      		// do sth with response
>>>>>    } failure:^(NSError *error) {
>>>>>     			 // when an error occurs...
>>>>>  }];
>>>>> 
>>>>> It feels much fluid on the user.
>>>>> Doing so we ?force? the app flow to ask token when it needs it, not in advance at startup of app. but i think this is good practice to lazy authz your app.
>>>>> 
>>>>> Thoughts?
>>>>> 
>>>>> Test repo can be found here:
>>>>> https://github.com/corinnekrych/aerogear-ios/blob/transparent.refresh/AeroGear-iOS/pipeline/AGRESTPipe.m#L169
>>>>> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-145.refresh/GoogleDrive/GoogleDrive/AGViewController.m
>>>>> 
>>>>> ++
>>>>> Corinne
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Summers Pittman
>>>>>> Phone:404 941 4698
>>>>>> Java is my crack.
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From daniel.bevenius at gmail.com  Fri May 16 10:18:42 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 16 May 2014 16:18:42 +0200
Subject: [aerogear-dev] Sync proposal 2 electric boogaloo
In-Reply-To: <53761B11.7000804@redhat.com>
References: <53761B11.7000804@redhat.com>
Message-ID: <CAFJm-3EZ=rkb0mm1eNKLpYJcd-uU2ZL91QGjmJQWgpvhmuRvoA@mail.gmail.com>

I was interested in the server side api but the link might be incorrect:
https://gist.github.com/secondsun/aerogear-sync-server-api



On 16 May 2014 16:05, Summers Pittman <supittma at redhat.com> wrote:

>
> Its that time of month again where I pay attention to sync. lohlmquist
> and I have been banging on some ideas for a few moments here and there
> and this is what has popped out so far:
>
> https://gist.github.com/secondsun/fdb681bc5a56f389b7dc
>
> Interesting bits start here :
> https://gist.github.com/secondsun/fdb681bc5a56f389b7dc#api-specification
> I have put together an android PoC for the repository API here
> :https://github.com/secondsun/aerogear-android-sync/tree/master/android
>
> wdyt?
>
> --
> 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/20140516/952f5da2/attachment.html 

From supittma at redhat.com  Fri May 16 10:25:52 2014
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 16 May 2014 10:25:52 -0400
Subject: [aerogear-dev] Sync proposal 2 electric boogaloo
In-Reply-To: <CAFJm-3EZ=rkb0mm1eNKLpYJcd-uU2ZL91QGjmJQWgpvhmuRvoA@mail.gmail.com>
References: <53761B11.7000804@redhat.com>
	<CAFJm-3EZ=rkb0mm1eNKLpYJcd-uU2ZL91QGjmJQWgpvhmuRvoA@mail.gmail.com>
Message-ID: <53761FF0.30507@redhat.com>

On Fri 16 May 2014 10:18:42 AM EDT, Daniel Bevenius wrote:
> I was interested in the server side api but the link might be incorrect:
> https://gist.github.com/secondsun/aerogear-sync-server-api

Yeah I took the doc from abstractj's branch and gisted it up with my 
changes.  The links are broken ATM and this doc only/mostly thinks 
about the client side for now.

>
>
>
> On 16 May 2014 16:05, Summers Pittman <supittma at redhat.com
> <mailto:supittma at redhat.com>> wrote:
>
>
>     Its that time of month again where I pay attention to sync. lohlmquist
>     and I have been banging on some ideas for a few moments here and there
>     and this is what has popped out so far:
>
>     https://gist.github.com/secondsun/fdb681bc5a56f389b7dc
>
>     Interesting bits start here :
>     https://gist.github.com/secondsun/fdb681bc5a56f389b7dc#api-specification
>     I have put together an android PoC for the repository API here
>     :https://github.com/secondsun/aerogear-android-sync/tree/master/android
>
>     wdyt?
>
>     --
>     Summers Pittman
>     >>Phone:404 941 4698 <tel:404%20941%204698>
>     >>Java is my crack.
>
>     _______________________________________________
>     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
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.


From supittma at redhat.com  Fri May 16 10:31:09 2014
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 16 May 2014 10:31:09 -0400
Subject: [aerogear-dev] Sync proposal 2 electric boogaloo
In-Reply-To: <CAFJm-3Ge+A35tHe68GDP4teHksLRS_pG8SmYFgTuQ-PspOTfUw@mail.gmail.com>
References: <53761B11.7000804@redhat.com>
	<CAFJm-3EZ=rkb0mm1eNKLpYJcd-uU2ZL91QGjmJQWgpvhmuRvoA@mail.gmail.com>
	<53761FF0.30507@redhat.com>
	<CAFJm-3Ge+A35tHe68GDP4teHksLRS_pG8SmYFgTuQ-PspOTfUw@mail.gmail.com>
Message-ID: <5376212D.90700@redhat.com>



On Fri 16 May 2014 10:29:01 AM EDT, Daniel Bevenius wrote:
> Ah cool!
>
> Looks good. Could we update aerogear.org/data-sync
> <http://aerogear.org/data-sync> or create a new branch for this?
Will just update the branch, no reason to add more confusion.
>
>
> On 16 May 2014 16:25, Summers Pittman <supittma at redhat.com
> <mailto:supittma at redhat.com>> wrote:
>
>     On Fri 16 May 2014 10:18:42 AM EDT, Daniel Bevenius wrote:
>
>         I was interested in the server side api but the link might be
>         incorrect:
>         https://gist.github.com/__secondsun/aerogear-sync-__server-api
>         <https://gist.github.com/secondsun/aerogear-sync-server-api>
>
>
>     Yeah I took the doc from abstractj's branch and gisted it up with
>     my changes.  The links are broken ATM and this doc only/mostly
>     thinks about the client side for now.
>
>
>
>
>         On 16 May 2014 16:05, Summers Pittman <supittma at redhat.com
>         <mailto:supittma at redhat.com>
>         <mailto:supittma at redhat.com <mailto:supittma at redhat.com>>> wrote:
>
>
>             Its that time of month again where I pay attention to
>         sync. lohlmquist
>             and I have been banging on some ideas for a few moments
>         here and there
>             and this is what has popped out so far:
>
>         https://gist.github.com/__secondsun/fdb681bc5a56f389b7dc
>         <https://gist.github.com/secondsun/fdb681bc5a56f389b7dc>
>
>             Interesting bits start here :
>         https://gist.github.com/__secondsun/__fdb681bc5a56f389b7dc#api-__specification
>         <https://gist.github.com/secondsun/fdb681bc5a56f389b7dc#api-specification>
>             I have put together an android PoC for the repository API here
>
>         :https://github.com/secondsun/__aerogear-android-sync/tree/__master/android
>         <https://github.com/secondsun/aerogear-android-sync/tree/master/android>
>
>             wdyt?
>
>             --
>             Summers Pittman
>             >>Phone:404 941 4698 <tel:404%20941%204698>
>         <tel:404%20941%204698>
>
>             >>Java is my crack.
>
>             _________________________________________________
>             aerogear-dev mailing list
>         aerogear-dev at lists.jboss.org
>         <mailto:aerogear-dev at lists.jboss.org>
>         <mailto:aerogear-dev at lists.__jboss.org
>         <mailto:aerogear-dev at lists.jboss.org>>
>         https://lists.jboss.org/__mailman/listinfo/aerogear-dev
>         <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
>
>
>
>
>
>         _________________________________________________
>         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
>         <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
>
>
>
>
>     --
>     Summers Pittman
>
>             Phone:404 941 4698 <tel:404%20941%204698>
>             Java is my crack.
>
>
>



--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.


From avibelli at redhat.com  Sun May 18 00:55:41 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Sat, 17 May 2014 21:55:41 -0700 (PDT)
Subject: [aerogear-dev] Keycloak integration BOM refactoring
Message-ID: <1400388941526-7830.post@n5.nabble.com>

Hi all, I have sent a first initial PR for the BOM refactoring of UPS after
Keycloak integration.
If everything is fine after the test, I will 'promote' all the additional
dependencies into the AeroGear BOMs, and send some more PRs.
Thanks
Andrea



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Keycloak-integration-BOM-refactoring-tp7830.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Sun May 18 17:47:39 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Sun, 18 May 2014 23:47:39 +0200
Subject: [aerogear-dev] Sending Push Notifications to a Lego Robot with
	SimplePush !
Message-ID: <CAD_dpu32eqbb6D8hcnSAyJzQXvM7VBBXneDJOHhrcFRue2k41A@mail.gmail.com>

Hi everyone !

I just wanted to share the results of my (really) nerdy Sunday. I was able
to send a Push Notification to my Lego EV3 Robot using the UnifiedPush
Server. The robot throws a ball when it receives the notification :)

The robot is under Linux and can run  the JVM. I've been using our Java
SimplePush client (
https://github.com/aerogear/aerogear-simplepush-java-client) hacked with
 Matzew's  WebSocket Java Client (
https://github.com/matzew/simple-websocket-client).

The UPS instance is from the OpenShift Cartridge and the Simple Push
Server, is the vert.x version, also running on OpenShift.

In this small video I show the Robot and my Android Device both receiving
the notification : https://www.youtube.com/watch?v=4uqfcqq42es

This is an interesting use of the SimplePush Protocol since every connected
device/object is eligible for the UPS ;)

Sebi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140518/d42889b4/attachment-0001.html 

From daniel.bevenius at gmail.com  Mon May 19 02:51:14 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 19 May 2014 08:51:14 +0200
Subject: [aerogear-dev] Team meeting
Message-ID: <CAFJm-3H+AKEGnvyp6w+AZM1T-mhbDK9Zfwudqot2VBSgVrmptQ@mail.gmail.com>

Agenda:
http://oksoclap.com/p/aerogear-team-mgt-20140519
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140519/a4c030f5/attachment.html 

From daniel.bevenius at gmail.com  Mon May 19 03:29:19 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 19 May 2014 09:29:19 +0200
Subject: [aerogear-dev] Sending Push Notifications to a Lego Robot with
 SimplePush !
In-Reply-To: <CAD_dpu32eqbb6D8hcnSAyJzQXvM7VBBXneDJOHhrcFRue2k41A@mail.gmail.com>
References: <CAD_dpu32eqbb6D8hcnSAyJzQXvM7VBBXneDJOHhrcFRue2k41A@mail.gmail.com>
Message-ID: <CAFJm-3FeRiGwH585g5uLYbBjhj4V=svYEoCHbKgPQjWuLa7AiQ@mail.gmail.com>

Nice work on this Sebi!




On 18 May 2014 23:47, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi everyone !
>
> I just wanted to share the results of my (really) nerdy Sunday. I was able
> to send a Push Notification to my Lego EV3 Robot using the UnifiedPush
> Server. The robot throws a ball when it receives the notification :)
>
> The robot is under Linux and can run  the JVM. I've been using our Java
> SimplePush client (
> https://github.com/aerogear/aerogear-simplepush-java-client) hacked with
>  Matzew's  WebSocket Java Client (
> https://github.com/matzew/simple-websocket-client).
>
> The UPS instance is from the OpenShift Cartridge and the Simple Push
> Server, is the vert.x version, also running on OpenShift.
>
> In this small video I show the Robot and my Android Device both receiving
> the notification : https://www.youtube.com/watch?v=4uqfcqq42es
>
> This is an interesting use of the SimplePush Protocol since every
> connected device/object is eligible for the UPS ;)
>
> 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/20140519/b92a8c95/attachment.html 

From miguel21op at gmail.com  Mon May 19 04:55:31 2014
From: miguel21op at gmail.com (Miguel Lemos)
Date: Mon, 19 May 2014 09:55:31 +0100
Subject: [aerogear-dev] Sending Push Notifications to a Lego Robot with
 SimplePush !
In-Reply-To: <CAD_dpu32eqbb6D8hcnSAyJzQXvM7VBBXneDJOHhrcFRue2k41A@mail.gmail.com>
References: <CAD_dpu32eqbb6D8hcnSAyJzQXvM7VBBXneDJOHhrcFRue2k41A@mail.gmail.com>
Message-ID: <CADPUygdyDFsnxni5CgvGY2JEfr3g=PRiVUuWKjQVLgLGQ-csmw@mail.gmail.com>

Congratulations for the criativity. A week-end much more chalanging and
funny than going to the mall :-)
No dia 18 de Mai de 2014 22:47, "Sebastien Blanc" <scm.blanc at gmail.com>
escreveu:
>
> Hi everyone !
>
> I just wanted to share the results of my (really) nerdy Sunday. I was
able to send a Push Notification to my Lego EV3 Robot using the UnifiedPush
Server. The robot throws a ball when it receives the notification :)
>
> The robot is under Linux and can run  the JVM. I've been using our Java
SimplePush client (
https://github.com/aerogear/aerogear-simplepush-java-client) hacked with
 Matzew's  WebSocket Java Client (
https://github.com/matzew/simple-websocket-client).
>
> The UPS instance is from the OpenShift Cartridge and the Simple Push
Server, is the vert.x version, also running on OpenShift.
>
> In this small video I show the Robot and my Android Device both receiving
the notification : https://www.youtube.com/watch?v=4uqfcqq42es
>
> This is an interesting use of the SimplePush Protocol since every
connected device/object is eligible for the UPS ;)
>
> 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/20140519/8e05ca5a/attachment.html 

From vmfamaral at gmail.com  Mon May 19 05:54:11 2014
From: vmfamaral at gmail.com (oxsav)
Date: Mon, 19 May 2014 02:54:11 -0700 (PDT)
Subject: [aerogear-dev] Android Push
Message-ID: <1400493251941-7835.post@n5.nabble.com>

Hi.
I'm trying to follow the tutorial about the android push notification: 
http://aerogear.org/docs/guides/aerogear-push-android/android-app/

For now I'm only trying to do this as it is without adding new features or
something like that. The thing is I do everything like is mentioned in the
tutorial, and it returns me this error:

E/AndroidRuntime(25982): java.lang.NoClassDefFoundError:
org.jboss.aerogear.android.unifiedpush.Registrations


I added the aerogear-android-1.2.0.jar as an external jar to my project..
Any idea how I can solve this?

Tks,
Vasco



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Push-tp7835.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Mon May 19 06:37:50 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 19 May 2014 12:37:50 +0200
Subject: [aerogear-dev] Android Push
In-Reply-To: <1400493251941-7835.post@n5.nabble.com>
References: <1400493251941-7835.post@n5.nabble.com>
Message-ID: <CAAg5f2TLxCPVCHgmN0uhPb9q3k3v2KorwNHx_th5fSY43zSqQw@mail.gmail.com>

Looks like some sort of incorrect dependebcy


Can you give this a try:

https://github.com/aerogear/aerogear-push-helloworld

Our new simplified getting started demos


Thx,
Matthias


On Monday, May 19, 2014, oxsav <vmfamaral at gmail.com> wrote:

> Hi.
> I'm trying to follow the tutorial about the android push notification:
> http://aerogear.org/docs/guides/aerogear-push-android/android-app/
>
> For now I'm only trying to do this as it is without adding new features or
> something like that. The thing is I do everything like is mentioned in the
> tutorial, and it returns me this error:
>
> E/AndroidRuntime(25982): java.lang.NoClassDefFoundError:
> org.jboss.aerogear.android.unifiedpush.Registrations
>
>
> I added the aerogear-android-1.2.0.jar as an external jar to my project..
> Any idea how I can solve this?
>
> Tks,
> Vasco
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Android-Push-tp7835.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <javascript:;>
> 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/20140519/09988547/attachment.html 

From matzew at apache.org  Mon May 19 06:48:10 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 19 May 2014 12:48:10 +0200
Subject: [aerogear-dev] Android Push
In-Reply-To: <1400493251941-7835.post@n5.nabble.com>
References: <1400493251941-7835.post@n5.nabble.com>
Message-ID: <CAAg5f2S8rxTh4a4_KEe0RN6fPFjm22v1QWx9ykEu=mp4V4w=uQ@mail.gmail.com>

Looks like some sort of incorrect dependebcy


Can you give this a try:

https://github.com/aerogear/aerogear-push-helloworld

Our new simplified getting started demos


Thx,
Matthias


On Monday, May 19, 2014, oxsav <vmfamaral at gmail.com> wrote:

> Hi.
> I'm trying to follow the tutorial about the android push notification:
> http://aerogear.org/docs/guides/aerogear-push-android/android-app/
>
> For now I'm only trying to do this as it is without adding new features or
> something like that. The thing is I do everything like is mentioned in the
> tutorial, and it returns me this error:
>
> E/AndroidRuntime(25982): java.lang.NoClassDefFoundError:
> org.jboss.aerogear.android.unifiedpush.Registrations
>
>
> I added the aerogear-android-1.2.0.jar as an external jar to my project..
> Any idea how I can solve this?
>
> Tks,
> Vasco
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Android-Push-tp7835.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <javascript:;>
> 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/20140519/62e14712/attachment.html 

From hbons at redhat.com  Mon May 19 08:03:13 2014
From: hbons at redhat.com (Hylke Bons)
Date: Mon, 19 May 2014 13:03:13 +0100
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <5374DB1B.9020405@redhat.com>
References: <5374DB1B.9020405@redhat.com>
Message-ID: <5379F301.7030607@redhat.com>

Hello,

Here are some updates based on the feedback from the meetings: 
https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
- Simplified dashboard stats
- Apps notifications table
- Defined entry points

Let me know what you think. I hope that covers everything.

Thanks,

Hylke



On 15/05/2014 16:19, Hylke Bons wrote:
> Hey,
>
> Here's an initial version:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
> I tried to incorporate most wishes expressed in the other thread.
>
> Most notable things:
> - Landing page with an overview of stats, most active apps, and error
> messages
> - Activity table shows both registration and notification events
> - Activity table is per variant, and not all activity on the server.
> Unless there's a usecase to have every event for every app/variant in a
> table I don't think we actually need it. The important thing is to get
> to error messages easily.
>
> Things to do/think about:
> - links/entry points to the activity table
> - filtering the activity table
>
> This is just the first iteration and we will improve on this.
> Let me know what you think.
>
> Thanks,
>
> Hylke
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From matzew at apache.org  Mon May 19 08:05:07 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 19 May 2014 14:05:07 +0200
Subject: [aerogear-dev] [Mobile Push 1.0.0] Client SDKs for Android,
	Cordova and iOS
Message-ID: <CAAg5f2Sb=qUTOi=z_6-RhPRPMnw_pF8eGouo6MSkAFDLRqEknw@mail.gmail.com>

Hi,

as said before (see [1]), this summer we will release the AeroGear Mobile
Push 1.0.0 to the community.

I took a look at the related JIRAs (see [2]) and noticed that for the
mobile client SDKs there are no outstanding tickets. Yay!

The github repos are also in an OK state :-) there are no feature related
open PRs; Well, besides a test improvement for the Cordova push plugin -
but that will be addressed soon;

My question is: Are you guys aware of any features that we need to add to
Android, Cordova or iOS, related for push ?

Once the Android and iOS bits are 'done', lets make sure we use those
latest versions on our Cordova plugin ;-)

Thanks!
Matthias

[1] http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
[2] https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140519/d2e34f7b/attachment-0001.html 

From bruno at abstractj.org  Mon May 19 08:08:53 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 19 May 2014 09:08:53 -0300
Subject: [aerogear-dev] Keycloak integration
In-Reply-To: <CAD_dpu3m+YRy-=SZbXsVfzC_qKwEMoT5Om2xx6iiY82_Y1WcDw@mail.gmail.com>
References: <CAAg5f2QZxk2hTQaC1iEMjz+aYF8PXbXMnvnTQBECxCh1go2GGw@mail.gmail.com>
	<CAAg5f2QQpkXSv7NBbC02=FqgbHt3GTQNSk9-KcWOZL-siS7JEQ@mail.gmail.com>
	<CAAg5f2T+nZRhqwHSSWBCugOQ0aqLp8mhxxT7rcfG4iXNFSnNLQ@mail.gmail.com>
	<CAAg5f2Tz2Qp91mtJ+tnVdbJHv1OZ516eoGgooX+eziq9Q9zDjg@mail.gmail.com>
	<CAD_dpu3m+YRy-=SZbXsVfzC_qKwEMoT5Om2xx6iiY82_Y1WcDw@mail.gmail.com>
Message-ID: <20140519120853.GB4458@abstractj.org>

I've already assigned some tasks to myself. I'll check the latest
updates from KC and UPS.

On 2014-05-16, Sebastien Blanc wrote:
> In addition to that I would like to mention that we rebased the Keycloak
> work from master into the Angular/UI Overhaul migration branch  , it's
> currently on this branch :
>
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/angular_keycloak
>
> To make testing easier a bundle (a not yet optimized) Console in the webapp
> folder.
>
> Sebi
>
>
>
>
>
> On Thu, May 15, 2014 at 11:20 AM, Matthias Wessendorf <mwessendorf at gmail.com
> > wrote:
>
> > this got merged;
> >
> > I have update the EPIC for this task:
> > https://issues.jboss.org/browse/AGPUSH-568
> >
> >
> > On Wed, May 14, 2014 at 4:10 PM, Matthias Wessendorf <matzew at apache.org>wrote:
> >
> >> I have submitted an _early_ PR to master to get the KC bits in - this
> >> will help the Angular.js based UI overhaul, as its currently lacks a proper
> >> login UI ;-)
> >>
> >> https://github.com/aerogear/aerogear-unifiedpush-server/pull/156
> >>
> >> Once that is merged to MASTER, the angular branch can be rebased on this;
> >>
> >> Note: I added notes for users, to go w/ a 'stable' 0.10.x version...
> >>
> >>
> >> -Matthias
> >>
> >>
> >> On Wed, May 14, 2014 at 9:10 AM, Matthias Wessendorf <matzew at apache.org>wrote:
> >>
> >>> Hello,
> >>>
> >>> here is an update on the integration: Bill did some updates to his
> >>> example template and worked on more things inside of Keycloak for a better
> >>> integration.
> >>>
> >>> Yesterday, I used his example work and applied it to our UPS:
> >>>
> >>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration
> >>>
> >>>
> >>> There is now an 'auth-server' module which produces a WAR (that also
> >>> contains an AeroGear theme), to be deployed to the AS:
> >>>
> >>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-two-war-integration/auth-server
> >>>
> >>>
> >>> The 'server' module is using a ContextListener for the configuration
> >>> work, instead of the previous keycloak.json file:
> >>>
> >>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-two-war-integration/server/src/main/java/org/jboss/aerogear/unifiedpush/keycloak/BootstrapListener.java
> >>>
> >>> Deploying the two WARs (auth before ups) will show the integration
> >>> (admin:admin is the initial password).
> >>>
> >>> IMO this is a huge step towards a proper Keycloak integration, but some
> >>> items are still open:
> >>> - nicer config (using his testrealm.json inside of the auth-server)
> >>> - user/roles mgmt
> >>> - integration w/ the new UI
> >>> - ...
> >>>
> >>> When Bruno is back, the work on this branch will continue.
> >>>
> >>> That's it for now.
> >>>
> >>> -Matthias
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Tue, May 6, 2014 at 11:49 AM, Matthias Wessendorf <matzew at apache.org>wrote:
> >>>
> >>>> Hello folks!
> >>>>
> >>>> Bill Burk was helping on the Keycloak front and besides fixing related
> >>>> items on the Keycloak server, he also created an example that we can use as
> >>>> a template for the actual integration. See [1]
> >>>>
> >>>> In the past, Bruno and I did integrate w/ an external Keycloak server
> >>>> (see [2]), and we did include the keycloak.json file (See [3]). Thanks to
> >>>> Bill's work on Keycloak, the 'protected app' no longer needs that, see [4].
> >>>> Also there is no more the need to customize the Keycloak Rest
> >>>> Application (Stian and I did look into that as well).
> >>>>
> >>>>
> >>>> Good news: This means the UPS can stay as it is -> no need to change
> >>>> internals (e.g. the 'bundle all in one WAR file' did force us to change our
> >>>> '/rest' URLs, as Keycloak uses them, see [5]).
> >>>>
> >>>> Inside of our 'modular' Keycloak branch (see [2] again), we can apply
> >>>> the work from Bill:
> >>>> * our current 'server' module will use a listener similar to [4]
> >>>> * create a "ups-auth" module similar to [6]
> >>>>
> >>>> On the 'ups-auth module' there is one area where we need to have some
> >>>> future improvement:
> >>>> * testrealm.json -> needs to be in Java code, due to the URL being
> >>>> hard-coded in there (we need to resolve the URL of the host, running the
> >>>> bits). But, IMO for now that should be good enough.
> >>>>
> >>>> Bruno did offer to help out on the Keycloak integration, so that I can
> >>>> go back to the analytics and mertrics feature. Thanks abstractj!! <3
> >>>>
> >>>> Greetings,
> >>>> Matthias
> >>>>
> >>>> [1]
> >>>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
> >>>> [2]
> >>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
> >>>> [3]
> >>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
> >>>> [4]
> >>>> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
> >>>> [5]
> >>>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
> >>>> [6]
> >>>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
> >>>>
> >>>>
> >>>> --
> >>>> 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
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

JBoss, a division of Red Hat

From matzew at apache.org  Mon May 19 08:09:51 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 19 May 2014 14:09:51 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <5379F301.7030607@redhat.com>
References: <5374DB1B.9020405@redhat.com>
	<5379F301.7030607@redhat.com>
Message-ID: <CAAg5f2TxumDJ8iFNt1ui_P7wRx3h73ePr_SmnZzyscRkV1rgGQ@mail.gmail.com>

awesome!

I think that pretty much reflects our last meeting

Thanks, Hylke!


On Mon, May 19, 2014 at 2:03 PM, Hylke Bons <hbons at redhat.com> wrote:

> Hello,
>
> Here are some updates based on the feedback from the meetings:
>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> - Simplified dashboard stats
> - Apps notifications table
> - Defined entry points
>
> Let me know what you think. I hope that covers everything.
>
> Thanks,
>
> Hylke
>
>
>
> On 15/05/2014 16:19, Hylke Bons wrote:
> > Hey,
> >
> > Here's an initial version:
> >
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >
> > I tried to incorporate most wishes expressed in the other thread.
> >
> > Most notable things:
> > - Landing page with an overview of stats, most active apps, and error
> > messages
> > - Activity table shows both registration and notification events
> > - Activity table is per variant, and not all activity on the server.
> > Unless there's a usecase to have every event for every app/variant in a
> > table I don't think we actually need it. The important thing is to get
> > to error messages easily.
> >
> > Things to do/think about:
> > - links/entry points to the activity table
> > - filtering the activity table
> >
> > This is just the first iteration and we will improve on this.
> > Let me know what you think.
> >
> > 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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140519/bb39bc76/attachment.html 

From edewit at redhat.com  Mon May 19 08:16:35 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 19 May 2014 14:16:35 +0200
Subject: [aerogear-dev] Cordova native ui plugin
Message-ID: <3500F618-FDC9-40D1-B1A9-7121910F6D49@redhat.com>

Hi,

I have a idea for a new cordova plugin, how about a plugin that let?s you add native ui components dynamically. A good use case for this could be to have native navigation on the top of your app.

We?ll need to bridge the events from native back to js and a way to define what components to add, initially we could support only a couple. 

What do you think?

	Erik Jan

From scm.blanc at gmail.com  Mon May 19 08:30:50 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 19 May 2014 14:30:50 +0200
Subject: [aerogear-dev] Cordova native ui plugin
In-Reply-To: <3500F618-FDC9-40D1-B1A9-7121910F6D49@redhat.com>
References: <3500F618-FDC9-40D1-B1A9-7121910F6D49@redhat.com>
Message-ID: <CAD_dpu0g2tKY7Hqp+CyoQvXB_YKsJ5_VZcO3kAtYrRefzQOqVg@mail.gmail.com>

Sounds cool ! But let's be sure it does not already exist, for instance I
know that Appgyver Steroids have this approach
http://www.appgyver.com/steroids/examples#navigation-bar


On Mon, May 19, 2014 at 2:16 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> I have a idea for a new cordova plugin, how about a plugin that let?s you
> add native ui components dynamically. A good use case for this could be to
> have native navigation on the top of your app.
>
> We?ll need to bridge the events from native back to js and a way to define
> what components to add, initially we could support only a couple.
>
> What do you think?
>
>         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/20140519/b646d01e/attachment.html 

From scm.blanc at gmail.com  Mon May 19 08:38:17 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 19 May 2014 14:38:17 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <CAAg5f2TxumDJ8iFNt1ui_P7wRx3h73ePr_SmnZzyscRkV1rgGQ@mail.gmail.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<CAAg5f2TxumDJ8iFNt1ui_P7wRx3h73ePr_SmnZzyscRkV1rgGQ@mail.gmail.com>
Message-ID: <CAD_dpu02ZD4EoxhjvmHofgNL6AR0OvGmkGdr=0sw+JXiY4cwnw@mail.gmail.com>

Great stuff !!
+1
Let's go on with this proposal.



On Mon, May 19, 2014 at 2:09 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> awesome!
>
> I think that pretty much reflects our last meeting
>
> Thanks, Hylke!
>
>
> On Mon, May 19, 2014 at 2:03 PM, Hylke Bons <hbons at redhat.com> wrote:
>
>> Hello,
>>
>> Here are some updates based on the feedback from the meetings:
>>
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> - Simplified dashboard stats
>> - Apps notifications table
>> - Defined entry points
>>
>> Let me know what you think. I hope that covers everything.
>>
>> Thanks,
>>
>> Hylke
>>
>>
>>
>> On 15/05/2014 16:19, Hylke Bons wrote:
>> > Hey,
>> >
>> > Here's an initial version:
>> >
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> >
>> > I tried to incorporate most wishes expressed in the other thread.
>> >
>> > Most notable things:
>> > - Landing page with an overview of stats, most active apps, and error
>> > messages
>> > - Activity table shows both registration and notification events
>> > - Activity table is per variant, and not all activity on the server.
>> > Unless there's a usecase to have every event for every app/variant in a
>> > table I don't think we actually need it. The important thing is to get
>> > to error messages easily.
>> >
>> > Things to do/think about:
>> > - links/entry points to the activity table
>> > - filtering the activity table
>> >
>> > This is just the first iteration and we will improve on this.
>> > Let me know what you think.
>> >
>> > 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
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140519/90cd48c1/attachment-0001.html 

From bruno at abstractj.org  Mon May 19 08:49:10 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 19 May 2014 09:49:10 -0300
Subject: [aerogear-dev] [aerogear-misc] release issue
In-Reply-To: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
References: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
Message-ID: <20140519124910.GC4458@abstractj.org>

Good morning,

AeroGear Misc was staged here and the version was discussed as well,
please check this thread
(http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-td7702.html).

I can't see what's wrong. Semantically the correct would be 0.2.0.

On 2014-05-09, Matthias Wessendorf wrote:
> Hi,
>
> Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
> number (0.2.0).
> This artifact was already pushed to maven central.
>
> On IRC we had the following idea:
> * update master to 0.1.2-SNAPSHOT
> * perform the release again (that hopefully will result in 0.1.2 on maven
> central)
>
> That still means we have a 0.2.0 on maven central. I will ask my contacts
> at Sonatype to remove the 0.2.0 bits;
>
> If folks are OK w/ that, I am happy to perform these steps by Monday morning
>
> Greetings,
> Matthias
>
> [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From bruno at abstractj.org  Mon May 19 08:49:47 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 19 May 2014 09:49:47 -0300
Subject: [aerogear-dev] [aerogear-misc] release issue
In-Reply-To: <20140509141258.45271762@kapy-ntb-x220>
References: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
	<20140509141258.45271762@kapy-ntb-x220>
Message-ID: <20140519124947.GD4458@abstractj.org>

And I still can't see what's wrong....

On 2014-05-09, Karel Piwko wrote:
> What about:
>
> 1/ Release ag-misc 0.1.2 to Central to fix ag-parent
> 2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
> => aligns minor version with ag-misc
> => Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send a PR)
>
> No deletes needed. Maven world will not collapse ;-)
>
> Karel
>
>
> On Fri, 9 May 2014 12:21:15 +0200
> Matthias Wessendorf <mwessendorf at gmail.com> wrote:
>
> > Hi,
> >
> > Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
> > number (0.2.0).
> > This artifact was already pushed to maven central.
> >
> > On IRC we had the following idea:
> > * update master to 0.1.2-SNAPSHOT
> > * perform the release again (that hopefully will result in 0.1.2 on maven
> > central)
> >
> > That still means we have a 0.2.0 on maven central. I will ask my contacts
> > at Sonatype to remove the 0.2.0 bits;
> >
> > If folks are OK w/ that, I am happy to perform these steps by Monday morning
> >
> > Greetings,
> > Matthias
> >
> > [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
> >
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj

From matzew at apache.org  Mon May 19 09:00:03 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 19 May 2014 15:00:03 +0200
Subject: [aerogear-dev] [aerogear-misc] release issue
In-Reply-To: <20140519124947.GD4458@abstractj.org>
References: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
	<20140509141258.45271762@kapy-ntb-x220>
	<20140519124947.GD4458@abstractj.org>
Message-ID: <CAAg5f2RRhhOhzv0SdHpqoudRy5iph0_vbf178dEWf0zVAbAwHA@mail.gmail.com>

The 0.2.0 has the wrong tag:
http://search.maven.org/remotecontent?filepath=org/jboss/aerogear/aerogear-misc/0.2.0/aerogear-misc-0.2.0.pom

and, I think more important, the related release of the -parent was going
against 0.1.2 (and not 0.2.0):
http://search.maven.org/remotecontent?filepath=org/jboss/aerogear/aerogear-parent/0.2.0/aerogear-parent-0.2.0.pom

That was the reason we did the 0.1.2 _after_ the 0.2.0

Next release will be 0.2.1 and atm nothing is broken

Andrea might be able to provide a few more details



On Mon, May 19, 2014 at 2:49 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> And I still can't see what's wrong....
>
> On 2014-05-09, Karel Piwko wrote:
> > What about:
> >
> > 1/ Release ag-misc 0.1.2 to Central to fix ag-parent
> > 2/ Release ag-parent 0.2.1 to Central, using 0.2.0 of ag-misc
> > => aligns minor version with ag-misc
> > => Optionally: Adds checkstyle to pluginMngmt (AEROGEAR-358) (I can send
> a PR)
> >
> > No deletes needed. Maven world will not collapse ;-)
> >
> > Karel
> >
> >
> > On Fri, 9 May 2014 12:21:15 +0200
> > Matthias Wessendorf <mwessendorf at gmail.com> wrote:
> >
> > > Hi,
> > >
> > > Andrea reported that the 0.1.2 release (see [1]) contains the wrong
> version
> > > number (0.2.0).
> > > This artifact was already pushed to maven central.
> > >
> > > On IRC we had the following idea:
> > > * update master to 0.1.2-SNAPSHOT
> > > * perform the release again (that hopefully will result in 0.1.2 on
> maven
> > > central)
> > >
> > > That still means we have a 0.2.0 on maven central. I will ask my
> contacts
> > > at Sonatype to remove the 0.2.0 bits;
> > >
> > > If folks are OK w/ that, I am happy to perform these steps by Monday
> morning
> > >
> > > Greetings,
> > > Matthias
> > >
> > > [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
> > >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
>
> 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/20140519/2c1f505d/attachment.html 

From kpiwko at redhat.com  Mon May 19 09:09:06 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Mon, 19 May 2014 15:09:06 +0200
Subject: [aerogear-dev] [aerogear-misc] release issue
In-Reply-To: <20140519124910.GC4458@abstractj.org>
References: <CAAg5f2TQcveHQQT1a0wM5LUbCoXNgyDsJ4jdqpPkMN6fb5SAwA@mail.gmail.com>
	<20140519124910.GC4458@abstractj.org>
Message-ID: <20140519150906.46b11a80@kapy-ntb-x220>

The problem was that version of aerogear-misc - 0.1.2 - defined in
aerogear-parent was missing on Maven Central, there was just 0.2.0.

As dependencies in <dependencyManagement> are not checked for availability
during install phase, users trying to use aerogear-misc managed by
aerogear-parent will see a resolution failure.

This was fixed by releasing aerogear-misc 0.1.2, content equal to 0.2.0, to
Maven Central.

Karel

On Mon, 19 May 2014 09:49:10 -0300
Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
> 
> AeroGear Misc was staged here and the version was discussed as well,
> please check this thread
> (http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-td7702.html).
> 
> I can't see what's wrong. Semantically the correct would be 0.2.0.
> 
> On 2014-05-09, Matthias Wessendorf wrote:
> > Hi,
> >
> > Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
> > number (0.2.0).
> > This artifact was already pushed to maven central.
> >
> > On IRC we had the following idea:
> > * update master to 0.1.2-SNAPSHOT
> > * perform the release again (that hopefully will result in 0.1.2 on maven
> > central)
> >
> > That still means we have a 0.2.0 on maven central. I will ask my contacts
> > at Sonatype to remove the 0.2.0 bits;
> >
> > If folks are OK w/ that, I am happy to perform these steps by Monday morning
> >
> > Greetings,
> > Matthias
> >
> > [1] https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
> 
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From lholmqui at redhat.com  Mon May 19 09:09:20 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Mon, 19 May 2014 09:09:20 -0400
Subject: [aerogear-dev] Sending Push Notifications to a Lego Robot with
	SimplePush !
In-Reply-To: <CAD_dpu32eqbb6D8hcnSAyJzQXvM7VBBXneDJOHhrcFRue2k41A@mail.gmail.com>
References: <CAD_dpu32eqbb6D8hcnSAyJzQXvM7VBBXneDJOHhrcFRue2k41A@mail.gmail.com>
Message-ID: <B4F82503-6925-4322-BEAB-B9527C41C9B4@redhat.com>

cool beans!!
On May 18, 2014, at 5:47 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi everyone ! 
> 
> I just wanted to share the results of my (really) nerdy Sunday. I was able to send a Push Notification to my Lego EV3 Robot using the UnifiedPush Server. The robot throws a ball when it receives the notification :)
> 
> The robot is under Linux and can run  the JVM. I've been using our Java SimplePush client (https://github.com/aerogear/aerogear-simplepush-java-client) hacked with  Matzew's  WebSocket Java Client (https://github.com/matzew/simple-websocket-client).
> 
> The UPS instance is from the OpenShift Cartridge and the Simple Push Server, is the vert.x version, also running on OpenShift.
> 
> In this small video I show the Robot and my Android Device both receiving the notification : https://www.youtube.com/watch?v=4uqfcqq42es
> 
> This is an interesting use of the SimplePush Protocol since every connected device/object is eligible for the UPS ;)
> 
> 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/20140519/1e005ab4/attachment.html 

From cvasilak at gmail.com  Mon May 19 10:11:23 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 19 May 2014 17:11:23 +0300
Subject: [aerogear-dev] Team meeting
In-Reply-To: <CAFJm-3H+AKEGnvyp6w+AZM1T-mhbDK9Zfwudqot2VBSgVrmptQ@mail.gmail.com>
References: <CAFJm-3H+AKEGnvyp6w+AZM1T-mhbDK9Zfwudqot2VBSgVrmptQ@mail.gmail.com>
Message-ID: <C2B49B49-12BB-4045-B438-739313A56C28@gmail.com>

fyi,
our meeting minutes:

<jbott>	 Meeting ended Mon May 19 13:53:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
<jbott>	 Minutes:        http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-19-13.44.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-19-13.44.txt
<jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-19-13.44.log.html

On May 19, 2014, at 9:51 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> Agenda:
> http://oksoclap.com/p/aerogear-team-mgt-20140519
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140519/dfdab8ea/attachment-0001.html 

From vmfamaral at gmail.com  Mon May 19 11:05:13 2014
From: vmfamaral at gmail.com (oxsav)
Date: Mon, 19 May 2014 08:05:13 -0700 (PDT)
Subject: [aerogear-dev] Android Push
In-Reply-To: <CAAg5f2S8rxTh4a4_KEe0RN6fPFjm22v1QWx9ykEu=mp4V4w=uQ@mail.gmail.com>
References: <1400493251941-7835.post@n5.nabble.com>
	<CAAg5f2S8rxTh4a4_KEe0RN6fPFjm22v1QWx9ykEu=mp4V4w=uQ@mail.gmail.com>
Message-ID: <1400511913891-7851.post@n5.nabble.com>

Thank you for your fast reply. 

Yep it worked :D

Thank you



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Push-tp7835p7851.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From bruno at abstractj.org  Mon May 19 12:02:27 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 19 May 2014 13:02:27 -0300
Subject: [aerogear-dev] Cordova native ui plugin
In-Reply-To: <3500F618-FDC9-40D1-B1A9-7121910F6D49@redhat.com>
References: <3500F618-FDC9-40D1-B1A9-7121910F6D49@redhat.com>
Message-ID: <20140519160227.GC9711@abstractj.org>

I'm n00b on Cordova, but why would you need a native navigation? I think
the idea is doable, not sure about the use case.

On 2014-05-19, Erik Jan de Wit wrote:
> Hi,
>
> I have a idea for a new cordova plugin, how about a plugin that let?s you add native ui components dynamically. A good use case for this could be to have native navigation on the top of your app.
>
> We?ll need to bridge the events from native back to js and a way to define what components to add, initially we could support only a couple.
>
> What do you think?
>
> 	Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj

From tkriz at redhat.com  Mon May 19 12:05:32 2014
From: tkriz at redhat.com (Tadeas Kriz)
Date: Mon, 19 May 2014 18:05:32 +0200
Subject: [aerogear-dev] Cordova native ui plugin
In-Reply-To: <20140519160227.GC9711@abstractj.org>
References: <3500F618-FDC9-40D1-B1A9-7121910F6D49@redhat.com>
	<20140519160227.GC9711@abstractj.org>
Message-ID: <CFC0365F-76B8-4D62-8C27-AE921CBED6B3@redhat.com>

You would definitely get better user experience and probably also some speed advantages.

On 19 May 2014, at 18:02, Bruno Oliveira <bruno at abstractj.org> wrote:

> I'm n00b on Cordova, but why would you need a native navigation? I think
> the idea is doable, not sure about the use case.
> 
> On 2014-05-19, Erik Jan de Wit wrote:
>> Hi,
>> 
>> I have a idea for a new cordova plugin, how about a plugin that let?s you add native ui components dynamically. A good use case for this could be to have native navigation on the top of your app.
>> 
>> We?ll need to bridge the events from native back to js and a way to define what components to add, initially we could support only a couple.
>> 
>> What do you think?
>> 
>> 	Erik Jan
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> --
> 
> 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 May 19 12:13:06 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 19 May 2014 13:13:06 -0300
Subject: [aerogear-dev] Sync proposal 2 electric boogaloo
In-Reply-To: <53761FF0.30507@redhat.com>
References: <53761B11.7000804@redhat.com>
	<CAFJm-3EZ=rkb0mm1eNKLpYJcd-uU2ZL91QGjmJQWgpvhmuRvoA@mail.gmail.com>
	<53761FF0.30507@redhat.com>
Message-ID: <20140519161306.GD9711@abstractj.org>

I'm watching you Summers....

On 2014-05-16, Summers Pittman wrote:
> On Fri 16 May 2014 10:18:42 AM EDT, Daniel Bevenius wrote:
> > I was interested in the server side api but the link might be incorrect:
> > https://gist.github.com/secondsun/aerogear-sync-server-api
>
> Yeah I took the doc from abstractj's branch and gisted it up with my
> changes.  The links are broken ATM and this doc only/mostly thinks
> about the client side for now.
>
> >
> >
> >
> > On 16 May 2014 16:05, Summers Pittman <supittma at redhat.com
> > <mailto:supittma at redhat.com>> wrote:
> >
> >
> >     Its that time of month again where I pay attention to sync. lohlmquist
> >     and I have been banging on some ideas for a few moments here and there
> >     and this is what has popped out so far:
> >
> >     https://gist.github.com/secondsun/fdb681bc5a56f389b7dc
> >
> >     Interesting bits start here :
> >     https://gist.github.com/secondsun/fdb681bc5a56f389b7dc#api-specification
> >     I have put together an android PoC for the repository API here
> >     :https://github.com/secondsun/aerogear-android-sync/tree/master/android
> >
> >     wdyt?
> >
> >     --
> >     Summers Pittman
> >     >>Phone:404 941 4698 <tel:404%20941%204698>
> >     >>Java is my crack.
> >
> >     _______________________________________________
> >     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
> >
> >
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj

From bruno at abstractj.org  Mon May 19 12:14:22 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 19 May 2014 13:14:22 -0300
Subject: [aerogear-dev] Empire JS day 2
In-Reply-To: <2D8C1BF3-7A44-4863-99B5-A04F9A5195B4@redhat.com>
References: <2D8C1BF3-7A44-4863-99B5-A04F9A5195B4@redhat.com>
Message-ID: <20140519161422.GE9711@abstractj.org>

Thanks for the write-up Luke.

On 2014-05-09, Lucas Holmquist wrote:
> Now for Day 2,
>
> going off topic for a second, i realized that after the first day, my jeans weren't skinny enough. Ok back to the talks
>
> Build Artifacts in Source Control
>
> by Clay Smith
>
> youtube link: https://www.youtube.com/watch?v=KxqVtsnP6Ko - part 1
>
> https://www.youtube.com/watch?v=ViPsP7HzMJ4 - part 2
>
> this talk was about how it is bad to put compiled production distribution stuff in git/vcs
>
> also talk about using the github release api
>
> and that we need better tools for production builds
>
> Preventing XSS & CSRF
>
> by Jeremy Stashewsky
>
> youtube link: https://www.youtube.com/watch?v=_jubb3g1HVg
>
> this was a cool talk about Cross Site Scripting and Cross Site Request Forgery and some techniques to help prevent it
>
> Bits of Nodebots.Next / Animating with Javascript
>
> by Rick Waldron
>
> youtube link: https://www.youtube.com/watch?v=0-6_iA1zZDk
>
> An awesome talk. Just watch the video
>
> Hacking Webforms with Phantom.js
>
> by Alyssa Ravasio
>
> youtube link: https://www.youtube.com/watch?v=HYKP0vZsTSI
>
> a interesting talk about using phantom.js to fill out forms.
>
> Her business is a camping booking site. Existing booking sites for campsites are crappy, and there is only really one. There is no public API for camp listings, so a user goes to her site, books their campsite on a nice looking/nice experience site, then in the background, phantom.js goes to the crappy site and books the camp site.
>
> MyDB
>
> by Guillermo Rauch - socket.io author( i think )
>
> youtube link: https://www.youtube.com/watch?v=0jwygdZW-r0
>
> kind of a neat talk about sync, probably somewhat relevant to what we might be doing
>
> BigPipe
>
> by Arnout Kazemier - from nodejitsu
>
> youtube link: https://www.youtube.com/watch?v=sYArq4XhdFo
>
> BigPipe is something that Facebook was suppose to deliver, but never really did, so these guys did there own thing
>
> it's basically the ability to render different parts of the page asyncly, using what they call pagelets
>
> an example of BigPipe in use is browsenpm.org
>
> Transitioning Groupon to node.js
>
> by Sean McCullough
>
> youtube link: https://www.youtube.com/watch?v=TWVblTpUlxM
>
> kind of a neat talk about moving groupon's rails stack to node.js and some of the challenges and why it was right for them
>
> Hacking Art with Node.js and Image Analysis
>
> by John Resig - Author of a little know library called jQuery
>
> youtube link: https://www.youtube.com/watch?v=_JrJdD2Ssnk
>
> showing off some library's that he wrote to do image analysis, didn't really show any code though
>
> WebRTC can be easy
>
> by Michelle Bu - author of PeerJS
>
> youtube link: https://www.youtube.com/watch?v=ONxw9R1Fxfs
>
> pretty neat talk about WebRTC and making it easier to use.
>
> The hidden benefits of static analysis
>
> by Kirill Cherkashin and Tsering Shrestha
>
> youtube link: https://www.youtube.com/watch?v=3ZqTvexCtZM
>
> talk about how JS tools can be awesome even though JS is a dynamic language.
>
> showed some WebStorm IDE js autocomplete stuff
>
> and some other libs like spy-js
>
> Easing into ECMAScript 6 and Beyond
>
> by Ben Newman - works at facebook
>
> youtube link: https://www.youtube.com/watch?v=kXY9hIPKuLQ
>
> showing off his library "recast" and how we should always be transpiling to code for the future without choking on it
>
> Pixel Art and Javascript
>
> by Vince Allen
>
> youtube link: https://www.youtube.com/watch?v=W6tP3nJp3NM
>
> Needed to leave to catch a train, so i missed this one, so just watch the video

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From mcarrano at redhat.com  Mon May 19 11:48:04 2014
From: mcarrano at redhat.com (Matt Carrano)
Date: Mon, 19 May 2014 11:48:04 -0400 (EDT)
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <5379F301.7030607@redhat.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
Message-ID: <115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>

Hey Hylke,

This is looking good. I had a few minor comments/questions about the layout and labeling.  Take a look at the marked up wireframe (attached).

-Matt 

----- Original Message -----
From: "Hylke Bons" <hbons at redhat.com>
To: aerogear-dev at lists.jboss.org
Cc: "Matt Carrano" <mcarrano at redhat.com>
Sent: Monday, May 19, 2014 8:03:13 AM
Subject: Re: [aerogear-dev] First go at stats/activity wireframes

Hello,

Here are some updates based on the feedback from the meetings: 
https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
- Simplified dashboard stats
- Apps notifications table
- Defined entry points

Let me know what you think. I hope that covers everything.

Thanks,

Hylke



On 15/05/2014 16:19, Hylke Bons wrote:
> Hey,
>
> Here's an initial version:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
> I tried to incorporate most wishes expressed in the other thread.
>
> Most notable things:
> - Landing page with an overview of stats, most active apps, and error
> messages
> - Activity table shows both registration and notification events
> - Activity table is per variant, and not all activity on the server.
> Unless there's a usecase to have every event for every app/variant in a
> table I don't think we actually need it. The important thing is to get
> to error messages easily.
>
> Things to do/think about:
> - links/entry points to the activity table
> - filtering the activity table
>
> This is just the first iteration and we will improve on this.
> Let me know what you think.
>
> Thanks,
>
> Hylke
> _______________________________________________
> 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: activity-spec_mcComments.png
Type: image/png
Size: 397974 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140519/4acc5fd2/attachment-0001.png 

From corinnekrych at gmail.com  Tue May 20 05:12:11 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Tue, 20 May 2014 11:12:11 +0200
Subject: [aerogear-dev] iOS meeting
Message-ID: <C529233B-43A0-4D35-8071-7A23F3B16139@gmail.com>

Hello iOS geeks,

Here is  the meeting agenda:
http://oksoclap.com/p/iOSMeeting-20.05.14

Let?s meet on our IRC channel at 2pm UTC+2hours to discuss it.

Everybody welcome!

++
Corinne

From matzew at apache.org  Tue May 20 06:54:20 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 20 May 2014 12:54:20 +0200
Subject: [aerogear-dev] GCM limit with 1000 registrationIDs
Message-ID: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>

Hello Antoine!

I think you reported AGPUSH-642 ([1]). I have created a branch out of our
stable 0.10.x branch:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/gcm_paging

I tested on my side and did not notice any issue; Do you mind testing this
branch as well ?

-Matthias

[1] https://issues.jboss.org/browse/AGPUSH-642

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140520/98d13141/attachment.html 

From vivek.pandey at pinelabs.com  Tue May 20 08:09:16 2014
From: vivek.pandey at pinelabs.com (Vivek Pandey)
Date: Tue, 20 May 2014 17:39:16 +0530
Subject: [aerogear-dev] UPS Production worthiness
Message-ID: <002b01cf7424$528dc0a0$f7a941e0$@pinelabs.com>

Hello Aerogear dev team,

 

We integrated UPS into our backend server which is serving various mobile
apps. While the development and testing phase went well, my manager is
questioning me about production worthiness about Aerogear. It would be great
help if you could point me to references/success stories where UPS is being
used in production environments and scaling well in medium to high loads.

 

Thanks,

Vivek

 

 


This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140520/e3261575/attachment.html 

From scm.blanc at gmail.com  Tue May 20 08:34:47 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 20 May 2014 14:34:47 +0200
Subject: [aerogear-dev] [Mobile Push 1.0.0] Client SDKs for Android,
 Cordova and iOS
In-Reply-To: <CAAg5f2Sb=qUTOi=z_6-RhPRPMnw_pF8eGouo6MSkAFDLRqEknw@mail.gmail.com>
References: <CAAg5f2Sb=qUTOi=z_6-RhPRPMnw_pF8eGouo6MSkAFDLRqEknw@mail.gmail.com>
Message-ID: <CAD_dpu2upQHRD7pU8Xg5GxbTcro_btb9YHOt5H2rTJB-Yy+v-g@mail.gmail.com>

Hi,
For the Cordova Push Plugin there is one (trivial) item open that should be
fixed before 1.0.  I created a jira to track it
https://issues.jboss.org/browse/AGCORDOVA-4



On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hi,
>
> as said before (see [1]), this summer we will release the AeroGear Mobile
> Push 1.0.0 to the community.
>
> I took a look at the related JIRAs (see [2]) and noticed that for the
> mobile client SDKs there are no outstanding tickets. Yay!
>
> The github repos are also in an OK state :-) there are no feature related
> open PRs; Well, besides a test improvement for the Cordova push plugin -
> but that will be addressed soon;
>
> My question is: Are you guys aware of any features that we need to add to
> Android, Cordova or iOS, related for push ?
>
> Once the Android and iOS bits are 'done', lets make sure we use those
> latest versions on our Cordova plugin ;-)
>
> Thanks!
> Matthias
>
> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
> [2] https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140520/f9b8d106/attachment.html 

From cvasilak at gmail.com  Tue May 20 08:41:01 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 20 May 2014 15:41:01 +0300
Subject: [aerogear-dev] iOS meeting
In-Reply-To: <C529233B-43A0-4D35-8071-7A23F3B16139@gmail.com>
References: <C529233B-43A0-4D35-8071-7A23F3B16139@gmail.com>
Message-ID: <643AFF62-3444-4AB3-A80F-0B260C535CF8@gmail.com>

fyi,
our meeting minutes:

<jbott>	 Meeting ended Tue May 20 12:10:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
<jbott>	 Minutes:        http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-20-11.49.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-20-11.49.txt
<jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-20-11.49.log.html

On May 20, 2014, at 12:12 PM, Corinne Krych <corinnekrych at gmail.com> wrote:

> Hello iOS geeks,
> 
> Here is  the meeting agenda:
> http://oksoclap.com/p/iOSMeeting-20.05.14
> 
> Let?s meet on our IRC channel at 2pm UTC+2hours to discuss it.
> 
> Everybody welcome!
> 
> ++
> Corinne
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From daniel at passos.me  Tue May 20 09:26:56 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 20 May 2014 10:26:56 -0300
Subject: [aerogear-dev] GCM limit with 1000 registrationIDs
In-Reply-To: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>
References: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>
Message-ID: <CAKjsGbvU8C6rk5WbqhPhd5QMdcvn=t__iXLTEvO214HoYmNPNA@mail.gmail.com>

http://developer.android.com/google/gcm/adv.html#throttling :)

-- Passos


On Tue, May 20, 2014 at 7:54 AM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hello Antoine!
>
> I think you reported AGPUSH-642 ([1]). I have created a branch out of our
> stable 0.10.x branch:
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/gcm_paging
>
> I tested on my side and did not notice any issue; Do you mind testing this
> branch as well ?
>
> -Matthias
>
> [1] https://issues.jboss.org/browse/AGPUSH-642
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140520/68370593/attachment.html 

From matzew at apache.org  Tue May 20 09:34:15 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 20 May 2014 15:34:15 +0200
Subject: [aerogear-dev] GCM limit with 1000 registrationIDs
In-Reply-To: <CAKjsGbvU8C6rk5WbqhPhd5QMdcvn=t__iXLTEvO214HoYmNPNA@mail.gmail.com>
References: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>
	<CAKjsGbvU8C6rk5WbqhPhd5QMdcvn=t__iXLTEvO214HoYmNPNA@mail.gmail.com>
Message-ID: <CAAg5f2S5_U4JCgL=UorMSTeC-E7dj82oHbNqqwMo4+DUy0TPfQ@mail.gmail.com>

Any comments on the branch, so far ?


On Tue, May 20, 2014 at 3:26 PM, Daniel Passos <daniel at passos.me> wrote:

> http://developer.android.com/google/gcm/adv.html#throttling :)
>
> -- Passos
>
>
> On Tue, May 20, 2014 at 7:54 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>> Hello Antoine!
>>
>> I think you reported AGPUSH-642 ([1]). I have created a branch out of our
>> stable 0.10.x branch:
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/gcm_paging
>>
>> I tested on my side and did not notice any issue; Do you mind testing
>> this branch as well ?
>>
>> -Matthias
>>
>> [1] https://issues.jboss.org/browse/AGPUSH-642
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140520/4de9f4ef/attachment-0001.html 

From supittma at redhat.com  Tue May 20 10:44:36 2014
From: supittma at redhat.com (Summers Pittman)
Date: Tue, 20 May 2014 10:44:36 -0400
Subject: [aerogear-dev] Sync proposal 2 electric boogaloo
In-Reply-To: <20140519161306.GD9711@abstractj.org>
References: <53761B11.7000804@redhat.com>
	<CAFJm-3EZ=rkb0mm1eNKLpYJcd-uU2ZL91QGjmJQWgpvhmuRvoA@mail.gmail.com>
	<53761FF0.30507@redhat.com> <20140519161306.GD9711@abstractj.org>
Message-ID: <537B6A54.4000304@redhat.com>

On Mon 19 May 2014 12:13:06 PM EDT, Bruno Oliveira wrote:
> I'm watching you Summers....

I sent a PR to your rebirth branch.

>
> On 2014-05-16, Summers Pittman wrote:
>> On Fri 16 May 2014 10:18:42 AM EDT, Daniel Bevenius wrote:
>>> I was interested in the server side api but the link might be incorrect:
>>> https://gist.github.com/secondsun/aerogear-sync-server-api
>>
>> Yeah I took the doc from abstractj's branch and gisted it up with my
>> changes.  The links are broken ATM and this doc only/mostly thinks
>> about the client side for now.
>>
>>>
>>>
>>>
>>> On 16 May 2014 16:05, Summers Pittman <supittma at redhat.com
>>> <mailto:supittma at redhat.com>> wrote:
>>>
>>>
>>>      Its that time of month again where I pay attention to sync. lohlmquist
>>>      and I have been banging on some ideas for a few moments here and there
>>>      and this is what has popped out so far:
>>>
>>>      https://gist.github.com/secondsun/fdb681bc5a56f389b7dc
>>>
>>>      Interesting bits start here :
>>>      https://gist.github.com/secondsun/fdb681bc5a56f389b7dc#api-specification
>>>      I have put together an android PoC for the repository API here
>>>      :https://github.com/secondsun/aerogear-android-sync/tree/master/android
>>>
>>>      wdyt?
>>>
>>>      --
>>>      Summers Pittman
>>>      >>Phone:404 941 4698 <tel:404%20941%204698>
>>>      >>Java is my crack.
>>>
>>>      _______________________________________________
>>>      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
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Summers Pittman
>>>> Phone:404 941 4698
>>>> Java is my crack.
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
>
> abstractj
> _______________________________________________
> 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 avibelli at redhat.com  Tue May 20 11:09:25 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Tue, 20 May 2014 08:09:25 -0700 (PDT)
Subject: [aerogear-dev] [Mobile Push 1.0.0] Client SDKs for Android,
 Cordova and iOS
In-Reply-To: <CAD_dpu2upQHRD7pU8Xg5GxbTcro_btb9YHOt5H2rTJB-Yy+v-g@mail.gmail.com>
References: <CAAg5f2Sb=qUTOi=z_6-RhPRPMnw_pF8eGouo6MSkAFDLRqEknw@mail.gmail.com>
	<CAD_dpu2upQHRD7pU8Xg5GxbTcro_btb9YHOt5H2rTJB-Yy+v-g@mail.gmail.com>
Message-ID: <1400598565142-7865.post@n5.nabble.com>

Hi, 
I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5 an old
issue (http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
about the google-play-services version shipped inside the cordova plugin.

Thanks
Andrea


Sebastien Blanc wrote
> Hi,
> For the Cordova Push Plugin there is one (trivial) item open that should
> be
> fixed before 1.0.  I created a jira to track it
> https://issues.jboss.org/browse/AGCORDOVA-4
> 
> 
> 
> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;

> matzew@

> &gt;wrote:
> 
>> Hi,
>>
>> as said before (see [1]), this summer we will release the AeroGear Mobile
>> Push 1.0.0 to the community.
>>
>> I took a look at the related JIRAs (see [2]) and noticed that for the
>> mobile client SDKs there are no outstanding tickets. Yay!
>>
>> The github repos are also in an OK state :-) there are no feature related
>> open PRs; Well, besides a test improvement for the Cordova push plugin -
>> but that will be addressed soon;
>>
>> My question is: Are you guys aware of any features that we need to add to
>> Android, Cordova or iOS, related for push ?
>>
>> Once the Android and iOS bits are 'done', lets make sure we use those
>> latest versions on our Cordova plugin ;-)
>>
>> Thanks!
>> Matthias
>>
>> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>> [2] https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> 

> aerogear-dev at .jboss

>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
> 
> _______________________________________________
> aerogear-dev mailing list

> aerogear-dev at .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From bruno at abstractj.org  Tue May 20 13:12:07 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 20 May 2014 14:12:07 -0300
Subject: [aerogear-dev] Sync proposal 2 electric boogaloo
In-Reply-To: <537B6A54.4000304@redhat.com>
References: <53761B11.7000804@redhat.com>
	<CAFJm-3EZ=rkb0mm1eNKLpYJcd-uU2ZL91QGjmJQWgpvhmuRvoA@mail.gmail.com>
	<53761FF0.30507@redhat.com> <20140519161306.GD9711@abstractj.org>
	<537B6A54.4000304@redhat.com>
Message-ID: <20140520171207.GB62455@abstractj.org>

Merged, but feel free to send a PR to aerogear.org

On 2014-05-20, Summers Pittman wrote:
> On Mon 19 May 2014 12:13:06 PM EDT, Bruno Oliveira wrote:
> >I'm watching you Summers....
>
> I sent a PR to your rebirth branch.
>
> >
> >On 2014-05-16, Summers Pittman wrote:
> >>On Fri 16 May 2014 10:18:42 AM EDT, Daniel Bevenius wrote:
> >>>I was interested in the server side api but the link might be incorrect:
> >>>https://gist.github.com/secondsun/aerogear-sync-server-api
> >>
> >>Yeah I took the doc from abstractj's branch and gisted it up with my
> >>changes.  The links are broken ATM and this doc only/mostly thinks
> >>about the client side for now.
> >>
> >>>
> >>>
> >>>
> >>>On 16 May 2014 16:05, Summers Pittman <supittma at redhat.com
> >>><mailto:supittma at redhat.com>> wrote:
> >>>
> >>>
> >>>     Its that time of month again where I pay attention to sync. lohlmquist
> >>>     and I have been banging on some ideas for a few moments here and there
> >>>     and this is what has popped out so far:
> >>>
> >>>     https://gist.github.com/secondsun/fdb681bc5a56f389b7dc
> >>>
> >>>     Interesting bits start here :
> >>>     https://gist.github.com/secondsun/fdb681bc5a56f389b7dc#api-specification
> >>>     I have put together an android PoC for the repository API here
> >>>     :https://github.com/secondsun/aerogear-android-sync/tree/master/android
> >>>
> >>>     wdyt?
> >>>
> >>>     --
> >>>     Summers Pittman
> >>>     >>Phone:404 941 4698 <tel:404%20941%204698>
> >>>     >>Java is my crack.
> >>>
> >>>     _______________________________________________
> >>>     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
> >>>
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>aerogear-dev mailing list
> >>>aerogear-dev at lists.jboss.org
> >>>https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >>
> >>--
> >>Summers Pittman
> >>>>Phone:404 941 4698
> >>>>Java is my crack.
> >>
> >>_______________________________________________
> >>aerogear-dev mailing list
> >>aerogear-dev at lists.jboss.org
> >>https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >--
> >
> >abstractj
> >_______________________________________________
> >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.
>

--

abstractj

From daniel at passos.me  Tue May 20 13:34:18 2014
From: daniel at passos.me (Daniel Passos)
Date: Tue, 20 May 2014 14:34:18 -0300
Subject: [aerogear-dev] [QUICKSTART] Information for the mobile clients
In-Reply-To: <CAD_dpu0uKAwHh2vcXf3mr00O-2Za1dPG3wMdvZd4NbjfGiZQVw@mail.gmail.com>
References: <CAD_dpu0q0X76hZj61FgDsqLB5D3MShknP7UXQDF0FJV+bJ7c=A@mail.gmail.com>
	<53502FF3.8010809@abstractj.org>
	<CAD_dpu0uKAwHh2vcXf3mr00O-2Za1dPG3wMdvZd4NbjfGiZQVw@mail.gmail.com>
Message-ID: <CAKjsGbs1vusKkMBKFmjuqe3tC_H_ERtyaNhRxFP_9Qq1sdVaMg@mail.gmail.com>

To register I send "userName" and the login response "loginName"?

-- Passos


On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc at gmail.com>wrote:

> Sure !
> This is just a version to ease the client development.
> I will ask PL team and Joshua their plans around HSTS and HTTPS.
> In the mean time we can track all of this with
> https://issues.jboss.org/browse/AGPUSH-596
>
> Thx for the comment !
> Sebi
>
>
> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno at abstractj.org>wrote:
>
>> If your idea is to be secure, please make sure to use HTTPS and enforce
>> users to be redirected. We did it in the past with HSTS on AG Security,
>> might not be hard to copy & paste.
>>
>> Sebastien Blanc wrote:
>> > And because I love you, I deployed on OpenShift a version of this
>> secured
>> > backend to ease the development of the clients !
>> >
>> > If you browse to http://contacts-sblanc.rhcloud.com/ you will even see
>> the
>> > mobile web client. This deployed version contains also the Push Message
>> > endpoint.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140520/a5ea805a/attachment.html 

From jbalunas at redhat.com  Tue May 20 14:06:27 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Tue, 20 May 2014 14:06:27 -0400
Subject: [aerogear-dev] UPS Production worthiness
In-Reply-To: <002b01cf7424$528dc0a0$f7a941e0$@pinelabs.com>
References: <002b01cf7424$528dc0a0$f7a941e0$@pinelabs.com>
Message-ID: <E4CB92A8-4F9E-490B-BB8D-21B402FE56A9@redhat.com>

Hi Vivek,

It's awesome to hear that you have integrated the UPS into your backend systems and some of your mobile apps!

We have a lot of confidence around the UPS, its functionality, and performance.  Our team has been working hard on improvements and stability including our QE team.  Also, as you may have seen we're planning a 1.0 release of the UPS this summer.

However at this time we don't have specific references or success stories outside of what you can see in the community mailing lists - other users using it ;-)  We're also about to kick off some performance and scale testing in the next couple of months.

Have you run into any issues that drove these questions about production worthiness?  If so please let us know and we'll certainly take a look.

Hope this helps!

Thanks,
Jay Balunas 

On May 20, 2014, at 8:09 AM, Vivek Pandey <vivek.pandey at pinelabs.com> wrote:

> Hello Aerogear dev team,
>  
> We integrated UPS into our backend server which is serving various mobile apps. While the development and testing phase went well, my manager is questioning me about production worthiness about Aerogear. It would be great help if you could point me to references/success stories where UPS is being used in production environments and scaling well in medium to high loads.
>  
> Thanks,
> Vivek
>  
>  
> 
> This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140520/5e816514/attachment.html 

From scm.blanc at gmail.com  Tue May 20 14:13:10 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 20 May 2014 20:13:10 +0200
Subject: [aerogear-dev] [QUICKSTART] Information for the mobile clients
In-Reply-To: <CAKjsGbs1vusKkMBKFmjuqe3tC_H_ERtyaNhRxFP_9Qq1sdVaMg@mail.gmail.com>
References: <CAD_dpu0q0X76hZj61FgDsqLB5D3MShknP7UXQDF0FJV+bJ7c=A@mail.gmail.com>
	<53502FF3.8010809@abstractj.org>
	<CAD_dpu0uKAwHh2vcXf3mr00O-2Za1dPG3wMdvZd4NbjfGiZQVw@mail.gmail.com>
	<CAKjsGbs1vusKkMBKFmjuqe3tC_H_ERtyaNhRxFP_9Qq1sdVaMg@mail.gmail.com>
Message-ID: <CAD_dpu3v5yutnmAzwaHs5r3fRfBhHd4oY-CvqP-C5yhnD13ReA@mail.gmail.com>

Since we changed the use case for the Push part (now we broadcast) ,
passing a alias to UPS is not relevant anymore. For the login it's indeed
"loginName" to be passed in the auth header along with the password.



On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel at passos.me> wrote:

> To register I send "userName" and the login response "loginName"?
>
> -- Passos
>
>
>
> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
>
>> Sure !
>> This is just a version to ease the client development.
>> I will ask PL team and Joshua their plans around HSTS and HTTPS.
>> In the mean time we can track all of this with
>> https://issues.jboss.org/browse/AGPUSH-596
>>
>> Thx for the comment !
>> Sebi
>>
>>
>> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno at abstractj.org>wrote:
>>
>>> If your idea is to be secure, please make sure to use HTTPS and enforce
>>> users to be redirected. We did it in the past with HSTS on AG Security,
>>> might not be hard to copy & paste.
>>>
>>> Sebastien Blanc wrote:
>>> > And because I love you, I deployed on OpenShift a version of this
>>> secured
>>> > backend to ease the development of the clients !
>>> >
>>> > If you browse to http://contacts-sblanc.rhcloud.com/ you will even
>>> see the
>>> > mobile web client. This deployed version contains also the Push Message
>>> > endpoint.
>>>
>>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140520/2cc8f222/attachment-0001.html 

From matzew at apache.org  Tue May 20 14:32:40 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 20 May 2014 20:32:40 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
Message-ID: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>

Hello,

w/ the advent of the 0.2.0 parent, we have checkstyle enabled;

However, I am not that happy, as the default rules are IMO a bit odd (e.g.
the unused imports is pretty nasty when developing)

We could:
a) get rid of it (perhaps not)
b) disable it on normal execution and only execute it on a release profile
or like that

right now I am running w/ skip - but that's a bit nasty...

Thoughts?
Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140520/22c860b8/attachment.html 

From scm.blanc at gmail.com  Tue May 20 14:39:19 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 20 May 2014 20:39:19 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
Message-ID: <CAD_dpu21OhvF37Py7eLXQMssCnmWSR4UDrNdsrbAHXwzL1DEzw@mail.gmail.com>

On Tue, May 20, 2014 at 8:32 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hello,
>
> w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
>
> However, I am not that happy, as the default rules are IMO a bit odd (e.g.
> the unused imports is pretty nasty when developing)
>
> We could:
> a) get rid of it (perhaps not)
> b) disable it on normal execution and only execute it on a release profile
> or like that
>
+1

>
> right now I am running w/ skip - but that's a bit nasty...
>
> Thoughts?
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140520/c3e3aaf1/attachment.html 

From bruno at abstractj.org  Tue May 20 14:56:03 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 20 May 2014 15:56:03 -0300
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
Message-ID: <20140520185603.GA67928@abstractj.org>

+1 on having an specific profile for checkstyle

On 2014-05-20, Matthias Wessendorf wrote:
> Hello,
>
> w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
>
> However, I am not that happy, as the default rules are IMO a bit odd (e.g.
> the unused imports is pretty nasty when developing)
>
> We could:
> a) get rid of it (perhaps not)
> b) disable it on normal execution and only execute it on a release profile
> or like that
>
> right now I am running w/ skip - but that's a bit nasty...
>
> Thoughts?
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From daniel.bevenius at gmail.com  Tue May 20 15:01:34 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Tue, 20 May 2014 21:01:34 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <20140520185603.GA67928@abstractj.org>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
Message-ID: <CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>

-1 I'd prefer to have checkstyle enabled by default, and integrate the
checkstyle into the IDE to avoid having to discover issue later when
building with maven.


On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org> wrote:

> +1 on having an specific profile for checkstyle
>
> On 2014-05-20, Matthias Wessendorf wrote:
> > Hello,
> >
> > w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
> >
> > However, I am not that happy, as the default rules are IMO a bit odd
> (e.g.
> > the unused imports is pretty nasty when developing)
> >
> > We could:
> > a) get rid of it (perhaps not)
> > b) disable it on normal execution and only execute it on a release
> profile
> > or like that
> >
> > right now I am running w/ skip - but that's a bit nasty...
> >
> > Thoughts?
> > Matthias
> >
> > --
> > Matthias Wessendorf
> >
> > blog: http://matthiaswessendorf.wordpress.com/
> > sessions: http://www.slideshare.net/mwessendorf
> > twitter: http://twitter.com/mwessendorf
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> 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/20140520/f6387493/attachment.html 

From qmx at qmx.me  Tue May 20 15:13:52 2014
From: qmx at qmx.me (Douglas Campos)
Date: Tue, 20 May 2014 16:13:52 -0300
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
Message-ID: <20140520191352.GD71775@rohan.local>

On Tue, May 20, 2014 at 08:32:40PM +0200, Matthias Wessendorf wrote:
> Hello,
> 
> w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
> 
> However, I am not that happy, as the default rules are IMO a bit odd (e.g.
> the unused imports is pretty nasty when developing)

You're picking with one of the very few checks I actually think are
useful :)

> 
> We could:
> a) get rid of it (perhaps not)
> b) disable it on normal execution and only execute it on a release profile
> or like that
> 
> right now I am running w/ skip - but that's a bit nasty...
> 
> Thoughts?
> Matthias
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


-- 
qmx

From bruno at abstractj.org  Tue May 20 15:20:52 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 20 May 2014 16:20:52 -0300
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
Message-ID: <20140520192052.GC67928@abstractj.org>

The only reason to have checkstyle enabled by default is: if we agree on
which rules should be active or not and provide an specific IDE setup.

Other than that, people like me will skip it. Why? Simple, I'm trying to
solve critical problems and also strugging to figure out why checkstyle
is do care about method lenght.

So to me if you're guys really want to introduce it we need:

- Definition of which rules were supposed to be active
- IDE profiles for Eclipse/IntelliJ
- Make the error messages something clear

Otherwise, I'm -?. It was never discussed here and if it exists on
aerogear-parent is all our fault.

On 2014-05-20, Daniel Bevenius wrote:
> -1 I'd prefer to have checkstyle enabled by default, and integrate the
> checkstyle into the IDE to avoid having to discover issue later when
> building with maven.
>
>
> On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > +1 on having an specific profile for checkstyle
> >
> > On 2014-05-20, Matthias Wessendorf wrote:
> > > Hello,
> > >
> > > w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
> > >
> > > However, I am not that happy, as the default rules are IMO a bit odd
> > (e.g.
> > > the unused imports is pretty nasty when developing)
> > >
> > > We could:
> > > a) get rid of it (perhaps not)
> > > b) disable it on normal execution and only execute it on a release
> > profile
> > > or like that
> > >
> > > right now I am running w/ skip - but that's a bit nasty...
> > >
> > > Thoughts?
> > > Matthias
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > 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


--

abstractj

From matzew at apache.org  Tue May 20 15:48:35 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 20 May 2014 21:48:35 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <20140520192052.GC67928@abstractj.org>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
	<20140520192052.GC67928@abstractj.org>
Message-ID: <CAAg5f2TRp4kwquRcdZ=gyoFFWoxyL7iZHYs6Zhg_HC+4uhJq5A@mail.gmail.com>

On Tuesday, May 20, 2014, Bruno Oliveira <bruno at abstractj.org> wrote:

> The only reason to have checkstyle enabled by default is: if we agree on
> which rules should be active or not and provide an specific IDE setup.


Exactly! (Includes headers, formarting etc)



>
> Other than that, people like me will skip it. Why? Simple, I'm trying to
> solve critical problems and also strugging to figure out why checkstyle
> is do care about method lenght.


Same here :-)



>
> So to me if you're guys really want to introduce it we need:
>
> - Definition of which rules were supposed to be active
> - IDE profiles for Eclipse/IntelliJ
> - Make the error messages something clear


+1



>
> Otherwise, I'm -?. It was never discussed here and if it exists on
> aerogear-parent is all our fault.


Yep, fully agree



>
> On 2014-05-20, Daniel Bevenius wrote:
> > -1 I'd prefer to have checkstyle enabled by default, and integrate the
> > checkstyle into the IDE to avoid having to discover issue later when
> > building with maven.
> >
> >
> > On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org <javascript:;>>
> wrote:
> >
> > > +1 on having an specific profile for checkstyle
> > >
> > > On 2014-05-20, Matthias Wessendorf wrote:
> > > > Hello,
> > > >
> > > > w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
> > > >
> > > > However, I am not that happy, as the default rules are IMO a bit odd
> > > (e.g.
> > > > the unused imports is pretty nasty when developing)
> > > >
> > > > We could:
> > > > a) get rid of it (perhaps not)
> > > > b) disable it on normal execution and only execute it on a release
> > > profile
> > > > or like that
> > > >
> > > > right now I am running w/ skip - but that's a bit nasty...
> > > >
> > > > Thoughts?
> > > > Matthias
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org <javascript:;>
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > abstractj
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org <javascript:;>
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org <javascript:;>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <javascript:;>
> 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/20140520/06676647/attachment-0001.html 

From bruno at abstractj.org  Tue May 20 16:02:38 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 20 May 2014 17:02:38 -0300
Subject: [aerogear-dev] Keycloak user/roles management
Message-ID: <20140520200238.GA70482@abstractj.org>

Good morning peeps,

Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I would
like to understand what do you guys want say with this issue.

Currently Keycloak already has its own user/roles managements. What do
you guys are looking for? Any specific requirements?

--

abstractj

From matzew at apache.org  Wed May 21 01:47:19 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 07:47:19 +0200
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <20140520200238.GA70482@abstractj.org>
References: <20140520200238.GA70482@abstractj.org>
Message-ID: <CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>

Hello,

yes - the handling is done by Keycloak itself; Last time we looked at user
management, we had the following in terms of roles:

https://gist.github.com/sebastienblanc/6547605

Not sure the names of these roles are great.... let's see

Basically I think the role definition in the gist still addresses most of
what we want to archive:
* super-user: in charge of managing the UPS realm (including users); can
see _ALL_ push applications  (that's the admin in Sebi's gist)
* PushAdmin: Someone that can manage applications and variants, but is not
able to add new users; he also sees only his applications/variants etc
(that's the developer in sebis gist)

The gist also contains a 'Viewer' role - At this point I am not sure we do
really need this. My impression is that if we have PushAdmins for our 1.0.0
community release that will be enough.

-Matthias




On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <bruno at abstractj.org>wrote:

> Good morning peeps,
>
> Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I would
> like to understand what do you guys want say with this issue.
>
> Currently Keycloak already has its own user/roles managements. What do
> you guys are looking for? Any specific requirements?
>
> --
>
> 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/20140521/d021d3ca/attachment.html 

From antoine.matyja at worldline.com  Wed May 21 07:40:54 2014
From: antoine.matyja at worldline.com (A577127)
Date: Wed, 21 May 2014 04:40:54 -0700 (PDT)
Subject: [aerogear-dev] GCM limit with 1000 registrationIDs
In-Reply-To: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>
References: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>
Message-ID: <1400672454662-7879.post@n5.nabble.com>

Sorry, I don't have time right now to do this 

By the way, when we tried this we found out it was very slow to record
tokens (we tried with h2 and mysql, best we got is like ~1sec/request). Is
it the same for you ?



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-GCM-limit-with-1000-registrationIDs-tp7858p7879.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Wed May 21 07:47:50 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 13:47:50 +0200
Subject: [aerogear-dev] GCM limit with 1000 registrationIDs
In-Reply-To: <1400672454662-7879.post@n5.nabble.com>
References: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>
	<1400672454662-7879.post@n5.nabble.com>
Message-ID: <CAAg5f2S5dqCS99CEmV4vEj=76m7rzZ5K-6wLT4PkOxyaHPyACA@mail.gmail.com>

On Wed, May 21, 2014 at 1:40 PM, A577127 <antoine.matyja at worldline.com>wrote:

> Sorry, I don't have time right now to do this
>
> By the way, when we tried this we found out it was very slow to record
> tokens


record tokens? what do you mean?



> (we tried with h2 and mysql, best we got is like ~1sec/request). Is
> it the same for you ?
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-GCM-limit-with-1000-registrationIDs-tp7858p7879.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/20140521/2288c775/attachment.html 

From vivek.pandey at pinelabs.com  Wed May 21 08:07:29 2014
From: vivek.pandey at pinelabs.com (Vivek Pandey)
Date: Wed, 21 May 2014 17:37:29 +0530
Subject: [aerogear-dev] UPS Production worthiness
In-Reply-To: <E4CB92A8-4F9E-490B-BB8D-21B402FE56A9@redhat.com>
References: <002b01cf7424$528dc0a0$f7a941e0$@pinelabs.com>
	<E4CB92A8-4F9E-490B-BB8D-21B402FE56A9@redhat.com>
Message-ID: <005d01cf74ed$3d977140$b8c653c0$@pinelabs.com>

Hi Jay,

 

Thanks for your reply.

 

While we have not faced any issues in using UPS in our limited testing, I
often see info stacktraces in ups logs

 

2014-05-16 10:19:20,032 INFO  [com.notnoop.apns.internal.ApnsConnectionImpl]
(Thread-118) Exception while waiting for error code:
java.net.SocketException: Socket closed

        at java.net.SocketInputStream.socketRead0(Native Method)
[rt.jar:1.7.0_51]

        at java.net.SocketInputStream.read(SocketInputStream.java:152)
[rt.jar:1.7.0_51]

        at java.net.SocketInputStream.read(SocketInputStream.java:122)
[rt.jar:1.7.0_51]

       .....

        at
com.notnoop.apns.internal.ApnsConnectionImpl$1MonitoringThread.run(ApnsConne
ctionImpl.java:114) [apns-0.2.3.jar:]

 

 

These stacktraces coupled with low dev activity of noop/java-apns project
are disconcerting to me. I am currently using UPS 0.10.2 war.

 

Thanks,

Vivek

From: Jay Balunas [mailto:jbalunas at redhat.com] 
Sent: Tuesday, May 20, 2014 11:36 PM
To: vivek.pandey at pinelabs.com; AeroGear Developer Mailing List
Cc: Jay Balunas
Subject: Re: [aerogear-dev] UPS Production worthiness

 

Hi Vivek,

 

It's awesome to hear that you have integrated the UPS into your backend
systems and some of your mobile apps!

 

We have a lot of confidence around the UPS, its functionality, and
performance.  Our team has been working hard on improvements and stability
including our QE team.  Also, as you may have seen we're planning a 1.0
release of the UPS this summer.

 

However at this time we don't have specific references or success stories
outside of what you can see in the community mailing lists - other users
using it ;-)  We're also about to kick off some performance and scale
testing in the next couple of months.

 

Have you run into any issues that drove these questions about production
worthiness?  If so please let us know and we'll certainly take a look.

 

Hope this helps!

 

Thanks,

Jay Balunas 

 

On May 20, 2014, at 8:09 AM, Vivek Pandey <vivek.pandey at pinelabs.com> wrote:





Hello Aerogear dev team,

 

We integrated UPS into our backend server which is serving various mobile
apps. While the development and testing phase went well, my manager is
questioning me about production worthiness about Aerogear. It would be great
help if you could point me to references/success stories where UPS is being
used in production environments and scaling well in medium to high loads.

 

Thanks,

Vivek

 

 

 

  _____  

This message may contain privileged and confidential information and is
solely for the use of intended recipient. The views expressed in this email
are those of the sender and not of Pine Labs. The recipient should check
this email and attachments for the presence of viruses / malwares etc. Pine
Labs accepts no liability for any damage caused by any virus transmitted by
this email. Pine Labs may monitor and record all emails.

  _____  


_______________________________________________
aerogear-dev mailing list
 <mailto:aerogear-dev at lists.jboss.org> aerogear-dev at lists.jboss.org
 <https://lists.jboss.org/mailman/listinfo/aerogear-dev>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

 


This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140521/a9dc515e/attachment-0001.html 

From matzew at apache.org  Wed May 21 08:24:55 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 14:24:55 +0200
Subject: [aerogear-dev] UPS Production worthiness
In-Reply-To: <005d01cf74ed$3d977140$b8c653c0$@pinelabs.com>
References: <002b01cf7424$528dc0a0$f7a941e0$@pinelabs.com>
	<E4CB92A8-4F9E-490B-BB8D-21B402FE56A9@redhat.com>
	<005d01cf74ed$3d977140$b8c653c0$@pinelabs.com>
Message-ID: <CAAg5f2QZYVo0FCESLrpF3oyBmYTUS132jtGkWKWWVeUmR=UjRg@mail.gmail.com>

Hello Vivek!


On Wed, May 21, 2014 at 2:07 PM, Vivek Pandey <vivek.pandey at pinelabs.com>wrote:

> Hi Jay,
>
>
>
> Thanks for your reply.
>
>
>
> While we have not faced any issues in using UPS in our limited testing, I
> often see info stacktraces in ups logs
>
>
>
> 2014-05-16 10:19:20,032 INFO
> [com.notnoop.apns.internal.ApnsConnectionImpl] (Thread-118) Exception while
> waiting for error code: java.net.SocketException: Socket closed
>
>         at java.net.SocketInputStream.socketRead0(Native Method)
> [rt.jar:1.7.0_51]
>
>         at java.net.SocketInputStream.read(SocketInputStream.java:152)
> [rt.jar:1.7.0_51]
>
>         at java.net.SocketInputStream.read(SocketInputStream.java:122)
> [rt.jar:1.7.0_51]
>
>        ?????
>
>         at
> com.notnoop.apns.internal.ApnsConnectionImpl$1MonitoringThread.run(ApnsConnectionImpl.java:114)
> [apns-0.2.3.jar:]
>
>
>
>
>
> These stacktraces coupled with low dev activity of noop/java-apns project
> are disconcerting to me.
>

the stack-trace is no harm - it's only happening w/ doing a monitoring of
the thread (that's what we currently do, when setting up ApnsService - I
thought about explicitly disable that)

The activity of the underlying java-apns is very low, yes! However @froh42
is getting back:
https://github.com/notnoop/java-apns/commits/master

There will be a new release in the near future; @froh42 asked me if I could
help with pushing the bits to maven central


That said, I recently started looking at pushy:
https://github.com/relayrides/pushy

I also sent a PR that would allow us to feed pushy w/ our certificate from
the database:
https://github.com/relayrides/pushy/pull/87

Hope that helps
-Matthias



> I am currently using UPS 0.10.2 war.
>
>
>
> Thanks,
>
> Vivek
>
> *From:* Jay Balunas [mailto:jbalunas at redhat.com]
> *Sent:* Tuesday, May 20, 2014 11:36 PM
> *To:* vivek.pandey at pinelabs.com; AeroGear Developer Mailing List
> *Cc:* Jay Balunas
> *Subject:* Re: [aerogear-dev] UPS Production worthiness
>
>
>
> Hi Vivek,
>
>
>
> It's awesome to hear that you have integrated the UPS into your backend
> systems and some of your mobile apps!
>
>
>
> We have a lot of confidence around the UPS, its functionality, and
> performance.  Our team has been working hard on improvements and stability
> including our QE team.  Also, as you may have seen we're planning a 1.0
> release of the UPS this summer.
>
>
>
> However at this time we don't have specific references or success stories
> outside of what you can see in the community mailing lists - other users
> using it ;-)  We're also about to kick off some performance and scale
> testing in the next couple of months.
>
>
>
> Have you run into any issues that drove these questions about production
> worthiness?  If so please let us know and we'll certainly take a look.
>
>
>
> Hope this helps!
>
>
>
> Thanks,
>
> Jay Balunas
>
>
>
> On May 20, 2014, at 8:09 AM, Vivek Pandey <vivek.pandey at pinelabs.com>
> wrote:
>
>
>
> Hello Aerogear dev team,
>
>
>
> We integrated UPS into our backend server which is serving various mobile
> apps. While the development and testing phase went well, my manager is
> questioning me about production worthiness about Aerogear. It would be
> great help if you could point me to references/success stories where UPS is
> being used in production environments and scaling well in medium to high
> loads.
>
>
>
> Thanks,
>
> Vivek
>
>
>
>
>
>
> ------------------------------
>
> This message may contain privileged and confidential information and is
> solely for the use of intended recipient. The views expressed in this email
> are those of the sender and not of Pine Labs. The recipient should check
> this email and attachments for the presence of viruses / malwares etc. Pine
> Labs accepts no liability for any damage caused by any virus transmitted by
> this email. Pine Labs may monitor and record all emails.
> ------------------------------
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> ------------------------------
> This message may contain privileged and confidential information and is
> solely for the use of intended recipient. The views expressed in this email
> are those of the sender and not of Pine Labs. The recipient should check
> this email and attachments for the presence of viruses / malwares etc. Pine
> Labs accepts no liability for any damage caused by any virus transmitted by
> this email. Pine Labs may monitor and record all emails.
> ------------------------------
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140521/fccd4d75/attachment.html 

From matzew at apache.org  Wed May 21 08:45:56 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 14:45:56 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
Message-ID: <CAAg5f2QDub2UGcos5deGAUyBW2bfds+pOwuOdBAksAcfqjpHGQ@mail.gmail.com>

Hylke,

any comments on Matt's reply?

Or is this the final draft:
https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png

-Matthias



On Mon, May 19, 2014 at 5:48 PM, Matt Carrano <mcarrano at redhat.com> wrote:

> Hey Hylke,
>
> This is looking good. I had a few minor comments/questions about the
> layout and labeling.  Take a look at the marked up wireframe (attached).
>
> -Matt
>
> ----- Original Message -----
> From: "Hylke Bons" <hbons at redhat.com>
> To: aerogear-dev at lists.jboss.org
> Cc: "Matt Carrano" <mcarrano at redhat.com>
> Sent: Monday, May 19, 2014 8:03:13 AM
> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
>
> Hello,
>
> Here are some updates based on the feedback from the meetings:
>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> - Simplified dashboard stats
> - Apps notifications table
> - Defined entry points
>
> Let me know what you think. I hope that covers everything.
>
> Thanks,
>
> Hylke
>
>
>
> On 15/05/2014 16:19, Hylke Bons wrote:
> > Hey,
> >
> > Here's an initial version:
> >
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >
> > I tried to incorporate most wishes expressed in the other thread.
> >
> > Most notable things:
> > - Landing page with an overview of stats, most active apps, and error
> > messages
> > - Activity table shows both registration and notification events
> > - Activity table is per variant, and not all activity on the server.
> > Unless there's a usecase to have every event for every app/variant in a
> > table I don't think we actually need it. The important thing is to get
> > to error messages easily.
> >
> > Things to do/think about:
> > - links/entry points to the activity table
> > - filtering the activity table
> >
> > This is just the first iteration and we will improve on this.
> > Let me know what you think.
> >
> > 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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140521/9fe9a906/attachment.html 

From kpiwko at redhat.com  Wed May 21 08:48:10 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 21 May 2014 14:48:10 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <20140520192052.GC67928@abstractj.org>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
	<20140520192052.GC67928@abstractj.org>
Message-ID: <20140521144810.6b56e7fa@kapy-ntb-x220>

That's not true, it was discussed during team meeting at
the times we've been using G+ as well (I can't prove that) and on ML as well:

http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-JavaScript-formatter-td5200.html

It just took 7 month for the PR to be merged. The point of initial checkstyle
rules set was chosen because:

* It was identified as the least annoying setup on ML, there were a lot of +1s
* There was a bug in released library caused by using unused import that was not
  available on classpath. I might be able to dig it out but it would take me a
  lot of time as I don't recall what project it was.

+9001 for abstract's proposal on having same setup for IDE as well. There is
nothing more annoying then something working in IDE but not in Maven. -1 for the
specific profile, as it shifts responsibility to clean up the mess to the person
doing the release.

Karel

On Tue, 20 May 2014 16:20:52 -0300
Bruno Oliveira <bruno at abstractj.org> wrote:

> The only reason to have checkstyle enabled by default is: if we agree on
> which rules should be active or not and provide an specific IDE setup.
> 
> Other than that, people like me will skip it. Why? Simple, I'm trying to
> solve critical problems and also strugging to figure out why checkstyle
> is do care about method lenght.
> 
> So to me if you're guys really want to introduce it we need:
> 
> - Definition of which rules were supposed to be active
> - IDE profiles for Eclipse/IntelliJ
> - Make the error messages something clear
> 
> Otherwise, I'm -?. It was never discussed here and if it exists on
> aerogear-parent is all our fault.
> 
> On 2014-05-20, Daniel Bevenius wrote:
> > -1 I'd prefer to have checkstyle enabled by default, and integrate the
> > checkstyle into the IDE to avoid having to discover issue later when
> > building with maven.
> >
> >
> > On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org> wrote:
> >
> > > +1 on having an specific profile for checkstyle
> > >
> > > On 2014-05-20, Matthias Wessendorf wrote:
> > > > Hello,
> > > >
> > > > w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
> > > >
> > > > However, I am not that happy, as the default rules are IMO a bit odd
> > > (e.g.
> > > > the unused imports is pretty nasty when developing)
> > > >
> > > > We could:
> > > > a) get rid of it (perhaps not)
> > > > b) disable it on normal execution and only execute it on a release
> > > profile
> > > > or like that
> > > >
> > > > right now I am running w/ skip - but that's a bit nasty...
> > > >
> > > > Thoughts?
> > > > Matthias
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > >
> > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > sessions: http://www.slideshare.net/mwessendorf
> > > > twitter: http://twitter.com/mwessendorf
> > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > --
> > >
> > > 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
> 
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From bruno at abstractj.org  Wed May 21 08:55:43 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 21 May 2014 09:55:43 -0300
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
Message-ID: <20140521125543.GC92541@abstractj.org>

Thank you Matthias, I will look at it and return back with more
questions if necessary.

On 2014-05-21, Matthias Wessendorf wrote:
> Hello,
>
> yes - the handling is done by Keycloak itself; Last time we looked at user
> management, we had the following in terms of roles:
>
> https://gist.github.com/sebastienblanc/6547605
>
> Not sure the names of these roles are great.... let's see
>
> Basically I think the role definition in the gist still addresses most of
> what we want to archive:
> * super-user: in charge of managing the UPS realm (including users); can
> see _ALL_ push applications  (that's the admin in Sebi's gist)
> * PushAdmin: Someone that can manage applications and variants, but is not
> able to add new users; he also sees only his applications/variants etc
> (that's the developer in sebis gist)
>
> The gist also contains a 'Viewer' role - At this point I am not sure we do
> really need this. My impression is that if we have PushAdmins for our 1.0.0
> community release that will be enough.
>
> -Matthias
>
>
>
>
> On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <bruno at abstractj.org>wrote:
>
> > Good morning peeps,
> >
> > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I would
> > like to understand what do you guys want say with this issue.
> >
> > Currently Keycloak already has its own user/roles managements. What do
> > you guys are looking for? Any specific requirements?
> >
> > --
> >
> > 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


--

abstractj

From bsutter at redhat.com  Wed May 21 09:19:07 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Wed, 21 May 2014 09:19:07 -0400
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <CAAg5f2QDub2UGcos5deGAUyBW2bfds+pOwuOdBAksAcfqjpHGQ@mail.gmail.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
	<CAAg5f2QDub2UGcos5deGAUyBW2bfds+pOwuOdBAksAcfqjpHGQ@mail.gmail.com>
Message-ID: <57F53505-5811-406D-9184-4C5939198CF2@redhat.com>

Not that you asked me but :-)

+1 on the horizontal "dashboard" section
+1 to the concern related to "status" - the first time I saw it I felt it only addressed errors - not all possible but recent "activity"
I think the word "Log" or "Activity" would be better

On May 21, 2014, at 8:45 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> Hylke,
> 
> any comments on Matt's reply?
> 
> Or is this the final draft:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> 
> -Matthias
> 
> 
> 
> On Mon, May 19, 2014 at 5:48 PM, Matt Carrano <mcarrano at redhat.com> wrote:
> Hey Hylke,
> 
> This is looking good. I had a few minor comments/questions about the layout and labeling.  Take a look at the marked up wireframe (attached).
> 
> -Matt
> 
> ----- Original Message -----
> From: "Hylke Bons" <hbons at redhat.com>
> To: aerogear-dev at lists.jboss.org
> Cc: "Matt Carrano" <mcarrano at redhat.com>
> Sent: Monday, May 19, 2014 8:03:13 AM
> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
> 
> Hello,
> 
> Here are some updates based on the feedback from the meetings:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> - Simplified dashboard stats
> - Apps notifications table
> - Defined entry points
> 
> Let me know what you think. I hope that covers everything.
> 
> Thanks,
> 
> Hylke
> 
> 
> 
> On 15/05/2014 16:19, Hylke Bons wrote:
> > Hey,
> >
> > Here's an initial version:
> > https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >
> > I tried to incorporate most wishes expressed in the other thread.
> >
> > Most notable things:
> > - Landing page with an overview of stats, most active apps, and error
> > messages
> > - Activity table shows both registration and notification events
> > - Activity table is per variant, and not all activity on the server.
> > Unless there's a usecase to have every event for every app/variant in a
> > table I don't think we actually need it. The important thing is to get
> > to error messages easily.
> >
> > Things to do/think about:
> > - links/entry points to the activity table
> > - filtering the activity table
> >
> > This is just the first iteration and we will improve on this.
> > Let me know what you think.
> >
> > 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
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140521/3250fd4f/attachment.html 

From antoine.matyja at worldline.com  Wed May 21 09:33:40 2014
From: antoine.matyja at worldline.com (A577127)
Date: Wed, 21 May 2014 06:33:40 -0700 (PDT)
Subject: [aerogear-dev] GCM limit with 1000 registrationIDs
In-Reply-To: <CAAg5f2S5dqCS99CEmV4vEj=76m7rzZ5K-6wLT4PkOxyaHPyACA@mail.gmail.com>
References: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>
	<1400672454662-7879.post@n5.nabble.com>
	<CAAg5f2S5dqCS99CEmV4vEj=76m7rzZ5K-6wLT4PkOxyaHPyACA@mail.gmail.com>
Message-ID: <1400679220199-7887.post@n5.nabble.com>

Uh wrong translation  I mean register tokens. We wrote a java sender that
registers lots of token (we wanted to register 1M tokens) with the REST api
http://aerogear.org/docs/specs/aerogear-push-rest/DeviceRegistration/

But it was very slow (~1/s), looks like the database slows the thing by
making big requests (huge joins ?).



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-GCM-limit-with-1000-registrationIDs-tp7858p7887.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Wed May 21 10:33:17 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 16:33:17 +0200
Subject: [aerogear-dev] GCM limit with 1000 registrationIDs
In-Reply-To: <1400679220199-7887.post@n5.nabble.com>
References: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>
	<1400672454662-7879.post@n5.nabble.com>
	<CAAg5f2S5dqCS99CEmV4vEj=76m7rzZ5K-6wLT4PkOxyaHPyACA@mail.gmail.com>
	<1400679220199-7887.post@n5.nabble.com>
Message-ID: <CAAg5f2TFDZ=hCfLRqLrS9z1pF_pV=19aUeFAAv7njN4jtgaxog@mail.gmail.com>

hey Antoine,

thanks for explaining - I will take a look at this:
https://issues.jboss.org/browse/AGPUSH-661

I will think about making the endpoint completely async (there is no real
benefit in returning a JSON of the device metadata anyways + do some
overhaul on the actual database)


On Wed, May 21, 2014 at 3:33 PM, A577127 <antoine.matyja at worldline.com>wrote:

> Uh wrong translation  I mean register tokens. We wrote a java sender that
> registers lots of token (we wanted to register 1M tokens) with the REST api
> http://aerogear.org/docs/specs/aerogear-push-rest/DeviceRegistration/
>
> But it was very slow (~1/s), looks like the database slows the thing by
> making big requests (huge joins ?).
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-GCM-limit-with-1000-registrationIDs-tp7858p7887.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/20140521/f5ffcad5/attachment.html 

From bruno at abstractj.org  Wed May 21 10:38:02 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 21 May 2014 11:38:02 -0300
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <20140521144810.6b56e7fa@kapy-ntb-x220>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
	<20140520192052.GC67928@abstractj.org>
	<20140521144810.6b56e7fa@kapy-ntb-x220>
Message-ID: <20140521143802.GD30785@abstractj.org>

I don't think you need to prove anything, to me is just the matter of
reach a consensus and think about what works for the whole team.

Is still possible skip checkstyle and leave the mess to the person doing the
release, even worse, the person doing the release can also skip this.

The only thing able to guarantee the quality of the code is the developer's
conscience. I don't think that enforcing checkstyle default rules will make us more
conscious tbh.

On 2014-05-21, Karel Piwko wrote:
> That's not true, it was discussed during team meeting at
> the times we've been using G+ as well (I can't prove that) and on ML as well:
>
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-JavaScript-formatter-td5200.html
>
> It just took 7 month for the PR to be merged. The point of initial checkstyle
> rules set was chosen because:
>
> * It was identified as the least annoying setup on ML, there were a lot of +1s
> * There was a bug in released library caused by using unused import that was not
>   available on classpath. I might be able to dig it out but it would take me a
>   lot of time as I don't recall what project it was.
>
> +9001 for abstract's proposal on having same setup for IDE as well. There is
> nothing more annoying then something working in IDE but not in Maven. -1 for the
> specific profile, as it shifts responsibility to clean up the mess to the person
> doing the release.
>
> Karel
>
> On Tue, 20 May 2014 16:20:52 -0300
> Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > The only reason to have checkstyle enabled by default is: if we agree on
> > which rules should be active or not and provide an specific IDE setup.
> >
> > Other than that, people like me will skip it. Why? Simple, I'm trying to
> > solve critical problems and also strugging to figure out why checkstyle
> > is do care about method lenght.
> >
> > So to me if you're guys really want to introduce it we need:
> >
> > - Definition of which rules were supposed to be active
> > - IDE profiles for Eclipse/IntelliJ
> > - Make the error messages something clear
> >
> > Otherwise, I'm -?. It was never discussed here and if it exists on
> > aerogear-parent is all our fault.
> >
> > On 2014-05-20, Daniel Bevenius wrote:
> > > -1 I'd prefer to have checkstyle enabled by default, and integrate the
> > > checkstyle into the IDE to avoid having to discover issue later when
> > > building with maven.
> > >
> > >
> > > On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org> wrote:
> > >
> > > > +1 on having an specific profile for checkstyle
> > > >
> > > > On 2014-05-20, Matthias Wessendorf wrote:
> > > > > Hello,
> > > > >
> > > > > w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
> > > > >
> > > > > However, I am not that happy, as the default rules are IMO a bit odd
> > > > (e.g.
> > > > > the unused imports is pretty nasty when developing)
> > > > >
> > > > > We could:
> > > > > a) get rid of it (perhaps not)
> > > > > b) disable it on normal execution and only execute it on a release
> > > > profile
> > > > > or like that
> > > > >
> > > > > right now I am running w/ skip - but that's a bit nasty...
> > > > >
> > > > > Thoughts?
> > > > > Matthias
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > >
> > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > twitter: http://twitter.com/mwessendorf
> > > >
> > > > > _______________________________________________
> > > > > aerogear-dev mailing list
> > > > > aerogear-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> > > >
> > > > --
> > > >
> > > > 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
> >
> >
> > --
> >
> > 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

--

abstractj

JBoss, a division of Red Hat

From bruno at abstractj.org  Wed May 21 11:08:36 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 21 May 2014 12:08:36 -0300
Subject: [aerogear-dev] Angular.js branch and UPS
Message-ID: <20140521150836.GA32839@abstractj.org>

Good morning peeps,

While I was navigating at angular branch
(https://github.com/aerogear/aerogear-unifiedpush-server/tree/angular_keycloak), I notice
that you guys don't make use of keycloak.js
(http://docs.jboss.org/keycloak/docs/1.0-alpha-3/userguide/html_single/index.html#d4e546). My
question is: why not? Or this something planned for the future?

My concern is about reinvent what KC already did on the client side.

--

abstractj

From matzew at apache.org  Wed May 21 11:20:00 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 17:20:00 +0200
Subject: [aerogear-dev] Angular.js branch and UPS
In-Reply-To: <20140521150836.GA32839@abstractj.org>
References: <20140521150836.GA32839@abstractj.org>
Message-ID: <CAAg5f2R8JEjqRtoOwFJmnyEBxqKbrbVEXMgFmS6zajwf5sbrqQ@mail.gmail.com>

On Wed, May 21, 2014 at 5:08 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning peeps,
>
> While I was navigating at angular branch
> (
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/angular_keycloak),
> I notice
> that you guys don't make use of keycloak.js
>

you guys ? :) it's more a 'we' are not using it ;-)


I was following this demo template from Bill:
https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups

No usage of keycloak.js there ;)




> (
> http://docs.jboss.org/keycloak/docs/1.0-alpha-3/userguide/html_single/index.html#d4e546).
> My
> question is: why not? Or this something planned for the future?
>


sure, talking to Stian on IRC I got the impression it's good to be used



>
> My concern is about reinvent what KC already did on the client side.
>

yep, fully agree - I can't access JIRA atm, otherwise I'd have created a
"keycloak.js usage" item under the AGPUSH-568 epic




>
> --
>
> 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/20140521/6c4ca0ca/attachment.html 

From scm.blanc at gmail.com  Wed May 21 11:20:44 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 21 May 2014 17:20:44 +0200
Subject: [aerogear-dev] Angular.js branch and UPS
In-Reply-To: <20140521150836.GA32839@abstractj.org>
References: <20140521150836.GA32839@abstractj.org>
Message-ID: <CAD_dpu3Dd01uv027PUOB2aFgmfCv904Gi30At+m=sQeU=Xp2CQ@mail.gmail.com>

I might be wrong but my understanding was that keycloak.js was needed for
pure htlm/JS web apps and not embedded with a backend like we have.


On Wed, May 21, 2014 at 5:08 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning peeps,
>
> While I was navigating at angular branch
> (
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/angular_keycloak),
> I notice
> that you guys don't make use of keycloak.js
> (
> http://docs.jboss.org/keycloak/docs/1.0-alpha-3/userguide/html_single/index.html#d4e546).
> My
> question is: why not? Or this something planned for the future?
>
> My concern is about reinvent what KC already did on the client side.
>
> --
>
> 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/20140521/dc1211d6/attachment.html 

From bruno at abstractj.org  Wed May 21 11:38:32 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 21 May 2014 12:38:32 -0300
Subject: [aerogear-dev] Angular.js branch and UPS
In-Reply-To: <CAAg5f2R8JEjqRtoOwFJmnyEBxqKbrbVEXMgFmS6zajwf5sbrqQ@mail.gmail.com>
References: <20140521150836.GA32839@abstractj.org>
	<CAAg5f2R8JEjqRtoOwFJmnyEBxqKbrbVEXMgFmS6zajwf5sbrqQ@mail.gmail.com>
Message-ID: <20140521153832.GA34280@abstractj.org>

On 2014-05-21, Matthias Wessendorf wrote:
> On Wed, May 21, 2014 at 5:08 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > Good morning peeps,
> >
> > While I was navigating at angular branch
> > (
> > https://github.com/aerogear/aerogear-unifiedpush-server/tree/angular_keycloak),
> > I notice
> > that you guys don't make use of keycloak.js
> >
>
> you guys ? :) it's more a 'we' are not using it ;-)

meh, bad wording.

>
>
> I was following this demo template from Bill:
> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
>
> No usage of keycloak.js there ;)

In theory we do
(https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/pom.xml#L209). Maybe we
just don't use it?

>
>
>
>
> > (
> > http://docs.jboss.org/keycloak/docs/1.0-alpha-3/userguide/html_single/index.html#d4e546).
> > My
> > question is: why not? Or this something planned for the future?
> >
>
>
> sure, talking to Stian on IRC I got the impression it's good to be used
>
>
>
> >
> > My concern is about reinvent what KC already did on the client side.
> >
>
> yep, fully agree - I can't access JIRA atm, otherwise I'd have created a
> "keycloak.js usage" item under the AGPUSH-568 epic
>
>
>
>
> >
> > --
> >
> > 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


--

abstractj

From matzew at apache.org  Wed May 21 11:40:58 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 17:40:58 +0200
Subject: [aerogear-dev] Angular.js branch and UPS
In-Reply-To: <20140521153832.GA34280@abstractj.org>
References: <20140521150836.GA32839@abstractj.org>
	<CAAg5f2R8JEjqRtoOwFJmnyEBxqKbrbVEXMgFmS6zajwf5sbrqQ@mail.gmail.com>
	<20140521153832.GA34280@abstractj.org>
Message-ID: <CAAg5f2RYbRpFX2ksSU+K61UHSaZHjoEqfQx30yT8Hh1=bSpPuQ@mail.gmail.com>

On Wed, May 21, 2014 at 5:38 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> On 2014-05-21, Matthias Wessendorf wrote:
> > On Wed, May 21, 2014 at 5:08 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > Good morning peeps,
> > >
> > > While I was navigating at angular branch
> > > (
> > >
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/angular_keycloak
> ),
> > > I notice
> > > that you guys don't make use of keycloak.js
> > >
> >
> > you guys ? :) it's more a 'we' are not using it ;-)
>
> meh, bad wording.
>
> >
> >
> > I was following this demo template from Bill:
> >
> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
> >
> > No usage of keycloak.js there ;)
>
> In theory we do
> (
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/pom.xml#L209).
> Maybe we
> just don't use it?
>

yeah, I mean their demo I was following did not directly use it;

That said - if it is the right way to go, let's do that

So I'd be a strong supporter for using that one, instead of doing our own :)



>
> >
> >
> >
> >
> > > (
> > >
> http://docs.jboss.org/keycloak/docs/1.0-alpha-3/userguide/html_single/index.html#d4e546
> ).
> > > My
> > > question is: why not? Or this something planned for the future?
> > >
> >
> >
> > sure, talking to Stian on IRC I got the impression it's good to be used
> >
> >
> >
> > >
> > > My concern is about reinvent what KC already did on the client side.
> > >
> >
> > yep, fully agree - I can't access JIRA atm, otherwise I'd have created a
> > "keycloak.js usage" item under the AGPUSH-568 epic
> >
> >
> >
> >
> > >
> > > --
> > >
> > > 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
>
>
> --
>
> 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/20140521/ae5116f0/attachment.html 

From hbons at redhat.com  Wed May 21 12:19:48 2014
From: hbons at redhat.com (Hylke Bons)
Date: Wed, 21 May 2014 17:19:48 +0100
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
Message-ID: <537CD224.3050306@redhat.com>

Hey,

The "Status" column only show errors. If there are none it will say 
something amongst the lines of "Everything is fine".

About the graphic: Sure, it's just the wireframe and may still change in 
the visual design depending on what looks good.

Thanks,

Hylke

On 19/05/2014 16:48, Matt Carrano wrote:
> Hey Hylke,
>
> This is looking good. I had a few minor comments/questions about the layout and labeling.  Take a look at the marked up wireframe (attached).
>
> -Matt
>
> ----- Original Message -----
> From: "Hylke Bons" <hbons at redhat.com>
> To: aerogear-dev at lists.jboss.org
> Cc: "Matt Carrano" <mcarrano at redhat.com>
> Sent: Monday, May 19, 2014 8:03:13 AM
> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
>
> Hello,
>
> Here are some updates based on the feedback from the meetings:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> - Simplified dashboard stats
> - Apps notifications table
> - Defined entry points
>
> Let me know what you think. I hope that covers everything.
>
> Thanks,
>
> Hylke
>
>
>
> On 15/05/2014 16:19, Hylke Bons wrote:
>> Hey,
>>
>> Here's an initial version:
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>
>> I tried to incorporate most wishes expressed in the other thread.
>>
>> Most notable things:
>> - Landing page with an overview of stats, most active apps, and error
>> messages
>> - Activity table shows both registration and notification events
>> - Activity table is per variant, and not all activity on the server.
>> Unless there's a usecase to have every event for every app/variant in a
>> table I don't think we actually need it. The important thing is to get
>> to error messages easily.
>>
>> Things to do/think about:
>> - links/entry points to the activity table
>> - filtering the activity table
>>
>> This is just the first iteration and we will improve on this.
>> Let me know what you think.
>>
>> Thanks,
>>
>> Hylke
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From bsutter at redhat.com  Wed May 21 14:41:11 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Wed, 21 May 2014 14:41:11 -0400
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <537CD224.3050306@redhat.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
	<537CD224.3050306@redhat.com>
Message-ID: <5533FB53-6955-4466-9FB8-635EA930165A@redhat.com>


On May 21, 2014, at 12:19 PM, Hylke Bons <hbons at redhat.com> wrote:

> Hey,
> 
> The "Status" column only show errors. If there are none it will say 
> something amongst the lines of "Everything is fine".
I guess what threw me off was that the Status box links to the Activity page - at least based on how I read that orange arrow connecting the two.


> 
> About the graphic: Sure, it's just the wireframe and may still change in 
> the visual design depending on what looks good.
> 
> Thanks,
> 
> Hylke
> 
> On 19/05/2014 16:48, Matt Carrano wrote:
>> Hey Hylke,
>> 
>> This is looking good. I had a few minor comments/questions about the layout and labeling.  Take a look at the marked up wireframe (attached).
>> 
>> -Matt
>> 
>> ----- Original Message -----
>> From: "Hylke Bons" <hbons at redhat.com>
>> To: aerogear-dev at lists.jboss.org
>> Cc: "Matt Carrano" <mcarrano at redhat.com>
>> Sent: Monday, May 19, 2014 8:03:13 AM
>> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
>> 
>> Hello,
>> 
>> Here are some updates based on the feedback from the meetings:
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> - Simplified dashboard stats
>> - Apps notifications table
>> - Defined entry points
>> 
>> Let me know what you think. I hope that covers everything.
>> 
>> Thanks,
>> 
>> Hylke
>> 
>> 
>> 
>> On 15/05/2014 16:19, Hylke Bons wrote:
>>> Hey,
>>> 
>>> Here's an initial version:
>>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>> 
>>> I tried to incorporate most wishes expressed in the other thread.
>>> 
>>> Most notable things:
>>> - Landing page with an overview of stats, most active apps, and error
>>> messages
>>> - Activity table shows both registration and notification events
>>> - Activity table is per variant, and not all activity on the server.
>>> Unless there's a usecase to have every event for every app/variant in a
>>> table I don't think we actually need it. The important thing is to get
>>> to error messages easily.
>>> 
>>> Things to do/think about:
>>> - links/entry points to the activity table
>>> - filtering the activity table
>>> 
>>> This is just the first iteration and we will improve on this.
>>> Let me know what you think.
>>> 
>>> 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



From matzew at apache.org  Wed May 21 15:43:23 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 21:43:23 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <5533FB53-6955-4466-9FB8-635EA930165A@redhat.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
	<537CD224.3050306@redhat.com>
	<5533FB53-6955-4466-9FB8-635EA930165A@redhat.com>
Message-ID: <CAAg5f2RxqR1ye+ScqBSua2JGMrpoy7KrqDs3UaKA8yUS9YxNqQ@mail.gmail.com>

BTW. on the top box (first screen), I am querying the DB per user:
- "my" applications (the active is worthless)
- notifications delivered by "my" apps
- devices registered with "my" apps

https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png

It would be odd if I see how many apps are on the entire server etc ;-)



On Wed, May 21, 2014 at 8:41 PM, Burr Sutter <bsutter at redhat.com> wrote:

>
> On May 21, 2014, at 12:19 PM, Hylke Bons <hbons at redhat.com> wrote:
>
> > Hey,
> >
> > The "Status" column only show errors. If there are none it will say
> > something amongst the lines of "Everything is fine".
> I guess what threw me off was that the Status box links to the Activity
> page - at least based on how I read that orange arrow connecting the two.
>
>
> >
> > About the graphic: Sure, it's just the wireframe and may still change in
> > the visual design depending on what looks good.
> >
> > Thanks,
> >
> > Hylke
> >
> > On 19/05/2014 16:48, Matt Carrano wrote:
> >> Hey Hylke,
> >>
> >> This is looking good. I had a few minor comments/questions about the
> layout and labeling.  Take a look at the marked up wireframe (attached).
> >>
> >> -Matt
> >>
> >> ----- Original Message -----
> >> From: "Hylke Bons" <hbons at redhat.com>
> >> To: aerogear-dev at lists.jboss.org
> >> Cc: "Matt Carrano" <mcarrano at redhat.com>
> >> Sent: Monday, May 19, 2014 8:03:13 AM
> >> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
> >>
> >> Hello,
> >>
> >> Here are some updates based on the feedback from the meetings:
> >>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >> - Simplified dashboard stats
> >> - Apps notifications table
> >> - Defined entry points
> >>
> >> Let me know what you think. I hope that covers everything.
> >>
> >> Thanks,
> >>
> >> Hylke
> >>
> >>
> >>
> >> On 15/05/2014 16:19, Hylke Bons wrote:
> >>> Hey,
> >>>
> >>> Here's an initial version:
> >>>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >>>
> >>> I tried to incorporate most wishes expressed in the other thread.
> >>>
> >>> Most notable things:
> >>> - Landing page with an overview of stats, most active apps, and error
> >>> messages
> >>> - Activity table shows both registration and notification events
> >>> - Activity table is per variant, and not all activity on the server.
> >>> Unless there's a usecase to have every event for every app/variant in a
> >>> table I don't think we actually need it. The important thing is to get
> >>> to error messages easily.
> >>>
> >>> Things to do/think about:
> >>> - links/entry points to the activity table
> >>> - filtering the activity table
> >>>
> >>> This is just the first iteration and we will improve on this.
> >>> Let me know what you think.
> >>>
> >>> 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
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140521/9de4dc67/attachment.html 

From bsutter at redhat.com  Wed May 21 15:55:11 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Wed, 21 May 2014 15:55:11 -0400
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <CAAg5f2RxqR1ye+ScqBSua2JGMrpoy7KrqDs3UaKA8yUS9YxNqQ@mail.gmail.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
	<537CD224.3050306@redhat.com>
	<5533FB53-6955-4466-9FB8-635EA930165A@redhat.com>
	<CAAg5f2RxqR1ye+ScqBSua2JGMrpoy7KrqDs3UaKA8yUS9YxNqQ@mail.gmail.com>
Message-ID: <EE3AC5E1-D0C3-4041-8054-51B5252DB998@redhat.com>


On May 21, 2014, at 3:43 PM, Matthias Wessendorf <matzew at apache.org> wrote:

> BTW. on the top box (first screen), I am querying the DB per user:
> - "my" applications (the active is worthless)
OK - so the "5" in the wireframe would be the "Total of My Apps"?

> - notifications delivered by "my" apps
Yes, that makes sense

> - devices registered with "my" apps

And when did we add the concept of "my" apps, I thought there was only "super-user" who sees all apps.

> 
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> 
> It would be odd if I see how many apps are on the entire server etc ;-) 
> 
> 
> 
> On Wed, May 21, 2014 at 8:41 PM, Burr Sutter <bsutter at redhat.com> wrote:
> 
> On May 21, 2014, at 12:19 PM, Hylke Bons <hbons at redhat.com> wrote:
> 
> > Hey,
> >
> > The "Status" column only show errors. If there are none it will say
> > something amongst the lines of "Everything is fine".
> I guess what threw me off was that the Status box links to the Activity page - at least based on how I read that orange arrow connecting the two.
> 
> 
> >
> > About the graphic: Sure, it's just the wireframe and may still change in
> > the visual design depending on what looks good.
> >
> > Thanks,
> >
> > Hylke
> >
> > On 19/05/2014 16:48, Matt Carrano wrote:
> >> Hey Hylke,
> >>
> >> This is looking good. I had a few minor comments/questions about the layout and labeling.  Take a look at the marked up wireframe (attached).
> >>
> >> -Matt
> >>
> >> ----- Original Message -----
> >> From: "Hylke Bons" <hbons at redhat.com>
> >> To: aerogear-dev at lists.jboss.org
> >> Cc: "Matt Carrano" <mcarrano at redhat.com>
> >> Sent: Monday, May 19, 2014 8:03:13 AM
> >> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
> >>
> >> Hello,
> >>
> >> Here are some updates based on the feedback from the meetings:
> >> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >> - Simplified dashboard stats
> >> - Apps notifications table
> >> - Defined entry points
> >>
> >> Let me know what you think. I hope that covers everything.
> >>
> >> Thanks,
> >>
> >> Hylke
> >>
> >>
> >>
> >> On 15/05/2014 16:19, Hylke Bons wrote:
> >>> Hey,
> >>>
> >>> Here's an initial version:
> >>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >>>
> >>> I tried to incorporate most wishes expressed in the other thread.
> >>>
> >>> Most notable things:
> >>> - Landing page with an overview of stats, most active apps, and error
> >>> messages
> >>> - Activity table shows both registration and notification events
> >>> - Activity table is per variant, and not all activity on the server.
> >>> Unless there's a usecase to have every event for every app/variant in a
> >>> table I don't think we actually need it. The important thing is to get
> >>> to error messages easily.
> >>>
> >>> Things to do/think about:
> >>> - links/entry points to the activity table
> >>> - filtering the activity table
> >>>
> >>> This is just the first iteration and we will improve on this.
> >>> Let me know what you think.
> >>>
> >>> 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
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140521/04088b09/attachment-0001.html 

From matzew at apache.org  Wed May 21 16:24:24 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 22:24:24 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <EE3AC5E1-D0C3-4041-8054-51B5252DB998@redhat.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
	<537CD224.3050306@redhat.com>
	<5533FB53-6955-4466-9FB8-635EA930165A@redhat.com>
	<CAAg5f2RxqR1ye+ScqBSua2JGMrpoy7KrqDs3UaKA8yUS9YxNqQ@mail.gmail.com>
	<EE3AC5E1-D0C3-4041-8054-51B5252DB998@redhat.com>
Message-ID: <CAAg5f2Rr45GwvqT4AKV1eCL4ihqEoy-ndK_K4m82bL_MBHnNjg@mail.gmail.com>

On Wed, May 21, 2014 at 9:55 PM, Burr Sutter <bsutter at redhat.com> wrote:

>
> On May 21, 2014, at 3:43 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> BTW. on the top box (first screen), I am querying the DB per user:
> - "my" applications (the active is worthless)
>
> OK - so the "5" in the wireframe would be the "Total of My Apps"?
>

yes


> - notifications delivered by "my" apps
>
> Yes, that makes sense
>
> - devices registered with "my" apps
>
>
> And when did we add the concept of "my" apps, I thought there was only
> "super-user" who sees all apps.
>

we had that already on the 'agenda' for the initial user-management - but
we skipped our own impl. due to Keycloak adpotion;

A recent thread:
http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007783.html


In here I describe a 'super-user' and a 'PushAdmin':
http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007784.html


Or do you think a 'shared' super-user is good enough? IMO it would be odd
if HR Manager and Marketing Manager would be seeing each others apps;

Feel free to chime in on that related thread




>
>
>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
> It would be odd if I see how many apps are on the entire server etc ;-)
>
>
>
> On Wed, May 21, 2014 at 8:41 PM, Burr Sutter <bsutter at redhat.com> wrote:
>
>>
>> On May 21, 2014, at 12:19 PM, Hylke Bons <hbons at redhat.com> wrote:
>>
>> > Hey,
>> >
>> > The "Status" column only show errors. If there are none it will say
>> > something amongst the lines of "Everything is fine".
>> I guess what threw me off was that the Status box links to the Activity
>> page - at least based on how I read that orange arrow connecting the two.
>>
>>
>> >
>> > About the graphic: Sure, it's just the wireframe and may still change in
>> > the visual design depending on what looks good.
>> >
>> > Thanks,
>> >
>> > Hylke
>> >
>> > On 19/05/2014 16:48, Matt Carrano wrote:
>> >> Hey Hylke,
>> >>
>> >> This is looking good. I had a few minor comments/questions about the
>> layout and labeling.  Take a look at the marked up wireframe (attached).
>> >>
>> >> -Matt
>> >>
>> >> ----- Original Message -----
>> >> From: "Hylke Bons" <hbons at redhat.com>
>> >> To: aerogear-dev at lists.jboss.org
>> >> Cc: "Matt Carrano" <mcarrano at redhat.com>
>> >> Sent: Monday, May 19, 2014 8:03:13 AM
>> >> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
>> >>
>> >> Hello,
>> >>
>> >> Here are some updates based on the feedback from the meetings:
>> >>
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> >> - Simplified dashboard stats
>> >> - Apps notifications table
>> >> - Defined entry points
>> >>
>> >> Let me know what you think. I hope that covers everything.
>> >>
>> >> Thanks,
>> >>
>> >> Hylke
>> >>
>> >>
>> >>
>> >> On 15/05/2014 16:19, Hylke Bons wrote:
>> >>> Hey,
>> >>>
>> >>> Here's an initial version:
>> >>>
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> >>>
>> >>> I tried to incorporate most wishes expressed in the other thread.
>> >>>
>> >>> Most notable things:
>> >>> - Landing page with an overview of stats, most active apps, and error
>> >>> messages
>> >>> - Activity table shows both registration and notification events
>> >>> - Activity table is per variant, and not all activity on the server.
>> >>> Unless there's a usecase to have every event for every app/variant in
>> a
>> >>> table I don't think we actually need it. The important thing is to get
>> >>> to error messages easily.
>> >>>
>> >>> Things to do/think about:
>> >>> - links/entry points to the activity table
>> >>> - filtering the activity table
>> >>>
>> >>> This is just the first iteration and we will improve on this.
>> >>> Let me know what you think.
>> >>>
>> >>> 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
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140521/9801451a/attachment.html 

From matzew at apache.org  Wed May 21 16:37:38 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 21 May 2014 22:37:38 +0200
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <20140521125543.GC92541@abstractj.org>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
Message-ID: <CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>

Just a thought... regarding those two roles 'PushAdmin' and 'Super-User',
IMO the Super-user should be able to see all apps (and their variants,
including registered devices).




On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Thank you Matthias, I will look at it and return back with more
> questions if necessary.
>
> On 2014-05-21, Matthias Wessendorf wrote:
> > Hello,
> >
> > yes - the handling is done by Keycloak itself; Last time we looked at
> user
> > management, we had the following in terms of roles:
> >
> > https://gist.github.com/sebastienblanc/6547605
> >
> > Not sure the names of these roles are great.... let's see
> >
> > Basically I think the role definition in the gist still addresses most of
> > what we want to archive:
> > * super-user: in charge of managing the UPS realm (including users); can
> > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > * PushAdmin: Someone that can manage applications and variants, but is
> not
> > able to add new users; he also sees only his applications/variants etc
> > (that's the developer in sebis gist)
> >
> > The gist also contains a 'Viewer' role - At this point I am not sure we
> do
> > really need this. My impression is that if we have PushAdmins for our
> 1.0.0
> > community release that will be enough.
> >
> > -Matthias
> >
> >
> >
> >
> > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <bruno at abstractj.org
> >wrote:
> >
> > > Good morning peeps,
> > >
> > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I would
> > > like to understand what do you guys want say with this issue.
> > >
> > > Currently Keycloak already has its own user/roles managements. What do
> > > you guys are looking for? Any specific requirements?
> > >
> > > --
> > >
> > > 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
>
>
> --
>
> 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/20140521/78d47aa2/attachment.html 

From jbalunas at redhat.com  Wed May 21 16:40:17 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Wed, 21 May 2014 16:40:17 -0400
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
Message-ID: <6F81DF84-E820-4FDB-9A06-D9125D3B6FBD@redhat.com>


On May 21, 2014, at 4:37 PM, Matthias Wessendorf <matzew at apache.org> wrote:

> Just a thought... regarding those two roles 'PushAdmin' and 'Super-User', IMO the Super-user should be able to see all apps (and their variants, including registered devices).

+1 imo someone needs to have the overall view.

> 
> 
> 
> 
> On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> Thank you Matthias, I will look at it and return back with more
> questions if necessary.
> 
> On 2014-05-21, Matthias Wessendorf wrote:
> > Hello,
> >
> > yes - the handling is done by Keycloak itself; Last time we looked at user
> > management, we had the following in terms of roles:
> >
> > https://gist.github.com/sebastienblanc/6547605
> >
> > Not sure the names of these roles are great.... let's see
> >
> > Basically I think the role definition in the gist still addresses most of
> > what we want to archive:
> > * super-user: in charge of managing the UPS realm (including users); can
> > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > * PushAdmin: Someone that can manage applications and variants, but is not
> > able to add new users; he also sees only his applications/variants etc
> > (that's the developer in sebis gist)
> >
> > The gist also contains a 'Viewer' role - At this point I am not sure we do
> > really need this. My impression is that if we have PushAdmins for our 1.0.0
> > community release that will be enough.
> >
> > -Matthias
> >
> >
> >
> >
> > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <bruno at abstractj.org>wrote:
> >
> > > Good morning peeps,
> > >
> > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I would
> > > like to understand what do you guys want say with this issue.
> > >
> > > Currently Keycloak already has its own user/roles managements. What do
> > > you guys are looking for? Any specific requirements?
> > >
> > > --
> > >
> > > 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
> 
> 
> --
> 
> 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/20140521/65b035cd/attachment-0001.html 

From edewit at redhat.com  Thu May 22 02:39:03 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 22 May 2014 08:39:03 +0200
Subject: [aerogear-dev] cordova angular quick start demo
In-Reply-To: <1398550160919-7588.post@n5.nabble.com>
References: <2F5B8A91-F681-4B8A-9D59-EFEFF8CDEEC4@redhat.com>
	<3B072A76-B780-496B-97DB-B7ED0C217B91@redhat.com>
	<1D82326B-4F90-4469-B5C4-617E9E2F097F@redhat.com>
	<409B6E7D-BD13-487E-ABE3-EC40D66DAB40@redhat.com>
	<1398479312724-7582.post@n5.nabble.com>
	<CAAg5f2QZ47MKdFUjBrgSrq2bV0EoFtdO2fyL57Q+Y=FC5fMaTA@mail.gmail.com>
	<6FB1647F-1F18-4B42-A168-D807BB276D0C@gmail.com>
	<1398550160919-7588.post@n5.nabble.com>
Message-ID: <74B6DC47-E376-4C55-85EC-C002E47447BA@redhat.com>

Hi,

I?ve started working on a AngularJs version of the quick start demo and I?ve based it upon ionic. Having components and support for gestures out of the box really makes sense to me. So Keith if you are still interested in helping, I have a branch where I?ve started https://github.com/edewit/aerogear-push-quickstarts/tree/angular

Cheers,
	Erik Jan

On 27 Apr,2014, at 0:09 , keithdmoore94 <keith at kdmooreconsulting.com> wrote:

> Where can I find the "mobile contacts quickstart demo" you speak of ?  On a
> side note, does anyone know how I can get the "mobile" import folder that
> has the "Import Cordova Project" option in Eclipse Kepler?   I noticed some
> screenshots of it in the  aerogear-push-helloworld-cordova
> <https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova>   
> readme page.  
> 
> 
> 
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-cordova-angular-quick-start-demo-tp7568p7588.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/20140522/c16c9d9e/attachment.html 

From kpiwko at redhat.com  Thu May 22 07:31:42 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Thu, 22 May 2014 13:31:42 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <20140521143802.GD30785@abstractj.org>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
	<20140520192052.GC67928@abstractj.org>
	<20140521144810.6b56e7fa@kapy-ntb-x220>
	<20140521143802.GD30785@abstractj.org>
Message-ID: <20140522133142.32164c99@kapy-ntb-x220>

This is the same issue as with unit tests. If they tend to take too
much time, people are skipping them. 

What about activating checkstyle in CI and or Git push hook, for both PRs and
direct commits upstream. This way a developer can develop without constraints
*until* he wants to push the code upstream. Would it help?

Thanks,

Karel

On Wed, 21 May 2014 11:38:02 -0300
Bruno Oliveira <bruno at abstractj.org> wrote:

> I don't think you need to prove anything, to me is just the matter of
> reach a consensus and think about what works for the whole team.
> 
> Is still possible skip checkstyle and leave the mess to the person doing the
> release, even worse, the person doing the release can also skip this.
> 
> The only thing able to guarantee the quality of the code is the developer's
> conscience. I don't think that enforcing checkstyle default rules will make
> us more conscious tbh.
> 
> On 2014-05-21, Karel Piwko wrote:
> > That's not true, it was discussed during team meeting at
> > the times we've been using G+ as well (I can't prove that) and on ML as
> > well:
> >
> > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-JavaScript-formatter-td5200.html
> >
> > It just took 7 month for the PR to be merged. The point of initial
> > checkstyle rules set was chosen because:
> >
> > * It was identified as the least annoying setup on ML, there were a lot of
> > +1s
> > * There was a bug in released library caused by using unused import that
> > was not available on classpath. I might be able to dig it out but it would
> > take me a lot of time as I don't recall what project it was.
> >
> > +9001 for abstract's proposal on having same setup for IDE as well. There is
> > nothing more annoying then something working in IDE but not in Maven. -1
> > for the specific profile, as it shifts responsibility to clean up the mess
> > to the person doing the release.
> >
> > Karel
> >
> > On Tue, 20 May 2014 16:20:52 -0300
> > Bruno Oliveira <bruno at abstractj.org> wrote:
> >
> > > The only reason to have checkstyle enabled by default is: if we agree on
> > > which rules should be active or not and provide an specific IDE setup.
> > >
> > > Other than that, people like me will skip it. Why? Simple, I'm trying to
> > > solve critical problems and also strugging to figure out why checkstyle
> > > is do care about method lenght.
> > >
> > > So to me if you're guys really want to introduce it we need:
> > >
> > > - Definition of which rules were supposed to be active
> > > - IDE profiles for Eclipse/IntelliJ
> > > - Make the error messages something clear
> > >
> > > Otherwise, I'm -?. It was never discussed here and if it exists on
> > > aerogear-parent is all our fault.
> > >
> > > On 2014-05-20, Daniel Bevenius wrote:
> > > > -1 I'd prefer to have checkstyle enabled by default, and integrate the
> > > > checkstyle into the IDE to avoid having to discover issue later when
> > > > building with maven.
> > > >
> > > >
> > > > On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org> wrote:
> > > >
> > > > > +1 on having an specific profile for checkstyle
> > > > >
> > > > > On 2014-05-20, Matthias Wessendorf wrote:
> > > > > > Hello,
> > > > > >
> > > > > > w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
> > > > > >
> > > > > > However, I am not that happy, as the default rules are IMO a bit odd
> > > > > (e.g.
> > > > > > the unused imports is pretty nasty when developing)
> > > > > >
> > > > > > We could:
> > > > > > a) get rid of it (perhaps not)
> > > > > > b) disable it on normal execution and only execute it on a release
> > > > > profile
> > > > > > or like that
> > > > > >
> > > > > > right now I am running w/ skip - but that's a bit nasty...
> > > > > >
> > > > > > Thoughts?
> > > > > > Matthias
> > > > > >
> > > > > > --
> > > > > > Matthias Wessendorf
> > > > > >
> > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > > twitter: http://twitter.com/mwessendorf
> > > > >
> > > > > > _______________________________________________
> > > > > > aerogear-dev mailing list
> > > > > > aerogear-dev at lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > 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
> > >
> > >
> > > --
> > >
> > > 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
> 
> --
> 
> 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


From matzew at apache.org  Thu May 22 07:50:59 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 22 May 2014 13:50:59 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <20140522133142.32164c99@kapy-ntb-x220>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
	<20140520192052.GC67928@abstractj.org>
	<20140521144810.6b56e7fa@kapy-ntb-x220>
	<20140521143802.GD30785@abstractj.org>
	<20140522133142.32164c99@kapy-ntb-x220>
Message-ID: <CAAg5f2Rai43FK3mkacge6u-bN_KJtxozrinO7WPUA3KeVKVOjQ@mail.gmail.com>

On Thursday, May 22, 2014, Karel Piwko <kpiwko at redhat.com> wrote:

> This is the same issue as with unit tests. If they tend to take too
> much time, people are skipping them.
>
> What about activating checkstyle in CI and or Git push hook, for both PRs
> and
> direct commits upstream. This way a developer can develop without
> constraints
> *until* he wants to push the code upstream. Would it help?


-1

I think we should work on proper templates for our IDEs instead



>
> Thanks,
>
> Karel
>
> On Wed, 21 May 2014 11:38:02 -0300
> Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > I don't think you need to prove anything, to me is just the matter of
> > reach a consensus and think about what works for the whole team.
> >
> > Is still possible skip checkstyle and leave the mess to the person doing
> the
> > release, even worse, the person doing the release can also skip this.
> >
> > The only thing able to guarantee the quality of the code is the
> developer's
> > conscience. I don't think that enforcing checkstyle default rules will
> make
> > us more conscious tbh.
> >
> > On 2014-05-21, Karel Piwko wrote:
> > > That's not true, it was discussed during team meeting at
> > > the times we've been using G+ as well (I can't prove that) and on ML as
> > > well:
> > >
> > >
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-JavaScript-formatter-td5200.html
> > >
> > > It just took 7 month for the PR to be merged. The point of initial
> > > checkstyle rules set was chosen because:
> > >
> > > * It was identified as the least annoying setup on ML, there were a
> lot of
> > > +1s
> > > * There was a bug in released library caused by using unused import
> that
> > > was not available on classpath. I might be able to dig it out but it
> would
> > > take me a lot of time as I don't recall what project it was.
> > >
> > > +9001 for abstract's proposal on having same setup for IDE as well.
> There is
> > > nothing more annoying then something working in IDE but not in Maven.
> -1
> > > for the specific profile, as it shifts responsibility to clean up the
> mess
> > > to the person doing the release.
> > >
> > > Karel
> > >
> > > On Tue, 20 May 2014 16:20:52 -0300
> > > Bruno Oliveira <bruno at abstractj.org> wrote:
> > >
> > > > The only reason to have checkstyle enabled by default is: if we
> agree on
> > > > which rules should be active or not and provide an specific IDE
> setup.
> > > >
> > > > Other than that, people like me will skip it. Why? Simple, I'm
> trying to
> > > > solve critical problems and also strugging to figure out why
> checkstyle
> > > > is do care about method lenght.
> > > >
> > > > So to me if you're guys really want to introduce it we need:
> > > >
> > > > - Definition of which rules were supposed to be active
> > > > - IDE profiles for Eclipse/IntelliJ
> > > > - Make the error messages something clear
> > > >
> > > > Otherwise, I'm -?. It was never discussed here and if it exists on
> > > > aerogear-parent is all our fault.
> > > >
> > > > On 2014-05-20, Daniel Bevenius wrote:
> > > > > -1 I'd prefer to have checkstyle enabled by default, and integrate
> the
> > > > > checkstyle into the IDE to avoid having to discover issue later
> when
> > > > > building with maven.
> > > > >
> > > > >
> > > > > On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org> wrote:
> > > > >
> > > > > > +1 on having an specific profile for checkstyle
> > > > > >
> > > > > > On 2014-05-20, Matthias Wessendorf wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
> > > > > > >
> > > > > > > However, I am not that happy, as the default rules are IMO a
> bit odd
> > > > > > (e.g.
> > > > > > > the unused imports is pretty nasty when developing)
> > > > > > >
> > > > > > > We could:
> > > > > > > a) get rid of it (perhaps not)
> > > > > > > b) disable it on normal execution and only execute it on a
> release
> > > > > > profile
> > > > > > > or like that
> > > > > > >
> > > > > > > right now I am running w/ skip - but that's a bit nasty...
> > > > > > >
> > > > > > > Thoughts?
> > > > > > > Matthias
> > > > > > >
> > > >



-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140522/07de91fb/attachment.html 

From bruno at abstractj.org  Thu May 22 08:34:03 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 22 May 2014 09:34:03 -0300
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <20140522133142.32164c99@kapy-ntb-x220>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
	<20140520192052.GC67928@abstractj.org>
	<20140521144810.6b56e7fa@kapy-ntb-x220>
	<20140521143802.GD30785@abstractj.org>
	<20140522133142.32164c99@kapy-ntb-x220>
Message-ID: <20140522123403.GB57419@abstractj.org>

Hi Karel, with the appropriate templates in place, that would make
sense.

I vote for adding it on CI.

On 2014-05-22, Karel Piwko wrote:
> This is the same issue as with unit tests. If they tend to take too
> much time, people are skipping them.
>
> What about activating checkstyle in CI and or Git push hook, for both PRs and
> direct commits upstream. This way a developer can develop without constraints
> *until* he wants to push the code upstream. Would it help?
>
> Thanks,
>
> Karel
>
> On Wed, 21 May 2014 11:38:02 -0300
> Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > I don't think you need to prove anything, to me is just the matter of
> > reach a consensus and think about what works for the whole team.
> >
> > Is still possible skip checkstyle and leave the mess to the person doing the
> > release, even worse, the person doing the release can also skip this.
> >
> > The only thing able to guarantee the quality of the code is the developer's
> > conscience. I don't think that enforcing checkstyle default rules will make
> > us more conscious tbh.
> >
> > On 2014-05-21, Karel Piwko wrote:
> > > That's not true, it was discussed during team meeting at
> > > the times we've been using G+ as well (I can't prove that) and on ML as
> > > well:
> > >
> > > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-JavaScript-formatter-td5200.html
> > >
> > > It just took 7 month for the PR to be merged. The point of initial
> > > checkstyle rules set was chosen because:
> > >
> > > * It was identified as the least annoying setup on ML, there were a lot of
> > > +1s
> > > * There was a bug in released library caused by using unused import that
> > > was not available on classpath. I might be able to dig it out but it would
> > > take me a lot of time as I don't recall what project it was.
> > >
> > > +9001 for abstract's proposal on having same setup for IDE as well. There is
> > > nothing more annoying then something working in IDE but not in Maven. -1
> > > for the specific profile, as it shifts responsibility to clean up the mess
> > > to the person doing the release.
> > >
> > > Karel
> > >
> > > On Tue, 20 May 2014 16:20:52 -0300
> > > Bruno Oliveira <bruno at abstractj.org> wrote:
> > >
> > > > The only reason to have checkstyle enabled by default is: if we agree on
> > > > which rules should be active or not and provide an specific IDE setup.
> > > >
> > > > Other than that, people like me will skip it. Why? Simple, I'm trying to
> > > > solve critical problems and also strugging to figure out why checkstyle
> > > > is do care about method lenght.
> > > >
> > > > So to me if you're guys really want to introduce it we need:
> > > >
> > > > - Definition of which rules were supposed to be active
> > > > - IDE profiles for Eclipse/IntelliJ
> > > > - Make the error messages something clear
> > > >
> > > > Otherwise, I'm -?. It was never discussed here and if it exists on
> > > > aerogear-parent is all our fault.
> > > >
> > > > On 2014-05-20, Daniel Bevenius wrote:
> > > > > -1 I'd prefer to have checkstyle enabled by default, and integrate the
> > > > > checkstyle into the IDE to avoid having to discover issue later when
> > > > > building with maven.
> > > > >
> > > > >
> > > > > On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org> wrote:
> > > > >
> > > > > > +1 on having an specific profile for checkstyle
> > > > > >
> > > > > > On 2014-05-20, Matthias Wessendorf wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
> > > > > > >
> > > > > > > However, I am not that happy, as the default rules are IMO a bit odd
> > > > > > (e.g.
> > > > > > > the unused imports is pretty nasty when developing)
> > > > > > >
> > > > > > > We could:
> > > > > > > a) get rid of it (perhaps not)
> > > > > > > b) disable it on normal execution and only execute it on a release
> > > > > > profile
> > > > > > > or like that
> > > > > > >
> > > > > > > right now I am running w/ skip - but that's a bit nasty...
> > > > > > >
> > > > > > > Thoughts?
> > > > > > > Matthias
> > > > > > >
> > > > > > > --
> > > > > > > Matthias Wessendorf
> > > > > > >
> > > > > > > blog: http://matthiaswessendorf.wordpress.com/
> > > > > > > sessions: http://www.slideshare.net/mwessendorf
> > > > > > > twitter: http://twitter.com/mwessendorf
> > > > > >
> > > > > > > _______________________________________________
> > > > > > > aerogear-dev mailing list
> > > > > > > aerogear-dev at lists.jboss.org
> > > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > 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
> > > >
> > > >
> > > > --
> > > >
> > > > 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
> >
> > --
> >
> > 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
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj

From corinnekrych at gmail.com  Thu May 22 09:49:40 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 22 May 2014 15:49:40 +0200
Subject: [aerogear-dev] [Mobile Push 1.0.0] Client SDKs for Android,
	Cordova and iOS
In-Reply-To: <1400598565142-7865.post@n5.nabble.com>
References: <CAAg5f2Sb=qUTOi=z_6-RhPRPMnw_pF8eGouo6MSkAFDLRqEknw@mail.gmail.com>
	<CAD_dpu2upQHRD7pU8Xg5GxbTcro_btb9YHOt5H2rTJB-Yy+v-g@mail.gmail.com>
	<1400598565142-7865.post@n5.nabble.com>
Message-ID: <E61DA3CC-412B-429B-A3BE-333F4A1C6D30@gmail.com>

Indeed we?re all good for iOS push registration lib.
++
Corinne
On 20 May 2014, at 17:09, Andrea Vibelli <avibelli at redhat.com> wrote:

> Hi, 
> I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5 an old
> issue (http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
> about the google-play-services version shipped inside the cordova plugin.
> 
> Thanks
> Andrea
> 
> 
> Sebastien Blanc wrote
>> Hi,
>> For the Cordova Push Plugin there is one (trivial) item open that should
>> be
>> fixed before 1.0.  I created a jira to track it
>> https://issues.jboss.org/browse/AGCORDOVA-4
>> 
>> 
>> 
>> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
> 
>> matzew@
> 
>> &gt;wrote:
>> 
>>> Hi,
>>> 
>>> as said before (see [1]), this summer we will release the AeroGear Mobile
>>> Push 1.0.0 to the community.
>>> 
>>> I took a look at the related JIRAs (see [2]) and noticed that for the
>>> mobile client SDKs there are no outstanding tickets. Yay!
>>> 
>>> The github repos are also in an OK state :-) there are no feature related
>>> open PRs; Well, besides a test improvement for the Cordova push plugin -
>>> but that will be addressed soon;
>>> 
>>> My question is: Are you guys aware of any features that we need to add to
>>> Android, Cordova or iOS, related for push ?
>>> 
>>> Once the Android and iOS bits are 'done', lets make sure we use those
>>> latest versions on our Cordova plugin ;-)
>>> 
>>> Thanks!
>>> Matthias
>>> 
>>> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>>> [2] https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>>> 
>>> 
>>> --
>>> Matthias Wessendorf
>>> 
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> 
> 
>> aerogear-dev at .jboss
> 
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
> 
>> aerogear-dev at .jboss
> 
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> 
> 
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.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 May 22 10:14:34 2014
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 22 May 2014 10:14:34 -0400
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <20140522123403.GB57419@abstractj.org>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
	<20140520192052.GC67928@abstractj.org>
	<20140521144810.6b56e7fa@kapy-ntb-x220>
	<20140521143802.GD30785@abstractj.org>
	<20140522133142.32164c99@kapy-ntb-x220>
	<20140522123403.GB57419@abstractj.org>
Message-ID: <537E064A.5010208@redhat.com>

On Thu 22 May 2014 08:34:03 AM EDT, Bruno Oliveira wrote:
> Hi Karel, with the appropriate templates in place, that would make
> sense.
>
> I vote for adding it on CI.
+1

In general I like the idea of checkstyle and friends, but it really 
slows down the code test commit flow when something trips me up.

It should probably be a profile thing like you said before.

>
> On 2014-05-22, Karel Piwko wrote:
>> This is the same issue as with unit tests. If they tend to take too
>> much time, people are skipping them.
>>
>> What about activating checkstyle in CI and or Git push hook, for both PRs and
>> direct commits upstream. This way a developer can develop without constraints
>> *until* he wants to push the code upstream. Would it help?
>>
>> Thanks,
>>
>> Karel
>>
>> On Wed, 21 May 2014 11:38:02 -0300
>> Bruno Oliveira <bruno at abstractj.org> wrote:
>>
>>> I don't think you need to prove anything, to me is just the matter of
>>> reach a consensus and think about what works for the whole team.
>>>
>>> Is still possible skip checkstyle and leave the mess to the person doing the
>>> release, even worse, the person doing the release can also skip this.
>>>
>>> The only thing able to guarantee the quality of the code is the developer's
>>> conscience. I don't think that enforcing checkstyle default rules will make
>>> us more conscious tbh.
>>>
>>> On 2014-05-21, Karel Piwko wrote:
>>>> That's not true, it was discussed during team meeting at
>>>> the times we've been using G+ as well (I can't prove that) and on ML as
>>>> well:
>>>>
>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-JavaScript-formatter-td5200.html
>>>>
>>>> It just took 7 month for the PR to be merged. The point of initial
>>>> checkstyle rules set was chosen because:
>>>>
>>>> * It was identified as the least annoying setup on ML, there were a lot of
>>>> +1s
>>>> * There was a bug in released library caused by using unused import that
>>>> was not available on classpath. I might be able to dig it out but it would
>>>> take me a lot of time as I don't recall what project it was.
>>>>
>>>> +9001 for abstract's proposal on having same setup for IDE as well. There is
>>>> nothing more annoying then something working in IDE but not in Maven. -1
>>>> for the specific profile, as it shifts responsibility to clean up the mess
>>>> to the person doing the release.
>>>>
>>>> Karel
>>>>
>>>> On Tue, 20 May 2014 16:20:52 -0300
>>>> Bruno Oliveira <bruno at abstractj.org> wrote:
>>>>
>>>>> The only reason to have checkstyle enabled by default is: if we agree on
>>>>> which rules should be active or not and provide an specific IDE setup.
>>>>>
>>>>> Other than that, people like me will skip it. Why? Simple, I'm trying to
>>>>> solve critical problems and also strugging to figure out why checkstyle
>>>>> is do care about method lenght.
>>>>>
>>>>> So to me if you're guys really want to introduce it we need:
>>>>>
>>>>> - Definition of which rules were supposed to be active
>>>>> - IDE profiles for Eclipse/IntelliJ
>>>>> - Make the error messages something clear
>>>>>
>>>>> Otherwise, I'm -?. It was never discussed here and if it exists on
>>>>> aerogear-parent is all our fault.
>>>>>
>>>>> On 2014-05-20, Daniel Bevenius wrote:
>>>>>> -1 I'd prefer to have checkstyle enabled by default, and integrate the
>>>>>> checkstyle into the IDE to avoid having to discover issue later when
>>>>>> building with maven.
>>>>>>
>>>>>>
>>>>>> On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org> wrote:
>>>>>>
>>>>>>> +1 on having an specific profile for checkstyle
>>>>>>>
>>>>>>> On 2014-05-20, Matthias Wessendorf wrote:
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> w/ the advent of the 0.2.0 parent, we have checkstyle enabled;
>>>>>>>>
>>>>>>>> However, I am not that happy, as the default rules are IMO a bit odd
>>>>>>> (e.g.
>>>>>>>> the unused imports is pretty nasty when developing)
>>>>>>>>
>>>>>>>> We could:
>>>>>>>> a) get rid of it (perhaps not)
>>>>>>>> b) disable it on normal execution and only execute it on a release
>>>>>>> profile
>>>>>>>> or like that
>>>>>>>>
>>>>>>>> right now I am running w/ skip - but that's a bit nasty...
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>> Matthias
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matthias Wessendorf
>>>>>>>>
>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> 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
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> 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
>>>
>>> --
>>>
>>> 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
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
>
> abstractj
> _______________________________________________
> 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 bdawidow at redhat.com  Fri May 23 04:35:09 2014
From: bdawidow at redhat.com (=?UTF-8?B?Qm9sZXPFgmF3IERhd2lkb3dpY3o=?=)
Date: Fri, 23 May 2014 10:35:09 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <CAAg5f2Rai43FK3mkacge6u-bN_KJtxozrinO7WPUA3KeVKVOjQ@mail.gmail.com>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>	<20140520185603.GA67928@abstractj.org>	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>	<20140520192052.GC67928@abstractj.org>	<20140521144810.6b56e7fa@kapy-ntb-x220>	<20140521143802.GD30785@abstractj.org>	<20140522133142.32164c99@kapy-ntb-x220>
	<CAAg5f2Rai43FK3mkacge6u-bN_KJtxozrinO7WPUA3KeVKVOjQ@mail.gmail.com>
Message-ID: <537F083D.4090507@redhat.com>

On 05/22/2014 01:50 PM, Matthias Wessendorf wrote:
>
>
> On Thursday, May 22, 2014, Karel Piwko <kpiwko at redhat.com
> <mailto:kpiwko at redhat.com>> wrote:
>
>     This is the same issue as with unit tests. If they tend to take too
>     much time, people are skipping them.
>
>     What about activating checkstyle in CI and or Git push hook, for
>     both PRs and
>     direct commits upstream. This way a developer can develop without
>     constraints
>     *until* he wants to push the code upstream. Would it help?
>
>
> -1
>
> I think we should work on proper templates for our IDEs instead


Major issue with IDE templates is that you cannot get both IDEA and 
Eclipse to reformat code in whole project into exactly same outcome. 
Unless you force people to use Eclipse formatter plugin in IDEA.

Also... checkstyle maven plugin is buggy... :)

>
>
>     Thanks,
>
>     Karel
>
>     On Wed, 21 May 2014 11:38:02 -0300
>     Bruno Oliveira <bruno at abstractj.org> wrote:
>
>      > I don't think you need to prove anything, to me is just the matter of
>      > reach a consensus and think about what works for the whole team.
>      >
>      > Is still possible skip checkstyle and leave the mess to the
>     person doing the
>      > release, even worse, the person doing the release can also skip this.
>      >
>      > The only thing able to guarantee the quality of the code is the
>     developer's
>      > conscience. I don't think that enforcing checkstyle default rules
>     will make
>      > us more conscious tbh.
>      >
>      > On 2014-05-21, Karel Piwko wrote:
>      > > That's not true, it was discussed during team meeting at
>      > > the times we've been using G+ as well (I can't prove that) and
>     on ML as
>      > > well:
>      > >
>      > >
>     http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-JavaScript-formatter-td5200.html
>      > >
>      > > It just took 7 month for the PR to be merged. The point of initial
>      > > checkstyle rules set was chosen because:
>      > >
>      > > * It was identified as the least annoying setup on ML, there
>     were a lot of
>      > > +1s
>      > > * There was a bug in released library caused by using unused
>     import that
>      > > was not available on classpath. I might be able to dig it out
>     but it would
>      > > take me a lot of time as I don't recall what project it was.
>      > >
>      > > +9001 for abstract's proposal on having same setup for IDE as
>     well. There is
>      > > nothing more annoying then something working in IDE but not in
>     Maven. -1
>      > > for the specific profile, as it shifts responsibility to clean
>     up the mess
>      > > to the person doing the release.
>      > >
>      > > Karel
>      > >
>      > > On Tue, 20 May 2014 16:20:52 -0300
>      > > Bruno Oliveira <bruno at abstractj.org> wrote:
>      > >
>      > > > The only reason to have checkstyle enabled by default is: if
>     we agree on
>      > > > which rules should be active or not and provide an specific
>     IDE setup.
>      > > >
>      > > > Other than that, people like me will skip it. Why? Simple,
>     I'm trying to
>      > > > solve critical problems and also strugging to figure out why
>     checkstyle
>      > > > is do care about method lenght.
>      > > >
>      > > > So to me if you're guys really want to introduce it we need:
>      > > >
>      > > > - Definition of which rules were supposed to be active
>      > > > - IDE profiles for Eclipse/IntelliJ
>      > > > - Make the error messages something clear
>      > > >
>      > > > Otherwise, I'm -?. It was never discussed here and if it
>     exists on
>      > > > aerogear-parent is all our fault.
>      > > >
>      > > > On 2014-05-20, Daniel Bevenius wrote:
>      > > > > -1 I'd prefer to have checkstyle enabled by default, and
>     integrate the
>      > > > > checkstyle into the IDE to avoid having to discover issue
>     later when
>      > > > > building with maven.
>      > > > >
>      > > > >
>      > > > > On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org>
>     wrote:
>      > > > >
>      > > > > > +1 on having an specific profile for checkstyle
>      > > > > >
>      > > > > > On 2014-05-20, Matthias Wessendorf wrote:
>      > > > > > > Hello,
>      > > > > > >
>      > > > > > > w/ the advent of the 0.2.0 parent, we have checkstyle
>     enabled;
>      > > > > > >
>      > > > > > > However, I am not that happy, as the default rules are
>     IMO a bit odd
>      > > > > > (e.g.
>      > > > > > > the unused imports is pretty nasty when developing)
>      > > > > > >
>      > > > > > > We could:
>      > > > > > > a) get rid of it (perhaps not)
>      > > > > > > b) disable it on normal execution and only execute it
>     on a release
>      > > > > > profile
>      > > > > > > or like that
>      > > > > > >
>      > > > > > > right now I am running w/ skip - but that's a bit nasty...
>      > > > > > >
>      > > > > > > Thoughts?
>      > > > > > > Matthias
>      > > > > > >
>      > > >
>
>
>
> --
> Sent from Gmail Mobile
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Boles?aw Dawidowicz
JBoss Portal Platform Architect | GateIn Portal Project Lead

From matzew at apache.org  Fri May 23 05:24:03 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 23 May 2014 11:24:03 +0200
Subject: [aerogear-dev] Internal 'API' change for the different Senders?
Message-ID: <CAAg5f2SburX-MNUTyEe7RACQZZ7ajhzMhjTiK52dJULJE9LtOw@mail.gmail.com>

Hello,

looking at the Senders, I'd like to re-introduce an interface which they
all extend:

/**
 * Each implementation deals with the specific of the underlying push
network, including transforming the content of the
 * {@link UnifiedPushMessage} to the proper message format of the
actual push network and maintaining the connection to it.
 */
public interface PushNotificationSender {

    /**
     * Sends the {@link UnifiedPushMessage} to the given clients,
identified by a collection of tokens, the underlying push network.
     *
     * @param variant contains details for the underlying push
network, e.g. API Keys/Ids
     * @param clientIdentifiers platform specific collection of client
identifiers
     * @param pushMessage payload to be send to the given clients
     * @param senderCallback invoked after submitting the request to
the underlying push network to indicate the status
     *                       of the request (<code>success</code> or
<code>error</code>
     */
    void sendPushMessage(Variant variant, Collection<String>
clientIdentifiers, UnifiedPushMessage pushMessage,
NotificationSenderCallback senderCallback);
}

What's really new here is passing in a 'callback'
(NotificationSenderCallback) that gives the caller of an
PushNotificationSender implementation a hint if we could submit the
messages to the push network, or not:

/**
 * A simple Callback interface used when sending {@link
org.jboss.aerogear.unifiedpush.message.UnifiedPushMessage} to
 * an actual push network.
 */
public interface NotificationSenderCallback {

    /**
     * Simple indicator which will be called on a successful to
deliver to the push network. However, the invocation of
     * this callback does <b>NOT</b> mean the messages have been sent
out to the mobile devices. The invocation simply means
     * the {@link
org.jboss.aerogear.unifiedpush.message.sender.PushNotificationSender}
was able to send the messages to
     * the push network for its further processing
     */
    void onSuccess();

    /**
     * Simple indicator which will be called on any type of error that
occurred while sending the payload to the
     * underlying push network.
     */
    void onError();
}

The reason why I'd like to do that is this give me better access to the
state of the request (for submitting messages). That is generally a nice
thing to be aware of the request-state. For our new "push history" overview
(see related threads), this comes handy, as I have all the needed
information in a more centralized place, instead of injecting a 'Metrics'
service into all the PushNotificationSender implementations:

...
// save APNs-delivery timestamp to metrics-database
// save number of APNs tokens to metrics-database
myAPNsSender.sendPushMessage(variant, collectionOfTokensForVariant,
upsMessage, new NotificationSenderCallback() {
    @Override
    public void onSuccess() {
        // save success status for the given variant to metrics-database
    }

    @Override
    public void onError() {
        // save failure status for the given variant to metrics-database
    }
});


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140523/cc618aeb/attachment-0001.html 

From matzew at apache.org  Fri May 23 05:24:59 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 23 May 2014 11:24:59 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <537F083D.4090507@redhat.com>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>
	<20140520185603.GA67928@abstractj.org>
	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>
	<20140520192052.GC67928@abstractj.org>
	<20140521144810.6b56e7fa@kapy-ntb-x220>
	<20140521143802.GD30785@abstractj.org>
	<20140522133142.32164c99@kapy-ntb-x220>
	<CAAg5f2Rai43FK3mkacge6u-bN_KJtxozrinO7WPUA3KeVKVOjQ@mail.gmail.com>
	<537F083D.4090507@redhat.com>
Message-ID: <CAAg5f2RORntNLdhg21sabWA0gmwfRqnNzG7FucAr_2dr_hEexg@mail.gmail.com>

On Fri, May 23, 2014 at 10:35 AM, Boles?aw Dawidowicz
<bdawidow at redhat.com>wrote:

> On 05/22/2014 01:50 PM, Matthias Wessendorf wrote:
> >
> >
> > On Thursday, May 22, 2014, Karel Piwko <kpiwko at redhat.com
> > <mailto:kpiwko at redhat.com>> wrote:
> >
> >     This is the same issue as with unit tests. If they tend to take too
> >     much time, people are skipping them.
> >
> >     What about activating checkstyle in CI and or Git push hook, for
> >     both PRs and
> >     direct commits upstream. This way a developer can develop without
> >     constraints
> >     *until* he wants to push the code upstream. Would it help?
> >
> >
> > -1
> >
> > I think we should work on proper templates for our IDEs instead
>
>
> Major issue with IDE templates is that you cannot get both IDEA and
> Eclipse to reformat code in whole project into exactly same outcome.
> Unless you force people to use Eclipse formatter plugin in IDEA.
>
> Also... checkstyle maven plugin is buggy... :)
>

sounds like you love checkstyle too :)


>
> >
> >
> >     Thanks,
> >
> >     Karel
> >
> >     On Wed, 21 May 2014 11:38:02 -0300
> >     Bruno Oliveira <bruno at abstractj.org> wrote:
> >
> >      > I don't think you need to prove anything, to me is just the
> matter of
> >      > reach a consensus and think about what works for the whole team.
> >      >
> >      > Is still possible skip checkstyle and leave the mess to the
> >     person doing the
> >      > release, even worse, the person doing the release can also skip
> this.
> >      >
> >      > The only thing able to guarantee the quality of the code is the
> >     developer's
> >      > conscience. I don't think that enforcing checkstyle default rules
> >     will make
> >      > us more conscious tbh.
> >      >
> >      > On 2014-05-21, Karel Piwko wrote:
> >      > > That's not true, it was discussed during team meeting at
> >      > > the times we've been using G+ as well (I can't prove that) and
> >     on ML as
> >      > > well:
> >      > >
> >      > >
> >
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-JavaScript-formatter-td5200.html
> >      > >
> >      > > It just took 7 month for the PR to be merged. The point of
> initial
> >      > > checkstyle rules set was chosen because:
> >      > >
> >      > > * It was identified as the least annoying setup on ML, there
> >     were a lot of
> >      > > +1s
> >      > > * There was a bug in released library caused by using unused
> >     import that
> >      > > was not available on classpath. I might be able to dig it out
> >     but it would
> >      > > take me a lot of time as I don't recall what project it was.
> >      > >
> >      > > +9001 for abstract's proposal on having same setup for IDE as
> >     well. There is
> >      > > nothing more annoying then something working in IDE but not in
> >     Maven. -1
> >      > > for the specific profile, as it shifts responsibility to clean
> >     up the mess
> >      > > to the person doing the release.
> >      > >
> >      > > Karel
> >      > >
> >      > > On Tue, 20 May 2014 16:20:52 -0300
> >      > > Bruno Oliveira <bruno at abstractj.org> wrote:
> >      > >
> >      > > > The only reason to have checkstyle enabled by default is: if
> >     we agree on
> >      > > > which rules should be active or not and provide an specific
> >     IDE setup.
> >      > > >
> >      > > > Other than that, people like me will skip it. Why? Simple,
> >     I'm trying to
> >      > > > solve critical problems and also strugging to figure out why
> >     checkstyle
> >      > > > is do care about method lenght.
> >      > > >
> >      > > > So to me if you're guys really want to introduce it we need:
> >      > > >
> >      > > > - Definition of which rules were supposed to be active
> >      > > > - IDE profiles for Eclipse/IntelliJ
> >      > > > - Make the error messages something clear
> >      > > >
> >      > > > Otherwise, I'm -?. It was never discussed here and if it
> >     exists on
> >      > > > aerogear-parent is all our fault.
> >      > > >
> >      > > > On 2014-05-20, Daniel Bevenius wrote:
> >      > > > > -1 I'd prefer to have checkstyle enabled by default, and
> >     integrate the
> >      > > > > checkstyle into the IDE to avoid having to discover issue
> >     later when
> >      > > > > building with maven.
> >      > > > >
> >      > > > >
> >      > > > > On 20 May 2014 20:56, Bruno Oliveira <bruno at abstractj.org>
> >     wrote:
> >      > > > >
> >      > > > > > +1 on having an specific profile for checkstyle
> >      > > > > >
> >      > > > > > On 2014-05-20, Matthias Wessendorf wrote:
> >      > > > > > > Hello,
> >      > > > > > >
> >      > > > > > > w/ the advent of the 0.2.0 parent, we have checkstyle
> >     enabled;
> >      > > > > > >
> >      > > > > > > However, I am not that happy, as the default rules are
> >     IMO a bit odd
> >      > > > > > (e.g.
> >      > > > > > > the unused imports is pretty nasty when developing)
> >      > > > > > >
> >      > > > > > > We could:
> >      > > > > > > a) get rid of it (perhaps not)
> >      > > > > > > b) disable it on normal execution and only execute it
> >     on a release
> >      > > > > > profile
> >      > > > > > > or like that
> >      > > > > > >
> >      > > > > > > right now I am running w/ skip - but that's a bit
> nasty...
> >      > > > > > >
> >      > > > > > > Thoughts?
> >      > > > > > > Matthias
> >      > > > > > >
> >      > > >
> >
> >
> >
> > --
> > Sent from Gmail Mobile
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
>
>
>
> --
> Boles?aw Dawidowicz
> JBoss Portal Platform Architect | GateIn Portal Project Lead
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140523/bb2494dd/attachment.html 

From matzew at apache.org  Fri May 23 05:45:21 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 23 May 2014 11:45:21 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <CAAg5f2Rr45GwvqT4AKV1eCL4ihqEoy-ndK_K4m82bL_MBHnNjg@mail.gmail.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
	<537CD224.3050306@redhat.com>
	<5533FB53-6955-4466-9FB8-635EA930165A@redhat.com>
	<CAAg5f2RxqR1ye+ScqBSua2JGMrpoy7KrqDs3UaKA8yUS9YxNqQ@mail.gmail.com>
	<EE3AC5E1-D0C3-4041-8054-51B5252DB998@redhat.com>
	<CAAg5f2Rr45GwvqT4AKV1eCL4ihqEoy-ndK_K4m82bL_MBHnNjg@mail.gmail.com>
Message-ID: <CAAg5f2TxXYeWbcFa6Do8oOKrzMBz9aSE3rj1Ww72WFCUWLJq9A@mail.gmail.com>

Hylke ,

do you have some of the HTML based mock-ups already ? E.g. for the
dashboard ?

Thanks!
Matthias


On Wed, May 21, 2014 at 10:24 PM, Matthias Wessendorf <matzew at apache.org>wrote:

>
>
>
> On Wed, May 21, 2014 at 9:55 PM, Burr Sutter <bsutter at redhat.com> wrote:
>
>>
>> On May 21, 2014, at 3:43 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>> BTW. on the top box (first screen), I am querying the DB per user:
>> - "my" applications (the active is worthless)
>>
>> OK - so the "5" in the wireframe would be the "Total of My Apps"?
>>
>
> yes
>
>
>> - notifications delivered by "my" apps
>>
>> Yes, that makes sense
>>
>> - devices registered with "my" apps
>>
>>
>> And when did we add the concept of "my" apps, I thought there was only
>> "super-user" who sees all apps.
>>
>
> we had that already on the 'agenda' for the initial user-management - but
> we skipped our own impl. due to Keycloak adpotion;
>
> A recent thread:
> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007783.html
>
>
> In here I describe a 'super-user' and a 'PushAdmin':
> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007784.html
>
>
> Or do you think a 'shared' super-user is good enough? IMO it would be odd
> if HR Manager and Marketing Manager would be seeing each others apps;
>
> Feel free to chime in on that related thread
>
>
>
>
>>
>>
>>
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>
>> It would be odd if I see how many apps are on the entire server etc ;-)
>>
>>
>>
>> On Wed, May 21, 2014 at 8:41 PM, Burr Sutter <bsutter at redhat.com> wrote:
>>
>>>
>>> On May 21, 2014, at 12:19 PM, Hylke Bons <hbons at redhat.com> wrote:
>>>
>>> > Hey,
>>> >
>>> > The "Status" column only show errors. If there are none it will say
>>> > something amongst the lines of "Everything is fine".
>>> I guess what threw me off was that the Status box links to the Activity
>>> page - at least based on how I read that orange arrow connecting the two.
>>>
>>>
>>> >
>>> > About the graphic: Sure, it's just the wireframe and may still change
>>> in
>>> > the visual design depending on what looks good.
>>> >
>>> > Thanks,
>>> >
>>> > Hylke
>>> >
>>> > On 19/05/2014 16:48, Matt Carrano wrote:
>>> >> Hey Hylke,
>>> >>
>>> >> This is looking good. I had a few minor comments/questions about the
>>> layout and labeling.  Take a look at the marked up wireframe (attached).
>>> >>
>>> >> -Matt
>>> >>
>>> >> ----- Original Message -----
>>> >> From: "Hylke Bons" <hbons at redhat.com>
>>> >> To: aerogear-dev at lists.jboss.org
>>> >> Cc: "Matt Carrano" <mcarrano at redhat.com>
>>> >> Sent: Monday, May 19, 2014 8:03:13 AM
>>> >> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
>>> >>
>>> >> Hello,
>>> >>
>>> >> Here are some updates based on the feedback from the meetings:
>>> >>
>>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>> >> - Simplified dashboard stats
>>> >> - Apps notifications table
>>> >> - Defined entry points
>>> >>
>>> >> Let me know what you think. I hope that covers everything.
>>> >>
>>> >> Thanks,
>>> >>
>>> >> Hylke
>>> >>
>>> >>
>>> >>
>>> >> On 15/05/2014 16:19, Hylke Bons wrote:
>>> >>> Hey,
>>> >>>
>>> >>> Here's an initial version:
>>> >>>
>>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>> >>>
>>> >>> I tried to incorporate most wishes expressed in the other thread.
>>> >>>
>>> >>> Most notable things:
>>> >>> - Landing page with an overview of stats, most active apps, and error
>>> >>> messages
>>> >>> - Activity table shows both registration and notification events
>>> >>> - Activity table is per variant, and not all activity on the server.
>>> >>> Unless there's a usecase to have every event for every app/variant
>>> in a
>>> >>> table I don't think we actually need it. The important thing is to
>>> get
>>> >>> to error messages easily.
>>> >>>
>>> >>> Things to do/think about:
>>> >>> - links/entry points to the activity table
>>> >>> - filtering the activity table
>>> >>>
>>> >>> This is just the first iteration and we will improve on this.
>>> >>> Let me know what you think.
>>> >>>
>>> >>> 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
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140523/56c2b329/attachment-0001.html 

From scm.blanc at gmail.com  Fri May 23 05:48:26 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 23 May 2014 11:48:26 +0200
Subject: [aerogear-dev] Internal 'API' change for the different Senders?
In-Reply-To: <CAAg5f2SburX-MNUTyEe7RACQZZ7ajhzMhjTiK52dJULJE9LtOw@mail.gmail.com>
References: <CAAg5f2SburX-MNUTyEe7RACQZZ7ajhzMhjTiK52dJULJE9LtOw@mail.gmail.com>
Message-ID: <CAD_dpu05ouNja04kg20r1cTZMKQVpgymKRyXQUpcSQRSvVsGzw@mail.gmail.com>

Looks like a great enhancement to me , +1 !



On Fri, May 23, 2014 at 11:24 AM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hello,
>
> looking at the Senders, I'd like to re-introduce an interface which they
> all extend:
>
> /**
>  * Each implementation deals with the specific of the underlying push network, including transforming the content of the
>  * {@link UnifiedPushMessage} to the proper message format of the actual push network and maintaining the connection to it.
>  */
> public interface PushNotificationSender {
>
>     /**
>      * Sends the {@link UnifiedPushMessage} to the given clients, identified by a collection of tokens, the underlying push network.
>      *
>      * @param variant contains details for the underlying push network, e.g. API Keys/Ids
>      * @param clientIdentifiers platform specific collection of client identifiers
>      * @param pushMessage payload to be send to the given clients
>      * @param senderCallback invoked after submitting the request to the underlying push network to indicate the status
>      *                       of the request (<code>success</code> or <code>error</code>
>      */
>     void sendPushMessage(Variant variant, Collection<String> clientIdentifiers, UnifiedPushMessage pushMessage, NotificationSenderCallback senderCallback);
> }
>
> What's really new here is passing in a 'callback'
> (NotificationSenderCallback) that gives the caller of an
> PushNotificationSender implementation a hint if we could submit the
> messages to the push network, or not:
>
> /**
>  * A simple Callback interface used when sending {@link org.jboss.aerogear.unifiedpush.message.UnifiedPushMessage} to
>  * an actual push network.
>  */
> public interface NotificationSenderCallback {
>
>     /**
>      * Simple indicator which will be called on a successful to deliver to the push network. However, the invocation of
>      * this callback does <b>NOT</b> mean the messages have been sent out to the mobile devices. The invocation simply means
>      * the {@link org.jboss.aerogear.unifiedpush.message.sender.PushNotificationSender} was able to send the messages to
>      * the push network for its further processing
>      */
>     void onSuccess();
>
>     /**
>      * Simple indicator which will be called on any type of error that occurred while sending the payload to the
>      * underlying push network.
>      */
>     void onError();
> }
>
> The reason why I'd like to do that is this give me better access to the
> state of the request (for submitting messages). That is generally a nice
> thing to be aware of the request-state. For our new "push history" overview
> (see related threads), this comes handy, as I have all the needed
> information in a more centralized place, instead of injecting a 'Metrics'
> service into all the PushNotificationSender implementations:
>
> ...
> // save APNs-delivery timestamp to metrics-database
> // save number of APNs tokens to metrics-database
> myAPNsSender.sendPushMessage(variant, collectionOfTokensForVariant, upsMessage, new NotificationSenderCallback() {
>     @Override
>     public void onSuccess() {
>         // save success status for the given variant to metrics-database
>     }
>
>     @Override
>     public void onError() {
>         // save failure status for the given variant to metrics-database
>     }
> });
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140523/b026a065/attachment.html 

From daniel at passos.me  Fri May 23 09:18:50 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 23 May 2014 10:18:50 -0300
Subject: [aerogear-dev] [Mobile Push 1.0.0] Client SDKs for Android,
 Cordova and iOS
In-Reply-To: <E61DA3CC-412B-429B-A3BE-333F4A1C6D30@gmail.com>
References: <CAAg5f2Sb=qUTOi=z_6-RhPRPMnw_pF8eGouo6MSkAFDLRqEknw@mail.gmail.com>
	<CAD_dpu2upQHRD7pU8Xg5GxbTcro_btb9YHOt5H2rTJB-Yy+v-g@mail.gmail.com>
	<1400598565142-7865.post@n5.nabble.com>
	<E61DA3CC-412B-429B-A3BE-333F4A1C6D30@gmail.com>
Message-ID: <CAKjsGbvvr=q0RMWwH+rkYyq_1Cne80ETZ=+4CrArt76QBU-A=g@mail.gmail.com>

All done in the android land

-- Passos


On Thu, May 22, 2014 at 10:49 AM, Corinne Krych <corinnekrych at gmail.com>wrote:

> Indeed we?re all good for iOS push registration lib.
> ++
> Corinne
> On 20 May 2014, at 17:09, Andrea Vibelli <avibelli at redhat.com> wrote:
>
> > Hi,
> > I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5 an
> old
> > issue (
> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
> > about the google-play-services version shipped inside the cordova plugin.
> >
> > Thanks
> > Andrea
> >
> >
> > Sebastien Blanc wrote
> >> Hi,
> >> For the Cordova Push Plugin there is one (trivial) item open that should
> >> be
> >> fixed before 1.0.  I created a jira to track it
> >> https://issues.jboss.org/browse/AGCORDOVA-4
> >>
> >>
> >>
> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
> >
> >> matzew@
> >
> >> &gt;wrote:
> >>
> >>> Hi,
> >>>
> >>> as said before (see [1]), this summer we will release the AeroGear
> Mobile
> >>> Push 1.0.0 to the community.
> >>>
> >>> I took a look at the related JIRAs (see [2]) and noticed that for the
> >>> mobile client SDKs there are no outstanding tickets. Yay!
> >>>
> >>> The github repos are also in an OK state :-) there are no feature
> related
> >>> open PRs; Well, besides a test improvement for the Cordova push plugin
> -
> >>> but that will be addressed soon;
> >>>
> >>> My question is: Are you guys aware of any features that we need to add
> to
> >>> Android, Cordova or iOS, related for push ?
> >>>
> >>> Once the Android and iOS bits are 'done', lets make sure we use those
> >>> latest versions on our Cordova plugin ;-)
> >>>
> >>> Thanks!
> >>> Matthias
> >>>
> >>> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
> >>> [2] https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
> >>>
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>>
> >
> >> aerogear-dev at .jboss
> >
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >
> >> aerogear-dev at .jboss
> >
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.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/20140523/9919edab/attachment.html 

From bsutter at redhat.com  Fri May 23 09:33:57 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Fri, 23 May 2014 09:33:57 -0400
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <CAAg5f2Rr45GwvqT4AKV1eCL4ihqEoy-ndK_K4m82bL_MBHnNjg@mail.gmail.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
	<537CD224.3050306@redhat.com>
	<5533FB53-6955-4466-9FB8-635EA930165A@redhat.com>
	<CAAg5f2RxqR1ye+ScqBSua2JGMrpoy7KrqDs3UaKA8yUS9YxNqQ@mail.gmail.com>
	<EE3AC5E1-D0C3-4041-8054-51B5252DB998@redhat.com>
	<CAAg5f2Rr45GwvqT4AKV1eCL4ihqEoy-ndK_K4m82bL_MBHnNjg@mail.gmail.com>
Message-ID: <4D22FD44-A52B-4056-861D-7AC335363D60@redhat.com>


On May 21, 2014, at 4:24 PM, Matthias Wessendorf <matzew at apache.org> wrote:

> 
> 
> 
> On Wed, May 21, 2014 at 9:55 PM, Burr Sutter <bsutter at redhat.com> wrote:
> 
> On May 21, 2014, at 3:43 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
>> BTW. on the top box (first screen), I am querying the DB per user:
>> - "my" applications (the active is worthless)
> OK - so the "5" in the wireframe would be the "Total of My Apps"?
> 
> yes 
> 
> 
>> - notifications delivered by "my" apps
> Yes, that makes sense
> 
>> - devices registered with "my" apps
> 
> And when did we add the concept of "my" apps, I thought there was only "super-user" who sees all apps.
> 
> we had that already on the 'agenda' for the initial user-management - but we skipped our own impl. due to Keycloak adpotion;
> 
> A recent thread:
> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007783.html
> 
> 
> In here I describe a 'super-user' and a 'PushAdmin':
> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007784.html
> 
> 
> Or do you think a 'shared' super-user is good enough? IMO it would be odd if HR Manager and Marketing Manager would be seeing each others apps;
I was thinking that the HR Manager & Marketing Manager would not be "push admins" - they would not know how to upload the pubkey from Apple.   
I like the idea of having a PushAdmin per app - so that they only break their own apps.   But it would still likely be an IT person who pays the $99 and sets everything up.



> 
> Feel free to chime in on that related thread 
> 
> 
>  
> 
>> 
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> 
>> It would be odd if I see how many apps are on the entire server etc ;-) 
>> 
>> 
>> 
>> On Wed, May 21, 2014 at 8:41 PM, Burr Sutter <bsutter at redhat.com> wrote:
>> 
>> On May 21, 2014, at 12:19 PM, Hylke Bons <hbons at redhat.com> wrote:
>> 
>> > Hey,
>> >
>> > The "Status" column only show errors. If there are none it will say
>> > something amongst the lines of "Everything is fine".
>> I guess what threw me off was that the Status box links to the Activity page - at least based on how I read that orange arrow connecting the two.
>> 
>> 
>> >
>> > About the graphic: Sure, it's just the wireframe and may still change in
>> > the visual design depending on what looks good.
>> >
>> > Thanks,
>> >
>> > Hylke
>> >
>> > On 19/05/2014 16:48, Matt Carrano wrote:
>> >> Hey Hylke,
>> >>
>> >> This is looking good. I had a few minor comments/questions about the layout and labeling.  Take a look at the marked up wireframe (attached).
>> >>
>> >> -Matt
>> >>
>> >> ----- Original Message -----
>> >> From: "Hylke Bons" <hbons at redhat.com>
>> >> To: aerogear-dev at lists.jboss.org
>> >> Cc: "Matt Carrano" <mcarrano at redhat.com>
>> >> Sent: Monday, May 19, 2014 8:03:13 AM
>> >> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
>> >>
>> >> Hello,
>> >>
>> >> Here are some updates based on the feedback from the meetings:
>> >> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> >> - Simplified dashboard stats
>> >> - Apps notifications table
>> >> - Defined entry points
>> >>
>> >> Let me know what you think. I hope that covers everything.
>> >>
>> >> Thanks,
>> >>
>> >> Hylke
>> >>
>> >>
>> >>
>> >> On 15/05/2014 16:19, Hylke Bons wrote:
>> >>> Hey,
>> >>>
>> >>> Here's an initial version:
>> >>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> >>>
>> >>> I tried to incorporate most wishes expressed in the other thread.
>> >>>
>> >>> Most notable things:
>> >>> - Landing page with an overview of stats, most active apps, and error
>> >>> messages
>> >>> - Activity table shows both registration and notification events
>> >>> - Activity table is per variant, and not all activity on the server.
>> >>> Unless there's a usecase to have every event for every app/variant in a
>> >>> table I don't think we actually need it. The important thing is to get
>> >>> to error messages easily.
>> >>>
>> >>> Things to do/think about:
>> >>> - links/entry points to the activity table
>> >>> - filtering the activity table
>> >>>
>> >>> This is just the first iteration and we will improve on this.
>> >>> Let me know what you think.
>> >>>
>> >>> 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
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140523/129f0d80/attachment-0001.html 

From daniel at passos.me  Fri May 23 09:35:03 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 23 May 2014 10:35:03 -0300
Subject: [aerogear-dev] Internal 'API' change for the different Senders?
In-Reply-To: <CAD_dpu05ouNja04kg20r1cTZMKQVpgymKRyXQUpcSQRSvVsGzw@mail.gmail.com>
References: <CAAg5f2SburX-MNUTyEe7RACQZZ7ajhzMhjTiK52dJULJE9LtOw@mail.gmail.com>
	<CAD_dpu05ouNja04kg20r1cTZMKQVpgymKRyXQUpcSQRSvVsGzw@mail.gmail.com>
Message-ID: <CAKjsGbszWSFyjC9yfHSgpd_aiw4O3BazmDoY01DFsc6Eb9T77w@mail.gmail.com>

+1


On Fri, May 23, 2014 at 6:48 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:

> Looks like a great enhancement to me , +1 !
>
>
>
> On Fri, May 23, 2014 at 11:24 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>> Hello,
>>
>> looking at the Senders, I'd like to re-introduce an interface which they
>> all extend:
>>
>> /**
>>  * Each implementation deals with the specific of the underlying push network, including transforming the content of the
>>  * {@link UnifiedPushMessage} to the proper message format of the actual push network and maintaining the connection to it.
>>  */
>> public interface PushNotificationSender {
>>
>>     /**
>>      * Sends the {@link UnifiedPushMessage} to the given clients, identified by a collection of tokens, the underlying push network.
>>      *
>>      * @param variant contains details for the underlying push network, e.g. API Keys/Ids
>>      * @param clientIdentifiers platform specific collection of client identifiers
>>      * @param pushMessage payload to be send to the given clients
>>      * @param senderCallback invoked after submitting the request to the underlying push network to indicate the status
>>      *                       of the request (<code>success</code> or <code>error</code>
>>      */
>>     void sendPushMessage(Variant variant, Collection<String> clientIdentifiers, UnifiedPushMessage pushMessage, NotificationSenderCallback senderCallback);
>> }
>>
>> What's really new here is passing in a 'callback'
>> (NotificationSenderCallback) that gives the caller of an
>> PushNotificationSender implementation a hint if we could submit the
>> messages to the push network, or not:
>>
>> /**
>>  * A simple Callback interface used when sending {@link org.jboss.aerogear.unifiedpush.message.UnifiedPushMessage} to
>>  * an actual push network.
>>  */
>> public interface NotificationSenderCallback {
>>
>>     /**
>>      * Simple indicator which will be called on a successful to deliver to the push network. However, the invocation of
>>      * this callback does <b>NOT</b> mean the messages have been sent out to the mobile devices. The invocation simply means
>>      * the {@link org.jboss.aerogear.unifiedpush.message.sender.PushNotificationSender} was able to send the messages to
>>      * the push network for its further processing
>>      */
>>     void onSuccess();
>>
>>     /**
>>      * Simple indicator which will be called on any type of error that occurred while sending the payload to the
>>      * underlying push network.
>>      */
>>     void onError();
>> }
>>
>> The reason why I'd like to do that is this give me better access to the
>> state of the request (for submitting messages). That is generally a nice
>> thing to be aware of the request-state. For our new "push history" overview
>> (see related threads), this comes handy, as I have all the needed
>> information in a more centralized place, instead of injecting a 'Metrics'
>> service into all the PushNotificationSender implementations:
>>
>> ...
>> // save APNs-delivery timestamp to metrics-database
>> // save number of APNs tokens to metrics-database
>> myAPNsSender.sendPushMessage(variant, collectionOfTokensForVariant, upsMessage, new NotificationSenderCallback() {
>>     @Override
>>     public void onSuccess() {
>>         // save success status for the given variant to metrics-database
>>     }
>>
>>     @Override
>>     public void onError() {
>>         // save failure status for the given variant to metrics-database
>>     }
>> });
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140523/d6388b25/attachment.html 

From matzew at apache.org  Fri May 23 10:00:37 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 23 May 2014 16:00:37 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <4D22FD44-A52B-4056-861D-7AC335363D60@redhat.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
	<537CD224.3050306@redhat.com>
	<5533FB53-6955-4466-9FB8-635EA930165A@redhat.com>
	<CAAg5f2RxqR1ye+ScqBSua2JGMrpoy7KrqDs3UaKA8yUS9YxNqQ@mail.gmail.com>
	<EE3AC5E1-D0C3-4041-8054-51B5252DB998@redhat.com>
	<CAAg5f2Rr45GwvqT4AKV1eCL4ihqEoy-ndK_K4m82bL_MBHnNjg@mail.gmail.com>
	<4D22FD44-A52B-4056-861D-7AC335363D60@redhat.com>
Message-ID: <CAAg5f2QsDNn3OfS6r5r-gzQVq4DjqJ01YwstbphM4CAgjuRhNQ@mail.gmail.com>

Yeah IT folks basically;

The (IT) owner of HR app, the (It) owner of marketing app etc

On Friday, May 23, 2014, Burr Sutter <bsutter at redhat.com> wrote:

>
> On May 21, 2014, at 4:24 PM, Matthias Wessendorf <matzew at apache.org<javascript:_e(%7B%7D,'cvml','matzew at apache.org');>>
> wrote:
>
>
>
>
> On Wed, May 21, 2014 at 9:55 PM, Burr Sutter <bsutter at redhat.com<javascript:_e(%7B%7D,'cvml','bsutter at redhat.com');>
> > wrote:
>
>>
>> On May 21, 2014, at 3:43 PM, Matthias Wessendorf <matzew at apache.org<javascript:_e(%7B%7D,'cvml','matzew at apache.org');>>
>> wrote:
>>
>> BTW. on the top box (first screen), I am querying the DB per user:
>> - "my" applications (the active is worthless)
>>
>> OK - so the "5" in the wireframe would be the "Total of My Apps"?
>>
>
> yes
>
>
>> - notifications delivered by "my" apps
>>
>> Yes, that makes sense
>>
>> - devices registered with "my" apps
>>
>>
>> And when did we add the concept of "my" apps, I thought there was only
>> "super-user" who sees all apps.
>>
>
> we had that already on the 'agenda' for the initial user-management - but
> we skipped our own impl. due to Keycloak adpotion;
>
> A recent thread:
> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007783.html
>
>
> In here I describe a 'super-user' and a 'PushAdmin':
> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007784.html
>
>
> Or do you think a 'shared' super-user is good enough? IMO it would be odd
> if HR Manager and Marketing Manager would be seeing each others apps;
>
> I was thinking that the HR Manager & Marketing Manager would not be "push
> admins" - they would not know how to upload the pubkey from Apple.
> I like the idea of having a PushAdmin per app - so that they only break
> their own apps.   But it would still likely be an IT person who pays the
> $99 and sets everything up.
>
>
>
>
> Feel free to chime in on that related thread
>
>
>
>
>
>
>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
> It would be odd if I see how many apps are on the entire server etc ;-)
>
>
>
> On Wed, May 21, 2014 at 8:41 PM, Burr Sutter <bsutter at redhat.com> wrote:
>
>
> On May 21, 2014, at 12:19 PM, Hylke Bons <hbons at redhat.com> wrote:
>
> > Hey,
> >
> > The "Status" column only show errors. If there are none it will say
> > something amongst the lines of "Everything is fine".
> I guess what threw me off was that the Status box links to the Activity
> page - at least based on how I read that orange arrow connecting the two.
>
>
> >
> > About the graphic: Sure, it's just the wireframe and may still change in
> > the visual design depending on what looks good.
> >
> > Thanks,
> >
> > Hylke
> >
> > On 19/05/2014 16:48, Matt Carrano wrote:
> >> Hey Hylke,
> >>
> >> This is looking good. I had a few minor comments/questions about the
> layout and labeling.  Take a look at the marked up wireframe (attached).
> >>
> >> -Matt
> >>
> >> ----- Original Message -----
> >> From: "Hylke Bons" <hbons at redhat.com>
> >> To: aerogear-dev at lists.jboss.org
> >> Cc: "Matt Carrano" <mcarrano at redhat.com>
> >> Sent: Monday, May 19, 2014 8:03:13 AM
> >> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
> >>
> >> Hello,
> >>
> >> Here are some updates based on the feedback from the meetings:
> >>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >> - Simplified dashboard stats
> >> - Apps notifications table
> >> - Defined entry points
> >>
> >> Let me know what you think. I hope that covers everything.
> >>
> >> Thanks,
> >>
> >> Hylke
> >>
> >>
> >>
> >> On 15/05/2014 16:19, Hylke Bons wrote:
> >>> Hey,
> >>>
> >>> Here's an initial version:
> >>>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >>>
> >>> I tried to incorporate most wishes expressed in the other thread.
> >>>
> >>> Most notable things:
> >>> - Landing page with an overview of stats, most active apps, and error
> >>> messages
> >>> - Activity table shows both registration and notification events
> >>> - Activity table is per variant, and not all activity on the server.
> >>> Unless there's a usecase to have every event for every app/variant in a
> >>> table I don't think we actually need it. The important thing is to get
> >>> to error messages easily.
> >>>
> >>> Things to do/think about:
> >>> - links/entry
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140523/7ace0989/attachment-0001.html 

From edewit at redhat.com  Fri May 23 10:45:04 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 23 May 2014 16:45:04 +0200
Subject: [aerogear-dev] [Mobile Push 1.0.0] Client SDKs for Android,
	Cordova and iOS
In-Reply-To: <CAKjsGbvvr=q0RMWwH+rkYyq_1Cne80ETZ=+4CrArt76QBU-A=g@mail.gmail.com>
References: <CAAg5f2Sb=qUTOi=z_6-RhPRPMnw_pF8eGouo6MSkAFDLRqEknw@mail.gmail.com>
	<CAD_dpu2upQHRD7pU8Xg5GxbTcro_btb9YHOt5H2rTJB-Yy+v-g@mail.gmail.com>
	<1400598565142-7865.post@n5.nabble.com>
	<E61DA3CC-412B-429B-A3BE-333F4A1C6D30@gmail.com>
	<CAKjsGbvvr=q0RMWwH+rkYyq_1Cne80ETZ=+4CrArt76QBU-A=g@mail.gmail.com>
Message-ID: <FAC542E0-B2E5-4B26-8557-A49940E0DEDC@redhat.com>

Created PR?s for the open issues on Cordova once merged all done :)

On 23 May,2014, at 15:18 , Daniel Passos <daniel at passos.me> wrote:

> All done in the android land
> 
> -- Passos
> 
> 
> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych <corinnekrych at gmail.com> wrote:
> Indeed we?re all good for iOS push registration lib.
> ++
> Corinne
> On 20 May 2014, at 17:09, Andrea Vibelli <avibelli at redhat.com> wrote:
> 
> > Hi,
> > I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5 an old
> > issue (http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
> > about the google-play-services version shipped inside the cordova plugin.
> >
> > Thanks
> > Andrea
> >
> >
> > Sebastien Blanc wrote
> >> Hi,
> >> For the Cordova Push Plugin there is one (trivial) item open that should
> >> be
> >> fixed before 1.0.  I created a jira to track it
> >> https://issues.jboss.org/browse/AGCORDOVA-4
> >>
> >>
> >>
> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
> >
> >> matzew@
> >
> >> &gt;wrote:
> >>
> >>> Hi,
> >>>
> >>> as said before (see [1]), this summer we will release the AeroGear Mobile
> >>> Push 1.0.0 to the community.
> >>>
> >>> I took a look at the related JIRAs (see [2]) and noticed that for the
> >>> mobile client SDKs there are no outstanding tickets. Yay!
> >>>
> >>> The github repos are also in an OK state :-) there are no feature related
> >>> open PRs; Well, besides a test improvement for the Cordova push plugin -
> >>> but that will be addressed soon;
> >>>
> >>> My question is: Are you guys aware of any features that we need to add to
> >>> Android, Cordova or iOS, related for push ?
> >>>
> >>> Once the Android and iOS bits are 'done', lets make sure we use those
> >>> latest versions on our Cordova plugin ;-)
> >>>
> >>> Thanks!
> >>> Matthias
> >>>
> >>> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
> >>> [2] https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
> >>>
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>>
> >
> >> aerogear-dev at .jboss
> >
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >
> >> aerogear-dev at .jboss
> >
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> >
> >
> > --
> > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.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/20140523/467eebf2/attachment.html 

From jbalunas at redhat.com  Fri May 23 11:09:37 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Fri, 23 May 2014 11:09:37 -0400
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <CAAg5f2QsDNn3OfS6r5r-gzQVq4DjqJ01YwstbphM4CAgjuRhNQ@mail.gmail.com>
References: <5374DB1B.9020405@redhat.com> <5379F301.7030607@redhat.com>
	<115052429.9408312.1400514484455.JavaMail.zimbra@redhat.com>
	<537CD224.3050306@redhat.com>
	<5533FB53-6955-4466-9FB8-635EA930165A@redhat.com>
	<CAAg5f2RxqR1ye+ScqBSua2JGMrpoy7KrqDs3UaKA8yUS9YxNqQ@mail.gmail.com>
	<EE3AC5E1-D0C3-4041-8054-51B5252DB998@redhat.com>
	<CAAg5f2Rr45GwvqT4AKV1eCL4ihqEoy-ndK_K4m82bL_MBHnNjg@mail.gmail.com>
	<4D22FD44-A52B-4056-861D-7AC335363D60@redhat.com>
	<CAAg5f2QsDNn3OfS6r5r-gzQVq4DjqJ01YwstbphM4CAgjuRhNQ@mail.gmail.com>
Message-ID: <6A55267B-FFB4-42A0-8105-A45DDE5E9F5D@redhat.com>


On May 23, 2014, at 10:00 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> Yeah IT folks basically;
> 
> The (IT) owner of HR app, the (It) owner of marketing app etc 

Right, we had talked about a more "marketing" "HR" type application interface would be a separate (or sibling) application - not shared directly with the admin console.  The use-cases imo are too different imo.

> 
> On Friday, May 23, 2014, Burr Sutter <bsutter at redhat.com> wrote:
> 
> On May 21, 2014, at 4:24 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
>> 
>> 
>> 
>> On Wed, May 21, 2014 at 9:55 PM, Burr Sutter <bsutter at redhat.com> wrote:
>> 
>> On May 21, 2014, at 3:43 PM, Matthias Wessendorf <matzew at apache.org> wrote:
>> 
>>> BTW. on the top box (first screen), I am querying the DB per user:
>>> - "my" applications (the active is worthless)
>> OK - so the "5" in the wireframe would be the "Total of My Apps"?
>> 
>> yes 
>> 
>> 
>>> - notifications delivered by "my" apps
>> Yes, that makes sense
>> 
>>> - devices registered with "my" apps
>> 
>> And when did we add the concept of "my" apps, I thought there was only "super-user" who sees all apps.
>> 
>> we had that already on the 'agenda' for the initial user-management - but we skipped our own impl. due to Keycloak adpotion;
>> 
>> A recent thread:
>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007783.html
>> 
>> 
>> In here I describe a 'super-user' and a 'PushAdmin':
>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007784.html
>> 
>> 
>> Or do you think a 'shared' super-user is good enough? IMO it would be odd if HR Manager and Marketing Manager would be seeing each others apps;
> I was thinking that the HR Manager & Marketing Manager would not be "push admins" - they would not know how to upload the pubkey from Apple.   
> I like the idea of having a PushAdmin per app - so that they only break their own apps.   But it would still likely be an IT person who pays the $99 and sets everything up.
> 
> 
> 
>> 
>> Feel free to chime in on that related thread 
>> 
>> 
>>  
>> 
>>> 
>>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>> 
>>> It would be odd if I see how many apps are on the entire server etc ;-) 
>>> 
>>> 
>>> 
>>> On Wed, May 21, 2014 at 8:41 PM, Burr Sutter <bsutter at redhat.com> wrote:
>>> 
>>> On May 21, 2014, at 12:19 PM, Hylke Bons <hbons at redhat.com> wrote:
>>> 
>>> > Hey,
>>> >
>>> > The "Status" column only show errors. If there are none it will say
>>> > something amongst the lines of "Everything is fine".
>>> I guess what threw me off was that the Status box links to the Activity page - at least based on how I read that orange arrow connecting the two.
>>> 
>>> 
>>> >
>>> > About the graphic: Sure, it's just the wireframe and may still change in
>>> > the visual design depending on what looks good.
>>> >
>>> > Thanks,
>>> >
>>> > Hylke
>>> >
>>> > On 19/05/2014 16:48, Matt Carrano wrote:
>>> >> Hey Hylke,
>>> >>
>>> >> This is looking good. I had a few minor comments/questions about the layout and labeling.  Take a look at the marked up wireframe (attached).
>>> >>
>>> >> -Matt
>>> >>
>>> >> ----- Original Message -----
>>> >> From: "Hylke Bons" <hbons at redhat.com>
>>> >> To: aerogear-dev at lists.jboss.org
>>> >> Cc: "Matt Carrano" <mcarrano at redhat.com>
>>> >> Sent: Monday, May 19, 2014 8:03:13 AM
>>> >> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
>>> >>
>>> >> Hello,
>>> >>
>>> >> Here are some updates based on the feedback from the meetings:
>>> >> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>> >> - Simplified dashboard stats
>>> >> - Apps notifications table
>>> >> - Defined entry points
>>> >>
>>> >> Let me know what you think. I hope that covers everything.
>>> >>
>>> >> Thanks,
>>> >>
>>> >> Hylke
>>> >>
>>> >>
>>> >>
>>> >> On 15/05/2014 16:19, Hylke Bons wrote:
>>> >>> Hey,
>>> >>>
>>> >>> Here's an initial version:
>>> >>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>> >>>
>>> >>> I tried to incorporate most wishes expressed in the other thread.
>>> >>>
>>> >>> Most notable things:
>>> >>> - Landing page with an overview of stats, most active apps, and error
>>> >>> messages
>>> >>> - Activity table shows both registration and notification events
>>> >>> - Activity table is per variant, and not all activity on the server.
>>> >>> Unless there's a usecase to have every event for every app/variant in a
>>> >>> table I don't think we actually need it. The important thing is to get
>>> >>> to error messages easily.
>>> >>>
>>> >>> Things to do/think about:
>>> >>> - links/entry
> 
> 
> -- 
> 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/20140523/7ac682de/attachment.html 

From bruno at abstractj.org  Fri May 23 11:33:22 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 23 May 2014 12:33:22 -0300
Subject: [aerogear-dev] Binaries from angular_keycloak branch
Message-ID: <20140523153322.GA25461@abstractj.org>

Good morning,

@hbons would like to see the latest changes at angular_branch and have
been facing with maven issues. So I uploaded it to my bucket on s3:

- http://golum.s3-website-eu-west-1.amazonaws.com/dist/ag-push.war

- http://golum.s3-website-eu-west-1.amazonaws.com/dist/auth-server.war

These binaries are based on it:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/166

I think for the future we can figure out a better way to deploy
snapshots on bintray or whatever storage.

--

abstractj

From matzew at apache.org  Fri May 23 12:08:32 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 23 May 2014 18:08:32 +0200
Subject: [aerogear-dev] Binaries from angular_keycloak branch
In-Reply-To: <20140523153322.GA25461@abstractj.org>
References: <20140523153322.GA25461@abstractj.org>
Message-ID: <CAAg5f2RpHc7ZGh71Rhw-m7k7a99FcqNpMopWyNzPydawhfiVKA@mail.gmail.com>

On Friday, May 23, 2014, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
>
> @hbons would like to see the latest changes at angular_branch and have
> been facing with maven issues. So I uploaded it to my bucket on s3:
>
> - http://golum.s3-website-eu-west-1.amazonaws.com/dist/ag-push.war
>
> - http://golum.s3-website-eu-west-1.amazonaws.com/dist/auth-server.war
>
> These binaries are based on it:
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/166
>
> I think for the future we can figure out a better way to deploy
> snapshots on bintray or whatever storage.


+1



>
> --
>
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org <javascript:;>
> 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/20140523/c2b2e6fd/attachment.html 

From edewit at redhat.com  Fri May 23 10:45:04 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 23 May 2014 16:45:04 +0200
Subject: [aerogear-dev] [Mobile Push 1.0.0] Client SDKs for Android,
	Cordova and iOS
In-Reply-To: <CAKjsGbvvr=q0RMWwH+rkYyq_1Cne80ETZ=+4CrArt76QBU-A=g@mail.gmail.com>
References: <CAAg5f2Sb=qUTOi=z_6-RhPRPMnw_pF8eGouo6MSkAFDLRqEknw@mail.gmail.com>
	<CAD_dpu2upQHRD7pU8Xg5GxbTcro_btb9YHOt5H2rTJB-Yy+v-g@mail.gmail.com>
	<1400598565142-7865.post@n5.nabble.com>
	<E61DA3CC-412B-429B-A3BE-333F4A1C6D30@gmail.com>
	<CAKjsGbvvr=q0RMWwH+rkYyq_1Cne80ETZ=+4CrArt76QBU-A=g@mail.gmail.com>
Message-ID: <FAC542E0-B2E5-4B26-8557-A49940E0DEDC@redhat.com>

Created PR?s for the open issues on Cordova once merged all done :)

On 23 May,2014, at 15:18 , Daniel Passos <daniel at passos.me> wrote:

> All done in the android land
> 
> -- Passos
> 
> 
> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych <corinnekrych at gmail.com> wrote:
> Indeed we?re all good for iOS push registration lib.
> ++
> Corinne
> On 20 May 2014, at 17:09, Andrea Vibelli <avibelli at redhat.com> wrote:
> 
> > Hi,
> > I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5 an old
> > issue (http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
> > about the google-play-services version shipped inside the cordova plugin.
> >
> > Thanks
> > Andrea
> >
> >
> > Sebastien Blanc wrote
> >> Hi,
> >> For the Cordova Push Plugin there is one (trivial) item open that should
> >> be
> >> fixed before 1.0.  I created a jira to track it
> >> https://issues.jboss.org/browse/AGCORDOVA-4
> >>
> >>
> >>
> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
> >
> >> matzew@
> >
> >> &gt;wrote:
> >>
> >>> Hi,
> >>>
> >>> as said before (see [1]), this summer we will release the AeroGear Mobile
> >>> Push 1.0.0 to the community.
> >>>
> >>> I took a look at the related JIRAs (see [2]) and noticed that for the
> >>> mobile client SDKs there are no outstanding tickets. Yay!
> >>>
> >>> The github repos are also in an OK state :-) there are no feature related
> >>> open PRs; Well, besides a test improvement for the Cordova push plugin -
> >>> but that will be addressed soon;
> >>>
> >>> My question is: Are you guys aware of any features that we need to add to
> >>> Android, Cordova or iOS, related for push ?
> >>>
> >>> Once the Android and iOS bits are 'done', lets make sure we use those
> >>> latest versions on our Cordova plugin ;-)
> >>>
> >>> Thanks!
> >>> Matthias
> >>>
> >>> [1] http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
> >>> [2] https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
> >>>
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>>
> >
> >> aerogear-dev at .jboss
> >
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >
> >> aerogear-dev at .jboss
> >
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> >
> >
> > --
> > View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.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/20140523/467eebf2/attachment-0002.html 

From bdawidow at redhat.com  Fri May 23 15:06:41 2014
From: bdawidow at redhat.com (=?UTF-8?B?Qm9sZXPFgmF3IERhd2lkb3dpY3o=?=)
Date: Fri, 23 May 2014 21:06:41 +0200
Subject: [aerogear-dev] checkstyle on aerogear-parent
In-Reply-To: <CAAg5f2RORntNLdhg21sabWA0gmwfRqnNzG7FucAr_2dr_hEexg@mail.gmail.com>
References: <CAAg5f2SNqdXNxh8aJivjdc3Usd0KFLeDcLAryu0H5x5k19mu-w@mail.gmail.com>	<20140520185603.GA67928@abstractj.org>	<CAFJm-3H7FMUys8Ay1u0NTnLm0jcvP24xZ=8naqneP0RvXz+J3w@mail.gmail.com>	<20140520192052.GC67928@abstractj.org>	<20140521144810.6b56e7fa@kapy-ntb-x220>	<20140521143802.GD30785@abstractj.org>	<20140522133142.32164c99@kapy-ntb-x220>	<CAAg5f2Rai43FK3mkacge6u-bN_KJtxozrinO7WPUA3KeVKVOjQ@mail.gmail.com>	<537F083D.4090507@redhat.com>
	<CAAg5f2RORntNLdhg21sabWA0gmwfRqnNzG7FucAr_2dr_hEexg@mail.gmail.com>
Message-ID: <537F9C41.10105@redhat.com>

On 05/23/2014 11:24 AM, Matthias Wessendorf wrote:

>      > -1
>      >
>      > I think we should work on proper templates for our IDEs instead
>
>
>     Major issue with IDE templates is that you cannot get both IDEA and
>     Eclipse to reformat code in whole project into exactly same outcome.
>     Unless you force people to use Eclipse formatter plugin in IDEA.
>
>     Also... checkstyle maven plugin is buggy... :)
>
>
> sounds like you love checkstyle too :)

Who doesn't ;)

-- 
Boles?aw Dawidowicz
JBoss Portal Platform Architect | GateIn Portal Project Lead

From bruno at abstractj.org  Fri May 23 16:35:23 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 23 May 2014 17:35:23 -0300
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
Message-ID: <20140523203523.GA38647@abstractj.org>

I think might not be hard to handle most of these scenarios on Keycloak,
but before move forward I would like to undestand why the admin is
removed here:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/ecbe017e65eaf95f7b8ff8c47de670dc77d985aa/auth-server/src/main/java/org/jboss/aerogear/unifiedpush/keycloak/UpsKeycloakApplication.java#L52

Any specific reason for it? I'm asking because I'm about to change it.
Are we planning to build our own admin interface?

On 2014-05-21, Matthias Wessendorf wrote:
> Just a thought... regarding those two roles 'PushAdmin' and 'Super-User',
> IMO the Super-user should be able to see all apps (and their variants,
> including registered devices).
>
>
>
>
> On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > Thank you Matthias, I will look at it and return back with more
> > questions if necessary.
> >
> > On 2014-05-21, Matthias Wessendorf wrote:
> > > Hello,
> > >
> > > yes - the handling is done by Keycloak itself; Last time we looked at
> > user
> > > management, we had the following in terms of roles:
> > >
> > > https://gist.github.com/sebastienblanc/6547605
> > >
> > > Not sure the names of these roles are great.... let's see
> > >
> > > Basically I think the role definition in the gist still addresses most of
> > > what we want to archive:
> > > * super-user: in charge of managing the UPS realm (including users); can
> > > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > > * PushAdmin: Someone that can manage applications and variants, but is
> > not
> > > able to add new users; he also sees only his applications/variants etc
> > > (that's the developer in sebis gist)
> > >
> > > The gist also contains a 'Viewer' role - At this point I am not sure we
> > do
> > > really need this. My impression is that if we have PushAdmins for our
> > 1.0.0
> > > community release that will be enough.
> > >
> > > -Matthias
> > >
> > >
> > >
> > >
> > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <bruno at abstractj.org
> > >wrote:
> > >
> > > > Good morning peeps,
> > > >
> > > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I would
> > > > like to understand what do you guys want say with this issue.
> > > >
> > > > Currently Keycloak already has its own user/roles managements. What do
> > > > you guys are looking for? Any specific requirements?
> > > >
> > > > --
> > > >
> > > > 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
> >
> >
> > --
> >
> > 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


--

abstractj

From matzew at apache.org  Fri May 23 17:42:43 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 23 May 2014 23:42:43 +0200
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <20140523203523.GA38647@abstractj.org>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
	<20140523203523.GA38647@abstractj.org>
Message-ID: <CAAg5f2RXjN-s5JdWdd+2wpiiJTEd84db8THMXzTmdyWjcK4J0A@mail.gmail.com>

On Fri, May 23, 2014 at 10:35 PM, Bruno Oliveira <bruno at abstractj.org>wrote:

> I think might not be hard to handle most of these scenarios on Keycloak,
> but before move forward I would like to undestand why the admin is
> removed here:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/ecbe017e65eaf95f7b8ff8c47de670dc77d985aa/auth-server/src/main/java/org/jboss/aerogear/unifiedpush/keycloak/UpsKeycloakApplication.java#L52
>
> Any specific reason for it? I'm asking because I'm about to change it.
>

I did follow the template we got from Bill:
https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/auth-server/src/main/java/org/aerogear/ups/security/UpsSecurityApplication.java#L35

I think in that example there was no 'super-user' that is in charge of the
realm management



> Are we planning to build our own admin interface?
>

nope; We will use theirs, but we may be applying our own theme to make it
look like UPS



>
> On 2014-05-21, Matthias Wessendorf wrote:
> > Just a thought... regarding those two roles 'PushAdmin' and 'Super-User',
> > IMO the Super-user should be able to see all apps (and their variants,
> > including registered devices).
> >
> >
> >
> >
> > On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > Thank you Matthias, I will look at it and return back with more
> > > questions if necessary.
> > >
> > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > Hello,
> > > >
> > > > yes - the handling is done by Keycloak itself; Last time we looked at
> > > user
> > > > management, we had the following in terms of roles:
> > > >
> > > > https://gist.github.com/sebastienblanc/6547605
> > > >
> > > > Not sure the names of these roles are great.... let's see
> > > >
> > > > Basically I think the role definition in the gist still addresses
> most of
> > > > what we want to archive:
> > > > * super-user: in charge of managing the UPS realm (including users);
> can
> > > > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > > > * PushAdmin: Someone that can manage applications and variants, but
> is
> > > not
> > > > able to add new users; he also sees only his applications/variants
> etc
> > > > (that's the developer in sebis gist)
> > > >
> > > > The gist also contains a 'Viewer' role - At this point I am not sure
> we
> > > do
> > > > really need this. My impression is that if we have PushAdmins for our
> > > 1.0.0
> > > > community release that will be enough.
> > > >
> > > > -Matthias
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <
> bruno at abstractj.org
> > > >wrote:
> > > >
> > > > > Good morning peeps,
> > > > >
> > > > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I
> would
> > > > > like to understand what do you guys want say with this issue.
> > > > >
> > > > > Currently Keycloak already has its own user/roles managements.
> What do
> > > > > you guys are looking for? Any specific requirements?
> > > > >
> > > > > --
> > > > >
> > > > > 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
> > >
> > >
> > > --
> > >
> > > 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
>
>
> --
>
> 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/20140523/4c7cba62/attachment-0001.html 

From bruno at abstractj.org  Sat May 24 13:00:20 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Sat, 24 May 2014 14:00:20 -0300
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <CAAg5f2RXjN-s5JdWdd+2wpiiJTEd84db8THMXzTmdyWjcK4J0A@mail.gmail.com>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
	<20140523203523.GA38647@abstractj.org>
	<CAAg5f2RXjN-s5JdWdd+2wpiiJTEd84db8THMXzTmdyWjcK4J0A@mail.gmail.com>
Message-ID: <20140524170020.GA47416@abstractj.org>

On 2014-05-23, Matthias Wessendorf wrote:
> On Fri, May 23, 2014 at 10:35 PM, Bruno Oliveira <bruno at abstractj.org>wrote:
>
> > I think might not be hard to handle most of these scenarios on Keycloak,
> > but before move forward I would like to undestand why the admin is
> > removed here:
> >
> > https://github.com/aerogear/aerogear-unifiedpush-server/blob/ecbe017e65eaf95f7b8ff8c47de670dc77d985aa/auth-server/src/main/java/org/jboss/aerogear/unifiedpush/keycloak/UpsKeycloakApplication.java#L52
> >
> > Any specific reason for it? I'm asking because I'm about to change it.
> >
>
> I did follow the template we got from Bill:
> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/auth-server/src/main/java/org/aerogear/ups/security/UpsSecurityApplication.java#L35
>
> I think in that example there was no 'super-user' that is in charge of the
> realm management

Following with our plan, I removed that piece of code and attached to my
angular PR.

>
>
>
> > Are we planning to build our own admin interface?
> >
>
> nope; We will use theirs, but we may be applying our own theme to make it
> look like UPS
>
>
>
> >
> > On 2014-05-21, Matthias Wessendorf wrote:
> > > Just a thought... regarding those two roles 'PushAdmin' and 'Super-User',
> > > IMO the Super-user should be able to see all apps (and their variants,
> > > including registered devices).
> > >
> > >
> > >
> > >
> > > On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org>
> > wrote:
> > >
> > > > Thank you Matthias, I will look at it and return back with more
> > > > questions if necessary.
> > > >
> > > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > > Hello,
> > > > >
> > > > > yes - the handling is done by Keycloak itself; Last time we looked at
> > > > user
> > > > > management, we had the following in terms of roles:
> > > > >
> > > > > https://gist.github.com/sebastienblanc/6547605
> > > > >
> > > > > Not sure the names of these roles are great.... let's see
> > > > >
> > > > > Basically I think the role definition in the gist still addresses
> > most of
> > > > > what we want to archive:
> > > > > * super-user: in charge of managing the UPS realm (including users);
> > can
> > > > > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > > > > * PushAdmin: Someone that can manage applications and variants, but
> > is
> > > > not
> > > > > able to add new users; he also sees only his applications/variants
> > etc
> > > > > (that's the developer in sebis gist)
> > > > >
> > > > > The gist also contains a 'Viewer' role - At this point I am not sure
> > we
> > > > do
> > > > > really need this. My impression is that if we have PushAdmins for our
> > > > 1.0.0
> > > > > community release that will be enough.
> > > > >
> > > > > -Matthias
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <
> > bruno at abstractj.org
> > > > >wrote:
> > > > >
> > > > > > Good morning peeps,
> > > > > >
> > > > > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I
> > would
> > > > > > like to understand what do you guys want say with this issue.
> > > > > >
> > > > > > Currently Keycloak already has its own user/roles managements.
> > What do
> > > > > > you guys are looking for? Any specific requirements?
> > > > > >
> > > > > > --
> > > > > >
> > > > > > 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
> > > >
> > > >
> > > > --
> > > >
> > > > 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
> >
> >
> > --
> >
> > 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


--

abstractj

From john.manko at gmail.com  Sat May 24 13:15:47 2014
From: john.manko at gmail.com (jmanko)
Date: Sat, 24 May 2014 10:15:47 -0700 (PDT)
Subject: [aerogear-dev] Understanding AeroGear development
Message-ID: <1400951747551-7925.post@n5.nabble.com>

I'm trying to get a hold on how to start development with AeroGear.  Is there
any tutorial on the actual HTML design (code, not visual editor).  Are all
applications meant to be single-paged with multi-view DIVs?  That's a lot of
unrelated content on the same page, and makes it messy when having to design
larger scaled apps.  

Anything that walks through what's taking place in the kitchen-sink sample
HTML page would be great, and what the standard conventions are.  Thank you
in advance.



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Understanding-AeroGear-development-tp7925.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From john.manko at gmail.com  Sat May 24 15:02:29 2014
From: john.manko at gmail.com (jmanko)
Date: Sat, 24 May 2014 12:02:29 -0700 (PDT)
Subject: [aerogear-dev] Understanding AeroGear development
In-Reply-To: <1400951747551-7925.post@n5.nabble.com>
References: <1400951747551-7925.post@n5.nabble.com>
Message-ID: <1400958149950-7926.post@n5.nabble.com>

I also noticed that when creating an HTML5 app within JBDS, none of the
AeroGear deps were added to the pom.  Am I missing something?



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Understanding-AeroGear-development-tp7925p7926.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Sun May 25 07:40:45 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Sun, 25 May 2014 13:40:45 +0200
Subject: [aerogear-dev] [Mobile Push 1.0.0] Client SDKs for Android,
 Cordova and iOS
In-Reply-To: <FAC542E0-B2E5-4B26-8557-A49940E0DEDC@redhat.com>
References: <CAAg5f2Sb=qUTOi=z_6-RhPRPMnw_pF8eGouo6MSkAFDLRqEknw@mail.gmail.com>
	<CAD_dpu2upQHRD7pU8Xg5GxbTcro_btb9YHOt5H2rTJB-Yy+v-g@mail.gmail.com>
	<1400598565142-7865.post@n5.nabble.com>
	<E61DA3CC-412B-429B-A3BE-333F4A1C6D30@gmail.com>
	<CAKjsGbvvr=q0RMWwH+rkYyq_1Cne80ETZ=+4CrArt76QBU-A=g@mail.gmail.com>
	<FAC542E0-B2E5-4B26-8557-A49940E0DEDC@redhat.com>
Message-ID: <CAAg5f2Q8cZ37QQN+uNrVaUX-2jpBRUsSdUHbxxh7M4g-biJJog@mail.gmail.com>

Awesome! Thanks for commenting, guys!

@Cordova: Will test (and merge ;-)) on Monday


On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Created PR?s for the open issues on Cordova once merged all done :)
>
> On 23 May,2014, at 15:18 , Daniel Passos <daniel at passos.me> wrote:
>
> All done in the android land
>
> -- Passos
>
>
> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych <corinnekrych at gmail.com>wrote:
>
>> Indeed we?re all good for iOS push registration lib.
>> ++
>> Corinne
>> On 20 May 2014, at 17:09, Andrea Vibelli <avibelli at redhat.com> wrote:
>>
>> > Hi,
>> > I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5 an
>> old
>> > issue (
>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
>> > about the google-play-services version shipped inside the cordova
>> plugin.
>> >
>> > Thanks
>> > Andrea
>> >
>> >
>> > Sebastien Blanc wrote
>> >> Hi,
>> >> For the Cordova Push Plugin there is one (trivial) item open that
>> should
>> >> be
>> >> fixed before 1.0.  I created a jira to track it
>> >> https://issues.jboss.org/browse/AGCORDOVA-4
>> >>
>> >>
>> >>
>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
>> >
>> >> matzew@
>> >
>> >> &gt;wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> as said before (see [1]), this summer we will release the AeroGear
>> Mobile
>> >>> Push 1.0.0 to the community.
>> >>>
>> >>> I took a look at the related JIRAs (see [2]) and noticed that for the
>> >>> mobile client SDKs there are no outstanding tickets. Yay!
>> >>>
>> >>> The github repos are also in an OK state :-) there are no feature
>> related
>> >>> open PRs; Well, besides a test improvement for the Cordova push
>> plugin -
>> >>> but that will be addressed soon;
>> >>>
>> >>> My question is: Are you guys aware of any features that we need to
>> add to
>> >>> Android, Cordova or iOS, related for push ?
>> >>>
>> >>> Once the Android and iOS bits are 'done', lets make sure we use those
>> >>> latest versions on our Cordova plugin ;-)
>> >>>
>> >>> Thanks!
>> >>> Matthias
>> >>>
>> >>> [1]
>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>> >>> [2]
>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>> >>>
>> >>>
>> >>> --
>> >>> Matthias Wessendorf
>> >>>
>> >>> blog: http://matthiaswessendorf.wordpress.com/
>> >>> sessions: http://www.slideshare.net/mwessendorf
>> >>> twitter: http://twitter.com/mwessendorf
>> >>>
>> >>> _______________________________________________
>> >>> aerogear-dev mailing list
>> >>>
>> >
>> >> aerogear-dev at .jboss
>> >
>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>
>> >>
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >
>> >> aerogear-dev at .jboss
>> >
>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >
>> >
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140525/37626da1/attachment.html 

From matzew at apache.org  Sun May 25 07:42:18 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Sun, 25 May 2014 13:42:18 +0200
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <20140524170020.GA47416@abstractj.org>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
	<20140523203523.GA38647@abstractj.org>
	<CAAg5f2RXjN-s5JdWdd+2wpiiJTEd84db8THMXzTmdyWjcK4J0A@mail.gmail.com>
	<20140524170020.GA47416@abstractj.org>
Message-ID: <CAAg5f2TUyeSh4Zi+_5X6UeS0TmKUJta7YTm-LVEq3zJUDsN7jw@mail.gmail.com>

Awesome! thanks!

I just merged the initial KC-Angular integration PR;

Now since the bits are on master, I feel more 'safe' to ask QE to test the
new components (e.g. KC and Angular based UI)

-Matthias


On Sat, May 24, 2014 at 7:00 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> On 2014-05-23, Matthias Wessendorf wrote:
> > On Fri, May 23, 2014 at 10:35 PM, Bruno Oliveira <bruno at abstractj.org
> >wrote:
> >
> > > I think might not be hard to handle most of these scenarios on
> Keycloak,
> > > but before move forward I would like to undestand why the admin is
> > > removed here:
> > >
> > >
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/ecbe017e65eaf95f7b8ff8c47de670dc77d985aa/auth-server/src/main/java/org/jboss/aerogear/unifiedpush/keycloak/UpsKeycloakApplication.java#L52
> > >
> > > Any specific reason for it? I'm asking because I'm about to change it.
> > >
> >
> > I did follow the template we got from Bill:
> >
> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/auth-server/src/main/java/org/aerogear/ups/security/UpsSecurityApplication.java#L35
> >
> > I think in that example there was no 'super-user' that is in charge of
> the
> > realm management
>
> Following with our plan, I removed that piece of code and attached to my
> angular PR.
>
> >
> >
> >
> > > Are we planning to build our own admin interface?
> > >
> >
> > nope; We will use theirs, but we may be applying our own theme to make it
> > look like UPS
> >
> >
> >
> > >
> > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > Just a thought... regarding those two roles 'PushAdmin' and
> 'Super-User',
> > > > IMO the Super-user should be able to see all apps (and their
> variants,
> > > > including registered devices).
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org
> >
> > > wrote:
> > > >
> > > > > Thank you Matthias, I will look at it and return back with more
> > > > > questions if necessary.
> > > > >
> > > > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > > > Hello,
> > > > > >
> > > > > > yes - the handling is done by Keycloak itself; Last time we
> looked at
> > > > > user
> > > > > > management, we had the following in terms of roles:
> > > > > >
> > > > > > https://gist.github.com/sebastienblanc/6547605
> > > > > >
> > > > > > Not sure the names of these roles are great.... let's see
> > > > > >
> > > > > > Basically I think the role definition in the gist still addresses
> > > most of
> > > > > > what we want to archive:
> > > > > > * super-user: in charge of managing the UPS realm (including
> users);
> > > can
> > > > > > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > > > > > * PushAdmin: Someone that can manage applications and variants,
> but
> > > is
> > > > > not
> > > > > > able to add new users; he also sees only his
> applications/variants
> > > etc
> > > > > > (that's the developer in sebis gist)
> > > > > >
> > > > > > The gist also contains a 'Viewer' role - At this point I am not
> sure
> > > we
> > > > > do
> > > > > > really need this. My impression is that if we have PushAdmins
> for our
> > > > > 1.0.0
> > > > > > community release that will be enough.
> > > > > >
> > > > > > -Matthias
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <
> > > bruno at abstractj.org
> > > > > >wrote:
> > > > > >
> > > > > > > Good morning peeps,
> > > > > > >
> > > > > > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I
> > > would
> > > > > > > like to understand what do you guys want say with this issue.
> > > > > > >
> > > > > > > Currently Keycloak already has its own user/roles managements.
> > > What do
> > > > > > > you guys are looking for? Any specific requirements?
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > 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
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > 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
> > >
> > >
> > > --
> > >
> > > 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
>
>
> --
>
> 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/20140525/dc7c7cd3/attachment-0001.html 

From tolisemm at gmail.com  Mon May 26 02:40:20 2014
From: tolisemm at gmail.com (tolis emmanouilidis)
Date: Mon, 26 May 2014 09:40:20 +0300
Subject: [aerogear-dev] aerogear-js CouchDB data-manager adapter
Message-ID: <CAN5SbcaXr8hv=36Vb-yMGYgAE+O1W8F3_+d9_oOufFVwuQGCyw@mail.gmail.com>

Hi,

I have started working on creating a CouchDB data-manager adapter which
uses the CouchDB REST API. The open-create database, read and save
operations are implemented [1] and tested both with encryption settings and
without encryption settings. If you'd like to give it a try, make sure that
you have enabled CORS on CouchDB side.

The remaining functions that needs to be implemented are remove and filter.
In addition, in order to keep consistent the data-manager API, we should
provide a way to remove all the documents in a CouchDB database-store.

a) Removing all documents in a CouchDB database

I'm thinking of fetching all the docs, using _all_docs endpoint which
returns _id and _rev (revision), mark them as _deleted and use the bulk
insert/update API to delete them. Not sure if this is a proper solution
since there might be a huge number of documents.

Another option would be to delete the database-store. This seems to be the
worst solution since the documents history will be permanently lost.

Any ideas?

b) Filtering

AFAIK, in order to perform filtering in a CouchDB database, a design
document and an appropriate view has to be created. My thought is that the
AGJS adapter should not create the view, instead we should assume that the
user has created the appopriate views and provide a setting in AGJS where
the view endpoint URl can be set.

Any ideas about filtering and the proper way to be implemented?

Thanks,
Tolis

[1]:
https://github.com/tolis-e/aerogear-js/commit/0cf952c36ea0f31aec2a6732d89eb469fd4a3d09
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140526/5d22ce8a/attachment.html 

From daniel.bevenius at gmail.com  Mon May 26 02:51:30 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 26 May 2014 08:51:30 +0200
Subject: [aerogear-dev] Team meeting
Message-ID: <CAFJm-3G4+KAUMG0tVbu9kwPx5XrEud7c0TYaJbTo7Tq5CCLLXw@mail.gmail.com>

Agenda:
http://oksoclap.com/p/aerogear-team-mgt-20140526
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140526/70839b1d/attachment.html 

From keith at kdmooreconsulting.com  Mon May 26 03:22:32 2014
From: keith at kdmooreconsulting.com (keithdmoore94)
Date: Mon, 26 May 2014 00:22:32 -0700 (PDT)
Subject: [aerogear-dev] cordova angular quick start demo
In-Reply-To: <74B6DC47-E376-4C55-85EC-C002E47447BA@redhat.com>
References: <2F5B8A91-F681-4B8A-9D59-EFEFF8CDEEC4@redhat.com>
	<3B072A76-B780-496B-97DB-B7ED0C217B91@redhat.com>
	<1D82326B-4F90-4469-B5C4-617E9E2F097F@redhat.com>
	<409B6E7D-BD13-487E-ABE3-EC40D66DAB40@redhat.com>
	<1398479312724-7582.post@n5.nabble.com>
	<CAAg5f2QZ47MKdFUjBrgSrq2bV0EoFtdO2fyL57Q+Y=FC5fMaTA@mail.gmail.com>
	<6FB1647F-1F18-4B42-A168-D807BB276D0C@gmail.com>
	<1398550160919-7588.post@n5.nabble.com>
	<74B6DC47-E376-4C55-85EC-C002E47447BA@redhat.com>
Message-ID: <2C70E0F4-25BE-4EF8-A196-BD08A41C7427@kdmooreconsulting.com>

Sure.  I will take a look.

On May 22, 2014, at 1:39 AM, Erik Jan de Wit [via aerogear-dev] <ml-node+s1069024n7902h89 at n5.nabble.com> wrote:

> Hi,
> 
> I?ve started working on a AngularJs version of the quick start demo and I?ve based it upon ionic. Having components and support for gestures out of the box really makes sense to me. So Keith if you are still interested in helping, I have a branch where I?ve started https://github.com/edewit/aerogear-push-quickstarts/tree/angular
> 
> Cheers,
> 	Erik Jan
> 
> On 27 Apr,2014, at 0:09 , keithdmoore94 <[hidden email]> wrote:
> 
>> Where can I find the "mobile contacts quickstart demo" you speak of ?  On a
>> side note, does anyone know how I can get the "mobile" import folder that
>> has the "Import Cordova Project" option in Eclipse Kepler?   I noticed some
>> screenshots of it in the  aerogear-push-helloworld-cordova
>> <https://github.com/aerogear/aerogear-push-helloworld/tree/master/cordova>   
>> readme page.  
>> 
>> 
>> 
>> --
>> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-cordova-angular-quick-start-demo-tp7568p7588.html
>> Sent from the aerogear-dev mailing list archive at Nabble.com.
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________ 
> 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-angular-quick-start-demo-tp7568p7902.html
> To unsubscribe from [aerogear-dev] cordova angular quick start demo, click here.
> NAML





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-cordova-angular-quick-start-demo-tp7568p7931.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/20140526/0d07da44/attachment.html 

From matzew at apache.org  Mon May 26 03:48:32 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 26 May 2014 09:48:32 +0200
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile Push
 1.0.0] Client SDKs for Android, Cordova and iOS)
Message-ID: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>

Hello,

the latest Android libs are now on master - should we do another release,
this week ?


-Matthias



On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> Awesome! Thanks for commenting, guys!
>
> @Cordova: Will test (and merge ;-)) on Monday
>
>
> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit <edewit at redhat.com>wrote:
>
>> Created PR?s for the open issues on Cordova once merged all done :)
>>
>> On 23 May,2014, at 15:18 , Daniel Passos <daniel at passos.me> wrote:
>>
>> All done in the android land
>>
>> -- Passos
>>
>>
>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych <corinnekrych at gmail.com>wrote:
>>
>>> Indeed we?re all good for iOS push registration lib.
>>> ++
>>> Corinne
>>> On 20 May 2014, at 17:09, Andrea Vibelli <avibelli at redhat.com> wrote:
>>>
>>> > Hi,
>>> > I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5an old
>>> > issue (
>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
>>> > about the google-play-services version shipped inside the cordova
>>> plugin.
>>> >
>>> > Thanks
>>> > Andrea
>>> >
>>> >
>>> > Sebastien Blanc wrote
>>> >> Hi,
>>> >> For the Cordova Push Plugin there is one (trivial) item open that
>>> should
>>> >> be
>>> >> fixed before 1.0.  I created a jira to track it
>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
>>> >>
>>> >>
>>> >>
>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
>>> >
>>> >> matzew@
>>> >
>>> >> &gt;wrote:
>>> >>
>>> >>> Hi,
>>> >>>
>>> >>> as said before (see [1]), this summer we will release the AeroGear
>>> Mobile
>>> >>> Push 1.0.0 to the community.
>>> >>>
>>> >>> I took a look at the related JIRAs (see [2]) and noticed that for the
>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
>>> >>>
>>> >>> The github repos are also in an OK state :-) there are no feature
>>> related
>>> >>> open PRs; Well, besides a test improvement for the Cordova push
>>> plugin -
>>> >>> but that will be addressed soon;
>>> >>>
>>> >>> My question is: Are you guys aware of any features that we need to
>>> add to
>>> >>> Android, Cordova or iOS, related for push ?
>>> >>>
>>> >>> Once the Android and iOS bits are 'done', lets make sure we use those
>>> >>> latest versions on our Cordova plugin ;-)
>>> >>>
>>> >>> Thanks!
>>> >>> Matthias
>>> >>>
>>> >>> [1]
>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>>> >>> [2]
>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Matthias Wessendorf
>>> >>>
>>> >>> blog: http://matthiaswessendorf.wordpress.com/
>>> >>> sessions: http://www.slideshare.net/mwessendorf
>>> >>> twitter: http://twitter.com/mwessendorf
>>> >>>
>>> >>> _______________________________________________
>>> >>> aerogear-dev mailing list
>>> >>>
>>> >
>>> >> aerogear-dev at .jboss
>>> >
>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>
>>> >>
>>> >> _______________________________________________
>>> >> aerogear-dev mailing list
>>> >
>>> >> aerogear-dev at .jboss
>>> >
>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > View this message in context:
>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.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
>>
>
>
>
> --
> 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/20140526/f2f1ebda/attachment-0001.html 

From matzew at apache.org  Mon May 26 04:59:10 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 26 May 2014 10:59:10 +0200
Subject: [aerogear-dev] GCM limit with 1000 registrationIDs
In-Reply-To: <CAAg5f2TFDZ=hCfLRqLrS9z1pF_pV=19aUeFAAv7njN4jtgaxog@mail.gmail.com>
References: <CAAg5f2SP0aqrtsyCAvDvRG1NzJXS2iaOO86BbML0PxiYVTVHOA@mail.gmail.com>
	<1400672454662-7879.post@n5.nabble.com>
	<CAAg5f2S5dqCS99CEmV4vEj=76m7rzZ5K-6wLT4PkOxyaHPyACA@mail.gmail.com>
	<1400679220199-7887.post@n5.nabble.com>
	<CAAg5f2TFDZ=hCfLRqLrS9z1pF_pV=19aUeFAAv7njN4jtgaxog@mail.gmail.com>
Message-ID: <CAAg5f2Twm9a1mNOyiObHJLpLDgg4MUxTrDAEf3HbNp_TS3fVZg@mail.gmail.com>

Hello Antoine,

I noticed the same issue, I will be looking into this, so that we can have
a better 'batch' import.

Thanks for reporting!
Matthias


On Wed, May 21, 2014 at 4:33 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> hey Antoine,
>
> thanks for explaining - I will take a look at this:
> https://issues.jboss.org/browse/AGPUSH-661
>
> I will think about making the endpoint completely async (there is no real
> benefit in returning a JSON of the device metadata anyways + do some
> overhaul on the actual database)
>
>
> On Wed, May 21, 2014 at 3:33 PM, A577127 <antoine.matyja at worldline.com>wrote:
>
>> Uh wrong translation  I mean register tokens. We wrote a java sender that
>> registers lots of token (we wanted to register 1M tokens) with the REST
>> api
>> http://aerogear.org/docs/specs/aerogear-push-rest/DeviceRegistration/
>>
>> But it was very slow (~1/s), looks like the database slows the thing by
>> making big requests (huge joins ?).
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-GCM-limit-with-1000-registrationIDs-tp7858p7887.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/20140526/c0569d79/attachment.html 

From cvasilak at gmail.com  Mon May 26 05:29:56 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 26 May 2014 12:29:56 +0300
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
Message-ID: <A7CCCFDE-F89A-4E8F-9C06-BD7BC1577259@gmail.com>

Hi all,

during the development of the iOS contacts client [1] , came across the following issues on the web interface. (Note: I am using edewit [2] branch that contains the Push functionality).

a) Login with ?duke:duke" (role.MAINTAINER)  and try to edit(PUT) an existing contact  you get back a 403-Forbidden message.
b) Login with ?admin:admin (role.ADMIN)  and try to delete(DELETE) an existing contact you get back a 403-Forbidden message.

Interestingly enough, on the iOS client using the same credentials in the above scenarios, they work correctly..  so possible(?) there are some issues on the web interface.

c) Logout on the web interface gives back a ?Forbidden? message.

Tested on both wildfly-8.1.0.CR1 / CR2 and JBoss- EAP-6.2

Let me know if these are currently worked on or you want me to create JIRA?s.

Thanks,
Christos


[1] https://github.com/aerogear/aerogear-push-quickstarts/pull/3
[2] https://github.com/edewit/jboss-wfk-quickstarts/tree/push/contacts-mobile-picketlink-secured

From daniel.bevenius at gmail.com  Mon May 26 05:57:55 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 26 May 2014 11:57:55 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <A7CCCFDE-F89A-4E8F-9C06-BD7BC1577259@gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<A7CCCFDE-F89A-4E8F-9C06-BD7BC1577259@gmail.com>
Message-ID: <CAFJm-3FOidFs5D7ogThjO7mORtb5q55r8BRCcn9jNbjoiHFy6w@mail.gmail.com>

Hey Christos

I've seen a few of these and perhaps all. I'm currently working on
extracting the webapp into a separate project/modules named
contacts-mobile-webapp. The webapp in that module was extracted from
contacts-mobile-picketlink-secured and I've made some modifications.

For the logout issue I had to add the following:
https://github.com/danbev/jboss-wfk-quickstarts/commit/d097ddf5c7385cf7ff8e7b003305ddb743d7fb2b#diff-e084cf285ab2733dcd0478559aa4aa40R164
This was to make the CORSFilter happy or it would consider the request
invalid.

I've also seen the 403 Forbidden messages but I'm no longer able to
reproduce them. I'll take another look at this though.

[1]
https://github.com/danbev/jboss-wfk-quickstarts/tree/push-proxy-quickstart


On 26 May 2014 11:29, Christos Vasilakis <cvasilak at gmail.com> wrote:

> Hi all,
>
> during the development of the iOS contacts client [1] , came across the
> following issues on the web interface. (Note: I am using edewit [2] branch
> that contains the Push functionality).
>
> a) Login with ?duke:duke" (role.MAINTAINER)  and try to edit(PUT) an
> existing contact  you get back a 403-Forbidden message.
> b) Login with ?admin:admin (role.ADMIN)  and try to delete(DELETE) an
> existing contact you get back a 403-Forbidden message.
>
> Interestingly enough, on the iOS client using the same credentials in the
> above scenarios, they work correctly..  so possible(?) there are some
> issues on the web interface.
>
> c) Logout on the web interface gives back a ?Forbidden? message.
>
> Tested on both wildfly-8.1.0.CR1 / CR2 and JBoss- EAP-6.2
>
> Let me know if these are currently worked on or you want me to create
> JIRA?s.
>
> Thanks,
> Christos
>
>
> [1] https://github.com/aerogear/aerogear-push-quickstarts/pull/3
> [2]
> https://github.com/edewit/jboss-wfk-quickstarts/tree/push/contacts-mobile-picketlink-secured
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140526/4a733927/attachment.html 

From matzew at apache.org  Mon May 26 06:02:30 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 26 May 2014 12:02:30 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <CAFJm-3FOidFs5D7ogThjO7mORtb5q55r8BRCcn9jNbjoiHFy6w@mail.gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<A7CCCFDE-F89A-4E8F-9C06-BD7BC1577259@gmail.com>
	<CAFJm-3FOidFs5D7ogThjO7mORtb5q55r8BRCcn9jNbjoiHFy6w@mail.gmail.com>
Message-ID: <CAAg5f2Q536Zi1A=OvhFEmdcN_8jzd3uALJ4sbfUom89d3p5Pzw@mail.gmail.com>

On Mon, May 26, 2014 at 11:57 AM, Daniel Bevenius <daniel.bevenius at gmail.com
> wrote:

> Hey Christos
>
> I've seen a few of these and perhaps all. I'm currently working on
> extracting the webapp into a separate project/modules named
> contacts-mobile-webapp. The webapp in that module was extracted from
> contacts-mobile-picketlink-secured and I've made some modifications.
>

+1 awesome!


>
> For the logout issue I had to add the following:
>
> https://github.com/danbev/jboss-wfk-quickstarts/commit/d097ddf5c7385cf7ff8e7b003305ddb743d7fb2b#diff-e084cf285ab2733dcd0478559aa4aa40R164
> This was to make the CORSFilter happy or it would consider the request
> invalid.
>
> I've also seen the 403 Forbidden messages but I'm no longer able to
> reproduce them. I'll take another look at this though.
>
> [1]
> https://github.com/danbev/jboss-wfk-quickstarts/tree/push-proxy-quickstart
>
>
> On 26 May 2014 11:29, Christos Vasilakis <cvasilak at gmail.com> wrote:
>
>> Hi all,
>>
>> during the development of the iOS contacts client [1] , came across the
>> following issues on the web interface. (Note: I am using edewit [2] branch
>> that contains the Push functionality).
>>
>> a) Login with ?duke:duke" (role.MAINTAINER)  and try to edit(PUT) an
>> existing contact  you get back a 403-Forbidden message.
>> b) Login with ?admin:admin (role.ADMIN)  and try to delete(DELETE) an
>> existing contact you get back a 403-Forbidden message.
>>
>> Interestingly enough, on the iOS client using the same credentials in the
>> above scenarios, they work correctly..  so possible(?) there are some
>> issues on the web interface.
>>
>> c) Logout on the web interface gives back a ?Forbidden? message.
>>
>> Tested on both wildfly-8.1.0.CR1 / CR2 and JBoss- EAP-6.2
>>
>> Let me know if these are currently worked on or you want me to create
>> JIRA?s.
>>
>> Thanks,
>> Christos
>>
>>
>> [1] https://github.com/aerogear/aerogear-push-quickstarts/pull/3
>> [2]
>> https://github.com/edewit/jboss-wfk-quickstarts/tree/push/contacts-mobile-picketlink-secured
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140526/e6b4e7d3/attachment.html 

From vivek.pandey at pinelabs.com  Mon May 26 06:27:15 2014
From: vivek.pandey at pinelabs.com (Vivek Pandey)
Date: Mon, 26 May 2014 15:57:15 +0530
Subject: [aerogear-dev] UPS Production worthiness
In-Reply-To: <CAAg5f2QZYVo0FCESLrpF3oyBmYTUS132jtGkWKWWVeUmR=UjRg@mail.gmail.com>
References: <002b01cf7424$528dc0a0$f7a941e0$@pinelabs.com>	<E4CB92A8-4F9E-490B-BB8D-21B402FE56A9@redhat.com>	<005d01cf74ed$3d977140$b8c653c0$@pinelabs.com>
	<CAAg5f2QZYVo0FCESLrpF3oyBmYTUS132jtGkWKWWVeUmR=UjRg@mail.gmail.com>
Message-ID: <003c01cf78cd$1095df40$31c19dc0$@pinelabs.com>

Hi Matthias,

 

It is good to know that activity in java-apns is picking up and also that you are looking at pushy.

 

I did a few tests which added installations to UPS with a concurrency of 4-8 threads. I was using Postgres 9.3 and UPS 0.10.3 war

 

I noticed that response slowed down considerably after some time with high CPU usage and continued to get worse. After doing some profiling, I found that bulk of CPU cycles are being taken by org.postgresql.core.VisibleBufferedInputStream.readMore. The entire thread stack is attached. Also postgres continuously flagged 

 

select installati0_.variantID as variant10_0_0_, installati0_.id as id1_3_0_, installati0_.id as id1_3_1_, installati0_.alias as alias2_3_1_, installati0_.deviceToken as deviceTo3_3_1_, installati0_.deviceType as deviceTy4_3_1_, installati0_.enabled as enabled5_3_1_, installati0_.operatingSystem as operatin6_3_1_, installati0_.osVersion as osVersio7_3_1_, installati0_.platform as platform8_3_1_, installati0_.simplePushEndpoint as simplePu9_3_1_ from InstallationImpl installati0_ where installati0_.variantID=$1

 

as the slow query. I am pretty sure that eager collection AbstractVariant.installations is the root cause of the problem. 

 

Please let me know if you need any more information.

 

Thanks

Vivek

 

From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf
Sent: Wednesday, May 21, 2014 5:55 PM
To: vivek.pandey at pinelabs.com; AeroGear Developer Mailing List
Subject: Re: [aerogear-dev] UPS Production worthiness

 

Hello Vivek!

 

On Wed, May 21, 2014 at 2:07 PM, Vivek Pandey <vivek.pandey at pinelabs.com> wrote:

Hi Jay,

 

Thanks for your reply.

 

While we have not faced any issues in using UPS in our limited testing, I often see info stacktraces in ups logs

 

2014-05-16 10:19:20,032 INFO  [com.notnoop.apns.internal.ApnsConnectionImpl] (Thread-118) Exception while waiting for error code: java.net.SocketException: Socket closed

        at java.net.SocketInputStream.socketRead0(Native Method) [rt.jar:1.7.0_51]

        at java.net.SocketInputStream.read(SocketInputStream.java:152) [rt.jar:1.7.0_51]

        at java.net.SocketInputStream.read(SocketInputStream.java:122) [rt.jar:1.7.0_51]

       ?????

        at com.notnoop.apns.internal.ApnsConnectionImpl$1MonitoringThread.run(ApnsConnectionImpl.java:114) [apns-0.2.3.jar:]

 

 

These stacktraces coupled with low dev activity of noop/java-apns project are disconcerting to me.

 

the stack-trace is no harm - it's only happening w/ doing a monitoring of the thread (that's what we currently do, when setting up ApnsService - I thought about explicitly disable that)

 

The activity of the underlying java-apns is very low, yes! However @froh42 is getting back:

https://github.com/notnoop/java-apns/commits/master

 

There will be a new release in the near future; @froh42 asked me if I could help with pushing the bits to maven central

 

 

That said, I recently started looking at pushy:

https://github.com/relayrides/pushy

 

I also sent a PR that would allow us to feed pushy w/ our certificate from the database:

https://github.com/relayrides/pushy/pull/87

 

Hope that helps

-Matthias

 

 

I am currently using UPS 0.10.2 war.

 

Thanks,

Vivek

From: Jay Balunas [mailto:jbalunas at redhat.com] 
Sent: Tuesday, May 20, 2014 11:36 PM
To: vivek.pandey at pinelabs.com; AeroGear Developer Mailing List
Cc: Jay Balunas
Subject: Re: [aerogear-dev] UPS Production worthiness

 

Hi Vivek,

 

It's awesome to hear that you have integrated the UPS into your backend systems and some of your mobile apps!

 

We have a lot of confidence around the UPS, its functionality, and performance.  Our team has been working hard on improvements and stability including our QE team.  Also, as you may have seen we're planning a 1.0 release of the UPS this summer.

 

However at this time we don't have specific references or success stories outside of what you can see in the community mailing lists - other users using it ;-)  We're also about to kick off some performance and scale testing in the next couple of months.

 

Have you run into any issues that drove these questions about production worthiness?  If so please let us know and we'll certainly take a look.

 

Hope this helps!

 

Thanks,

Jay Balunas 

 

On May 20, 2014, at 8:09 AM, Vivek Pandey <vivek.pandey at pinelabs.com> wrote:

 

Hello Aerogear dev team,

 

We integrated UPS into our backend server which is serving various mobile apps. While the development and testing phase went well, my manager is questioning me about production worthiness about Aerogear. It would be great help if you could point me to references/success stories where UPS is being used in production environments and scaling well in medium to high loads.

 

Thanks,

Vivek

 

 

 


  _____  


This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.


  _____  



_______________________________________________
aerogear-dev mailing list
 <mailto:aerogear-dev at lists.jboss.org> aerogear-dev at lists.jboss.org
 <https://lists.jboss.org/mailman/listinfo/aerogear-dev> https://lists.jboss.org/mailman/listinfo/aerogear-dev

 

 

  _____  

This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.

  _____  

 


_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev





 

-- 
Matthias Wessendorf 

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf 


This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140526/81629f57/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: threadstack.txt
Url: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140526/81629f57/attachment-0001.txt 

From edewit at redhat.com  Mon May 26 06:59:07 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 26 May 2014 12:59:07 +0200
Subject: [aerogear-dev] UPS Production worthiness
In-Reply-To: <003c01cf78cd$1095df40$31c19dc0$@pinelabs.com>
References: <002b01cf7424$528dc0a0$f7a941e0$@pinelabs.com>	<E4CB92A8-4F9E-490B-BB8D-21B402FE56A9@redhat.com>	<005d01cf74ed$3d977140$b8c653c0$@pinelabs.com>
	<CAAg5f2QZYVo0FCESLrpF3oyBmYTUS132jtGkWKWWVeUmR=UjRg@mail.gmail.com>
	<003c01cf78cd$1095df40$31c19dc0$@pinelabs.com>
Message-ID: <17C1B903-C13B-482F-93FA-1B9B55AEF707@redhat.com>

Hi Vivek,

We?ve fixed that https://github.com/aerogear/aerogear-unifiedpush-server/commit/1357c9e834286a9227a90e9ab618226aa54bbbf3 the collection is now lazy. But I?m sure other query optimisations can be made.

Cheers,
	Erik Jan

On 26 May,2014, at 12:27 , Vivek Pandey <vivek.pandey at pinelabs.com> wrote:

> Hi Matthias,
>  
> It is good to know that activity in java-apns is picking up and also that you are looking at pushy.
>  
> I did a few tests which added installations to UPS with a concurrency of 4-8 threads. I was using Postgres 9.3 and UPS 0.10.3 war
>  
> I noticed that response slowed down considerably after some time with high CPU usage and continued to get worse. After doing some profiling, I found that bulk of CPU cycles are being taken by org.postgresql.core.VisibleBufferedInputStream.readMore. The entire thread stack is attached. Also postgres continuously flagged
>  
> select installati0_.variantID as variant10_0_0_, installati0_.id as id1_3_0_, installati0_.id as id1_3_1_, installati0_.alias as alias2_3_1_, installati0_.deviceToken as deviceTo3_3_1_, installati0_.deviceType as deviceTy4_3_1_, installati0_.enabled as enabled5_3_1_, installati0_.operatingSystem as operatin6_3_1_, installati0_.osVersion as osVersio7_3_1_, installati0_.platform as platform8_3_1_, installati0_.simplePushEndpoint as simplePu9_3_1_ from InstallationImpl installati0_ where installati0_.variantID=$1
>  
> as the slow query. I am pretty sure that eager collection AbstractVariant.installations is the root cause of the problem.
>  
> Please let me know if you need any more information.
>  
> Thanks
> Vivek
>  
> From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf
> Sent: Wednesday, May 21, 2014 5:55 PM
> To: vivek.pandey at pinelabs.com; AeroGear Developer Mailing List
> Subject: Re: [aerogear-dev] UPS Production worthiness
>  
> Hello Vivek!
>  
> 
> On Wed, May 21, 2014 at 2:07 PM, Vivek Pandey <vivek.pandey at pinelabs.com> wrote:
> Hi Jay,
>  
> Thanks for your reply.
>  
> While we have not faced any issues in using UPS in our limited testing, I often see info stacktraces in ups logs
>  
> 2014-05-16 10:19:20,032 INFO  [com.notnoop.apns.internal.ApnsConnectionImpl] (Thread-118) Exception while waiting for error code: java.net.SocketException: Socket closed
>         at java.net.SocketInputStream.socketRead0(Native Method) [rt.jar:1.7.0_51]
>         at java.net.SocketInputStream.read(SocketInputStream.java:152) [rt.jar:1.7.0_51]
>         at java.net.SocketInputStream.read(SocketInputStream.java:122) [rt.jar:1.7.0_51]
>        ?????
>         at com.notnoop.apns.internal.ApnsConnectionImpl$1MonitoringThread.run(ApnsConnectionImpl.java:114) [apns-0.2.3.jar:]
>  
>  
> These stacktraces coupled with low dev activity of noop/java-apns project are disconcerting to me.
>  
> the stack-trace is no harm - it's only happening w/ doing a monitoring of the thread (that's what we currently do, when setting up ApnsService - I thought about explicitly disable that)
>  
> The activity of the underlying java-apns is very low, yes! However @froh42 is getting back:
> https://github.com/notnoop/java-apns/commits/master
>  
> There will be a new release in the near future; @froh42 asked me if I could help with pushing the bits to maven central
>  
>  
> That said, I recently started looking at pushy:
> https://github.com/relayrides/pushy
>  
> I also sent a PR that would allow us to feed pushy w/ our certificate from the database:
> https://github.com/relayrides/pushy/pull/87
>  
> Hope that helps
> -Matthias
>  
>  
> I am currently using UPS 0.10.2 war.
>  
> Thanks,
> Vivek
> From: Jay Balunas [mailto:jbalunas at redhat.com] 
> Sent: Tuesday, May 20, 2014 11:36 PM
> To: vivek.pandey at pinelabs.com; AeroGear Developer Mailing List
> Cc: Jay Balunas
> Subject: Re: [aerogear-dev] UPS Production worthiness
>  
> Hi Vivek,
>  
> It's awesome to hear that you have integrated the UPS into your backend systems and some of your mobile apps!
>  
> We have a lot of confidence around the UPS, its functionality, and performance.  Our team has been working hard on improvements and stability including our QE team.  Also, as you may have seen we're planning a 1.0 release of the UPS this summer.
>  
> However at this time we don't have specific references or success stories outside of what you can see in the community mailing lists - other users using it ;-)  We're also about to kick off some performance and scale testing in the next couple of months.
>  
> Have you run into any issues that drove these questions about production worthiness?  If so please let us know and we'll certainly take a look.
>  
> Hope this helps!
>  
> Thanks,
> Jay Balunas 
>  
> On May 20, 2014, at 8:09 AM, Vivek Pandey <vivek.pandey at pinelabs.com> wrote:
>  
> 
> Hello Aerogear dev team,
>  
> We integrated UPS into our backend server which is serving various mobile apps. While the development and testing phase went well, my manager is questioning me about production worthiness about Aerogear. It would be great help if you could point me to references/success stories where UPS is being used in production environments and scaling well in medium to high loads.
>  
> Thanks,
> Vivek
>  
>  
>  
> This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>  
>  
> This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.
>  
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
>  
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.
> 
> <threadstack.txt>_______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140526/769ed7a2/attachment-0001.html 

From matzew at apache.org  Mon May 26 07:23:35 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 26 May 2014 13:23:35 +0200
Subject: [aerogear-dev] UPS Production worthiness
In-Reply-To: <17C1B903-C13B-482F-93FA-1B9B55AEF707@redhat.com>
References: <002b01cf7424$528dc0a0$f7a941e0$@pinelabs.com>
	<E4CB92A8-4F9E-490B-BB8D-21B402FE56A9@redhat.com>
	<005d01cf74ed$3d977140$b8c653c0$@pinelabs.com>
	<CAAg5f2QZYVo0FCESLrpF3oyBmYTUS132jtGkWKWWVeUmR=UjRg@mail.gmail.com>
	<003c01cf78cd$1095df40$31c19dc0$@pinelabs.com>
	<17C1B903-C13B-482F-93FA-1B9B55AEF707@redhat.com>
Message-ID: <CAAg5f2TuC73jcYBj7BUHA5zT6L68oqdjTH_yQZVm8XxsoyPULg@mail.gmail.com>

On Mon, May 26, 2014 at 12:59 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi Vivek,
>
> We?ve fixed that
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/1357c9e834286a9227a90e9ab618226aa54bbbf3 the
> collection is now lazy. But I?m sure other query optimisations can be made.
>

+1

btw. Vivek, I added your mail to an existing ticket:
https://issues.jboss.org/browse/AGPUSH-661

-Matthias


>
> Cheers,
> Erik Jan
>
> On 26 May,2014, at 12:27 , Vivek Pandey <vivek.pandey at pinelabs.com> wrote:
>
> Hi Matthias,
>
> It is good to know that activity in java-apns is picking up and also that
> you are looking at pushy.
>
> I did a few tests which added installations to UPS with a concurrency of
> 4-8 threads. I was using Postgres 9.3 and UPS 0.10.3 war
>
> I noticed that response slowed down considerably after some time with high
> CPU usage and continued to get worse. After doing some profiling, I found
> that bulk of CPU cycles are being taken by
> org.postgresql.core.VisibleBufferedInputStream.readMore. The entire thread
> stack is attached. Also postgres continuously flagged
>
> select installati0_.variantID as variant10_0_0_, installati0_.id as
> id1_3_0_, installati0_.id as id1_3_1_, installati0_.alias as alias2_3_1_,
> installati0_.deviceToken as deviceTo3_3_1_, installati0_.deviceType as
> deviceTy4_3_1_, installati0_.enabled as enabled5_3_1_,
> installati0_.operatingSystem as operatin6_3_1_, installati0_.osVersion as
> osVersio7_3_1_, installati0_.platform as platform8_3_1_,
> installati0_.simplePushEndpoint as simplePu9_3_1_ from InstallationImpl
> installati0_ where installati0_.variantID=$1
>
> as the slow query. I am pretty sure that eager collection
> AbstractVariant.installations is the root cause of the problem.
>
> Please let me know if you need any more information.
>
> Thanks
> Vivek
>
> *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com<mwessendorf at gmail.com>
> ] *On Behalf Of *Matthias Wessendorf
> *Sent:* Wednesday, May 21, 2014 5:55 PM
> *To:* vivek.pandey at pinelabs.com; AeroGear Developer Mailing List
> *Subject:* Re: [aerogear-dev] UPS Production worthiness
>
> Hello Vivek!
>
>
> On Wed, May 21, 2014 at 2:07 PM, Vivek Pandey <vivek.pandey at pinelabs.com>
> wrote:
> Hi Jay,
>
> Thanks for your reply.
>
> While we have not faced any issues in using UPS in our limited testing, I
> often see info stacktraces in ups logs
>
> 2014-05-16 10:19:20,032 INFO
> [com.notnoop.apns.internal.ApnsConnectionImpl] (Thread-118) Exception while
> waiting for error code: java.net.SocketException: Socket closed
>         at java.net.SocketInputStream.socketRead0(Native Method)
> [rt.jar:1.7.0_51]
>         at java.net.SocketInputStream.read(SocketInputStream.java:152)
> [rt.jar:1.7.0_51]
>         at java.net.SocketInputStream.read(SocketInputStream.java:122)
> [rt.jar:1.7.0_51]
>        ?????
>         at
> com.notnoop.apns.internal.ApnsConnectionImpl$1MonitoringThread.run(ApnsConnectionImpl.java:114)
> [apns-0.2.3.jar:]
>
>
> These stacktraces coupled with low dev activity of noop/java-apns project
> are disconcerting to me.
>
> the stack-trace is no harm - it's only happening w/ doing a monitoring of
> the thread (that's what we currently do, when setting up ApnsService - I
> thought about explicitly disable that)
>
> The activity of the underlying java-apns is very low, yes! However @froh42
> is getting back:
> https://github.com/notnoop/java-apns/commits/master
>
> There will be a new release in the near future; @froh42 asked me if I
> could help with pushing the bits to maven central
>
>
> That said, I recently started looking at pushy:
> https://github.com/relayrides/pushy
>
> I also sent a PR that would allow us to feed pushy w/ our certificate from
> the database:
> https://github.com/relayrides/pushy/pull/87
>
> Hope that helps
> -Matthias
>
>
>
> I am currently using UPS 0.10.2 war.
>
> Thanks,
> Vivek
> *From:* Jay Balunas [mailto:jbalunas at redhat.com]
> *Sent:* Tuesday, May 20, 2014 11:36 PM
> *To:* vivek.pandey at pinelabs.com; AeroGear Developer Mailing List
> *Cc:* Jay Balunas
> *Subject:* Re: [aerogear-dev] UPS Production worthiness
>
> Hi Vivek,
>
> It's awesome to hear that you have integrated the UPS into your backend
> systems and some of your mobile apps!
>
> We have a lot of confidence around the UPS, its functionality, and
> performance.  Our team has been working hard on improvements and stability
> including our QE team.  Also, as you may have seen we're planning a 1.0
> release of the UPS this summer.
>
> However at this time we don't have specific references or success stories
> outside of what you can see in the community mailing lists - other users
> using it ;-)  We're also about to kick off some performance and scale
> testing in the next couple of months.
>
> Have you run into any issues that drove these questions about production
> worthiness?  If so please let us know and we'll certainly take a look.
>
> Hope this helps!
>
> Thanks,
> Jay Balunas
>
> On May 20, 2014, at 8:09 AM, Vivek Pandey <vivek.pandey at pinelabs.com>
> wrote:
>
>
> Hello Aerogear dev team,
>
> We integrated UPS into our backend server which is serving various mobile
> apps. While the development and testing phase went well, my manager is
> questioning me about production worthiness about Aerogear. It would be
> great help if you could point me to references/success stories where UPS is
> being used in production environments and scaling well in medium to high
> loads.
>
> Thanks,
> Vivek
>
>
>
> ------------------------------
> This message may contain privileged and confidential information and is
> solely for the use of intended recipient. The views expressed in this email
> are those of the sender and not of Pine Labs. The recipient should check
> this email and attachments for the presence of viruses / malwares etc. Pine
> Labs accepts no liability for any damage caused by any virus transmitted by
> this email. Pine Labs may monitor and record all emails.
> ------------------------------
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> ------------------------------
> This message may contain privileged and confidential information and is
> solely for the use of intended recipient. The views expressed in this email
> are those of the sender and not of Pine Labs. The recipient should check
> this email and attachments for the presence of viruses / malwares etc. Pine
> Labs accepts no liability for any damage caused by any virus transmitted by
> this email. Pine Labs may monitor and record all emails.
> ------------------------------
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> ------------------------------
> This message may contain privileged and confidential information and is
> solely for the use of intended recipient. The views expressed in this email
> are those of the sender and not of Pine Labs. The recipient should check
> this email and attachments for the presence of viruses / malwares etc. Pine
> Labs accepts no liability for any damage caused by any virus transmitted by
> this email. Pine Labs may monitor and record all emails.
> ------------------------------
>
> <threadstack.txt>_______________________________________________
>
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140526/5123fe63/attachment-0001.html 

From lukas.fryc at gmail.com  Mon May 26 07:55:06 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 26 May 2014 13:55:06 +0200
Subject: [aerogear-dev] aerogear-js CouchDB data-manager adapter
In-Reply-To: <CAN5SbcaXr8hv=36Vb-yMGYgAE+O1W8F3_+d9_oOufFVwuQGCyw@mail.gmail.com>
References: <CAN5SbcaXr8hv=36Vb-yMGYgAE+O1W8F3_+d9_oOufFVwuQGCyw@mail.gmail.com>
Message-ID: <CAEroY34ms4KWzV8uKh9AK_iuBxtO6xgQ8xFjBf3=DP0+Mij2Ag@mail.gmail.com>

Hey Tolis,

great job with the adapter!


a) remove()

since there are obviously many ways how to achieve "delete all docs",
I believe it's up to user to choose the way he wants the docs deleted
i.e. it could be up to Data Manager configuration whether data will be
deleted with or without a history loss (aka wipe out). wdyt?


b) Filtering

It would be pretty overwhelming for a user to create a view per particular
use of the filter() method, since it can have pretty arbitrary form.
We are also able to create temporary views, but that requires you to
perform one additional POST request and it is costly.

Are we able to come up with a common view definition that would cover all
the filtering capabilities - i.e. generic aerogear-filter view?
Something that user would define once and all cases would be covered.
I have not practically played with CouchDB, but according the docs it could
be somehow possible.



Btw as I think about it, there might be lack of function for limiting what
data to transfer.
i.e. Filtering API allows you to select just particular docs, but it does
not help you to avoid what will be transferred.

All the Data Managers so far are local ones, CouchDB is a first one that
actually transfers data from the wire.


Cheers,

~ Lukas


On Mon, May 26, 2014 at 8:40 AM, tolis emmanouilidis <tolisemm at gmail.com>wrote:

> Hi,
>
> I have started working on creating a CouchDB data-manager adapter which
> uses the CouchDB REST API. The open-create database, read and save
> operations are implemented [1] and tested both with encryption settings and
> without encryption settings. If you'd like to give it a try, make sure that
> you have enabled CORS on CouchDB side.
>
> The remaining functions that needs to be implemented are remove and
> filter. In addition, in order to keep consistent the data-manager API, we
> should provide a way to remove all the documents in a CouchDB
> database-store.
>
> a) Removing all documents in a CouchDB database
>
> I'm thinking of fetching all the docs, using _all_docs endpoint which
> returns _id and _rev (revision), mark them as _deleted and use the bulk
> insert/update API to delete them. Not sure if this is a proper solution
> since there might be a huge number of documents.
>
> Another option would be to delete the database-store. This seems to be the
> worst solution since the documents history will be permanently lost.
>
> Any ideas?
>
>  b) Filtering
>
> AFAIK, in order to perform filtering in a CouchDB database, a design
> document and an appropriate view has to be created. My thought is that the
> AGJS adapter should not create the view, instead we should assume that the
> user has created the appopriate views and provide a setting in AGJS where
> the view endpoint URl can be set.
>
> Any ideas about filtering and the proper way to be implemented?
>
> Thanks,
> Tolis
>
> [1]:
> https://github.com/tolis-e/aerogear-js/commit/0cf952c36ea0f31aec2a6732d89eb469fd4a3d09
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140526/ae9cdece/attachment.html 

From bruno at abstractj.org  Mon May 26 08:10:57 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 26 May 2014 09:10:57 -0300
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
Message-ID: <20140526121057.GA64465@abstractj.org>


Good morning peeps, after the latest change[1] correct me if I'm wrong. But
I think KC and UPS will do pretty much what we need.

We have a push admin and the super user on KC side enabled. Let me know
if that is what you need and I will take a look at viewer role.


[1] -
https://github.com/aerogear/aerogear-unifiedpush-server/commit/3e118b1c758493942ef2a00e1541302a03e5519c


On 2014-05-21, Matthias Wessendorf wrote:
> Just a thought... regarding those two roles 'PushAdmin' and 'Super-User',
> IMO the Super-user should be able to see all apps (and their variants,
> including registered devices).
>
>
>
>
> On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > Thank you Matthias, I will look at it and return back with more
> > questions if necessary.
> >
> > On 2014-05-21, Matthias Wessendorf wrote:
> > > Hello,
> > >
> > > yes - the handling is done by Keycloak itself; Last time we looked at
> > user
> > > management, we had the following in terms of roles:
> > >
> > > https://gist.github.com/sebastienblanc/6547605
> > >
> > > Not sure the names of these roles are great.... let's see
> > >
> > > Basically I think the role definition in the gist still addresses most of
> > > what we want to archive:
> > > * super-user: in charge of managing the UPS realm (including users); can
> > > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > > * PushAdmin: Someone that can manage applications and variants, but is
> > not
> > > able to add new users; he also sees only his applications/variants etc
> > > (that's the developer in sebis gist)
> > >
> > > The gist also contains a 'Viewer' role - At this point I am not sure we
> > do
> > > really need this. My impression is that if we have PushAdmins for our
> > 1.0.0
> > > community release that will be enough.
> > >
> > > -Matthias
> > >
> > >
> > >
> > >
> > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <bruno at abstractj.org
> > >wrote:
> > >
> > > > Good morning peeps,
> > > >
> > > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I would
> > > > like to understand what do you guys want say with this issue.
> > > >
> > > > Currently Keycloak already has its own user/roles managements. What do
> > > > you guys are looking for? Any specific requirements?
> > > >
> > > > --
> > > >
> > > > 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
> >
> >
> > --
> >
> > 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


--

abstractj

From daniel.bevenius at gmail.com  Mon May 26 08:14:19 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 26 May 2014 14:14:19 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <CAAg5f2Q536Zi1A=OvhFEmdcN_8jzd3uALJ4sbfUom89d3p5Pzw@mail.gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<A7CCCFDE-F89A-4E8F-9C06-BD7BC1577259@gmail.com>
	<CAFJm-3FOidFs5D7ogThjO7mORtb5q55r8BRCcn9jNbjoiHFy6w@mail.gmail.com>
	<CAAg5f2Q536Zi1A=OvhFEmdcN_8jzd3uALJ4sbfUom89d3p5Pzw@mail.gmail.com>
Message-ID: <CAFJm-3ES4VQL8=rBT22jKuo+6T-18AB4Oh=XP4p172o4fSLR1g@mail.gmail.com>

I'm seeing an issue with deleting of a contact...
If I log in as user 'admin' and delete a contact, the next screen the
deleted user is still in the list of contacts. If I then go to the "List
View" the user is gone.



On 26 May 2014 12:02, Matthias Wessendorf <matzew at apache.org> wrote:

>
>
>
> On Mon, May 26, 2014 at 11:57 AM, Daniel Bevenius <
> daniel.bevenius at gmail.com> wrote:
>
>> Hey Christos
>>
>> I've seen a few of these and perhaps all. I'm currently working on
>> extracting the webapp into a separate project/modules named
>> contacts-mobile-webapp. The webapp in that module was extracted from
>> contacts-mobile-picketlink-secured and I've made some modifications.
>>
>
> +1 awesome!
>
>
>>
>> For the logout issue I had to add the following:
>>
>> https://github.com/danbev/jboss-wfk-quickstarts/commit/d097ddf5c7385cf7ff8e7b003305ddb743d7fb2b#diff-e084cf285ab2733dcd0478559aa4aa40R164
>> This was to make the CORSFilter happy or it would consider the request
>> invalid.
>>
>> I've also seen the 403 Forbidden messages but I'm no longer able to
>> reproduce them. I'll take another look at this though.
>>
>> [1]
>> https://github.com/danbev/jboss-wfk-quickstarts/tree/push-proxy-quickstart
>>
>>
>> On 26 May 2014 11:29, Christos Vasilakis <cvasilak at gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> during the development of the iOS contacts client [1] , came across the
>>> following issues on the web interface. (Note: I am using edewit [2] branch
>>> that contains the Push functionality).
>>>
>>> a) Login with ?duke:duke" (role.MAINTAINER)  and try to edit(PUT) an
>>> existing contact  you get back a 403-Forbidden message.
>>> b) Login with ?admin:admin (role.ADMIN)  and try to delete(DELETE) an
>>> existing contact you get back a 403-Forbidden message.
>>>
>>> Interestingly enough, on the iOS client using the same credentials in
>>> the above scenarios, they work correctly..  so possible(?) there are some
>>> issues on the web interface.
>>>
>>> c) Logout on the web interface gives back a ?Forbidden? message.
>>>
>>> Tested on both wildfly-8.1.0.CR1 / CR2 and JBoss- EAP-6.2
>>>
>>> Let me know if these are currently worked on or you want me to create
>>> JIRA?s.
>>>
>>> Thanks,
>>> Christos
>>>
>>>
>>> [1] https://github.com/aerogear/aerogear-push-quickstarts/pull/3
>>> [2]
>>> https://github.com/edewit/jboss-wfk-quickstarts/tree/push/contacts-mobile-picketlink-secured
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140526/0aae8451/attachment.html 

From bruno at abstractj.org  Mon May 26 08:23:22 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 26 May 2014 09:23:22 -0300
Subject: [aerogear-dev] Understanding AeroGear development
In-Reply-To: <1400958149950-7926.post@n5.nabble.com>
References: <1400951747551-7925.post@n5.nabble.com>
	<1400958149950-7926.post@n5.nabble.com>
Message-ID: <20140526122321.GB64465@abstractj.org>

Good morning my friend, which kind of deps are you talking about? Do you
have the steps to reproduce your issue?

On 2014-05-24, jmanko wrote:
> I also noticed that when creating an HTML5 app within JBDS, none of the
> AeroGear deps were added to the pom.  Am I missing something?
>
>
>
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Understanding-AeroGear-development-tp7925p7926.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

--

abstractj

From matzew at apache.org  Mon May 26 09:11:44 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 26 May 2014 15:11:44 +0200
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <20140526121057.GA64465@abstractj.org>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
	<20140526121057.GA64465@abstractj.org>
Message-ID: <CAAg5f2R6ByA=vMpicqXYEO32vemFFXzqf99CQR0qcj+Qigha1g@mail.gmail.com>

On Mon, May 26, 2014 at 2:10 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

>
> Good morning peeps, after the latest change[1] correct me if I'm wrong. But
> I think KC and UPS will do pretty much what we need.
>
> We have a push admin and the super user on KC side enabled. Let me know
> if that is what you need and I will take a look at viewer role.
>

One thing that I noticed: when I login as 'admin', I don't see the
applications created by 'user'
I think with that change, the 'admin' is the overall Keycloak-Admin.


I had a chat w/ Stian in the past, for the above mentioned
"super-user" (which is leveraging the Keycloak realm) Stian and I were
thinking of a "Super User", that simply has not all permissions. For
instance, it would have:
* AdminRoles.VIEW_USERS
* AdminRoles.MANAGE_USERS

But it would not have the "AdminRoles.ADMIN" role. As we don't need to have
that guy/super-user being able to create realms or other applications, just
the "user access" items.

I guess that's why we did see the 'remove()' before

-Matthias




>
>
> [1] -
>
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/3e118b1c758493942ef2a00e1541302a03e5519c
>
>
> On 2014-05-21, Matthias Wessendorf wrote:
> > Just a thought... regarding those two roles 'PushAdmin' and 'Super-User',
> > IMO the Super-user should be able to see all apps (and their variants,
> > including registered devices).
> >
> >
> >
> >
> > On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > Thank you Matthias, I will look at it and return back with more
> > > questions if necessary.
> > >
> > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > Hello,
> > > >
> > > > yes - the handling is done by Keycloak itself; Last time we looked at
> > > user
> > > > management, we had the following in terms of roles:
> > > >
> > > > https://gist.github.com/sebastienblanc/6547605
> > > >
> > > > Not sure the names of these roles are great.... let's see
> > > >
> > > > Basically I think the role definition in the gist still addresses
> most of
> > > > what we want to archive:
> > > > * super-user: in charge of managing the UPS realm (including users);
> can
> > > > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > > > * PushAdmin: Someone that can manage applications and variants, but
> is
> > > not
> > > > able to add new users; he also sees only his applications/variants
> etc
> > > > (that's the developer in sebis gist)
> > > >
> > > > The gist also contains a 'Viewer' role - At this point I am not sure
> we
> > > do
> > > > really need this. My impression is that if we have PushAdmins for our
> > > 1.0.0
> > > > community release that will be enough.
> > > >
> > > > -Matthias
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <
> bruno at abstractj.org
> > > >wrote:
> > > >
> > > > > Good morning peeps,
> > > > >
> > > > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I
> would
> > > > > like to understand what do you guys want say with this issue.
> > > > >
> > > > > Currently Keycloak already has its own user/roles managements.
> What do
> > > > > you guys are looking for? Any specific requirements?
> > > > >
> > > > > --
> > > > >
> > > > > 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
> > >
> > >
> > > --
> > >
> > > 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
>
>
> --
>
> 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/20140526/4dada999/attachment.html 

From daniel.bevenius at gmail.com  Mon May 26 10:00:14 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 26 May 2014 16:00:14 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <CAFJm-3ES4VQL8=rBT22jKuo+6T-18AB4Oh=XP4p172o4fSLR1g@mail.gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<A7CCCFDE-F89A-4E8F-9C06-BD7BC1577259@gmail.com>
	<CAFJm-3FOidFs5D7ogThjO7mORtb5q55r8BRCcn9jNbjoiHFy6w@mail.gmail.com>
	<CAAg5f2Q536Zi1A=OvhFEmdcN_8jzd3uALJ4sbfUom89d3p5Pzw@mail.gmail.com>
	<CAFJm-3ES4VQL8=rBT22jKuo+6T-18AB4Oh=XP4p172o4fSLR1g@mail.gmail.com>
Message-ID: <CAFJm-3H9-t1E--T+_ctZ7+YVpw2XVwByoHFm-hFSBZWTxMiQag@mail.gmail.com>

I think I've got the delete sorted with this commit:
https://github.com/danbev/jboss-wfk-quickstarts/commit/0dfdb8d27ca8ba984e1e92582fb30e6a2e681b00




On 26 May 2014 14:14, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> I'm seeing an issue with deleting of a contact...
> If I log in as user 'admin' and delete a contact, the next screen the
> deleted user is still in the list of contacts. If I then go to the "List
> View" the user is gone.
>
>
>
> On 26 May 2014 12:02, Matthias Wessendorf <matzew at apache.org> wrote:
>
>>
>>
>>
>> On Mon, May 26, 2014 at 11:57 AM, Daniel Bevenius <
>> daniel.bevenius at gmail.com> wrote:
>>
>>> Hey Christos
>>>
>>> I've seen a few of these and perhaps all. I'm currently working on
>>> extracting the webapp into a separate project/modules named
>>> contacts-mobile-webapp. The webapp in that module was extracted from
>>> contacts-mobile-picketlink-secured and I've made some modifications.
>>>
>>
>> +1 awesome!
>>
>>
>>>
>>> For the logout issue I had to add the following:
>>>
>>> https://github.com/danbev/jboss-wfk-quickstarts/commit/d097ddf5c7385cf7ff8e7b003305ddb743d7fb2b#diff-e084cf285ab2733dcd0478559aa4aa40R164
>>> This was to make the CORSFilter happy or it would consider the request
>>> invalid.
>>>
>>> I've also seen the 403 Forbidden messages but I'm no longer able to
>>> reproduce them. I'll take another look at this though.
>>>
>>> [1]
>>> https://github.com/danbev/jboss-wfk-quickstarts/tree/push-proxy-quickstart
>>>
>>>
>>> On 26 May 2014 11:29, Christos Vasilakis <cvasilak at gmail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> during the development of the iOS contacts client [1] , came across the
>>>> following issues on the web interface. (Note: I am using edewit [2] branch
>>>> that contains the Push functionality).
>>>>
>>>> a) Login with ?duke:duke" (role.MAINTAINER)  and try to edit(PUT) an
>>>> existing contact  you get back a 403-Forbidden message.
>>>> b) Login with ?admin:admin (role.ADMIN)  and try to delete(DELETE) an
>>>> existing contact you get back a 403-Forbidden message.
>>>>
>>>> Interestingly enough, on the iOS client using the same credentials in
>>>> the above scenarios, they work correctly..  so possible(?) there are some
>>>> issues on the web interface.
>>>>
>>>> c) Logout on the web interface gives back a ?Forbidden? message.
>>>>
>>>> Tested on both wildfly-8.1.0.CR1 / CR2 and JBoss- EAP-6.2
>>>>
>>>> Let me know if these are currently worked on or you want me to create
>>>> JIRA?s.
>>>>
>>>> Thanks,
>>>> Christos
>>>>
>>>>
>>>> [1] https://github.com/aerogear/aerogear-push-quickstarts/pull/3
>>>> [2]
>>>> https://github.com/edewit/jboss-wfk-quickstarts/tree/push/contacts-mobile-picketlink-secured
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/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/20140526/bccc2992/attachment.html 

From cvasilak at gmail.com  Mon May 26 10:11:17 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Mon, 26 May 2014 17:11:17 +0300
Subject: [aerogear-dev] Team meeting
In-Reply-To: <CAFJm-3G4+KAUMG0tVbu9kwPx5XrEud7c0TYaJbTo7Tq5CCLLXw@mail.gmail.com>
References: <CAFJm-3G4+KAUMG0tVbu9kwPx5XrEud7c0TYaJbTo7Tq5CCLLXw@mail.gmail.com>
Message-ID: <AC48ADD3-A2B6-4B78-8880-AD61AD114D63@gmail.com>

fyi,
meeting minutes:

<jbott>	 Meeting ended Mon May 26 13:53:20 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
<jbott>	 Minutes:        http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-26-13.44.html
<jbott>	 Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-26-13.44.txt
<jbott>	 Log:            http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-05-26-13.44.log.html

On May 26, 2014, at 9:51 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> Agenda:
> http://oksoclap.com/p/aerogear-team-mgt-20140526
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140526/46e40f06/attachment-0001.html 

From bruno at abstractj.org  Mon May 26 10:20:37 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 26 May 2014 11:20:37 -0300
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <CAAg5f2R6ByA=vMpicqXYEO32vemFFXzqf99CQR0qcj+Qigha1g@mail.gmail.com>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
	<20140526121057.GA64465@abstractj.org>
	<CAAg5f2R6ByA=vMpicqXYEO32vemFFXzqf99CQR0qcj+Qigha1g@mail.gmail.com>
Message-ID: <20140526142037.GA68605@abstractj.org>

On 2014-05-26, Matthias Wessendorf wrote:
> On Mon, May 26, 2014 at 2:10 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> >
> > Good morning peeps, after the latest change[1] correct me if I'm wrong. But
> > I think KC and UPS will do pretty much what we need.
> >
> > We have a push admin and the super user on KC side enabled. Let me know
> > if that is what you need and I will take a look at viewer role.
> >
>
> One thing that I noticed: when I login as 'admin', I don't see the
> applications created by 'user'
> I think with that change, the 'admin' is the overall Keycloak-Admin.

With the recent changes we have 2 admins:

- KC admin
- UPS admin

I think the UPS admin should have the visibility of all applications
created, right? I will look at this.

>
>
> I had a chat w/ Stian in the past, for the above mentioned
> "super-user" (which is leveraging the Keycloak realm) Stian and I were
> thinking of a "Super User", that simply has not all permissions. For
> instance, it would have:
> * AdminRoles.VIEW_USERS
> * AdminRoles.MANAGE_USERS
>
> But it would not have the "AdminRoles.ADMIN" role. As we don't need to have
> that guy/super-user being able to create realms or other applications, just
> the "user access" items.
>
> I guess that's why we did see the 'remove()' before

I understand the permission scope restriction for KC admin
(aka super-user). But if we remove the admin, how could you login to manage
users/roles?

>
> -Matthias
>
>
>
>
> >
> >
> > [1] -
> >
> > https://github.com/aerogear/aerogear-unifiedpush-server/commit/3e118b1c758493942ef2a00e1541302a03e5519c
> >
> >
> > On 2014-05-21, Matthias Wessendorf wrote:
> > > Just a thought... regarding those two roles 'PushAdmin' and 'Super-User',
> > > IMO the Super-user should be able to see all apps (and their variants,
> > > including registered devices).
> > >
> > >
> > >
> > >
> > > On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org>
> > wrote:
> > >
> > > > Thank you Matthias, I will look at it and return back with more
> > > > questions if necessary.
> > > >
> > > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > > Hello,
> > > > >
> > > > > yes - the handling is done by Keycloak itself; Last time we looked at
> > > > user
> > > > > management, we had the following in terms of roles:
> > > > >
> > > > > https://gist.github.com/sebastienblanc/6547605
> > > > >
> > > > > Not sure the names of these roles are great.... let's see
> > > > >
> > > > > Basically I think the role definition in the gist still addresses
> > most of
> > > > > what we want to archive:
> > > > > * super-user: in charge of managing the UPS realm (including users);
> > can
> > > > > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > > > > * PushAdmin: Someone that can manage applications and variants, but
> > is
> > > > not
> > > > > able to add new users; he also sees only his applications/variants
> > etc
> > > > > (that's the developer in sebis gist)
> > > > >
> > > > > The gist also contains a 'Viewer' role - At this point I am not sure
> > we
> > > > do
> > > > > really need this. My impression is that if we have PushAdmins for our
> > > > 1.0.0
> > > > > community release that will be enough.
> > > > >
> > > > > -Matthias
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <
> > bruno at abstractj.org
> > > > >wrote:
> > > > >
> > > > > > Good morning peeps,
> > > > > >
> > > > > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I
> > would
> > > > > > like to understand what do you guys want say with this issue.
> > > > > >
> > > > > > Currently Keycloak already has its own user/roles managements.
> > What do
> > > > > > you guys are looking for? Any specific requirements?
> > > > > >
> > > > > > --
> > > > > >
> > > > > > 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
> > > >
> > > >
> > > > --
> > > >
> > > > 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
> >
> >
> > --
> >
> > 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


--

abstractj

From lukas.fryc at gmail.com  Mon May 26 10:24:20 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 26 May 2014 16:24:20 +0200
Subject: [aerogear-dev] Understanding AeroGear development
In-Reply-To: <1400951747551-7925.post@n5.nabble.com>
References: <1400951747551-7925.post@n5.nabble.com>
Message-ID: <CAEroY35bJTFe+DdOycTbiLEgwQO+KmVPhA9La8osS=fZPVWEGg@mail.gmail.com>

Hey John,

first thing you may want to do is checkout the cookbooks:

https://github.com/aerogear/aerogear-js-cookbook

If you enter particular directories with samples,
you will see contents of README files that describes AeroGear API used for
given sample.


The API documentation for AeroGear.js is placed here:

http://aerogear.org/docs/specs/aerogear-js/


Otherwise you can find more in general documentation:

http://aerogear.org/docs/

~ Lukas


On Sat, May 24, 2014 at 7:15 PM, jmanko <john.manko at gmail.com> wrote:

> I'm trying to get a hold on how to start development with AeroGear.  Is
> there
> any tutorial on the actual HTML design (code, not visual editor).  Are all
> applications meant to be single-paged with multi-view DIVs?  That's a lot
> of
> unrelated content on the same page, and makes it messy when having to
> design
> larger scaled apps.
>
> Anything that walks through what's taking place in the kitchen-sink sample
> HTML page would be great, and what the standard conventions are.  Thank you
> in advance.
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Understanding-AeroGear-development-tp7925.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/20140526/cca68e29/attachment.html 

From matzew at apache.org  Mon May 26 10:27:26 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 26 May 2014 16:27:26 +0200
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <20140526142037.GA68605@abstractj.org>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
	<20140526121057.GA64465@abstractj.org>
	<CAAg5f2R6ByA=vMpicqXYEO32vemFFXzqf99CQR0qcj+Qigha1g@mail.gmail.com>
	<20140526142037.GA68605@abstractj.org>
Message-ID: <CAAg5f2TTBR7dwPfz8x9m+ftWkAJ1hOo+DdO9d3ry06Ky5q+Vww@mail.gmail.com>

On Mon, May 26, 2014 at 4:20 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> On 2014-05-26, Matthias Wessendorf wrote:
> > On Mon, May 26, 2014 at 2:10 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > >
> > > Good morning peeps, after the latest change[1] correct me if I'm
> wrong. But
> > > I think KC and UPS will do pretty much what we need.
> > >
> > > We have a push admin and the super user on KC side enabled. Let me know
> > > if that is what you need and I will take a look at viewer role.
> > >
> >
> > One thing that I noticed: when I login as 'admin', I don't see the
> > applications created by 'user'
> > I think with that change, the 'admin' is the overall Keycloak-Admin.
>
> With the recent changes we have 2 admins:
>
> - KC admin
> - UPS admin
>
> I think the UPS admin should have the visibility of all applications
> created, right? I will look at this.
>

* super-user: in charge of managing the UPS realm (including users); can
see _ALL_ push applications  (that's the 'admin' in Sebi's older gist)
* PushAdmin: Someone that can manage applications and variants, but is not
able to add new users; he also sees only his applications/variants etc
(that's the 'developer' in sebisolder  gist)



>
> >
> >
> > I had a chat w/ Stian in the past, for the above mentioned
> > "super-user" (which is leveraging the Keycloak realm) Stian and I were
> > thinking of a "Super User", that simply has not all permissions. For
> > instance, it would have:
> > * AdminRoles.VIEW_USERS
> > * AdminRoles.MANAGE_USERS
> >
> > But it would not have the "AdminRoles.ADMIN" role. As we don't need to
> have
> > that guy/super-user being able to create realms or other applications,
> just
> > the "user access" items.
> >
> > I guess that's why we did see the 'remove()' before
>
> I understand the permission scope restriction for KC admin
> (aka super-user). But if we remove the admin, how could you login to manage
> users/roles?
>

The "super-admin" would be still able to manage the realm, but he would be
no longer a 'real' KC admin, by removing the 'AdminRoles.ADMIN' role,
that's what Stian and I were talking in the past.
Perhaps he can say a bit more




>
> >
> > -Matthias
> >
> >
> >
> >
> > >
> > >
> > > [1] -
> > >
> > >
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/3e118b1c758493942ef2a00e1541302a03e5519c
> > >
> > >
> > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > Just a thought... regarding those two roles 'PushAdmin' and
> 'Super-User',
> > > > IMO the Super-user should be able to see all apps (and their
> variants,
> > > > including registered devices).
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org
> >
> > > wrote:
> > > >
> > > > > Thank you Matthias, I will look at it and return back with more
> > > > > questions if necessary.
> > > > >
> > > > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > > > Hello,
> > > > > >
> > > > > > yes - the handling is done by Keycloak itself; Last time we
> looked at
> > > > > user
> > > > > > management, we had the following in terms of roles:
> > > > > >
> > > > > > https://gist.github.com/sebastienblanc/6547605
> > > > > >
> > > > > > Not sure the names of these roles are great.... let's see
> > > > > >
> > > > > > Basically I think the role definition in the gist still addresses
> > > most of
> > > > > > what we want to archive:
> > > > > > * super-user: in charge of managing the UPS realm (including
> users);
> > > can
> > > > > > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > > > > > * PushAdmin: Someone that can manage applications and variants,
> but
> > > is
> > > > > not
> > > > > > able to add new users; he also sees only his
> applications/variants
> > > etc
> > > > > > (that's the developer in sebis gist)
> > > > > >
> > > > > > The gist also contains a 'Viewer' role - At this point I am not
> sure
> > > we
> > > > > do
> > > > > > really need this. My impression is that if we have PushAdmins
> for our
> > > > > 1.0.0
> > > > > > community release that will be enough.
> > > > > >
> > > > > > -Matthias
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <
> > > bruno at abstractj.org
> > > > > >wrote:
> > > > > >
> > > > > > > Good morning peeps,
> > > > > > >
> > > > > > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I
> > > would
> > > > > > > like to understand what do you guys want say with this issue.
> > > > > > >
> > > > > > > Currently Keycloak already has its own user/roles managements.
> > > What do
> > > > > > > you guys are looking for? Any specific requirements?
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > 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
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > 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
> > >
> > >
> > > --
> > >
> > > 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
>
>
> --
>
> 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/20140526/28d2aced/attachment-0001.html 

From lukas.fryc at gmail.com  Mon May 26 10:29:11 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 26 May 2014 16:29:11 +0200
Subject: [aerogear-dev] Understanding AeroGear development
In-Reply-To: <1400958149950-7926.post@n5.nabble.com>
References: <1400951747551-7925.post@n5.nabble.com>
	<1400958149950-7926.post@n5.nabble.com>
Message-ID: <CAEroY34xz1qjH33hgxysYkMoDwNaKYLxGtudoctUj7BQ4oyrgw@mail.gmail.com>

If you want to build HTML5 based app, you should grab AeroGear.js,
but there you won't find any Maven based dependencies.

You should use either pre-built version of aerogear.js
or you can use Bower based dependency resolution (JavaScript's "Grunt +
Bower" ~= Java's "Maven").


And the HTML5 app demo within JBDS does not use AeroGear, that's right. :-)


On Sat, May 24, 2014 at 9:02 PM, jmanko <john.manko at gmail.com> wrote:

> I also noticed that when creating an HTML5 app within JBDS, none of the
> AeroGear deps were added to the pom.  Am I missing something?
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/Understanding-AeroGear-development-tp7925p7926.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/20140526/ebde4b36/attachment.html 

From bruno at abstractj.org  Mon May 26 10:46:01 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 26 May 2014 11:46:01 -0300
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <CAAg5f2TTBR7dwPfz8x9m+ftWkAJ1hOo+DdO9d3ry06Ky5q+Vww@mail.gmail.com>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
	<20140526121057.GA64465@abstractj.org>
	<CAAg5f2R6ByA=vMpicqXYEO32vemFFXzqf99CQR0qcj+Qigha1g@mail.gmail.com>
	<20140526142037.GA68605@abstractj.org>
	<CAAg5f2TTBR7dwPfz8x9m+ftWkAJ1hOo+DdO9d3ry06Ky5q+Vww@mail.gmail.com>
Message-ID: <20140526144601.GB68605@abstractj.org>

On 2014-05-26, Matthias Wessendorf wrote:
> On Mon, May 26, 2014 at 4:20 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > On 2014-05-26, Matthias Wessendorf wrote:
> > > On Mon, May 26, 2014 at 2:10 PM, Bruno Oliveira <bruno at abstractj.org>
> > wrote:
> > >
> > > >
> > > > Good morning peeps, after the latest change[1] correct me if I'm
> > wrong. But
> > > > I think KC and UPS will do pretty much what we need.
> > > >
> > > > We have a push admin and the super user on KC side enabled. Let me know
> > > > if that is what you need and I will take a look at viewer role.
> > > >
> > >
> > > One thing that I noticed: when I login as 'admin', I don't see the
> > > applications created by 'user'
> > > I think with that change, the 'admin' is the overall Keycloak-Admin.
> >
> > With the recent changes we have 2 admins:
> >
> > - KC admin
> > - UPS admin
> >
> > I think the UPS admin should have the visibility of all applications
> > created, right? I will look at this.
> >
>
> * super-user: in charge of managing the UPS realm (including users); can
> see _ALL_ push applications  (that's the 'admin' in Sebi's older gist)
> * PushAdmin: Someone that can manage applications and variants, but is not
> able to add new users; he also sees only his applications/variants etc
> (that's the 'developer' in sebisolder  gist)

You already said it in the previous e-mail, not necessary to say it
again. I think the point of confusion here is:

KC admin can't see your application/variants or whatever you want,
because it doesn't belong to KC. If you look at
http://docs.jboss.org/keycloak/docs/1.0-alpha-3/userguide/html_single/index.html#d4e311,
you will notice that KC is very good on managing application, but knows
nothing about UPS, which is correct.

>From my understanding we have 2 admins: KC and UPS. So when you say
super user, I can see into this way:

- super user: KC admin to manage realms, configurations, revoke clients,
  manage users...etc. 0 visibility of UPS domain, into other words this
  admin can't manage variants or applications.

- admin: UPS admin. This user can't manage realms, configuration, revoke
  clients, manage users...etc. But has full visibility of UPS domain,
  into other words manage variants or applications etc.


>
>
>
> >
> > >
> > >
> > > I had a chat w/ Stian in the past, for the above mentioned
> > > "super-user" (which is leveraging the Keycloak realm) Stian and I were
> > > thinking of a "Super User", that simply has not all permissions. For
> > > instance, it would have:
> > > * AdminRoles.VIEW_USERS
> > > * AdminRoles.MANAGE_USERS
> > >
> > > But it would not have the "AdminRoles.ADMIN" role. As we don't need to
> > have
> > > that guy/super-user being able to create realms or other applications,
> > just
> > > the "user access" items.
> > >
> > > I guess that's why we did see the 'remove()' before
> >
> > I understand the permission scope restriction for KC admin
> > (aka super-user). But if we remove the admin, how could you login to manage
> > users/roles?
> >
>
> The "super-admin" would be still able to manage the realm, but he would be
> no longer a 'real' KC admin, by removing the 'AdminRoles.ADMIN' role,
> that's what Stian and I were talking in the past.
> Perhaps he can say a bit more

Change permissions, I understand. But I don't understand why we need to
remove the user. Either way I will talk with Stian, thank you.

>
>
>
>
> >
> > >
> > > -Matthias
> > >
> > >
> > >
> > >
> > > >
> > > >
> > > > [1] -
> > > >
> > > >
> > https://github.com/aerogear/aerogear-unifiedpush-server/commit/3e118b1c758493942ef2a00e1541302a03e5519c
> > > >
> > > >
> > > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > > Just a thought... regarding those two roles 'PushAdmin' and
> > 'Super-User',
> > > > > IMO the Super-user should be able to see all apps (and their
> > variants,
> > > > > including registered devices).
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <bruno at abstractj.org
> > >
> > > > wrote:
> > > > >
> > > > > > Thank you Matthias, I will look at it and return back with more
> > > > > > questions if necessary.
> > > > > >
> > > > > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > yes - the handling is done by Keycloak itself; Last time we
> > looked at
> > > > > > user
> > > > > > > management, we had the following in terms of roles:
> > > > > > >
> > > > > > > https://gist.github.com/sebastienblanc/6547605
> > > > > > >
> > > > > > > Not sure the names of these roles are great.... let's see
> > > > > > >
> > > > > > > Basically I think the role definition in the gist still addresses
> > > > most of
> > > > > > > what we want to archive:
> > > > > > > * super-user: in charge of managing the UPS realm (including
> > users);
> > > > can
> > > > > > > see _ALL_ push applications  (that's the admin in Sebi's gist)
> > > > > > > * PushAdmin: Someone that can manage applications and variants,
> > but
> > > > is
> > > > > > not
> > > > > > > able to add new users; he also sees only his
> > applications/variants
> > > > etc
> > > > > > > (that's the developer in sebis gist)
> > > > > > >
> > > > > > > The gist also contains a 'Viewer' role - At this point I am not
> > sure
> > > > we
> > > > > > do
> > > > > > > really need this. My impression is that if we have PushAdmins
> > for our
> > > > > > 1.0.0
> > > > > > > community release that will be enough.
> > > > > > >
> > > > > > > -Matthias
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <
> > > > bruno at abstractj.org
> > > > > > >wrote:
> > > > > > >
> > > > > > > > Good morning peeps,
> > > > > > > >
> > > > > > > > Before I jump in https://issues.jboss.org/browse/AGPUSH-639. I
> > > > would
> > > > > > > > like to understand what do you guys want say with this issue.
> > > > > > > >
> > > > > > > > Currently Keycloak already has its own user/roles managements.
> > > > What do
> > > > > > > > you guys are looking for? Any specific requirements?
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > 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
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > 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
> > > >
> > > >
> > > > --
> > > >
> > > > 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
> >
> >
> > --
> >
> > 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


--

abstractj

From matzew at apache.org  Mon May 26 11:00:16 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 26 May 2014 17:00:16 +0200
Subject: [aerogear-dev] Keycloak user/roles management
In-Reply-To: <20140526144601.GB68605@abstractj.org>
References: <20140520200238.GA70482@abstractj.org>
	<CAAg5f2Q77bva4ZHeoVcE3GRuJFTuggOii2kbkmTfyrKEMaefMA@mail.gmail.com>
	<20140521125543.GC92541@abstractj.org>
	<CAAg5f2Tn3tj8Mu4ooBpqobGmwyii=UMVTixLLZp0UURH66jYGw@mail.gmail.com>
	<20140526121057.GA64465@abstractj.org>
	<CAAg5f2R6ByA=vMpicqXYEO32vemFFXzqf99CQR0qcj+Qigha1g@mail.gmail.com>
	<20140526142037.GA68605@abstractj.org>
	<CAAg5f2TTBR7dwPfz8x9m+ftWkAJ1hOo+DdO9d3ry06Ky5q+Vww@mail.gmail.com>
	<20140526144601.GB68605@abstractj.org>
Message-ID: <CAAg5f2S1ZC9gZhNN7Jnh8Rkrmvsdh36HLBkR6MsoCsdBM7qWWQ@mail.gmail.com>

On Mon, May 26, 2014 at 4:46 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> On 2014-05-26, Matthias Wessendorf wrote:
> > On Mon, May 26, 2014 at 4:20 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
> >
> > > On 2014-05-26, Matthias Wessendorf wrote:
> > > > On Mon, May 26, 2014 at 2:10 PM, Bruno Oliveira <bruno at abstractj.org
> >
> > > wrote:
> > > >
> > > > >
> > > > > Good morning peeps, after the latest change[1] correct me if I'm
> > > wrong. But
> > > > > I think KC and UPS will do pretty much what we need.
> > > > >
> > > > > We have a push admin and the super user on KC side enabled. Let me
> know
> > > > > if that is what you need and I will take a look at viewer role.
> > > > >
> > > >
> > > > One thing that I noticed: when I login as 'admin', I don't see the
> > > > applications created by 'user'
> > > > I think with that change, the 'admin' is the overall Keycloak-Admin.
> > >
> > > With the recent changes we have 2 admins:
> > >
> > > - KC admin
> > > - UPS admin
> > >
> > > I think the UPS admin should have the visibility of all applications
> > > created, right? I will look at this.
> > >
> >
> > * super-user: in charge of managing the UPS realm (including users); can
> > see _ALL_ push applications  (that's the 'admin' in Sebi's older gist)
> > * PushAdmin: Someone that can manage applications and variants, but is
> not
> > able to add new users; he also sees only his applications/variants etc
> > (that's the 'developer' in sebisolder  gist)
>
> You already said it in the previous e-mail, not necessary to say it
> again. I think the point of confusion here is:
>
> KC admin can't see your application/variants or whatever you want,
> because it doesn't belong to KC. If you look at
>
> http://docs.jboss.org/keycloak/docs/1.0-alpha-3/userguide/html_single/index.html#d4e311
> ,
> you will notice that KC is very good on managing application, but knows
> nothing about UPS, which is correct.
>

yes, that's correct and makes sense.


>
> >From my understanding we have 2 admins: KC and UPS. So when you say
> super user, I can see into this way:
>
> - super user: KC admin to manage realms, configurations, revoke clients,
>   manage users...etc. 0 visibility of UPS domain, into other words this
>   admin can't manage variants or applications.
>
> - admin: UPS admin. This user can't manage realms, configuration, revoke
>   clients, manage users...etc. But has full visibility of UPS domain,
>   into other words manage variants or applications etc.
>


Let's see. We need a KC-Admin to manage the UPS-realm, but just that realm;
Since we don't plan on shipping a 'full' Keycloak server,
the option to create new realms etc should be disabled (e.g. according to
Stian by removing the AdminRole)

For UPS, we might need two different roles:
* Super-User
* Push-Admin

So, that the Super-User see the all five applications (for instance):
* two from PushAdmin_1
* three from PushAdmin_2



>
>
> >
> >
> >
> > >
> > > >
> > > >
> > > > I had a chat w/ Stian in the past, for the above mentioned
> > > > "super-user" (which is leveraging the Keycloak realm) Stian and I
> were
> > > > thinking of a "Super User", that simply has not all permissions. For
> > > > instance, it would have:
> > > > * AdminRoles.VIEW_USERS
> > > > * AdminRoles.MANAGE_USERS
> > > >
> > > > But it would not have the "AdminRoles.ADMIN" role. As we don't need
> to
> > > have
> > > > that guy/super-user being able to create realms or other
> applications,
> > > just
> > > > the "user access" items.
> > > >
> > > > I guess that's why we did see the 'remove()' before
> > >
> > > I understand the permission scope restriction for KC admin
> > > (aka super-user). But if we remove the admin, how could you login to
> manage
> > > users/roles?
> > >
> >
> > The "super-admin" would be still able to manage the realm, but he would
> be
> > no longer a 'real' KC admin, by removing the 'AdminRoles.ADMIN' role,
> > that's what Stian and I were talking in the past.
> > Perhaps he can say a bit more
>
> Change permissions, I understand. But I don't understand why we need to
> remove the user. Either way I will talk with Stian, thank you.
>

sounds good



>
> >
> >
> >
> >
> > >
> > > >
> > > > -Matthias
> > > >
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > > [1] -
> > > > >
> > > > >
> > >
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/3e118b1c758493942ef2a00e1541302a03e5519c
> > > > >
> > > > >
> > > > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > > > Just a thought... regarding those two roles 'PushAdmin' and
> > > 'Super-User',
> > > > > > IMO the Super-user should be able to see all apps (and their
> > > variants,
> > > > > > including registered devices).
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <
> bruno at abstractj.org
> > > >
> > > > > wrote:
> > > > > >
> > > > > > > Thank you Matthias, I will look at it and return back with more
> > > > > > > questions if necessary.
> > > > > > >
> > > > > > > On 2014-05-21, Matthias Wessendorf wrote:
> > > > > > > > Hello,
> > > > > > > >
> > > > > > > > yes - the handling is done by Keycloak itself; Last time we
> > > looked at
> > > > > > > user
> > > > > > > > management, we had the following in terms of roles:
> > > > > > > >
> > > > > > > > https://gist.github.com/sebastienblanc/6547605
> > > > > > > >
> > > > > > > > Not sure the names of these roles are great.... let's see
> > > > > > > >
> > > > > > > > Basically I think the role definition in the gist still
> addresses
> > > > > most of
> > > > > > > > what we want to archive:
> > > > > > > > * super-user: in charge of managing the UPS realm (including
> > > users);
> > > > > can
> > > > > > > > see _ALL_ push applications  (that's the admin in Sebi's
> gist)
> > > > > > > > * PushAdmin: Someone that can manage applications and
> variants,
> > > but
> > > > > is
> > > > > > > not
> > > > > > > > able to add new users; he also sees only his
> > > applications/variants
> > > > > etc
> > > > > > > > (that's the developer in sebis gist)
> > > > > > > >
> > > > > > > > The gist also contains a 'Viewer' role - At this point I am
> not
> > > sure
> > > > > we
> > > > > > > do
> > > > > > > > really need this. My impression is that if we have PushAdmins
> > > for our
> > > > > > > 1.0.0
> > > > > > > > community release that will be enough.
> > > > > > > >
> > > > > > > > -Matthias
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <
> > > > > bruno at abstractj.org
> > > > > > > >wrote:
> > > > > > > >
> > > > > > > > > Good morning peeps,
> > > > > > > > >
> > > > > > > > > Before I jump in
> https://issues.jboss.org/browse/AGPUSH-639. I
> > > > > would
> > > > > > > > > like to understand what do you guys want say with this
> issue.
> > > > > > > > >
> > > > > > > > > Currently Keycloak already has its own user/roles
> managements.
> > > > > What do
> > > > > > > > > you guys are looking for? Any specific requirements?
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > >
> > > > > > > > > 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
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > 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
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > 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
> > >
> > >
> > > --
> > >
> > > 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
>
>
> --
>
> 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/20140526/7868f912/attachment-0001.html 

From daniel.bevenius at gmail.com  Tue May 27 02:10:11 2014
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Tue, 27 May 2014 08:10:11 +0200
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <CAFJm-3H9-t1E--T+_ctZ7+YVpw2XVwByoHFm-hFSBZWTxMiQag@mail.gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<A7CCCFDE-F89A-4E8F-9C06-BD7BC1577259@gmail.com>
	<CAFJm-3FOidFs5D7ogThjO7mORtb5q55r8BRCcn9jNbjoiHFy6w@mail.gmail.com>
	<CAAg5f2Q536Zi1A=OvhFEmdcN_8jzd3uALJ4sbfUom89d3p5Pzw@mail.gmail.com>
	<CAFJm-3ES4VQL8=rBT22jKuo+6T-18AB4Oh=XP4p172o4fSLR1g@mail.gmail.com>
	<CAFJm-3H9-t1E--T+_ctZ7+YVpw2XVwByoHFm-hFSBZWTxMiQag@mail.gmail.com>
Message-ID: <CAFJm-3Fxd8LR8eqhGTBzutpc_Tu+LsQ5VW+ANzrKaq0QnbBmZw@mail.gmail.com>

I had plans to extract the web application from contacts-mobile-basic and
contacts-mobile-secured into contacts-mobile-webapp, so that there would
only be one webapp in the code base. That would have enabled us to
configure a single webapp to work against any of the three backends:
1. contacts-mobile-basic
2. contacts-mobile-picketlink-secured
3. contacts-mobile-proxy

But after looking closer I think it might make more sense to leave
contacts-mobile-basic as-is, and let contacts-mobile-webapp work against
contacts-mobile-picketlink-secured and contacts-mobile-proxy. This is due
to the security pages/links etc that have no backend support in
contacts-mobile-basic.

The current state of things is that I've extracted the webapp from
contacts-mobile-picketlink-secured into contacts-mobile-webapp and tested
it against contacts-mobile-picketlink-secured and contacts-mobile-proxy and
things work as expected [1].

I need a fabric8-1.1.0.Beta7 before I can issue a PR for this but it would
be great if anyone has time to tryout the branch below and see if we can
discover any additional issue.

Thanks,

/Dan

[1]
https://github.com/danbev/jboss-wfk-quickstarts/tree/push-proxy-quickstart



On 26 May 2014 16:00, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> I think I've got the delete sorted with this commit:
>
> https://github.com/danbev/jboss-wfk-quickstarts/commit/0dfdb8d27ca8ba984e1e92582fb30e6a2e681b00
>
>
>
>
> On 26 May 2014 14:14, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:
>
>> I'm seeing an issue with deleting of a contact...
>> If I log in as user 'admin' and delete a contact, the next screen the
>> deleted user is still in the list of contacts. If I then go to the "List
>> View" the user is gone.
>>
>>
>>
>> On 26 May 2014 12:02, Matthias Wessendorf <matzew at apache.org> wrote:
>>
>>>
>>>
>>>
>>> On Mon, May 26, 2014 at 11:57 AM, Daniel Bevenius <
>>> daniel.bevenius at gmail.com> wrote:
>>>
>>>> Hey Christos
>>>>
>>>> I've seen a few of these and perhaps all. I'm currently working on
>>>> extracting the webapp into a separate project/modules named
>>>> contacts-mobile-webapp. The webapp in that module was extracted from
>>>> contacts-mobile-picketlink-secured and I've made some modifications.
>>>>
>>>
>>> +1 awesome!
>>>
>>>
>>>>
>>>> For the logout issue I had to add the following:
>>>>
>>>> https://github.com/danbev/jboss-wfk-quickstarts/commit/d097ddf5c7385cf7ff8e7b003305ddb743d7fb2b#diff-e084cf285ab2733dcd0478559aa4aa40R164
>>>> This was to make the CORSFilter happy or it would consider the request
>>>> invalid.
>>>>
>>>> I've also seen the 403 Forbidden messages but I'm no longer able to
>>>> reproduce them. I'll take another look at this though.
>>>>
>>>> [1]
>>>> https://github.com/danbev/jboss-wfk-quickstarts/tree/push-proxy-quickstart
>>>>
>>>>
>>>> On 26 May 2014 11:29, Christos Vasilakis <cvasilak at gmail.com> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> during the development of the iOS contacts client [1] , came across
>>>>> the following issues on the web interface. (Note: I am using edewit [2]
>>>>> branch that contains the Push functionality).
>>>>>
>>>>> a) Login with ?duke:duke" (role.MAINTAINER)  and try to edit(PUT) an
>>>>> existing contact  you get back a 403-Forbidden message.
>>>>> b) Login with ?admin:admin (role.ADMIN)  and try to delete(DELETE) an
>>>>> existing contact you get back a 403-Forbidden message.
>>>>>
>>>>> Interestingly enough, on the iOS client using the same credentials in
>>>>> the above scenarios, they work correctly..  so possible(?) there are some
>>>>> issues on the web interface.
>>>>>
>>>>> c) Logout on the web interface gives back a ?Forbidden? message.
>>>>>
>>>>> Tested on both wildfly-8.1.0.CR1 / CR2 and JBoss- EAP-6.2
>>>>>
>>>>> Let me know if these are currently worked on or you want me to create
>>>>> JIRA?s.
>>>>>
>>>>> Thanks,
>>>>> Christos
>>>>>
>>>>>
>>>>> [1] https://github.com/aerogear/aerogear-push-quickstarts/pull/3
>>>>> [2]
>>>>> https://github.com/edewit/jboss-wfk-quickstarts/tree/push/contacts-mobile-picketlink-secured
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/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/20140527/6646696d/attachment.html 

From cvasilak at gmail.com  Tue May 27 03:50:25 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Tue, 27 May 2014 10:50:25 +0300
Subject: [aerogear-dev] contacts-mobile-basic quick start
In-Reply-To: <CAFJm-3Fxd8LR8eqhGTBzutpc_Tu+LsQ5VW+ANzrKaq0QnbBmZw@mail.gmail.com>
References: <33FAC87C-F08E-4C86-842F-7A3F7D107D45@redhat.com>
	<A7CCCFDE-F89A-4E8F-9C06-BD7BC1577259@gmail.com>
	<CAFJm-3FOidFs5D7ogThjO7mORtb5q55r8BRCcn9jNbjoiHFy6w@mail.gmail.com>
	<CAAg5f2Q536Zi1A=OvhFEmdcN_8jzd3uALJ4sbfUom89d3p5Pzw@mail.gmail.com>
	<CAFJm-3ES4VQL8=rBT22jKuo+6T-18AB4Oh=XP4p172o4fSLR1g@mail.gmail.com>
	<CAFJm-3H9-t1E--T+_ctZ7+YVpw2XVwByoHFm-hFSBZWTxMiQag@mail.gmail.com>
	<CAFJm-3Fxd8LR8eqhGTBzutpc_Tu+LsQ5VW+ANzrKaq0QnbBmZw@mail.gmail.com>
Message-ID: <682680FC-677F-4566-8E2C-9392CEC4FC83@gmail.com>


On May 27, 2014, at 9:10 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:

> I had plans to extract the web application from contacts-mobile-basic and contacts-mobile-secured into contacts-mobile-webapp, so that there would only be one webapp in the code base. That would have enabled us to configure a single webapp to work against any of the three backends:
> 1. contacts-mobile-basic
> 2. contacts-mobile-picketlink-secured
> 3. contacts-mobile-proxy
> 
> But after looking closer I think it might make more sense to leave contacts-mobile-basic as-is, and let contacts-mobile-webapp work against contacts-mobile-picketlink-secured and contacts-mobile-proxy. This is due to the security pages/links etc that have no backend support in contacts-mobile-basic.

+1

> 
> The current state of things is that I've extracted the webapp from contacts-mobile-picketlink-secured into contacts-mobile-webapp and tested it against contacts-mobile-picketlink-secured and contacts-mobile-proxy and things work as expected [1].
> 
> I need a fabric8-1.1.0.Beta7 before I can issue a PR for this but it would be great if anyone has time to tryout the branch below and see if we can discover any additional issue. 

sure thing, let me give it a spin both the web app and with the iOS app.

-
Christos

> 
> Thanks,
> 
> /Dan
> 
> [1] https://github.com/danbev/jboss-wfk-quickstarts/tree/push-proxy-quickstart
> 
> 
> 
> On 26 May 2014 16:00, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:
> I think I've got the delete sorted with this commit:
> https://github.com/danbev/jboss-wfk-quickstarts/commit/0dfdb8d27ca8ba984e1e92582fb30e6a2e681b00
> 
> 
> 
> 
> On 26 May 2014 14:14, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:
> I'm seeing an issue with deleting of a contact... 
> If I log in as user 'admin' and delete a contact, the next screen the deleted user is still in the list of contacts. If I then go to the "List View" the user is gone. 
> 
> 
> 
> On 26 May 2014 12:02, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Mon, May 26, 2014 at 11:57 AM, Daniel Bevenius <daniel.bevenius at gmail.com> wrote:
> Hey Christos 
> 
> I've seen a few of these and perhaps all. I'm currently working on extracting the webapp into a separate project/modules named contacts-mobile-webapp. The webapp in that module was extracted from contacts-mobile-picketlink-secured and I've made some modifications.
> 
> +1 awesome!
>  
> 
> For the logout issue I had to add the following:
> https://github.com/danbev/jboss-wfk-quickstarts/commit/d097ddf5c7385cf7ff8e7b003305ddb743d7fb2b#diff-e084cf285ab2733dcd0478559aa4aa40R164
> This was to make the CORSFilter happy or it would consider the request invalid. 
> 
> I've also seen the 403 Forbidden messages but I'm no longer able to reproduce them. I'll take another look at this though.
> 
> [1] https://github.com/danbev/jboss-wfk-quickstarts/tree/push-proxy-quickstart
> 
> 
> On 26 May 2014 11:29, Christos Vasilakis <cvasilak at gmail.com> wrote:
> Hi all,
> 
> during the development of the iOS contacts client [1] , came across the following issues on the web interface. (Note: I am using edewit [2] branch that contains the Push functionality).
> 
> a) Login with ?duke:duke" (role.MAINTAINER)  and try to edit(PUT) an existing contact  you get back a 403-Forbidden message.
> b) Login with ?admin:admin (role.ADMIN)  and try to delete(DELETE) an existing contact you get back a 403-Forbidden message.
> 
> Interestingly enough, on the iOS client using the same credentials in the above scenarios, they work correctly..  so possible(?) there are some issues on the web interface.
> 
> c) Logout on the web interface gives back a ?Forbidden? message.
> 
> Tested on both wildfly-8.1.0.CR1 / CR2 and JBoss- EAP-6.2
> 
> Let me know if these are currently worked on or you want me to create JIRA?s.
> 
> Thanks,
> Christos
> 
> 
> [1] https://github.com/aerogear/aerogear-push-quickstarts/pull/3
> [2] https://github.com/edewit/jboss-wfk-quickstarts/tree/push/contacts-mobile-picketlink-secured
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140527/d8cd9e6a/attachment-0001.html 

From kpiwko at redhat.com  Tue May 27 08:28:25 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Tue, 27 May 2014 14:28:25 +0200
Subject: [aerogear-dev] Internal 'API' change for the different Senders?
In-Reply-To: <CAAg5f2SburX-MNUTyEe7RACQZZ7ajhzMhjTiK52dJULJE9LtOw@mail.gmail.com>
References: <CAAg5f2SburX-MNUTyEe7RACQZZ7ajhzMhjTiK52dJULJE9LtOw@mail.gmail.com>
Message-ID: <20140527142825.51c5ddb8@kapy-ntb-x220>

+1

On Fri, 23 May 2014 11:24:03 +0200
Matthias Wessendorf <matzew at apache.org> wrote:

> Hello,
> 
> looking at the Senders, I'd like to re-introduce an interface which they
> all extend:
> 
> /**
>  * Each implementation deals with the specific of the underlying push
> network, including transforming the content of the
>  * {@link UnifiedPushMessage} to the proper message format of the
> actual push network and maintaining the connection to it.
>  */
> public interface PushNotificationSender {
> 
>     /**
>      * Sends the {@link UnifiedPushMessage} to the given clients,
> identified by a collection of tokens, the underlying push network.
>      *
>      * @param variant contains details for the underlying push
> network, e.g. API Keys/Ids
>      * @param clientIdentifiers platform specific collection of client
> identifiers
>      * @param pushMessage payload to be send to the given clients
>      * @param senderCallback invoked after submitting the request to
> the underlying push network to indicate the status
>      *                       of the request (<code>success</code> or
> <code>error</code>
>      */
>     void sendPushMessage(Variant variant, Collection<String>
> clientIdentifiers, UnifiedPushMessage pushMessage,
> NotificationSenderCallback senderCallback);
> }
> 
> What's really new here is passing in a 'callback'
> (NotificationSenderCallback) that gives the caller of an
> PushNotificationSender implementation a hint if we could submit the
> messages to the push network, or not:
> 
> /**
>  * A simple Callback interface used when sending {@link
> org.jboss.aerogear.unifiedpush.message.UnifiedPushMessage} to
>  * an actual push network.
>  */
> public interface NotificationSenderCallback {
> 
>     /**
>      * Simple indicator which will be called on a successful to
> deliver to the push network. However, the invocation of
>      * this callback does <b>NOT</b> mean the messages have been sent
> out to the mobile devices. The invocation simply means
>      * the {@link
> org.jboss.aerogear.unifiedpush.message.sender.PushNotificationSender}
> was able to send the messages to
>      * the push network for its further processing
>      */
>     void onSuccess();
> 
>     /**
>      * Simple indicator which will be called on any type of error that
> occurred while sending the payload to the
>      * underlying push network.
>      */
>     void onError();
> }
> 
> The reason why I'd like to do that is this give me better access to the
> state of the request (for submitting messages). That is generally a nice
> thing to be aware of the request-state. For our new "push history" overview
> (see related threads), this comes handy, as I have all the needed
> information in a more centralized place, instead of injecting a 'Metrics'
> service into all the PushNotificationSender implementations:
> 
> ...
> // save APNs-delivery timestamp to metrics-database
> // save number of APNs tokens to metrics-database
> myAPNsSender.sendPushMessage(variant, collectionOfTokensForVariant,
> upsMessage, new NotificationSenderCallback() {
>     @Override
>     public void onSuccess() {
>         // save success status for the given variant to metrics-database
>     }
> 
>     @Override
>     public void onError() {
>         // save failure status for the given variant to metrics-database
>     }
> });
> 
> 


From lholmqui at redhat.com  Tue May 27 09:12:18 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 27 May 2014 09:12:18 -0400
Subject: [aerogear-dev] aerogear-js CouchDB data-manager adapter
In-Reply-To: <CAEroY34ms4KWzV8uKh9AK_iuBxtO6xgQ8xFjBf3=DP0+Mij2Ag@mail.gmail.com>
References: <CAN5SbcaXr8hv=36Vb-yMGYgAE+O1W8F3_+d9_oOufFVwuQGCyw@mail.gmail.com>
	<CAEroY34ms4KWzV8uKh9AK_iuBxtO6xgQ8xFjBf3=DP0+Mij2Ag@mail.gmail.com>
Message-ID: <17E821F0-B658-4AD2-B770-D204232D95C7@redhat.com>

Cool Stuff,  i will take a look

On May 26, 2014, at 7:55 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> Hey Tolis,
> 
> great job with the adapter!
> 
> 
> a) remove()
> 
> since there are obviously many ways how to achieve "delete all docs",
> I believe it's up to user to choose the way he wants the docs deleted
> i.e. it could be up to Data Manager configuration whether data will be deleted with or without a history loss (aka wipe out). wdyt?
> 
> 
> b) Filtering
> 
> It would be pretty overwhelming for a user to create a view per particular use of the filter() method, since it can have pretty arbitrary form.
> We are also able to create temporary views, but that requires you to perform one additional POST request and it is costly.
> 
> Are we able to come up with a common view definition that would cover all the filtering capabilities - i.e. generic aerogear-filter view?
> Something that user would define once and all cases would be covered.
> I have not practically played with CouchDB, but according the docs it could be somehow possible.
> 
> 
> 
> Btw as I think about it, there might be lack of function for limiting what data to transfer. 
> i.e. Filtering API allows you to select just particular docs, but it does not help you to avoid what will be transferred.
> 
> All the Data Managers so far are local ones, CouchDB is a first one that actually transfers data from the wire.

This is a concern i had when created the JIRA,   This ?adapter? might be more appropriate for DataSync( or whatever we are calling it ).  I know we were looking at couchDB as a possible backend.

I?m wondering if we should hold off for now,  and just keep DataManager client side storage only for the moment.  I think the fallback functionality will be non-trivial  


> 
> 
> Cheers,
> 
> ~ Lukas
> 
> 
> On Mon, May 26, 2014 at 8:40 AM, tolis emmanouilidis <tolisemm at gmail.com> wrote:
> Hi,
> 
> I have started working on creating a CouchDB data-manager adapter which uses the CouchDB REST API. The open-create database, read and save operations are implemented [1] and tested both with encryption settings and without encryption settings. If you'd like to give it a try, make sure that you have enabled CORS on CouchDB side.
> 
> The remaining functions that needs to be implemented are remove and filter. In addition, in order to keep consistent the data-manager API, we should provide a way to remove all the documents in a CouchDB database-store.
> 
> a) Removing all documents in a CouchDB database
> 
> I'm thinking of fetching all the docs, using _all_docs endpoint which returns _id and _rev (revision), mark them as _deleted and use the bulk insert/update API to delete them. Not sure if this is a proper solution since there might be a huge number of documents.
> 
> Another option would be to delete the database-store. This seems to be the worst solution since the documents history will be permanently lost.
> 
> Any ideas?
> 
> b) Filtering
> 
> AFAIK, in order to perform filtering in a CouchDB database, a design document and an appropriate view has to be created. My thought is that the AGJS adapter should not create the view, instead we should assume that the user has created the appopriate views and provide a setting in AGJS where the view endpoint URl can be set. 
> 
> Any ideas about filtering and the proper way to be implemented?
> 
> Thanks,
> Tolis
> 
> [1]: https://github.com/tolis-e/aerogear-js/commit/0cf952c36ea0f31aec2a6732d89eb469fd4a3d09
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140527/55da950f/attachment.html 

From matzew at apache.org  Tue May 27 09:48:12 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 27 May 2014 15:48:12 +0200
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile
 Push 1.0.0] Client SDKs for Android, Cordova and iOS)
In-Reply-To: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
References: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
Message-ID: <CAAg5f2TNU3=z+ywhhLi4NstYyiVJkLDpt2KQ9idzqV3ozZaQTw@mail.gmail.com>

any thoughts ?


-M


On Mon, May 26, 2014 at 9:48 AM, Matthias Wessendorf <matzew at apache.org>wrote:

> Hello,
>
> the latest Android libs are now on master - should we do another release,
> this week ?
>
>
> -Matthias
>
>
>
> On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>> Awesome! Thanks for commenting, guys!
>>
>> @Cordova: Will test (and merge ;-)) on Monday
>>
>>
>> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit <edewit at redhat.com>wrote:
>>
>>> Created PR?s for the open issues on Cordova once merged all done :)
>>>
>>> On 23 May,2014, at 15:18 , Daniel Passos <daniel at passos.me> wrote:
>>>
>>> All done in the android land
>>>
>>> -- Passos
>>>
>>>
>>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych <corinnekrych at gmail.com>wrote:
>>>
>>>> Indeed we?re all good for iOS push registration lib.
>>>> ++
>>>> Corinne
>>>> On 20 May 2014, at 17:09, Andrea Vibelli <avibelli at redhat.com> wrote:
>>>>
>>>> > Hi,
>>>> > I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5an old
>>>> > issue (
>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
>>>> > about the google-play-services version shipped inside the cordova
>>>> plugin.
>>>> >
>>>> > Thanks
>>>> > Andrea
>>>> >
>>>> >
>>>> > Sebastien Blanc wrote
>>>> >> Hi,
>>>> >> For the Cordova Push Plugin there is one (trivial) item open that
>>>> should
>>>> >> be
>>>> >> fixed before 1.0.  I created a jira to track it
>>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
>>>> >
>>>> >> matzew@
>>>> >
>>>> >> &gt;wrote:
>>>> >>
>>>> >>> Hi,
>>>> >>>
>>>> >>> as said before (see [1]), this summer we will release the AeroGear
>>>> Mobile
>>>> >>> Push 1.0.0 to the community.
>>>> >>>
>>>> >>> I took a look at the related JIRAs (see [2]) and noticed that for
>>>> the
>>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
>>>> >>>
>>>> >>> The github repos are also in an OK state :-) there are no feature
>>>> related
>>>> >>> open PRs; Well, besides a test improvement for the Cordova push
>>>> plugin -
>>>> >>> but that will be addressed soon;
>>>> >>>
>>>> >>> My question is: Are you guys aware of any features that we need to
>>>> add to
>>>> >>> Android, Cordova or iOS, related for push ?
>>>> >>>
>>>> >>> Once the Android and iOS bits are 'done', lets make sure we use
>>>> those
>>>> >>> latest versions on our Cordova plugin ;-)
>>>> >>>
>>>> >>> Thanks!
>>>> >>> Matthias
>>>> >>>
>>>> >>> [1]
>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>>>> >>> [2]
>>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>>>> >>>
>>>> >>>
>>>> >>> --
>>>> >>> Matthias Wessendorf
>>>> >>>
>>>> >>> blog: http://matthiaswessendorf.wordpress.com/
>>>> >>> sessions: http://www.slideshare.net/mwessendorf
>>>> >>> twitter: http://twitter.com/mwessendorf
>>>> >>>
>>>> >>> _______________________________________________
>>>> >>> aerogear-dev mailing list
>>>> >>>
>>>> >
>>>> >> aerogear-dev at .jboss
>>>> >
>>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >>>
>>>> >>
>>>> >> _______________________________________________
>>>> >> aerogear-dev mailing list
>>>> >
>>>> >> aerogear-dev at .jboss
>>>> >
>>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > View this message in context:
>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.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
>>>
>>
>>
>>
>> --
>> 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/20140527/22647b97/attachment-0001.html 

From avibelli at redhat.com  Tue May 27 09:55:44 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Tue, 27 May 2014 06:55:44 -0700 (PDT)
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile
 Push 1.0.0] Client SDKs for Android, Cordova and iOS)
In-Reply-To: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
References: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
Message-ID: <1401198944803-7958.post@n5.nabble.com>

Hi Matthias, 
it would be nice to have a new release with the latest changes, IMO!

And since the thread started from Client SDKs :-), it would be nice to have
also a new release of aerogear-push-ios-registration, the last tag 0.9.0 is
pretty old compared to the latest features on master branch.

Thanks :-)
Andrea


Matthias Wessendorf wrote
> Hello,
> 
> the latest Android libs are now on master - should we do another release,
> this week ?
> 
> 
> -Matthias
> 
> 
> 
> On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf &lt;

> matzew@

> &gt;wrote:
> 
>> Awesome! Thanks for commenting, guys!
>>
>> @Cordova: Will test (and merge ;-)) on Monday
>>
>>
>> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit &lt;

> edewit@

> &gt;wrote:
>>
>>> Created PR?s for the open issues on Cordova once merged all done :)
>>>
>>> On 23 May,2014, at 15:18 , Daniel Passos &lt;

> daniel@

> &gt; wrote:
>>>
>>> All done in the android land
>>>
>>> -- Passos
>>>
>>>
>>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych &lt;

> corinnekrych@

> &gt;wrote:
>>>
>>>> Indeed we?re all good for iOS push registration lib.
>>>> ++
>>>> Corinne
>>>> On 20 May 2014, at 17:09, Andrea Vibelli &lt;

> avibelli@

> &gt; wrote:
>>>>
>>>> > Hi,
>>>> > I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5an
>>>> old
>>>> > issue (
>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
>>>> > about the google-play-services version shipped inside the cordova
>>>> plugin.
>>>> >
>>>> > Thanks
>>>> > Andrea
>>>> >
>>>> >
>>>> > Sebastien Blanc wrote
>>>> >> Hi,
>>>> >> For the Cordova Push Plugin there is one (trivial) item open that
>>>> should
>>>> >> be
>>>> >> fixed before 1.0.  I created a jira to track it
>>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
>>>> >
>>>> >> matzew@
>>>> >
>>>> >> &gt;wrote:
>>>> >>
>>>> >>> Hi,
>>>> >>>
>>>> >>> as said before (see [1]), this summer we will release the AeroGear
>>>> Mobile
>>>> >>> Push 1.0.0 to the community.
>>>> >>>
>>>> >>> I took a look at the related JIRAs (see [2]) and noticed that for
>>>> the
>>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
>>>> >>>
>>>> >>> The github repos are also in an OK state :-) there are no feature
>>>> related
>>>> >>> open PRs; Well, besides a test improvement for the Cordova push
>>>> plugin -
>>>> >>> but that will be addressed soon;
>>>> >>>
>>>> >>> My question is: Are you guys aware of any features that we need to
>>>> add to
>>>> >>> Android, Cordova or iOS, related for push ?
>>>> >>>
>>>> >>> Once the Android and iOS bits are 'done', lets make sure we use
>>>> those
>>>> >>> latest versions on our Cordova plugin ;-)
>>>> >>>
>>>> >>> Thanks!
>>>> >>> Matthias
>>>> >>>
>>>> >>> [1]
>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>>>> >>> [2]
>>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>>>> >>>
>>>> >>>
>>>> >>> --
>>>> >>> Matthias Wessendorf
>>>> >>>
>>>> >>> blog: http://matthiaswessendorf.wordpress.com/
>>>> >>> sessions: http://www.slideshare.net/mwessendorf
>>>> >>> twitter: http://twitter.com/mwessendorf
>>>> >>>
>>>> >>> _______________________________________________
>>>> >>> aerogear-dev mailing list
>>>> >>>
>>>> >
>>>> >> aerogear-dev at .jboss
>>>> >
>>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >>>
>>>> >>
>>>> >> _______________________________________________
>>>> >> aerogear-dev mailing list
>>>> >
>>>> >> aerogear-dev at .jboss
>>>> >
>>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > View this message in context:
>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.html
>>>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>> > _______________________________________________
>>>> > aerogear-dev mailing list
>>>> > 

> aerogear-dev at .jboss

>>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> 

> aerogear-dev at .jboss

>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> 

> aerogear-dev at .jboss

>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> 

> aerogear-dev at .jboss

>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> 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 .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-tp7932p7958.html
Sent from the aerogear-dev mailing list archive at Nabble.com.


From matzew at apache.org  Tue May 27 09:57:32 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 27 May 2014 15:57:32 +0200
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile
 Push 1.0.0] Client SDKs for Android, Cordova and iOS)
In-Reply-To: <1401198944803-7958.post@n5.nabble.com>
References: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
	<1401198944803-7958.post@n5.nabble.com>
Message-ID: <CAAg5f2REuLFHShwt0FRc49nqhuNEaQ8+VwXRniighzm29psjyQ@mail.gmail.com>

On Tue, May 27, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com> wrote:

> Hi Matthias,
> it would be nice to have a new release with the latest changes, IMO!
>
> And since the thread started from Client SDKs :-), it would be nice to have
> also a new release of aerogear-push-ios-registration, the last tag 0.9.0 is
> pretty old compared to the latest features on master branch.
>

let's discuss that on the actual thread - not here; I started this mainly
for the Cordova release


>
> Thanks :-)
> Andrea
>
>
> Matthias Wessendorf wrote
> > Hello,
> >
> > the latest Android libs are now on master - should we do another release,
> > this week ?
> >
> >
> > -Matthias
> >
> >
> >
> > On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf &lt;
>
> > matzew@
>
> > &gt;wrote:
> >
> >> Awesome! Thanks for commenting, guys!
> >>
> >> @Cordova: Will test (and merge ;-)) on Monday
> >>
> >>
> >> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit &lt;
>
> > edewit@
>
> > &gt;wrote:
> >>
> >>> Created PR?s for the open issues on Cordova once merged all done :)
> >>>
> >>> On 23 May,2014, at 15:18 , Daniel Passos &lt;
>
> > daniel@
>
> > &gt; wrote:
> >>>
> >>> All done in the android land
> >>>
> >>> -- Passos
> >>>
> >>>
> >>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych &lt;
>
> > corinnekrych@
>
> > &gt;wrote:
> >>>
> >>>> Indeed we?re all good for iOS push registration lib.
> >>>> ++
> >>>> Corinne
> >>>> On 20 May 2014, at 17:09, Andrea Vibelli &lt;
>
> > avibelli@
>
> > &gt; wrote:
> >>>>
> >>>> > Hi,
> >>>> > I have reported also in
> https://issues.jboss.org/browse/AGCORDOVA-5an
> >>>> old
> >>>> > issue (
> >>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
> >>>> > about the google-play-services version shipped inside the cordova
> >>>> plugin.
> >>>> >
> >>>> > Thanks
> >>>> > Andrea
> >>>> >
> >>>> >
> >>>> > Sebastien Blanc wrote
> >>>> >> Hi,
> >>>> >> For the Cordova Push Plugin there is one (trivial) item open that
> >>>> should
> >>>> >> be
> >>>> >> fixed before 1.0.  I created a jira to track it
> >>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
> >>>> >
> >>>> >> matzew@
> >>>> >
> >>>> >> &gt;wrote:
> >>>> >>
> >>>> >>> Hi,
> >>>> >>>
> >>>> >>> as said before (see [1]), this summer we will release the AeroGear
> >>>> Mobile
> >>>> >>> Push 1.0.0 to the community.
> >>>> >>>
> >>>> >>> I took a look at the related JIRAs (see [2]) and noticed that for
> >>>> the
> >>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
> >>>> >>>
> >>>> >>> The github repos are also in an OK state :-) there are no feature
> >>>> related
> >>>> >>> open PRs; Well, besides a test improvement for the Cordova push
> >>>> plugin -
> >>>> >>> but that will be addressed soon;
> >>>> >>>
> >>>> >>> My question is: Are you guys aware of any features that we need to
> >>>> add to
> >>>> >>> Android, Cordova or iOS, related for push ?
> >>>> >>>
> >>>> >>> Once the Android and iOS bits are 'done', lets make sure we use
> >>>> those
> >>>> >>> latest versions on our Cordova plugin ;-)
> >>>> >>>
> >>>> >>> Thanks!
> >>>> >>> Matthias
> >>>> >>>
> >>>> >>> [1]
> >>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
> >>>> >>> [2]
> >>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
> >>>> >>>
> >>>> >>>
> >>>> >>> --
> >>>> >>> Matthias Wessendorf
> >>>> >>>
> >>>> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>>> >>> sessions: http://www.slideshare.net/mwessendorf
> >>>> >>> twitter: http://twitter.com/mwessendorf
> >>>> >>>
> >>>> >>> _______________________________________________
> >>>> >>> aerogear-dev mailing list
> >>>> >>>
> >>>> >
> >>>> >> aerogear-dev at .jboss
> >>>> >
> >>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>> >>>
> >>>> >>
> >>>> >> _______________________________________________
> >>>> >> aerogear-dev mailing list
> >>>> >
> >>>> >> aerogear-dev at .jboss
> >>>> >
> >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> > --
> >>>> > View this message in context:
> >>>>
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.html
> >>>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
> >>>> > _______________________________________________
> >>>> > aerogear-dev mailing list
> >>>> >
>
> > aerogear-dev at .jboss
>
> >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>>
>
> > aerogear-dev at .jboss
>
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>>
>
> > aerogear-dev at .jboss
>
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>>
>
> > aerogear-dev at .jboss
>
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >>
> >>
> >> --
> >> 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 .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-tp7932p7958.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/20140527/6fcc9f14/attachment.html 

From edewit at redhat.com  Tue May 27 10:13:22 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 27 May 2014 16:13:22 +0200
Subject: [aerogear-dev] Cordova
Message-ID: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>

Hi,

Now Cordova has it?s own jira project and therefore it?s own version number, but in github the plugins have their own repository. Would it make sense to move all the plugins into one central github repository and when making a release to release all of them?

Wdyt?
	Erik Jan

From matzew at apache.org  Tue May 27 10:16:22 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 27 May 2014 16:16:22 +0200
Subject: [aerogear-dev] Cordova
In-Reply-To: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
References: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
Message-ID: <CAAg5f2RvF-pdNV0zTWm5e3Jt-_9MsBc7YnXAWFebj7HukFW4-w@mail.gmail.com>

On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> Now Cordova has it?s own jira project and therefore it?s own version
> number, but in github the plugins have their own repository. Would it make
> sense to move all the plugins into one central github repository and when
> making a release to release all of them?
>


That means we get a few new release of the geo-plugin, while we really have
just changed things on the push-plugin (as an example) ?

-Matthias


>
> Wdyt?
>         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/20140527/5a5cf05a/attachment.html 

From bruno at abstractj.org  Tue May 27 10:16:51 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 27 May 2014 11:16:51 -0300
Subject: [aerogear-dev] Cordova
In-Reply-To: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
References: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
Message-ID: <20140527141651.GA26279@abstractj.org>

What do you mean by a central repository? Example?

On 2014-05-27, Erik Jan de Wit wrote:
> Hi,
>
> Now Cordova has it?s own jira project and therefore it?s own version number, but in github the plugins have their own repository. Would it make sense to move all the plugins into one central github repository and when making a release to release all of them?
>
> Wdyt?
> 	Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--

abstractj

From edewit at redhat.com  Tue May 27 10:19:58 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 27 May 2014 16:19:58 +0200
Subject: [aerogear-dev] Cordova
In-Reply-To: <20140527141651.GA26279@abstractj.org>
References: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
	<20140527141651.GA26279@abstractj.org>
Message-ID: <B8CA7AA4-B2D6-4220-BBAD-8612937DD9B2@redhat.com>

by repository I mean git repository
On 27 May,2014, at 16:16 , Bruno Oliveira <bruno at abstractj.org> wrote:

> What do you mean by a central repository? Example?
> 
> On 2014-05-27, Erik Jan de Wit wrote:
>> Hi,
>> 
>> Now Cordova has it?s own jira project and therefore it?s own version number, but in github the plugins have their own repository. Would it make sense to move all the plugins into one central github repository and when making a release to release all of them?
>> 
>> Wdyt?
>> 	Erik Jan
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From edewit at redhat.com  Tue May 27 10:21:30 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 27 May 2014 16:21:30 +0200
Subject: [aerogear-dev] Cordova
In-Reply-To: <CAAg5f2RvF-pdNV0zTWm5e3Jt-_9MsBc7YnXAWFebj7HukFW4-w@mail.gmail.com>
References: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
	<CAAg5f2RvF-pdNV0zTWm5e3Jt-_9MsBc7YnXAWFebj7HukFW4-w@mail.gmail.com>
Message-ID: <BB9F46A1-47D9-4BBF-9971-1A6D95CFEA24@redhat.com>

We get a release of AeroGear Cordova and all it?s components. I know if you want to find out what changed for each plugin and version, that will be less ideal. If you have a suggestion to have it tracked better I?m all ears

On 27 May,2014, at 16:16 , Matthias Wessendorf <matzew at apache.org> wrote:

> 
> 
> 
> On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
> Hi,
> 
> Now Cordova has it?s own jira project and therefore it?s own version number, but in github the plugins have their own repository. Would it make sense to move all the plugins into one central github repository and when making a release to release all of them?
> 
> 
> That means we get a few new release of the geo-plugin, while we really have just changed things on the push-plugin (as an example) ? 
> 
> -Matthias
>  
> 
> Wdyt?
>         Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140527/7a205857/attachment.html 

From lholmqui at redhat.com  Tue May 27 10:27:13 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 27 May 2014 10:27:13 -0400
Subject: [aerogear-dev] pipeline node.js experiment
Message-ID: <9BE2D0A8-2B9C-4A84-A96E-8E16841F79E7@redhat.com>

Last week i decided to start playing around with converting the AeroGear.js Pipeline library to run in node.js

I thought this would be a good place to start when thinking about how ES6 modules work, and how the code would need to be structured.

This is no doubt a WIP, but have a look see here:

https://github.com/lholmquist/aerogear-pipeline

currently it only deals in JSON

For usage checkout the tests. The Usage should be similar but since this is node.js, i?m following some of their conventions for how they do callbacks. The convention is to have a callback where the first argument is the err

an example read:

pipe.read({ id: 1 }, function(err, data, response) {
});
or to read all

pipe.read(function (err, data, response) {
});
and since this is just wrapping a http.request, it will also emit any events the http.request emits

For those wondering about my code style here, i?ve adapted the style from the yeoman project, with 1 difference, 4 spaces instead of 2

I'm not sure what part of the library could be next, datamanager might not make sense here since there is no "client side" storage per say.

I have a WIP implentation of a SimplePush client here: https://github.com/lholmquist/aerogear-simplepush-node-client

Thoughts?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140527/f82adc06/attachment.html 

From gorkem.ercan at gmail.com  Tue May 27 10:28:53 2014
From: gorkem.ercan at gmail.com (Gorkem Ercan)
Date: Tue, 27 May 2014 10:28:53 -0400
Subject: [aerogear-dev] Cordova
In-Reply-To: <BB9F46A1-47D9-4BBF-9971-1A6D95CFEA24@redhat.com>
References: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
	<CAAg5f2RvF-pdNV0zTWm5e3Jt-_9MsBc7YnXAWFebj7HukFW4-w@mail.gmail.com>
	<BB9F46A1-47D9-4BBF-9971-1A6D95CFEA24@redhat.com>
Message-ID: <CA+X37ck=BTNU5i8R4DOpYkRh_cOvbkrk7mxnVi07K1WVs4xQcw@mail.gmail.com>

On the practical side, it makes it a bit harder to install a Cordova plugin
from a git repo (because you need to point to a subdir)  via Eclipse Thym
and Cordova CLI.
--
Gorkem


On Tue, May 27, 2014 at 10:21 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> We get a release of AeroGear Cordova and all it?s components. I know if
> you want to find out what changed for each plugin and version, that will be
> less ideal. If you have a suggestion to have it tracked better I?m all ears
>
> On 27 May,2014, at 16:16 , Matthias Wessendorf <matzew at apache.org> wrote:
>
>
>
>
> On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit at redhat.com>wrote:
>
>> Hi,
>>
>> Now Cordova has it?s own jira project and therefore it?s own version
>> number, but in github the plugins have their own repository. Would it make
>> sense to move all the plugins into one central github repository and when
>> making a release to release all of them?
>>
>
>
> That means we get a few new release of the geo-plugin, while we really
> have just changed things on the push-plugin (as an example) ?
>
> -Matthias
>
>
>>
>> Wdyt?
>>         Erik Jan
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140527/f340a3cf/attachment-0001.html 

From edewit at redhat.com  Tue May 27 10:51:23 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 27 May 2014 16:51:23 +0200
Subject: [aerogear-dev] Cordova
In-Reply-To: <CA+X37ck=BTNU5i8R4DOpYkRh_cOvbkrk7mxnVi07K1WVs4xQcw@mail.gmail.com>
References: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
	<CAAg5f2RvF-pdNV0zTWm5e3Jt-_9MsBc7YnXAWFebj7HukFW4-w@mail.gmail.com>
	<BB9F46A1-47D9-4BBF-9971-1A6D95CFEA24@redhat.com>
	<CA+X37ck=BTNU5i8R4DOpYkRh_cOvbkrk7mxnVi07K1WVs4xQcw@mail.gmail.com>
Message-ID: <569E19FA-0DC8-4F26-A643-A4FF6C3C5B69@redhat.com>

That is a very good point? so if we keep them as separate repos how do we manage multiple versions / releases in jira

On 27 May,2014, at 16:28 , Gorkem Ercan <gorkem.ercan at gmail.com> wrote:

> On the practical side, it makes it a bit harder to install a Cordova plugin from a git repo (because you need to point to a subdir)  via Eclipse Thym and Cordova CLI.
> --
> Gorkem
> 
> 
> On Tue, May 27, 2014 at 10:21 AM, Erik Jan de Wit <edewit at redhat.com> wrote:
> We get a release of AeroGear Cordova and all it?s components. I know if you want to find out what changed for each plugin and version, that will be less ideal. If you have a suggestion to have it tracked better I?m all ears
> 
> On 27 May,2014, at 16:16 , Matthias Wessendorf <matzew at apache.org> wrote:
> 
>> 
>> 
>> 
>> On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
>> Hi,
>> 
>> Now Cordova has it?s own jira project and therefore it?s own version number, but in github the plugins have their own repository. Would it make sense to move all the plugins into one central github repository and when making a release to release all of them?
>> 
>> 
>> That means we get a few new release of the geo-plugin, while we really have just changed things on the push-plugin (as an example) ? 
>> 
>> -Matthias
>>  
>> 
>> Wdyt?
>>         Erik Jan
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140527/f6b2be47/attachment.html 

From gorkem.ercan at gmail.com  Tue May 27 10:56:41 2014
From: gorkem.ercan at gmail.com (Gorkem Ercan)
Date: Tue, 27 May 2014 10:56:41 -0400
Subject: [aerogear-dev] Cordova
In-Reply-To: <569E19FA-0DC8-4F26-A643-A4FF6C3C5B69@redhat.com>
References: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
	<CAAg5f2RvF-pdNV0zTWm5e3Jt-_9MsBc7YnXAWFebj7HukFW4-w@mail.gmail.com>
	<BB9F46A1-47D9-4BBF-9971-1A6D95CFEA24@redhat.com>
	<CA+X37ck=BTNU5i8R4DOpYkRh_cOvbkrk7mxnVi07K1WVs4xQcw@mail.gmail.com>
	<569E19FA-0DC8-4F26-A643-A4FF6C3C5B69@redhat.com>
Message-ID: <CA+X37c=ty9gA0jmZXQuukt+8bfiNjd8+Zy7iqhmqyGFa-sRbuA@mail.gmail.com>

Would tagging all repos with the same version number as the jira version
number on a release work?
--
Gorkem


On Tue, May 27, 2014 at 10:51 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> That is a very good point? so if we keep them as separate repos how do we
> manage multiple versions / releases in jira
>
> On 27 May,2014, at 16:28 , Gorkem Ercan <gorkem.ercan at gmail.com> wrote:
>
> On the practical side, it makes it a bit harder to install a Cordova
> plugin from a git repo (because you need to point to a subdir)  via Eclipse
> Thym and Cordova CLI.
> --
> Gorkem
>
>
> On Tue, May 27, 2014 at 10:21 AM, Erik Jan de Wit <edewit at redhat.com>wrote:
>
>> We get a release of AeroGear Cordova and all it?s components. I know if
>> you want to find out what changed for each plugin and version, that will be
>> less ideal. If you have a suggestion to have it tracked better I?m all ears
>>
>> On 27 May,2014, at 16:16 , Matthias Wessendorf <matzew at apache.org> wrote:
>>
>>
>>
>>
>> On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit at redhat.com>wrote:
>>
>>> Hi,
>>>
>>> Now Cordova has it?s own jira project and therefore it?s own version
>>> number, but in github the plugins have their own repository. Would it make
>>> sense to move all the plugins into one central github repository and when
>>> making a release to release all of them?
>>>
>>
>>
>> That means we get a few new release of the geo-plugin, while we really
>> have just changed things on the push-plugin (as an example) ?
>>
>> -Matthias
>>
>>
>>>
>>> Wdyt?
>>>         Erik Jan
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140527/8a224df1/attachment.html 

From tolisemm at gmail.com  Tue May 27 11:23:14 2014
From: tolisemm at gmail.com (tolis emmanouilidis)
Date: Tue, 27 May 2014 18:23:14 +0300
Subject: [aerogear-dev] pipeline node.js experiment
In-Reply-To: <9BE2D0A8-2B9C-4A84-A96E-8E16841F79E7@redhat.com>
References: <9BE2D0A8-2B9C-4A84-A96E-8E16841F79E7@redhat.com>
Message-ID: <CAN5SbcZPn69+C2Uw6DtOKL48dyvQFpYMpFxwrLr_SuGOsTbgJQ@mail.gmail.com>

looks great

+1 for using some conventions of npm code styling

It would be nice to follow one more npm-code-style convention about
callbacks, which says that the callback is always the last argument in the
list. It will be easier for users to use our API and it improves
consistency.


2014-05-27 17:27 GMT+03:00 Lucas Holmquist <lholmqui at redhat.com>:

> Last week i decided to start playing around with converting the
> AeroGear.js Pipeline library to run in node.js
>
> I thought this would be a good place to start when thinking about how ES6
> modules work, and how the code would need to be structured.
>
> This is no doubt a WIP, but have a look see here:
>
> https://github.com/lholmquist/aerogear-pipeline
>
> *currently it only deals in JSON*
>
> For usage checkout the tests. The Usage should be similar but since this
> is node.js, i?m following some of their conventions for how they do
> callbacks. The convention is to have a callback where the first argument is
> the err
>
> an example read:
>
> pipe.read({ id: 1 }, function(err, data, response) {
> });
>
> or to read all
>
> pipe.read(function (err, data, response) {
> });
>
> and since this is just wrapping a http.request, it will also emit any
> events the http.request emits
>
> *For those wondering about my code style here, i?ve adapted the style from
> the yeoman project, with 1 difference, 4 spaces instead of 2*
>
> I'm not sure what part of the library could be next, datamanager might not
> make sense here since there is no "client side" storage per say.
>
> I have a WIP implentation of a SimplePush client here:
> https://github.com/lholmquist/aerogear-simplepush-node-client
>
> Thoughts?
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140527/14b2fed4/attachment.html 

From scm.blanc at gmail.com  Tue May 27 11:28:34 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Tue, 27 May 2014 17:28:34 +0200
Subject: [aerogear-dev] pipeline node.js experiment
In-Reply-To: <CAN5SbcZPn69+C2Uw6DtOKL48dyvQFpYMpFxwrLr_SuGOsTbgJQ@mail.gmail.com>
References: <9BE2D0A8-2B9C-4A84-A96E-8E16841F79E7@redhat.com>
	<CAN5SbcZPn69+C2Uw6DtOKL48dyvQFpYMpFxwrLr_SuGOsTbgJQ@mail.gmail.com>
Message-ID: <CAD_dpu3w5x7=_JNow_tTY9uFGkuH3H_g-vYvhHg2rz72O=grPg@mail.gmail.com>

Nice !
For the datamanager, it would make sense if we had adapters for "backend"
persistence solution and that would be a fantastic library ;)



On Tue, May 27, 2014 at 5:23 PM, tolis emmanouilidis <tolisemm at gmail.com>wrote:

> looks great
>
> +1 for using some conventions of npm code styling
>
> It would be nice to follow one more npm-code-style convention about
> callbacks, which says that the callback is always the last argument in the
> list. It will be easier for users to use our API and it improves
> consistency.
>
>
> 2014-05-27 17:27 GMT+03:00 Lucas Holmquist <lholmqui at redhat.com>:
>
>> Last week i decided to start playing around with converting the
>> AeroGear.js Pipeline library to run in node.js
>>
>> I thought this would be a good place to start when thinking about how ES6
>> modules work, and how the code would need to be structured.
>>
>> This is no doubt a WIP, but have a look see here:
>>
>> https://github.com/lholmquist/aerogear-pipeline
>>
>> *currently it only deals in JSON*
>>
>> For usage checkout the tests. The Usage should be similar but since this
>> is node.js, i?m following some of their conventions for how they do
>> callbacks. The convention is to have a callback where the first argument is
>> the err
>>
>> an example read:
>>
>> pipe.read({ id: 1 }, function(err, data, response) {
>> });
>>
>> or to read all
>>
>> pipe.read(function (err, data, response) {
>> });
>>
>> and since this is just wrapping a http.request, it will also emit any
>> events the http.request emits
>>
>> *For those wondering about my code style here, i?ve adapted the style
>> from the yeoman project, with 1 difference, 4 spaces instead of 2*
>>
>> I'm not sure what part of the library could be next, datamanager might
>> not make sense here since there is no "client side" storage per say.
>>
>> I have a WIP implentation of a SimplePush client here:
>> https://github.com/lholmquist/aerogear-simplepush-node-client
>>
>> Thoughts?
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140527/ec98ff37/attachment-0001.html 

From lholmqui at redhat.com  Tue May 27 11:29:08 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 27 May 2014 11:29:08 -0400
Subject: [aerogear-dev] pipeline node.js experiment
In-Reply-To: <CAN5SbcZPn69+C2Uw6DtOKL48dyvQFpYMpFxwrLr_SuGOsTbgJQ@mail.gmail.com>
References: <9BE2D0A8-2B9C-4A84-A96E-8E16841F79E7@redhat.com>
	<CAN5SbcZPn69+C2Uw6DtOKL48dyvQFpYMpFxwrLr_SuGOsTbgJQ@mail.gmail.com>
Message-ID: <B3B66624-9ACA-4B12-AE42-9E4F16459AC7@redhat.com>


On May 27, 2014, at 11:23 AM, tolis emmanouilidis <tolisemm at gmail.com> wrote:

> looks great
> 
> +1 for using some conventions of npm code styling
> 
> It would be nice to follow one more npm-code-style convention about callbacks, which says that the callback is always the last argument in the list. It will be easier for users to use our API and it improves
> consistency.

+1, and it might do that sort of already,  but maybe not  :)

> 
> 
> 2014-05-27 17:27 GMT+03:00 Lucas Holmquist <lholmqui at redhat.com>:
> Last week i decided to start playing around with converting the AeroGear.js Pipeline library to run in node.js
> 
> I thought this would be a good place to start when thinking about how ES6 modules work, and how the code would need to be structured.
> 
> This is no doubt a WIP, but have a look see here:
> 
> https://github.com/lholmquist/aerogear-pipeline
> 
> currently it only deals in JSON
> 
> For usage checkout the tests. The Usage should be similar but since this is node.js, i?m following some of their conventions for how they do callbacks. The convention is to have a callback where the first argument is the err
> 
> an example read:
> 
> pipe.read({ id: 1 }, function(err, data, response) {
> });
> or to read all
> 
> pipe.read(function (err, data, response) {
> });
> and since this is just wrapping a http.request, it will also emit any events the http.request emits
> 
> For those wondering about my code style here, i?ve adapted the style from the yeoman project, with 1 difference, 4 spaces instead of 2
> 
> I'm not sure what part of the library could be next, datamanager might not make sense here since there is no "client side" storage per say.
> 
> I have a WIP implentation of a SimplePush client here: https://github.com/lholmquist/aerogear-simplepush-node-client
> 
> Thoughts?
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140527/9b62857d/attachment.html 

From lukas.fryc at gmail.com  Tue May 27 14:43:20 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Tue, 27 May 2014 20:43:20 +0200
Subject: [aerogear-dev] pipeline node.js experiment
In-Reply-To: <B3B66624-9ACA-4B12-AE42-9E4F16459AC7@redhat.com>
References: <9BE2D0A8-2B9C-4A84-A96E-8E16841F79E7@redhat.com>
	<CAN5SbcZPn69+C2Uw6DtOKL48dyvQFpYMpFxwrLr_SuGOsTbgJQ@mail.gmail.com>
	<B3B66624-9ACA-4B12-AE42-9E4F16459AC7@redhat.com>
Message-ID: <CAEroY36MsjmR1hfmHjcJCn9f+UoVk5g-Ux8Grw6iK18dqGYQdg@mail.gmail.com>

Hey Luke,

speaking about ES6, have you considered to adopt Promises in Pipes as well?
:-)

...read().then().catch() obsession


On Tue, May 27, 2014 at 5:29 PM, Lucas Holmquist <lholmqui at redhat.com>wrote:

>
> On May 27, 2014, at 11:23 AM, tolis emmanouilidis <tolisemm at gmail.com>
> wrote:
>
> looks great
>
> +1 for using some conventions of npm code styling
>
> It would be nice to follow one more npm-code-style convention about
> callbacks, which says that the callback is always the last argument in the
> list. It will be easier for users to use our API and it improves
>
> consistency.
>
>
> +1, and it might do that sort of already,  but maybe not  :)
>
>
>
> 2014-05-27 17:27 GMT+03:00 Lucas Holmquist <lholmqui at redhat.com>:
>
>> Last week i decided to start playing around with converting the
>> AeroGear.js Pipeline library to run in node.js
>>
>> I thought this would be a good place to start when thinking about how ES6
>> modules work, and how the code would need to be structured.
>>
>> This is no doubt a WIP, but have a look see here:
>>
>> https://github.com/lholmquist/aerogear-pipeline
>>
>> *currently it only deals in JSON*
>>
>> For usage checkout the tests. The Usage should be similar but since this
>> is node.js, i?m following some of their conventions for how they do
>> callbacks. The convention is to have a callback where the first argument is
>> the err
>>
>> an example read:
>>
>> pipe.read({ id: 1 }, function(err, data, response) {
>> });
>>
>> or to read all
>>
>> pipe.read(function (err, data, response) {
>> });
>>
>> and since this is just wrapping a http.request, it will also emit any
>> events the http.request emits
>>
>> *For those wondering about my code style here, i?ve adapted the style
>> from the yeoman project, with 1 difference, 4 spaces instead of 2*
>>
>> I'm not sure what part of the library could be next, datamanager might
>> not make sense here since there is no "client side" storage per say.
>>
>> I have a WIP implentation of a SimplePush client here:
>> https://github.com/lholmquist/aerogear-simplepush-node-client
>>
>> Thoughts?
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140527/8184c1a4/attachment.html 

From lholmqui at redhat.com  Tue May 27 14:45:54 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Tue, 27 May 2014 14:45:54 -0400
Subject: [aerogear-dev] pipeline node.js experiment
In-Reply-To: <CAEroY36MsjmR1hfmHjcJCn9f+UoVk5g-Ux8Grw6iK18dqGYQdg@mail.gmail.com>
References: <9BE2D0A8-2B9C-4A84-A96E-8E16841F79E7@redhat.com>
	<CAN5SbcZPn69+C2Uw6DtOKL48dyvQFpYMpFxwrLr_SuGOsTbgJQ@mail.gmail.com>
	<B3B66624-9ACA-4B12-AE42-9E4F16459AC7@redhat.com>
	<CAEroY36MsjmR1hfmHjcJCn9f+UoVk5g-Ux8Grw6iK18dqGYQdg@mail.gmail.com>
Message-ID: <CF772186-A45F-4FE1-B539-4CF90A9093E1@redhat.com>


On May 27, 2014, at 2:43 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> Hey Luke,
> 
> speaking about ES6, have you considered to adopt Promises in Pipes as well? :-)
> 
> ...read().then().catch() obsession

i do,  but i wanted to wait until we got rid of the jQuery dependency for the browser lib first

for the node.js version,  it can happen anytime 

:)

> 
> 
> On Tue, May 27, 2014 at 5:29 PM, Lucas Holmquist <lholmqui at redhat.com> wrote:
> 
> On May 27, 2014, at 11:23 AM, tolis emmanouilidis <tolisemm at gmail.com> wrote:
> 
>> looks great
>> 
>> +1 for using some conventions of npm code styling
>> 
>> It would be nice to follow one more npm-code-style convention about callbacks, which says that the callback is always the last argument in the list. It will be easier for users to use our API and it improves
>> consistency.
> 
> +1, and it might do that sort of already,  but maybe not  :)
> 
>> 
>> 
>> 2014-05-27 17:27 GMT+03:00 Lucas Holmquist <lholmqui at redhat.com>:
>> Last week i decided to start playing around with converting the AeroGear.js Pipeline library to run in node.js
>> 
>> I thought this would be a good place to start when thinking about how ES6 modules work, and how the code would need to be structured.
>> 
>> This is no doubt a WIP, but have a look see here:
>> 
>> https://github.com/lholmquist/aerogear-pipeline
>> 
>> currently it only deals in JSON
>> 
>> For usage checkout the tests. The Usage should be similar but since this is node.js, i?m following some of their conventions for how they do callbacks. The convention is to have a callback where the first argument is the err
>> 
>> an example read:
>> 
>> 
>> pipe.read({ id: 1 }, function(err, data, response) {
>> });
>> or to read all
>> 
>> 
>> pipe.read(function (err, data, response) {
>> });
>> and since this is just wrapping a http.request, it will also emit any events the http.request emits
>> 
>> For those wondering about my code style here, i?ve adapted the style from the yeoman project, with 1 difference, 4 spaces instead of 2
>> 
>> I'm not sure what part of the library could be next, datamanager might not make sense here since there is no "client side" storage per say.
>> 
>> I have a WIP implentation of a SimplePush client here: https://github.com/lholmquist/aerogear-simplepush-node-client
>> 
>> Thoughts?
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140527/aebdc843/attachment-0001.html 

From bruno at abstractj.org  Tue May 27 15:17:20 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Tue, 27 May 2014 16:17:20 -0300
Subject: [aerogear-dev] Cordova
In-Reply-To: <B8CA7AA4-B2D6-4220-BBAD-8612937DD9B2@redhat.com>
References: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
	<20140527141651.GA26279@abstractj.org>
	<B8CA7AA4-B2D6-4220-BBAD-8612937DD9B2@redhat.com>
Message-ID: <20140527191720.GB48959@abstractj.org>

I assume we are all talking about a git repositories here. By central
repository do you mean create something like /aerogear/cordova.git - and put everything
inside?

If yes, I would vote for separated repositories.

On 2014-05-27, Erik Jan de Wit wrote:
> by repository I mean git repository
> On 27 May,2014, at 16:16 , Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > What do you mean by a central repository? Example?
> >
> > On 2014-05-27, Erik Jan de Wit wrote:
> >> Hi,
> >>
> >> Now Cordova has it?s own jira project and therefore it?s own version number, but in github the plugins have their own repository. Would it make sense to move all the plugins into one central github repository and when making a release to release all of them?
> >>
> >> Wdyt?
> >> 	Erik Jan
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> > --
> >
> > 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

--

abstractj

From matzew at apache.org  Wed May 28 03:03:23 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 09:03:23 +0200
Subject: [aerogear-dev] Cordova
In-Reply-To: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
References: <8DDF522B-5D78-4A05-8538-1E50425FCABE@redhat.com>
Message-ID: <CAAg5f2QEetQb_za+AK9Z2PhUOrM06tfevrRECQYh4DFXCUEeNg@mail.gmail.com>

On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> Now Cordova has it?s own jira project and therefore it?s own version
> number, but in github the plugins have their own repository. Would it make
> sense to move all the plugins into one central github repository and when
> making a release to release all of them?
>

To address the 'version' issue, I guess we can have a schema like below
inside of the Cordova JIRA:

crypto-x.y.z
geo-x.y.z
push-x.y.z
etc

That way we can still track the different components, on their own versions
- and do specific releases in JIRA as well


>
> Wdyt?
>         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/20140528/f7ce05e5/attachment.html 

From tolisemm at gmail.com  Wed May 28 03:19:18 2014
From: tolisemm at gmail.com (tolis emmanouilidis)
Date: Wed, 28 May 2014 10:19:18 +0300
Subject: [aerogear-dev] aerogear-js CouchDB data-manager adapter
In-Reply-To: <17E821F0-B658-4AD2-B770-D204232D95C7@redhat.com>
References: <CAN5SbcaXr8hv=36Vb-yMGYgAE+O1W8F3_+d9_oOufFVwuQGCyw@mail.gmail.com>
	<CAEroY34ms4KWzV8uKh9AK_iuBxtO6xgQ8xFjBf3=DP0+Mij2Ag@mail.gmail.com>
	<17E821F0-B658-4AD2-B770-D204232D95C7@redhat.com>
Message-ID: <CAN5SbcYYKjc962J6M4rFpK5N0OBeoW=qvVwKYDHnjoYpei9ByQ@mail.gmail.com>

Thank you both.

I agree to freeze the adapter's development until datasync is discussed.

comments inline

2014-05-27 16:12 GMT+03:00 Lucas Holmquist <lholmqui at redhat.com>:

> Cool Stuff,  i will take a look
>
> On May 26, 2014, at 7:55 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
>
> Hey Tolis,
>
> great job with the adapter!
>
>
> a) remove()
>
> since there are obviously many ways how to achieve "delete all docs",
> I believe it's up to user to choose the way he wants the docs deleted
> i.e. it could be up to Data Manager configuration whether data will be
> deleted with or without a history loss (aka wipe out). wdyt?
>
> +1

investigation is needed to find out if there are any best practices


>
> b) Filtering
>
> It would be pretty overwhelming for a user to create a view per particular
> use of the filter() method, since it can have pretty arbitrary form.
> We are also able to create temporary views, but that requires you to
> perform one additional POST request and it is costly.
>
> I think it's not overwelming for a user to create the view manually.
CouchDB filtering is based on the key (simple or complex). IMO the ability
to search/filter different fields (which are not part of a complex key) and
create a view in each request, has no meaning in CouchDB. If a user has a
such requirement and data-queries are changing very often, then he should
consider using a different NoSQL db. CouchDB serves specific purposes and a
possible AeroGear JS CouchDB adapter should not offer functionality which
CouchDB is not designed to serve.

Temporary views are not a solution, for sure. They are one-off queries,
meaning that they are computed in each call (expensive and slow). CouchDB
docs suggest to use them for development purposes.


> Are we able to come up with a common view definition that would cover all
> the filtering capabilities - i.e. generic aerogear-filter view?
> Something that user would define once and all cases would be covered.
> I have not practically played with CouchDB, but according the docs it
> could be somehow possible.
>
>
>
> Btw as I think about it, there might be lack of function for limiting what
> data to transfer.
> i.e. Filtering API allows you to select just particular docs, but it does
> not help you to avoid what will be transferred.
>
> All the Data Managers so far are local ones, CouchDB is a first one that
> actually transfers data from the wire.
>
>
> This is a concern i had when created the JIRA,   This ?adapter? might be
> more appropriate for DataSync( or whatever we are calling it ).  I know we
> were looking at couchDB as a possible backend.
>
> I?m wondering if we should hold off for now,  and just keep DataManager
> client side storage only for the moment.  I think the fallback
> functionality will be non-trivial
>
> agreed


>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140528/c7f31aff/attachment.html 

From avibelli at redhat.com  Wed May 28 04:08:29 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Wed, 28 May 2014 01:08:29 -0700 (PDT)
Subject: [aerogear-dev] New iOS Push SDK Client Release
Message-ID: <1401264508560-7977.post@n5.nabble.com>

Hi all, 
the latest release of aerogear-push-ios-registration, version 0.9.0, is
pretty old (more than 2 months ago), and does not contain some useful
features like the build script for the creation of framework and static
libs, and the new extended readme with instruction on how to use them.

Are there any plans for a new release?
Thanks
Andrea




--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/New-iOS-Push-SDK-Client-Release-tp7977.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From edewit at redhat.com  Wed May 28 05:05:04 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 28 May 2014 11:05:04 +0200
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile
	Push 1.0.0] Client SDKs for Android, Cordova and iOS)
In-Reply-To: <CAAg5f2REuLFHShwt0FRc49nqhuNEaQ8+VwXRniighzm29psjyQ@mail.gmail.com>
References: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
	<1401198944803-7958.post@n5.nabble.com>
	<CAAg5f2REuLFHShwt0FRc49nqhuNEaQ8+VwXRniighzm29psjyQ@mail.gmail.com>
Message-ID: <133BDEC2-A1A6-416F-8A8C-2F4EAF06CB88@redhat.com>

We could do another release although there are not many changes since the last release (0.5.0)

Change log:
	updated lib (android)
	Automate plugin testing using grunt-cordova-plugin-jasmine.
	fix a bug with the foreground/isInline flag
	fix bug with android not sending cached message


On 27 May,2014, at 15:57 , Matthias Wessendorf <matzew at apache.org> wrote:

> 
> 
> 
> On Tue, May 27, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com> wrote:
> Hi Matthias,
> it would be nice to have a new release with the latest changes, IMO!
> 
> And since the thread started from Client SDKs :-), it would be nice to have
> also a new release of aerogear-push-ios-registration, the last tag 0.9.0 is
> pretty old compared to the latest features on master branch.
> 
> let's discuss that on the actual thread - not here; I started this mainly for the Cordova release
>  
> 
> Thanks :-)
> Andrea
> 
> 
> Matthias Wessendorf wrote
> > Hello,
> >
> > the latest Android libs are now on master - should we do another release,
> > this week ?
> >
> >
> > -Matthias
> >
> >
> >
> > On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf &lt;
> 
> > matzew@
> 
> > &gt;wrote:
> >
> >> Awesome! Thanks for commenting, guys!
> >>
> >> @Cordova: Will test (and merge ;-)) on Monday
> >>
> >>
> >> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit &lt;
> 
> > edewit@
> 
> > &gt;wrote:
> >>
> >>> Created PR?s for the open issues on Cordova once merged all done :)
> >>>
> >>> On 23 May,2014, at 15:18 , Daniel Passos &lt;
> 
> > daniel@
> 
> > &gt; wrote:
> >>>
> >>> All done in the android land
> >>>
> >>> -- Passos
> >>>
> >>>
> >>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych &lt;
> 
> > corinnekrych@
> 
> > &gt;wrote:
> >>>
> >>>> Indeed we?re all good for iOS push registration lib.
> >>>> ++
> >>>> Corinne
> >>>> On 20 May 2014, at 17:09, Andrea Vibelli &lt;
> 
> > avibelli@
> 
> > &gt; wrote:
> >>>>
> >>>> > Hi,
> >>>> > I have reported also in https://issues.jboss.org/browse/AGCORDOVA-5an
> >>>> old
> >>>> > issue (
> >>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
> >>>> > about the google-play-services version shipped inside the cordova
> >>>> plugin.
> >>>> >
> >>>> > Thanks
> >>>> > Andrea
> >>>> >
> >>>> >
> >>>> > Sebastien Blanc wrote
> >>>> >> Hi,
> >>>> >> For the Cordova Push Plugin there is one (trivial) item open that
> >>>> should
> >>>> >> be
> >>>> >> fixed before 1.0.  I created a jira to track it
> >>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
> >>>> >
> >>>> >> matzew@
> >>>> >
> >>>> >> &gt;wrote:
> >>>> >>
> >>>> >>> Hi,
> >>>> >>>
> >>>> >>> as said before (see [1]), this summer we will release the AeroGear
> >>>> Mobile
> >>>> >>> Push 1.0.0 to the community.
> >>>> >>>
> >>>> >>> I took a look at the related JIRAs (see [2]) and noticed that for
> >>>> the
> >>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
> >>>> >>>
> >>>> >>> The github repos are also in an OK state :-) there are no feature
> >>>> related
> >>>> >>> open PRs; Well, besides a test improvement for the Cordova push
> >>>> plugin -
> >>>> >>> but that will be addressed soon;
> >>>> >>>
> >>>> >>> My question is: Are you guys aware of any features that we need to
> >>>> add to
> >>>> >>> Android, Cordova or iOS, related for push ?
> >>>> >>>
> >>>> >>> Once the Android and iOS bits are 'done', lets make sure we use
> >>>> those
> >>>> >>> latest versions on our Cordova plugin ;-)
> >>>> >>>
> >>>> >>> Thanks!
> >>>> >>> Matthias
> >>>> >>>
> >>>> >>> [1]
> >>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
> >>>> >>> [2]
> >>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
> >>>> >>>
> >>>> >>>
> >>>> >>> --
> >>>> >>> Matthias Wessendorf
> >>>> >>>
> >>>> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>>> >>> sessions: http://www.slideshare.net/mwessendorf
> >>>> >>> twitter: http://twitter.com/mwessendorf
> >>>> >>>
> >>>> >>> _______________________________________________
> >>>> >>> aerogear-dev mailing list
> >>>> >>>
> >>>> >
> >>>> >> aerogear-dev at .jboss
> >>>> >
> >>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>> >>>
> >>>> >>
> >>>> >> _______________________________________________
> >>>> >> aerogear-dev mailing list
> >>>> >
> >>>> >> aerogear-dev at .jboss
> >>>> >
> >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> > --
> >>>> > View this message in context:
> >>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.html
> >>>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
> >>>> > _______________________________________________
> >>>> > aerogear-dev mailing list
> >>>> >
> 
> > aerogear-dev at .jboss
> 
> >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> aerogear-dev mailing list
> >>>>
> 
> > aerogear-dev at .jboss
> 
> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>>
> 
> > aerogear-dev at .jboss
> 
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>>
> 
> > aerogear-dev at .jboss
> 
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >>
> >>
> >> --
> >> 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 .jboss
> 
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> 
> 
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-tp7932p7958.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/20140528/a331f7dd/attachment-0001.html 

From matzew at apache.org  Wed May 28 05:08:09 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 11:08:09 +0200
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile
 Push 1.0.0] Client SDKs for Android, Cordova and iOS)
In-Reply-To: <133BDEC2-A1A6-416F-8A8C-2F4EAF06CB88@redhat.com>
References: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
	<1401198944803-7958.post@n5.nabble.com>
	<CAAg5f2REuLFHShwt0FRc49nqhuNEaQ8+VwXRniighzm29psjyQ@mail.gmail.com>
	<133BDEC2-A1A6-416F-8A8C-2F4EAF06CB88@redhat.com>
Message-ID: <CAAg5f2S0kr8AEQuPgKSSGVkL6Vb4NVAjgBis3uMsEdVmrndFXw@mail.gmail.com>

On Wed, May 28, 2014 at 11:05 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> We could do another release although there are not many changes since the
> last release (0.5.0)
>

+1 to release 0.5.0 soon-ish


-M




>
> Change log:
> updated lib (android)
> Automate plugin testing using grunt-cordova-plugin-jasmine.
> fix a bug with the foreground/isInline flag
> fix bug with android not sending cached message
>
>
> On 27 May,2014, at 15:57 , Matthias Wessendorf <matzew at apache.org> wrote:
>
>
>
>
> On Tue, May 27, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com>wrote:
>
>> Hi Matthias,
>> it would be nice to have a new release with the latest changes, IMO!
>>
>> And since the thread started from Client SDKs :-), it would be nice to
>> have
>> also a new release of aerogear-push-ios-registration, the last tag 0.9.0
>> is
>> pretty old compared to the latest features on master branch.
>>
>
> let's discuss that on the actual thread - not here; I started this mainly
> for the Cordova release
>
>
>>
>> Thanks :-)
>> Andrea
>>
>>
>> Matthias Wessendorf wrote
>> > Hello,
>> >
>> > the latest Android libs are now on master - should we do another
>> release,
>> > this week ?
>> >
>> >
>> > -Matthias
>> >
>> >
>> >
>> > On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf &lt;
>>
>> > matzew@
>>
>> > &gt;wrote:
>> >
>> >> Awesome! Thanks for commenting, guys!
>> >>
>> >> @Cordova: Will test (and merge ;-)) on Monday
>> >>
>> >>
>> >> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit &lt;
>>
>> > edewit@
>>
>> > &gt;wrote:
>> >>
>> >>> Created PR?s for the open issues on Cordova once merged all done :)
>> >>>
>> >>> On 23 May,2014, at 15:18 , Daniel Passos &lt;
>>
>> > daniel@
>>
>> > &gt; wrote:
>> >>>
>> >>> All done in the android land
>> >>>
>> >>> -- Passos
>> >>>
>> >>>
>> >>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych &lt;
>>
>> > corinnekrych@
>>
>> > &gt;wrote:
>> >>>
>> >>>> Indeed we?re all good for iOS push registration lib.
>> >>>> ++
>> >>>> Corinne
>> >>>> On 20 May 2014, at 17:09, Andrea Vibelli &lt;
>>
>> > avibelli@
>>
>> > &gt; wrote:
>> >>>>
>> >>>> > Hi,
>> >>>> > I have reported also in
>> https://issues.jboss.org/browse/AGCORDOVA-5an
>> >>>> old
>> >>>> > issue (
>> >>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html
>> )
>> >>>> > about the google-play-services version shipped inside the cordova
>> >>>> plugin.
>> >>>> >
>> >>>> > Thanks
>> >>>> > Andrea
>> >>>> >
>> >>>> >
>> >>>> > Sebastien Blanc wrote
>> >>>> >> Hi,
>> >>>> >> For the Cordova Push Plugin there is one (trivial) item open that
>> >>>> should
>> >>>> >> be
>> >>>> >> fixed before 1.0.  I created a jira to track it
>> >>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
>> >>>> >
>> >>>> >> matzew@
>> >>>> >
>> >>>> >> &gt;wrote:
>> >>>> >>
>> >>>> >>> Hi,
>> >>>> >>>
>> >>>> >>> as said before (see [1]), this summer we will release the
>> AeroGear
>> >>>> Mobile
>> >>>> >>> Push 1.0.0 to the community.
>> >>>> >>>
>> >>>> >>> I took a look at the related JIRAs (see [2]) and noticed that for
>> >>>> the
>> >>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
>> >>>> >>>
>> >>>> >>> The github repos are also in an OK state :-) there are no feature
>> >>>> related
>> >>>> >>> open PRs; Well, besides a test improvement for the Cordova push
>> >>>> plugin -
>> >>>> >>> but that will be addressed soon;
>> >>>> >>>
>> >>>> >>> My question is: Are you guys aware of any features that we need
>> to
>> >>>> add to
>> >>>> >>> Android, Cordova or iOS, related for push ?
>> >>>> >>>
>> >>>> >>> Once the Android and iOS bits are 'done', lets make sure we use
>> >>>> those
>> >>>> >>> latest versions on our Cordova plugin ;-)
>> >>>> >>>
>> >>>> >>> Thanks!
>> >>>> >>> Matthias
>> >>>> >>>
>> >>>> >>> [1]
>> >>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>> >>>> >>> [2]
>> >>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>> >>>> >>>
>> >>>> >>>
>> >>>> >>> --
>> >>>> >>> Matthias Wessendorf
>> >>>> >>>
>> >>>> >>> blog: http://matthiaswessendorf.wordpress.com/
>> >>>> >>> sessions: http://www.slideshare.net/mwessendorf
>> >>>> >>> twitter: http://twitter.com/mwessendorf
>> >>>> >>>
>> >>>> >>> _______________________________________________
>> >>>> >>> aerogear-dev mailing list
>> >>>> >>>
>> >>>> >
>> >>>> >> aerogear-dev at .jboss
>> >>>> >
>> >>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>> >>>
>> >>>> >>
>> >>>> >> _______________________________________________
>> >>>> >> aerogear-dev mailing list
>> >>>> >
>> >>>> >> aerogear-dev at .jboss
>> >>>> >
>> >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > --
>> >>>> > View this message in context:
>> >>>>
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.html
>> >>>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
>> >>>> > _______________________________________________
>> >>>> > aerogear-dev mailing list
>> >>>> >
>>
>> > aerogear-dev at .jboss
>>
>> >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>>
>> >>>>
>> >>>> _______________________________________________
>> >>>> aerogear-dev mailing list
>> >>>>
>>
>> > aerogear-dev at .jboss
>>
>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>>
>> >>>
>> >>> _______________________________________________
>> >>> aerogear-dev mailing list
>> >>>
>>
>> > aerogear-dev at .jboss
>>
>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> aerogear-dev mailing list
>> >>>
>>
>> > aerogear-dev at .jboss
>>
>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> 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 .jboss
>>
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-tp7932p7958.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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140528/82e18115/attachment.html 

From corinnekrych at gmail.com  Wed May 28 05:14:09 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Wed, 28 May 2014 11:14:09 +0200
Subject: [aerogear-dev] New iOS Push SDK Client Release
In-Reply-To: <1401264508560-7977.post@n5.nabble.com>
References: <1401264508560-7977.post@n5.nabble.com>
Message-ID: <7BB3FB2F-1DAC-4051-B1C0-1B88F9CB4215@gmail.com>

Hello Andrea

you?re rught we missed Framework build + documentation. Let?s release a 0.9.1.
To answer you?re roadmap question, so far we use the general UnifiedPush roadmap [1].
I?ll send a PR to update 0.12.0 with iOS framework bits.

Ok for all?

++
Corinne
[1] http://aerogear.org/docs/planning/roadmaps/UnifiedPush/

On 28 May 2014, at 10:08, Andrea Vibelli <avibelli at redhat.com> wrote:

> Hi all, 
> the latest release of aerogear-push-ios-registration, version 0.9.0, is
> pretty old (more than 2 months ago), and does not contain some useful
> features like the build script for the creation of framework and static
> libs, and the new extended readme with instruction on how to use them.
> 
> Are there any plans for a new release?
> Thanks
> Andrea
> 
> 
> 
> 
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/New-iOS-Push-SDK-Client-Release-tp7977.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 edewit at redhat.com  Wed May 28 05:15:46 2014
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 28 May 2014 11:15:46 +0200
Subject: [aerogear-dev] cordova plugin release
Message-ID: <DDAEA9F3-E106-4697-BC1C-F83A9E130790@redhat.com>

Hi,

As discussed here (http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-td7932.html) we are going to release a new version of the cordova push plugin the new version 0.5.1 most important feature is the updated android libraries. There are also some community bug fixes:

	fix a bug with the foreground/isInline flag
	fix bug with android not sending cached message
	Automate plugin testing using grunt-cordova-plugin-jasmine.

Thank you TadeasKriz and keithdmoore for contributing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140528/64154a97/attachment-0001.html 

From scm.blanc at gmail.com  Wed May 28 05:18:29 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 28 May 2014 11:18:29 +0200
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile
 Push 1.0.0] Client SDKs for Android, Cordova and iOS)
In-Reply-To: <CAAg5f2S0kr8AEQuPgKSSGVkL6Vb4NVAjgBis3uMsEdVmrndFXw@mail.gmail.com>
References: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
	<1401198944803-7958.post@n5.nabble.com>
	<CAAg5f2REuLFHShwt0FRc49nqhuNEaQ8+VwXRniighzm29psjyQ@mail.gmail.com>
	<133BDEC2-A1A6-416F-8A8C-2F4EAF06CB88@redhat.com>
	<CAAg5f2S0kr8AEQuPgKSSGVkL6Vb4NVAjgBis3uMsEdVmrndFXw@mail.gmail.com>
Message-ID: <CAD_dpu3CJuThf75Mo21Rs9535s4Dn5SmDoHCcGfYQFiKsXv5YA@mail.gmail.com>

IMHO would be nice if we could include
https://issues.jboss.org/browse/AGCORDOVA-9 also in this release
 (even maybe  https://issues.jboss.org/browse/AGCORDOVA-8 , I know the
branch exist, just need to be PRed)


On Wed, May 28, 2014 at 11:08 AM, Matthias Wessendorf <matzew at apache.org>wrote:

>
>
>
> On Wed, May 28, 2014 at 11:05 AM, Erik Jan de Wit <edewit at redhat.com>wrote:
>
>> We could do another release although there are not many changes since the
>> last release (0.5.0)
>>
>
> +1 to release 0.5.0 soon-ish
>
>
> -M
>
>
>
>
>>
>> Change log:
>> updated lib (android)
>> Automate plugin testing using grunt-cordova-plugin-jasmine.
>>  fix a bug with the foreground/isInline flag
>> fix bug with android not sending cached message
>>
>>
>> On 27 May,2014, at 15:57 , Matthias Wessendorf <matzew at apache.org> wrote:
>>
>>
>>
>>
>> On Tue, May 27, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com>wrote:
>>
>>> Hi Matthias,
>>> it would be nice to have a new release with the latest changes, IMO!
>>>
>>> And since the thread started from Client SDKs :-), it would be nice to
>>> have
>>> also a new release of aerogear-push-ios-registration, the last tag 0.9.0
>>> is
>>> pretty old compared to the latest features on master branch.
>>>
>>
>> let's discuss that on the actual thread - not here; I started this mainly
>> for the Cordova release
>>
>>
>>>
>>> Thanks :-)
>>> Andrea
>>>
>>>
>>> Matthias Wessendorf wrote
>>> > Hello,
>>> >
>>> > the latest Android libs are now on master - should we do another
>>> release,
>>> > this week ?
>>> >
>>> >
>>> > -Matthias
>>> >
>>> >
>>> >
>>> > On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf &lt;
>>>
>>> > matzew@
>>>
>>> > &gt;wrote:
>>> >
>>> >> Awesome! Thanks for commenting, guys!
>>> >>
>>> >> @Cordova: Will test (and merge ;-)) on Monday
>>> >>
>>> >>
>>> >> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit &lt;
>>>
>>> > edewit@
>>>
>>> > &gt;wrote:
>>> >>
>>> >>> Created PR?s for the open issues on Cordova once merged all done :)
>>> >>>
>>> >>> On 23 May,2014, at 15:18 , Daniel Passos &lt;
>>>
>>> > daniel@
>>>
>>> > &gt; wrote:
>>> >>>
>>> >>> All done in the android land
>>> >>>
>>> >>> -- Passos
>>> >>>
>>> >>>
>>> >>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych &lt;
>>>
>>> > corinnekrych@
>>>
>>> > &gt;wrote:
>>> >>>
>>> >>>> Indeed we?re all good for iOS push registration lib.
>>> >>>> ++
>>> >>>> Corinne
>>> >>>> On 20 May 2014, at 17:09, Andrea Vibelli &lt;
>>>
>>> > avibelli@
>>>
>>> > &gt; wrote:
>>> >>>>
>>> >>>> > Hi,
>>> >>>> > I have reported also in
>>> https://issues.jboss.org/browse/AGCORDOVA-5an
>>> >>>> old
>>> >>>> > issue (
>>> >>>>
>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
>>> >>>> > about the google-play-services version shipped inside the cordova
>>> >>>> plugin.
>>> >>>> >
>>> >>>> > Thanks
>>> >>>> > Andrea
>>> >>>> >
>>> >>>> >
>>> >>>> > Sebastien Blanc wrote
>>> >>>> >> Hi,
>>> >>>> >> For the Cordova Push Plugin there is one (trivial) item open that
>>> >>>> should
>>> >>>> >> be
>>> >>>> >> fixed before 1.0.  I created a jira to track it
>>> >>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
>>> >>>> >>
>>> >>>> >>
>>> >>>> >>
>>> >>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
>>> >>>> >
>>> >>>> >> matzew@
>>> >>>> >
>>> >>>> >> &gt;wrote:
>>> >>>> >>
>>> >>>> >>> Hi,
>>> >>>> >>>
>>> >>>> >>> as said before (see [1]), this summer we will release the
>>> AeroGear
>>> >>>> Mobile
>>> >>>> >>> Push 1.0.0 to the community.
>>> >>>> >>>
>>> >>>> >>> I took a look at the related JIRAs (see [2]) and noticed that
>>> for
>>> >>>> the
>>> >>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
>>> >>>> >>>
>>> >>>> >>> The github repos are also in an OK state :-) there are no
>>> feature
>>> >>>> related
>>> >>>> >>> open PRs; Well, besides a test improvement for the Cordova push
>>> >>>> plugin -
>>> >>>> >>> but that will be addressed soon;
>>> >>>> >>>
>>> >>>> >>> My question is: Are you guys aware of any features that we need
>>> to
>>> >>>> add to
>>> >>>> >>> Android, Cordova or iOS, related for push ?
>>> >>>> >>>
>>> >>>> >>> Once the Android and iOS bits are 'done', lets make sure we use
>>> >>>> those
>>> >>>> >>> latest versions on our Cordova plugin ;-)
>>> >>>> >>>
>>> >>>> >>> Thanks!
>>> >>>> >>> Matthias
>>> >>>> >>>
>>> >>>> >>> [1]
>>> >>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>>> >>>> >>> [2]
>>> >>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>>> >>>> >>>
>>> >>>> >>>
>>> >>>> >>> --
>>> >>>> >>> Matthias Wessendorf
>>> >>>> >>>
>>> >>>> >>> blog: http://matthiaswessendorf.wordpress.com/
>>> >>>> >>> sessions: http://www.slideshare.net/mwessendorf
>>> >>>> >>> twitter: http://twitter.com/mwessendorf
>>> >>>> >>>
>>> >>>> >>> _______________________________________________
>>> >>>> >>> aerogear-dev mailing list
>>> >>>> >>>
>>> >>>> >
>>> >>>> >> aerogear-dev at .jboss
>>> >>>> >
>>> >>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>> >>>
>>> >>>> >>
>>> >>>> >> _______________________________________________
>>> >>>> >> aerogear-dev mailing list
>>> >>>> >
>>> >>>> >> aerogear-dev at .jboss
>>> >>>> >
>>> >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>> >
>>> >>>> >
>>> >>>> >
>>> >>>> >
>>> >>>> >
>>> >>>> > --
>>> >>>> > View this message in context:
>>> >>>>
>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.html
>>> >>>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
>>> >>>> > _______________________________________________
>>> >>>> > aerogear-dev mailing list
>>> >>>> >
>>>
>>> > aerogear-dev at .jboss
>>>
>>> >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>>
>>> >>>>
>>> >>>> _______________________________________________
>>> >>>> aerogear-dev mailing list
>>> >>>>
>>>
>>> > aerogear-dev at .jboss
>>>
>>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> aerogear-dev mailing list
>>> >>>
>>>
>>> > aerogear-dev at .jboss
>>>
>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> aerogear-dev mailing list
>>> >>>
>>>
>>> > aerogear-dev at .jboss
>>>
>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> 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 .jboss
>>>
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-tp7932p7958.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
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140528/9abf049a/attachment.html 

From matzew at apache.org  Wed May 28 05:20:33 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 11:20:33 +0200
Subject: [aerogear-dev] New iOS Push SDK Client Release
In-Reply-To: <7BB3FB2F-1DAC-4051-B1C0-1B88F9CB4215@gmail.com>
References: <1401264508560-7977.post@n5.nabble.com>
	<7BB3FB2F-1DAC-4051-B1C0-1B88F9CB4215@gmail.com>
Message-ID: <CAAg5f2SMwTTDhaQ58VZAGaL1K-ZNpXA3QaQfrQ+Ztbgi=31ptA@mail.gmail.com>

On Wed, May 28, 2014 at 11:14 AM, Corinne Krych <corinnekrych at gmail.com>wrote:

> Hello Andrea
>
> you?re rught we missed Framework build + documentation. Let?s release a
> 0.9.1.
> To answer you?re roadmap question, so far we use the general UnifiedPush
> roadmap [1].
>

which means by summer the push bits should be 1.0.0:
http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html

-M



> I?ll send a PR to update 0.12.0 with iOS framework bits.
>
> Ok for all?
>
> ++
> Corinne
> [1] http://aerogear.org/docs/planning/roadmaps/UnifiedPush/
>
> On 28 May 2014, at 10:08, Andrea Vibelli <avibelli at redhat.com> wrote:
>
> > Hi all,
> > the latest release of aerogear-push-ios-registration, version 0.9.0, is
> > pretty old (more than 2 months ago), and does not contain some useful
> > features like the build script for the creation of framework and static
> > libs, and the new extended readme with instruction on how to use them.
> >
> > Are there any plans for a new release?
> > Thanks
> > Andrea
> >
> >
> >
> >
> > --
> > View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/New-iOS-Push-SDK-Client-Release-tp7977.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/20140528/1f4afe24/attachment-0001.html 

From matzew at apache.org  Wed May 28 05:22:33 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 11:22:33 +0200
Subject: [aerogear-dev] cordova plugin release
In-Reply-To: <DDAEA9F3-E106-4697-BC1C-F83A9E130790@redhat.com>
References: <DDAEA9F3-E106-4697-BC1C-F83A9E130790@redhat.com>
Message-ID: <CAAg5f2RQFJfWZovsndLm0=seVNHQzjv0eBzgfQ5gNt7OaLPhYA@mail.gmail.com>

On Wed, May 28, 2014 at 11:15 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> As discussed here (
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-td7932.html)
> we are going to release a new version of the cordova push plugin the new
> version 0.5.1 most important feature is the updated android libraries.
>

I'd say let's do it as version 0.6.0, since this summer, the push bits
should be 1.0.0:
http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html



>  There are also some community bug fixes:
>
> * fix a bug with the foreground/isInline flag
> <https://github.com/aerogear/aerogear-pushplugin-cordova/commit/9f1766356d93e223f7678f9e53884e17d82a6467>*
> * fix bug with android not sending cached message
> <https://github.com/aerogear/aerogear-pushplugin-cordova/commit/95db7d91610fdf410b0be544b43ef5bbeb63d749>*
> * Automate plugin testing using grunt-cordova-plugin-jasmine.
> <https://github.com/aerogear/aerogear-pushplugin-cordova/commit/c12f287fd40027da68bdb6a062a0ebc37427d6d9>*
>
> Thank you TadeasKriz and keithdmoore for contributing
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140528/06a008d5/attachment.html 

From matzew at apache.org  Wed May 28 05:23:12 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 11:23:12 +0200
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile
 Push 1.0.0] Client SDKs for Android, Cordova and iOS)
In-Reply-To: <CAD_dpu3CJuThf75Mo21Rs9535s4Dn5SmDoHCcGfYQFiKsXv5YA@mail.gmail.com>
References: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
	<1401198944803-7958.post@n5.nabble.com>
	<CAAg5f2REuLFHShwt0FRc49nqhuNEaQ8+VwXRniighzm29psjyQ@mail.gmail.com>
	<133BDEC2-A1A6-416F-8A8C-2F4EAF06CB88@redhat.com>
	<CAAg5f2S0kr8AEQuPgKSSGVkL6Vb4NVAjgBis3uMsEdVmrndFXw@mail.gmail.com>
	<CAD_dpu3CJuThf75Mo21Rs9535s4Dn5SmDoHCcGfYQFiKsXv5YA@mail.gmail.com>
Message-ID: <CAAg5f2RObDN7_RLDoy0qjWQAsOVeTJM2CPc31fiiJzJONQJrCQ@mail.gmail.com>

oh, yeah - good catches!

-Matthias


On Wed, May 28, 2014 at 11:18 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:

> IMHO would be nice if we could include
> https://issues.jboss.org/browse/AGCORDOVA-9 also in this release
>  (even maybe  https://issues.jboss.org/browse/AGCORDOVA-8 , I know the
> branch exist, just need to be PRed)
>
>
> On Wed, May 28, 2014 at 11:08 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>>
>>
>>
>> On Wed, May 28, 2014 at 11:05 AM, Erik Jan de Wit <edewit at redhat.com>wrote:
>>
>>> We could do another release although there are not many changes since
>>> the last release (0.5.0)
>>>
>>
>> +1 to release 0.5.0 soon-ish
>>
>>
>> -M
>>
>>
>>
>>
>>>
>>> Change log:
>>> updated lib (android)
>>> Automate plugin testing using grunt-cordova-plugin-jasmine.
>>>  fix a bug with the foreground/isInline flag
>>> fix bug with android not sending cached message
>>>
>>>
>>> On 27 May,2014, at 15:57 , Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>
>>>
>>>
>>> On Tue, May 27, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com>wrote:
>>>
>>>> Hi Matthias,
>>>> it would be nice to have a new release with the latest changes, IMO!
>>>>
>>>> And since the thread started from Client SDKs :-), it would be nice to
>>>> have
>>>> also a new release of aerogear-push-ios-registration, the last tag
>>>> 0.9.0 is
>>>> pretty old compared to the latest features on master branch.
>>>>
>>>
>>> let's discuss that on the actual thread - not here; I started this
>>> mainly for the Cordova release
>>>
>>>
>>>>
>>>> Thanks :-)
>>>> Andrea
>>>>
>>>>
>>>> Matthias Wessendorf wrote
>>>> > Hello,
>>>> >
>>>> > the latest Android libs are now on master - should we do another
>>>> release,
>>>> > this week ?
>>>> >
>>>> >
>>>> > -Matthias
>>>> >
>>>> >
>>>> >
>>>> > On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf &lt;
>>>>
>>>> > matzew@
>>>>
>>>> > &gt;wrote:
>>>> >
>>>> >> Awesome! Thanks for commenting, guys!
>>>> >>
>>>> >> @Cordova: Will test (and merge ;-)) on Monday
>>>> >>
>>>> >>
>>>> >> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit &lt;
>>>>
>>>> > edewit@
>>>>
>>>> > &gt;wrote:
>>>> >>
>>>> >>> Created PR?s for the open issues on Cordova once merged all done :)
>>>> >>>
>>>> >>> On 23 May,2014, at 15:18 , Daniel Passos &lt;
>>>>
>>>> > daniel@
>>>>
>>>> > &gt; wrote:
>>>> >>>
>>>> >>> All done in the android land
>>>> >>>
>>>> >>> -- Passos
>>>> >>>
>>>> >>>
>>>> >>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych &lt;
>>>>
>>>> > corinnekrych@
>>>>
>>>> > &gt;wrote:
>>>> >>>
>>>> >>>> Indeed we?re all good for iOS push registration lib.
>>>> >>>> ++
>>>> >>>> Corinne
>>>> >>>> On 20 May 2014, at 17:09, Andrea Vibelli &lt;
>>>>
>>>> > avibelli@
>>>>
>>>> > &gt; wrote:
>>>> >>>>
>>>> >>>> > Hi,
>>>> >>>> > I have reported also in
>>>> https://issues.jboss.org/browse/AGCORDOVA-5an
>>>> >>>> old
>>>> >>>> > issue (
>>>> >>>>
>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
>>>> >>>> > about the google-play-services version shipped inside the cordova
>>>> >>>> plugin.
>>>> >>>> >
>>>> >>>> > Thanks
>>>> >>>> > Andrea
>>>> >>>> >
>>>> >>>> >
>>>> >>>> > Sebastien Blanc wrote
>>>> >>>> >> Hi,
>>>> >>>> >> For the Cordova Push Plugin there is one (trivial) item open
>>>> that
>>>> >>>> should
>>>> >>>> >> be
>>>> >>>> >> fixed before 1.0.  I created a jira to track it
>>>> >>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
>>>> >>>> >>
>>>> >>>> >>
>>>> >>>> >>
>>>> >>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
>>>> >>>> >
>>>> >>>> >> matzew@
>>>> >>>> >
>>>> >>>> >> &gt;wrote:
>>>> >>>> >>
>>>> >>>> >>> Hi,
>>>> >>>> >>>
>>>> >>>> >>> as said before (see [1]), this summer we will release the
>>>> AeroGear
>>>> >>>> Mobile
>>>> >>>> >>> Push 1.0.0 to the community.
>>>> >>>> >>>
>>>> >>>> >>> I took a look at the related JIRAs (see [2]) and noticed that
>>>> for
>>>> >>>> the
>>>> >>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
>>>> >>>> >>>
>>>> >>>> >>> The github repos are also in an OK state :-) there are no
>>>> feature
>>>> >>>> related
>>>> >>>> >>> open PRs; Well, besides a test improvement for the Cordova push
>>>> >>>> plugin -
>>>> >>>> >>> but that will be addressed soon;
>>>> >>>> >>>
>>>> >>>> >>> My question is: Are you guys aware of any features that we
>>>> need to
>>>> >>>> add to
>>>> >>>> >>> Android, Cordova or iOS, related for push ?
>>>> >>>> >>>
>>>> >>>> >>> Once the Android and iOS bits are 'done', lets make sure we use
>>>> >>>> those
>>>> >>>> >>> latest versions on our Cordova plugin ;-)
>>>> >>>> >>>
>>>> >>>> >>> Thanks!
>>>> >>>> >>> Matthias
>>>> >>>> >>>
>>>> >>>> >>> [1]
>>>> >>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>>>> >>>> >>> [2]
>>>> >>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>>>> >>>> >>>
>>>> >>>> >>>
>>>> >>>> >>> --
>>>> >>>> >>> Matthias Wessendorf
>>>> >>>> >>>
>>>> >>>> >>> blog: http://matthiaswessendorf.wordpress.com/
>>>> >>>> >>> sessions: http://www.slideshare.net/mwessendorf
>>>> >>>> >>> twitter: http://twitter.com/mwessendorf
>>>> >>>> >>>
>>>> >>>> >>> _______________________________________________
>>>> >>>> >>> aerogear-dev mailing list
>>>> >>>> >>>
>>>> >>>> >
>>>> >>>> >> aerogear-dev at .jboss
>>>> >>>> >
>>>> >>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >>>> >>>
>>>> >>>> >>
>>>> >>>> >> _______________________________________________
>>>> >>>> >> aerogear-dev mailing list
>>>> >>>> >
>>>> >>>> >> aerogear-dev at .jboss
>>>> >>>> >
>>>> >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >>>> >
>>>> >>>> >
>>>> >>>> >
>>>> >>>> >
>>>> >>>> >
>>>> >>>> > --
>>>> >>>> > View this message in context:
>>>> >>>>
>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.html
>>>> >>>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>> >>>> > _______________________________________________
>>>> >>>> > aerogear-dev mailing list
>>>> >>>> >
>>>>
>>>> > aerogear-dev at .jboss
>>>>
>>>> >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >>>>
>>>> >>>>
>>>> >>>> _______________________________________________
>>>> >>>> aerogear-dev mailing list
>>>> >>>>
>>>>
>>>> > aerogear-dev at .jboss
>>>>
>>>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >>>>
>>>> >>>
>>>> >>> _______________________________________________
>>>> >>> aerogear-dev mailing list
>>>> >>>
>>>>
>>>> > aerogear-dev at .jboss
>>>>
>>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> _______________________________________________
>>>> >>> aerogear-dev mailing list
>>>> >>>
>>>>
>>>> > aerogear-dev at .jboss
>>>>
>>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> >>>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> 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 .jboss
>>>>
>>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-tp7932p7958.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
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140528/782612e7/attachment-0001.html 

From cvasilak at gmail.com  Wed May 28 05:23:22 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Wed, 28 May 2014 12:23:22 +0300
Subject: [aerogear-dev] New iOS Push SDK Client Release
In-Reply-To: <7BB3FB2F-1DAC-4051-B1C0-1B88F9CB4215@gmail.com>
References: <1401264508560-7977.post@n5.nabble.com>
	<7BB3FB2F-1DAC-4051-B1C0-1B88F9CB4215@gmail.com>
Message-ID: <D86E8BE1-766D-4788-ADEC-40D95F01ACD3@gmail.com>


On May 28, 2014, at 12:14 PM, Corinne Krych <corinnekrych at gmail.com> wrote:

> Hello Andrea
> 
> you?re rught we missed Framework build + documentation. Let?s release a 0.9.1.

since the changes from the previous release is the framework build and we are already using it in our quick starts with no issues, I am +1 to release a new version 0.9.1 ASAP and can happen till the end of the week.

Any objections?

-
Christos



> To answer you?re roadmap question, so far we use the general UnifiedPush roadmap [1].
> I?ll send a PR to update 0.12.0 with iOS framework bits.
> 
> Ok for all?
> 
> ++
> Corinne
> [1] http://aerogear.org/docs/planning/roadmaps/UnifiedPush/
> 
> On 28 May 2014, at 10:08, Andrea Vibelli <avibelli at redhat.com> wrote:
> 
>> Hi all, 
>> the latest release of aerogear-push-ios-registration, version 0.9.0, is
>> pretty old (more than 2 months ago), and does not contain some useful
>> features like the build script for the creation of framework and static
>> libs, and the new extended readme with instruction on how to use them.
>> 
>> Are there any plans for a new release?
>> Thanks
>> Andrea
>> 
>> 
>> 
>> 
>> --
>> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/New-iOS-Push-SDK-Client-Release-tp7977.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



From matzew at apache.org  Wed May 28 05:26:05 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 11:26:05 +0200
Subject: [aerogear-dev] New iOS Push SDK Client Release
In-Reply-To: <D86E8BE1-766D-4788-ADEC-40D95F01ACD3@gmail.com>
References: <1401264508560-7977.post@n5.nabble.com>
	<7BB3FB2F-1DAC-4051-B1C0-1B88F9CB4215@gmail.com>
	<D86E8BE1-766D-4788-ADEC-40D95F01ACD3@gmail.com>
Message-ID: <CAAg5f2QoxYcagXizXLA__pEJeXhUozT589nOMMMwQGKELwWmUA@mail.gmail.com>

On Wed, May 28, 2014 at 11:23 AM, Christos Vasilakis <cvasilak at gmail.com>wrote:

>
> On May 28, 2014, at 12:14 PM, Corinne Krych <corinnekrych at gmail.com>
> wrote:
>
> > Hello Andrea
> >
> > you?re rught we missed Framework build + documentation. Let?s release a
> 0.9.1.
>
> since the changes from the previous release is the framework build and we
> are already using it in our quick starts with no issues, I am +1 to release
> a new version 0.9.1 ASAP and can happen till the end of the week.
>

oh, cool! that's perfect


>
> Any objections?
>
> -
> Christos
>
>
>
> > To answer you?re roadmap question, so far we use the general UnifiedPush
> roadmap [1].
> > I?ll send a PR to update 0.12.0 with iOS framework bits.
> >
> > Ok for all?
> >
> > ++
> > Corinne
> > [1] http://aerogear.org/docs/planning/roadmaps/UnifiedPush/
> >
> > On 28 May 2014, at 10:08, Andrea Vibelli <avibelli at redhat.com> wrote:
> >
> >> Hi all,
> >> the latest release of aerogear-push-ios-registration, version 0.9.0, is
> >> pretty old (more than 2 months ago), and does not contain some useful
> >> features like the build script for the creation of framework and static
> >> libs, and the new extended readme with instruction on how to use them.
> >>
> >> Are there any plans for a new release?
> >> Thanks
> >> Andrea
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/New-iOS-Push-SDK-Client-Release-tp7977.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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140528/a824bff5/attachment.html 

From scm.blanc at gmail.com  Wed May 28 05:26:49 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 28 May 2014 11:26:49 +0200
Subject: [aerogear-dev] cordova plugin release
In-Reply-To: <CAAg5f2RQFJfWZovsndLm0=seVNHQzjv0eBzgfQ5gNt7OaLPhYA@mail.gmail.com>
References: <DDAEA9F3-E106-4697-BC1C-F83A9E130790@redhat.com>
	<CAAg5f2RQFJfWZovsndLm0=seVNHQzjv0eBzgfQ5gNt7OaLPhYA@mail.gmail.com>
Message-ID: <CAD_dpu1y=RAZ1hCt_WfhdfqSGgZBng8b6DrvXjMcQaCAE3XMmQ@mail.gmail.com>

Let me just repaste my answer from the other thread ;)
"
IMHO would be nice if we could include
https://issues.jboss.org/browse/AGCORDOVA-9 also in this release
 (even maybe  https://issues.jboss.org/browse/AGCORDOVA-8 , I know the
branch exist, just need to be PRed)
"



On Wed, May 28, 2014 at 11:22 AM, Matthias Wessendorf <matzew at apache.org>wrote:

>
>
>
> On Wed, May 28, 2014 at 11:15 AM, Erik Jan de Wit <edewit at redhat.com>wrote:
>
>> Hi,
>>
>> As discussed here (
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-td7932.html)
>> we are going to release a new version of the cordova push plugin the new
>> version 0.5.1 most important feature is the updated android libraries.
>>
>
> I'd say let's do it as version 0.6.0, since this summer, the push bits
> should be 1.0.0:
> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>
>
>
>>  There are also some community bug fixes:
>>
>> * fix a bug with the foreground/isInline flag
>> <https://github.com/aerogear/aerogear-pushplugin-cordova/commit/9f1766356d93e223f7678f9e53884e17d82a6467>*
>> * fix bug with android not sending cached message
>> <https://github.com/aerogear/aerogear-pushplugin-cordova/commit/95db7d91610fdf410b0be544b43ef5bbeb63d749>*
>> * Automate plugin testing using grunt-cordova-plugin-jasmine.
>> <https://github.com/aerogear/aerogear-pushplugin-cordova/commit/c12f287fd40027da68bdb6a062a0ebc37427d6d9>*
>>
>> Thank you TadeasKriz and keithdmoore for contributing
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140528/2748d82c/attachment.html 

From matzew at apache.org  Wed May 28 05:27:04 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 11:27:04 +0200
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile
 Push 1.0.0] Client SDKs for Android, Cordova and iOS)
In-Reply-To: <CAAg5f2RObDN7_RLDoy0qjWQAsOVeTJM2CPc31fiiJzJONQJrCQ@mail.gmail.com>
References: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
	<1401198944803-7958.post@n5.nabble.com>
	<CAAg5f2REuLFHShwt0FRc49nqhuNEaQ8+VwXRniighzm29psjyQ@mail.gmail.com>
	<133BDEC2-A1A6-416F-8A8C-2F4EAF06CB88@redhat.com>
	<CAAg5f2S0kr8AEQuPgKSSGVkL6Vb4NVAjgBis3uMsEdVmrndFXw@mail.gmail.com>
	<CAD_dpu3CJuThf75Mo21Rs9535s4Dn5SmDoHCcGfYQFiKsXv5YA@mail.gmail.com>
	<CAAg5f2RObDN7_RLDoy0qjWQAsOVeTJM2CPc31fiiJzJONQJrCQ@mail.gmail.com>
Message-ID: <CAAg5f2R14-BcnR08a7YrTrMxh+DU8A9j42PRBs2EDAZcMABD=w@mail.gmail.com>

and... perhaps we can include the next iOS deliverable as well:
http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007893.html

-M


On Wed, May 28, 2014 at 11:23 AM, Matthias Wessendorf <matzew at apache.org>wrote:

> oh, yeah - good catches!
>
> -Matthias
>
>
> On Wed, May 28, 2014 at 11:18 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
>
>> IMHO would be nice if we could include
>> https://issues.jboss.org/browse/AGCORDOVA-9 also in this release
>>  (even maybe  https://issues.jboss.org/browse/AGCORDOVA-8 , I know the
>> branch exist, just need to be PRed)
>>
>>
>> On Wed, May 28, 2014 at 11:08 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>>
>>>
>>>
>>>
>>> On Wed, May 28, 2014 at 11:05 AM, Erik Jan de Wit <edewit at redhat.com>wrote:
>>>
>>>> We could do another release although there are not many changes since
>>>> the last release (0.5.0)
>>>>
>>>
>>> +1 to release 0.5.0 soon-ish
>>>
>>>
>>> -M
>>>
>>>
>>>
>>>
>>>>
>>>> Change log:
>>>> updated lib (android)
>>>> Automate plugin testing using grunt-cordova-plugin-jasmine.
>>>>  fix a bug with the foreground/isInline flag
>>>> fix bug with android not sending cached message
>>>>
>>>>
>>>> On 27 May,2014, at 15:57 , Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, May 27, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com>wrote:
>>>>
>>>>> Hi Matthias,
>>>>> it would be nice to have a new release with the latest changes, IMO!
>>>>>
>>>>> And since the thread started from Client SDKs :-), it would be nice to
>>>>> have
>>>>> also a new release of aerogear-push-ios-registration, the last tag
>>>>> 0.9.0 is
>>>>> pretty old compared to the latest features on master branch.
>>>>>
>>>>
>>>> let's discuss that on the actual thread - not here; I started this
>>>> mainly for the Cordova release
>>>>
>>>>
>>>>>
>>>>> Thanks :-)
>>>>> Andrea
>>>>>
>>>>>
>>>>> Matthias Wessendorf wrote
>>>>> > Hello,
>>>>> >
>>>>> > the latest Android libs are now on master - should we do another
>>>>> release,
>>>>> > this week ?
>>>>> >
>>>>> >
>>>>> > -Matthias
>>>>> >
>>>>> >
>>>>> >
>>>>> > On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf &lt;
>>>>>
>>>>> > matzew@
>>>>>
>>>>> > &gt;wrote:
>>>>> >
>>>>> >> Awesome! Thanks for commenting, guys!
>>>>> >>
>>>>> >> @Cordova: Will test (and merge ;-)) on Monday
>>>>> >>
>>>>> >>
>>>>> >> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit &lt;
>>>>>
>>>>> > edewit@
>>>>>
>>>>> > &gt;wrote:
>>>>> >>
>>>>> >>> Created PR?s for the open issues on Cordova once merged all done :)
>>>>> >>>
>>>>> >>> On 23 May,2014, at 15:18 , Daniel Passos &lt;
>>>>>
>>>>> > daniel@
>>>>>
>>>>> > &gt; wrote:
>>>>> >>>
>>>>> >>> All done in the android land
>>>>> >>>
>>>>> >>> -- Passos
>>>>> >>>
>>>>> >>>
>>>>> >>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych &lt;
>>>>>
>>>>> > corinnekrych@
>>>>>
>>>>> > &gt;wrote:
>>>>> >>>
>>>>> >>>> Indeed we?re all good for iOS push registration lib.
>>>>> >>>> ++
>>>>> >>>> Corinne
>>>>> >>>> On 20 May 2014, at 17:09, Andrea Vibelli &lt;
>>>>>
>>>>> > avibelli@
>>>>>
>>>>> > &gt; wrote:
>>>>> >>>>
>>>>> >>>> > Hi,
>>>>> >>>> > I have reported also in
>>>>> https://issues.jboss.org/browse/AGCORDOVA-5an
>>>>> >>>> old
>>>>> >>>> > issue (
>>>>> >>>>
>>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
>>>>> >>>> > about the google-play-services version shipped inside the
>>>>> cordova
>>>>> >>>> plugin.
>>>>> >>>> >
>>>>> >>>> > Thanks
>>>>> >>>> > Andrea
>>>>> >>>> >
>>>>> >>>> >
>>>>> >>>> > Sebastien Blanc wrote
>>>>> >>>> >> Hi,
>>>>> >>>> >> For the Cordova Push Plugin there is one (trivial) item open
>>>>> that
>>>>> >>>> should
>>>>> >>>> >> be
>>>>> >>>> >> fixed before 1.0.  I created a jira to track it
>>>>> >>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
>>>>> >>>> >>
>>>>> >>>> >>
>>>>> >>>> >>
>>>>> >>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
>>>>> >>>> >
>>>>> >>>> >> matzew@
>>>>> >>>> >
>>>>> >>>> >> &gt;wrote:
>>>>> >>>> >>
>>>>> >>>> >>> Hi,
>>>>> >>>> >>>
>>>>> >>>> >>> as said before (see [1]), this summer we will release the
>>>>> AeroGear
>>>>> >>>> Mobile
>>>>> >>>> >>> Push 1.0.0 to the community.
>>>>> >>>> >>>
>>>>> >>>> >>> I took a look at the related JIRAs (see [2]) and noticed that
>>>>> for
>>>>> >>>> the
>>>>> >>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
>>>>> >>>> >>>
>>>>> >>>> >>> The github repos are also in an OK state :-) there are no
>>>>> feature
>>>>> >>>> related
>>>>> >>>> >>> open PRs; Well, besides a test improvement for the Cordova
>>>>> push
>>>>> >>>> plugin -
>>>>> >>>> >>> but that will be addressed soon;
>>>>> >>>> >>>
>>>>> >>>> >>> My question is: Are you guys aware of any features that we
>>>>> need to
>>>>> >>>> add to
>>>>> >>>> >>> Android, Cordova or iOS, related for push ?
>>>>> >>>> >>>
>>>>> >>>> >>> Once the Android and iOS bits are 'done', lets make sure we
>>>>> use
>>>>> >>>> those
>>>>> >>>> >>> latest versions on our Cordova plugin ;-)
>>>>> >>>> >>>
>>>>> >>>> >>> Thanks!
>>>>> >>>> >>> Matthias
>>>>> >>>> >>>
>>>>> >>>> >>> [1]
>>>>> >>>>
>>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
>>>>> >>>> >>> [2]
>>>>> >>>>
>>>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
>>>>> >>>> >>>
>>>>> >>>> >>>
>>>>> >>>> >>> --
>>>>> >>>> >>> Matthias Wessendorf
>>>>> >>>> >>>
>>>>> >>>> >>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> >>>> >>> sessions: http://www.slideshare.net/mwessendorf
>>>>> >>>> >>> twitter: http://twitter.com/mwessendorf
>>>>> >>>> >>>
>>>>> >>>> >>> _______________________________________________
>>>>> >>>> >>> aerogear-dev mailing list
>>>>> >>>> >>>
>>>>> >>>> >
>>>>> >>>> >> aerogear-dev at .jboss
>>>>> >>>> >
>>>>> >>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> >>>> >>>
>>>>> >>>> >>
>>>>> >>>> >> _______________________________________________
>>>>> >>>> >> aerogear-dev mailing list
>>>>> >>>> >
>>>>> >>>> >> aerogear-dev at .jboss
>>>>> >>>> >
>>>>> >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> >>>> >
>>>>> >>>> >
>>>>> >>>> >
>>>>> >>>> >
>>>>> >>>> >
>>>>> >>>> > --
>>>>> >>>> > View this message in context:
>>>>> >>>>
>>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.html
>>>>> >>>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
>>>>> >>>> > _______________________________________________
>>>>> >>>> > aerogear-dev mailing list
>>>>> >>>> >
>>>>>
>>>>> > aerogear-dev at .jboss
>>>>>
>>>>> >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> _______________________________________________
>>>>> >>>> aerogear-dev mailing list
>>>>> >>>>
>>>>>
>>>>> > aerogear-dev at .jboss
>>>>>
>>>>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> >>>>
>>>>> >>>
>>>>> >>> _______________________________________________
>>>>> >>> aerogear-dev mailing list
>>>>> >>>
>>>>>
>>>>> > aerogear-dev at .jboss
>>>>>
>>>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> _______________________________________________
>>>>> >>> aerogear-dev mailing list
>>>>> >>>
>>>>>
>>>>> > aerogear-dev at .jboss
>>>>>
>>>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>> >>>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> --
>>>>> >> 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 .jboss
>>>>>
>>>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-tp7932p7958.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
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140528/5235a808/attachment-0001.html 

From bruno at abstractj.org  Wed May 28 05:34:44 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 28 May 2014 06:34:44 -0300
Subject: [aerogear-dev] New Cordova (Push) release? (was: Re: [Mobile
 Push 1.0.0] Client SDKs for Android, Cordova and iOS)
In-Reply-To: <CAAg5f2R14-BcnR08a7YrTrMxh+DU8A9j42PRBs2EDAZcMABD=w@mail.gmail.com>
References: <CAAg5f2Qmct4DtBtOVKaTsDTq-2U0=oTXTq1F8usncn+bUOCL9Q@mail.gmail.com>
	<1401198944803-7958.post@n5.nabble.com>
	<CAAg5f2REuLFHShwt0FRc49nqhuNEaQ8+VwXRniighzm29psjyQ@mail.gmail.com>
	<133BDEC2-A1A6-416F-8A8C-2F4EAF06CB88@redhat.com>
	<CAAg5f2S0kr8AEQuPgKSSGVkL6Vb4NVAjgBis3uMsEdVmrndFXw@mail.gmail.com>
	<CAD_dpu3CJuThf75Mo21Rs9535s4Dn5SmDoHCcGfYQFiKsXv5YA@mail.gmail.com>
	<CAAg5f2RObDN7_RLDoy0qjWQAsOVeTJM2CPc31fiiJzJONQJrCQ@mail.gmail.com>
	<CAAg5f2R14-BcnR08a7YrTrMxh+DU8A9j42PRBs2EDAZcMABD=w@mail.gmail.com>
Message-ID: <20140528093444.GD76726@abstractj.org>

Maybe also include the planned release here:
http://aerogear.org/docs/planning/roadmaps/AeroGearCordova/ ?

On 2014-05-28, Matthias Wessendorf wrote:
> and... perhaps we can include the next iOS deliverable as well:
> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007893.html
>
> -M
>
>
> On Wed, May 28, 2014 at 11:23 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>
> > oh, yeah - good catches!
> >
> > -Matthias
> >
> >
> > On Wed, May 28, 2014 at 11:18 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
> >
> >> IMHO would be nice if we could include
> >> https://issues.jboss.org/browse/AGCORDOVA-9 also in this release
> >>  (even maybe  https://issues.jboss.org/browse/AGCORDOVA-8 , I know the
> >> branch exist, just need to be PRed)
> >>
> >>
> >> On Wed, May 28, 2014 at 11:08 AM, Matthias Wessendorf <matzew at apache.org>wrote:
> >>
> >>>
> >>>
> >>>
> >>> On Wed, May 28, 2014 at 11:05 AM, Erik Jan de Wit <edewit at redhat.com>wrote:
> >>>
> >>>> We could do another release although there are not many changes since
> >>>> the last release (0.5.0)
> >>>>
> >>>
> >>> +1 to release 0.5.0 soon-ish
> >>>
> >>>
> >>> -M
> >>>
> >>>
> >>>
> >>>
> >>>>
> >>>> Change log:
> >>>> updated lib (android)
> >>>> Automate plugin testing using grunt-cordova-plugin-jasmine.
> >>>>  fix a bug with the foreground/isInline flag
> >>>> fix bug with android not sending cached message
> >>>>
> >>>>
> >>>> On 27 May,2014, at 15:57 , Matthias Wessendorf <matzew at apache.org>
> >>>> wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Tue, May 27, 2014 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com>wrote:
> >>>>
> >>>>> Hi Matthias,
> >>>>> it would be nice to have a new release with the latest changes, IMO!
> >>>>>
> >>>>> And since the thread started from Client SDKs :-), it would be nice to
> >>>>> have
> >>>>> also a new release of aerogear-push-ios-registration, the last tag
> >>>>> 0.9.0 is
> >>>>> pretty old compared to the latest features on master branch.
> >>>>>
> >>>>
> >>>> let's discuss that on the actual thread - not here; I started this
> >>>> mainly for the Cordova release
> >>>>
> >>>>
> >>>>>
> >>>>> Thanks :-)
> >>>>> Andrea
> >>>>>
> >>>>>
> >>>>> Matthias Wessendorf wrote
> >>>>> > Hello,
> >>>>> >
> >>>>> > the latest Android libs are now on master - should we do another
> >>>>> release,
> >>>>> > this week ?
> >>>>> >
> >>>>> >
> >>>>> > -Matthias
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > On Sun, May 25, 2014 at 1:40 PM, Matthias Wessendorf &lt;
> >>>>>
> >>>>> > matzew@
> >>>>>
> >>>>> > &gt;wrote:
> >>>>> >
> >>>>> >> Awesome! Thanks for commenting, guys!
> >>>>> >>
> >>>>> >> @Cordova: Will test (and merge ;-)) on Monday
> >>>>> >>
> >>>>> >>
> >>>>> >> On Fri, May 23, 2014 at 4:45 PM, Erik Jan de Wit &lt;
> >>>>>
> >>>>> > edewit@
> >>>>>
> >>>>> > &gt;wrote:
> >>>>> >>
> >>>>> >>> Created PR?s for the open issues on Cordova once merged all done :)
> >>>>> >>>
> >>>>> >>> On 23 May,2014, at 15:18 , Daniel Passos &lt;
> >>>>>
> >>>>> > daniel@
> >>>>>
> >>>>> > &gt; wrote:
> >>>>> >>>
> >>>>> >>> All done in the android land
> >>>>> >>>
> >>>>> >>> -- Passos
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> On Thu, May 22, 2014 at 10:49 AM, Corinne Krych &lt;
> >>>>>
> >>>>> > corinnekrych@
> >>>>>
> >>>>> > &gt;wrote:
> >>>>> >>>
> >>>>> >>>> Indeed we?re all good for iOS push registration lib.
> >>>>> >>>> ++
> >>>>> >>>> Corinne
> >>>>> >>>> On 20 May 2014, at 17:09, Andrea Vibelli &lt;
> >>>>>
> >>>>> > avibelli@
> >>>>>
> >>>>> > &gt; wrote:
> >>>>> >>>>
> >>>>> >>>> > Hi,
> >>>>> >>>> > I have reported also in
> >>>>> https://issues.jboss.org/browse/AGCORDOVA-5an
> >>>>> >>>> old
> >>>>> >>>> > issue (
> >>>>> >>>>
> >>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-April/007530.html)
> >>>>> >>>> > about the google-play-services version shipped inside the
> >>>>> cordova
> >>>>> >>>> plugin.
> >>>>> >>>> >
> >>>>> >>>> > Thanks
> >>>>> >>>> > Andrea
> >>>>> >>>> >
> >>>>> >>>> >
> >>>>> >>>> > Sebastien Blanc wrote
> >>>>> >>>> >> Hi,
> >>>>> >>>> >> For the Cordova Push Plugin there is one (trivial) item open
> >>>>> that
> >>>>> >>>> should
> >>>>> >>>> >> be
> >>>>> >>>> >> fixed before 1.0.  I created a jira to track it
> >>>>> >>>> >> https://issues.jboss.org/browse/AGCORDOVA-4
> >>>>> >>>> >>
> >>>>> >>>> >>
> >>>>> >>>> >>
> >>>>> >>>> >> On Mon, May 19, 2014 at 2:05 PM, Matthias Wessendorf &lt;
> >>>>> >>>> >
> >>>>> >>>> >> matzew@
> >>>>> >>>> >
> >>>>> >>>> >> &gt;wrote:
> >>>>> >>>> >>
> >>>>> >>>> >>> Hi,
> >>>>> >>>> >>>
> >>>>> >>>> >>> as said before (see [1]), this summer we will release the
> >>>>> AeroGear
> >>>>> >>>> Mobile
> >>>>> >>>> >>> Push 1.0.0 to the community.
> >>>>> >>>> >>>
> >>>>> >>>> >>> I took a look at the related JIRAs (see [2]) and noticed that
> >>>>> for
> >>>>> >>>> the
> >>>>> >>>> >>> mobile client SDKs there are no outstanding tickets. Yay!
> >>>>> >>>> >>>
> >>>>> >>>> >>> The github repos are also in an OK state :-) there are no
> >>>>> feature
> >>>>> >>>> related
> >>>>> >>>> >>> open PRs; Well, besides a test improvement for the Cordova
> >>>>> push
> >>>>> >>>> plugin -
> >>>>> >>>> >>> but that will be addressed soon;
> >>>>> >>>> >>>
> >>>>> >>>> >>> My question is: Are you guys aware of any features that we
> >>>>> need to
> >>>>> >>>> add to
> >>>>> >>>> >>> Android, Cordova or iOS, related for push ?
> >>>>> >>>> >>>
> >>>>> >>>> >>> Once the Android and iOS bits are 'done', lets make sure we
> >>>>> use
> >>>>> >>>> those
> >>>>> >>>> >>> latest versions on our Cordova plugin ;-)
> >>>>> >>>> >>>
> >>>>> >>>> >>> Thanks!
> >>>>> >>>> >>> Matthias
> >>>>> >>>> >>>
> >>>>> >>>> >>> [1]
> >>>>> >>>>
> >>>>> http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007675.html
> >>>>> >>>> >>> [2]
> >>>>> >>>>
> >>>>> https://issues.jboss.org/issues/?jql=labels%20%3D%20MobilePush-1.0
> >>>>> >>>> >>>
> >>>>> >>>> >>>
> >>>>> >>>> >>> --
> >>>>> >>>> >>> Matthias Wessendorf
> >>>>> >>>> >>>
> >>>>> >>>> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>>>> >>>> >>> sessions: http://www.slideshare.net/mwessendorf
> >>>>> >>>> >>> twitter: http://twitter.com/mwessendorf
> >>>>> >>>> >>>
> >>>>> >>>> >>> _______________________________________________
> >>>>> >>>> >>> aerogear-dev mailing list
> >>>>> >>>> >>>
> >>>>> >>>> >
> >>>>> >>>> >> aerogear-dev at .jboss
> >>>>> >>>> >
> >>>>> >>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>> >>>> >>>
> >>>>> >>>> >>
> >>>>> >>>> >> _______________________________________________
> >>>>> >>>> >> aerogear-dev mailing list
> >>>>> >>>> >
> >>>>> >>>> >> aerogear-dev at .jboss
> >>>>> >>>> >
> >>>>> >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>> >>>> >
> >>>>> >>>> >
> >>>>> >>>> >
> >>>>> >>>> >
> >>>>> >>>> >
> >>>>> >>>> > --
> >>>>> >>>> > View this message in context:
> >>>>> >>>>
> >>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-iOS-tp7839p7865.html
> >>>>> >>>> > Sent from the aerogear-dev mailing list archive at Nabble.com.
> >>>>> >>>> > _______________________________________________
> >>>>> >>>> > aerogear-dev mailing list
> >>>>> >>>> >
> >>>>>
> >>>>> > aerogear-dev at .jboss
> >>>>>
> >>>>> >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>> >>>>
> >>>>> >>>>
> >>>>> >>>> _______________________________________________
> >>>>> >>>> aerogear-dev mailing list
> >>>>> >>>>
> >>>>>
> >>>>> > aerogear-dev at .jboss
> >>>>>
> >>>>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>> >>>>
> >>>>> >>>
> >>>>> >>> _______________________________________________
> >>>>> >>> aerogear-dev mailing list
> >>>>> >>>
> >>>>>
> >>>>> > aerogear-dev at .jboss
> >>>>>
> >>>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> _______________________________________________
> >>>>> >>> aerogear-dev mailing list
> >>>>> >>>
> >>>>>
> >>>>> > aerogear-dev at .jboss
> >>>>>
> >>>>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>> >>>
> >>>>> >>
> >>>>> >>
> >>>>> >>
> >>>>> >> --
> >>>>> >> 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 .jboss
> >>>>>
> >>>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> View this message in context:
> >>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-New-Cordova-Push-release-was-Re-Mobile-Push-1-0-0-Client-SDKs-for-Android-Cordova-and-i-tp7932p7958.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
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.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


--

abstractj

From bruno at abstractj.org  Wed May 28 05:38:11 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Wed, 28 May 2014 06:38:11 -0300
Subject: [aerogear-dev] New iOS Push SDK Client Release
In-Reply-To: <D86E8BE1-766D-4788-ADEC-40D95F01ACD3@gmail.com>
References: <1401264508560-7977.post@n5.nabble.com>
	<7BB3FB2F-1DAC-4051-B1C0-1B88F9CB4215@gmail.com>
	<D86E8BE1-766D-4788-ADEC-40D95F01ACD3@gmail.com>
Message-ID: <20140528093811.GE76726@abstractj.org>

Release the Kraken!

On 2014-05-28, Christos Vasilakis wrote:
>
> On May 28, 2014, at 12:14 PM, Corinne Krych <corinnekrych at gmail.com> wrote:
>
> > Hello Andrea
> >
> > you?re rught we missed Framework build + documentation. Let?s release a 0.9.1.
>
> since the changes from the previous release is the framework build and we are already using it in our quick starts with no issues, I am +1 to release a new version 0.9.1 ASAP and can happen till the end of the week.
>
> Any objections?
>
> -
> Christos
>
>
>
> > To answer you?re roadmap question, so far we use the general UnifiedPush roadmap [1].
> > I?ll send a PR to update 0.12.0 with iOS framework bits.
> >
> > Ok for all?
> >
> > ++
> > Corinne
> > [1] http://aerogear.org/docs/planning/roadmaps/UnifiedPush/
> >
> > On 28 May 2014, at 10:08, Andrea Vibelli <avibelli at redhat.com> wrote:
> >
> >> Hi all,
> >> the latest release of aerogear-push-ios-registration, version 0.9.0, is
> >> pretty old (more than 2 months ago), and does not contain some useful
> >> features like the build script for the creation of framework and static
> >> libs, and the new extended readme with instruction on how to use them.
> >>
> >> Are there any plans for a new release?
> >> Thanks
> >> Andrea
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/New-iOS-Push-SDK-Client-Release-tp7977.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

--

abstractj

From kpiwko at redhat.com  Wed May 28 09:31:54 2014
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 28 May 2014 15:31:54 +0200
Subject: [aerogear-dev] UnifiedPush WAR file -> Maven Central
In-Reply-To: <20140411090527.289235b5@kapy-ntb-x220>
References: <CAAg5f2QoOZ14MTYuOeGNUdOWg++5WekTTqakmasxqvtdiAs+Hg@mail.gmail.com>
	<20140411090527.289235b5@kapy-ntb-x220>
Message-ID: <20140528153154.40f01fe3@kapy-ntb-x220>

Any reason why it was not done for 0.10.3?

Bintray is actually broken as Maven repository, at is contains just WAR, not
unifiedserver-parent pom. So matzew's repo is the only working Maven repo since
modularization.

Karel

On Fri, 11 Apr 2014 09:05:27 +0200
Karel Piwko <kpiwko at redhat.com> wrote:

> +1, this still holds true. Temporary workaround we are using is to use
> Bintray/matzew's repo as a Maven Repository [1]. 
> 
> The other benefit of using Maven Central is staging feature through JBoss
> Nexus. So it would be easier to test staged release.
> 
> Karel
> 
> [1]
> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/junit-rule/src/test/java/org/jboss/aerogear/unifiedpush/test/Deployments.java#L167
> 
> 
> On Thu, 10 Apr 2014 20:09:20 +0200
> Matthias Wessendorf <matzew at apache.org> wrote:
> 
> > Hello,
> > 
> > we got asked by QE before, and now by LiveOak, if possible to put our WAR
> > file to Maven Central.
> > 
> > It makes things easier for others that are _integrating_ with out bits.
> > 
> > 
> > 
> > any thoughts ?
> > 
> > -Matthias
> > 
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From matzew at apache.org  Wed May 28 10:00:45 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 16:00:45 +0200
Subject: [aerogear-dev] [status] Quickstarts for Mobile Push 1.0.0 community
	release
Message-ID: <CAAg5f2QE_6mp+EFuOhkb=GCfo_OpkDTZmWroMj25QJpKaOsHbA@mail.gmail.com>

Hello,

we just met for the quickstarts; The work should be done by mid June or
earlier. So that we have all of that working fine and polished for our
Face2Face meeting.
<https://gist.github.com/matzew/459590aa794c5f97c99a#server>SERVER

   - Josh's PicketLink/JAX-RS version is almost there (a few things to
   polish)
   - Dan worked with James on a gateway version (using Fabric8, see [1])
   (The idea is have the mobile devices talk to the gateway and have the
   gateway/proxy do the work against the JAX-RS app (that might behind the
   firewall))

<https://gist.github.com/matzew/459590aa794c5f97c99a#clients>CLIENTS

   - Passos is about to finish the Android version
   - Christos is about to finish the iOS version
   - Cordova versions (jqm / Angular) are done, by Erik

<https://gist.github.com/matzew/459590aa794c5f97c99a#structure-of-the-gh-repo>Structure
of the GH REPO

/servers/
... /contacts-mobile-picketlink-secured
... /contacts-mobile-proxy
/clients/
... /cordova/
...... /contacts-mobile-cordova-jqm-client
...... /contacts-mobile-cordova-angular-client
... /contacts-mobile-android-client
... /contacts-mobile-ios-client


   - If time allows (we think yes), the 'web-app' from the PL/JAXRS will be
   a separated WAR file

<https://gist.github.com/matzew/459590aa794c5f97c99a#issues>ISSUES

   - jqm has issues with older androids; Well, according to the team only
   Android 4.4 only works 'acceptable' w/ JQM
   - Erik suggested removing the transitions (might make things faster)

We will revist next week, otherwise Luke/Lukas might get a 'chance' :-) to
take a look as well

Any questions ?

-Matthias

[1] https://github.com/fabric8io/fabric8/tree/master/gateway

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140528/7d9487ed/attachment-0001.html 

From matzew at apache.org  Wed May 28 10:01:26 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 16:01:26 +0200
Subject: [aerogear-dev] UnifiedPush WAR file -> Maven Central
In-Reply-To: <20140528153154.40f01fe3@kapy-ntb-x220>
References: <CAAg5f2QoOZ14MTYuOeGNUdOWg++5WekTTqakmasxqvtdiAs+Hg@mail.gmail.com>
	<20140411090527.289235b5@kapy-ntb-x220>
	<20140528153154.40f01fe3@kapy-ntb-x220>
Message-ID: <CAAg5f2TjM16JwJos0uZ_JAAZNRyTsiaY-qEz=kDhwXfS9SRaAQ@mail.gmail.com>

I am currently checking if there will be a 0.10.4 ;-)


On Wed, May 28, 2014 at 3:31 PM, Karel Piwko <kpiwko at redhat.com> wrote:

> Any reason why it was not done for 0.10.3?
>
> Bintray is actually broken as Maven repository, at is contains just WAR,
> not
> unifiedserver-parent pom. So matzew's repo is the only working Maven repo
> since
> modularization.
>
> Karel
>
> On Fri, 11 Apr 2014 09:05:27 +0200
> Karel Piwko <kpiwko at redhat.com> wrote:
>
> > +1, this still holds true. Temporary workaround we are using is to use
> > Bintray/matzew's repo as a Maven Repository [1].
> >
> > The other benefit of using Maven Central is staging feature through JBoss
> > Nexus. So it would be easier to test staged release.
> >
> > Karel
> >
> > [1]
> >
> https://github.com/aerogear/aerogear-unifiedpush-server-integration-tests/blob/junit-rule/src/test/java/org/jboss/aerogear/unifiedpush/test/Deployments.java#L167
> >
> >
> > On Thu, 10 Apr 2014 20:09:20 +0200
> > Matthias Wessendorf <matzew at apache.org> wrote:
> >
> > > Hello,
> > >
> > > we got asked by QE before, and now by LiveOak, if possible to put our
> WAR
> > > file to Maven Central.
> > >
> > > It makes things easier for others that are _integrating_ with out bits.
> > >
> > >
> > >
> > > any thoughts ?
> > >
> > > -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/20140528/adaf35ed/attachment.html 

From bsutter at redhat.com  Wed May 28 10:50:57 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Wed, 28 May 2014 10:50:57 -0400
Subject: [aerogear-dev] Understanding AeroGear development
In-Reply-To: <1400958149950-7926.post@n5.nabble.com>
References: <1400951747551-7925.post@n5.nabble.com>
	<1400958149950-7926.post@n5.nabble.com>
Message-ID: <A82522E6-D3BD-4005-A070-A36114E1706F@redhat.com>


On May 24, 2014, at 3:02 PM, jmanko <john.manko at gmail.com> wrote:

> I also noticed that when creating an HTML5 app within JBDS, none of the
> AeroGear deps were added to the pom.  Am I missing something?
Are you building a Hybrid app? If so, you get Aerogear as a Cordova plugin

http://screencast.com/t/Y2HXagdjeI

If you are building a mobile web app - then you add a reference to aerogear.js on your own/manually.


> 
> 
> 
> --
> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Understanding-AeroGear-development-tp7925p7926.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/20140528/bbccf671/attachment.html 

From lholmqui at redhat.com  Wed May 28 11:44:18 2014
From: lholmqui at redhat.com (Lucas Holmquist)
Date: Wed, 28 May 2014 11:44:18 -0400
Subject: [aerogear-dev] [status] Quickstarts for Mobile Push 1.0.0
	community release
In-Reply-To: <CAAg5f2QE_6mp+EFuOhkb=GCfo_OpkDTZmWroMj25QJpKaOsHbA@mail.gmail.com>
References: <CAAg5f2QE_6mp+EFuOhkb=GCfo_OpkDTZmWroMj25QJpKaOsHbA@mail.gmail.com>
Message-ID: <AA49EE0C-F91D-44ED-978E-CA2705A9FA89@redhat.com>


On May 28, 2014, at 10:00 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> Hello,
> 
> we just met for the quickstarts; The work should be done by mid June or earlier. So that we have all of that working fine and polished for our Face2Face meeting.
> 
> SERVER
> 
> Josh's PicketLink/JAX-RS version is almost there (a few things to polish)
> Dan worked with James on a gateway version (using Fabric8, see [1]) (The idea is have the mobile devices talk to the gateway and have the gateway/proxy do the work against the JAX-RS app (that might behind the firewall))
> CLIENTS
> 
> Passos is about to finish the Android version
> Christos is about to finish the iOS version
> Cordova versions (jqm / Angular) are done, by Erik
> Structure of the GH REPO
> 
> /servers/
> ... /contacts-mobile-picketlink-secured
> ... /contacts-mobile-proxy
> /clients/
> ... /cordova/
> ...... /contacts-mobile-cordova-jqm-client
> ...... /contacts-mobile-cordova-angular-client
> ... /contacts-mobile-android-client
> ... /contacts-mobile-ios-client
> If time allows (we think yes), the 'web-app' from the PL/JAXRS will be a separated WAR file
> ISSUES
> 
> jqm has issues with older androids; Well, according to the team only Android 4.4 only works 'acceptable' w/ JQM
> Erik suggested removing the transitions (might make things faster)
> We will revist next week, otherwise Luke/Lukas might get a 'chance' :-) to take a look as well
> 
> 
hey,  thats me  :) 
> Any questions ?
> 
> -Matthias
> 
> [1] https://github.com/fabric8io/fabric8/tree/master/gateway
> 
> 
> -- 
> Matthias Wessendorf 
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140528/15e57d12/attachment.html 

From hbons at redhat.com  Wed May 28 11:59:53 2014
From: hbons at redhat.com (Hylke Bons)
Date: Wed, 28 May 2014 16:59:53 +0100
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <5374DB1B.9020405@redhat.com>
References: <5374DB1B.9020405@redhat.com>
Message-ID: <538607F9.5090105@redhat.com>

Hey,

I've made a couple of small changes to the wireframes. Matt had some 
good feedback about the dashboard table showing 'recent' errors: it 
wasn't really clear what kind of time period it covered, and error 
messages could be hidden due to the table pagination in the log table.

These are the changes that try to address the above issues compared to 
the agreed upon previous design:
- Dashboard area: "Status" -> "Warnings"
- "Clear All" link/button to clear the list of errors on the dashboard
- The log table has a tab showing "Failed" vs. "All" messages.

https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png

Let me know if this is ok and at all still possible to still do in the 
current timeframe ("Clear All" seems to require extra backend logic).

Thanks,

Hylke




On 15/05/2014 16:19, Hylke Bons wrote:
> Hey,
>
> Here's an initial version:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
> I tried to incorporate most wishes expressed in the other thread.
>
> Most notable things:
> - Landing page with an overview of stats, most active apps, and error
> messages
> - Activity table shows both registration and notification events
> - Activity table is per variant, and not all activity on the server.
> Unless there's a usecase to have every event for every app/variant in a
> table I don't think we actually need it. The important thing is to get
> to error messages easily.
>
> Things to do/think about:
> - links/entry points to the activity table
> - filtering the activity table
>
> This is just the first iteration and we will improve on this.
> Let me know what you think.
>
> Thanks,
>
> Hylke
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From matzew at apache.org  Wed May 28 12:14:08 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 18:14:08 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <538607F9.5090105@redhat.com>
References: <5374DB1B.9020405@redhat.com>
	<538607F9.5090105@redhat.com>
Message-ID: <CAAg5f2SzSL=5A5ZvPoKfgcZk3-SMWCt4CaepsEf7tM6cWzoO-g@mail.gmail.com>

On Wed, May 28, 2014 at 5:59 PM, Hylke Bons <hbons at redhat.com> wrote:

> Hey,
>
> I've made a couple of small changes to the wireframes. Matt had some
> good feedback about the dashboard table showing 'recent' errors: it
> wasn't really clear what kind of time period it covered, and error
> messages could be hidden due to the table pagination in the log table.
>
> These are the changes that try to address the above issues compared to
> the agreed upon previous design:
> - Dashboard area: "Status" -> "Warnings"
>

we can say that a it has failed for the variant;
As said before, we can not (technically) say that just three messages failed



> - "Clear All" link/button to clear the list of errors on the dashboard
>

hrm ... why? We will _not_ persist that 'clear' - it will be visible on
next loop to the page;
IMO useless button ...


> - The log table has a tab showing "Failed" vs. "All" messages.
>

not sure, we really need this, ATM

remember.... we talked about a 'simple' overview... and now with the
dashboard being added, we already have have more,
and this is even more of that ...

Not sure ...


>
>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
> Let me know if this is ok and at all still possible to still do in the
> current timeframe ("Clear All" seems to require extra backend logic).
>

yep, will NOT be implemented for 1.0.0


>
> Thanks,
>
> Hylke
>
>
>
>
> On 15/05/2014 16:19, Hylke Bons wrote:
> > Hey,
> >
> > Here's an initial version:
> >
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >
> > I tried to incorporate most wishes expressed in the other thread.
> >
> > Most notable things:
> > - Landing page with an overview of stats, most active apps, and error
> > messages
> > - Activity table shows both registration and notification events
> > - Activity table is per variant, and not all activity on the server.
> > Unless there's a usecase to have every event for every app/variant in a
> > table I don't think we actually need it. The important thing is to get
> > to error messages easily.
> >
> > Things to do/think about:
> > - links/entry points to the activity table
> > - filtering the activity table
> >
> > This is just the first iteration and we will improve on this.
> > Let me know what you think.
> >
> > 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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140528/f707ef44/attachment-0001.html 

From hbons at redhat.com  Wed May 28 12:26:30 2014
From: hbons at redhat.com (Hylke Bons)
Date: Wed, 28 May 2014 17:26:30 +0100
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <CAAg5f2SzSL=5A5ZvPoKfgcZk3-SMWCt4CaepsEf7tM6cWzoO-g@mail.gmail.com>
References: <5374DB1B.9020405@redhat.com>	<538607F9.5090105@redhat.com>
	<CAAg5f2SzSL=5A5ZvPoKfgcZk3-SMWCt4CaepsEf7tM6cWzoO-g@mail.gmail.com>
Message-ID: <53860E36.1060909@redhat.com>

That's fine, we won't do it for this cycle then.

Thanks,

Hylke

On 28/05/2014 17:14, Matthias Wessendorf wrote:
>
>
>
> On Wed, May 28, 2014 at 5:59 PM, Hylke Bons <hbons at redhat.com 
> <mailto:hbons at redhat.com>> wrote:
>
>     Hey,
>
>     I've made a couple of small changes to the wireframes. Matt had some
>     good feedback about the dashboard table showing 'recent' errors: it
>     wasn't really clear what kind of time period it covered, and error
>     messages could be hidden due to the table pagination in the log table.
>
>     These are the changes that try to address the above issues compared to
>     the agreed upon previous design:
>     - Dashboard area: "Status" -> "Warnings"
>
>
> we can say that a it has failed for the variant;
> As said before, we can not (technically) say that just three messages 
> failed
>
>     - "Clear All" link/button to clear the list of errors on the dashboard
>
>
> hrm ... why? We will _not_ persist that 'clear' - it will be visible 
> on next loop to the page;
> IMO useless button ...
>
>     - The log table has a tab showing "Failed" vs. "All" messages.
>
>
> not sure, we really need this, ATM
>
> remember.... we talked about a 'simple' overview... and now with the 
> dashboard being added, we already have have more,
> and this is even more of that ...
>
> Not sure ...
>
>
>     https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
>     Let me know if this is ok and at all still possible to still do in the
>     current timeframe ("Clear All" seems to require extra backend logic).
>
>
> yep, will NOT be implemented for 1.0.0
>
>
>     Thanks,
>
>     Hylke
>
>
>
>
>     On 15/05/2014 16:19, Hylke Bons wrote:
>     > Hey,
>     >
>     > Here's an initial version:
>     >
>     https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>     >
>     > I tried to incorporate most wishes expressed in the other thread.
>     >
>     > Most notable things:
>     > - Landing page with an overview of stats, most active apps, and
>     error
>     > messages
>     > - Activity table shows both registration and notification events
>     > - Activity table is per variant, and not all activity on the server.
>     > Unless there's a usecase to have every event for every
>     app/variant in a
>     > table I don't think we actually need it. The important thing is
>     to get
>     > to error messages easily.
>     >
>     > Things to do/think about:
>     > - links/entry points to the activity table
>     > - filtering the activity table
>     >
>     > This is just the first iteration and we will improve on this.
>     > Let me know what you think.
>     >
>     > Thanks,
>     >
>     > Hylke
>     > _______________________________________________
>     > 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
>
>     _______________________________________________
>     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
>
>
>
>
> -- 
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/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/20140528/36aa79fe/attachment.html 

From matzew at apache.org  Wed May 28 12:34:52 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 18:34:52 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <53860E36.1060909@redhat.com>
References: <5374DB1B.9020405@redhat.com> <538607F9.5090105@redhat.com>
	<CAAg5f2SzSL=5A5ZvPoKfgcZk3-SMWCt4CaepsEf7tM6cWzoO-g@mail.gmail.com>
	<53860E36.1060909@redhat.com>
Message-ID: <CAAg5f2TC6f-N-Lnp_PQh3uLZdHMJMVWo-QpGQipKrh0tXxG+Jw@mail.gmail.com>

On Wed, May 28, 2014 at 6:26 PM, Hylke Bons <hbons at redhat.com> wrote:

>  That's fine, we won't do it for this cycle then.
>

perfect!



>
> Thanks,
>
> Hylke
>
>
> On 28/05/2014 17:14, Matthias Wessendorf wrote:
>
>
>
>
> On Wed, May 28, 2014 at 5:59 PM, Hylke Bons <hbons at redhat.com> wrote:
>
>> Hey,
>>
>> I've made a couple of small changes to the wireframes. Matt had some
>> good feedback about the dashboard table showing 'recent' errors: it
>> wasn't really clear what kind of time period it covered, and error
>> messages could be hidden due to the table pagination in the log table.
>>
>> These are the changes that try to address the above issues compared to
>> the agreed upon previous design:
>> - Dashboard area: "Status" -> "Warnings"
>>
>
>  we can say that a it has failed for the variant;
> As said before, we can not (technically) say that just three messages
> failed
>
>
>
>> - "Clear All" link/button to clear the list of errors on the dashboard
>>
>
>  hrm ... why? We will _not_ persist that 'clear' - it will be visible on
> next loop to the page;
> IMO useless button ...
>
>
>> - The log table has a tab showing "Failed" vs. "All" messages.
>>
>
>  not sure, we really need this, ATM
>
>  remember.... we talked about a 'simple' overview... and now with the
> dashboard being added, we already have have more,
> and this is even more of that ...
>
>  Not sure ...
>
>
>>
>>
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>
>> Let me know if this is ok and at all still possible to still do in the
>> current timeframe ("Clear All" seems to require extra backend logic).
>>
>
>  yep, will NOT be implemented for 1.0.0
>
>
>>
>> Thanks,
>>
>> Hylke
>>
>>
>>
>>
>> On 15/05/2014 16:19, Hylke Bons wrote:
>>  > Hey,
>> >
>> > Here's an initial version:
>> >
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> >
>> > I tried to incorporate most wishes expressed in the other thread.
>> >
>> > Most notable things:
>> > - Landing page with an overview of stats, most active apps, and error
>> > messages
>> > - Activity table shows both registration and notification events
>> > - Activity table is per variant, and not all activity on the server.
>> > Unless there's a usecase to have every event for every app/variant in a
>> > table I don't think we actually need it. The important thing is to get
>> > to error messages easily.
>> >
>> > Things to do/think about:
>> > - links/entry points to the activity table
>> > - filtering the activity table
>> >
>> > This is just the first iteration and we will improve on this.
>> > Let me know what you think.
>> >
>> > 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
>>
>
>
>
>  --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.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/20140528/d8ef29be/attachment.html 

From mcarrano at redhat.com  Wed May 28 13:22:03 2014
From: mcarrano at redhat.com (Matt Carrano)
Date: Wed, 28 May 2014 13:22:03 -0400 (EDT)
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <CAAg5f2SzSL=5A5ZvPoKfgcZk3-SMWCt4CaepsEf7tM6cWzoO-g@mail.gmail.com>
References: <5374DB1B.9020405@redhat.com> <538607F9.5090105@redhat.com>
	<CAAg5f2SzSL=5A5ZvPoKfgcZk3-SMWCt4CaepsEf7tM6cWzoO-g@mail.gmail.com>
Message-ID: <1139598237.15821254.1401297723758.JavaMail.zimbra@redhat.com>



----- Original Message -----
From: "Matthias Wessendorf" <matzew at apache.org>
To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
Cc: "Matt Carrano" <mcarrano at redhat.com>
Sent: Wednesday, May 28, 2014 12:14:08 PM
Subject: Re: [aerogear-dev] First go at stats/activity wireframes

On Wed, May 28, 2014 at 5:59 PM, Hylke Bons <hbons at redhat.com> wrote:

> Hey,
>
> I've made a couple of small changes to the wireframes. Matt had some
> good feedback about the dashboard table showing 'recent' errors: it
> wasn't really clear what kind of time period it covered, and error
> messages could be hidden due to the table pagination in the log table.
>
> These are the changes that try to address the above issues compared to
> the agreed upon previous design:
> - Dashboard area: "Status" -> "Warnings"
>

we can say that a it has failed for the variant;
As said before, we can not (technically) say that just three messages failed



> - "Clear All" link/button to clear the list of errors on the dashboard
>

hrm ... why? We will _not_ persist that 'clear' - it will be visible on
next loop to the page;
IMO useless button ...

Agree that if the clear is not persisted, then the button is useless.  My original question to Hylke was how do items get removed from this message queue?  If the user cannot clear them, do they persist for a certain amount of time?  Is the queue finite (i.e. holds the last n messages)?  Understand the scope issues, and that this will not likely make the 1.0.0 release, but just want to make sure these questions are considered.


> - The log table has a tab showing "Failed" vs. "All" messages.
>

not sure, we really need this, ATM

remember.... we talked about a 'simple' overview... and now with the
dashboard being added, we already have have more,
and this is even more of that ...

Not sure ...


>
>
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
> Let me know if this is ok and at all still possible to still do in the
> current timeframe ("Clear All" seems to require extra backend logic).
>

yep, will NOT be implemented for 1.0.0


>
> Thanks,
>
> Hylke
>
>
>
>
> On 15/05/2014 16:19, Hylke Bons wrote:
> > Hey,
> >
> > Here's an initial version:
> >
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >
> > I tried to incorporate most wishes expressed in the other thread.
> >
> > Most notable things:
> > - Landing page with an overview of stats, most active apps, and error
> > messages
> > - Activity table shows both registration and notification events
> > - Activity table is per variant, and not all activity on the server.
> > Unless there's a usecase to have every event for every app/variant in a
> > table I don't think we actually need it. The important thing is to get
> > to error messages easily.
> >
> > Things to do/think about:
> > - links/entry points to the activity table
> > - filtering the activity table
> >
> > This is just the first iteration and we will improve on this.
> > Let me know what you think.
> >
> > 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
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

From matzew at apache.org  Wed May 28 14:45:36 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 May 2014 20:45:36 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <1139598237.15821254.1401297723758.JavaMail.zimbra@redhat.com>
References: <5374DB1B.9020405@redhat.com> <538607F9.5090105@redhat.com>
	<CAAg5f2SzSL=5A5ZvPoKfgcZk3-SMWCt4CaepsEf7tM6cWzoO-g@mail.gmail.com>
	<1139598237.15821254.1401297723758.JavaMail.zimbra@redhat.com>
Message-ID: <CAAg5f2RAvDD0axYQMvUDUy5OUer298EZJ68yvz7hye_A05U0fA@mail.gmail.com>

On Wed, May 28, 2014 at 7:22 PM, Matt Carrano <mcarrano at redhat.com> wrote:

>
>
> ----- Original Message -----
> From: "Matthias Wessendorf" <matzew at apache.org>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Cc: "Matt Carrano" <mcarrano at redhat.com>
> Sent: Wednesday, May 28, 2014 12:14:08 PM
> Subject: Re: [aerogear-dev] First go at stats/activity wireframes
>
> On Wed, May 28, 2014 at 5:59 PM, Hylke Bons <hbons at redhat.com> wrote:
>
> > Hey,
> >
> > I've made a couple of small changes to the wireframes. Matt had some
> > good feedback about the dashboard table showing 'recent' errors: it
> > wasn't really clear what kind of time period it covered, and error
> > messages could be hidden due to the table pagination in the log table.
> >
> > These are the changes that try to address the above issues compared to
> > the agreed upon previous design:
> > - Dashboard area: "Status" -> "Warnings"
> >
>
> we can say that a it has failed for the variant;
> As said before, we can not (technically) say that just three messages
> failed
>
>
>
> > - "Clear All" link/button to clear the list of errors on the dashboard
> >
>
> hrm ... why? We will _not_ persist that 'clear' - it will be visible on
> next loop to the page;
> IMO useless button ...
>
> Agree that if the clear is not persisted, then the button is useless.  My
> original question to Hylke was how do items get removed from this message
> queue?  If the user cannot clear them, do they persist for a certain amount
> of time?  Is the queue finite (i.e. holds the last n messages)?


The last n issues will be presented;

Generally the 'push status info' is only visible for 30 days - afterwards
they are deleted



> Understand the scope issues, and that this will not likely make the 1.0.0
> release, but just want to make sure these questions are considered.
>

Thanks!

I think we are good to go, and ignore the bits that mentioned above

-M


>
>
> > - The log table has a tab showing "Failed" vs. "All" messages.
> >
>
> not sure, we really need this, ATM
>
> remember.... we talked about a 'simple' overview... and now with the
> dashboard being added, we already have have more,
> and this is even more of that ...
>
> Not sure ...
>
>
> >
> >
> >
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> >
> > Let me know if this is ok and at all still possible to still do in the
> > current timeframe ("Clear All" seems to require extra backend logic).
> >
>
> yep, will NOT be implemented for 1.0.0
>
>
> >
> > Thanks,
> >
> > Hylke
> >
> >
> >
> >
> > On 15/05/2014 16:19, Hylke Bons wrote:
> > > Hey,
> > >
> > > Here's an initial version:
> > >
> >
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
> > >
> > > I tried to incorporate most wishes expressed in the other thread.
> > >
> > > Most notable things:
> > > - Landing page with an overview of stats, most active apps, and error
> > > messages
> > > - Activity table shows both registration and notification events
> > > - Activity table is per variant, and not all activity on the server.
> > > Unless there's a usecase to have every event for every app/variant in a
> > > table I don't think we actually need it. The important thing is to get
> > > to error messages easily.
> > >
> > > Things to do/think about:
> > > - links/entry points to the activity table
> > > - filtering the activity table
> > >
> > > This is just the first iteration and we will improve on this.
> > > Let me know what you think.
> > >
> > > 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
> >
>
>
>
> --
> 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/20140528/2af0fcf0/attachment.html 

From corinnekrych at gmail.com  Thu May 29 01:18:25 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 29 May 2014 07:18:25 +0200
Subject: [aerogear-dev] OAuth2 and Account Management
Message-ID: <CE1F1C3B-8EE6-47CE-815A-50A0026A8AAB@gmail.com>

Hello all

It all started in that thread [1] talking about Android OAuth2 PR, but the discussion shifted on account management and storage. I think AccountManager deserves its own thread besides it?s a cross client topic (although implicit grant for pure web app is less a use case) so title is not right. Let?s fork the discussion.

Main goal of AccountManager is to store all the social access tokens per account. Here is the use case:
Some application may have to deal with several OAuth2 providers. For example in ios-cookbook, we have Shoot app which let you upload your photos to Google Drive(should change that to Google+ eventually), Facebook (and soon Instagram). When a user open Shoot for the first time and want to share to facebook, he will be prompted for OAuth2 grant, same thing for Google grant. The second photo will not trigger any grant as we?ve got the tokens. But if a user close the app and reopen it, we need something to store them if we don?t want to prompt again => AccountManager.

Encrypted or not encrypted?
Obviously access token and even more refresh token are sensitive data. Should we store them encrypted or in a secure storage like KeyChain or KeyStore? If we go that path a password is required to encrypt or access keychain, so we need an extra prompt for the user to enter password. For example, we can chage Shoot to require a password at first login to ancrypt/decrypt access token.
I would leave this decision to the end-use rdeveloper of the app. I would go for a configurable AccountManager, being able to take a store as demo here [2].

For now proposed API:
As explained here [3], use same method signature authz: like for AGAuthorizer. But when use on AccountManager it will create a authzModule and add an account to store tokens.

What?s next?
We need to be able to revoke tokens and remove account from account manager.

Thoughts? 
@summers : as you?re the guy behind Account Manager, if you can have a look to iOS PR [2] [3] I would love to hear about your thoughts

++
Corinne
[1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-OAuth2-PR-td7576.html
[2] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot/AGShootViewController.m#L45
[3] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot.md#aerogear-account-manager
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140529/7bab9580/attachment.html 

From lukas.fryc at gmail.com  Thu May 29 07:20:03 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 29 May 2014 13:20:03 +0200
Subject: [aerogear-dev] AG Push Console review
Message-ID: <CAEroY35Z_HjLVgO-bUfYXYhdL5Z_+yuMBy8B9Vft0hNu4nx5qg@mail.gmail.com>

Hey guys,

Viliam asked me to forward his review notes/remarks here:

Nice job, Viliam, I will incorporate your suggestions.

Btw the overall state of UX improvements is tracked here:

https://issues.jboss.org/browse/AGPUSH-671


Cheers,

~ Lukas



-------- Original Message --------Subject:AG Console review Date:Wed, 28
May 2014 15:01:19 +0200From:Viliam Rockai <vrockai at redhat.com> To:Matthias
Wessendorf <mwessend at redhat.com>, Lukas Fryc <lfryc at redhat.com> CC:Alexandre
Mendonca <amendonc at redhat.com>

Hi,

I went through the console code. Overall, it looks just fine. Previously
I thought I'll just put comments into the code and make a commit. Since
I found only a few issues, it's not worth it. So here is my list:

* The name of your angularjs module is "newadminApp". I think it should
be something like "agconsole".

* You're missing feedback for user on many places. If the error says
'Something went wrong...', it doesn't say much to a user. Even changing
it to denote the current operation would be better, something like
'Unable to create new application'. On most of the $resource.* methods
you're missing the feedback, too. For most of them the information about
success would be annoying, but maybe it could be interesting for user to
see errors like 'Unable to get the application list, check your
connection to the server...'. When my session to the console timed-out,
the operation I was trying to do (renaming of app) didn't do anything,
but I had no clue why.

* AFAIK it's considered a bad practice to use jQuery inside controllers.
You use only two $ functions: $.extend and $.ajax, which can be replaced
with angular.extend/angular.copy and the $resource service. If you can't
find a way how to do something without jQuery inside controller, maybe
creating of custom directive is the right solution, but this doesn't
seem to be the case.

* It seems that you're using several switch statements just to assign a
value based on input. This seems to be a good candidate for using a map.

* Notifications - they are inside ng-view pages. It looks fine and works
for your current purposes. But if you make some new page in the future,
which redirects you (i.e. creating a new entity, after submit, user is
redirected to entity list with newly created stuff), you may loose the
message. Another disadvantage of this is non-consistent L&F for feedback
messages. The advantage is, that you're not covering any content with
the message as LO does.

* In installation.html I see stuff like <col width="45%">. I think this
should be rewritten to use the bootstrap grid layout (classes like
col-md-12...).

* We use our custom directive lo-autofocus for the 1st input in modals.
Right after the modal pops-up, user has the focus on the first input and
pressing enter submits the modal.

* The last one is not a problem at all, I just don't feel right about
it :) You use $window.location.href instead $location.absUrl(). They
seem to do the same, but since you don't use any other $window stuff,
using $location makes more sense to me.



Btw, we were thinking about creating a dynamic creation of breadcrumbs,
too. But since we didn't want to have them fully dependent on the URL
(URLs could change for us in the future), we didn't do it. Are you sure
you want to make url and breadcrumbs to be linked this way?

Anyway, congrats, you did good job with the console and this review
helped me to get aware of some problems the LO console may have, too.

Viliam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140529/add82512/attachment-0001.html 

From cvasilak at gmail.com  Thu May 29 07:35:52 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Thu, 29 May 2014 14:35:52 +0300
Subject: [aerogear-dev] iOS push-sdk new release
In-Reply-To: <20140528093811.GE76726@abstractj.org>
References: <1401264508560-7977.post@n5.nabble.com>
	<7BB3FB2F-1DAC-4051-B1C0-1B88F9CB4215@gmail.com>
	<D86E8BE1-766D-4788-ADEC-40D95F01ACD3@gmail.com>
	<20140528093811.GE76726@abstractj.org>
Message-ID: <1D8D5A4D-D7E7-4376-B027-E9398A5D1F3C@gmail.com>

Hi all,

just tagged and pushed on cocoapods[1] a new version of the iOS client push-sdk v0.9.1. Big change on this release is the ability to embed the library either as a static lib or with the convenience of framework (more details in [2]). Whether you are using cocoapods or not, you now have more options to push-enabled your iOS projects!

I would like to thank Andrea Vibelli for making this happen, great work!

enjoy!

-
Christos

[1] http://cocoapods.org/?q=AeroGear-Push
[2] http://cocoadocs.org/docsets/AeroGear-Push/0.9.1/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140529/2e7315d4/attachment.html 

From lukas.fryc at gmail.com  Thu May 29 07:43:02 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 29 May 2014 13:43:02 +0200
Subject: [aerogear-dev] UPS admin-ui distribution compiled by
	frontend-maven-plugin
Message-ID: <CAEroY35YqT=B6G4a4YAHS5t0hgdA=gtjXjvbfUrHVHJuAF+g9Q@mail.gmail.com>

Hey guys,

we would like to evaluate "frontend-maven-plugin" [1] that could be used as
a mean to compile admin-ui distribution files into ag-push.war webapp
during Maven build time

This way we would enable people not familiar with node/npm/bower/grunt
tooling to compile latest and greatest,

and additionally avoid a need to compile and save into git repository.

https://issues.jboss.org/browse/AGPUSH-672

Note1: web developer will still leverage Node tooling

Note2: this is post UPS 0.11.0 thing! ;-)


As pointed out in the JIRA, this may have its downsides,

so if anyone has some concerns please speak up now. :-)


Cheers,

~ Lukas

[1] https://github.com/eirslett/frontend-maven-plugin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140529/7748cfc8/attachment.html 

From bruno at abstractj.org  Thu May 29 09:00:09 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 29 May 2014 10:00:09 -0300
Subject: [aerogear-dev] UPS admin-ui distribution compiled by
 frontend-maven-plugin
In-Reply-To: <CAEroY35YqT=B6G4a4YAHS5t0hgdA=gtjXjvbfUrHVHJuAF+g9Q@mail.gmail.com>
References: <CAEroY35YqT=B6G4a4YAHS5t0hgdA=gtjXjvbfUrHVHJuAF+g9Q@mail.gmail.com>
Message-ID: <20140529130009.GA33519@abstractj.org>

Good morning, I have some n00b questions. What happens with web
developer or node developers who don't care about Maven? Is still
possible to make use of pure node to build admin-ui?

Speaking about the downsides:

I think this might be a concern, if is necessary to fix something at each Node
upgrade.

> * he had some issues himself to get it work, especially during Node
upgrades
> * stability of the build can be questionable

I'm not sure about the negative influence if is possible to choose. Could you
please elaborate?

> * it can negatively influence developers that are not aware of Node
tooling

My latest question is: do we really need this? why?

On 2014-05-29, Luk?? Fry? wrote:
> Hey guys,
>
> we would like to evaluate "frontend-maven-plugin" [1] that could be used as
> a mean to compile admin-ui distribution files into ag-push.war webapp
> during Maven build time
>
> This way we would enable people not familiar with node/npm/bower/grunt
> tooling to compile latest and greatest,
>
> and additionally avoid a need to compile and save into git repository.
>
> https://issues.jboss.org/browse/AGPUSH-672
>
> Note1: web developer will still leverage Node tooling
>
> Note2: this is post UPS 0.11.0 thing! ;-)
>
>
> As pointed out in the JIRA, this may have its downsides,
>
> so if anyone has some concerns please speak up now. :-)
>
>
> Cheers,
>
> ~ Lukas
>
> [1] https://github.com/eirslett/frontend-maven-plugin

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From bruno at abstractj.org  Thu May 29 09:18:56 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Thu, 29 May 2014 10:18:56 -0300
Subject: [aerogear-dev] OAuth2 and Account Management
In-Reply-To: <CE1F1C3B-8EE6-47CE-815A-50A0026A8AAB@gmail.com>
References: <CE1F1C3B-8EE6-47CE-815A-50A0026A8AAB@gmail.com>
Message-ID: <20140529131856.GB33519@abstractj.org>

On 2014-05-29, Corinne Krych wrote:
> Hello all
>
> It all started in that thread [1] talking about Android OAuth2 PR, but the discussion shifted on account management and storage. I think AccountManager deserves its own thread besides it?s a cross client topic (although implicit grant for pure web app is less a use case) so title is not right. Let?s fork the discussion.
>
> Main goal of AccountManager is to store all the social access tokens per account. Here is the use case:
> Some application may have to deal with several OAuth2 providers. For example in ios-cookbook, we have Shoot app which let you upload your photos to Google Drive(should change that to Google+ eventually), Facebook (and soon Instagram). When a user open Shoot for the first time and want to share to facebook, he will be prompted for OAuth2 grant, same thing for Google grant. The second photo will not trigger any grant as we?ve got the tokens. But if a user close the app and reopen it, we need something to store them if we don?t want to prompt again => AccountManager.
>
> Encrypted or not encrypted?

Encrypted, always.

> Obviously access token and even more refresh token are sensitive data. Should we store them encrypted or in a secure storage like KeyChain or KeyStore? If we go that path a password is required to encrypt or access keychain, so we need an extra prompt for the user to enter password. For example, we can chage Shoot to require a password at first login to ancrypt/decrypt access token.

I think here is where offline specification comes in to place
(https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-security-offline/index.md). We already discussed the workflow of how to protect sensitive offline data, but if it's missing something, feel free to include. Into this way we can avoid overlappings.

> I would leave this decision to the end-use rdeveloper of the app. I would go for a configurable AccountManager, being able to take a store as demo here [2].
>

I think it must be encrypted by default and let them disable if
necessary.

> For now proposed API:
> As explained here [3], use same method signature authz: like for AGAuthorizer. But when use on AccountManager it will create a authzModule and add an account to store tokens.
>
> What?s next?
> We need to be able to revoke tokens and remove account from account manager.
>
> Thoughts?
> @summers : as you?re the guy behind Account Manager, if you can have a look to iOS PR [2] [3] I would love to hear about your thoughts
>
> ++
> Corinne
> [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-OAuth2-PR-td7576.html
> [2] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot/AGShootViewController.m#L45
> [3] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot.md#aerogear-account-manager

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj

From lukas.fryc at gmail.com  Thu May 29 09:44:37 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 29 May 2014 15:44:37 +0200
Subject: [aerogear-dev] UPS admin-ui distribution compiled by
	frontend-maven-plugin
In-Reply-To: <20140529130009.GA33519@abstractj.org>
References: <CAEroY35YqT=B6G4a4YAHS5t0hgdA=gtjXjvbfUrHVHJuAF+g9Q@mail.gmail.com>
	<20140529130009.GA33519@abstractj.org>
Message-ID: <CAEroY34yNuU=ZNms8hRjy5W7aqZD8zMdmam3puYX155_c5TAJA@mail.gmail.com>

On Thu, May 29, 2014 at 3:00 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning, I have some n00b questions. What happens with web
> developer or node developers who don't care about Maven? Is still
> possible to make use of pure node to build admin-ui?
>

This is a completely valid question and that's why it was answered
beforehand. :-)

{quote} Note1: web developer will still leverage Node tooling {quote}

...during his regular workflow



> Speaking about the downsides:
>
> I think this might be a concern, if is necessary to fix something at each
> Node
> upgrade.
>
> > * he had some issues himself to get it work, especially during Node
> upgrades
> > * stability of the build can be questionable
>
> I'm not sure about the negative influence if is possible to choose. Could
> you
> please elaborate?
>
> > * it can negatively influence developers that are not aware of Node
> tooling
>

Since I did not used it, I can't say it's 100% way to go, but it's worth a
prototype work.

There seems to be a non-trivial community around this tool.

(Btw we did something similar with use of PhantomJS back in Arquillian and
it's HUGE win for users.
They don't even know there was ever some problem with downloading
PhantomJS.)



>
> My latest question is: do we really need this? why?
>

The problem this plugin solves is that everytime you change admin-ui, you
need to compile down distribution and save it as a source tree (and this
itself is no, no..!, NO!).

* if you forget. you will get your friends into trouble - they won't work
on up to date version anymore
* you are polluting git commit history with non-relevant changes
(sidenote: at this very moment, we don't compile distribution - once we do
so, some of admin-ui dist files will be removed and some will be added with
each admin-ui change)




The fact is not only we, but also larger community, are facing the same
issue:

* how the hell connect the web development tooling with Maven tooling?,
* or vice-versa my boss wants me to produce WAR, but I'm frontend developer
who knows no java

It frontend-maven-plugin works it is the solution for broader audience. If
not, we should keep seeking an answer.


>
> On 2014-05-29, Luk?? Fry? wrote:
> > Hey guys,
> >
> > we would like to evaluate "frontend-maven-plugin" [1] that could be used
> as
> > a mean to compile admin-ui distribution files into ag-push.war webapp
> > during Maven build time
> >
> > This way we would enable people not familiar with node/npm/bower/grunt
> > tooling to compile latest and greatest,
> >
> > and additionally avoid a need to compile and save into git repository.
> >
> > https://issues.jboss.org/browse/AGPUSH-672
> >
> > Note1: web developer will still leverage Node tooling
> >
> > Note2: this is post UPS 0.11.0 thing! ;-)
> >
> >
> > As pointed out in the JIRA, this may have its downsides,
> >
> > so if anyone has some concerns please speak up now. :-)
> >
> >
> > Cheers,
> >
> > ~ Lukas
> >
> > [1] https://github.com/eirslett/frontend-maven-plugin
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> 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/20140529/ca04fc6e/attachment-0001.html 

From supittma at redhat.com  Thu May 29 11:05:59 2014
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 29 May 2014 11:05:59 -0400
Subject: [aerogear-dev] OAuth2 and Account Management
In-Reply-To: <CE1F1C3B-8EE6-47CE-815A-50A0026A8AAB@gmail.com>
References: <CE1F1C3B-8EE6-47CE-815A-50A0026A8AAB@gmail.com>
Message-ID: <53874CD7.7030708@redhat.com>

On 05/29/2014 01:18 AM, Corinne Krych wrote:
> Hello all
>
> It all started in that thread [1] talking about Android OAuth2 PR, but 
> the discussion shifted on account management and storage. I think 
> AccountManager deserves its own thread besides it's a cross client 
> topic (although implicit grant for pure web app is less a use case) so 
> title is not right. Let's fork the discussion.
>
> Main goal of AccountManager is to store all the social access tokens 
> per account. Here is the use case:
> Some application may have to deal with several OAuth2 providers. For 
> example in ios-cookbook, we have Shoot app which let you upload your 
> photos to Google Drive(should change that to Google+ eventually), 
> Facebook (and soon Instagram). When a user open Shoot for the first 
> time and want to share to facebook, he will be prompted for OAuth2 
> grant, same thing for Google grant. The second photo will not trigger 
> any grant as we've got the tokens. But if a user close the app and 
> reopen it, we need something to store them if we don't want to prompt 
> again => AccountManager.
>
> Encrypted or not encrypted?
> Obviously access token and even more refresh token are sensitive data. 
> Should we store them encrypted or in a secure storage like KeyChain or 
> KeyStore? If we go that path a password is required to encrypt or 
> access keychain, so we need an extra prompt for the user to enter 
> password. For example, we can chage Shoot to require a password at 
> first login to ancrypt/decrypt access token.
> I would leave this decision to the end-use rdeveloper of the app. I 
> would go for a configurable AccountManager, being able to take a store 
> as demo here [2].
>
> For now proposed API:
> As explained here [3], use same method signature authz: like for 
> AGAuthorizer. But when use on AccountManager it will create a 
> authzModule and add an account to store tokens.
>
> What's next?
> We need to be able to revoke tokens and remove account from account 
> manager.
>
> Thoughts?
> @summers : as you're the guy behind Account Manager, if you can have a 
> look to iOS PR [2] [3] I would love to hear about your thoughts
WRT #3 I think that this is a really neat was of solving some of my 
design concerns on the Android side.  Without getting too gory into the 
details, the AuthzModule is responsible for managing the lifecycle of 
the AccountManager/AccountService.  Having the Service/Manager be the 
factory class for AuthzModules is much more sane.
>
> ++
> Corinne
> [1] 
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-OAuth2-PR-td7576.html
> [2] 
> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot/AGShootViewController.m#L45
> [3] 
> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot.md#aerogear-account-manager
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


-- 
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140529/bc1209f7/attachment.html 

From avibelli at redhat.com  Thu May 29 12:08:03 2014
From: avibelli at redhat.com (Andrea Vibelli)
Date: Thu, 29 May 2014 09:08:03 -0700 (PDT)
Subject: [aerogear-dev] UnifiedPush Java Sender use of AeroGear BOMs
Message-ID: <1401379683386-8011.post@n5.nabble.com>

Hi all, 
is there any plan to merge the PR
https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/41, that
would let the UnifiedPush Java Sender inherit and use the AeroGear BOMs?

Thanks
Andrea



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Java-Sender-use-of-AeroGear-BOMs-tp8011.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Thu May 29 12:28:01 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 29 May 2014 18:28:01 +0200
Subject: [aerogear-dev] UnifiedPush Java Sender use of AeroGear BOMs
In-Reply-To: <1401379683386-8011.post@n5.nabble.com>
References: <1401379683386-8011.post@n5.nabble.com>
Message-ID: <CAD_dpu3+NLriGSysCgO8o1TX-2k-rgR1C2MA_TQ7Ea7J7GLdaw@mail.gmail.com>

Sure,
I will make sure to merge that tomorrow.
Seb



On Thu, May 29, 2014 at 6:08 PM, Andrea Vibelli <avibelli at redhat.com> wrote:

> Hi all,
> is there any plan to merge the PR
> https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/41, that
> would let the UnifiedPush Java Sender inherit and use the AeroGear BOMs?
>
> Thanks
> Andrea
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/UnifiedPush-Java-Sender-use-of-AeroGear-BOMs-tp8011.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/20140529/8b6693fd/attachment.html 

From bsutter at redhat.com  Thu May 29 12:36:16 2014
From: bsutter at redhat.com (Burr Sutter)
Date: Thu, 29 May 2014 12:36:16 -0400
Subject: [aerogear-dev] AG Push Console review
In-Reply-To: <CAEroY35Z_HjLVgO-bUfYXYhdL5Z_+yuMBy8B9Vft0hNu4nx5qg@mail.gmail.com>
References: <CAEroY35Z_HjLVgO-bUfYXYhdL5Z_+yuMBy8B9Vft0hNu4nx5qg@mail.gmail.com>
Message-ID: <BB339F66-F547-43A4-8CB0-26685DA2E0D9@redhat.com>

This is great feedback - thank you Viliam


On May 29, 2014, at 7:20 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> Hey guys,
> 
> Viliam asked me to forward his review notes/remarks here:
> 
> Nice job, Viliam, I will incorporate your suggestions.
> 
> Btw the overall state of UX improvements is tracked here:
> 
> https://issues.jboss.org/browse/AGPUSH-671
> 
> 
> Cheers,
> 
> ~ Lukas
> 
> 
> 
> -------- Original Message --------
> Subject:	AG Console review
> Date:	Wed, 28 May 2014 15:01:19 +0200
> From:	Viliam Rockai <vrockai at redhat.com>
> To:	Matthias Wessendorf <mwessend at redhat.com>, Lukas Fryc <lfryc at redhat.com>
> CC:	Alexandre Mendonca <amendonc at redhat.com>
> 
> 
> Hi,
> 
> I went through the console code. Overall, it looks just fine. Previously
> I thought I'll just put comments into the code and make a commit. Since
> I found only a few issues, it's not worth it. So here is my list:
> 
> * The name of your angularjs module is "newadminApp". I think it should
> be something like "agconsole".
> 
> * You're missing feedback for user on many places. If the error says
> 'Something went wrong...', it doesn't say much to a user. Even changing
> it to denote the current operation would be better, something like
> 'Unable to create new application'. On most of the $resource.* methods
> you're missing the feedback, too. For most of them the information about
> success would be annoying, but maybe it could be interesting for user to
> see errors like 'Unable to get the application list, check your
> connection to the server...'. When my session to the console timed-out,
> the operation I was trying to do (renaming of app) didn't do anything,
> but I had no clue why.
> 
> * AFAIK it's considered a bad practice to use jQuery inside controllers.
> You use only two $ functions: $.extend and $.ajax, which can be replaced
> with angular.extend/angular.copy and the $resource service. If you can't
> find a way how to do something without jQuery inside controller, maybe
> creating of custom directive is the right solution, but this doesn't
> seem to be the case.
> 
> * It seems that you're using several switch statements just to assign a
> value based on input. This seems to be a good candidate for using a map.
> 
> * Notifications - they are inside ng-view pages. It looks fine and works
> for your current purposes. But if you make some new page in the future,
> which redirects you (i.e. creating a new entity, after submit, user is
> redirected to entity list with newly created stuff), you may loose the
> message. Another disadvantage of this is non-consistent L&F for feedback
> messages. The advantage is, that you're not covering any content with
> the message as LO does. 
> 
> * In installation.html I see stuff like <col width="45%">. I think this
> should be rewritten to use the bootstrap grid layout (classes like
> col-md-12...).
> 
> * We use our custom directive lo-autofocus for the 1st input in modals.
> Right after the modal pops-up, user has the focus on the first input and
> pressing enter submits the modal.
> 
> * The last one is not a problem at all, I just don't feel right about
> it :) You use $window.location.href instead $location.absUrl(). They
> seem to do the same, but since you don't use any other $window stuff,
> using $location makes more sense to me.
> 
> 
> 
> Btw, we were thinking about creating a dynamic creation of breadcrumbs,
> too. But since we didn't want to have them fully dependent on the URL
> (URLs could change for us in the future), we didn't do it. Are you sure
> you want to make url and breadcrumbs to be linked this way?
> 
> Anyway, congrats, you did good job with the console and this review
> helped me to get aware of some problems the LO console may have, too.
> 
> Viliam
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140529/92628984/attachment.html 

From jbalunas at redhat.com  Thu May 29 15:09:52 2014
From: jbalunas at redhat.com (Jay Balunas)
Date: Thu, 29 May 2014 15:09:52 -0400
Subject: [aerogear-dev] AG Push Console review
In-Reply-To: <BB339F66-F547-43A4-8CB0-26685DA2E0D9@redhat.com>
References: <CAEroY35Z_HjLVgO-bUfYXYhdL5Z_+yuMBy8B9Vft0hNu4nx5qg@mail.gmail.com>
	<BB339F66-F547-43A4-8CB0-26685DA2E0D9@redhat.com>
Message-ID: <4666D95B-B08F-4465-B447-160A57005C80@redhat.com>


On May 29, 2014, at 12:36 PM, Burr Sutter <bsutter at redhat.com> wrote:

> This is great feedback - thank you Viliam

+1 thanks a lot Villiam!

> 
> 
> On May 29, 2014, at 7:20 AM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:
> 
>> Hey guys,
>> 
>> Viliam asked me to forward his review notes/remarks here:
>> 
>> Nice job, Viliam, I will incorporate your suggestions.
>> 
>> Btw the overall state of UX improvements is tracked here:
>> 
>> https://issues.jboss.org/browse/AGPUSH-671
>> 
>> 
>> Cheers,
>> 
>> ~ Lukas
>> 
>> 
>> 
>> -------- Original Message --------
>> Subject:	AG Console review
>> Date:	Wed, 28 May 2014 15:01:19 +0200
>> From:	Viliam Rockai <vrockai at redhat.com>
>> To:	Matthias Wessendorf <mwessend at redhat.com>, Lukas Fryc <lfryc at redhat.com>
>> CC:	Alexandre Mendonca <amendonc at redhat.com>
>> 
>> 
>> Hi,
>> 
>> I went through the console code. Overall, it looks just fine. Previously
>> I thought I'll just put comments into the code and make a commit. Since
>> I found only a few issues, it's not worth it. So here is my list:
>> 
>> * The name of your angularjs module is "newadminApp". I think it should
>> be something like "agconsole".
>> 
>> * You're missing feedback for user on many places. If the error says
>> 'Something went wrong...', it doesn't say much to a user. Even changing
>> it to denote the current operation would be better, something like
>> 'Unable to create new application'. On most of the $resource.* methods
>> you're missing the feedback, too. For most of them the information about
>> success would be annoying, but maybe it could be interesting for user to
>> see errors like 'Unable to get the application list, check your
>> connection to the server...'. When my session to the console timed-out,
>> the operation I was trying to do (renaming of app) didn't do anything,
>> but I had no clue why.
>> 
>> * AFAIK it's considered a bad practice to use jQuery inside controllers.
>> You use only two $ functions: $.extend and $.ajax, which can be replaced
>> with angular.extend/angular.copy and the $resource service. If you can't
>> find a way how to do something without jQuery inside controller, maybe
>> creating of custom directive is the right solution, but this doesn't
>> seem to be the case.
>> 
>> * It seems that you're using several switch statements just to assign a
>> value based on input. This seems to be a good candidate for using a map.
>> 
>> * Notifications - they are inside ng-view pages. It looks fine and works
>> for your current purposes. But if you make some new page in the future,
>> which redirects you (i.e. creating a new entity, after submit, user is
>> redirected to entity list with newly created stuff), you may loose the
>> message. Another disadvantage of this is non-consistent L&F for feedback
>> messages. The advantage is, that you're not covering any content with
>> the message as LO does. 
>> 
>> * In installation.html I see stuff like <col width="45%">. I think this
>> should be rewritten to use the bootstrap grid layout (classes like
>> col-md-12...).
>> 
>> * We use our custom directive lo-autofocus for the 1st input in modals.
>> Right after the modal pops-up, user has the focus on the first input and
>> pressing enter submits the modal.
>> 
>> * The last one is not a problem at all, I just don't feel right about
>> it :) You use $window.location.href instead $location.absUrl(). They
>> seem to do the same, but since you don't use any other $window stuff,
>> using $location makes more sense to me.
>> 
>> 
>> 
>> Btw, we were thinking about creating a dynamic creation of breadcrumbs,
>> too. But since we didn't want to have them fully dependent on the URL
>> (URLs could change for us in the future), we didn't do it. Are you sure
>> you want to make url and breadcrumbs to be linked this way?
>> 
>> Anyway, congrats, you did good job with the console and this review
>> helped me to get aware of some problems the LO console may have, too.
>> 
>> Viliam
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140529/f661e49e/attachment-0001.html 

From cvasilak at gmail.com  Fri May 30 08:19:18 2014
From: cvasilak at gmail.com (Christos Vasilakis)
Date: Fri, 30 May 2014 15:19:18 +0300
Subject: [aerogear-dev] OAuth2 and Account Management
In-Reply-To: <20140529131856.GB33519@abstractj.org>
References: <CE1F1C3B-8EE6-47CE-815A-50A0026A8AAB@gmail.com>
	<20140529131856.GB33519@abstractj.org>
Message-ID: <301DFEAA-12FB-453D-B280-01334C7A4C90@gmail.com>


On May 29, 2014, at 4:18 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> On 2014-05-29, Corinne Krych wrote:
>> Hello all
>> 
>> It all started in that thread [1] talking about Android OAuth2 PR, but the discussion shifted on account management and storage. I think AccountManager deserves its own thread besides it?s a cross client topic (although implicit grant for pure web app is less a use case) so title is not right. Let?s fork the discussion.
>> 
>> Main goal of AccountManager is to store all the social access tokens per account. Here is the use case:
>> Some application may have to deal with several OAuth2 providers. For example in ios-cookbook, we have Shoot app which let you upload your photos to Google Drive(should change that to Google+ eventually), Facebook (and soon Instagram). When a user open Shoot for the first time and want to share to facebook, he will be prompted for OAuth2 grant, same thing for Google grant. The second photo will not trigger any grant as we?ve got the tokens. But if a user close the app and reopen it, we need something to store them if we don?t want to prompt again => AccountManager.
>> 
>> Encrypted or not encrypted?
> 
> Encrypted, always.
> 
>> Obviously access token and even more refresh token are sensitive data. Should we store them encrypted or in a secure storage like KeyChain or KeyStore? If we go that path a password is required to encrypt or access keychain, so we need an extra prompt for the user to enter password. For example, we can chage Shoot to require a password at first login to ancrypt/decrypt access token.
> 
> I think here is where offline specification comes in to place
> (https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-security-offline/index.md). We already discussed the workflow of how to protect sensitive offline data, but if it's missing something, feel free to include. Into this way we can avoid overlappings.
> 
>> I would leave this decision to the end-use rdeveloper of the app. I would go for a configurable AccountManager, being able to take a store as demo here [2].
>> 
> 
> I think it must be encrypted by default and let them disable if
> necessary.

if not mistaken, the idea is the AccountManager to create a default encrypted store and use that for storing the tokens. If the user  for some reason wants to go without an encrypted one, we can have the interface of the AccountManager accept also an instance of an arbitaty  Store<?> and utilise this after in.

am i correct no?

-
Christos


> 
>> For now proposed API:
>> As explained here [3], use same method signature authz: like for AGAuthorizer. But when use on AccountManager it will create a authzModule and add an account to store tokens.
>> 
>> What?s next?
>> We need to be able to revoke tokens and remove account from account manager.
>> 
>> Thoughts?
>> @summers : as you?re the guy behind Account Manager, if you can have a look to iOS PR [2] [3] I would love to hear about your thoughts
>> 
>> ++
>> Corinne
>> [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-OAuth2-PR-td7576.html
>> [2] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot/AGShootViewController.m#L45
>> [3] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot.md#aerogear-account-manager
> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> --
> 
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



From corinnekrych at gmail.com  Fri May 30 08:42:45 2014
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 30 May 2014 14:42:45 +0200
Subject: [aerogear-dev] OAuth2 and Account Management
In-Reply-To: <301DFEAA-12FB-453D-B280-01334C7A4C90@gmail.com>
References: <CE1F1C3B-8EE6-47CE-815A-50A0026A8AAB@gmail.com>
	<20140529131856.GB33519@abstractj.org>
	<301DFEAA-12FB-453D-B280-01334C7A4C90@gmail.com>
Message-ID: <CAL8vO=c9VnNdGT7ATFkzBLeJc1hJts=V7w0kBB3+W1md-zhZ8w@mail.gmail.com>

+1
I'll go for AccountManager taking a Store as an injection. Up to the
developer to choose the store.
Preferred scenario is to use EncryptedStore and as explain in Encrypted
Data section from offline spec, it does require password input.
Demo app (cookbook) could show the usage of AccountManager with encrypted
storage.
Let's not defined any default. but more a recommended scenario.

@summerp ok for you to remove creation of memory storage within
AccountManager and let the user inject its own store?

++
Corinne



On 30 May 2014 14:19, Christos Vasilakis <cvasilak at gmail.com> wrote:

>
> On May 29, 2014, at 4:18 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> > On 2014-05-29, Corinne Krych wrote:
> >> Hello all
> >>
> >> It all started in that thread [1] talking about Android OAuth2 PR, but
> the discussion shifted on account management and storage. I think
> AccountManager deserves its own thread besides it?s a cross client topic
> (although implicit grant for pure web app is less a use case) so title is
> not right. Let?s fork the discussion.
> >>
> >> Main goal of AccountManager is to store all the social access tokens
> per account. Here is the use case:
> >> Some application may have to deal with several OAuth2 providers. For
> example in ios-cookbook, we have Shoot app which let you upload your photos
> to Google Drive(should change that to Google+ eventually), Facebook (and
> soon Instagram). When a user open Shoot for the first time and want to
> share to facebook, he will be prompted for OAuth2 grant, same thing for
> Google grant. The second photo will not trigger any grant as we?ve got the
> tokens. But if a user close the app and reopen it, we need something to
> store them if we don?t want to prompt again => AccountManager.
> >>
> >> Encrypted or not encrypted?
> >
> > Encrypted, always.
> >
> >> Obviously access token and even more refresh token are sensitive data.
> Should we store them encrypted or in a secure storage like KeyChain or
> KeyStore? If we go that path a password is required to encrypt or access
> keychain, so we need an extra prompt for the user to enter password. For
> example, we can chage Shoot to require a password at first login to
> ancrypt/decrypt access token.
> >
> > I think here is where offline specification comes in to place
> > (
> https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-security-offline/index.md).
> We already discussed the workflow of how to protect sensitive offline data,
> but if it's missing something, feel free to include. Into this way we can
> avoid overlappings.
> >
> >> I would leave this decision to the end-use rdeveloper of the app. I
> would go for a configurable AccountManager, being able to take a store as
> demo here [2].
> >>
> >
> > I think it must be encrypted by default and let them disable if
> > necessary.
>
> if not mistaken, the idea is the AccountManager to create a default
> encrypted store and use that for storing the tokens. If the user  for some
> reason wants to go without an encrypted one, we can have the interface of
> the AccountManager accept also an instance of an arbitaty  Store<?> and
> utilise this after in.
>
> am i correct no?
>
> -
> Christos
>
>
> >
> >> For now proposed API:
> >> As explained here [3], use same method signature authz: like for
> AGAuthorizer. But when use on AccountManager it will create a authzModule
> and add an account to store tokens.
> >>
> >> What?s next?
> >> We need to be able to revoke tokens and remove account from account
> manager.
> >>
> >> Thoughts?
> >> @summers : as you?re the guy behind Account Manager, if you can have a
> look to iOS PR [2] [3] I would love to hear about your thoughts
> >>
> >> ++
> >> Corinne
> >> [1]
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-OAuth2-PR-td7576.html
> >> [2]
> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot/AGShootViewController.m#L45
> >> [3]
> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/AGIOS-190.account/Shoot/Shoot.md#aerogear-account-manager
> >
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140530/b529f7be/attachment.html 

From bruno at abstractj.org  Fri May 30 09:03:32 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 30 May 2014 10:03:32 -0300
Subject: [aerogear-dev] IRC meeting for Offline spec
Message-ID: <20140530130332.GA9911@abstractj.org>

Good morning, after talking with Corinne and Christos we are planning a
IRC meeting on Monday (Jun 2) 12 p.m BRT, just after our team meeting.

The goal is to discuss the offline spec, what we've been planning and
how it could help OAuth2 implementation on the client side.

If you want to join, let us know.

--

abstractj

From hbons at redhat.com  Fri May 30 09:41:49 2014
From: hbons at redhat.com (Hylke Bons)
Date: Fri, 30 May 2014 14:41:49 +0100
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <5374DB1B.9020405@redhat.com>
References: <5374DB1B.9020405@redhat.com>
Message-ID: <53888A9D.8020308@redhat.com>

Hey,

I've finished the HTML/CSS implementation, which can be found here: 
https://github.com/hbons/admin-mockup

It needs a tiny bit of cleanup in the code itself, but it's all there.

Preview screenshots:
https://raw.githubusercontent.com/hbons/admin-mockup/master/dashboard-preview.png
https://raw.githubusercontent.com/hbons/admin-mockup/master/activity-preview.png

Thanks,

Hylke


On 15/05/2014 16:19, Hylke Bons wrote:
> Hey,
>
> Here's an initial version:
> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>
> I tried to incorporate most wishes expressed in the other thread.
>
> Most notable things:
> - Landing page with an overview of stats, most active apps, and error
> messages
> - Activity table shows both registration and notification events
> - Activity table is per variant, and not all activity on the server.
> Unless there's a usecase to have every event for every app/variant in a
> table I don't think we actually need it. The important thing is to get
> to error messages easily.
>
> Things to do/think about:
> - links/entry points to the activity table
> - filtering the activity table
>
> This is just the first iteration and we will improve on this.
> Let me know what you think.
>
> Thanks,
>
> Hylke
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


From scm.blanc at gmail.com  Fri May 30 10:00:46 2014
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 30 May 2014 16:00:46 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <53888A9D.8020308@redhat.com>
References: <5374DB1B.9020405@redhat.com>
	<53888A9D.8020308@redhat.com>
Message-ID: <CAD_dpu2P3nW2pVPDd8HhJiBofDjqrmQ_W-6D1TC8H-WoaGQZFQ@mail.gmail.com>

Hey !

Looks nice !
I will probably start integrating this on Monday.

Sebi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140530/28c16d90/attachment.html 

From tkriz at redhat.com  Fri May 30 11:27:23 2014
From: tkriz at redhat.com (Tadeas Kriz)
Date: Fri, 30 May 2014 17:27:23 +0200
Subject: [aerogear-dev] Unified Push responds with 404 if no installations
	exist for a variant
Message-ID: <2597BEEE-33E3-4A83-A094-0100A2009775@redhat.com>

Hey,

while aligning integration tests with 0.11.0, I?ve found a changed behaviour when requesting list of installations for a variant. Before the change, if I used wrong (non-existent) variant ID, I got 404 Not Found, and when I used existing variant ID, I got a response with an empty json array. That way I could easily say if the variant id was wrong or not. Now, I get 404 even when the variant ID is correct, but the variant has no installations. The old code: [1] and the new code: [2]

My question is, if this is by design? And if so, why doesn?t variant listing work the same way? From [3] I understand that it responds with an empty json array when there are no android variants for the given push application ID and with 404 if the push application ID is wrong. I just want to be sure before changing integration tests to expect the 404 instead of an empty json array.

Thanks

1 - https://github.com/aerogear/aerogear-unifiedpush-server/blob/2ecf73ea4e3bf4d82705222a219a62f7c8af04bb/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/InstallationManagementEndpoint.java#L56-L60
2 - https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/InstallationManagementEndpoint.java#L62-L64
3 - https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AndroidVariantEndpoint.java#L84-L86

?
Tadeas Kriz



From matzew at apache.org  Fri May 30 11:36:34 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 30 May 2014 17:36:34 +0200
Subject: [aerogear-dev] Unified Push responds with 404 if no
	installations exist for a variant
In-Reply-To: <2597BEEE-33E3-4A83-A094-0100A2009775@redhat.com>
References: <2597BEEE-33E3-4A83-A094-0100A2009775@redhat.com>
Message-ID: <CAAg5f2QHvt8YeAoGzgh1jM36ODkyy_frqmZ5+Gaxtpba8kS3JQ@mail.gmail.com>

On Fri, May 30, 2014 at 5:27 PM, Tadeas Kriz <tkriz at redhat.com> wrote:

> Hey,
>
> while aligning integration tests with 0.11.0, I?ve found a changed
> behaviour when requesting list of installations for a variant. Before the
> change, if I used wrong (non-existent) variant ID, I got 404 Not Found, and
> when I used existing variant ID, I got a response with an empty json array.
> That way I could easily say if the variant id was wrong or not. Now, I get
> 404 even when the variant ID is correct, but the variant has no
> installations. The old code: [1] and the new code: [2]
>
> My question is, if this is by design?


Nope - that is a bug;

Can you file a JIRA for it ?

Thanks!



> And if so, why doesn?t variant listing work the same way? From [3] I
> understand that it responds with an empty json array when there are no
> android variants for the given push application ID and with 404 if the push
> application ID is wrong. I just want to be sure before changing integration
> tests to expect the 404 instead of an empty json array.
>
> Thanks
>
> 1 -
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/2ecf73ea4e3bf4d82705222a219a62f7c8af04bb/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/InstallationManagementEndpoint.java#L56-L60
> 2 -
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/InstallationManagementEndpoint.java#L62-L64
> 3 -
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AndroidVariantEndpoint.java#L84-L86
>
> ?
> Tadeas Kriz
>
>


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140530/dff05681/attachment.html 

From bruno at abstractj.org  Fri May 30 12:03:33 2014
From: bruno at abstractj.org (Bruno Oliveira)
Date: Fri, 30 May 2014 13:03:33 -0300
Subject: [aerogear-dev] Instructions to build admin-ui
Message-ID: <20140530160333.GA20669@abstractj.org>

Good morning,

I'm looking for instructions of how to build admin-ui correctly. Where could I find it?

Currently I tried
https://github.com/aerogear/aerogear-unifiedpush-server-admin-ui/blob/master/README.md
and also
https://github.com/aerogear/collateral/wiki/UPS-Admin-Console-Process.
The reason why I want this is because Sebastien managed to get it
working
https://github.com/abstractj/aerogear-unifiedpush-server/tree/angular-auth
and something very dirty might be happening with my environment.

What I want to do is very simple. Trigger the following event:
https://github.com/abstractj/aerogear-unifiedpush-server/commit/aeed989288ae0c42a8f163b303fb1d89a029b635#diff-bd44ccad477ae267b4939a7797ddc9eeR90.

I also tried to copy these files to server/src/main/webapp/ but it
didnt'work.

Thanks in advance.

--

abstractj

From lukas.fryc at gmail.com  Fri May 30 12:44:15 2014
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Fri, 30 May 2014 18:44:15 +0200
Subject: [aerogear-dev] Instructions to build admin-ui
In-Reply-To: <20140530160333.GA20669@abstractj.org>
References: <20140530160333.GA20669@abstractj.org>
Message-ID: <CAEroY36Yg+jrx1OwSZ6T=HYXEok8b9QEdtOz6tes8EFCC6gCxw@mail.gmail.com>

Hey man,

I can't find the instructions myself atm.
(they could have been lost during merge (?))

I found this copy, which is almost up to date:
https://github.com/lfryc/aerogear-unifiedpush-server/tree/master/admin-ui#using-with-jboss-eapwildfly

Basically, run

upload exploded ag-push.war/ to JBoss AS 7.1.
$ cd admin-ui/
$ grunt server
modify generated local-config.json to point to that exploded war
$ grunt server

Hope it helps.

Meanwhile, I will update the instructions in the master.

Cheers,

~ Lukas


On Fri, May 30, 2014 at 6:03 PM, Bruno Oliveira <bruno at abstractj.org> wrote:

> Good morning,
>
> I'm looking for instructions of how to build admin-ui correctly. Where
> could I find it?
>
> Currently I tried
>
> https://github.com/aerogear/aerogear-unifiedpush-server-admin-ui/blob/master/README.md
> and also
> https://github.com/aerogear/collateral/wiki/UPS-Admin-Console-Process.
> The reason why I want this is because Sebastien managed to get it
> working
> https://github.com/abstractj/aerogear-unifiedpush-server/tree/angular-auth
> and something very dirty might be happening with my environment.
>
> What I want to do is very simple. Trigger the following event:
>
> https://github.com/abstractj/aerogear-unifiedpush-server/commit/aeed989288ae0c42a8f163b303fb1d89a029b635#diff-bd44ccad477ae267b4939a7797ddc9eeR90
> .
>
> I also tried to copy these files to server/src/main/webapp/ but it
> didnt'work.
>
> Thanks in advance.
>
> --
>
> 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/20140530/c7d95cba/attachment.html 

From daniel at passos.me  Fri May 30 14:48:44 2014
From: daniel at passos.me (Daniel Passos)
Date: Fri, 30 May 2014 15:48:44 -0300
Subject: [aerogear-dev] [QUICKSTART] Information for the mobile clients
In-Reply-To: <CAD_dpu3v5yutnmAzwaHs5r3fRfBhHd4oY-CvqP-C5yhnD13ReA@mail.gmail.com>
References: <CAD_dpu0q0X76hZj61FgDsqLB5D3MShknP7UXQDF0FJV+bJ7c=A@mail.gmail.com>
	<53502FF3.8010809@abstractj.org>
	<CAD_dpu0uKAwHh2vcXf3mr00O-2Za1dPG3wMdvZd4NbjfGiZQVw@mail.gmail.com>
	<CAKjsGbs1vusKkMBKFmjuqe3tC_H_ERtyaNhRxFP_9Qq1sdVaMg@mail.gmail.com>
	<CAD_dpu3v5yutnmAzwaHs5r3fRfBhHd4oY-CvqP-C5yhnD13ReA@mail.gmail.com>
Message-ID: <CAKjsGbtZfJ1vSJfSz5pH4_UpwgJskyf+tdg2VQ8UctQduT3zGg@mail.gmail.com>

Someone know that I am doing wrong?
Login

curl -v -b cookies.txt -c cookies.txt \
     -H "Accept: application/json" \
     -H "Content-type: application/json" \
     -u "myuser:mypass" \
     -X GET http://quickstarts-edewit.rhcloud.com/rest/security/user/info

Update Contact

curl -v -b cookies.txt -c cookies.txt \
     -H "Accept: application/json" \
     -H "Content-type: application/json" \
     -X PUT \
     -d '{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example at example.com",
"birthDate":"2001-03-24"}' \
      http://quickstarts-edewit.rhcloud.com/rest/contacts/7

? Passos
?


On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Since we changed the use case for the Push part (now we broadcast) ,
> passing a alias to UPS is not relevant anymore. For the login it's indeed
> "loginName" to be passed in the auth header along with the password.
>
>
>
> On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel at passos.me> wrote:
>
>> To register I send "userName" and the login response "loginName"?
>>
>> -- Passos
>>
>>
>>
>> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> Sure !
>>> This is just a version to ease the client development.
>>> I will ask PL team and Joshua their plans around HSTS and HTTPS.
>>> In the mean time we can track all of this with
>>> https://issues.jboss.org/browse/AGPUSH-596
>>>
>>> Thx for the comment !
>>> Sebi
>>>
>>>
>>> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno at abstractj.org>
>>> wrote:
>>>
>>>> If your idea is to be secure, please make sure to use HTTPS and enforce
>>>> users to be redirected. We did it in the past with HSTS on AG Security,
>>>> might not be hard to copy & paste.
>>>>
>>>> Sebastien Blanc wrote:
>>>> > And because I love you, I deployed on OpenShift a version of this
>>>> secured
>>>> > backend to ease the development of the clients !
>>>> >
>>>> > If you browse to http://contacts-sblanc.rhcloud.com/ you will even
>>>> see the
>>>> > mobile web client. This deployed version contains also the Push
>>>> Message
>>>> > endpoint.
>>>>
>>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.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/20140530/e5edb53a/attachment-0001.html 

From matzew at apache.org  Sat May 31 01:28:05 2014
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 31 May 2014 07:28:05 +0200
Subject: [aerogear-dev] First go at stats/activity wireframes
In-Reply-To: <CAD_dpu2P3nW2pVPDd8HhJiBofDjqrmQ_W-6D1TC8H-WoaGQZFQ@mail.gmail.com>
References: <5374DB1B.9020405@redhat.com> <53888A9D.8020308@redhat.com>
	<CAD_dpu2P3nW2pVPDd8HhJiBofDjqrmQ_W-6D1TC8H-WoaGQZFQ@mail.gmail.com>
Message-ID: <CAAg5f2Rne99mhV8p4Ux0mvvA2Fvir8EZe4aWkhDs_xwObyXw8Q@mail.gmail.com>

Awesome!

Hylke, I marked your two tickets as resolved:
https://issues.jboss.org/browse/AGPUSH-579
https://issues.jboss.org/browse/AGPUSH-580

@Sebi: I assigned this to you:
https://issues.jboss.org/browse/AGPUSH-636


On Fri, May 30, 2014 at 4:00 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Hey !
>
> Looks nice !
> I will probably start integrating this on Monday.
>
> 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/20140531/6a9642f6/attachment.html